Contents

Mitsubishi R02CPU Controller CPU User's Manual PDF

1 of 716
1 of 716

Summary of Content for Mitsubishi R02CPU Controller CPU User's Manual PDF

MELSEC iQ-R Programmable Controller CPU Module User's Manual

-R00CPU -R01CPU -R02CPU -R04CPU -R04ENCPU -R08CPU -R08ENCPU -R16CPU -R16ENCPU -R32CPU -R32ENCPU -R120CPU -R120ENCPU

SAFETY PRECAUTIONS (Read these precautions before using this product.) Before using MELSEC iQ-R series programmable controllers, please read the manuals for the product and the relevant manuals introduced in those manuals carefully, and pay full attention to safety to handle the product correctly. If products are used in a different way from that specified by manufacturers, the protection function of the products may not work properly. In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".

Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious consequences. Observe the precautions of both levels because they are important for personal and system safety. Make sure that the end users read this manual and then keep the manual in a safe place for future reference.

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.

1

2

[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) Emergency stop circuits, protection circuits, and protective interlock circuits for conflicting

operations (such as forward/reverse rotations or upper/lower limit positioning) must be configured external to the programmable controller.

(2) When the programmable controller detects an abnormal condition, it stops the operation and all outputs are: Turned off if the overcurrent or overvoltage protection of the power supply module is activated. Held or turned off according to the parameter setting if the self-diagnostic function of the CPU

module detects an error such as a watchdog timer error. (3) All outputs may be turned on if an error occurs in a part, such as an 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 "General Safety Requirements" in the MELSEC iQ-R Module Configuration Manual.

(4) Outputs may remain on or off due to a failure of a component such as a relay and transistor in an output circuit. Configure an external circuit for monitoring output signals that could cause a serious accident.

In an output circuit, 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.

Configure a circuit so that the external power supply is turned off first and then the programmable controller. If the programmable controller is turned off 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 manuals for the network used. For the manuals, please consult your local Mitsubishi representative. Failure to do so may result in an accident due to an incorrect output or malfunction.

When connecting an external device with a CPU module or intelligent function module to modify data of a running programmable controller, configure an interlock circuit in the program to ensure that the entire system will always operate safely. For other forms of control (such as program modification, parameter change, forced output, or operating status change) of a running programmable controller, read the relevant manuals carefully and ensure that the operation is safe before proceeding. Improper operation may damage machines or cause accidents.

[Design Precautions]

[Design Precautions]

WARNING Especially, when a remote programmable controller is controlled by an external device, immediate

action cannot be taken if a problem occurs in the programmable controller due to a communication failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions to be taken between the external device and CPU module in case of a communication failure.

Do not write any data to the "system area" and "write-protect area" of the buffer memory in the module. Also, do not use any "use prohibited" signals as an output signal from the CPU module to each module. Doing so may cause malfunction of the programmable controller system. For the "system area", "write-protect area", and the "use prohibited" signals, refer to the user's manual for the module used.

If a communication cable is disconnected, the network may be unstable, resulting in a communication failure of multiple stations. Configure an interlock circuit in the program to ensure that the entire system will always operate safely even if communications fail. Incorrect output or malfunction due to a communication failure may result in an accident.

CAUTION Do not install the control lines or communication cables together with the main circuit lines or power

cables. Doing so may result in malfunction due to electromagnetic interference. Keep a distance of 100mm or more between those cables.

During control of an inductive load such as a lamp, heater, or solenoid valve, a large current (approximately ten times greater than normal) may flow when the output is turned from off to on. Therefore, use a module that has a sufficient current rating.

After the CPU module is powered on or is reset, the time taken to enter the RUN status varies depending on the system configuration, parameter settings, and/or program size. Design circuits so that the entire system will always operate safely, regardless of the time.

Do not power off the programmable controller or reset the CPU module while the settings are being written. Doing so will make the data in the flash ROM and SD memory card undefined. The values need to be set in the buffer memory and written to the flash ROM and SD memory card again. Doing so also may cause malfunction or failure of the module.

When changing the operating status of the CPU module from external devices (such as the remote RUN/STOP functions), select "Do Not Open by Program" for "Opening Method" of "Module Parameter". If "Open by Program" is selected, an execution of the remote STOP function causes the communication line to close. Consequently, the CPU module cannot reopen the line, and external devices cannot execute the remote RUN function.

3

4

[Security Precautions]

[Installation Precautions]

[Installation Precautions]

WARNING To maintain the security (confidentiality, integrity, and availability) of the programmable controller and

the system against unauthorized access, denial-of-service (DoS) attacks, computer viruses, and other cyberattacks from external devices via the network, take appropriate measures such as firewalls, virtual private networks (VPNs), and antivirus solutions.

WARNING Shut off the external power supply (all phases) used in the system before mounting or removing the

module. Failure to do so may result in electric shock or cause the module to fail or malfunction.

CAUTION Use the programmable controller in an environment that meets the general specifications in the Safety

Guidelines (IB-0800525). Failure to do so may result in electric shock, fire, malfunction, or damage to or deterioration of the product.

To mount a module, place the concave part(s) located at the bottom onto the guide(s) of the base unit, and push in the module until the hook(s) located at the top snaps into place. Incorrect interconnection may cause malfunction, failure, or drop of the module.

To mount a module with no module fixing hook, place the concave part(s) located at the bottom onto the guide(s) of the base unit, push in the module, and fix it with screw(s). Incorrect interconnection 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 screws within the specified torque range. Undertightening can cause drop of the component or wire, short circuit, or malfunction. Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction. For the specified torque range, refer to the MELSEC iQ- R Module Configuration Manual.

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

When using an SD memory card, fully insert it into the SD memory card slot. Check that it is inserted completely. Poor contact may cause malfunction.

Securely insert an extended SRAM cassette or a battery-less option cassette into the cassette connector of the CPU module. After insertion, close the cassette cover and check that the cassette is inserted completely. Poor contact may cause malfunction.

Beware that the module could be very hot while power is on and immediately after power-off. Do not directly touch any conductive parts and electronic components of the module, SD memory

card, extended SRAM cassette, battery-less option cassette, or connector. Doing so can cause malfunction or failure of the module.

[Wiring Precautions]

[Wiring Precautions]

WARNING Shut off the external power supply (all phases) used in the system before installation and wiring.

Failure to do so may result in electric shock or cause the module to fail or malfunction. After installation and wiring, attach a blank cover module (RG60) to each empty slot before powering

on the system for operation. Also, attach an extension connector protective cover*1 to each unused extension cable connector as necessary. Directly touching any conductive parts of the connectors while power is on may result in electric shock. *1 For details, please consult your local Mitsubishi Electric representative.

CAUTION Individually ground the FG and LG terminals of the programmable controller with a ground resistance

of 100 ohms or less. 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 signal 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 fire or failure.

Connectors for external devices must be crimped or pressed with the tool specified by the manufacturer, or must be correctly soldered.

Securely connect the connector to the module. Poor contact may cause malfunction. Do not install the control lines or communication cables together with the main circuit lines or power

cables. Doing so may result in malfunction due to noise. Keep a distance of 100mm or more between those cables.

Place the cables in a duct or clamp them. If not, dangling cables may swing or inadvertently be pulled, resulting in malfunction or damage to modules or cables. In addition, the weight of the cables may put stress on modules in an environment of strong vibrations and shocks. Do not clamp the extension cables with the jacket stripped. Doing so may change the characteristics of the cables, resulting in malfunction.

Check the interface type and correctly connect the cable. Incorrect wiring (connecting the cable to an incorrect interface) may cause failure of the module and external device.

Tighten the terminal screws or connector screws within the specified torque range. Undertightening can cause drop of the screw, short circuit, fire, or malfunction. Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.

When disconnecting the cable from the module, do not pull the cable by the cable part. For the cable with connector, hold the connector part of the cable. For the cable connected to the terminal block, loosen the terminal screw. Pulling the cable connected to the module may result in malfunction or damage to the module or cable.

5

6

[Wiring Precautions]

[Startup and Maintenance Precautions]

CAUTION Prevent foreign matter such as dust or wire chips from entering the module. Such foreign matter can

cause a fire, failure, or malfunction. When a protective film is attached to the top of the module, remove it before system operation. If not,

inadequate heat dissipation of the module may cause a fire, failure, or malfunction. 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 qualified maintenance personnel with knowledge of protection against electric shock. For wiring, refer to the MELSEC iQ-R Module Configuration Manual.

For Ethernet cables to be used in the system, select the ones that meet the specifications in the user's manual for the module used. If not, normal data transmission is not guaranteed.

WARNING Do not touch any terminal while power is on. Doing so will cause electric shock or malfunction. Correctly connect the battery connector. Do not charge, disassemble, heat, short-circuit, solder, or

throw the battery into the fire. Also, do not expose it to liquid or strong shock. Doing so will cause the battery to produce heat, explode, ignite, or leak, resulting in injury and fire.

Shut off the external power supply (all phases) used in the system before cleaning the module or retightening the terminal screws, connector screws, or module fixing screws. Failure to do so may result in electric shock.

[Startup and Maintenance Precautions]

CAUTION When connecting an external device with a CPU module or intelligent function module to modify data

of a running programmable controller, configure an interlock circuit in the program to ensure that the entire system will always operate safely. For other forms of control (such as program modification, parameter change, forced output, or operating status change) of a running programmable controller, read the relevant manuals carefully and ensure that the operation is safe before proceeding. Improper operation may damage machines or cause accidents.

Especially, when a remote programmable controller is controlled by an external device, immediate action cannot be taken if a problem occurs in the programmable controller due to a communication failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions to be taken between the external device and CPU module in case of a communication failure.

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 away in all directions from the programmable controller. Failure to do so may cause malfunction.

Shut off the external power supply (all phases) used in the system before mounting or removing the module. Failure to do so may cause the module to fail or malfunction.

Tighten the screws within the specified torque range. Undertightening can cause drop of the component or wire, short circuit, or malfunction. Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.

After the first use of the product, do not perform each of the following operations more than 50 times (IEC 61131-2/JIS B 3502 compliant). Exceeding the limit may cause malfunction.

Mounting/removing the module to/from the base unit Inserting/removing the extended SRAM cassette or battery-less option cassette to/from the

CPU module Mounting/removing the terminal block to/from the module Connecting/disconnecting the extension cable to/from the base unit

After the first use of the product, do not insert/remove the SD memory card to/from the CPU module more than 500 times. Exceeding the limit may cause malfunction.

Do not touch the metal terminals on the back side of the SD memory card. Doing so may cause malfunction or failure of the module.

Do not touch the integrated circuits on the circuit board of an extended SRAM cassette or a battery- less option cassette. Doing so may cause malfunction or failure of the module.

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.

Use a clean and dry cloth to wipe off dirt on the module.

7

8

[Startup and Maintenance Precautions]

[Operating Precautions]

CAUTION Startup and maintenance of a control panel must be performed by qualified maintenance personnel

with knowledge of protection against electric shock. Lock the control panel so that only qualified maintenance personnel can operate it.

Before handling the module, touch a conducting object such as a grounded metal to discharge the static electricity from the human body. Wearing a grounded antistatic wrist strap is recommended. Failure to do so may cause the module to fail or malfunction.

CAUTION When changing data and operating status, and modifying program of the running programmable

controller from an external device such as a personal computer connected to an intelligent function module, read relevant manuals carefully and ensure the safety before operation. Incorrect change or modification may cause system malfunction, damage to the machines, or accidents.

Do not power off the programmable controller or reset the CPU module while the setting values in the buffer memory are being written to the flash ROM in the module. Doing so will make the data in the flash ROM and SD memory card undefined. The values need to be set in the buffer memory and written to the flash ROM and SD memory card again. Doing so also may cause malfunction or failure of the module.

[Computer Connection Precautions]

[Disposal Precautions]

[Transportation Precautions]

CAUTION When connecting a personal computer to a module having a USB interface, observe the following

precautions as well as the instructions described in the manual for the personal computer used. Failure to do so may cause the module to fail. (1) When the personal computer is AC-powered

When the personal computer has a 3-pin AC plug or an AC plug with a grounding wire, connect the plug to a grounding receptacle or ground the grounding wire. Ground the personal computer and the module with a ground resistance of 100 ohms or less. When the personal computer has a 2-pin AC plug without a grounding wire, connect the computer to the module by following the procedure below. For power supplied to the personal computer and the module, using the same power source is recommended. 1. Unplug the personal computer from the AC receptacle. 2. Check that the personal computer is unplugged. Then, connect the personal computer to the module with a USB cable. 3. Plug the personal computer into the AC receptacle.

(2) When the personal computer is battery-powered The personal computer can be connected to the module without taking specific measures.

For details, refer to the following. Cautions When Using Mitsubishi Programmable Controllers or GOTs Connected to a Personal Computer With the RS-232/USB Interface (FA-A-0298) When the USB cable used is the GT09-C30USB-5P manufactured by Mitsubishi Electric, specific measures are not required to connect the AC-powered personal computer to the module. However, note that the signal ground (SG) is common for the module and its USB interface. Therefore, if an SG potential difference occurs between the module and the connected devices, it causes failures of the module and the connected devices.

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 on battery regulations in EU member states, refer to the MELSEC iQ-R Module Configuration Manual.

CAUTION When transporting lithium batteries, follow the transportation regulations. For details on the regulated

models, refer to the MELSEC iQ-R Module Configuration Manual. The halogens (such as fluorine, chlorine, bromine, and iodine), which are contained in a fumigant

used for disinfection and pest control of wood packaging materials, may cause failure of the product. Prevent the entry of fumigant residues into the product or consider other methods (such as heat treatment) instead of fumigation. The disinfection and pest control measures must be applied to unprocessed raw wood.

9

10

INTRODUCTION Thank you for purchasing the Mitsubishi Electric MELSEC iQ-R series programmable controllers. This manual describes the procedures before operation, specifications, functions, devices, parameters, and troubleshooting of the relevant products listed below. Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the functions and performance of the MELSEC iQ-R series programmable controller to handle the product correctly. When applying the program examples provided in this manual to an actual system, ensure the applicability and confirm that it will not cause system control problems. Note that the menu names and operating procedures may differ depending on an operating system in use and its version. When reading this manual, replace the names and procedures with the applicable ones as necessary. Please make sure that the end users read this manual.

Relevant products

When using the R00CPU, R01CPU, and R02CPU, replace terms of some LEDs as follows to read this manual. PROGRAM RUN LED P RUN LED CARD READY LED C RDY LED CARD ACCESS LED C ACS LED FUNCTION LED FUNC LED

Item Model CPU module R00CPU, R01CPU, R02CPU, R04CPU, R04ENCPU, R08CPU, R08ENCPU, R16CPU, R16ENCPU, R32CPU, R32ENCPU,

R120CPU, R120ENCPU

C O

N TE

N TS

CONTENTS SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 GENERIC TERMS AND ABBREVIATIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

PART 1 PART NAMES

CHAPTER 1 CPU Module 26 1.1 R00CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 1.2 R01CPU, R02CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 1.3 RnCPU (except for R00CPU, R01CPU, and R02CPU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 1.4 RnENCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

CHAPTER 2 Extended SRAM Cassette and Battery-less Option Cassette 35

PART 2 PROCEDURES BEFORE OPERATION

CHAPTER 3 START-UP PROCEDURE 38 3.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 3.2 Installing a Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.3 Inserting or Removing an Extended SRAM Cassette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Insertion procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Removal procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.4 Inserting and Removing an SD Memory Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Insertion procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Removal procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.5 Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3.6 Connecting a Personal Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3.7 Initializing the CPU Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.8 Setting Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.9 Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Registering labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Inserting program elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Inserting POUs by key input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.10 Converting the Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.11 Saving the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.12 Writing Data to the Programmable Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.13 Resetting the CPU Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.14 Executing the Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 3.15 Monitoring the Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

11

12

PART 3 SYSTEM CONFIGURATION

CHAPTER 4 SYSTEM CONFIGURATION 58

PART 4 SPECIFICATIONS

CHAPTER 5 PERFORMANCE SPECIFICATIONS 62 5.1 CPU Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Hardware specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Programming specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.2 Extended SRAM Cassette. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 5.3 Battery-less Option Cassette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

PART 5 CPU MODULE OPERATION

CHAPTER 6 RUNNING A PROGRAM 70 6.1 Scan Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Initial processing (when powered on or switched to RUN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 I/O refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Program operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 END processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6.2 Scan Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Initial scan time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Constant scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Device/label access service processing setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

6.3 Data Communication and I/O Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Data communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 I/O processing and response delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Refresh mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Direct mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

6.4 Program Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 6.5 Program Execution Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Initial execution type program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Scan execution type program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Fixed scan execution type program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Event execution type program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Standby type program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Execution type change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Group setting for refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

6.6 Subroutine Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 6.7 Interrupt Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Interrupt period setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Interrupt enabled during instruction execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Processing at interrupt program startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Multiple interrupt function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

C O

N TE

N TS

CHAPTER 7 CPU MODULE OPERATION PROCESSING 120 7.1 Operation Processing by Operating Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 7.2 Operation Processing When Operating Status Is Changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Output mode at operating status change (STOP to RUN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 7.3 Operation Processing at Momentary Power Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

CHAPTER 8 MEMORY CONFIGURATION OF THE CPU MODULE 124 8.1 Memory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Program memory/program cache memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Device/label memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Data memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Function memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Refresh memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 CPU buffer memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Signal flow memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 SD memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

8.2 File Size Unit in Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 8.3 Memory Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Initialization and value clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 8.4 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

File types and storage memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 File operation available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 File size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

PART 6 FUNCTIONS

CHAPTER 9 FUNCTION LIST 144

CHAPTER 10 CLOCK FUNCTION 148 10.1 Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Clock data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Changing the clock data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Reading the clock data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Precautions on the clock data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

10.2 Setting Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 10.3 Daylight Saving Time Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Daylight saving time setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Timing of daylight saving time adjustment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Daylight saving time function operation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Operation of other functions using clock data during daylight saving time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

10.4 System Clock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Special relay used for system clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Special register used for system clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

CHAPTER 11 WRITING DATA TO THE CPU MODULE 155 11.1 Writing Data to the Programmable Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 11.2 Online Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Online change (ladder block). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

13

14

File batch online change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 11.3 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

CHAPTER 12 RAS FUNCTIONS 166 12.1 Scan Monitoring Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Scan time monitoring time setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Watchdog timer reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

12.2 Self-Diagnostics Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Self-diagnostics timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Check method of error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 CPU module operation upon error detection setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Error detection invalidation setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

12.3 Error Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 12.4 Event History Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Event history setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Logging of the event history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Viewing the event history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Clearing the event history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

12.5 Program Cache Memory Auto Recovery Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

CHAPTER 13 REMOTE OPERATION 187 13.1 Remote RUN/STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Executing method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

13.2 Remote PAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Executing method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

13.3 Setting RUN-PAUSE Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 13.4 Remote RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Enabling remote RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Executing method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

CHAPTER 14 BOOT OPERATION 191 14.1 Boot Operation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 14.2 Specifiable File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 14.3 Allowed Maximum Number of Boot Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 14.4 Configuring the Boot Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 14.5 Writing Boot Settings and Boot Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 14.6 Operation When Security Functions Are Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

When a security key is set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 When a file password is set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

14.7 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

CHAPTER 15 MONITOR FUNCTION 196 15.1 Real-Time Monitor Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 15.2 Scan Time Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 15.3 Specified Program Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

C O

N TE

N TS

CHAPTER 16 TEST FUNCTION 204 16.1 External Input/Output Forced On/Off Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 16.2 Device Test with Execution Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

CHAPTER 17 DATA LOGGING FUNCTION 226 17.1 Data Logging Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 17.2 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 17.3 Data to Be Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Number of data points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Data type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Data to be collected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

17.4 Data Collection Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Each scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Time specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Interrupt occurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Condition specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

17.5 Logging Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Operating procedure for continuous logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Operating procedure for trigger logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

17.6 Data Logging File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Storage format of data logging files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Storage location of data logging files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

17.7 States of the Data Logging Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Data logging states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 LED status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

17.8 Steps Until the Collected Data Is Saved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Internal buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Switching to a storage file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

17.9 Missing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Conditions under which missing data occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

17.10 Data Logging File Transfer (Auto Transfer to FTP Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 17.11 Data Logging File Transfer to Data Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 17.12 Setting Behavior at the Time of Transition to RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 17.13 Auto Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 17.14 SD Memory Card Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 17.15 SD Memory Card Life When the Data Logging Function Is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 17.16 Errors Generated During Data Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 17.17 Special Relay and Special Register Used by the Data Logging Function . . . . . . . . . . . . . . . . . . . . . . . . . 291 17.18 Precautions to Take When Using the Data Logging Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

CHAPTER 18 DEBUG FUNCTION 304 18.1 Memory Dump Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Object data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Trigger condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Procedure for memory dump. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Flow of data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Memory dump file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 States of the memory dump function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Sizes of files used for the memory dump function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Special relay and special register used in the memory dump function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

15

16

Precautions for the memory dump function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

CHAPTER 19 DATABASE FUNCTION 315 19.1 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 19.2 Database Access Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Usage procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Creating Unicode text files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Transactions for databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Folder configuration of databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Timing of database update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

19.3 CPU Module Database Access (from External Device) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Usage procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Built-in database access setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Creating a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Adding a database to the ODBC data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Application example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

CHAPTER 20 PID CONTROL FUNCTION 344

CHAPTER 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 346 21.1 Backup Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Backup processing triggered by turning on SM1351. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Automatic backup using SD944 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Checking backup errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

21.2 Restoration Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Restoration processing triggered by turning on SM1354 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Automatic restoration using SD955. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Checking restoration errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

CHAPTER 22 MULTIPLE CPU SYSTEM FUNCTION 368 22.1 Out-of-group I/O Fetch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Accessing controlled module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Accessing non-controlled module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

22.2 Operation Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Stop setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Synchronous startup setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 Clock data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

22.3 Multiple CPU Parameter Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 22.4 Data Communication Between CPU Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Memory to be used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Fixed scan communication setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Error detection setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Module-by-module data guarantee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Communication through refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 Communication through direct access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 Data assurance by program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

C O

N TE

N TS

Communication between CPU modules in error state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 22.5 Multiple CPU Synchronous Interrupt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

Execution timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Multiple interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398

CHAPTER 23 SECURITY FUNCTION 399 23.1 Write-Protect Function for Device Data (from Outside the CPU Module) . . . . . . . . . . . . . . . . . . . . . . . . . 401

CHAPTER 24 SEQUENCE SCAN SYNCHRONIZATION SAMPLING FUNCTION 405

CHAPTER 25 ROUTING SETTING 407 25.1 Setting Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 25.2 Setting Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 25.3 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

CHAPTER 26 FIRMWARE UPDATE FUNCTION 409

PART 7 DEVICES, LABELS, AND CONSTANTS

CHAPTER 27 DEVICES 412 27.1 Device List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 27.2 Device Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Range of use of device points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 27.3 User Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

Input (X). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Output (Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Internal relay (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Latch relay (L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Link relay (B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Annunciator (F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Link special relay (SB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Edge relay (V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Step relay (S). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Data register (D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Link register (W) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Link special register (SW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

27.4 System Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 Function device (FX/FY/FD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 Special relay (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Special register (SD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

27.5 Link Direct Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Specification method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Specification range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 Difference from link refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436

27.6 Module Access Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

27.7 CPU Buffer Memory Access Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

17

18

Specification method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 27.8 Index Register (Z/LZ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

16-bit index modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 32-bit index modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Device for which index modification can be performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Index register setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Combination of index modification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

27.9 File Register (R/ZR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Specification method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Setting file registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Clearing file registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

27.10 Refresh Data Register (RD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 Refresh memory setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

27.11 Nesting (N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 27.12 Pointer (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Global pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 Local pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 Pointer setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

27.13 Interrupt Pointer (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 Interrupt factors of the interrupt pointer numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 The priority for the interrupt pointer numbers and interrupt factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

27.14 Network No. Specification Device (J) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 27.15 I/O No. Specification Device (U) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 27.16 SFC Block Device (BL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 27.17 SFC Transition Device (TR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 27.18 Global Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 27.19 Local Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 27.20 Indirect Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456

CHAPTER 28 LABELS 457 28.1 Global Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 28.2 Local Labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 28.3 Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 28.4 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 28.5 Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462 28.6 Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 28.7 Label Access Setting from External Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468

Configuration procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 Label communication data storage location and operation at the time of each setting operation . . . . . . . . . . . 470 File operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470

28.8 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

CHAPTER 29 LATCH FUNCTION 473 29.1 Latch with Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

Types of latch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Applicable devices and labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 Setting latch on devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 Setting latch on labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 Clearing latch range data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

C O

N TE

N TS

Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 29.2 Latch with Battery-less Option Cassette. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480

Usage procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

CHAPTER 30 DEVICE/LABEL INITIAL VALUE SETTINGS 483 30.1 Setting Initial Device/Label Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484

Setting initial device values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 Setting initial label values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

30.2 Applicable Devices/Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486 30.3 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

CHAPTER 31 CONSTANTS 487 31.1 Decimal Constant (K) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 31.2 Hexadecimal Constant (H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 31.3 Real Constant (E). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

Setting range for real numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 Processing when operation is in progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

31.4 Character String Constant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 31.5 Notation of Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489

PART 8 TROUBLESHOOTING

CHAPTER 32 TROUBLESHOOTING PROCEDURE 492 32.1 Troubleshooting with LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

LED status of the CPU module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 32.2 Troubleshooting Using the Engineering Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

System monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Module diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Event history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

CHAPTER 33 TROUBLESHOOTING BY SYMPTOM 496 33.1 When the POWER LED of the Power Supply Module Turns Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 33.2 When the READY LED of the CPU Module Turns Off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 33.3 When the Specific Extension Base Unit Cannot Be Recognized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 33.4 When the Specific Q Series Extension Base Unit Cannot Be Recognized . . . . . . . . . . . . . . . . . . . . . . . . 497 33.5 When Data Cannot Be Written to the Programmable Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 33.6 When Data Cannot Be Read from the Programmable Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 33.7 When the Operating Status of the CPU Module Cannot Be Changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 33.8 When the Ethernet Function Cannot Be Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 33.9 When the CC-Link IE Field Network Basic Function Cannot Be Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 33.10 When the CPU Module Database Access Function Cannot Be Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

When the data source name cannot be set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 When the connection test fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 When the ODBC server of the CPU module cannot be connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 When the connection is disconnected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

19

20

CHAPTER 34 ERROR CODES 500 34.1 Error Code System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 34.2 Operation When an Error Occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 34.3 How to Clear Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 34.4 List of Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502

Codes of errors detected by the self-diagnostic function (1000H to 3FFFH) . . . . . . . . . . . . . . . . . . . . . . . . . . 502 Codes of errors detected by other than the self-diagnostic function (4000H to 4FFFH) . . . . . . . . . . . . . . . . . . 537 Codes of errors detected by other than the self-diagnostic function (C000H to CFFFH) . . . . . . . . . . . . . . . . . 560

CHAPTER 35 EVENT LIST 561 35.1 How to Read the Event List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 35.2 Event List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

APPENDICES 571 Appendix 1 External Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 Appendix 2 Compliance with EMC and Low Voltage Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576 Appendix 3 Functional Availability By CPU Module Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577 Appendix 4 List of Special Relay Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580 System information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582 SFC information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 System clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585 Fixed scan function information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588 Drive information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589 Instruction related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591 Latch area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594 Data logging function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595 CPU module data backup/restoration function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597 iQ Sensor Solution data backup/restoration function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597 File transfer function (FTP client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598 Global label assignment information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598 Memory dump function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598 Event history function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599 CPU module database access function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599 Ethernet function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600 CC-Link IE Field Network Basic function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601

Appendix 5 List of Special Register Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602 Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603 System information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610 SFC information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614 System clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614 Fixed scan function information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615 Drive information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617 Instruction related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620 Firmware update function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622 Latch area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624 Data logging function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626 CPU module data backup/restoration function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628 Data backup/restoration function of iQ Sensor Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628 Interrupt pointer mask pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632

C O

N TE

N TS

Event history function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632 Memory dump function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633 Real-time monitor function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633 Debug function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633 CPU module database access function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634 Ethernet function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635 CC-Link IE Field Network Basic function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638 System monitoring information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639

Appendix 6 Buffer Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642 List of buffer memory addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642 Details on buffer memory addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643

Appendix 7 Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647 Instruction execution time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647 Program execution time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647 END processing time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649 Data logging function processing time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 Memory dump function processing time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670 Real-time monitor function processing time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670 Database function processing time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671 SFC program processing time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673 SFC program switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674 Processing time until the file operation is completed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675

Appendix 8 Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677 System parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677 CPU Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678 Module parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679 Memory card parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679

Appendix 9 Target List and Operation Details of the Device/Label Access Service Processing Setting . . . . . 680 Target list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680 Operation details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682

Appendix 10Program Restoration Information Write Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686 Checking the program restoration information write status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688

Appendix 11List of Available SQL Commands for CPU Module Database Access Function . . . . . . . . . . . . . . . 689 Data definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689 Data operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691 Clause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693 Aggregate function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695 Arithmetic function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696

Appendix 12Added and Enhanced Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700

INDEX 706

REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .709 CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .710 WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711 TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .712 COPYRIGHTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .712

21

22

RELEVANT MANUALS

This manual does not include detailed information on the following: General specifications Applicable combinations of CPU modules and the other modules, and the number of mountable modules Installation For details, refer to the following. MELSEC iQ-R Module Configuration Manual This manual does not include information on the module function blocks. For details, refer to the Function Block Reference for the module used.

e-Manual refers to the Mitsubishi Electric FA electronic book manuals that can be browsed using a dedicated tool. e-Manual has the following features: Required information can be cross-searched in multiple manuals. Other manuals can be accessed from the links in the manual. The hardware specifications of each part can be found from the product figures. Pages that users often browse can be bookmarked. Sample programs can be copied to an engineering tool.

Manual name [manual number] Description Available form MELSEC iQ-R Programmable Controller CPU Module User's Manual [SH-082488ENG] (this manual)

Procedures before operation, specifications, devices, memory, functions, parameters and troubleshooting of the programmable controller CPU module

Print book

e-Manual PDF

MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup) [SH-081256ENG]

Specifications, procedures before operation, system configuration, wiring, and communication examples of Ethernet, CC-Link IE Controller Network, and CC-Link IE Field Network

Print book

e-Manual PDF

MELSEC iQ-R Ethernet User's Manual (Application) [SH-081257ENG]

Functions, parameter settings, programming, troubleshooting, I/O signals, and buffer memory of Ethernet

Print book

e-Manual PDF

MELSEC iQ-R CPU Module Function Block Reference [BCN-P5999-0374]

Specifications of the MELSEC iQ-R series CPU module FBs e-Manual PDF

MELSEC iQ-R Ethernet, CC-Link IE, and MELSECNET/H Function Block Reference [BCN-P5999-0381]

Specifications of the following MELSEC iQ-R series module FBs: Ethernet-equipped module FBs, CC-Link IE TSN module FBs, CC-Link IE Controller Network module FBs, CC-Link IE Field Network module FBs, and MELSECNET/H network module FBs

e-Manual PDF

MELSEC iQ-R Programming Manual (Program Design) [SH-081265ENG]

Program specifications (ladder, ST, FBD/LD, and SFC programs) e-Manual PDF

MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks) [SH-081266ENG]

Instructions for the CPU module and standard functions/function blocks

e-Manual PDF

MELSEC iQ-R Programming Manual (Module Dedicated Instructions) [SH-081976ENG]

Dedicated instructions for the intelligent function modules e-Manual PDF

GX Works3 Operating Manual [SH-081215ENG]

System configuration, parameter settings, and online operations of GX Works3

e-Manual PDF

CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series) [SH-082478ENG]

System configuration and operation/setting procedures when using CPU Module Logging Configuration Tool

e-Manual PDF

TERMS Unless otherwise specified, this manual uses the following terms.

Term Description Buffer memory Memory in an intelligent function module for storing data such as setting values and monitored values. When

integrated into the CPU module, this memory refers to a memory for storing data such as setting values and monitored values of the Ethernet function, and data used for data communication of the multiple CPU system function.

Control CPU A CPU module that controls connected I/O modules and intelligent function modules. The multiple CPU system allows the user to assign this control to any CPU module on a module-by-module basis.

CPU Module Logging Configuration Tool Software to configure data logging settings and to manage collected data

Dedicated instruction An instruction that simplifies programming for using functions of intelligent function modules

Device A memory of a CPU module to store data. Devices such as X, Y, M, D, and others are provided depending on the intended use.

Engineering tool A tool used for setting up programmable controllers, programming, debugging, and maintenance.

FB instance A function block that is inserted to a sequence program

Global label A label that is valid for all the program data when multiple program data are created in the project. There are two types of global label: a module specific label (module label), which is generated automatically by GX Works3, and an optional label, which can be created for any specified device.

GX LogViewer Software to display data collected by data logging

Intelligent function module A module that has functions other than input and output, such as an A/D converter module and D/A converter module

Label A variable consisting of a specified string used in I/O data or internal processing

Module label A label that represents one of memory areas (I/O signals and buffer memory areas) specific to each module in a given character string. For the module used, GX Works3 automatically generates this label, which can be used as a global label.

POU A unit that configures a program. Units are categorized and provided in accordance with functions. A program that is composed of POUs (program organization units) allows the lower-layer processing, when the program is multi-layered, to be divided into several units by processing and function, enabling the creation of programs based on each unit.

Program block A group of POUs that configure a program

Signal flow The execution status that the last time an operation of a program or an FB is executed in each step.

23

24

GENERIC TERMS AND ABBREVIATIONS Unless otherwise specified, this manual uses the following generic terms and abbreviations.

Generic term and abbreviation Description Base unit A main base unit, an extension base unit, an RQ extension base unit

CC-Link IE Controller Network-equipped module

An RJ71GP21-SX CC-Link IE Controller Network module, an RJ71GP21S-SX CC-Link IE Controller Network module, and the following modules when the CC-Link IE Controller Network function is used: RJ71EN71 RnENCPU

CC-Link IE Field Network-equipped master/local module

An RJ71GF11-T2 CC-Link IE Field Network master/local module and the following modules when the CC-Link IE Field Network function is used: RJ71EN71 RnENCPU

CC-Link IE TSN master/local module RJ71GN11-T2, RJ71GN11-EIP (CC-Link IE TSN part)

CPU module R00CPU, R01CPU, R02CPU, R04CPU, R04ENCPU, R08CPU, R08ENCPU, R16CPU, R16ENCPU, R32CPU, R32ENCPU, R120CPU, R120ENCPU

Device supporting iQSS A device which supports iQ Sensor Solution. For iQ Sensor Solution, refer to the following. iQ Sensor Solution Reference Manual

Ethernet interface module with built-in CC- Link IE

RJ71EN71

Ethernet-equipped module The following modules when the Ethernet function is used: RJ71EN71 CPU module

I/O module An input module, an output module, an I/O combined module, and an interrupt module

Motion module RD78G4, RD78G8, RD78G16, RD78G32, RD78G64, RD78GHV, RD78GHW

Network module Includes the following: Ethernet interface module CC-Link IE TSN master/local module CC-Link IE Controller Network module CC-Link IE Field Network master/local module MELSECNET/H network module MELSECNET/10 network module RnENCPU (network part)

Power supply module A MELSEC iQ-R series power supply module

Programmable controller CPU R00CPU, R01CPU, R02CPU, R04CPU, R04ENCPU, R08CPU, R08ENCPU, R16CPU, R16ENCPU, R32CPU, R32ENCPU, R120CPU, R120ENCPU

RAS Reliability, Availability, Serviceability This term refers to the overall usability of automated equipment.

Remote head module An RJ72GF15-T2 CC-Link IE Field Network remote head module

RJ71GN11-EIP (CC-Link IE TSN part) An RJ71GN11-EIP when it performs communications on CC-Link IE TSN

RJ71GN11-EIP (EtherNet/IP part) An RJ71GN11-EIP when it performs communications on EtherNet/IP

RnCPU R00CPU, R01CPU, R02CPU, R04CPU, R08CPU, R16CPU, R32CPU, R120CPU

RnENCPU R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, R120ENCPU

RnENCPU (CPU part) A module on the left-hand side of the RnENCPU ( MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup))

RnENCPU (network part) A module on the right-hand side of the RnENCPU ( MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup))

Station sub ID number An ID number of a sensor connected to a CC-Link-compatible communication module

Windows 7 or later Windows7, Windows8, Windows8.1, Windows10

PA R

T 1

PART 1 PART NAMES

This part consists of the following chapters.

1 CPU Module

2 Extended SRAM Cassette and Battery-less Option Cassette

25

26

1 CPU Module This section describes the part names of the CPU module.

1.1 R00CPU

(9)

(2)(1) (3) (4) (5)

(6) (7)

(8)

(12)

(11)

(14)

(15) (13)

(10)

1 CPU Module 1.1 R00CPU

1

*1 When a cable is connected to the USB connector at all times, clamp the cable to prevent a poor connection, moving, and disconnection by unintentional pulling.

No. Name Description (1) READY LED Indicates the operating status of the CPU module and the error level. ( Page 493 LED status of the CPU

module) READY LEDERROR LED status Onoff: Normal operation Onon: Minor error Onflashing: Moderate error Flashingon: Minor error Flashing (every 2s)off: Initial processing Offon/flashing: Major error

(2) ERROR LED

(3) P RUN LED Indicates the operating status of the program. On: Being executed (RUN state) Flashing: Being suspended (PAUSE state) Off: Stopped (STOP state) or stop error

(4) USER LED Indicates the status of the annunciator (F). ( Page 417 Annunciator (F)) On: Annunciator (F) ON Off: Normal operation

(5) FUNC LED Turns on or flashes when the following functions are used: LED setting External input/output forced on/off function Program restoration information write Device test with execution condition

For the LED status, refer to the description of each function. Page 172 LED display setting

(6) SPEED LED Refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)(7) SD/RD LED

(8) RUN/STOP/RESET switch A switch for controlling the operating status of the CPU module. ( Page 55 Executing the Program) RUN: Executes the program. STOP: Stops the program. RESET: Resets the CPU module. (Keep the switch in the RESET position for approximately one second.) Operate the RUN/STOP/RESET switch with your fingers. To prevent the switch from being damaged, do not use any tool such as a screwdriver.

(9) USB port*1 A connector for a USB-compatible peripheral (connector type: miniB)

(10) Ethernet port Refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

(11) Battery compartment A compartment for storing the body of the battery (FX3U-32BL) when the battery is connected.

(12) Battery connector A connector for connecting to the battery (FX3U-32BL)

(13) LED cover A cover for the LEDs, USB port, and battery. Open this cover and connect/disconnect a USB-compatible peripheral or the battery. Otherwise, keep the cover closed to prevent entry of foreign matter such as dust.

(14) Switch cover A cover for the RUN/STOP/RESET switch. Open this cover and set the RUN/STOP/RESET switch. Otherwise, keep the cover closed to prevent entry of foreign matter such as dust.

(15) Production information marking Shows the production information (16 digits) of the module.

1 CPU Module 1.1 R00CPU 27

28

1.2 R01CPU, R02CPU The R01CPU is used as an example.

(13)

(2)(1) (3) (4)

(5) (6)

(7)

(8) (9)

(10)

(16)

(15)

(18)

(19) (17)

(14)

(11)

(12)

1 CPU Module 1.2 R01CPU, R02CPU

1

*1 When a cable is connected to the USB connector at all times, clamp the cable to prevent a poor connection, moving, and disconnection by unintentional pulling.

No. Name Description (1) READY LED Indicates the operating status of the CPU module and the error level. ( Page 493 LED status of the CPU

module) READY LEDERROR LED status Onoff: Normal operation Onon: Minor error Onflashing: Moderate error Flashingon: Minor error Flashing (every 2s)off: Initial processing Offon/flashing: Major error

(2) ERROR LED

(3) P RUN LED Indicates the operating status of the program. On: Being executed (RUN state) Flashing: Being suspended (PAUSE state) Off: Stopped (STOP state) or stop error

(4) USER LED Indicates the status of the annunciator (F). ( Page 417 Annunciator (F)) On: Annunciator (F) ON Off: Normal operation

(5) C RDY LED Indicates the availability of the SD memory card. On: Available Flashing: Ready Off: Not available or not inserted

(6) C ACS LED Indicates the access status of the SD memory card. On: Being accessed Off: Not accessed

(7) FUNC LED Turns on or flashes when the following functions are used: LED setting External input/output forced on/off function Program restoration information write Device test with execution condition

For the LED status, refer to the description of each function. Page 172 LED display setting

(8) SPEED LED Refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)(9) SD/RD LED

(10) RUN/STOP/RESET switch A switch for controlling the operating status of the CPU module. ( Page 55 Executing the Program) RUN: Executes the program. STOP: Stops the program. RESET: Resets the CPU module. (Keep the switch in the RESET position for approximately one second.) Operate the RUN/STOP/RESET switch with your fingers. To prevent the switch from being damaged, do not use any tool such as a screwdriver.

(11) SD CARD OFF button A switch for disabling access to the SD memory card to remove it from the CPU module ( Page 42 Inserting and Removing an SD Memory Card)

(12) SD memory card slot A slot where an SD memory card is inserted

(13) USB port*1 A connector for a USB-compatible peripheral (connector type: miniB)

(14) Ethernet port Refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

(15) Battery compartment A compartment for storing the body of the battery (FX3U-32BL) when the battery is connected.

(16) Battery connector A connector for connecting to the battery (FX3U-32BL)

(17) LED cover A cover for the LEDs, USB port, and battery. Open this cover and connect/disconnect a USB-compatible peripheral or the battery. Otherwise, keep the cover closed to prevent entry of foreign matter such as dust.

(18) Switch cover A cover for the RUN/STOP/RESET switch and SD memory card slot. Open this cover and set the RUN/STOP/ RESET switch or insert or remove an SD memory card. Otherwise, keep the cover closed to prevent entry of foreign matter such as dust.

(19) Production information marking Shows the production information (16 digits) of the module.

1 CPU Module 1.2 R01CPU, R02CPU 29

30

1.3 RnCPU (except for R00CPU, R01CPU, and R02CPU)

The R04CPU is used as an example.

(1)

(9)

(2) (3) (4) (5) (6) (7) (8)

(12)

(11)

(14)

(15)

(17)

(13)

(21) (10)

(18)

(19)

(20)

(16)

1 CPU Module 1.3 RnCPU (except for R00CPU, R01CPU, and R02CPU)

1

*1 When a cable is connected to the USB connector at all times, clamp the cable to prevent a poor connection, moving, and disconnection by unintentional pulling.

No. Name Description (1) READY LED Indicates the operating status of the CPU module and the error level. ( Page 493 LED status of the CPU

module) READY LEDERROR LED status Onoff: Normal operation Onon: Minor error Onflashing: Moderate error Flashing (every 2s)off: Initial processing Offon/flashing: Major error

(2) ERROR LED

(3) PROGRAM RUN LED Indicates the operating status of the program. On: Being executed (RUN state) Flashing: Being suspended (PAUSE state) Off: Stopped (STOP state) or stop error

(4) USER LED Indicates the status of the annunciator (F). ( Page 417 Annunciator (F)) On: Annunciator (F) ON Off: Normal operation

(5) BATTERY LED Indicates the battery status. Flashing: Battery low Off: Normal operation

(6) CARD READY LED Indicates the availability of the SD memory card. On: Available Flashing: Ready Off: Not available or not inserted

(7) CARD ACCESS LED Indicates the access status of the SD memory card. On: Being accessed Off: Not accessed

(8) FUNCTION LED Turns on or flashes when the following functions are used: LED setting External input/output forced on/off function Program restoration information write Device test with execution condition

For the LED status, refer to the description of each function. Page 172 LED display setting

(9) SPEED LED Refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)(10) SD/RD LED

(11) RUN/STOP/RESET switch A switch for controlling the operating status of the CPU module. ( Page 55 Executing the Program) RUN: Executes the program. STOP: Stops the program. RESET: Resets the CPU module. (Keep the switch in the RESET position for approximately one second.) Operate the RUN/STOP/RESET switch with your fingers. To prevent the switch from being damaged, do not use any tool such as a screwdriver.

(12) SD CARD OFF button A switch for disabling access to the SD memory card to remove it from the CPU module ( Page 42 Inserting and Removing an SD Memory Card)

(13) SD memory card slot A slot where an SD memory card is inserted

(14) USB port*1 A connector for a USB-compatible peripheral (connector type: miniB)

(15) Ethernet port Refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

(16) Battery A backup battery to hold clock data and to use the backup power function for the device/label memory

(17) Battery connector pin A pin for connecting a lead wire of the battery (To save the battery, the lead wire is disconnected from the connector before shipment.)

(18) Cassette cover A cover for the connector where an extended SRAM cassette or a battery-less option cassette is inserted ( Page 35 Extended SRAM Cassette and Battery-less Option Cassette, Page 41 Inserting or Removing an Extended SRAM Cassette)

(19) LED cover A cover for the LED indicators, SD memory card slot, and switches. Open this cover and insert or remove an SD memory card or set the RUN/STOP/RESET switch. Otherwise, keep the cover closed to prevent entry of foreign matter such as dust.

(20) USB cover A cover for the USB port. Open this cover and connect a USB-compatible peripheral. Otherwise, keep the cover closed to prevent entry of foreign matter such as dust.

(21) Production information marking Shows the production information (16 digits) of the module.

1 CPU Module 1.3 RnCPU (except for R00CPU, R01CPU, and R02CPU) 31

32

1.4 RnENCPU The R04ENCPU is used as an example.

(22)

(1)

(9)

(2) (3) (4) (5) (6) (7) (8)

(12)

(11)

(14)

(15)

(17)

(13)

(21)

(10)

(18)

(19)

(20)

(16)

1 CPU Module 1.4 RnENCPU

1

*1 When a cable is connected to the USB connector at all times, clamp the cable to prevent a poor connection, moving, and disconnection by unintentional pulling.

No. Name Description (1) READY LED Indicates the operating status of the CPU module and the error level. ( Page 493 LED status of the CPU

module) READY LEDERROR LED status Onoff: Normal operation Onon: Minor error Onflashing: Moderate error Flashingoff: Initial processing Offon/flashing: Major error

(2) ERROR LED

(3) PROGRAM RUN LED Indicates the operating status of the program. On: Being executed (RUN state) Flashing: Being suspended (PAUSE state) Off: Stopped (STOP state) or stop error

(4) USER LED Indicates the status of the annunciator (F). ( Page 417 Annunciator (F)) On: Annunciator (F) ON Off: Normal operation

(5) BATTERY LED Indicates the battery status. Flashing: Battery low Off: Normal operation

(6) CARD READY LED Indicates the availability of the SD memory card. On: Available Flashing: Ready Off: Not available or not inserted

(7) CARD ACCESS LED Indicates the access status of the SD memory card. On: Being accessed Off: Not accessed

(8) FUNCTION LED Turns on or flashes when the following functions are used: LED setting External input/output forced on/off function Program restoration information write Device test with execution condition

For the LED status, refer to the description of each function. Page 172 LED display setting

(9) SPEED LED Refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)(10) SD/RD LED

(11) RUN/STOP/RESET switch A switch for controlling the operating status of the CPU module. ( Page 55 Executing the Program) RUN: Executes the program. STOP: Stops the program. RESET: Resets the CPU module. (Keep the switch in the RESET position for approximately one second.) Operate the RUN/STOP/RESET switch with your fingers. To prevent the switch from being damaged, do not use any tool such as a screwdriver.

(12) SD CARD OFF button A switch for disabling access to the SD memory card to remove it from the CPU module ( Page 42 Inserting and Removing an SD Memory Card)

(13) SD memory card slot A slot where an SD memory card is inserted

(14) USB port*1 A connector for a USB-compatible peripheral (connector type: miniB)

(15) Ethernet port (CPU P1) Refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

(16) Battery A backup battery to hold clock data and to use the backup power function for the device/label memory

(17) Battery connector pin A pin for connecting a lead wire of the battery (To save the battery, the lead wire is disconnected from the connector before shipment.)

(18) Cassette cover A cover for the connector where an extended SRAM cassette or a battery-less option cassette is inserted ( Page 35 Extended SRAM Cassette and Battery-less Option Cassette, Page 41 Inserting or Removing an Extended SRAM Cassette)

(19) LED cover A cover for the LED indicators, SD memory card slot, and switches. Open this cover and insert or remove an SD memory card or set the RUN/STOP/RESET switch. Otherwise, keep the cover closed to prevent entry of foreign matter such as dust.

(20) USB cover A cover for the USB port. Open this cover and connect a USB-compatible peripheral. Otherwise, keep the cover closed to prevent entry of foreign matter such as dust.

(21) Production information marking Shows the production information (16 digits) of the module.

(22) Network part Refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

1 CPU Module 1.4 RnENCPU 33

34

MEMO

1 CPU Module 1.4 RnENCPU

2

2 Extended SRAM Cassette and Battery-less Option Cassette

This section describes the part names of the extended SRAM cassette and the battery-less option cassette.

No. Name Description (1) Tab for cassette insertion/removal A part which is held when an extended SRAM cassette or a battery-less option cassette is inserted or removed

( Page 41 Inserting or Removing an Extended SRAM Cassette)

(1)

2 Extended SRAM Cassette and Battery-less Option Cassette 35

36

MEMO

2 Extended SRAM Cassette and Battery-less Option Cassette

PA R

T 2

PART 2 PROCEDURES BEFORE OPERATION

This part consists of the following chapter.

3 START-UP PROCEDURE

37

38

3 START-UP PROCEDURE This chapter describes the procedures before operation.

3.1 Overview This section describes an outline of the procedure before operation for each CPU module.

1. Installing a Battery Install a battery to the CPU module. ( Page 40 Installing a Battery)

R00CPU, R01CPU, and R02CPU are the CPU modules that do not need a battery for holding data. Use the battery (FX3U-32BL) to save clock data in the event of a long-term (10 days or more) power failure. ( Page 40 FX3U-32BL)

2. Inserting a cassette (an extended SRAM cassette or a battery-less option cassette) or an SD memory card Insert a cassette (an extended SRAM cassette or a battery-less option cassette) or an SD memory card into the CPU module as needed. ( Page 41 Inserting or Removing an Extended SRAM Cassette, Page 42 Inserting and Removing an SD Memory Card)

When inserting a battery-less option cassette, refer to "Latch with Battery-less Option Cassette". ( Page 480 Latch with Battery-less Option Cassette)

3. Mounting modules and connecting cables Mount modules on the base unit, and connect cables. ( MELSEC iQ-R Module Configuration Manual)

4. Powering on the system Check the following before powering on the system. A cable is correctly connected to the power supply. Power supply voltage is within the specified range. The CPU module is in the STOP state. A personal computer on which an engineering tool has been installed is connected to the CPU module. ( Page 45

Connecting a Personal Computer)

5. Powering on the personal computer Power on the personal computer on which the engineering tool has been installed (the personal computer connected to the CPU module).

6. Starting up the engineering tool Start up the engineering tool that has been installed on the personal computer connected to the CPU module.

3 START-UP PROCEDURE 3.1 Overview

3

7. Initializing the CPU module Initialize the CPU module using the engineering tool. ( Page 46 Initializing the CPU Module)

8. Setting parameters The following table shows which parameters are required when changing the number of slots/the number of occupied points of a module, using an SD memory card, or using specific functions.

When the RnENCPU is used, set network parameters to the network part as well. ( User's Manual (Application) for the network used) System parameters are automatically set by loading an actual system configuration to the Module Configuration window of the engineering tool.

9. Programming Create a program using the engineering tool. ( Page 49 Programming)

10.Writing data to the programmable controller Write the parameters set and the program created by using the engineering tool to the CPU module. ( Page 53 Writing Data to the Programmable Controller)

11. Resetting the CPU module Restart the system in either of the following ways. Power off and on the system. Reset the CPU module. ( Page 54 Resetting the CPU Module)

12.Checking for errors Check the status of the READY LED and ERROR LED of the CPU module. If an error is detected, identify the error using the engineering tool, and eliminate the error cause. ( Page 492 TROUBLESHOOTING PROCEDURE)

13. Executing the program Run the CPU module, and check that the PROGRAM RUN LED (P RUN LED) turns on. ( Page 55 Executing the Program)

14.Monitoring the program Check that the program operates normally using the engineering tool. ( Page 56 Monitoring the Program)

When Required parameter Reference Changing the number of slots or the number of occupied points of a module

System parameters CPU parameters

Page 46 Setting Parameters

Using an SD memory card Memory card parameters Page 191 BOOT OPERATION Page 468 Label Access Setting from External Device

Using the Ethernet function of the CPU module Module parameters Some intelligent function modules require multiple module parameters and module extension parameters.

MELSEC iQ-R Ethernet/CC- Link IE User's Manual (Startup)

Using the CC-Link IE Field Network Basic function of the CPU module

CC-Link IE Field Network Basic Reference Manual

Using an intelligent function module User's manual for the module used

3 START-UP PROCEDURE 3.1 Overview 39

40

3.2 Installing a Battery Install a battery to the CPU module.

Installation procedure

Q6BAT The connector plug of the Q6BAT is disconnected from the jack of the CPU module before shipment. To use the battery, connect the connector plug of the Q6BAT and the jack of the CPU module by following the procedure below.

Precautions When using the CPU module with the battery removed, check that the jack (3) of the CPU module is inserted in the socket

on the battery cover located on the bottom of the CPU module. Do not drop or apply strong shock to the module and the battery.

FX3U-32BL To use the battery in the R00CPU, R01CPU, or R02CPU, connect the battery, following the procedure below.

Battery error detection setting in the engineering tool The following setting is required to use the battery in the R00CPU, R01CPU, or R02CPU.

[CPU Parameter] [RAS Setting] [Error Detection Setting] [Battery Error] Set the parameter to "Detect". (The default setting is "Not Detected".)

1. Open the battery cover located on the bottom of the CPU module.

2. Check that the Q6BAT (1) is correctly installed.

3. Check the direction and securely insert the connector plug (2) of the Q6BAT to the jack (3) of the CPU module.

4. Close the battery cover.

1. Open the LED cover on the front side of the CPU module.

2. Connect the lead connectors to the battery connector (1) in the right orientation. Insert the battery in the battery compartment (2).

3. Close the LED cover.

(2)

(3)

(1)

(2) (1)

3 START-UP PROCEDURE 3.2 Installing a Battery

3

3.3 Inserting or Removing an Extended SRAM Cassette

Insert an extended SRAM cassette to the CPU module as needed.

Insertion procedure Insert an extended SRAM cassette while the programmable controller is powered off.

Precautions The availability of the extended SRAM cassette differs depending on the CPU module used. For the availability, refer to the

performance specifications of the extended SRAM cassette. ( Page 67 Extended SRAM Cassette) When the extended SRAM cassette is inserted or removed, all the data such as devices and the file register stored in the

device/label memory are erased. Back up the data in the programmable controller before replacing the cassette. If the capacity of the extended SRAM cassette differs before and after the replacement, the ERROR LED of the CPU

module may flash. But, it is not an error. Change the capacity setting in the CPU parameters. (Refer to step 5 above.)

The extended SRAM cassette for the Universal model QCPU (Q4MCA-MBS) cannot be used.

Removal procedure Remove the extended SRAM cassette while the programmable controller is powered off.

1. Read the data on the device/label memory from the CPU module, and save it in advance using the engineering tool. (When the extended SRAM cassette is removed, all of the data on the device/label memory are erased.)

2. Power off the programmable controller.

3. Remove the CPU module from the base unit, and open the cassette cover located on the side of the CPU module.

4. Hold the top and bottom of the tab of the extended SRAM cassette, and pull the cassette straight out of the connector.

5. Close the cover, and mount the CPU module back on the base unit.

6. Power on the programmable controller.

7. Set the "Extended SRAM Cassette Setting" in "CPU Parameter" to "Not Mounted".

1. Open the cassette cover (1) located on the side of the CPU module.

2. Hold the top and bottom of the tab (2) of an extended SRAM cassette (with the notched edge facing to the right), and insert the cassette straight into the connector. After inserting the cassette, check that it is inserted completely.

3. Close the cover, and mount the CPU module on the base unit.

4. Power on the programmable controller.

5. Set the capacity of the inserted cassette to "Extended SRAM Cassette Setting" in "CPU Parameter" using the engineering tool.

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Setting] [Cassette Setting] [Extended SRAM Cassette Setting]

6. Using the engineering tool, check that SM626 (Extended SRAM cassette insertion flag) is on.

(1)

(2)

3 START-UP PROCEDURE 3.3 Inserting or Removing an Extended SRAM Cassette 41

42

3.4 Inserting and Removing an SD Memory Card Insert an SD memory card to the CPU module as needed.

Insertion procedure Check the direction and insert an SD memory card, following the procedure below.

For the R01CPU and R02CPU, insert an SD memory card as shown below.

1. Insert an SD memory card (1) into the card slot until it clicks with the notched edge in the direction as illustrated. After inserting the cassette, check that it is inserted completely. Poor contact may cause malfunction.

2. The CARD READY LED (C RDY LED) (2) starts flashing. When the card is ready to be used, the CARD READY LED (C RDY LED) stops flashing and turns on.

3. If the CARD READY LED (C RDY LED) does not turn on even after the card is inserted, check that SM606 (SD memory card forced disable instruction) and SM607 (SD memory card forced disable status flag) are off.

(2)

(1)

(2)

(1)

3 START-UP PROCEDURE 3.4 Inserting and Removing an SD Memory Card

3

Removal procedure

*1 SM606 (SD memory card forced disable instruction) can also disable access to an SD memory card. For details, refer to the following. Page 132 How to forcibly disable the SD memory card with a special relay

Precautions Do not drop or apply strong shock to the module and SD memory cards. Follow the procedure above when inserting or removing the SD memory card while the system is powered on. If not, the

data on the SD memory card may corrupt. If any function that accesses the SD memory card is being executed when the SD CARD OFF button is pressed to remove

the card, the CARD READY LED turns off after the processing of the function is completed. For this reason, the time required until the LED turns off differs depending on the function being executed.

If SM605 (Memory card remove/insert prohibit flag) is on, the CARD READY LED does not turn off even if the SD CARD OFF button is pressed. If not, turn on SM606 (SD memory card forced disable instruction) to forcibly disable access to the card.

For the R01CPU and R02CPU, remove an SD memory card as shown below.

1. Press the SD CARD OFF button (1) for one second or longer to disable access to the SD memory card.* 1

2. The CARD READY LED (C RDY LED) (2) flashes during the access stop processing, and turns off upon completion of the processing.

3. Push in and release the SD memory card (3), and then pull the card out of the slot.

(2)

(1)

(3)

(2)

(3)

(1)

3 START-UP PROCEDURE 3.4 Inserting and Removing an SD Memory Card 43

44

3.5 Creating a Project Activate the engineering tool and create a project.

[Project] [New]

Procedure Create a program, following the procedure below. The procedure is for the program described in ladder diagrams.

Module labels are the labels where the I/O signals and buffer memory areas of a module are predefined. Using module labels allows the user to create programs without considering module internal addresses.

Sample comments are the comments where system devices (special relay/special register) and buffer memory areas of a module are predefined. Using sample comments saves the time of inputting the comments.

1. Select "RCPU" in "Series", and the CPU module model to use in "Type". Then, select a programming language to use in the project in "Program". Select "Ladder", and click the [OK] button.

2. Click the [OK] button when the window for adding the module appears.

3 START-UP PROCEDURE 3.5 Creating a Project

3

3.6 Connecting a Personal Computer Connect a personal computer where an engineering tool has been installed to the CPU module.

Procedure Connect a personal computer directly to the CPU module, following the procedure below.

Install a USB driver to use a USB cable for the first time. ( GX Works3 Operating Manual)

1. Connect a personal computer to the CPU module using a USB cable or Ethernet cable.

2. Select [Online] [Current Connection Destination] on the menu bar of the engineering tool.

3. Click the [CPU Module Direct Coupled Setting] button on the "Specify Connection Destination Connection" window.

4. Select the connection method, and click the [Yes] button.

5. Click the [Connection Test] button, and check if the personal computer is connected to the CPU module.

3 START-UP PROCEDURE 3.6 Connecting a Personal Computer 45

46

3.7 Initializing the CPU Module Initialize the CPU module.

[Online] [CPU Memory Operation]

Procedure

3.8 Setting Parameters Set system parameters and parameters for each module.

When the engineering tool is connected to the actual system Set parameters by loading an actual system configuration to the Module Configuration window of the engineering tool.

[Navigation window] [Module Configuration]

Precautions The RQ extension base units, MELSEC-Q series extension base units, and modules mounted on those base units cannot be loaded. For those cannot be loaded, select the units and modules on the Element Selection window, and drag and drop them to the system configured on the Module Configuration window.

1. Select "Data Memory" on the "Memory Management" window, and click the [Initialization] button.

2. Select "File Storage Area", and click the [Initialization] button.

3. After the initialization processing completes, click the [Close] button.

1. Open the Module Configuration window, and select [Online] [Read Module Configuration from PLC] on the menu bar.

2. Click the [Yes] button when the window for adding module labels of the mounted modules appears.

3. The system parameters are automatically set, and the actual system configuration is displayed on the Module Configuration window.

4. Double-click each module (CPU module, I/O module, or intelligent function module) to display the corresponding module parameter editor.

5. Set parameters, and click the [Apply] button to close the window.

3 START-UP PROCEDURE 3.7 Initializing the CPU Module

3

When the engineering tool is not connected to the actual system Set parameters by configuring a system manually on the Module Configuration window of the engineering tool.

To use the RnENCPU, the modules can be found from different categories. Select each module from the following categories on the Element Selection window. RnENCPU (CPU part): "PLC CPU" RnENCPU (network part): "CPU Extension"

1. Select a base unit on the Element Selection window, and drag and drop it to the Module Configuration window.

2. Drag and drop modules to be used on the base unit placed.

3. Select [Edit] [Parameter] [Fix] on the menu bar.

4. Click the [Yes] button when the window for adding module labels of the configured modules appears.

5. Open the parameter editor of each module by double-clicking the module.

6. Set parameters, and click the [Apply] button to close the window.

3 START-UP PROCEDURE 3.8 Setting Parameters 47

48

Setting parameters from the Navigation window Set the following parameters from the Navigation window.

System parameters These parameters need to be set from the Navigation window in the following cases: to change the number of slots on the base unit or the number of occupied points of the module; for a multiple CPU system; and for module synchronization operations.

[Navigation window] [Parameter] [System Parameter]

Module parameters of the CPU module These parameters are required to execute the Ethernet function or CC-Link IE Field Network Basic function of the CPU module.

[Navigation window] [Parameter] [Module model name] [Module Parameter]

Memory card parameters These parameters are required to execute functions that access the SD memory card.

[Navigation window] [Parameter] [Module model name] [Memory Card Parameter]

Multiple module parameters and module extension parameters Some intelligent function modules require multiple module parameters and module extension parameters.

[Navigation window] [Parameter] [Module Information] [Intelligent function module] [Module Parameter] or [Module Extended Parameter]

System parameters can be set on the following windows. Select the window depending on their application purposes. Module Configuration window: Use this window when using the module specific data (such as number of

occupied points) as is. System Parameter window: Use this window when changing the number of slots or the number of occupied

points.

3 START-UP PROCEDURE 3.8 Setting Parameters

3

3.9 Programming Create a program. This section describes how to create a program using the following program example.

Program example

When Start1 turns on, Timer1 starts counting, and Lamp1 turns on. When the current value of Timer1 reaches 1000, Lamp1 turns off. When Stop1 turns on, Lamp1 turns off.

Registering labels Label is a variable whose name and data type can be declared by a user. Use of labels allows programming without being aware of devices and buffer memory addresses. For this reason, programs using labels can be used in other systems where the module configuration is different. Labels can be registered on the label editor.

[Navigation window] [Program] [Scan] [MAIN] [ProgPou] [Local Label]

Procedure Register the label "Start1" in the program example, following the procedure below.

Register other labels in the program example in the same way.

The class, initial value, and constant of labels can be set as needed by clicking the [Show Details] button on the label editor.

Labels can also be registered while programming without opening the label editor. ( Page 52 Inserting POUs by key input)

Devices can be assigned to global labels. Open the global label editor, and enter a device in the "Assign (Device/Label)" field.

1. Enter the name, "Start1", in the "Label Name" field (1).

2. Click the button (2) on the right of the "Data Type" field to open the "Data Type Selection" window.

3. Specify the data type. Select "Bit", and click the [OK] button.

(1) (2)

3 START-UP PROCEDURE 3.9 Programming 49

50

Inserting program elements Drag and drop required program elements to the ladder editor.

[Navigation window] [Program] [Scan] [MAIN] [ProgPou] [ProgramBody]

Procedure Insert a normally open contact of "Start1" in the program example, following the procedure below.

Insert other program elements in the program example in the same way.

Common instructions, such as contacts and coils, standard functions/function blocks, and user-defined function blocks/functions can be found in the [POU List] (1) in the Element Selection window. Narrow the list using the drop-down menu (2) for "Display Target", and select program elements.

Module labels and module function blocks can be found in the [Module] list (3). Programs are efficiently created only by dragging and dropping the module labels and module function blocks on the editor.

1. Select a program element from the Element Selection window, and drag and drop (1) it to the desired position on the ladder editor. In this example, drag and drop "LD[1]".

2. Double-click the inserted program element, and click the [Extd Dspl] button to open the ladder entry window.

3. Specify the operand. In this example, enter "Start" for "s" in the "Device/Label" field.

4. Select an item from the displayed list (3). In this example, select "Start1".

5. The normally open contact of "Start1" is inserted to the program.

(1)

(2) (3)

(2)

(1) (3)

3 START-UP PROCEDURE 3.9 Programming

3

Inserting function blocks Insert function blocks, following the procedure below.

Creating function blocks/functions User-defined function blocks/functions must be created before inserted to the program.

1. Select a function block from the Element Selection window, and drag and drop it to the desired position on the ladder editor.

2. The "FB Instance Name" window opens. Select the target label (global label or local label), and enter an instance name.

3. Select [Convert] [Convert] on the menu bar. The ladder is converted, and the rungs are connected to the input and output labels of the FB instance.

4. Add the input and output parts of the inserted function block to complete the program. For details on the input and output parts, refer to the following.

Function Block Reference for the module used

1. Right-click "FB/FUN" (1) on the Navigation window, and select "Add New Data" (2) to open the setting window.

2. To create a function block, set the data type to "Function Block" using the drop-down list. To create a function, set the data type to "Function". Then, click the [OK] button.

3. Program the operation of the function block or function in "ProgramBody".

(1) (2)

3 START-UP PROCEDURE 3.9 Programming 51

52

Inserting POUs by key input POUs can be inserted by key input.

Procedure Inserting a normally open contact of "Start1" in the program example, following the procedure below.

A new label can be registered during insertion. Enter the name of a new label on the ladder entry window, and click the [OK] button. Then, specify the registered destination, class, and data type of the label on the "Undefined Label Registration" window, and click the [OK] button.

1. Click the insertion position on the ladder editor, and press .

2. Enter the name, "Start", in the entry field (1). Select "Start1" from the displayed list (2).

3. The normally open contact of "Start1" is inserted to the program.

(1) (2)

3 START-UP PROCEDURE 3.9 Programming

3

3.10 Converting the Program Determine the input ladder blocks.

Procedure 1. Select [Convert] [Convert] on the menu bar.

2. When the conversion processing completes and the input ladder blocks are determined, the color of those ladder blocks changes from gray to white.

3.11 Saving the Project Save the created project.

[Project] [Save as]

3.12 Writing Data to the Programmable Controller Write the set parameters and the created program to the CPU module.

[Online] [Write to PLC]

Procedure

For the operation of the CPU module, the system parameter file, CPU parameter file, and program file must be written. For the operation of the I/O modules and intelligent function modules, the module parameter files and module extension parameter file must be written as well.

When a parameter setting is changed, reset the CPU module. ( Page 54 Resetting the CPU Module) Use of the [Select Favorites] button enables users to easily select frequently-used files, such as the system

parameter file, CPU parameter file, and program file. Register items as favorites on the window opened by selecting [Setting] [Register Favorites Selection] on the menu bar.

1. Select the system parameter file, CPU parameter file, module parameter file, and program file on the "Online Data Operation" window. If any function block is used, select the corresponding FB/FUN file as well.

2. Click the [Execute] button.

3. After the write processing completes, click the [Close] button.

3 START-UP PROCEDURE 3.10 Converting the Program 53

54

3.13 Resetting the CPU Module Reset the CPU module using the RUN/STOP/RESET switch located on the front of the CPU module.

Procedure

Operate the RUN/STOP/RESET switch with your fingers. Use of a tool such as a screwdriver may damage the switch.

For the R00CPU, R01CPU, and R02CPU, the switch and LED are located as shown below.

1. Set the RUN/STOP/RESET switch (1) to the RESET position for a second or longer.

2. Check that the ERROR LED (2) flashes for several times and turns off.

3. Set the switch back to the STOP position.

(2)

(1)

(2)

(1)

3 START-UP PROCEDURE 3.13 Resetting the CPU Module

3

3.14 Executing the Program Execute the program written to the programmable controller by using the RUN/STOP/RESET switch.

Procedure

For the R00CPU, R01CPU, and R02CPU, the switch and LED are located as shown below.

1. Set the RUN/STOP/RESET switch (1) to the RUN position.

2. Check that the PROGRAM RUN LED (P RUN) (2) turns on. (2)

(1)

(2)

(1)

3 START-UP PROCEDURE 3.14 Executing the Program 55

56

3.15 Monitoring the Program Monitor the program operation using the engineering tool.

Monitoring on the monitor status bar For the monitor status bar, refer to the following. GX Works3 Operating Manual

Monitoring on the ladder editor The on/off states of contacts and coils and the current values of word devices and labels can be monitored on the ladder editor.

1. Select [Online] [Monitor] [Start Monitoring] on the menu bar.

2. Monitor the on/off states of contacts and coils and the current values of word devices and labels.

On/off state display The on/off states are displayed on the editor as follows:

Changing the current value To change the current value, select the cell on the ladder editor, and press + double-click the cell or press + while the program is being monitored.

The program can also be monitored on the Device/Buffer Memory Batch window or the Watch window. ( GX Works3 Operating Manual)

(1) The on/off states of the contacts and coils are displayed.

(2) The current value of the word/double word type data is displayed.

(1)

(1)

(2)

ON:

OFF:

3 START-UP PROCEDURE 3.15 Monitoring the Program

PA R

T 3

PART 3 SYSTEM CONFIGURATION

This part consists of the following chapter.

4 SYSTEM CONFIGURATION

57

58

4 SYSTEM CONFIGURATION For system configurations using the MELSEC iQ-R series modules, applicable combinations of CPU modules and the other modules, the number of mountable modules, installation, and wiring, refer to the following. MELSEC iQ-R Module Configuration Manual

4 SYSTEM CONFIGURATION

4

MEMO

4 SYSTEM CONFIGURATION 59

60

MEMO

4 SYSTEM CONFIGURATION

PA R

T 4

PART 4 SPECIFICATIONS

This part consists of the following chapter.

5 PERFORMANCE SPECIFICATIONS

61

62

5 PERFORMANCE SPECIFICATIONS

5.1 CPU Module This section describes the specifications of the CPU module.

Hardware specifications Item R00 R01 R02 R04

R04EN R08 R08EN

R16 R16EN

R32 R32EN

R120 R120EN

Operation control method Stored program cyclic operation

I/O control mode Refresh mode (The direct access input/output is available by specifying the direct access input/output (DX, DY).)

Instruction processing time

LD instruction 31.3ns 3.92ns 0.98ns

MOV instruction 62.7ns 7.84ns 1.96ns

Instruction processing time (structured text)

IF 31.3ns 3.92ns 1.96ns

CASE 31.3ns 3.92ns 1.96ns

FOR 31.3ns 3.92ns 1.96ns

Memory capacity

Program capacity 10K steps (40K bytes)

15K steps (60K bytes)

20K steps (80K bytes)

40K steps (160K bytes)

80K steps (320K bytes)

160K steps (640K bytes)

320K steps (1280K bytes)

1200K steps (4800K bytes)

Program memory 40K bytes 60K bytes 80K bytes 160K bytes 320K bytes 640K bytes 1280K bytes 4800K bytes

SD memory card Differs depending on the SD memory card used. (SD/SDHC memory card: 32G bytes maximum)

Device/ label memory

Total 252K bytes 400K bytes 1188K bytes 1720K bytes 2316K bytes 3380K bytes

Device area*1

60K bytes 80K bytes

Label area*1

60K bytes 80K bytes 100K bytes 180K bytes 220K bytes

Latch label area*1

4K bytes 8K bytes

File storage area*1

128K bytes 256K bytes 1024K bytes 1536K bytes 2048K bytes 3072K bytes

Signal flow memory

Area for programs

1.25K bytes 1.87K bytes 2.5K bytes 5K bytes 10K bytes 20K bytes 40K bytes 150K bytes

Area for function blocks

256K bytes 256K bytes*2

Data memory 1.5M bytes 2M bytes 5M bytes 10M bytes 20M bytes 40M bytes

Function memory 20480K bytes/5120 bytes*11

CPU buffer memory 1072K bytes (536K words) (including the fixed scan communication area (24K words))

Refresh memory 2048K bytes*3

Number of storable files*10

Program memory (P: number of program files, FB: number of FB files)

P: 32, FB*7: 16 P: 64, FB*7: 32

P: 124, FB*7: 64

P: 252, FB*7: 128

Device/label memory (file storage area)

128*4 324 (with or without an extended SRAM cassette)*4

Data memory 256*5 512*5

Function memory 512*6

SD memory card NZ1MEM-2GBSD: 256*5

NZ1MEM-4GBSD, NZ1MEM-8GBSD, NZ1MEM-16GBSD: 32767*5

Number of storable folders*10

Data memory 256*5 512*5

Function memory 512*6

SD memory card NZ1MEM-2GBSD: 256*5

NZ1MEM-4GBSD, NZ1MEM-8GBSD, NZ1MEM-16GBSD: 32767*5

5 PERFORMANCE SPECIFICATIONS 5.1 CPU Module

5

*1 The capacity of device area, label area, latch label area, and file storage area can be changed in parameter. The capacity of the device/ label memory can be increased by inserting an extended SRAM cassette. ( Page 127 Device/label memory area setting)

*2 For the programmable controller CPU with the firmware version "27" or earlier, the memory capacity is 20K bytes. *3 This is the total capacity of the device area and module label area. *4 System files are included. *5 The number indicates the number of files and folders (including system files and system folders) can be created in the root directory on

the condition that the number of characters in the file or folder name is 13 or less. In a subdirectory, up to 32767 folders can be created. Note that the number of storable files and folders will decrease if many folders with a long name, more than 13 characters (including an extension), are created.

*6 The number indicates the number of files and folders (including system files and system folders) can be created in the root directory on the condition that the number of characters in the file or folder name is 13 or less. In a subdirectory, up to 2482 folders can be created.

*7 One FB file can store 64 function blocks. *8 These backup power times apply under the ambient temperature of 25 . *9 The internal current consumption increases by 0.15A maximum when a battery-less option cassette is inserted. *10 The following characters cannot be used for file or folder names: A space, "%*+,/:;<=>?[\]|'{}&~@^. *11 The capacity differs depending on the firmware version and the production information of the CPU module. ( Page 700 Added and

Enhanced Functions)

For the hardware specifications of the RnENCPU (network part), refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

USB port USB2.0 High Speed (miniB)1

Ethernet port Refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

Clock function

Display Year, month, date, hour, minute, second, and day of the week (automatic leap year adjustment)

Accuracy -2.43 to +3.52s (TYP. +0.55s)/d at 0 -3.08 to +3.53s (TYP. +0.23s)/d at 25 -13.03 to +1.91s (TYP. -5.56s)/d at 55

-1.00 to +1.00s/d at 0 to 55

Number of occupied I/O points RnENCPU (network part): 32

Backup power

Backup method Capacitor

Backup power time*8 10 days Three minutes

Data retained Clock data Device/label memory, clock data

Allowable momentary power failure time

The time differs depending on the power supply module used. ( MELSEC iQ-R Module Configuration Manual)

Internal current consumption (5VDC) 0.67A RnCPU: 0.67A*9

RnENCPU: 1.49A*9

External dimensions

Height 106mm (Base unit mounting side: 98mm)

Width 27.8mm RnCPU: 27.8mm RnENCPU: 56mm

Depth 110mm

Weight 0.20kg RnCPU: 0.20kg RnENCPU: 0.40kg

Item R00 R01 R02 R04 R04EN

R08 R08EN

R16 R16EN

R32 R32EN

R120 R120EN

5 PERFORMANCE SPECIFICATIONS 5.1 CPU Module 63

64

Programming specifications Item R00 R01 R02 R04

R04EN R08 R08EN

R16 R16EN

R32 R32EN

R120 R120EN

Programming language Ladder diagram (LD) Sequential function chart (SFC)*5

Structured text (ST) Function block diagram (FBD/LD)

Programming supporting function Function block (FB) Label programming (system/local/global)

Program operation

Execution type Initial execution type Scan execution type Fixed scan execution type Event execution type Standby type

Type of interrupt Interrupt using the internal timer (I28 to I31)

Interrupt by a module Inter-module synchronous interrupt

(I44) Multiple CPU synchronous interrupt

(I45)

Interrupt using the internal timer (I28 to I31) High-speed internal timer interrupt 1 (I49) High-speed internal timer interrupt 2 (I48) Interrupt by a module Inter-module synchronous interrupt (I44) Multiple CPU synchronous interrupt (I45)*6

Number of executable programs 32 64 124 252

Number of FB files 16 32 64 128

Tact performance

Constant scan 0.5 to 2000ms (The value can be set in increments of 0.1ms.)

0.2 to 2000ms (The value can be set in increments of 0.1ms.)

Fixed scan interrupt

Interrupt using the internal timer (I28 to I31)

0.5 to 1000ms (The value can be set in increments of 0.5ms.)

High-speed internal timer interrupt 1 (I49)

0.05 to 1000ms (The value can be set in increments of 0.05ms.)

High-speed internal timer interrupt 2 (I48)

0.05 to 1000ms (The value can be set in increments of 0.05ms.)

Inter-module synchronous interrupt (I44)

0.5 to 10.00ms (The value can be set in increments of 0.05ms.)

0.1 to 10.00ms (The value can be set in increments of 0.05ms.)

Multiple CPU synchronous interrupt (I45)*6

0.5 to 10.00ms (The value can be set in increments of 0.05ms.)

0.1 to 10.00ms (The value can be set in increments of 0.05ms.)

Timer performance

Low-speed timer 1 to 1000ms (Default: 100ms)

High-speed timer 0.01 to 100ms (Default: 10ms)

Long timer 0.001 to 1000ms (Default: 0.001ms)

Number of I/O points 4096 points

5 PERFORMANCE SPECIFICATIONS 5.1 CPU Module

5

Number of user device points (default)

Input (X) 8192 points (fixed) 12288 points (fixed)

Output (Y) 8192 points (fixed) 12288 points (fixed)

Internal relay (M) 8192 points (user-changeable)*1 12288 points (user-changeable)*1

Link relay (B) 8192 points (user-changeable)*1

Link special relay (SB) 2048 points (user-changeable)*1

Annunciator (F) 2048 points (user-changeable)*1

Edge relay (V) 2048 points (user-changeable)*1

Step relay (S)*4*5 0 points (user-changeable)*1

Timer device

Timer (T) 2048 points (user-changeable)*1 1024 points (user-changeable)*1

Long timer (LT)

0 points (user-changeable)*1 1024 points (user-changeable)*1

Retentive timer device

Retentive timer (ST)

0 points (user-changeable)*1

Long retentive timer (LST)

0 points (user-changeable)*1

Counter device

Counter (C) 1024 points (user-changeable)*1 512 points (user-changeable)*1

Long counter (LC)

0 points (user-changeable)*1 512 points (user-changeable)*1

Data register (D) 12288 points (user-changeable)*1 18432 points (user-changeable)*1

Link register (W) 8192 points (user-changeable)*1

Link special register (SW) 2048 points (user-changeable)*1

Latch relay (L) 8192 points (user-changeable)*1

Number of system device points

Special relay (SM) 4096 points (fixed)

Special register (SD) 4096 points (fixed)

Function input (FX) 16 points (fixed)

Function output (FY) 16 points (fixed)

Function register (FD) 5 points 4 words (fixed)

Number of file register points (default)

File register (R/ZR) 0 points (user-changeable)*1

Number of index register points (default)

Index register (Z) 20 points (user-changeable, up to 24 points)

Long index register (LZ) 2 points (user-changeable, up to 12 points)

Number of pointer points

Pointer (P) (global/local) (default)

8192 points (user-changeable, up to 16384 points) 16384 points (user- changeable, up to 32768 points)

Interrupt pointer (I) 1024 points (fixed)

Number of link direct device points

Link input (J\X) 160K points maximum*2*7

Link output (J\Y) 160K points maximum*2*7

Link relay (J\B) 640K points maximum*2*7

Link register (J\W) 2560K points maximum*2*7

Link special relay (J\SB)

5120 points maximum*2*7

Link special register (J\SW)

5120 points maximum*2*7

Number of module access device points

Intelligent function module device (U\G)

268435456 points maximum*2

Item R00 R01 R02 R04 R04EN

R08 R08EN

R16 R16EN

R32 R32EN

R120 R120EN

5 PERFORMANCE SPECIFICATIONS 5.1 CPU Module 65

66

*1 For the setting range, refer to the following. Page 414 Device Setting

*2 These are the maximum points that can be handled in the CPU module. The number of points actually used differs depending on the module used.

*3 The maximum point differs depending on the parameter setting (Multiple CPU Setting). *4 These devices are used in SFC programs. For details on SFC programs, refer to the following.

MELSEC iQ-R Programming Manual (Program Design) *5 If using the devices with the RnCPU, check the versions of the CPU module and engineering tool used. ( Page 700 Added and

Enhanced Functions) *6 The RnENCPU does not support the use of this interrupt. *7 The maximum number of points differs depending on the "Link Direct Device Setting" of the engineering tool. Before using the "Link

Direct Device Setting", check the version of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

For the programming specifications of the RnENCPU (network part), refer to the following. MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

Number of CPU buffer memory access device points

Buffer memory (U3E\G)

268435456 points maximum*2

Fixed scan communication area in the buffer memory (U3E\HG)

12288 points maximum*3

Number of refresh data register points (default)

Refresh data register (RD)

524288 points (1048576 points maximum)

Number of nesting points

Nesting (N) 15 points

Number of other device points

SFC block device (BL)*4*5 128 points 320 points

SFC transition device (TR)*4*5

0 points (Used only as device comments.)

Item R00 R01 R02 R04 R04EN

R08 R08EN

R16 R16EN

R32 R32EN

R120 R120EN

5 PERFORMANCE SPECIFICATIONS 5.1 CPU Module

5

5.2 Extended SRAM Cassette This section describes the performance specifications of the extended SRAM cassette.

*1 Check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

The R00CPU, R01CPU, and R02CPU do not support the use of these devices.

5.3 Battery-less Option Cassette This section describes the performance specifications of the battery-less option cassette.

*1 Check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

The R00CPU, R01CPU, and R02CPU do not support the use of these devices.

Item NZ2MC-1MBS NZ2MC-2MBS NZ2MC-4MBS NZ2MC-8MBS NZ2MC-16MBS*1

Capacity 1M bytes 2M bytes 4M bytes 8M bytes 16M bytes

Number of insertions and removals Limited to 50 times

External dimensions Height 49mm

Width 32mm

Depth 18.5mm

Weight 20g

Item NZ1BLC*1

Number of insertions and removals Limited to 50 times

Internal current consumption (5VDC) 0.15A

External dimensions Height 49mm

Width 32mm

Depth 18.5mm

Weight 20g

5 PERFORMANCE SPECIFICATIONS 5.2 Extended SRAM Cassette 67

68

MEMO

5 PERFORMANCE SPECIFICATIONS 5.3 Battery-less Option Cassette

PA R

T 5

PART 5 CPU MODULE OPERATION

This part consists of the following chapters.

6 RUNNING A PROGRAM

7 CPU MODULE OPERATION PROCESSING

8 MEMORY CONFIGURATION OF THE CPU MODULE

69

70

6 RUNNING A PROGRAM

6.1 Scan Configuration The following shows the scan configuration of the CPU module.

Initial processing (when powered on or switched to RUN) For the initial processing (when powered on or switched to RUN), the following processes are performed: : Performed, : Not performed

*1 Checking each parameter and program takes time depending on the parameter setting and the number of programs, and thus the CPU module may take time to respond to the peripheral.

When functions that require an SD memory card are enabled and the status of the SD memory card is as follows, the initial processing (when powered on or switched to RUN) takes time, and thus the CPU module may take time to respond to the peripheral. A large number of files is stored in the SD memory card. The SD memory card is close to the end of life or it has reached the end of life.

Item Initial processing Initial processing (when switched to RUN)

Booting from an SD memory card

Checking each parameter and program*1

Checking the consistency of parameters for the multiple CPU system configuration

Assigning the I/O number to the mounted module

Initializing and setting the information of each module

Initializing a device/label outside the latch range (Bit device: Off, Others: 0)

Setting the device/label initial value

CPU module internal operation

Structure of a scan

Initial processing (when powered on or switched to RUN)

I/O refresh

Program execution

END processing

6 RUNNING A PROGRAM 6.1 Scan Configuration

6

I/O refresh The module performs the following before starting program operation. ON/OFF data input from the input module/intelligent function module to the CPU module. ON/OFF data output from the CPU module to the output module/intelligent function module.

While constant scan is in progress, I/O refresh is performed after the waiting time for constant scan expires.

Program operation According to the program settings, the module executes from step 0 through the END/FEND instruction for each program. This program is referred to as a main routine program. A main routine program can be divided into subroutine programs. ( Page 98 Subroutine Program)

END processing The CPU module performs the following processing. Network module link refresh Link refresh of CC-Link IE Field Network Basic Intelligent function module refresh Instruction end processing (including dedicated instruction for the module) Device latch processing Service processing such as read and write of devices, labels, and program access files ( Page 680 Target List and

Operation Details of the Device/Label Access Service Processing Setting) Watchdog timer reset ( Page 166 Watchdog timer reset) Refresh between CPU modules (for the multiple CPU system configuration) Data collection by the data logging function (when the collection interval is set to "Each scanning cycle" or "Sample data at

the next END processing after the specified time has elapsed") Sequence scan synchronization sampling function Recording function (when the sampling method is set to "Each scanning cycle" or "Time specification") Self-diagnostics processing Sets a value to the special relay/special register (for those with the set timing specified as the END processing timing)

Even during the END processing, an interrupt program, fixed scan execution type program, or event execution type program (when the trigger type is set to at interrupt occurrence) is executed. To prevent the execution of an interrupt program during the END processing, disable an interrupt by the DI instruction immediately before the END processing, and enable an interrupt by the EI instruction at the head of the interrupt program.

6 RUNNING A PROGRAM 6.1 Scan Configuration 71

72

6.2 Scan Time The CPU module repeats the following processing. The scan time is the sum of the following processing and execution time.

*1 The initial scan time includes this processing.

Initial scan time The first scan time after the CPU module becomes in the RUN state.

How to check the initial scan time See below. Values stored in SD518 (Initial Scan Time) and SD519 (Initial Scan Time) Program List Monitor ( GX Works3 Operating Manual)

Initial scan time monitoring Monitoring is performed with the initial scan time monitoring time. ( Page 166 Scan time monitoring time setting)

Precautions on the initial scan time monitoring time Set the initial scan time monitoring time longer than the execution time of the initial scan time.

Initial processing (when switched to RUN)*1

I/O refresh

Program execution

END processing

Switched to RUN

Scan time

6 RUNNING A PROGRAM 6.2 Scan Time

6

Constant scan Scan time is different for each scan because its processing time varies depending on whether instructions used in a program are executed or not. By setting constant scan, the I/O refresh interval can be kept constant even when the program execution time varies because the program can be executed repeatedly by keeping the scan time constant. When constant scan is set (Setting value = 7ms)

When constant scan is not set

Setting constant scan Constant scan can be set.

[CPU Parameter] [RAS Setting] [Constant Scan Setting]

Window

Displayed items

The setting time for the constant scan must be a value that satisfies the relational expression below. "Watchdog timer setting time" > "Constant scan setting time" > "Maximum scan time of the program" If the maximum scan time of the program is longer than the constant scan setting time, it is assumed as an error to ignore the constant scan, and the scan time of the program is applied.

Item Description Setting range Default Constant Scan Sets the constant scan time. R00CPU, R01CPU, R02CPU:

0.5 to 2000ms (in increments of 0.1ms)

Other CPU modules: 0.2 to 2000ms (in increments of 0.1ms)

END

5ms

0 END 0

2ms 6ms

END 0

1ms 5ms

END 0

2ms

7ms7ms 7ms

Program

END processing

Waiting time

END

5ms

0 END 0 END 0 END 0

6ms 5ms

Program

END processing

6 RUNNING A PROGRAM 6.2 Scan Time 73

74

Accuracy of constant scan The accuracy of the constant scan is 0.01ms. However, if processing, which should be executed during the waiting time from the completion of the END processing to the start of the next scan, is being executed, the constant scan cannot finish even if the constant scan time is reached. The constant scan may increase by the program execution time of the interrupt factor. ( Page 74 Precautions)

Precautions Processing of the program is stopped during the waiting time from the time the END processing is completed for the program until the next scan starts. If any of the following processing requests is received during the waiting time, the corresponding processing is executed. Interrupt program Fixed scan execution type program Event execution type program which uses occurrence of an interrupt as a trigger Device/label access service processing

6 RUNNING A PROGRAM 6.2 Scan Time

6

Device/label access service processing setting The user can specify the time or the execution timing of the device/label access service processing which is performed during the END processing. A request to the CPU module from a peripheral is processed by the device/label access service processing. A communication response to a request from a peripheral varies depending on the scan time and the state of communication load. To create the service processing environment suitable for the system, change the device/label access service processing setting as shown below. Set a longer time for the device/label access service processing to improve a communication response to a peripheral. Set a shorter time for the device/label access service processing to reduce a scan time extension due to service

processing. Note that communications to the CPU module from multiple peripherals may lower a communication response to each peripheral. Thus, consider the performance of communication responses and the extension of scan time, and adjust the service processing environment according to the system by methods such as setting a longer time for the device/label access service processing or changing the parameter settings of peripherals so that the timeout time becomes longer.

For functions to which the device/label access service processing setting can be applied, refer to the list targeted for device/label access service processing setting. ( Page 680 Target list)

GOT GOT

GOT A GOT A

GOT B

1m s

Engineering tool

Ladder monitor Device monitor

Refresh processing

Control processing (at program execution)

Device and label access service processing setting = 10% of scan time Device and label access service processing time = 1ms

Program execution

END processing

1 sc

an (1

0m s)

Device/label access service processing request

Engineering tool

The device/label access service processing is executed in the END processing.

Engineering tool

6 RUNNING A PROGRAM 6.2 Scan Time 75

76

Setting method The device/label access service processing can be configured as follows.

[CPU Parameter] [Service Processing Setting] [Device/Label Access Service Processing Setting]

Window

Displayed items

Item Description Setting range Default Specifying Method

Select a method for specifying the service processing for access to devices/labels.

Execute the Process as Scan Time Proceeds

Set Processing Time Set Processing Counts Execute END Processing between

Programs

Execute the Process as Scan Time Proceeds

Rate Set the ratio of the device/label access service processing to execute during a single scan when "Execute the Process as Scan Time Proceeds" is enabled. The device/label access service processing time is determined based on the scan time.

1 to 99% (unit: 1%) 10%

Time Set the device/label access service processing time per scan when "Set Processing Time" is enabled.

0.1 to 1000ms (unit: 0.1ms) 0.1ms

Counts Set the number of executions of the device/label access service processing per scan when "Set Processing Counts" is enabled.

1 to 10 times (unit: 1 time) 1 time

6 RUNNING A PROGRAM 6.2 Scan Time

6

Operations enabled by setting details Operations enabled by setting details of the device/label access service processing setting are as follows.

*1 This term indicates how long the scan time will be extended at its maximum due to the device/label access service processing. *2 This term indicates how much the scan time will be varied due to the device/label access service processing. *3 This term indicates how long the response time will take after a request for the device/label access service processing is received from

an engineering tool or the like. *4 This term indicates how much the response time will be varied depending on the contents of requests for the device/label access service

processing from engineering tools or the like. *5 When this function is enabled, monitoring is performed between execution of programs, and therefore values of ongoing operation may

be read out. ( Page 78 When "Execute END Processing between Programs" is enabled) For what operation is enabled by setting each item, refer to the following. Page 682 Operation details

Item Scan performance Device/label access service process performance

Inter- program monitoring *5

Application

Increase*1 Stability*2 Response time*3

Stability*4

Execute the Process as Scan Time Proceeds

Medium Medium Medium Medium None This setting is useful to execute the device/label access service processing in a way commensurate with the system size. It allows the system to be designed without considering the device/label access service processing time because it is determined as a function of the scan time. Multiple requests are processed until the specified ratio is exceeded. If exceeded, the remaining requests are processed in the END processing of the next scan. When no request data is received in the current scan, the scan time is shortened by the specified ratio as the CPU module proceeds to the next scan without waiting for requests.

Set Processing Time Medium High Medium High None This setting is useful to give priority to the device/label access service processing. It allows for stable communication because the CPU module can always process a constant amount of the device/label access service processing without affecting the scan time. Multiple requests are processed until the specified processing time is exceeded. If exceeded, the remaining requests are processed in the END processing of the next scan. When no request data is received in the current scan, the scan time is shortened by the specified processing time as the CPU module proceeds to the next scan without waiting for requests.

Set Processing Counts

Large Low Medium High None This setting is useful to stably execute the device/label access service processing in a system where requests come from multiple peripherals. It provides stable communication in a system where multiple peripherals exist because the CPU module can execute the device/ label access service processing based on the number of request sources. Multiple requests are processed until the specified number of executions of the service processing is reached. When no request data is received in the current scan, the CPU module proceeds to the next scan without waiting for requests.

Execute END Processing between Programs

Large Medium Quick High Yes This setting is useful to give priority to the device/label access service processing in a system with a large number of programs. It improves the communication response as it enables the device/label access service processing to be executed multiple times during a single scan. When no request data is received between program executions and/or during the END processing, the CPU module proceeds to the next program or scan without waiting for requests.

6 RUNNING A PROGRAM 6.2 Scan Time 77

78

Precautions This section describes the precautions on the device/label access service processing setting.

Functions that may prolong the scan time For the following functions, the scan time may become longer than the specified time during processing even when this setting is applied. Online change Device/buffer memory batch monitor Real-time monitor function Data logging function Sequence scan synchronization sampling function Recording function File register write or read*1

*1 The scan time becomes longer when the size of data to write or read is large.

When constant scan is set The CPU module always processes one request during the END processing, and processes the remaining requests during the wait time for the next constant scan. Set constant scan setting time considering the time required for the device/label access service processing to execute.

When "Execute END Processing between Programs" is enabled When "Execute END Processing between Programs" is enabled, the device/label access service processing, such as device access, is performed between program executions and during the END processing. Therefore, when monitoring and current value change are performed in the situation where a device value is processed across programs, values of ongoing operation may be read or written.* 1

Also, when "Execute END Processing between Programs" is enabled, if monitoring and current value change are performed for the file register where "Use File Register of Each Program" is enabled, unintended data may be obtained or written. In this case, the value of the file register may not fall into the range depending on whether the file register is used for each program and the size of the file register.* 2

The target timing of monitoring or current value change can be specified by using the specified program monitor. ( Page 202 Specified Program Monitor) *1 Because the timing of monitoring or current value change (during execution of a program or the END processing) cannot be specified,

values of ongoing operation may be read or written. *2 Because monitoring is performed between programs and the operation is executed during the END processing, a file register to be

registered and whose current value is to be changed cannot be specified.

6 RUNNING A PROGRAM 6.2 Scan Time

6

6.3 Data Communication and I/O Processing Data communication In data communication, data such as I/O signals, buffer memory, and link device of the CPU module and intelligent function module are communicated. There are two modes for data communication: refresh mode which automatically sends\receives the module data into the device or label of the CPU module at END processing and direct mode which accesses when an instruction is executed in a program. When data communication is conducted for the module where a major error occurs, the following operation is performed: When access by the contact instruction is executed for the controlled module, non-running, rather than an error, is returned.

When direct access by other instructions is executed, "Major error in module" (error code: 2450) occurs. No error occurs when direct access for the non-controlled module is executed.

I/O processing and response delay The CPU module performs the I/O processing in the refresh mode. Using the direct access input/output in a 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.

Refresh mode The CPU module performs I/O processing collectively at a specified timing. The following table lists the refresh timing which can be specified. ( Page 80 Refresh mode)

*1 There are modules which performs the refresh processing at a specified END processing rather than at every END processing. ( User's manual for the module used)

Direct mode The CPU module performs I/O processing when each instruction is executed in a program. To access input/output modules in the direct mode, use the direct access input or direct access output in a program. ( Page 82 Direct mode)

Differences between refresh mode and direct mode The direct mode directly accesses I/O modules at execution of an instruction. Therefore, data is input faster than when it is input in refresh mode. Processing time required for each instruction, however, takes longer. The following table lists the availability of the refresh mode and the direct mode for each input and output.

Refresh timing Description When END processing is performed The refresh processing is performed in every END processing*1.

At the execution time of specified program

The refresh processing is performed before and after specified program execution. ( Page 97 Group setting for refresh)

Item Refresh mode Direct mode Input/output modules Enabled Enabled

Input/output of intelligent function modules

Remote input/output in CC-Link IE Controller Network, CC-Link IE Field Network, CC-Link IE Field Network Basic, MELSECNET/H, or CC-Link

Disabled

6 RUNNING A PROGRAM 6.3 Data Communication and I/O Processing 79

80

Refresh mode The CPU module performs I/O processing collectively at a specified timing. The timing of the input refresh and output refresh follows the specified refresh timing setting.

Outline of the processing The following describes the details of the refresh mode.

*1 The remote input refresh area indicates the area to be used when refresh is set to the input (X) in CC-Link IE Controller Network, CC- Link IE Field Network, CC-Link IE Field Network Basic, MELSECNET/H, or CC-Link.

*2 Data in the engineering tool input area can be turned on or off by the following: Test operation of an engineering tool Writing data from the network module Writing data from an external device using SLMP

*3 Data in the output (Y) device memory can be turned on or off by the following: Test operation of an engineering tool Writing data from the network module Writing data from an external device using SLMP

Item Description Input refresh At a specified timing (at END instruction execution or before specified program execution), input data are collectively

read out from the input modules (1), the OR processing with the engineering tool input area and remote input refresh area is executed, and then the data are stored in the input (X) device memory.

0 X10

Input module or output moduleCPU module

Device memory

On/off data

On/off data

Input of on/off data by input refresh

Output of on/off data by output refresh

X0

Y22

(3)

(4)

(5)

(1)

(2)Y20

*3

CPU module

CPU (operation processing area)

Input (X) device memory

Input module access area

Output (Y) device memory

Input refresh

Network module

Network module

Input module

Output module Output refresh

Remote input refresh area*1

Remote input area for CC-Link IE Field Network Basic

Engineering tool input area*2

Remote output area for CC-Link IE Field Network Basic

6 RUNNING A PROGRAM 6.3 Data Communication and I/O Processing

6

Input On/off data of an input module are batch-input to the area for communication with the input module in the CPU module at a specified timing (at END instruction execution or before specified program execution). The CPU module performs program operations using the on/off data stored in the input (X) device memory.

Output The operation results of the 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 at a specified timing (at END instruction execution or before specified program execution).

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. [Example] A program that turns on the output Y5E when the input X5 turns on

Y5E turns on the earliest

Y5E turns on the latest

Output refresh At a specified timing (at END instruction execution or before specified program execution), data in the output (Y) device memory (2) are collectively output to the output module.

Execution of an input contact instruction

Input data in the input (X) device memory (3) are read out and the program is executed.

Execution of an output contact instruction

Output data in the output (Y) device memory (4) are read out and the program is executed.

Execution of the OUT instruction The operation result of the program (5) are stored to the output (Y) device memory.

Item Description

55 X5 Y5E

OFF ON

0 END END0 056

OFF ON

X5

OFF ON

Y5E

OFF ON

Delay time

(Minimum 1 scan)

: Input refresh

External contact

External load

Devices in the CPU module

: Output refresh

OFF ON

0 END END0 056

OFF ON

X5

OFF ON

Y5E

OFF ON

Delay time

(Maximum 2 scans)

: Input refresh

External contact

External load

Devices in the CPU module

: Output refresh

6 RUNNING A PROGRAM 6.3 Data Communication and I/O Processing 81

82

Direct mode The CPU module performs I/O processing when each instruction is executed in a program.

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

Outline of the processing The following describes the details of the direct mode.

*1 Data in the engineering tool input area can be turned on or off by the following: Test operation of an engineering tool Writing data from the network module Writing data from an external device using SLMP

*2 Data in the output (Y) device memory can be turned on or off by the following: Test operation of an engineering tool Writing data from the network module Writing data from an external device using SLMP

Item Description Execution of an input contact instruction

The OR processing is executed with the input information of the input module (1) and the input data of the engineering tool input area (2) or remote input refresh area. The result is stored in the input (X) device memory and is used as input data (3) to execute the program.

Execution of an output contact instruction

Output data in the output (Y) device memory (4) are read out and the program is executed.

Execution of the OUT instruction The operation result of the program (5) are output to the output module, and stored in the output (Y) device memory.

0 DX10

Input module or output moduleCPU module

Device memory

On/off data

On/off data

Input of on/off data upon instruction execution

Output of on/off data upon instruction execution

(3)

(4)

(5)

DX0

Y20

(1) (2)

DY25

CPU module

CPU (operation processing area)

*2

Input (X) device memory

Output (Y) device memory

Input module

Output module

Engineering tool input area*1

6 RUNNING A PROGRAM 6.3 Data Communication and I/O Processing

6

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. [Example] A program that turns on the output DY5E when the input DX5 turns on

Y5E turns on the earliest

Y5E turns on the latest

55 DX5 DY5E

OFF ON

0 55 56

OFF ON

OFF ON

Delay time

External contact

DX5 (External contact)

DY5E (External load)

Devices in the CPU module

OFF ON

0 55 56

OFF ON

OFF ON

END 0 55 56

External contact

DX5 (External contact)

DY5E (External load)

Devices in the CPU module

Delay time

(maximum 1 scan)

: Input refresh

: Output refresh

6 RUNNING A PROGRAM 6.3 Data Communication and I/O Processing 83

84

6.4 Program Flow Programs are executed in order when the CPU module is switched to the RUN state according to the program execution type and execution sequence settings (Page 85 Program Execution Type, Page 96 Execution type change).

Programs with the same execution type are executed according to the execution sequence settings.

STOP RUN

Initial processing

Does an initial execution type

program exist?

Does not exist

Exists

I/O refresh

Scan execution type program

END processing

I/O refresh

Initial execution type program

Standby type program

Fixed scan execution type program

Event execution type program

6 RUNNING A PROGRAM 6.4 Program Flow

6

6.5 Program Execution Type Set the execution condition of the program. ( Page 96 Execution type change)

Initial execution type program Initial execution type program is executed only once when the CPU module has been powered off and on, or switched from the STOP state to the RUN state. Use this execution type for a program, for example, initial processing for the intelligent function module, which does not need execution after executed once in the initial scan.

Note that the execution time of the initial execution type program is the same as the initial scan time. ( Page 72 Initial scan time) When multiple initial execution type programs are executed, the execution time of the initial execution type program will be the total time until all the initial execution type programs finish execution.

*1 The sum of the initial execution type program execution time and END processing time is the initial scan time.

Precautions The following lists the precautions for the initial execution type programs.

Restrictions on program creation In the initial execution type program, do not use an instruction which requires several scans to complete (i.e., an instruction with a completion device).

Ex.

e.g. SEND and RECV instructions

(1) Divides programs into the initial execution type programs and scan execution type programs.

(1)

When controlled by one program

Program B

Program A

When controlled by separate programs (an initial execution type program is used)

Processing performed only once

Processing performed in each scan

Initial execution type program

Scan execution type program

END

0

0

END

END0

0 0END END 0

*1

Power-on RUN, STOP RUN

END processing

Initial execution type program A

Initial execution type program B

Initial execution type program C

Scan execution type program

First scan Second scan Third scan

6 RUNNING A PROGRAM 6.5 Program Execution Type 85

86

Scan execution type program Scan execution type program is executed only once per every scan starting from the scan following the scan in which the initial execution type program was executed.

When multiple scan execution type programs are executed, the execution time of the scan execution type program will be the total time until all the scan execution type programs finish execution. Note that if interrupt program, fixed scan execution type program, and/or event execution type program are executed before the scan execution type program finishes execution, the execution time for these programs is also included.

Fixed scan execution type program An interrupt program which is executed at a specified time interval. Differently from the normal interrupt program, this type of program does not require the interrupt pointer (I) and the IRET instruction and is executed for each program file unit.

To execute a fixed scan execution type program, the EI instruction must be used to enable interrupts.

0

END0

END0

END0

END0

END0

END0

END0

Scan time

Scan execution type program B

Scan execution type program C

Scan execution type program A

Initial execution type program

END processing

Power-onRUN, STOPRUN

4th scan3rd scan2nd scan1st scan

Condition established

Condition established

Fixed scan execution type program

Scan execution type program

END processing

Fixed scan interval

6 RUNNING A PROGRAM 6.5 Program Execution Type

6

Fixed scan interval setting Set the execution condition of the fixed scan execution type program.

[CPU Parameter] [Program Setting]

Operating procedure

Displayed items

"Program Setting" window 1. Click "Detailed Setting" on the "Program Setting" window.

"Detailed Setting" window 2. Select the program name and set the execution type to "Fixed Scan".

3. Click "Detailed Setting Information".

"Fixed Scan Execution Type Detailed Setting" window 4. Set the fixed scan interval.

Item Description Setting range Default Specified Time Intervals

Sets the fixed scan interval to execute the fixed scan execution type program.

When "ms" is selected: 0.5 to 60000ms (in increments of 0.5ms)

When "s" is selected: 1 to 60s (in increments of 1s)

Unit Selects the unit for the fixed scan interval. ms s

ms

6 RUNNING A PROGRAM 6.5 Program Execution Type 87

88

Operation when the execution condition is satisfied The following describes operation of the program.

If the execution condition is satisfied before the interrupt is enabled by the EI instruction The program enters the waiting status and is executed when the interrupt is enabled. Note that if the execution condition for this fixed scan execution type program is satisfied more than once during the waiting status, the program is executed only once when the interrupt is enabled.

If there are multiple fixed scan execution type programs If the specified time comes simultaneously for these programs, they are executed in order according to the specified execution sequence.

If another or the same execution condition is satisfied while the fixed scan execution type program is being executed

The program is executed according to the fixed scan execution mode setting.

If the execution condition is satisfied while the interrupt is disabled by the system The program is executed according to the fixed scan execution mode setting.

If an interrupt factor occurs during link refresh The link refresh is suspended and the fixed scan execution type program is executed. Even while the station-based block data assurance is enabled for cyclic data during refresh of such links as CC-Link IE Field Network, if the fixed scan execution type program uses a device specified as the refresh target, the station-based block data assurance for cyclic data is not available.

If an interrupt factor occurs during the waiting time after END processing in constant scan execution

The fixed scan execution type program is executed.

*1 If processing does not finish during the waiting time, the scan time is extended.

(1) The link refresh is suspended and the fixed scan execution type program is executed.

(1)

10ms10ms10ms10ms

Interrupt factor

Execution of link refresh

Execution of the fixed scan execution type program

*1

Condition established

Waiting time

Fixed scan interval

END processing

Scan execution type program

Fixed scan execution type program

Constant scan

6 RUNNING A PROGRAM 6.5 Program Execution Type

6

If another interrupt occurs while the fixed scan execution type program is being executed If an interrupt program (including an interrupt which triggers the event execution type program) is triggered while the fixed scan execution type program is being executed, the program operates in accordance with the interrupt priority. ( Page 114 Multiple interrupt function)

Processing when the fixed scan execution type program starts The same processing as when the interrupt program starts. ( Page 111 Processing at interrupt program startup)

Fixed scan execution mode For fixed scan interrupts (I28 to I31, I48, I49) triggered by the fixed scan execution type program or the internal timer of the CPU module, this mode specifies the program execution operation that is performed when more than one interrupt occurs ( Page 100 Operation upon occurrence of an interrupt factor) However, an execution cause which occurs while the interrupt is disabled by the DI instruction is excluded from the fixed scan execution mode target.

Operation in the fixed scan execution mode This section describes the operation which can be performed in the fixed scan execution mode. Execution Count Takes Priority The program is executed for all the pending number of executions so that it can be executed the same number of times as execution causes.

Precede Fixed Scan When a pending execution exists, it is performed within the delay limit value behind a cycle. ( Page 90 Delay limit value behind a cycle) Note that, even if more than one pending execution exists, only one execution is performed.

Fixed scan execution mode setting Use the fixed scan execution mode setting.

[CPU Parameter] [Interrupt Settings] [Fixed Scan Execution Mode Setting]

Window

Displayed items

(1) The program is executed just three times, which is the pending number of executions, as soon as interrupt becomes available.

Item Description Setting range Default Fixed Scan Execution Mode

When fixed scan characteristics are prioritized, an execution is performed within the delay limit value behind a cycle. When the number of executions is prioritized, all the pending executions are performed.

Precede Fixed Scan Execution Count Takes

Priority

Precede Fixed Scan

(1) Section where interrupts are disabled

"MAIN" (Fixed scan execution type program)

Cycle interval of MAIN Execution cause: 6 times

Number of executions: 6 times

Section where interrupts are disabled

Cycle interval of MAIN

"MAIN" (Fixed scan execution type program)

Number of executions: 4 times

Execution cause: 6 times

Delay behind the cycle

6 RUNNING A PROGRAM 6.5 Program Execution Type 89

90

Delay limit value behind a cycle This value indicates the allowable period of time for a delay (a time lag) behind a cycle and a waiting program is executed if an interrupt is enabled within the period. If an interrupt is enabled outside the period, the program is not executed.

The delay limit value behind a cycle differs as follows. For the fixed scan execution type program The value is the greatest common divisor of the fixed scan intervals of all the fixed scan execution type programs. For example, if there are fixed scan execution type programs with 2ms, 4ms, and 12ms scan periods, the delay limit value behind a cycle is 2ms. For fixed scan interrupts (I28 to I31, I48, I49) using the internal timer of the CPU module The value is fixed to the same value as the fixed scan interval. For example, if the periods are I28: 100ms and I29: 20ms, the delay limit value behind a cycle is 100ms for I28, and 20ms for I29.

Section where interrupts are disabled

"MAIN" (Fixed scan execution type program)

Cycle interval of MAIN

Delay behind the cycle

Delay limit value behind the cycle

6 RUNNING A PROGRAM 6.5 Program Execution Type

6

Event execution type program This type of program starts execution when triggered by a specified event. ( Page 91 Trigger type) The program is executed at the execution turn specified in the program settings of the CPU parameters, and if execution conditions of the specified trigger are met when the execution turn of the event execution type program comes, the program is executed.

*1 Measurement of elapsed time is 10ms or more because it is determined depending on the scan time.

Trigger type The following lists the triggers for the event execution type programs. ( Page 94 Trigger setting)

Interrupt occurrence by the interrupt pointer (I) When the specified interrupt factor occurs, the program is immediately executed once. However, before that, interrupt must be enabled by executing the EI instruction. Enabling programs to be independently executed as interrupt programs, this method eliminates the need to write the FEND instruction, interrupt pointers, and the IRET instruction within scan execution type programs.

Interrupt pointers (I) which can be specified are I0 to I15, I28 to I31, I44, I45, I48, I49, I50 to I1023.

Execution conditions for the event execution type program which is triggered by interrupt occurred by the interrupt pointer (I) are the same as those for general interrupt programs. ( Page 100 Operation upon occurrence of an interrupt factor)

(1) When an interrupt occurs, the event execution type program C is executed immediately.

Y50 M0

10ms*1 10ms*1 10ms*1

Y50: ON

First scan

The interrupt (I60) occurred.

Second scan Third scan Fourth scan Fifth scan

Power-on RUN, STOP RUN

Scan execution type program A

Scan execution type program C (Executed when Y50 is turned on.)

Scan execution type program D (Executed when the interrupt (I60) occurred.)

Event execution type program E (Executed when 10ms elapses.)

END processing

Scan execution type program B

Execution order

(1)

Scan execution type program A

Scan execution type program B

END processing

Scan execution type program C (Executed when the interrupt (I60) occurred.)

Execution order

Power-on RUN, STOP RUN

First scan Second scan Third scan

The interrupt (I60) occurred.

6 RUNNING A PROGRAM 6.5 Program Execution Type 91

92

Bit data ON (TRUE) The program is executed at the execution turn specified in program setting of the CPU parameters, and if the specified bit data is ON (TRUE) when the execution turn of the event execution type program comes, the program is executed. The current values of the output (Y), timer (T), and long timer (LT) used in this program can be cleared at the execution turn that comes after the specified bit data is changed from ON (TRUE) to OFF (FALSE).

Applicable devices are as follows.

*1 A local device or index-modified device cannot be specified. *2 This is not available when "Use File Register of Each Program" is enabled. However, if no file register is assigned or if specification is

out of the range, interrupt is not be turned on (TRUE).

To measure the timer and the retentive timer continuously even when the trigger execution condition of the event execution type program is not met, use the long timer (LT) and the long retentive timer (LST). The timer (T) and the retentive timer (ST) can be used in the event execution type program. However, they do not measure time when the trigger execution condition of the event execution type program is not met. Set "Clear Output and Current Value of Timer" to "Clear" when using the timer (T) and the retentive timer (ST). ( Page 94 Trigger setting) Note that if the above parameter is set, the use of the long timer (LT) and the long retentive timer (LST) is limited to the same as that of the timer (T) and the retentive timer (ST). (They do not measure time continuously when the trigger execution condition of the event execution type program is not met.)

(1) If Y50 is on when the execution turn of the event execution type program C comes, the program is executed. If Y50 is OFF, the program is not executed. (2) When "Clear Output and Current Value of Timer" is set, the current values of the output (Y), timer (T), and long timer (LT) used in this program are cleared

at the execution turn of the event execution type program that comes after Y50 is off.

Item Description Device*1 Bit device X(DX), Y, M, L, F, SM, B, SB, Jn\X, Jn\Y, Jn\B, Jn\SB

Bit specification of word device D, SD, W, SW, R*2, ZR*2, RD, Un\G, Jn\W, Jn\SW

Y50 M0

Y50 M0

(1) (2)

Y50: ON Y50: OFF

Execution order

Scan execution type program A

Scan execution type program B

Scan execution type program C (Executed when Y50 is turned on.)

END processing

Power-on RUN, STOP RUN

First scan Second scan Third scan Fourth scan

Section where Y50 is ON

6 RUNNING A PROGRAM 6.5 Program Execution Type

6

Passing time After the status of the CPU module is changed into the RUN state, programs are executed in execution turn specified in "Program Setting" of "CPU Parameter". If the specified time passes, the event execution type program is executed once when the execution turn of the program comes. The time is measured again starting from the program execution and the above operation is repeated. This method can be used when the processing is executed regularly after the specified time passes. This method is not for the interrupt execution which another program execution is interrupted and processed to secure the punctuality. The current values of the output (Y), timer (T), and long timer (LT) used in this program can be cleared at the execution turn that comes after the specified time passes.

Even though "Clear Output and Current Value of Timer" is set to "Clear" in the CPU parameters, the output value and the current value of the timer are not cleared if the scan time is longer than the value set to "Passing Time".

To measure time when the trigger type is set to "Passing Time", use the long timer (LT) and the long retentive timer (LST).

(1) After the specified time elapses, the event execution type program C is executed when the execution turn of the program comes. (2) When "Clear Output and Current Value of Timer" is set, the current values of the output (Y), timer (T), and long timer (LT) used in this program are cleared

at the execution turn of the event execution type program that comes after the specified time elapses.

10ms 10ms

(1) (2)

10ms

First scan Second scan Third scan Fourth scan

Power-on RUN, STOP RUN

Scan execution type program A

Scan execution type program C (Executed when 10ms elapses.)

END processing

Scan execution type program B

Execution order

Measurement section

The specified time 10ms elapses.

The specified time 10ms elapses.

6 RUNNING A PROGRAM 6.5 Program Execution Type 93

94

Trigger setting Use the event execution type detail setting.

[CPU Parameter] [Program Setting]

Operating procedure

Displayed items

*1 It cannot be set in the R00CPU, R01CPU, and R02CPU.

"Program Setting" window 1. Click "Detailed Setting" on the "Program Setting" window.

"Detailed Setting" window 2. Select the program name and set the execution type to "Event".

3. Click "Detailed Setting Information".

"Event Execution Type Detailed Setting" window 4. Sets the trigger type to execute the event execution type program.

Item Description Setting range Default Interruption occurrence Sets the interrupt pointer used as the trigger. I0 to I15, I28 to I31, I44, I45, I48*1, I49*1, I50 to I1023

ON of Bit Data (TRUE) Sets the device used as the trigger. Page 92 Bit data ON (TRUE)

Clear Output and Current Value of Timer

Sets that the current values of the output (Y), timer (T), and long timer (LT) used in this program are cleared at the execution turn of the event execution type program that comes after the specified bit data is OFF.

Do Not Clear Clear

Do Not Clear

Passing Time Unit Sets the time passed. When "ms" is selected: 1 to 65535ms (in units of 1ms)

When "s" is selected: 1 to 65535s (in units of 1s)

ms

Clear Output and Current Value of Timer

Sets that the current values of the output (Y), timer (T), and long timer (LT) used in this program are cleared at the execution turn of the event execution type program that comes after the specified time passes.

Do Not Clear Clear

Do Not Clear

6 RUNNING A PROGRAM 6.5 Program Execution Type

6

Standby type program This type of program is executed only when its execution is requested.

Librarization of programs Set a subroutine program and/or an interrupt program as a standby type program to manage them separately from the main routine program. In a single standby type program, multiple subroutine programs and interrupt programs can be created.

Program arrangement change Prepare programs available in all systems to use them only when necessary. For example, a program set in advance as the standby type with a parameter can be changed to scan execution type and executed. ( Page 96 Using an instruction)

Execution method The standby type program is executed as follows. Create a subroutine program and interrupt program within the standby type program, and then call them when an interrupt

occurs or by specifying with a pointer. Switch to another execution type program.

P100

I0 P100

I0

Main routine program

Subroutine program

Interrupt program

Scan execution type program Scan execution type program

Standby type program

Main routine program

Subroutine program

Interrupt program

6 RUNNING A PROGRAM 6.5 Program Execution Type 95

96

Execution type change This section describes how to change the execution type of programs.

Using parameter settings "Program Setting" can be used to specify the execution type of programs.

[CPU Parameter] [Program Setting] [Detailed Setting]

Operating procedure

Using an instruction Use the following instructions. PSCAN PSTOP POFF

Change timing The execution type change timing is shown below.

*1 This instruction stops the execution of the program at END processing after instruction execution.

"Program Setting" window 1. Click "Detailed Setting" on the "Program Setting" window.

"Detailed Setting" window 2. For each program, select the execution type in "Type" of "Execution Type".

Execution type before change

Execution instruction

PSCAN PSTOP POFF Initial Switches to "Scan" at the next scan. Switches to "Standby" at the next

scan. Turns off the output at the next scan and switches to "Standby" at the scan after that.Scan Non-processing (does not change from "Scan")

Fixed scan/event Switches to "Scan" at the next scan. Turns off the output at the next scan and switches to "Standby" at the scan after that.*1

Standby Non-processing (does not change from "Standby")

Non-processing (does not change from "Standby")

Initial execution type program

Standby type program Event execution type/Fixed scan execution type program

Scan execution type program

PSCAN instruction

PSCAN instruction

PSCAN instructionPSTOP or POFF instruction

PSTOP or POFF instruction

PSTOP or POFF instruction

6 RUNNING A PROGRAM 6.5 Program Execution Type

6

Precautions The following lists the precautions when changing the execution type. If a fixed scan execution type program or event execution type program is changed to another execution type, it cannot be

restored to the original execution type. If an instruction is executed multiple times in a single scan for a single program, the program operates for the instruction

executed last. For details on operation if an SFC program is specified, refer to the following. MELSEC iQ-R Programming Manual (Program Design)

Group setting for refresh Refresh can be performed when a specified program is executed*1 by setting a group number to each program and specifying the number for each module. *1 Input refresh (load of analog input, Input (X)) is performed before execution of a program, and output refresh (analog output, Output (Y))

is performed after execution of a program.

Refresh group setting A group number is set to each program.

[CPU Parameter] [Program Setting] [Program Setting] [Detailed Setting]

Window

Displayed items

When the specified group number is not set in the refresh settings of each module, the program is executed, but the refresh of the relevant group number is not executed.

Refresh setting of each module Select "At the execution time of specified program" in "Refresh Setting" of each module, and type the group number of the program to be refreshed.

[Module Parameter] [Refresh Setting]

Window

(Example: The "Refresh Setting" window for an I/O module)

For refresh of each module, refer to the manual for the module used.

Item Description Setting range Default Refresh Group Setting Set the group number of each program which is specified for each

module. (Do not Set) Groups [1] to [64]

(Do not Set)

6 RUNNING A PROGRAM 6.5 Program Execution Type 97

98

6.6 Subroutine Program Subroutine program is a program that is executed from a pointer (P) through the RET instruction. It is executed only when called by a subroutine call instruction (such as the CALL instruction or the ECALL instruction). A pointer type label can also be used instead of a pointer (P). The subroutine program is used for the following purposes. By grouping programs executed multiple times in a single scan into a single subroutine program, the total number of steps

in a single program can be decreased. By making a program which is only executed in a certain condition a subroutine program, the scan time can be shortened

for that program execution.

*1 The pointers are not required to be defined in an ascending order.

Making a program a standby type allows it to be managed as a separate program. ( Page 95 Standby type program) Use the ECALL instruction and other similar instructions to call program files.

For details on nesting (nesting structure) of subroutine programs, refer to the nesting (N). ( Page 446 Nesting (N))

Precautions The following lists the precautions when using the subroutine program. When using a local device, setting of SM776 (Local device setting at CALL) allows for using a local device of a program file

at the storage location of the subroutine program. Do not use the timer (T, ST). However, the timer can be used if the timer coil (the OUT T instruction) is executed only

once per scan. If the RET instruction is not used to return to the calling program and then the program is terminated, an error will occur. If a pointer (P) or pointer type global label exists within FB or FUN, an error will occur.

(1) The end of the main routine program

FEND

RET

RET

RET

END

P0

P8

P1

(1)

Main routine program

Program A

Subroutine program 1

Subroutine program 2

Subroutine program 3

Pointer*1

6 RUNNING A PROGRAM 6.6 Subroutine Program

6

6.7 Interrupt Program A program from an interrupt pointer (I) through the IRET instruction.

*1 Only one interrupt program can be created with a single interrupt pointer number. *2 The interrupt pointers are not required to be defined in an ascending order.

When an interrupt factor occurs, the interrupt program corresponding to its interrupt pointer number is executed. ( Page 450 The priority for the interrupt pointer numbers and interrupt factors) However, before that, interrupt must be enabled by using the EI instruction.

Making a program a standby type allows it to be managed as a separate program. ( Page 95 Standby type program)

(1) The end of the main routine program

I0: Interrupt factor for I0 I29: Interrupt factor for I29

FEND

EI

IRET

IRET

END

I0

I29

(1)

Main routine program

Interrupt program (I0)

Interrupt program (I29)

Interrupt pointer*1*2

IRET

IRET

I0 I29

Main routine program

Interrupt program (I0)

Interrupt program (I29)

Execution

Execution Execution Execution

Execution

Time

6 RUNNING A PROGRAM 6.7 Interrupt Program 99

10

Operation upon occurrence of an interrupt factor The following shows the operation when an interrupt factor occurs.

If an interrupt factor occurs during link refresh The link refresh is suspended and the interrupt program is executed. Even though the station-based block data assurance is enabled for cyclic data during refresh of such links as CC-Link IE Field Network, if the interrupt program uses a device specified as the refresh target, the station-based block data assurance for cyclic data is not available.

If an interrupt factor occurs during the waiting time after END processing in constant scan execution

The interrupt program for the interrupt factor is executed.

If another interrupt occurs while the interrupt program is being executed If an interrupt such as a fixed scan execution type program (including an interrupt which triggers the event execution type program) is triggered while an interrupt program is being executed, the program operates in accordance with the interrupt priority. ( Page 114 Interrupt priority)

If multiple interrupt factors occur simultaneously while the interrupt is enabled The interrupt programs are executed in the order of priority. If multiple interrupts with the same interrupt priority occur simultaneously, the interrupt programs are executed in the order of interrupt priority. ( Page 117 Multiple interrupt execution sequence)

(1) The link refresh is suspended and the interrupt program is executed.

(1)

10ms10ms10ms10ms

Interrupt factor

Execution of link refresh

Execution of the interrupt program

I50 I100 I150

IRET

IRET

IRET

Execution

Execution

Execution

Interrupt enabled (EI) Simultaneous occurrence of multiple interrupt factors

Main routine program

Interrupt program (I50)

Interrupt program (I100)

Interrupt program (I150)

High

Priority

Low

Waiting to be processed

Waiting to be processed

0 6 RUNNING A PROGRAM 6.7 Interrupt Program

6

If an interrupt factor occurs while interrupt is disabled (DI) For I0 to I15, I28 to I31, I48, I49, and I50 to I1023 The interrupt factor that has occurred is memorized, and the interrupt program corresponding to the factor will be executed when the interrupt is enabled. Even if the same interrupt factor occurs multiple times, it will be memorized only once. If the IMASK instruction and SIMASK instruction are used to disable the interrupt, all the memorized factors will be discarded.

For I45 The interrupt factor that has occurred is memorized, and the I45 interrupt program will be executed when the interrupt is enabled. Even if the I45 interrupt occurs multiple times, its interrupt factor will be memorized only once. If the IMASK instruction and SIMASK instruction are used to disable the interrupt, all the memorized factors will be discarded.

(1) The second and following interrupt factors that occur while interrupts have been disabled (DI) are not memorized. (2) When interrupts are enabled, interrupts are executed in order from I49 because it has a higher priority. (3) I28 is executed. (I49 is not executed for the second time.)

Mc: Multiple CPU synchronization cycle (1) The interrupt factor is memorized. (2) The second and following interrupt factors that occur while interrupts have been disabled (DI) are not memorized. (3) The interrupt is executed. (4) The interrupt is executed because interrupts are enabled.

I28 I49 I49I28

t

(1)

(2) (3)

Main routine program

I49 interrupt program

Interrupts are disabled. (DI)

Interrupts are enabled. (EI)

EI execution

I28 interrupt programP rio

rit y

le ve

l o f

in te

rr up

t

High

Low

I45 I45I45 (1)

(3)

t

Mc Mc Mc Mc

(2)

(4)Interrupts are disabled (DI).

Main routine program

I45 interrupt program

6 RUNNING A PROGRAM 6.7 Interrupt Program 101

10

For I44 If interrupt is enabled before the next cycle, the I44 interrupt program will be executed when the interrupt is enabled. If interrupt continues to be disabled beyond the start of the next cycle (the second cycle), the memorized information will be discarded (even when the interrupt is enabled, the I44 interrupt program will not be executed). Also, if the I44 interrupt program for this cause cannot be executed, SM480 (Cycle overrun flag for inter-module synchronization program (I44)) is turned on, and SD480 (Number of cycle overrun events for inter-module synchronization cycle program (I44)) reaches its upper limit. If the IMASK instruction and SIMASK instruction are used to disable the interrupt, all the memorized factors will be discarded.

Sc: Inter-module synchronization cycle (1) The interrupt factor is memorized. (2) Because an interrupt does not occur, the memorized information is discarded in the second cycle. (3) The interrupt is executed when interrupts are enabled. (4) I44 is not executed because interrupts continue to be disabled beyond the second cycle of I44. (5) The interrupt is executed because interrupts are enabled.

I44 I44 I44I44

t

(1)(1) (2)

(5)

(3)

(4)

ScScScSc

Interrupts are disabled (DI).

Interrupts are disabled (DI).

Main routine program

I44 interrupt program

2 6 RUNNING A PROGRAM 6.7 Interrupt Program

6

If an interrupt factor with the same or a lower priority occurs while the interrupt program is being executed

For I0 to I15 and I50 to I1023 The interrupt factor that has occurred is memorized. After the running interrupt program finishes, the interrupt program corresponding to the factor will be executed. Even if the same interrupt factor occurs multiple times, it will be memorized only once.

For I45 The interrupt factor that has occurred is memorized. After the running interrupt program finishes, the I45 interrupt program will be executed. Even if the I45 interrupt occurs multiple times, its interrupt factor will be memorized only once.

(1) The second and following interrupt factors that occur while interrupts have been disabled (DI) are not memorized. (2) After the interrupt in execution is completed, interrupts are executed in order from I50 because it has a higher priority. Although both I50 and I80 have the

same priority level, I50 is executed ahead of I80 because I50 has a higher priority order. (3) I80 is executed. (I50 is not executed for the second time.) (4) I100 is executed. (I80 is not executed for the second time.)

Mc: Multiple CPU synchronization cycle (1) The interrupt factor is memorized. (2) The second and following interrupt factors that occur while interrupts have been disabled (DI) are not memorized. (3) After I49 that has a higher priority level is completed, I45 is executed. (4) Because both I44 and I45 have the same priority level, the interrupt is executed after I44 is completed. (5) The interrupt is executed because I49 and I44 have been completed.

I0

I100 I80 I50 I100 I80 I50

t

(1)

(4)(2)

(3)

Main routine program

I0 interrupt program

I50 interrupt program

High

Low

I80 interrupt program

I100 interrupt program

Priority level of interrupt: I0 = I50 = I80

P rio

rit y

le ve

l o f

in te

rr up

t

I45 I49 I44

I45I45 I45 I45

t

(1) (1)(2) (2)

(5)

(3) (4)

McMcMcMcMc

Main routine program

I49 interrupt program

I45 interrupt program

I44 interrupt program

Priority level of interrupt: I45 = I44

High

P rio

rit y

le ve

l o f

in te

rr up

t

Low

6 RUNNING A PROGRAM 6.7 Interrupt Program 103

10

For I28 to I31, I48, and I49 The interrupt factor that has occurred is memorized. After the running interrupt program finishes, the interrupt program corresponding to the factor will be executed. If the same interrupt factor occurs multiple times, it will be memorized once but operation at the second and later occurrences depends on setting of the fixed scan execution mode ( Page 89 Fixed scan execution mode). When "Execution Count Takes Priority" is enabled, the interrupt program corresponding to the memorized interrupt factor will be executed after the running interrupt program finishes. When "Precede Fixed Scan" is enabled, the second and later occurrences will not be memorized.

(1) The second and following interrupt factors that occur while interrupts are being executed operate according to the setting of the fixed scan execution mode. (2) The program is not executed for the second time. (3) After the interrupt in execution is completed, interrupts are executed in order from I29 because it has a higher priority. (4) The second interrupt is executed.

(1) The second and following interrupt factors that occur while interrupts are being executed operate according to the setting of the fixed scan execution mode. (2) The program is not executed for the second time. (3) After the interrupt in execution is completed, interrupts are executed in order from I29 because it has a higher priority. (4) The second interrupt is executed.

I49 I28 I28

(2)

(4) t

(1)

(3)

High

Low

Main routine program

I49 interrupt program

I28 interrupt program

When interrupts with lower priority level than the one being executed occur

When "Execution Count Takes Priority" is set

When "Fixed Scan Takes Priority" is set

P rio

rit y

le ve

l o f

in te

rr up

t

I31 I29I28 I29I28

B

A

t

(4)

(4)

(1)

(2)

(3)

When interrupts with the same priority level as the one being executed occur

Main routine program

I31 interrupt program

I29 interrupt program

I28 interrupt program

Priority level of interrupt: I31 = I29 = I28

When "Fixed Scan Takes Priority" is set

High

Low

P rio

rit y

le ve

l o f

in te

rr up

t

From A From B

When "Execution Count Takes Priority" is set

4 6 RUNNING A PROGRAM 6.7 Interrupt Program

6

For I44 If the running interrupt program finishes before the next cycle, the I44 interrupt program will be executed when the running interrupt program finishes. If the running interrupt program continues beyond the start of the next cycle (the second cycle), the memorized information will be discarded (even when the running interrupt program finishes, the I44 interrupt program will not be executed). Also, if the I44 interrupt program for this cause cannot be executed, SM480 (Cycle overrun flag for inter-module synchronization program (I44)) is turned on, and SD480 (Number of cycle overrun events for inter-module synchronization cycle program (I44)) reaches its upper limit.

Sc: Inter-module synchronization cycle (1) The interrupt factor is memorized. (2) Because an interrupt does not occur, the memorized information is discarded in the second cycle. (3) After I49 that has a higher priority level is completed, I44 is executed. (4) After I45 that has the same priority level and a higher priority order is completed, the interrupt is executed. (5) I44 is not executed because the termination of I49 or I45 is in the second cycle for I44. (6) The interrupt is executed because I49 and I45 have been completed.

I49 I44

I45 I44

I49 I44 I44 I44

Sc Sc Sc Sc Sc

t

(1) (1) (1) (2)

(6)

(3)

(4)

(5)

Main routine program

I49 interrupt program

I45 interrupt program

I44 interrupt program

Priority level of interrupt: I45 = I44

P rio

rit y

le ve

l o f

in te

rr up

t

High

Low

6 RUNNING A PROGRAM 6.7 Interrupt Program 105

10

If the same interrupt factor occurs while the interrupt program is being executed For I0 to I15 and I50 to I1023 The interrupt factor that has occurred is memorized, and the interrupt program corresponding to the factor will be executed when the interrupt is enabled. Even if the same interrupt factor occurs multiple times, it will be memorized only once.

For I45 If an interrupt factor which is the same as that for the running interrupt program occurs, the factor is not memorized. Therefore, the corresponding interrupt program will not be executed after the running interrupt program finishes. Also, if the I45 interrupt program for this cause cannot be executed, SM481 (Cycle overrun flag for multiple CPU synchronization program (I45)) is turned on, and SD481 (Number of cycle overrun events for multiple CPU synchronization program (I45)) reaches its upper limit.

For I28 to I31, I48, and I49 The interrupt factor that has occurred is memorized. After the running interrupt program finishes, the interrupt program corresponding to the factor will be executed. If the same interrupt factor occurs multiple times, it will be memorized once but operation at the second and later occurrences depends on setting of the fixed scan execution mode ( Page 89 Fixed scan execution mode). When "Execution Count Takes Priority" is enabled, the interrupt program corresponding to the memorized interrupt factor will be executed after the running interrupt program finishes. When "Precede Fixed Scan" is enabled, the second and later occurrences will not be memorized.

(1) The second and following interrupt factors that occur while interrupts are executed are not memorized. (2) After the interrupt in execution is completed, the first interrupt program is executed.

Mc: Multiple CPU synchronization cycle (1) The interrupt factor is discarded because the same interrupt (I45) is being executed. (2) The interrupt is not executed. (3) The interrupt is executed.

(1) The second and following interrupt factors that occur while interrupts are being executed operate according to the setting of the fixed scan execution mode. (2) The program is not executed for the second time. (3) The second interrupt is executed.

I0I0

I0

t

(1)

(2)

Main routine program

I0 interrupt program

I45 I45 I45

McMc

t

(3)

(2)

(1) Main routine program

I45 interrupt program

I31 I31 I31

t

(1)

(2)

(3)

Main routine program

I31 interrupt program

When "Fixed Scan Takes Priority" is set When "Execution Count Takes Priority" is set

6 6 RUNNING A PROGRAM 6.7 Interrupt Program

6

For I44 If an interrupt factor which is the same as that for the running interrupt program occurs, the factor is not memorized. Therefore, the corresponding interrupt program will not be executed after the running interrupt program finishes. Also, if the I44 interrupt program for this cause cannot be executed, SM480 (Cycle overrun flag for inter-module synchronization program (I44)) is turned on, and SD480 (Number of cycle overrun events for inter-module synchronization cycle program (I44)) reaches its upper limit.

Sc: Inter-module synchronization cycle (1) The interrupt factor is discarded because the same interrupt (I44) is being executed. (2) The interrupt is not executed. (3) The interrupt is executed.

I44 I44 I44

ScSc

t

(1)

(2)

(3) Main routine program

I44 interrupt program

6 RUNNING A PROGRAM 6.7 Interrupt Program 107

10

If an interrupt factor occurs in the STOP/PAUSE status For I0 to I15, I28 to I31, I48, I49, and I50 to I1023 The interrupt factor that has occurred is memorized, and the corresponding interrupt program will be executed when the CPU module switches to the RUN state and the interrupt is enabled. Even if the same interrupt factor occurs multiple times before switching to the RUN state, it will be memorized only once.

For I45 The interrupt factor that has occurred is not memorized, and therefore the corresponding interrupt program will not be executed even when the CPU module switches to the RUN state and the interrupt is enabled. The interrupt program will be executed when the CPU module switches to the RUN state and then the first interrupt factor occurs.

(1) The second and following interrupt factors that occur while the CPU module is in the STOP state are not memorized. (2) When interrupts are enabled by changing the operating status of the CPU module from STOP to RUN, interrupts are executed in order from I50 that has a

higher priority level. (3) I100 is executed. (I50 is not executed for the second time.)

Mc: Multiple CPU synchronization cycle (1) The interrupt is not executed. (2) The interrupt is executed.

I100 I100I50 I50

STOP/PAUSE RUN

t

(1)

(2)

(3)

Main routine program

I50 interrupt program

CPU module operating status

I100 interrupt program

Interrupts are disabled. (DI)

EI execution Interrupts are enabled.

(EI)

High

P rio

rit y

le ve

l o f

in te

rr up

t

Low

I45 I45 I45

STOP/PAUSE RUN

t

(1)

(2)

Mc Mc

(2)Main routine program

I45 interrupt program

CPU module operating status

8 6 RUNNING A PROGRAM 6.7 Interrupt Program

6

For I44 The interrupt factor that has occurred is not memorized, and therefore the corresponding interrupt program will not be executed even when the CPU module switches to the RUN state and the interrupt is enabled. Instead, startup of interrupt is prepared when the CPU module switches to the RUN state and the interrupt is enabled (the interrupt program will not be executed upon occurrence of the first interrupt factor). Then, the interrupt program will be executed during the second cycle after the switch to the RUN state.

Sc: Inter-module synchronization cycle (1) The interrupt is not executed. (2) The interrupt is executed.

I44 I44 I44

STOP/PAUSE RUN

Sc Sc

t

(2)

(1)(1)

Main routine program

I44 interrupt program

CPU module operating status

6 RUNNING A PROGRAM 6.7 Interrupt Program 109

11

Interrupt period setting The interrupt cycle based on the internal timer can be specified.

[CPU Parameter] [Interrupt Settings] [Fixed Scan Interval Setting]

Window

Displayed items

*1 This item is not displayed on the R00CPU, R01CPU, and R02CPU.

Interrupt enabled during instruction execution Sets whether or not to enable or disable execution of an interrupt program during execution of an instruction. By enabling the interrupt during instruction execution, an interrupt can occur even while an instruction with a long processing time is being executed, resulting in higher interrupt accuracy.

[CPU Parameter] [Interrupt Settings] [Interrupt Enable Setting in Executing Instruction]

Window

Displayed items

Item Item Description Setting range Default Interrupt Setting from Internal Timer I28 Sets the execution interval of I28. 0.5 to 1000ms (in units of 0.5ms) 100.0ms

I29 Sets the execution interval of I29. 40.0ms

I30 Sets the execution interval of I30. 20.0ms

I31 Sets the execution interval of I31. 10.0ms

I48*1 Sets the execution interval of I48. 0.05 to 1000ms (in units of 0.05ms) 5.00ms

I49*1 Sets the execution interval of I49. 1.00ms

Item Description Setting range

Default

Interrupt in Executing Instruction

Sets whether or not to enable or disable execution of an interrupt program during execution of an instruction. For the precautions with "Enable" set, refer to the precautions for an interrupt program. ( Page 118 Precautions)

Disable Enable

Disable

0 6 RUNNING A PROGRAM 6.7 Interrupt Program

6

Processing at interrupt program startup The processing shown below is performed when the interrupt program starts. Saving/restoring of the file register (R) block number Saving/restoring of the index register (Z, LZ)

Saving/restoring of the file register (R) block number When an interrupt program starts, the block number of the file register (R) of the running program is saved and passed to the interrupt program. Also, when the interrupt program finishes, the saved block number is restored to the running program.

[CPU Parameter] [Interrupt Settings] [Block No. Save/Recovery Setting]

Window

Displayed items

When the block number of the file register (R) is not changed during execution of an interrupt program, enabling "Not Saved/Recovered" can reduce the startup time and the termination time of the interrupt program. ( Page 648 Overhead time when executing the interrupt program). To change the block number of the file register (R) while "Not Saved/Recovered" is enabled, the block number of that file register (R) must be saved/restored by the program.

Item Description Setting range Default File Register (R) Block No.

Sets whether or not the block number of the file register (R) is saved/restored when an interrupt program is being executed.

Not Saved/ Recovered

Save/Recover

Save/Recover

6 RUNNING A PROGRAM 6.7 Interrupt Program 111

11

Saving/restoring of the index register (Z, LZ) When an interrupt program starts, the value of the index register (Z, LZ) of the running program is saved. When the interrupt program finishes, and the saved value is restored to the running program. Note that when an interrupt program starts, the local index register (Z, LZ) is not switched to the different one. When the local index register (Z, LZ) is used for the interrupt program/fixed scan execution type program/event execution type program which uses occurrence of an interrupt as a trigger, the register which has been used for the previous program is continuously used. Thus, the local index register (Z, LZ) cannot be used independently. Saving/restoring of the index register

Operations of the local index register and local device

*1 The value of Z0 is changed by the interrupt program, fixed scan execution type program, or event execution type program. *2 For when SM777 is on (when using the local device of the program file of storage location)

(1) This value can be used as a value specific to the scan execution type program. (Using the value in an interrupt program is not needed to be concerned.) (2) This value can be used only at the moment an interrupt program, fixed scan execution type program, or event execution type program is executed. (The

value cannot be used continuously.)

Z0=0 Z0=3 *1Z0=0 Z0=0

Z0=0 Z0=0

Z0=0

Z0=0 (2)

(1) Interrupt program/ Fixed scan execution type program/ Event execution type program

Execution program

Value of the index register

Scan execution type program

Switch Scan execution type program

Switch

Save

Return

Save area of the index register (for scan execution type programs)

Interrupt program/ Fixed scan execution type program/ Event execution type program

Without change

Save

Return

Without change

Z0=0Z0=1 Z0=1Z0=10 Z0=1Z0=1

#D0=0#D0=1 #D0=1

#D0=0#D0=100 #D0=100

Execution program

Local index register (Z0) for A

Local index register (Z0) for B

Local device (#D0) for A*2

Local device (#D0) for B*2

Scan execution type program (A)

Scan execution type program (A)Switch Return

Return

Switch

Save Save

Not used Not used

Interrupt program/ Fixed scan execution type program/ Event execution type program (B)

Interrupt program/ Fixed scan execution type program/ Event execution type program (B)

Without change Without change

2 6 RUNNING A PROGRAM 6.7 Interrupt Program

6

If the value of the index register used for the interrupt program is continuously used for the next interrupt program, the value of the index register for the interrupt program must be saved or restored. Create a program to add the MOV instruction and the ZPUSH/ZPOP instruction.

(1)This value can be used as a value specific to the main routine program. (2)This value can be used as a value specific to the interrupt program. (This value can be used continuously.)

Z0=0 Z0=3 *3

D0=0 D0=3 D0=3D0=3-

Z0=0 Z0=3 *4

D0=3

Z0=0 Z0=0

Z0=0 Z0=0 Z0=0MOV D0 Z0I50

MOV K3 Z0

IRET

MOV Z0 D0

FEND

(1) (2)

Value of the index register

Save area of the index register (for scan execution type programs)

Save

ReturnWithout change Without change

Save

Interrupt programExecution program Main routine program

Switch Main routine program

Switch Interrupt programReturn

Value of D0

Program example

Main routine program

*3 A value in Z0 changes at MOV D0 Z0. *4 Z is zero when the program and are not added.

6 RUNNING A PROGRAM 6.7 Interrupt Program 113

11

Multiple interrupt function When a new interrupt triggered by another factor occurs during execution of an interrupt program, the running program will be suspended if its priority is lower than that of the new interrupt. A program with higher priority is executed based on the set priority whenever its execution condition is satisfied.

Interrupt priority If the interrupt priority of a program for which its execution condition has been satisfied is higher than that of the running program, the programs are executed in accordance with their interrupt priority. If the interrupt priority of the new program is the same or lower, it enters the waiting status until the running program finishes. The interrupt priorities 1 to 4 listed below cannot be changed, whereas the interrupt priorities 5 to 8 can. ( Page 115 Interrupt priority setting)

(1) A high-priority interrupt is executed by interrupting a low-priority interrupt. (2) Even if a high-priority interrupt occurs, it enters the waiting status until the interrupt in execution is completed.

Interrupt priority

Interrupt factor (Interrupt pointer) Execution sequence at simultaneous occurrence

Changeability

High Low

1 High-speed interrupt by internal timer 1 (I49) Unchangeable (Fixed)2 High-speed interrupt by internal timer 2 (I48)

3 Inter-module synchronous interrupt (I44), Multiple CPU synchronous interrupt (I45)

I45 I44

4 Interrupt by internal timer (I28 to I31), Fixed scan execution type program

I31 I30 I29 I28 Fixed scan execution type program

5 to 8 Interrupt from module (I0 to I15, I50 to I1023) I0 I1023 Changeable

(1) (2)

When the multiple interrupt function is enabled

I10 interrupt program

I0 interrupt program

Main routine program Time

I10 interrupt program

I0 interrupt program

Main routine program Time

Interrupt is being executed.

Interrupt stops.

interrupt occurs.

Program stops.

Program restarts.

I10: High I0: Low

When not set (at default) [Priority]

4 6 RUNNING A PROGRAM 6.7 Interrupt Program

6

Interrupt priority setting The interrupt priority (5 to 8) of interrupts from modules can be changed.

[CPU Parameter] [Interrupt Settings] [Interrupt Priority Setting from Module]

Operating procedure

Displayed items

"Interrupt Settings" window 1. Set "Multiple Interrupt" to "Enable" on the "Interrupt Settings" window, and click "Detailed Setting".

"Detailed Setting" window 2. Change the priority of each interrupt pointer.

Item Description Setting range Default Multiple Interrupt Sets whether or not to enable multiple interrupt. Disable

Enable Disable

Interrupt priority

Detailed Setting

Sets the priority of the interrupt pointers I0 to I15 and I50 to I1023. 5 to 8 8

6 RUNNING A PROGRAM 6.7 Interrupt Program 115

11

Disabling/enabling interrupts with a specified or lower priority Interrupts with a priority equal or lower than that specified by the DI or EI instruction can be disabled or enabled even when multiple interrupts are present.

Ex.

Order of interrupt occurrence:

Order of interrupt execution:

Order of interrupt completion:

Disabled interrupt priorities and the current interrupt priority can be checked in SD758 (Interrupt disabling for each priority setting value) and SD757 (Current interrupt priority) respectively.

Priority Interrupt pointer High Low

1 I49

2 I48

3 I44, I45

4 I28, I29, I30, I31

5 I101

6 I0, I50, I100

7 I1020

8 An interrupt pointer among I50 to I1023 with the priority other than 5 to 7

(1) Interrupt is enabled. (2) Interrupts with priority 3 to 8 are disabled. (3) I28 is not executed because interrupts with priority 3 to 8 are disabled. (4) I48 is executed because its interrupt priority is higher. (5) Return from interrupt. Execution of the interrupted I10 resumes. (6) High-priority interrupt I28 is executed because interrupts with priority 3 to 8 have been enabled.

[ EI ]

[ DI K3 ] [ EI ]

(1)

(2)

(3)

(4)

(5)

(6)

(5)

[Priority 2] 1) I48 interrupt program

[Priority 4] 2) I28 interrupt program

[Priority 8] 3) I10 interrupt program

Scan execution type program

Time

6 6 RUNNING A PROGRAM 6.7 Interrupt Program

6

Multiple interrupt execution sequence When multiple interrupts occur, the interrupt program with the highest priority is executed. Then, the interrupt program with the highest priority among those interrupted and in waiting status as a result of interrupts will be executed next when the previous is finished.

Ex.

Order of interrupt occurrence:

Order of interrupt execution:

Order of interrupt completion:

Priority Interrupt pointer High Low

1 I49

2 I48

3 I44, I45

4 I28, I29, I30, I31

5 I101

6 I0, I50, I100

7 I1020

8 An interrupt pointer among I50 to I1023 with the priority other than 5 to 7

(1) Interrupt is enabled. (2) I50 is executed because its interrupt priority is higher. (3) Enters waiting status because its interrupt priority is lower. (4) I101 is executed because its interrupt priority is higher. (5) Return from interrupt. Execution of the interrupted I50 resumes. (6) Enters the waiting status until the execution of I50 completes because its interrupt priority is the same as that of I50 by setting. (7) I0 is executed before I100 because its interrupt pointer is smaller. (8) Return from interrupt. I1020 is executed because its interrupt priority is higher than those of I1020 and I0. (9) Return from interrupt. I1020 is executed because its interrupt priority is higher than that of I2. (10)Return from interrupt. Execution of the interrupted I2 resumes.

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

EI

6)[Priority 5] 1) I101 interrupt program

[Priority 6] 2) I0 interrupt program

[Priority 6] 3) I50 interrupt program

[Priority 6] 4) I100 interrupt program

[Priority 7] 5) I1020 interrupt program

[Priority 8] 6) I2 interrupt program

Scan execution type program

Time

3) 5) 1) 4) 2)

6 RUNNING A PROGRAM 6.7 Interrupt Program 117

11

Precautions The precautions for the interrupt program are mentioned below.

Restrictions on program creation The PLS/PLF instruction performs OFF processing in the scan after the instruction execution. The device turned on

remains on until the interrupt program starts again and the instruction is executed. The timer (T, ST) and the counter (C) cannot be used for interrupt programs.

Data inconsistency When the interrupt during instruction execution is set to "Enable", processing of an instruction may be suspended and the interrupt program may be executed. Accordingly, if the interrupted program and the interrupt program both use the same device, data may become inconsistent. Take the following preventive measures. Use the DI instruction to disable the interrupt for an instruction that causes inconsistency when interrupted. In an interrupt program, before accessing the device shared by overlapping programs, transfer data to another device in

batch to use, and then write back to the shared device in batch. When using the bit data, be careful so that the interrupted program and the interrupt program shall not use the same bit

data.

If the interrupt accuracy does not increase If the interrupt accuracy does not increase even when the interrupt during instruction execution is set to "Enable", it may increase by taking the following measures: Limit each character string used in a program to 32 characters or less in length. Decrease the multiplex interrupts. Reduce the number of times to access the Q series module or the number of points. Do not access the Q series module from multiple CPU modules when the multiple CPU system is configured.

Monitoring the interrupt program execution time The execution time of the interrupt program can be monitored with the interrupt program in which the inter-module synchronous interrupt (I44) and multiple CPU synchronous interrupt (I45) are used. ( Page 169 Error detection setting)

When the start-up of an interrupt program is delayed If the execution interval of the interrupt program is short, the start-up of the interrupt program may be delayed when the instruction with a long processing time is executed, the online ladder block change is performed, or a Q series module is accessed simultaneously from multiple CPU modules using instructions in the multiple CPU system configuration. Therefore, when the execution time is monitored for the interrupt program that uses the inter-module synchronous interrupt (I44) and multiple CPU synchronous interrupt (I45), an error may be detected in the CPU module. ( Page 169 Error detection setting)

Consideration when using the data logging function and the recording function When occurrence of an interrupt is specified as the data collection condition of data logging or when the sampling method of the recording function is set to use the trigger instruction in an interrupt program, set the fixed scan interval of the interrupt program, taking into consideration the processing time for these functions. ( Page 299 Using together with interrupt programs)

8 6 RUNNING A PROGRAM 6.7 Interrupt Program

6

Interrupt processing with FB/FUN FB/FUN consists of multiple instructions. When an interrupt occurs during execution of the FB/FUN, the execution will be suspended and an interrupt program will be executed even though "Interrupt Enable Setting in Executing Instruction" of the CPU parameter has been set to "Disable". To disable the execution of the interrupt program during execution of FB/FUN, use the DI instruction to disable the interrupt before the FB/FUN is called and use the EI instruction to enable the interrupt after execution of the FB/FUN. In ST programs and FBD/LD programs, each of the following elements and program elements consists of multiple instructions. Instruction (manufacturer-defined FB/FUN) Arithmetic operations in ST programs (Example: D0 := D1 + D2 - D3;) Logical operations in ST programs (Example: M0 := M1 AND M2 OR M3;) To disable the interrupt during execution of an ST program or an FBD/LD program, use the DI instruction and the EI instruction before and after each element or program element regardless of the setting of "Interrupt Enable Setting in Executing Instruction".

Extended interrupt program processing time If interrupts during instruction execution are set to "Enable" in the interrupt enabled during instruction execution setting, and the interrupt program is executed when the following conditions are met, the interrupt program processing time will take longer. ( Page 110 Interrupt enabled during instruction execution) If accessing the refresh data register (RD), a module label, or labels, or using FB/ST/FBD in the interrupt program while

executing an instruction involving the transfer of a significant amount of data to the device/label memory, or during refresh processing.

If accessing the device/label memory in the interrupt program when using FB/ST/FBD while executing an instruction involving the transfer of a significant amount of data to the refresh data register (RD), a module label, or a label, or during refresh processing to the refresh data register (RD) or a module label.

Delay in interrupt programs Completing low-priority interrupt programs may take time if high-priority interrupt programs are executed frequently when the multiple interrupt function is used. Adjust the processing of high-priority interrupt programs to allow execution of low-priority interrupts.

Devices and labels used by interrupt programs Do not use the same global devices and labels in multiple interrupt programs because it may cause data inconsistency when the multiple interrupt function is used.

6 RUNNING A PROGRAM 6.7 Interrupt Program 119

12

7 CPU MODULE OPERATION PROCESSING Here is a list of the operating status of the CPU module: RUN state STOP state PAUSE state

7.1 Operation Processing by Operating Status This displays operation processing according to the operating status of the CPU module.

Operation processing in RUN state In RUN state, the program operation is repeatedly performed in the following order: Step 0 END/FEND instruction Step 0.

Output at the time of entering RUN state Depending on the setting of output (Y) at the time of change from STOP state to RUN state, either of the following is output. ( Page 122 Output mode at operating status change (STOP to RUN)) Status of the output (Y) that was saved during the STOP state Operation result after the completion of one scan The device memory other than the output (Y) holds the status immediately before the RUN state. However, if a device initial value is set up, this initial value is set. In addition, the local devices are cleared.

Operation processing in STOP state In STOP state, the operation is stopped (state with a stop error included).

Output at the time of entering STOP state All points are turned off with the output status immediately before the STOP state saved. The device memory other than the output (Y) holds the status immediately before the STOP state.

Operation processing in PAUSE state In PAUSE state, the program operation is suspended holding the status of the output and the device memory after the completion of one scan.

0 7 CPU MODULE OPERATION PROCESSING 7.1 Operation Processing by Operating Status

7

7.2 Operation Processing When Operating Status Is Changed

This displays operation processing when the operating status of the CPU module is changed.

CPU module operating status

CPU module processing

Program External output Device memory

Other than Y Y STOP RUN Executes the program from the

start. Determines the status depending on the setting of "Output Mode Setting at STOP to RUN" in the CPU parameter. ( Page 122 Output mode at operating status change (STOP to RUN))

Retains the device memory status immediately before the RUN state. However, if a device/ label initial value has been set, this initial value is set. Clears local devices.

Determines the status depending on the setting of "Output Mode Setting at STOP to RUN" in the CPU parameter. ( Page 122 Output mode at operating status change (STOP to RUN))

RUN STOP Executes the program up to the END instruction and then stops.

Saves the output (Y) status immediately before the STOP state, and all points turn off.

Retains the device memory status immediately before the STOP state.

Saves the output (Y) status immediately before the STOP state, and all points turn off.

RUN PAUSE Stops the operation after the execution of one scan.

Retains the output (Y) status immediately before the PAUSE state.

Retains the device memory status immediately before the PAUSE state.

Retains the output (Y) status immediately before the PAUSE state.

PAUSE RUN Executes the program from the start.

Retains the output (Y) status immediately before the RUN state.

Retains the device memory status immediately before the RUN state. Clears local devices.

Retains the output (Y) status immediately before the RUN state.

PAUSE STOP Operation remains stopped. Saves the output (Y) status immediately before the STOP state, and all points turn off.

Retains the device memory status immediately before the STOP state.

Saves the output (Y) status immediately before the STOP state, and all points turn off.

STOP PAUSE Operation remains stopped. Retains the output (Y) status immediately before the PAUSE state.

Retains the device memory status immediately before the PAUSE state.

Retains the output (Y) status immediately before the PAUSE state.

7 CPU MODULE OPERATION PROCESSING 7.2 Operation Processing When Operating Status Is Changed 121

12

Output mode at operating status change (STOP to RUN) When the operating status changes from RUN to STOP, for example, the CPU module internally stores the status of the outputs (Y) to turn them all off.

Operation when the operating status is changed from STOP to RUN Select whether or not to resume from the previous output status when the operation status of the CPU module is changed from STOP to RUN by using a holding circuit.

Outputting the output (Y) status before STOP The program operation is resumed after outputting the output (Y) status immediately before the operating status of the CPU module is changed to the STOP state. If the output (Y) is forcibly turned on in the STOP state, the status prior to the STOP state is output. If the output (Y) was off before entering the STOP state, the status when it was on is not retained. In the following figure, X20 represents the start button, X21 represents the stop button, and Y represents an output.

Clearing the output (Y) (output after one scan) All outputs are turned off, and the output (Y) is output after the program operations are executed. If the output (Y) is forcibly turned on when the operating state is STOP, the ON state is retained. In the following figure, X20 represents the start button, X21 represents the stop button, and Y represents an output.

Setting the output mode Set the mode in "Output Mode Setting of STOP to RUN".

[CPU Parameter] [Operation Related Setting] [Output Mode Setting of STOP to RUN]

Window

Displayed items

Item Description Setting range Default Output Mode of STOP to RUN

Set the operation of the output (Y) when the operating status is changed from STOP to RUN.

Output the Output (Y) Status before STOP Clear (Output is 1 scan later) the Output

(Y)

Output the Output (Y) Status before STOP

ON

OFF

OFF

ON

OFF

X21

Y0

X20

RUNSTOP STOPRUN

X21

Y0

X20

RUNSTOP STOPRUN ON

OFF

ON

OFF

OFF

2 7 CPU MODULE OPERATION PROCESSING 7.2 Operation Processing When Operating Status Is Changed

7

7.3 Operation Processing at Momentary Power Failure When an input power supply voltage supplied to the power supply module falls below the specified range, a momentary power failure is detected and the following operation processing is performed.

Momentary power failure not exceeding the allowable momentary power failure time If a momentary power failure occurs, the event history is registered to suspend the operation processing. Note however that measurement of the timer device continues. In addition, the output status is held.

When the momentary power failure is cleared Once the momentary power failure is cleared, the operation processing continues.

Measurement of the watchdog timer (WDT) at a momentary power failure Even if the operation is suspended due to a momentary power failure, measurement of the watchdog timer continues. For example, assuming that the monitoring time of scan time is set to 200ms and the scan time is 190ms, a momentary power failure of 15ms causes a WDT error. ( Page 166 Scan time monitoring time setting)

Momentary power failure exceeding the allowable momentary power failure time This case results in initial start, the same operation processing as when the CPU module is powered on or is reset.

7 CPU MODULE OPERATION PROCESSING 7.3 Operation Processing at Momentary Power Failure 123

12

8 MEMORY CONFIGURATION OF THE CPU MODULE

8.1 Memory Configuration The following shows the memory configuration of the CPU module.

*1 The built-in memory is a generic term of the memory built in the CPU module. *2 The R00CPU, R01CPU, and R02CPU retain the data in each device/label with latch setting without a battery during power failure. (

Page 473 Latch with Battery) The other programmable controller CPUs retain the data in each device/label with latch setting without a battery during power failure by inserting a battery-less option cassette to the CPU module. ( Page 480 Latch with Battery-less Option Cassette)

*3 This memory can be used in the R04CPU, R08CPU, R16CPU, R32CPU, R120CPU, R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, and R120ENCPU.

*4 An SD memory card cannot be used in the R00CPU.

The usage of the memory can be checked from the engineering tool. ( GX Works3 Operating Manual) The number of writes for the program memory and data memory is limited to 100000 times. When using the

function that the target file is written, pay attention to the number of writes. (Page 136 File types and storage memory) The current number of writes for the program memory and data memory can be checked in the special register (SD630/SD631 and SD634/SD635). ( Page 617 Drive information)

RAM ROM

Program memory

Data memory

Signal flow memory

CPU buffer memory

Refresh memory

Program cache memory

Device/label memory*2

Function memory*3

SD memory card*4

Built-in memory*1

4 8 MEMORY CONFIGURATION OF THE CPU MODULE 8.1 Memory Configuration

8

Program memory/program cache memory The program memory and program cache memory store necessary programs for the CPU module to perform operations. At the following timing, data in the program memory is transferred to the program cache memory*1 and an operation is performed. *1 This memory is used for program operations.

Powered-on Reset operation

Application The program memory and program cache memory store execution programs of program files and FB (function block) files. Execution programs include instruction codes, statements, and notes.

Data to be allocated The file header area*1 and the execution program area (including reserved area for online change) that exist in program files and FB files are allocated to the program memory. *1 Depending on the model and firmware version of the CPU module, the file header area is allocated to the data memory. ( Page 126

Destination of the file header area)

Data allocation and procedure of read/write operations The following figure shows the data allocation of the program memory and program cache memory and the procedure of read/ write operations from/to the programmable controller.

*1 Program restoration information includes the information required to read a program from the programmable controller with the engineering tool.

*2 Depending on the model and firmware version of the CPU module, the destination of the file header area is the data memory. ( Page 126 Destination of the file header area)

For read/write operations from/to the programmable controller, refer to the following. GX Works3 Operating Manual

(1) When data is written to the programmable controller, the file header, execution program, and reserved area for online change are written to the program cache memory, and program restoration information is written to the data memory.

(2) After being written to the program cache memory, the data is automatically transferred to the program memory. (3) When data is read from the programmable controller, the file header, execution program, and reserved area for online change are read from the program

memory, and the program restoration information is read from the data memory. (4) After the CPU module is powered off and on or is reset, the data in the program memory is transferred to the program cache memory and operations are

executed.

(1)

(1)

(2) (3)

(1)

(3)

(3)

(4)

+

Data memory

Program cache memory

Program memory

When the data is written to the programmable controller

When the CPU module is powered off and on or is reset

Engineering tool

When the data is read from the programmable controller

Inside of the CPU module

File header area*2

Program restoration information area*1

Program file

Execution program area

Reserved area for online change

8 MEMORY CONFIGURATION OF THE CPU MODULE 8.1 Memory Configuration 125

12

Destination of the file header area For the following CPU modules, the destination of the file header area is the data memory.

Device/label memory The device/label memory has the following areas.

The capacity of each area can be changed with the setting of the CPU parameter. ( Page 127 Device/label memory area setting)

Data to be allocated The following table lists the data allocated to each area.

*1 File register files which are stored in the area for storing file register files can be written or read in file unit.

Free space of areas can be checked in "Device/Label Memory Area Capacity Setting". ( Page 127 Device/label memory area setting)

CPU module Firmware version R04CPU, R08CPU, R16CPU, R32CPU, R120CPU R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, R120ENCPU

"30" or earlier

Area Application Device area User device

Label area Label area Global label and local label

Latch label area Global label and local label with latch specified

Local device area Local device (excluding index register)

File storage area File register file and other data*1

Device area

Label area

Label area

Latch label area

Local device area

File storage area

6 8 MEMORY CONFIGURATION OF THE CPU MODULE 8.1 Memory Configuration

8

Device/label memory area setting The capacity of each data area allocated within the device/label memory can be changed. ( Page 126 Device/label memory)

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Setting]

Operating procedure

Displayed items

*1 Check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions) *2 When using 16MB extended SRAM cassettes (NZ2MC-16MBS), precautions apply when setting the file register capacity. ( Page

444 Setting file registers) *3 This item is not displayed on the R00CPU, R01CPU, and R02CPU. *4 This item is not displayed for CPU modules for which the latch with the battery-less option cassette cannot be used.

Please note that the total of the capacity of each area (including the capacity of the local device area) should not exceed the capacity of the device/label memory ( Page 62 Hardware specifications). The total of the capacity of each area can be checked in "Device/Label Memory Area Capacity Setting".

When the capacity of the file storage area is changed, files (file register files) stored in the area are deleted, and therefore it is required to write file register files. Also, when files are stored in the CPU module, they must be read to other place before the capacity of the file storage area is changed and written back to the CPU module after the change.

"Device/Label Memory Area Setting" window 1. Set whether to use an extended SRAM cassette or battery-less option cassette in "Cassette Setting".

2. Set the capacity of each area in "Device/ Label Memory Area Capacity Setting".

Item Description Setting range Default Cassette Setting*3

Extended SRAM Cassette Setting When using an extended SRAM cassette, select the capacity of the cassette.

Not Mounted 1MB 2MB 4MB 8MB 16MB*1

Not Mounted

Battery-less Option Cassette Setting*1*4 Set whether to insert a battery-less option cassette.

Not Mounted Mounted

Not Mounted

Device/Label Memory Area Capacity Setting

Device Area Device Area Capacity

Sets the capacity of the device area to be used for global devices.

Page 128 Default capacity of each area

Page 128 Default capacity of each areaLabel Area Label Area Capacity Sets the capacity of the label area to be used

for global labels and local labels.

Latch Label Area Capacity

Sets the capacity of the latch label area to be used for latch type labels.

File Storage Area Capacity*2 Sets the capacity of the file storage area to be used for storing register files and others.

Device/Label Memory Area Capacity Setting Shows the device/label memory configuration.

8 MEMORY CONFIGURATION OF THE CPU MODULE 8.1 Memory Configuration 127

12

Default capacity of each area The default capacity of each area is as follows.

The capacity of the local device area to be set is obtained by deducting the total capacity of the device area, label area, latch label area, and file storage area from the total capacity of the device/label memory of each model. However, even if the total capacity of the device area and label area is smaller than the following, the capacity cannot be assigned to the local device area. (The area which is smaller than the following is the area not used.) R00CPU, R01CPU, R02CPU: 30K words R04CPU, R04ENCPU: 40K words R08CPU, R08ENCPU: 50K words R16CPU, R16ENCPU: 60K words R32CPU, R32ENCPU: 70K words R120CPU, R120ENCPU: 90K words

The setting range of the capacity of each area The following tables list the setting range of the capacity of each area on the device/label memory.* 1

The availability of an extended SRAM cassette varies depending on the CPU module used. For the availability, check the performance specifications of the extended SRAM cassette. ( Page 67 Extended SRAM Cassette) *1 The rest of other areas are automatically set as the capacity of the local device area.

R00CPU, R01CPU, R02CPU

R04CPU, R04ENCPU

Item R00CPU, R01CPU, R02CPU

R04CPU, R04ENCPU

R08CPU, R08ENCPU

R16CPU, R16ENCPU

R32CPU, R32ENCPU

R120CPU, R120ENCPU

Device area 30K words 40K words 40K words 40K words 40K words 40K words

Label area 30K words 30K words 40K words 50K words 90K words 110K words

Latch label area 2K words 2K words 2K words 2K words 4K words 4K words

Local device area 0K word 0K word 0K word 0K word 0K word 0K word

File storage area 64K words 128K words 512K words 768K words 1024K words 1536K words

Area Setting range of capacity of each area Device area 1 to 126K words

Label area 0 to 125K words

Latch label area 0 to 96K words

File storage area 0 to 96K words

Area Setting range of capacity of each area

Without an extended SRAM cassette

With an extended SRAM cassette (1MB)

With an extended SRAM cassette (2MB)

With an extended SRAM cassette (4MB)

With an extended SRAM cassette (8MB)

With an extended SRAM cassette (16MB)

Device area 2 to 200K words 2 to 712K words 2 to 1224K words 2 to 2248K words 2 to 4296K words 2 to 8392K words

Label area 0 to 198K words 0 to 710K words 0 to 1222K words 0 to 2246K words 0 to 4294K words 0 to 8390K words

Latch label area 0 to 160K words 0 to 672K words 0 to 1184K words 0 to 2208K words 0 to 4256K words 0 to 8352K words

File storage area 0 to 160K words 0 to 672K words 0 to 1184K words 0 to 2208K words 0 to 4256K words 0 to 8352K words

8 8 MEMORY CONFIGURATION OF THE CPU MODULE 8.1 Memory Configuration

8

R08CPU, R08ENCPU

R16CPU, R16ENCPU

R32CPU, R32ENCPU

R120CPU, R120ENCPU

To check which CPU modules can be used with extended SRAM cassettes, refer to the following. Page 67 Extended SRAM Cassette

Area Setting range of capacity of each area

Without an extended SRAM cassette

With an extended SRAM cassette (1MB)

With an extended SRAM cassette (2MB)

With an extended SRAM cassette (4MB)

With an extended SRAM cassette (8MB)

With an extended SRAM cassette (16MB)

Device area 2 to 594K words 2 to 1106K words 2 to 1618K words 2 to 2642K words 2 to 4690K words 2 to 8786K words

Label area 0 to 592K words 0 to 1104K words 0 to 1616K words 0 to 2640K words 0 to 4688K words 0 to 8784K words

Latch label area 0 to 544K words 0 to 1056K words 0 to 1568K words 0 to 2592K words 0 to 4640K words 0 to 8736K words

File storage area 0 to 544K words 0 to 1056K words 0 to 1568K words 0 to 2592K words 0 to 4640K words 0 to 8736K words

Area Setting range of capacity of each area

Without an extended SRAM cassette

With an extended SRAM cassette (1MB)

With an extended SRAM cassette (2MB)

With an extended SRAM cassette (4MB)

With an extended SRAM cassette (8MB)

With an extended SRAM cassette (16MB)

Device area 2 to 860K words 2 to 1372K words 2 to 1884K words 2 to 2908K words 2 to 4956K words 2 to 9052K words

Label area 0 to 858K words 0 to 1370K words 0 to 1882K words 0 to 2906K words 0 to 4954K words 0 to 9050K words

Latch label area 0 to 800K words 0 to 1312K words 0 to 1824K words 0 to 2848K words 0 to 4896K words 0 to 8992K words

File storage area 0 to 800K words 0 to 1312K words 0 to 1824K words 0 to 2848K words 0 to 4896K words 0 to 8992K words

Area Setting range of capacity of each area

Without an extended SRAM cassette

With an extended SRAM cassette (1MB)

With an extended SRAM cassette (2MB)

With an extended SRAM cassette (4MB)

With an extended SRAM cassette (8MB)

With an extended SRAM cassette (16MB)

Device area 2 to 1158K words 2 to 1670K words 2 to 2182K words 2 to 3206K words 2 to 5254K words 2 to 9350K words

Label area 0 to 1156K words 0 to 1668K words 0 to 2180K words 0 to 3204K words 0 to 5252K words 0 to 9348K words

Latch label area 0 to 1088K words 0 to 1600K words 0 to 2112K words 0 to 3136K words 0 to 5184K words 0 to 9280K words

File storage area 0 to 1088K words 0 to 1600K words 0 to 2112K words 0 to 3136K words 0 to 5184K words 0 to 9280K words

Area Setting range of capacity of each area

Without an extended SRAM cassette

With an extended SRAM cassette (1MB)

With an extended SRAM cassette (2MB)

With an extended SRAM cassette (4MB)

With an extended SRAM cassette (8MB)

With an extended SRAM cassette (16MB)

Device area 2 to 1690K words 2 to 2202K words 2 to 2714K words 2 to 3738K words 2 to 5786K words 2 to 9882K words

Label area 0 to 1688K words 0 to 2200K words 0 to 2712K words 0 to 3736K words 0 to 5784K words 0 to 9880K words

Latch label area 0 to 1600K words 0 to 2112K words 0 to 2624K words 0 to 3648K words 0 to 5696K words 0 to 9792K words

File storage area 0 to 1600K words 0 to 2112K words 0 to 2624K words 0 to 3648K words 0 to 5696K words 0 to 9792K words

8 MEMORY CONFIGURATION OF THE CPU MODULE 8.1 Memory Configuration 129

13

Data memory This memory is used to store the parameter file, device comment file, and/or the user's folder/file. Data such as the parameter file and the device comment files written by the engineering tool is stored in the "$MELPRJ$" folder. The "$MELPRJ$" folder is created after memory initialization. Note that the "$MELPRJ$" folder cannot be deleted. (Folders under the "$MELPRJ$" folder can be deleted.)

For details on how to create and delete user folders, refer to the following. GX Works3 Operating Manual

Precautions Do not delete or rename the folders or files being accessed or those being executed by a function.

Function memory This memory is temporarily used for the specific function. The following is the function that uses the function memory.

Also, data can be deleted or transferred to the data memory by using the special relay. ( Page 589 Drive information)

Precautions Do not delete or rename the folders or files being accessed or those being executed by a function.

Function Reference Data logging function (when "CPU built-in memory (function memory)" is selected for "Data storage destination memory")

Page 226 DATA LOGGING FUNCTION

/ $MELPRJ$

Parameter filesRoot directory

Any folder Any folder

Any file Any file

0 8 MEMORY CONFIGURATION OF THE CPU MODULE 8.1 Memory Configuration

8

Refresh memory This memory is used to store data used to refresh communication with the intelligent function module. ( Page 445 Refresh Data Register (RD))

CPU buffer memory This memory is used by the Ethernet function or in data communication between multiple CPUs. ( Page 642 Buffer Memory)

Signal flow memory This memory is used to memorize the execution status of the instruction in the last scan. The CPU module judges whether to execute a rising/falling edge execution instruction by referring to the signal flow memory.

The execution status of the last instruction is stored in the signal flow memory in two ways: executed or not executed. The instructions that refer to the signal flow memory judge whether to execute a rising/falling edge execution instruction depending on the input condition of the instruction and the execution status of the last instruction stored in the signal flow memory.

For instances of the function block, refer to the following. MELSEC iQ-R Programming Manual (Program Design)

The following shows the instructions that refer to the last execution status of the signal flow memory. Contact instruction: LDP, LDF, ANDP, ANDF, ORP, ORF, LDPI, LDFI, ANDPI, ANDFI, ORPI, and ORFI Association instruction: MEP, MEF Output instruction: SET F, RST F, PLS, PLF, FF Rising edge execution instruction: P (such as INCP and MOVP), SP., ZP., GP., JP., DP., MP.,

UDCNT1, UDCNT2, TTMR, STMR, RAMPQ, SPD, PLSY, PWM, MTR, SORTD(_U), DSORTD(_U), LEDR, DUTY, LOGTRG, LOGTRGR, TIMCHK, HOURM, DHOURM, PID, XCALL, SCJ

For a program, the same number of areas as steps of the program are assigned to the signal flow memory (for program). For a function, the signal flow memory is not assigned since the instructions that refer to the last execution status of the signal flow memory cannot be used in

the function. For a subroutine type function block, the same number of areas as instructions that refer to the signal flow memory in the function block are assigned to the

signal flow memory (for FB). Different areas are assigned to each instance. When the macro type function block is called from the subroutine type function block, the areas including the ones used for the macro type function block are assigned.

For a macro type function block, the same number of areas as the number of steps of the macro type function block are assigned to the signal flow memory (for program).

INCP wCount1

INCP wCount2

Signal flow memory

Executed

Not executed

8 MEMORY CONFIGURATION OF THE CPU MODULE 8.1 Memory Configuration 131

13

SD memory card This memory is used to store the folder/file created by a function using the SD memory card as well as the user's folder/file. The folder configuration is the same as the data memory. However, in the case of the SD memory card, the "$MELPRJ$" folder will be created when the SD memory card becomes available (when the SD memory card is mounted).

For details on how to insert or remove the SD memory card, refer to the following. Page 41 Inserting or Removing an Extended SRAM Cassette

How to forcibly disable the SD memory card with a special relay If the SD memory card is removed while the CPU module is powered on, data in the SD memory card may be corrupted. Use a special relay to forcibly disable access to the SD memory card without turning on and off the power. The following shows how to forcibly disable the SD memory card with a special relay.

1. Turn on SM606 (SD memory card forced disable instruction). After an instruction by SM606, and until SM607 changes, an instruction by the ON/OFF state change of SM606 is disabled. Note that after SM607 changes, an instruction by the ON/OFF state change of SM606 is enabled, and operation is performed based on the ON/OFF state of SM606.

2. Check that the CARD READY LED is off or SM607 (SD memory card forced disable status flag) is on.

3. Remove the SD memory card.

After the SD memory card is disabled, to cancel the disabled status, insert the SD memory card again and power off and on or reset the CPU module. When the SD memory card is inserted again, the CARD READY LED changes from flashing to on.

(1) Forced disable instruction by the ON state (2) Instruction to cancel forced disable status by the OFF state enabled

OFF ON

SM606

SM607

(2)

OFF ON

ON

(1)

(Instruction enabled by the SM606 status) (Instruction disabled by the SM606 status) (Instruction enabled by the SM606 status)

2 8 MEMORY CONFIGURATION OF THE CPU MODULE 8.1 Memory Configuration

8

Operation of each function accessing the SD memory card Disabling the SD memory card affects the operation of each function accessing the SD memory card. For the functions shown below, the following table shows the operations when the SD memory card forced disable instruction is executed during access to the SD memory card and when access is made to the SD memory card after the SD memory card is disabled.

*1 Same as the operation when the SD memory card is not inserted

Precautions Do not delete or rename the folders or files being accessed or those being executed by a function.

Precautions when forcibly disabling the SD memory card When forced disable operation with the SD CARD OFF button and forced disable operation by SM606 are executed

together, the operation executed earlier is enabled, and the operation executed later is disabled. For example, after the SD memory card is forcibly disabled with the SD CARD OFF button, when SM606 is turned on and off without removing the SD memory card, the disabled status of the SD memory card can be canceled. However, after forcibly disabling the SD memory card with the SD CARD OFF button, even by removing the SD memory card, turning on SM606, and inserting the SD memory card, the SD memory card is not enabled. To enable the SD memory card, after it is inserted again, SM606 must be turned off.

If this function is executed while an external device is writing a file to the SD memory card, writing of the file may fail. Cancel the SD memory card disable status, then write the file again.

Function being executed SD memory card forced disable instruction executed during access to the SD memory card

Access made to the SD memory card after the SD memory card is disabled

Boot operation

Access to device comment or label in SD memory card

Device/label initial value operation at status change from STOP to RUN

The SD memory card becomes disabled after the executed function is completed.

An error occurs in the CPU module.*1

Access to SD memory card by engineering tool, SLMP, FTP function

The function is responded to with an error. The function is responded to with an error.

Instruction to access SD memory card The SD memory card becomes disabled after the instruction is completed.

The instruction is completed with an error.

CPU module data backup/restoration function When the processing for the file being backed up/ restored is completed, the SD memory card is disabled, the executed function is completed with an error, and the error cause is stored in the special register.

The error cause is stored in the special register.

iQ Sensor Solution data backup/restoration function

After the backup or restore operation is completed, the SD memory card is disabled.

The function is responded to with an error.

File transfer function (FTP client) When the processing for the file during file transfer execution is completed, the SD memory card is disabled, the file transfer function instruction is completed with an error, and the error cause is stored in the completion status.

The file transfer function instruction is completed with an error, and the error cause is stored in the completion status.

8 MEMORY CONFIGURATION OF THE CPU MODULE 8.1 Memory Configuration 133

13

8.2 File Size Unit in Memory The minimum unit of capacity for storing a file in the memory is referred to as the file size unit (cluster size).

File size unit based on memory area

*1 The file size unit (cluster size) differs depending on the firmware version and production information of the CPU module. ( Page 700 Added and Enhanced Functions)

Data is written in the unit of the file size (cluster size). For example, when 464 bytes of CPU parameter is written to the data memory on R04CPU, it is written as 1024 bytes of data because the file size unit of the data memory is 1024 bytes.

File size unit of each SD memory card

CPU module File size unit

Program memory Device/label memory Data memory Function memory R00CPU, R01CPU, R02CPU 4 bytes 512 bytes 1024 bytes

R04CPU, R04ENCPU 8192/2048 bytes*1

R08CPU, R08ENCPU 2048 bytes

R16CPU, R16ENCPU 4096 bytes

R32CPU, R32ENCPU 8192 bytes

R120CPU, R120ENCPU 16384 bytes

SD memory card File size unit NZ1MEM-2GBSD 32K bytes

NZ1MEM-4GBSD

NZ1MEM-8GBSD

NZ1MEM-16GBSD

4 8 MEMORY CONFIGURATION OF THE CPU MODULE 8.2 File Size Unit in Memory

8

8.3 Memory Operation Initialization and value clear Each memory can be initialized and cleared to zero by using the engineering tool. For details on the operation method, refer to the following. GX Works3 Operating Manual

If the power goes off during initialization or zero clear, the memory is left in the state of that point, and it is necessary to re-execute the memory operation.

Memory initialization during execution of another function No memory can be initialized during execution of the following functions. Check that the following functions are not being executed and then initialize the memory. CPU module data backup/restoration function iQ Sensor Solution data backup/restoration function

Clearing values during execution of another function CPU module data backup/restoration function During execution of the CPU module data backup/restoration function, devices, labels, file register areas, and latch areas cannot be cleared to zero. Check that the CPU module data backup/restoration function is not being executed and then clear devices, labels, file register areas, and latch areas to zero.

iQ Sensor Solution data backup/restoration function During execution of the iQ Sensor Solution data backup/restoration function, file register areas cannot be cleared to zero. Check that the iQ Sensor Solution data backup/restoration function is not being executed and then clear file register areas to zero.

Items to be specified in the engineering tool Target Initialization Data memory Deletes all the folders and files in the program memory and data

memory.

Device/label memory Deletes all the files in the file storage areas in the device/label memory. The battery-less option cassette is initialized.

SD memory card Deletes all the folders and files in the SD memory card.

Value clear Device, label Zero clear Excluding devices and labels with latch specified, clears the following to zero: X, Y, M, B, F, SB, V, S, T, ST, LT, LST, C, LC, D, W, SW, FX, FY, FD, Z, LZ, RD, and all labels (including module labels).

Zero clear (including Latches (1) and (2)) Including devices and labels with latch specified, clears the following to zero: X, Y, M, B, F, SB, V, S, T, ST, LT, LST, C, LC, D, W, SW, FX, FY, FD, Z, LZ, RD, and all labels (including module labels).

File register Zero clear All files Clears the contents of all the file registers to zero.

File specification Clears only the contents of the specified file register(s) to zero.

Zero clear excluding Latch (2) Clears the file registers other than Latch (2) to zero.

Device / label / file register latch clear Clears devices, labels, and file registers other than Latch (2) to zero.

8 MEMORY CONFIGURATION OF THE CPU MODULE 8.3 Memory Operation 135

13

8.4 Files This section lists the files used by the CPU module.

File types and storage memory This table lists the types of files, which are generated by parameter settings and functions in use, as well as their storage memory. : Can be stored (Mandatory), : Can be stored, : Cannot be stored

File type CPU built-in memory SD memory card

File name and extensionProgram

memory Device/label memory

Data memory

Drive 0 Drive 3 Drive 4 Drive 2 Program *4 *4 ANY_STRING.PRG

FB file *4 *4 ANY_STRING.PFB

CPU parameter CPU.PRM

System parameter SYSTEM.PRM

Module parameter UNIT.PRM

Module extension parameter*7 UEXmmmnn.PRM*1

UEXmmm00.PPR*5

Memory card parameter MEMCARD.PRM

Device comment ANY_STRING.DCM

Initial device value ANY_STRING.DID

Global label setting file GLBLINF.IFG

Initial label value file

Initial global label value file

GLBLINF.LID

Initial local label value file

PROGRAM_NAME.LID

File register *3 ANY_STRING.QDR

Event history EVENT.LOG EVEN2.LOG

Device data storage file *3 DEVSTORE.QST

General-purpose data ANY_STRING.CSV/BIN

Data logging setting file

Common setting file

LOGCOM.LCS

Individual setting file

LOGnn.LIS*2

Memory dump setting file *3 MEMDUMP.DPS

Remote password 00000001.SYP

Firmware update file *3 mmmm_vv.SYF

Firmware update prohibited file *3 FWUPDP.SYU

Faulty database check file ErrorDB.txt

Database path file dbmaintainpath.txt

System file for backing up CPU module data

$BKUP_CPU_INF.BSC

Backup data file for backing up CPU module data

BKUP_CPU.BKD

Device/label data file for backing up CPU module data

BKUP_CPU_DEVLAB.BKD

System file for the iQ Sensor Solution data backup/restoration function

$BKUP_UNIT_INF.BSI

Backup data file for the iQ Sensor Solution data backup/restoration function

Depends on a connected device.QBR*6

ODBC server setting file netserver.cfg

Slave station parameter file *9 *9 SLAVEmmmnnnxxxx.NSP*8

6 8 MEMORY CONFIGURATION OF THE CPU MODULE 8.4 Files

8

*1 mmm represents the start I/O number (first three digits in four-digit hexadecimal representation) of each module. For the CPU module, it will be 3FFH. Also, nn represents the serial number (two-digit hexadecimal representation) of module extension parameter files or module-specific backup parameter files of each module.

*2 nn corresponds to the setting number and is 01 through 10. *3 Can be stored but cannot operate as a function. *4 When this file is stored in the built-in memory of the CPU module, it is divided into program memory and data memory and stored. (

Page 142 Configuration of a program file) *5 The module extension parameter for the protocol setting is a file for storing protocol setting information in the predefined protocol

support function. *6 This file name depends on the connection type of the iQ Sensor Solution data backup/restoration function. For the file name, refer to the

following. iQ Sensor Solution Reference Manual

*7 The parameter cannot be written to the CPU modules on other stations via MELSECNET/H of the Q series. *8 mmm represents the start I/O number (first three digits in four-digit hexadecimal representation) of the master station of CC-Link IE TSN,

nnn represents the number of units in network configuration setting, and xxxx represents the serial number (four-digit hexadecimal representation) of the parameter.

*9 Up to 1024 parameters can be stored. *10 For files that support the Web server function, refer to the following.

MELSEC iQ-R Ethernet User's Manual (Application)

Recording setting file RECCFGn.RSI

User Web page file Files that support the Web server function*10

File type CPU built-in memory SD memory card

File name and extensionProgram

memory Device/label memory

Data memory

Drive 0 Drive 3 Drive 4 Drive 2

8 MEMORY CONFIGURATION OF THE CPU MODULE 8.4 Files 137

13

File operation available The following lists the file operations which can be executed to each file in the CPU module by external devices. : Available, : N/A

File type Operation from engineering tool Operation with SLMP and FTP server function

Operation via instruction*1

Write Read Delete Write Read Delete Write Read Program *2*7 *4 *3*6 *3*6

FB file *2*7 *4 *3*6 *3*6

Parameter *4 *4 *3*6 *3

Device comment *4 *3*6 *3*6

Initial device value *4 *3*6 *3*6

Global label setting file *7*8*9 *9 *4 *3*6 *3*6

Initial label value file

Initial global label value file

*4 *3 *3*6

Initial local label value file

*4 *3 *3*6

File register *4 *3

Event history *10 *10

Device data storage file *3*6 *3*6

General-purpose data *4

Data logging setting file

Common setting file

*5 *5 *5

Individual setting file

*5 *5 *5

Memory dump setting file *4

Remote password *4 *4 *3*6 *3*6

Faulty database check file *4

Database path file

Firmware update file *4

Firmware update prohibited file *4

Module-specific backup parameter *3 *3

System file for backing up CPU module data

Backup data file for backing up CPU module data

*4

Device/label data file for backing up CPU module data

*4

System file for the iQ Sensor Solution data backup/restoration function

Backup data file for the iQ Sensor Solution data backup/restoration function

*4

ODBC server setting file

Slave station parameter file *4

Recording setting file *11 *4 *11 *11

User Web page file *12 *12 *12

8 8 MEMORY CONFIGURATION OF THE CPU MODULE 8.4 Files

8

*1 Modification of data in files, such as read/write from/to file register and execution of the FWRITE/FREAD instruction *2 When the CPU module is in the STOP state, the file operation is performed by writing the FB file to the programmable controller. In the

RUN state, it is performed by online change. Note that only programs and FB files that are registered in the parameter can be written when the operating status of the CPU module is RUN.

*3 Available only when the CPU module operation status is STOP/PAUSE. A communication error occurs when operated in the RUN state. *4 Available only when the CPU module operation status is STOP/PAUSE. When a program tries to perform memory operation while the

CPU module is RUN, the operation is continued after the operation status is changed through remote STOP. *5 Operation on CPU Module Logging Configuration Tool. *6 When the operation target is the SD memory card, the operation can be performed even while the CPU module is RUN. *7 The availability of the online change (the file batch online change of FB files and the global label setting file) differs depending on the

model and firmware version. For supported models and firmware versions, refer to the following. Page 700 Added and Enhanced Functions For executable conditions of the file batch online change, refer to the following. GX Works3 Operating Manual When the modules that do not support the online change mentioned above are used, the operation that is performed in the RUN state continues after the operating status is changed by the remote STOP function.

*8 If the global label that can be accessed from the external device is set and the CPU module is in the RUN state, only read operation is available.

*9 When the CPU module is in the RUN state, the file operation is available only when the target file is already written to the CPU module. *10 When the recording function is in the process of saving, the file operation is not available. *11 When the recording function is in one of the following states, the file operation is not available.

Preparing Operating Save trigger established Saving

*12 For supported models and firmware versions, refer to the following. MELSEC iQ-R Ethernet User's Manual (Application)

8 MEMORY CONFIGURATION OF THE CPU MODULE 8.4 Files 139

14

File size The following table lists the size of files that can be stored in the CPU module.

File type File size Program Approx. 4050 bytes minimum (only the END instruction + 500 steps reserved for online program

change)

FB file Approx. 4900 bytes minimum (non-processing FB + 500 steps reserved for online program change)

CPU parameter 744 bytes minimum

System parameter 112 bytes minimum

Module parameter Differs depending on the module used. For example, the size is 1036 bytes at minimum when the Ethernet function is used.

Module extension parameter Differs depending on the module used. For example, the size is 65572 bytes when the predefined protocol support function is used with the Ethernet function.

Module-specific backup parameter Differs depending on the module used.

Memory card parameter 124 bytes minimum

Device comment 220 bytes minimum (when a device comment with 20 characters is set in a device)

Initial device value Approx. 140 bytes minimum (when the initial value of a word device is set)

Global label setting file Approx. 660 bytes minimum (when a word-type global label is set)

Initial label value file Initial global label value file Approx. 140 bytes minimum (when the initial value of a word-type global label is set)

Initial local label value file

File register file 2048 bytes minimum (when the setting capacity is 1K words)

Event history 1024 bytes minimum (when the setting capacity is 1K bytes (default setting is 131072 bytes))

Device data storage file 2048 bytes minimum (when the setting capacity is 1K words)

General-purpose data The size differs depending on the size of the file to be written.

Data logging setting file Common setting file 142 bytes (When the setting is configured so that one-word data is collected in a binary file at each scan in continuous logging)

Individual setting file 1192 bytes (When the setting is configured so that one-word data is collected in a binary file at each scan in continuous logging only for setting No.1)

Memory dump setting file 1224 bytes (when the save file name is "MEMDUMP_00")

Remote password 224 bytes minimum

Firmware update file 6816338 bytes minimum

Firmware update prohibited file 92 bytes minimum

Faulty database check file Total number of characters in the file path 2 bytes + number of databases 4 bytes

Database path file Total number of characters in the file path 2 bytes + number of databases 4 bytes

System file for backing up CPU module data 20 + 12 + ((N1 34) + (N2 34) + (N3 34)) + M + 8 bytes N1: Number of target drives N2: Number of target files N3: Number of target folders M: Total name size of target files/folders (bytes) (including ".", extensions, but no drive symbols)

Backup data file for backing up CPU module data When the data logging setting has been registered: 30608 bytes When the data logging setting has not been registered: 30200 bytes

Device/label data file for backing up CPU module data When local devices are not set 20 + 20 + (N1 142) + 16 + (N2 134) + (16 + (162 + (N3 18) + 1087104 + M1)) + 28 + M3 + M4

+ M5 + 8 bytes*1

When local devices are set 20 + 20 + (N1 142) + 16 + (N2 134) + (16 + (162 + (N3 18) + 1087104 + M1)) + (16 + N1 (8

+ ((N4 18) + M2))) + 28 + M3 + M4 + M5 + 8 bytes*1

N1: Number of programs N2: Number of file register files N3: Number of set device types (excluding SM, SD, FX, FY, FD, X, Y, and G/HG) N4: Number of local device settings (Number of device types) M1: Total size of set devices (bytes) (excluding SM, SD, FX, FY, FD, X, Y, and G/HG) M2: Total size of local devices (bytes) M3: Module label size (bytes) M4: Label area size (bytes) M5: Latch label area size (bytes)

System file for the iQ Sensor Solution data backup/ restoration function

CC-Link 36 + 20 N bytes (N: No. of devices supporting iQSS whose data has successfully been backed up) Built-in Ethernet 52 + M bytes (M: Backup data file name size*1) The file name size differs depending on the device supporting iQSS.

0 8 MEMORY CONFIGURATION OF THE CPU MODULE 8.4 Files

8

*1 Up to 3 bytes are added to the total file size so that the size will be a multiple of 4 bytes. *2 S4 is added only when local devices are used. *3 When the number of device points that is assigned to local devices is 0, N5 is 0.

When the CPU module versions are different, a program which can be written to a CPU module with a certain version may not be written to the one with another version due to overcapacity. In this case, delete the steps reserved for online program change (default: 500 steps) and write the program to the CPU module. GX Works3 Operating Manual

Backup data file for the iQ Sensor Solution data backup/restoration function

The size differs depending on the device supporting iQSS.

ODBC server setting file 236 bytes (when the IP address of the CPU module is 192.168.3.39)

Slave station parameter file The size differs depending on the slave station used.

Recording setting file 920 bytes (when only one recording setting (setting No.1) is made and the settings are configured as follows) Recording Period Setting: "Recording Method" is set to "File Saving Trigger Only", "Saving Period

Before Trigger" is set to 30 seconds, and "Saving Period After Trigger" is set to 5 seconds. Device/Label Sampling Target Setting: "Specify Device/Label in batch" is not set and only M0 (32

words) is set in "Device Individual Specification". Sampling Interval Setting: "Each Scan" File Saving Trigger Setting: None Saving Path Setting: Not changed Program: REC only (The number of texts for the file name is three.) Device comment: Common device comments FB/FUN: None

File type File size

8 MEMORY CONFIGURATION OF THE CPU MODULE 8.4 Files 141

14

Configuration of a program file The following figure shows the configuration of a program.

Configuration of a program This file consists of a file header, execution program, reserved area for online change, and program restoration information.

When the program is stored in the CPU module, file header, execution program, and reserved area for online change are allocated to the program memory. Program restoration information is allocated to the data memory. The following table shows the destination memory to which each area is allocated when a program is stored in the CPU module.

FB file This file consists of a file header, execution program, reserved area for online change, and program restoration information.

When an FB file is stored in the CPU module, the file header, execution program, and reserved area for online change are allocated to the program memory. Program restoration information is allocated to the data memory. The destination memory to which each area is allocated when an FB file is stored in the CPU module is the same as that for programs.

Area Destination memory Description File header Program memory This area stores the configuration of the file, and the labels and information of FBs used in the

program. The size differs depending on the created program.

Execution program This area stores the execution program of the created program.

Reserved area for online change This area is used when the online program change which increases the number of steps is executed (default: 500 steps (2000 bytes)). At writing to the programmable controller or at online ladder block change, the capacity of the area can be changed from the engineering tool.

Program restoration information Data memory This area stores information required for reading the program from the programmable controller.

Program configuration

File header

Execution program

Reserved area for online change

Program restoration information

The size changes depending on the created program.

The capacity can be set from an engineering tool (Default: 500 steps).

FB file configuration

File header

Execution program

Reserved area for online change

The size changes depending on the created program.

The capacity can be set from an engineering tool (Default: 500 steps).

Program restoration information

2 8 MEMORY CONFIGURATION OF THE CPU MODULE 8.4 Files

PA R

T 6

PART 6 FUNCTIONS

This part consists of the following chapters.

9 FUNCTION LIST

10 CLOCK FUNCTION

11 WRITING DATA TO THE CPU MODULE

12 RAS FUNCTIONS

13 REMOTE OPERATION

14 BOOT OPERATION

15 MONITOR FUNCTION

16 TEST FUNCTION

17 DATA LOGGING FUNCTION

18 DEBUG FUNCTION

19 DATABASE FUNCTION

20 PID CONTROL FUNCTION

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION

22 MULTIPLE CPU SYSTEM FUNCTION

23 SECURITY FUNCTION

24 SEQUENCE SCAN SYNCHRONIZATION SAMPLING FUNCTION

25 ROUTING SETTING

26 FIRMWARE UPDATE FUNCTION

143

14

9 FUNCTION LIST The following table lists the functions of the CPU module.

Some functions have restrictions on the firmware version and the production information of the CPU module used or the version of the engineering tool used. ( Page 700 Added and Enhanced Functions)

Function Description Availability Reference

R00 CPU

R01/ R02 CPU

Rn(EN)CPUs other than the left ones

Constant scan Repeatedly runs a program while retaining the scan time constant.

Page 73 Constant scan

Device/label access service processing setting

Sets the time or execution timing of the device/label access service processing performed in the END processing in parameter.

Page 75 Device/label access service processing setting

Interrupt function

Multiple interrupt function

When an interrupt occurs while an interrupt program triggered by another cause is running, stops the program if its priority is lower than that of the new interrupt, and runs the higher-priority program whenever its execution condition is satisfied.

Page 114 Multiple interrupt function

Output mode setting when the status changed from STOP to RUN

Sets the output (Y) status when the operating status of the CPU module is switched from STOP to RUN.

Page 122 Output mode at operating status change (STOP to RUN)

Device/label memory area setting

Sets the capacity of each area in the device/label memory. Page 127 Device/label memory area setting

Internal buffer capacity setting

Sets the capacity of the area (internal buffer) used by the system to temporarily store the results of data logging and memory dump processing.

Page 265 Internal buffer capacity setting

SD memory card forced disable

Forcibly disables an access to the SD memory card without powering off the system even when the function that accesses the SD memory card is being executed.

Page 132 How to forcibly disable the SD memory card with a special relay

Clock function Manages time for the system functions such as time stamps for the event history function and date information for the data logging function.

Page 148 CLOCK FUNCTION

Writing data to the CPU module

Writing data to the programmable controller

Writes the specified data of the project with the engineering tool to the memory of the CPU module.

Page 155 Writing Data to the Programmable Controller

GX Works3 Operating Manual

Online change (ladder block)

Writes the part of a program edited on the ladder editor using the engineering tool to the running CPU module in units of ladder blocks. Edited contents spanning multiple files or multiple portions can be written to the CPU module at once.

Page 155 Online change (ladder block)

GX Works3 Operating Manual

Online change (files)

Writes programs and other data to the running CPU module in units of files.

Page 159 File batch online change

GX Works3 Operating Manual

4 9 FUNCTION LIST

9

RAS function

Scan monitoring function

Detects a hardware failure or program error by monitoring that the END processing is performed within a set scan time.

Page 166 Scan Monitoring Function

Self-diagnostics function

Self-diagnoses the CPU module to see whether an error exist or not.

Page 168 Self- Diagnostics Function

FB hierarchy information

Displays the FB hierarchy information of the function block with an error in the "Module Diagnostics" window.

GX Works3 Operating Manual

Error clear Batch-clears all the continuation errors being detected. Page 174 Error Clear

Event history function

Collects operations executed and errors detected from the modules, and saves them in the CPU module. The saved logs can be checked in chronological order.

Page 177 Event History Function

Program cache memory auto recovery function

Automatically detects and recovers the data stored in the program cache memory of the CPU module at the time of program execution if the data is overwritten due to the factors such as excessive electrical noise.

Page 186 Program Cache Memory Auto Recovery Function

Remote operation Remotely controls the operating status of the CPU module without switch operation.

Page 187 REMOTE OPERATION

Boot operation Transfers files in the SD memory card to the built-in memory of the CPU module when the CPU module is powered off and on or reset.

Page 191 BOOT OPERATION

Monitor function

Circuit monitor Checks the status of a running program on the program editor.

GX Works3 Operating Manual

Device/buffer memory batch monitor

Monitors values in devices and buffer memory using the engineering tool connected.

GX Works3 Operating Manual

Watch Registers devices and labels, and checks the current values.

GX Works3 Operating Manual

Program monitor list

Monitors the execution time of each program and the number of executions using the engineering tool connected.

GX Works3 Operating Manual

Interrupt program monitor list

Monitors the number of executions of interrupt programs using the engineering tool connected.

GX Works3 Operating Manual

Real-time monitor function

Monitors the data in the specified device of the CPU module at a specified interval or at a desired timing in real time.

GX Works3 Operating Manual

Scan time measurement

Measures the processing time of the set program section using the engineering tool.

Page 197 Scan Time Measurement

GX Works3 Operating Manual

Scan time clear Clears values of the scan time at a desired timing without stopping the CPU module.

GX Works3 Operating Manual

Specified program monitor

Checks (monitors) device/label values in the program specified by the engineering tool on the program editor and changes current values.

Page 202 Specified Program Monitor

GX Works3 Operating Manual

Test function

External input/ output forced on/ off function

Forcibly turns on/off the external input/output from the engineering tool.

Page 204 External Input/Output Forced On/ Off Function

GX Works3 Operating Manual

Device test with execution condition

Changes a device value for the specified step of a program, using the engineering tool.

Page 212 Device Test with Execution Conditions

GX Works3 Operating Manual

Data logging function Collects data at a specified interval or a desired timing, and stores them as a file.

Page 226 DATA LOGGING FUNCTION

CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series)

Function Description Availability Reference

R00 CPU

R01/ R02 CPU

Rn(EN)CPUs other than the left ones

9 FUNCTION LIST 145

14

Recording function Saves the device/label data set in the engineering tool into an SD memory card in the recorder module at the specified timing.

MELSEC iQ-R System Recorder User's Manual (Startup)

MELSEC iQ-R System Recorder User's Manual (Application)

Co-recording function Synchronizes the timing of data saving between modules that support this function.

MELSEC iQ-R System Recorder Co-recording Function Reference Manual

Debug function

Memory dump function

Saves the data in the devices of the CPU module at a desired timing.

Page 304 Memory Dump Function

SFC function Executes programs written in sequential function chart (SFC).

MELSEC iQ-R Programming Manual (Program Design)

Database function

Database access instruction

Adds, updates, obtains, or deletes data with respect to the tabular data such as product and production information managed as databases on a SD memory card of the CPU module.

Page 318 Database Access Instruction

MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/ Function Blocks)

CPU module database access (from external device) function

Operates a database, that is built in an SD memory card inserted into the CPU module, through the Ethernet port of the CPU module from an application on a personal computer.

Page 324 CPU Module Database Access (from External Device) Function

PID control function Performs PID control by using the PID operation instruction.

MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/ Function Blocks)

CPU module data backup/ restoration function

Backs up data such as program files, parameter files, and device/label data files in a CPU module to an SD memory card. The data backed up can be restored as necessary.

Page 346 CPU MODULE DATA BACKUP/ RESTORATION FUNCTION

Multiple CPU system function

Out-of-group I/O fetch

Enables loading the input and output data of non-controlled modules.

Page 369 Out-of-group I/O Fetch

Multiple CPU synchronized startup

Synchronizes the startup of CPU modules in a multiple CPU system so that operations of all the CPU modules start at the unified time.

Page 373 Synchronous startup setting

Data communications between CPU modules

Communicates data between CPU modules in a multiple CPU system.

Page 378 Data Communication Between CPU Modules

Multiple CPU synchronous interrupt

Executes an interrupt program at the fixed communication timing set in parameter.

Page 397 Multiple CPU Synchronous Interrupt

Function Description Availability Reference

R00 CPU

R01/ R02 CPU

Rn(EN)CPUs other than the left ones

6 9 FUNCTION LIST

9

Security function

Block password function

Prevents unauthorized access to programs (in units of POUs).

GX Works3 Operating Manual

Security key authentication function

Prevents unauthorized access to programs (in units of program files) or unauthorized execution of programs.

GX Works3 Operating Manual

File password function

Prevents unauthorized reading/writing of data from/to files. GX Works3 Operating Manual

IP filter function Identifies the IP address of external devices over Ethernet, and blocks access from an invalid IP address.

GX Works3 Operating Manual

MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

Remote password function

Restricts access via Ethernet that is taking a different route from specific communication routes.

GX Works3 Operating Manual

MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

Write-protect function for device data (from outside the CPU module)

Disables writing to devices from engineering tools and GOTs. Devices to be protected and their ranges can be set by the user. This prevents specified device data from being tampered with.

Page 401 Write-Protect Function for Device Data (from Outside the CPU Module)

Sequence scan synchronization sampling function

Collects data of the CPU module in synchronization with the sequence scan of the CPU module between each module.

Page 405 SEQUENCE SCAN SYNCHRONIZATION SAMPLING FUNCTION

Routing setting Sets the communication path required for transient communication to the stations on the different network.

Page 407 ROUTING SETTING

Label access setting from external device

Enables communications specifying the global label name from the GOT and external devices using SLMP.

Page 468 Label Access Setting from External Device

Latch function

Latch with a battery

Holds the device/label data in the CPU module even at power-off.

Page 473 Latch with Battery

Latch with a battery-less option cassette

Holds the device/label data in the CPU module without a battery when a battery-less option cassette is inserted into the CPU module.

Page 480 Latch with Battery-less Option Cassette

Initial device/label value setting

Sets the initial values of devices and labels used in the program directly (not via the program) to the devices, labels, and buffer memory areas of intelligent function modules.

Page 483 DEVICE/ LABEL INITIAL VALUE SETTINGS

Ethernet function Accesses the CPU module over Ethernet. Using this function, the CPU module can connect to MELSOFT products and GOTs, perform socket communications, and transfer FTP files.

MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

SLMP communication function

Enables accesses to devices/labels and remote operations from external devices other than the engineering tool by sending request messages using SLMP.

SLMP Reference Manual

Inter-module synchronization function

Controls multiple modules synchronously. MELSEC iQ-R Inter- Module Synchronization Function Reference Manual

CC-Link IE Field Network Basic function

Function available in CC-Link IE Field Network Basic CC-Link IE Field Network Basic Reference Manual

iQ Sensor Solution function Functions provided by iQ Sensor Solution iQ Sensor Solution Reference Manual

Firmware update function

Update using the engineering tool

Enables users to update firmware versions of CPU modules and intelligent function modules using the engineering tool.

MELSEC iQ-R Module Configuration Manual

Update using an SD memory card

Enables users to update firmware versions of CPU modules and intelligent function modules using an SD memory card.

MELSEC iQ-R Module Configuration Manual

Function Description Availability Reference

R00 CPU

R01/ R02 CPU

Rn(EN)CPUs other than the left ones

9 FUNCTION LIST 147

14

10 CLOCK FUNCTION The CPU module internally maintains clock data and uses it to manage time for the system functions such as time stamp for the event history and the data logging function.

10.1 Time Setting The clock continues operating with the internal battery of the CPU module while the CPU module is powered off or during power failure longer than the allowable momentary power failure time.

The R00CPU, R01CPU, and R02CPU continue the clock operation for 10 days without a battery in power failure state.

Clock data The following table lists the details of clock data in the CPU module.

*1 Data can be read from the S(P).DATERD instruction. ( MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks))

Changing the clock data The clock data can be changed in one of the following methods: Using the engineering tool Using SM/SD Using the instruction Automatic change using the SNTP server

When the clock data is changed, the following operation is performed: The millisecond value is reset to zero. Depending on the millisecond value immediately before the reset, the

second value can be rounded up. Considering that the second value can increase by one second maximum when the clock data is changed, configure the system.

Clock setting (Event code: 24000) is logged in the event history.

Using the engineering tool Choose "Set Clock" from the menu. ( GX Works3 Operating Manual)

Data name 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 Week 0: Sunday, 1: Monday, 2: Tuesday, 3: Wednesday, 4: Thursday, 5: Friday, 6: Saturday

1/1000 seconds*1 0 to 999

8 10 CLOCK FUNCTION 10.1 Time Setting

10

Using SM/SD After SM210 (Clock data set request) is tuned off and on, values stored in SD210 (Clock data) to SD216 (Clock data) are written to the CPU module. Once the write operation is finished, SM210 is turned on and off. If values in SD210 to SD216 are out of the effective range, SM211 (Clock data set error) turns on and the values in SD210 to SD216 are not written to the CPU module.

Using the instruction Use the DATEWR instruction to write the clock data to the CPU module. ( MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks))

Automatic change using the SNTP server The time of CPU module is automatically set by collecting clock data from the time information server (SNTP server) connected to the LAN at the specified timing. ( MELSEC iQ-R Ethernet User's Manual (Application))

Reading the clock data The clock data can be read in one of the following methods: Using SM/SD Using the instruction

Using SM/SD When SM213 (Clock data read request) is turned on, the clock data is read to SD210 to SD216.

Using the instruction Use the DATERD(P)/S(P).DATERD instructions to read the clock data from the CPU module. ( MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks))

Precautions on the clock data The following lists the precautions on the clock data.

When using the product for the first time Since the clock data is not set at the factory, be sure to set the correct data.

Modifying the clock data Even if a portion of the clock data is changed, be sure to write all the data to the CPU module again.

Range of the clock data The clock data must be written within the following range. Page 148 Clock data Even within the range, the clock function does not operate normally if data outside the clock range is written to the CPU module.

Ex.

Operating status of the CPU module when impossible date is set

Date Write operation to the CPU module CPU module operating status February 30 Executed An error is not detected.

32th of month 13 Not executed When the DATEWR instruction is executed, "Operation error" (error code: 3405H) is detected.

When SM210 is on, SM211 turns on.

10 CLOCK FUNCTION 10.1 Time Setting 149

15

10.2 Setting Time Zone The time zone used for the CPU module can be specified. Specifying the time zone enables the clock of the programmable controller to work in the local time zone.

[CPU Parameter] [Operation Related Setting] [Clock Related Setting]

Window

Displayed items

To reflect the time zone setting on the CPU module, the module must be restarted. If no parameter is set for the CPU module, it operates with "UTC+9".

On the multiple CPU system, the time zone setting of the CPU No.1 is used for other CPU modules. (the time zone setting of CPUs No.2 to 4 is not applied even when it is specified.)

Item Description Setting range Default Time Zone Sets the time zone used by the CPU module. UTC+13

UTC+12 UTC+11 UTC+10 UTC+9:30 UTC+9 UTC+8 UTC+7 UTC+6:30 UTC+6 UTC+5:45 UTC+5:30 UTC+5 UTC+4:30 UTC+4 UTC+3:30 UTC+3 UTC+2 UTC+1 UTC UTC-1 UTC-2 UTC-3 UTC-3:30 UTC-4 UTC-4:30 UTC-5 UTC-6 UTC-7 UTC-8 UTC-9 UTC-10 UTC-11 UTC-12

UTC+9

Comment Enters a comment for a time zone (e.g., name of the city). 32 characters or less

0 10 CLOCK FUNCTION 10.2 Setting Time Zone

10

10.3 Daylight Saving Time Function The daylight saving time function is used to adjust the CPU module time to daylight saving time. This function advances the CPU module time by one hour on the starting date of daylight saving time, and reverses the time by 1 hour on the ending date.

Ex.

If daylight saving time starts from 2.00 on the second Sunday in March, and ends at 2.00 on the first Sunday in November

Before executing the daylight-saving time function, check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

Daylight saving time setting Sets the starting date and ending date for daylight saving time.

[CPU Parameter] [Operation Related Setting] [Clock Related Setting] [Setting to Adjust Clock for Daylight Saving Time]

Window

01:59:59 01:00:00 01:00:01

01:00:0101:00:0000:59:59

01:59:59

01:59:59

03:00:00

02:00:00

03:00:01

02:00:01

(1) (2)

Daylight-saving time

Second Sunday in March

First Sunday in November

[Before adjustment]

[After adjustment]

10 CLOCK FUNCTION 10.3 Daylight Saving Time Function 151

15

Displayed items

With the multiple CPU system, the "Setting to Adjust Clock for Daylight Saving Time" for CPU No.1 is used for other CPU modules. (The "Setting to Adjust Clock for Daylight Saving Time" will not be valid for CPU Nos. 2 to 4.)

The same month cannot be specified for the start and end of the timing of the switch. February 29 cannot be specified directly. If specifying February 29, the date can be substituted by entering

"Last Date in February".

Timing of daylight saving time adjustment Daylight saving time is adjusted at the following times. ON the starting date and ending date of daylight saving time When the CPU module is powered on When the CPU module is reset

Item Description Setting range Default Adjust Clock for Daylight Saving Time Sets whether to enable the daylight saving time setting. Enable

Disable Disable

Start/End Time Specification Method Sets the timing of the switch to daylight saving time to specified week or specified date.

Specified week Specified date

Specified week

Week Start Month Sets the daylight saving time starting date. 1 to 12 3

Week 1st Week 2nd Week 3rd Week 4th Week The Last Week

2nd Week

Day of Week

Sunday Monday Tuesday Wednesday Thursday Friday Saturday

Sunday

Time 0:00 to 23:00 2:00

End Month Sets the daylight saving time ending date. 1 to 12 11

Week 1st Week 2nd Week 3rd Week 4th Week The Last Week

1st Week

Day of Week

Sunday Monday Tuesday Wednesday Thursday Friday Saturday

Sunday

Time 0:00 to 23:00 2:00

Date Start Month Sets the daylight saving time starting date. 1 to 12 3

Day 1 to 31, The Last Date 1

Time 0:00 to 23:00 2:00

End Month Sets the daylight saving time ending date. 1 to 12 11

Day 1 to 31, The Last Date 1

Time 0:00 to 23:00 2:00

2 10 CLOCK FUNCTION 10.3 Daylight Saving Time Function

10

Daylight saving time function operation check The daylight saving time function operation can be checked as follows.

Special relay SM217 (Daylight saving time status flag) can be used to check whether the date lies inside or outside the daylight saving time period. ( Page 579 List of Special Relay Areas)

Event history The history for the start and end of daylight saving time can be checked in the event history for the date set in "Setting to Adjust Clock for Daylight Saving Time" ( Page 563 Event List)

Operation of other functions using clock data during daylight saving time Functions using CPU module clock data operate as follows during the daylight saving time period.

Precautions This section describes precautions on the daylight saving time function. The clock data cannot be changed to data less than one hour from the starting time of the daylight saving time.

Furthermore, if the "Setting to Adjust Clock for Daylight Saving Time" for CPU No.1 in a multiple CPU system is enabled, it will not be possible to change the clock data to data less than one hour from the starting time of the daylight saving time for CPU modules for CPU Nos. 2 to 4.

For the period less than one hour from the starting time or less than one hour until the ending time of daylight saving time, the function that is triggered by time may not work or may work twice.

When the "Setting to Adjust Clock for Daylight Saving Time" is enabled, functions operate based on date information after adjustment for daylight saving time. For this reason, dates and times output by functions that uses clock data are reversed ((before adjustment) (after adjustment)) and therefore the order (No.) in which events occur and the sorting order for the date on which events occur may not match. Consequently, when checking output results in chronological order, sort not in the order for the date on which events occur, but in the order (No.) in which events occur.

Ex.

Event history

Since the time goes back one hour at No.00005 where the daylight saving time ends, the dates and times on which events occurred are reversed at the upper and lower side of the broken line ((time of new event history) < (time of old event history)).

Item Description Clock data reading Reads clock data following adjustment for daylight saving time.

Clock data writing Writes as clock data following adjustment for daylight saving time.

10 CLOCK FUNCTION 10.3 Daylight Saving Time Function 153

15

10.4 System Clock The system clock is turned on/off by the system or turns on/off automatically at the interval specified by the user.

Special relay used for system clock Special relay used for system clock are as follows ( Page 585 System clock)

Precautions SM409 to SM415 (System clock) start to measure the time before the CPU module is switched to RUN. Therefore, the time

from the first scan after the CPU module has been switched to RUN until switching of the on/off state of the system clock may not match the measurement time of the system clock.

The on/off status of SM409 to SM415 (System clock) changes even during execution of a program. For this reason, when one program has multiple processes that are performed based on the on/off status of the system clock, these processes are not performed in the execution order of the program. If these processes are required to be performed in the execution order of the program, write a program such that the on/off status of the system clock is transferred to an internal relay at the start of every scan and each processing is performed based on the status in the internal relay.

Special register used for system clock Special register used for system clock are as follows ( Page 614 System clock)

SM number Name SM400 Always On

SM401 Always Off

SM402 After RUN, ON for 1 scan only

SM403 After RUN, OFF for 1 scan only

SM409 0.01 second clock

SM410 0.1 second clock

SM411 0.2 second clock

SM412 1 second clock

SM413 2 second clock

SM414 2n second clock

SM415 2n millisecond 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

SM440 On only initial I44 execution after RUN

SM441 On only initial I45 execution after RUN

SD number Name SD412 One second counter

SD414 2n second clock setting

SD415 2n ms clock setting

SD420 Scan counter

4 10 CLOCK FUNCTION 10.4 System Clock

11

11 WRITING DATA TO THE CPU MODULE This chapter describes the functions relating to writing data to the CPU module.

11.1 Writing Data to the Programmable Controller This function writes data specified by the project of the engineering tool to the memory of the CPU module. For details, refer to the following. GX Works3 Operating Manual

11.2 Online Change The following table lists the types of the online change.

Online change (ladder block) This function writes the part of a program edited on the ladder editor using the engineering tool to the running CPU module in units of ladder blocks. Edited contents spanning multiple files or multiple portions can be written to the CPU module at once.

For details on the operating procedure of the online change (ladder block) on engineering tools, refer to the following. GX Works3 Operating Manual

Type Description Reference Online change Online change (ladder

block) Changes and writes a part of the program and data online. Page 155 Online change (ladder block)

GX Works3 Operating Manual

Online change (SFC block) Changes, adds, or deletes SFC blocks online. GX Works3 Operating Manual MELSEC iQ-R Programming Manual

(Program Design)

File batch online change Writes data in file units online. Page 159 File batch online change GX Works3 Operating Manual

(1) Portion edited in the engineering tool (2) The changed ladder block is written to the running CPU module. (3) The program contents in the program cache memory are changed. (4) After changing the program contents in the program cache memory, they are automatically transferred to the program memory.

X0

X1

X3

X4

X2 X10

X11

X13

X14

X12

X15 X5

Y30

SET M0

END

Y50

SET M10

END

(1)

(2)

(3) (4)

Program A Program B

Engineering tool

CPU module Inside the CPU module

Transfer

Program cache memory

Program memory (ROM)

11 WRITING DATA TO THE CPU MODULE 11.1 Writing Data to the Programmable Controller 155

15

Editable contents Within a program block, instructions and pointers (P, I) can be added, changed, or deleted. Also, for each program component, program blocks can be added, changed, or deleted. However, if the user try to edit a label, FB, or FUN, the following limitations are applied.

Editable contents within a program block To change or delete global label definition and global label, all the programs and FB files using them must match both on the engineering tool and in the CPU module.

Editable contents within FB definition To add or change instructions that refer to a local label or the signal flow memory, the size of the instructions cannot exceed

the reserved area capacity*1. The same applies to the standard function blocks and module function blocks because those function blocks also have local labels. For details, refer to the following.

To add a local label, all the programs and FB files referencing the FB file which stores the FB definition to be modified must match both on the engineering tool and in the CPU module.

For input and output labels (VAR_INPUT, VAR_OUTPUT, and VAR_IN_OUT) and public labels, to add, change, or delete subroutine type FB and FUN interface information*2, all the programs and FB files referencing the FB file storing the FB definition to modify must match both on the engineering tool and in the CPU module.

*1 Reserved area refers to the area used for adding or changing a local label or a local instance when a program is changed online. The area is 48 words for non-latch type local labels, 16 words for latch type labels, and 4 words for signal flow memory by default. The reserved area can be changed for each function block definition. ( GX Works3 Operating Manual)

*2 The subroutine type FB and FUN interface information means: All FB definition, FUN definitions, and their definition numbers contained in FB files Definition names The number of all input labels, and their data types The number of all output labels, and their data types The number of all I/O labels, and their data types The number of public local labels in FB definition and their data types The implementation method of FB definition

Editable contents within FUN definition For input and output labels (VAR_INPUT and VAR_OUTPUT), to add, change, or delete subroutine type FB and FUN interface information, all the programs and FB files referencing the FB file storing the FB definition to modify must match both on the engineering tool and in the CPU module.

Editable contents for each program component To add or delete FB or FUN definition to or from an FB file, all the programs and FB files referencing the target FB file must match both on the engineering tool and in the CPU module.

Range changeable in a single session The following shows the number of steps and number of ladder blocks which can be changed in a single session. Number of ladder blocks in a file: 64 blocks Maximum number of steps in a ladder block: 65535 steps Total number of steps for all blocks (steps before changes + steps after changes): 364K steps

Item Reference Precautions for adding a local label Precautions when local labels are added into the MELSEC iQ-R series function blocks (FA-A-0232)

Instructions that refer to the signal flow memory Page 131 Signal flow memory

6 11 WRITING DATA TO THE CPU MODULE 11.2 Online Change

11

Reserved area for online change Reserved area for online change can be set in a program file to address the online change (ladder block) which causes a change in the program file size. ( GX Works3 Operating Manual) In addition, if the changed program exceeds the program file capacity (including reserved area for online change) during the online change (ladder block), the reserved area for online change can be set again if there is space available in the program memory.

Required free space in the data memory If the data memory does not have enough free space when the online change (ladder block) is executed, an error occurs. The free space of the data memory required for the execution of the online change (ladder block) depends on the size of program files to be changed or the usage of labels.

*1 When the setting of [Convert] Online Program Change] [Write Program Restore Information] is "Write with Execution Program", the required free space is equal to the size of the program restoration information.

The size of the program restoration information can be checked from the memory capacity calculation of the engineering tool.

[Tool] [Confirm Memory Size (Offline)]

Ex.

The following table lists required free space of the data memory (size of program restoration information) for the online change (ladder block) in the R120CPU with a firmware version "30" or earlier.

Online change (ladder block) during the boot operation When the online change (ladder block) is performed while booting from the SD memory card, the corresponding files on the booting SD memory card can also be changed.

CPU module Firmware version Required data memory space R00CPU, R01CPU, R02CPU All firmware versions Total increased size of the relevant program

restoration information*1 R04CPU, R08CPU, R16CPU, R32CPU, R120CPU R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, R120ENCPU

"31" or later

"30" or earlier Size of the program restoration information

Target program of online change (ladder block)

Required free space in the data memory

When labels are not used When labels are used (200 global labels and 200 local labels are used)

Ladder program of 1K steps Approx. 20K bytes Approx. 40K bytes

Ladder program of 10K steps Approx. 80K bytes Approx. 140K bytes

Ladder program of 100K steps Approx. 550K bytes Approx. 1000K bytes

11 WRITING DATA TO THE CPU MODULE 11.2 Online Change 157

15

Setting the initial value for registering/changing label definition The initial value used when registering/changing label definition can be set. ( GX Works3 Operating Manual)

Initial value setting availability Indicates whether or not the initial value can be set when adding or changing a label. : Available, : Conditionally available, : Not available

*1 The initial value can be set only when a new area is assigned again. *2 A different initial value can be set for each instance. *3 Since the local label in FUN definition is an undefined value, initialize it by a program in the FUN definition before using it in a program.

When using GX Works3 version 1.000A When the label definition (the initial value or any other value) is changed, write the initial label value file to

the CPU module after the online change (ladder block). Otherwise, an error occurs when the CPU module is powered off and on or reset, or the module operating status is changed from STOP to RUN.

To clear all the initial values, delete the initial label value files in the CPU module. If the boot operation is being performed, the initial label value files are stored on the SD memory card. Delete the initial label value files on the SD memory card, and also delete the files set in the module card parameters ("Boot File Setting"). Otherwise, an error occurs when the CPU module is powered off and on or reset, or the module operating status is changed from STOP to RUN.

Label type Label addition Label change Program block Global label *1

Local label *1

FB definition Local label *2 *1

FUN definition Local label *3 *3

8 11 WRITING DATA TO THE CPU MODULE 11.2 Online Change

11

File batch online change This function writes programs and other data to the running CPU module in units of files. For the operating procedure and the execution condition of the file batch online change, refer to the following. GX Works3 Operating Manual

Writing FB files and the global label setting file The file batch online change of FB files and the global label setting file is available depending on the model and firmware version of the CPU module. ( Page 700 Added and Enhanced Functions) When executing the file batch online change of FB files and the global label setting file, configure the setting of the write target file described below before system operation. However, the setting is not required when the R00CPU, R01CPU, or R02CPU is used.

Setting of the file to be written 1. Check that SM388 (File batch online change operation setting status) is off.

2. Set "AFBFH" to SD384 (System operation setting).

3. Turn off and on SM384 (System operation setting request). SM384 automatically turns off. If writing has failed, SM385 (System operation setting error) turns on and an error is stored in SD385 (System operation setting error cause).

4. Check that SM385 is off, and turn off or reset the CPU module.

5. SM388 turns on.

This setting requires powering off the system or resetting the CPU module. For this reason, configure this setting before system operation when executing the file batch online change of FB files and the global label setting file.

If the file batch online change is executed after this setting is configured (while SM388 is on), the scan time may increase compared with the case when the file batch online change is executed before this setting is configured (while SM388 is off).

Procedure for clearing the setting (how to reset the write target file setting) 1. Check that SM388 (File batch online change operation setting status) is on.

2. Set "AFB0H" to SD384 (System operation setting).

3. Turn off and on SM384 (System operation setting request). SM384 automatically turns off. If writing has failed, SM385 (System operation setting error) turns on and an error is stored in SD385 (System operation setting error cause).

4. Check that SM385 is off, and turn off or reset the CPU module.

5. SM388 turns off.

11 WRITING DATA TO THE CPU MODULE 11.2 Online Change 159

16

11.3 Precautions This section describes the precautions on writing data to the CPU module.

Prohibited operation (Turning off or resetting the CPU modules) When writing data to the programmable controller or executing the online change (ladder block), do not turn off or reset the

CPU module. Otherwise, the operation does not complete successfully. If doing so, write the data to the programmable controller again.

Do not power off and on or reset the CPU module when the program memory transfer is not completed. Otherwise, a stop error occurs.

Operation from engineering tools Operations cannot be executed simultaneously The file batch online change or online change (ladder block) cannot be executed simultaneously with the following operations from the engineering tool. Write to the programmable controller (excluding device, local device, global label, or local label data). File batch online change or online change (ladder block) Memory initialization

0 11 WRITING DATA TO THE CPU MODULE 11.3 Precautions

11

Writing during the program memory transfer When the program memory transfer starts during writing to the programmable controller or the online change from an engineering tool, writing to the programmable controller or the online change from another engineering tool can be executed. However, if this operation is performed, the progress of the ongoing transfer is reset to 0%. The transfer progress which is reset to 0% resumes when the program memory transfer from another engineering tool starts.

If the later program memory transfer (from the engineering tool 2) has completed with an error, the former program memory transfer (from the engineering tool 1) does not complete. In such a case, write the data again instead of powering off and on or resetting the CPU module.

Engineering tool 1 Engineering tool 2 Description The program memory transfer from the

engineering tool 1 starts.

Writing from the engineering tool 2 starts during the transfer from the engineering tool 1. The progress of the transfer from the engineering tool 1 is reset to 0%.

When the program memory transfer from the engineering tool 2 starts, the transfer from the engineering tool 1 progresses as well.

11 WRITING DATA TO THE CPU MODULE 11.3 Precautions 161

16

When the online change (ladder block) is used The following describes the precautions on using the online change (ladder block).

When deleting the OUT instruction which is on When deleting the OUT instruction (coil) which is not necessary for control, check that the OUT instruction is off before deleting it. If the OUT instruction is deleted without turning it off in advance, the output will be retained.

Program file not registered in program setting A program file which is not registered in parameter setting cannot be written.

Instructions which do not operate correctly The following table lists the instructions which do not operate correctly during the online change (ladder block) or writing data to the programmable controller. In the SFC program, these instructions do not operate correctly only when they are in active steps.

Rising instruction When a rising instruction exists within the range to be changed, the rising instruction will not be executed even if the execution condition (OFF to ON) is satisfied after completion of the online change (ladder block) or writing data to the programmable controller.

Instructions which do not operate correctly

Description

Rising instruction (PLS and P instructions)

When a rising instruction exists within the range to be changed, the rising instruction will not be executed even if the execution condition (OFF to ON) is taken at completion of online program change.

Falling instruction (PLF and F instructions)

When a falling instruction exists within the range to be changed, the falling instruction will not be executed even if the execution condition (ON to OFF) is taken at completion of online program change.

SCJ instruction If an SCJ instruction exists within the range to be changed and the execution condition is taken, the program will jump without waiting for a single scan.

STMR instruction If an STMR instruction exists within the range to be changed, the STMR instruction will be executed.

(1) The rising instruction will not be executed even if the execution condition is OFF to ON.

END END END0 0 0

OFF OFF

ON

OFF

OFF

OFF

OFF

OFF

OFF

ON

ON

ON

ON

ON

ON ON

X0

M0

X0

M0

X0

M0

(1)

[ PLS M0 ] X0

A A

OFF ON

Online change completion

1 scan Status of X0

2 11 WRITING DATA TO THE CPU MODULE 11.3 Precautions

11

Falling instruction When a falling instruction exists within the range to be changed, the falling instruction will not be executed even if the execution condition (ON to OFF) is satisfied after completion of the online change (ladder block) or writing data to the programmable controller.

SCJ instruction If an SCJ instruction exists within the range to be changed and the execution condition is satisfied at the completion of the online change (ladder block) or writing data to the programmable controller, the program will jump without waiting for a single scan.

(1) The falling instruction will not be executed even if the execution condition is OFF to OFF. (2) If a completion of the online program change and a timing of satisfying the execution condition (ON to OFF) occur simultaneously, the falling instruction will

not be executed.

(1) The program jumps to the specified pointer. (2) The program jumps to the specified pointer without waiting for a single scan.

END END END0 0 0

OFF OFF

ON OFF

OFF

OFF

OFF

ON

ON

ONON OFF

X0

M0

X0

M0

(1)

[ PLF M0 ] X0

A A

(2)

Online change completion

1 scan Status of X0

END END END0 0 0

OFF OFF

ON ON

[ SCJ P0 ] X0

A A

OFF ON

(1)

(1)

(2)

X0

X0

X0

OFF

ON

OFF

ON

OFF

ON

Online change completion

1 scanStatus of X0

SCJ instruction

SCJ instruction

SCJ instruction

11 WRITING DATA TO THE CPU MODULE 11.3 Precautions 163

16

STMR instruction If an STMR instruction exists within the range to be changed, the STMR instruction will be executed.

Initializing the last execution if the ladder at the online change (ladder block) has an FB call If a subroutine type FB is called within the changed ladder block, information of the last execution, such as the rising instruction and the falling instruction within the FB definition of the called subroutine type FB, is not initialized.

When the start-up of an interrupt program is delayed When the online change (ladder block) is performed, the start-up of the interrupt program may be delayed. Therefore, when the execution time is monitored for the interrupt program that uses the inter-module synchronous interrupt (I44) and multiple CPU synchronous interrupt (I45), an error may be detected in the CPU module. ( Page 169 Error detection setting)

Scan monitoring function during online changes Some sections are not targeted for the scan monitoring while online changes are being performed, and therefore a WDT error may not be detected if the scan time set in the scan time monitoring time (WDT) setting is exceeded.

Increase in scan time of the online change (ladder block) When global labels and local labels are added, or when there are many programs and FB files to be changed or many changes, the scan time may be increased by several dozen milliseconds.

Online change (ladder block) of when another function is performed The online change (ladder block) cannot be performed during execution of the following functions. Check that the following functions are not being executed and then perform the online change (ladder block). CPU module data backup/restoration function iQ Sensor Solution data backup/restoration function

(1) The STMR instruction functions because the STMR instruction is included in the ladder block where the online change has been executed. (2) The STMR instruction does not function because the STMR instruction is not included in the ladder block where the online change is executed. (3) The instruction functions even when M0 and M10 are off. (4) The instruction does not function.

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

M0

M10

M20

1

1

2

2

END 0 END

M0

M20

M10

0 END 0

STMR T0 K10 M100

STMR T1 K10 M200

M0

M20

M10 STMR T0 K10 M100

STMR T1 K10 M200

1

2

M0

M20

STMR T0 K10 M100

STMR T1 K10 M200

(4)

(1)

(2)

(3)STMR instruction

STMR instruction

Online change completion

1 scan

M10 is added at the online change.

4 11 WRITING DATA TO THE CPU MODULE 11.3 Precautions

11

When multiple users execute the online change function to one CPU module Note the following: Use engineering tools with the same version. Make the option settings the same in all the engineering tools. To prevent program block names from duplicating due to debugs by multiple users when adding a program block or

changing a program block name, select "Yes" for "Duplication Check for POU" under [Convert] [Online Program Change] in the "Options" window of the engineering tool.

For editable contents, refer to the following. Page 156 Editable contents Do not make any changes that affect other programs (for example, editing the same program by multiple users, editing

FBs/FUNs/global labels, or having a duplicate program block name or a duplicate global pointer). If one user makes such a change to a program and execute the online program change function of the engineering tool, and after that, another user execute the online program change function for another program, the engineering tool will detect a mismatch of data in the programmable controller. In this case, verify the data in the changed program and data in the CPU module, and check the mismatched data. Match the data and write the program by using the write to PLC function of the engineering tool, if needed.

Note that after debugging by multiple users, an appointed person must perform the following operations: Read the project from the CPU module by using the read from PLC function of the engineering tool, rebuild (reassign) all the data, and write the project back to the CPU module.

During the file batch online change The following describes the precautions on the file batch online change.

Writing the label data Write labels using the file batch online change only when new label data is added. When the label data is changed or deleted, write data to the programmable controller or execute the online change (ladder block) after the data is rebuilt (reassigned).

Falling instruction in the subroutine type FB program When writing an FB file online, do not use falling instructions in the subroutine type FB program while SM388 (File batch online change operation setting status) is on.

File batch online change during execution of another function The file batch online change cannot be executed during execution of the following functions. An error occurs at execution. Data logging function (when the storage location is the function memory) Data logging file transfer (when the storage location is the function memory)

11 WRITING DATA TO THE CPU MODULE 11.3 Precautions 165

16

12 RAS FUNCTIONS

12.1 Scan Monitoring Function This function detects hardware and program errors of the CPU module by monitoring the scan time. The watchdog timer, an internal timer of the CPU module, is used to monitor the following scan. Initial scan (first scan) Second and later scans

Scan time monitoring time setting Set the scan time monitoring time.

[CPU Parameter] [RAS Setting] [Scan Time Monitoring Time (WDT) Setting]

Window

Displayed items

Watchdog timer reset The watchdog timer is reset when the END/FEND instruction is executed. While the CPU module is running correctly, if the END/FEND instruction is executed within the set time of the watchdog timer, the watchdog timer does not count up. If the END/FEND instruction cannot be executed within the set time of the watchdog timer due to a hardware error of the CPU module or increase in program execution time due to an interrupt or other causes, the watchdog timer counts up.

Item Description Setting range Default Initial Scan Sets the scan-time monitoring time (WDT) for the initial scan (first

scan). 10 to 2000ms (in units of 10ms) 2000ms

After 2nd Scan Sets the scan-time monitoring time (WDT) for the second and later scans.

10 to 2000ms (in units of 10ms) 200ms

6 12 RAS FUNCTIONS 12.1 Scan Monitoring Function

12

Precautions The following lists the precautions on the scan monitoring function.

Measurement error of watchdog timer Since the watchdog timer produces an error within the range of 0 to 10ms, take this into consideration when setting the scan time monitoring time. For example, if the scan time monitoring time is set to 100ms, an error will occur when the scan time falls within the range 100ms < t < 110ms.

Resetting the watchdog timer when repeatedly executing a program The watchdog timer can be reset by executing the WDT reset instruction from the program. If the watchdog timer counts up while a program is being repeatedly executed by the FOR instruction and NEXT instruction, use the WDT reset instruction to reset the watchdog timer.

Scan time when the WDT reset instruction is used Even when the watchdog timer is reset by the WDT reset instruction, the scan time is not reset. The scan time is accumulated until the END instruction is executed.

FOR K1000

WDT

NEXT

M0

Program which processes data repeatedly

Reset the watchdog timer.

1000 times of repeats

END 0 END 0

Internal processing time Program Internal processing time

Scan execution program A

Scan execution program B

Watchdog timer reset (internal processing by the CPU module)

Scan execution program A

Scan time

Watchdog timer measurement time

Next scan time

Watchdog timer reset (internal processing by the CPU module)

12 RAS FUNCTIONS 12.1 Scan Monitoring Function 167

16

12.2 Self-Diagnostics Function This function (the CPU module itself) checks if a problem exists in the CPU module.

Self-diagnostics timing If an error occurs when the CPU module is powered on or while it is in the RUN/STOP state, the CPU module detects, and displays it, and stops operation. However, depending on the error occurrence status or the instruction to execute, the CPU module may not be able to detect the error. Configure safety circuits external to the programmable controller to ensure that the entire system operates safely even in such a case.

Check method of error This section describes the check methods when error occurs.

Check method using the special relay and special register When the CPU module detects an error, it turns SM0 (Latest self-diagnostic error (including annunciator ON)) and SM1 (Latest self-diagnostic error (not including annunciator ON)) on and stores the error code corresponding to the error definition in SD0 (Latest self-diagnostics error code). If multiple errors are detected, the latest error code is stored in SD0. Use SM0, SM1, and SD0 on the program for the CPU module or mechanical interlock. Besides, the error code up to 16 pieces for the error contents being currently generated will be stored into SD10 to SD25 (Self-diagnostic error number). (The error code for the error content of 17th piece on and after will not be stored.)

Check method using LED The error occurrence conditions can be checked through the lighting conditions of ERROR LED. (Page 493 LED status of the CPU module)

Check method using the engineering tool The error conditions for the overall system, error or event history being currently generated can be checked on the Module diagnostics window. ( GX Works3 Operating Manual)

Existing errors Up to 16 errors (descriptions of errors) currently existing on the CPU module can be displayed.* 1 However, even when an additional error occurs after a stop error, the error information is not updated. *1 The maximum number of displayable errors is 15 for continuation errors and 1 for stop errors. When 15 continuation errors are displayed

and another one occurs, description of the new error is not displayed. Also, when an error with the same code has already been displayed, the date and time of occurrence and detailed information of the relevant error are not updated.

Error history Occurred errors is logged in the event history ( Page 177 Event History Function) The event history is updated only when a battery error occurs, independent of the operating status of the CPU module. Also, when a battery error is detected after the occurrence of a stop error, the information on existing errors is not refreshed, and only the event history is updated.

8 12 RAS FUNCTIONS 12.2 Self-Diagnostics Function

12

CPU module operation upon error detection setting Configure each CPU module operation setting when an error is detected.

Mode when an error is detected If the self-diagnostic function of the CPU module detects an error, the CPU module can be in one of the following operation status:

Mode for stopping the operation of CPU module Operation stops when an error has been detected. During stopping the operation may vary depending on the output mode setting when module parameter error occurs. When "Clear" is set: Output for the corresponding module is turned off. When "Hold" is set: Output for the corresponding module is held.

For the setting method of module parameter, refer to the manual for each module.

Mode for continuing the operation of CPU module If an error has been detected, the program other than programs (instruction) where an error was generated is executed.

Error detection setting Set whether or not to detect errors.

[CPU Parameter] [RAS Setting] [Error Detection Setting]

Window

Displayed items

*1 When "Not Detected" is set and an operating module is removed, a module verification error is not detected, but a stop error may occur if a program tries to access the removed module. The removed module will not be accessible even when it is re-installed. Therefore, if an access to the re-installed module occurs by switching the operating status of the CPU module from STOP to RUN.

*2 When "Not Detected" is set, values are stored in the special relay and special register (SM150 to SM154/SD150 to SD154) that indicate the status of the redundant power supply module.

*3 When a battery is installed, change the setting to "Detect". Otherwise, the installation status and replacement period of the battery cannot be checked because the battery error cannot be detected.

Item Description Setting range Default Battery Error Sets whether or not to detect the battery error. Detect

Not Detected R00CPU, R01CPU, and

R02CPU: Not Detected*3

Other CPU modules: Detect

Module Verification Error*1 Sets whether or not to detect a module verification error. Detect

Fuse Blown Sets whether or not to detect a fuse blown of the controlled module.

Redundant Power Supply System Error*2 Sets whether or not to detect a power supply module error (power off or power supply failure in either system) in the redundant power supply system.

Synchronous Interrupt Program (I44, I45) Executing Time Excessive

Execution Interval Excess (I44, I45)

Sets whether or not to detect the excessive execution time of synchronous interrupt program (I44, I45).

Not Detected

Program Execution Section Excess (I45)

Sets whether or not to detect the program execution section excess errors of synchronous interrupt program (I45).

12 RAS FUNCTIONS 12.2 Self-Diagnostics Function 169

17

Applicable errors to the error detection setting The following table lists errors for which whether or not to detect the errors can be set.

CPU module operation upon error detection setting Set the CPU module operation upon error detection.

[CPU Parameter] [RAS Setting] [CPU Module Operation Setting at Error Detected]

Window

Displayed items

*1 This item is not displayed on the R00CPU.

Error name Error code Power shutoff (either of the redundant power supply modules) 1010H

Failure (either of the redundant power supply modules) 1020H

Battery error 1090H

Module verification error 2400H, 2401H

Fuse blown error 2420H

Item Description Setting range Default Instruction Execution Error

I/O No./Network No. Specification Error

Sets the CPU module operation when a specification error of I/O numbers/Network numbers has been detected.

Stop Continue

Stop

Device/Label/Buffer Memory Specification Incorrect

Sets the CPU module operation when a specification error of Device/Label/Buffer memory has been detected.

File Name Specification Incorrect

Sets the CPU module operation upon a file name specification error.

Operation Error Sets the CPU module operation upon an operation error.

Memory Card Error*1 Sets the CPU module operation upon a memory card error.

Module Verify Error Sets the CPU module operation upon a module verification error.

Fuse Blown Sets the CPU module operation upon a fuse blown error of controlled module.

Synchronous Interrupt Execution Interval Error (CPU Module)

Sets the CPU module operation upon a detection of a synchronization signal error on the CPU module.

0 12 RAS FUNCTIONS 12.2 Self-Diagnostics Function

12

Applicable errors to the CPU module operation upon error detection setting The following table lists the applicable errors to the setting that specifies the CPU module operation of when the specific errors are detected.

CPU module operation setting Specify the operation which the CPU module should perform when an error occurs on each intelligent function module.

[System Parameter] [I/O Assignment] tab [I/O Assignment Setting]

Window

Displayed items

Applicable errors to the CPU module operation setting The following table lists the applicable errors to the setting that specifies the CPU module operation of when the specific errors have occurred in each intelligent function module.

Stop setting For the multiple CPU system configuration, it can be specified whether or not to stop all CPU modules when a major or moderate error occurs on a CPU module. ( Page 372 Stop setting)

Error name Error code Memory card error 2120H, 2121H

Module verification error 2400H, 2401H

Fuse blown error 2420H

Inter-module synchronization signal error 2610H

Multiple CPU synchronization signal error 2630H

I/O number or network number specification error 2800H, 2801H, 2802H, 2803H, 2804H, 2805H, 2806H, 2807H, 2810H

Device, label, or buffer memory specification error 2820H, 2821H, 2822H, 2823H, 2824H

File name specification error 2840H, 2841H, 2842H

Operation error 3400H, 3401H, 3402H, 3403H, 3404H, 3405H, 3406H, 3420H, 3421H, 3422H, 3423H, 3424H, 3425H, 3426H, 3427H, 3430H, 3440H, 3441H, 34A0H

Item Description Setting range Default CPU Module Operation Setting at Error Detection

Set the CPU module operation upon the detection of Major or Moderate errors in the configured module.

Critical: Stop, Moderate: Continue Critical: Stop, Moderate: Stop Critical: Continue, Moderate:

Continue

Critical: Stop, Moderate: Continue

Error name Error code Module moderate error 1200H

Module major error 2441H, 2442H, 2450H

12 RAS FUNCTIONS 12.2 Self-Diagnostics Function 171

17

LED display setting Set whether to display or hide the ERROR LED, USER LED, BATTERY LED, and FUNCTION LED.

[CPU Parameter] [RAS Setting] [LED Display Setting]

Window

Displayed items

*1 To specify whether to display or hide the FUNCTION LED, verify the versions of the CPU module and the engineering tool. ( Page 700 Added and Enhanced Functions)

*2 This item is not displayed on the R00CPU, R01CPU, or R02CPU. When the battery error is detected in the R00CPU, R01CPU, and R02CPU, the ERROR LED turns on.

*3 For the R00CPU, the parameter is fixed to "None". For the FUNCTION LED display, the following cases have priority over the function that is set in the LED display setting. When the external input/output forced on/off function is executed (in registration) ( Page 209 FUNCTION LED) When program restoration information is not written ( Page 686 Checking the program restoration information write

status) When the device tests with execution conditions are registered ( Page 212 Device Test with Execution Conditions)

Item Description Setting range Default ERROR LED Minor Error (Continue Error) Set whether or not to display the ERROR LED when a minor error

occurs. Display Do Not Display

Display

USER LED Annunciator ON Set whether the USER LED is displayed or not when annunciator (F) ON is detected.

BATTERY LED*2

Battery Error Set whether the BATTERY LED is displayed or not when a battery error occurs.

FUNCTION LED*1*3

Function to use FUNCTION LED

Set the function that uses FUNCTION LED. If FUNCTION LED is not used, set "None".

Data logging function

Memory dump function

None

Data logging function

2 12 RAS FUNCTIONS 12.2 Self-Diagnostics Function

12

Error detection invalidation setting Turning on the target bit of SD49 (Error detection invalidation setting) disables detection of the corresponding continuation error.* 1 ( Page 603 Diagnostic information) *1 When using the error detection invalidation setting, check the version of the CPU module used. ( Page 700 Added and Enhanced

Functions) The following operations are not disabled even when the detection of the applicable continuation error is disabled in this setting. Storage in buffer memory (Un\G770 to Un\G792) ( MELSEC iQ-R Ethernet User's Manual (Application)) Setting of the completion status of the built-in Ethernet function instruction ( MELSEC iQ-R Programming Manual (CPU

Module Instructions, Standard Functions/Function Blocks)) Data is not retained in SD49 during power failure. Therefore, register this setting again after turning off and on or resetting the CPU module.

Applicable errors to the error detection invalidation setting The following table lists errors for which the detection of the continuation error can be disabled.

Error name Error code Connection establishment failed 112EH

Socket communications response send error 1133H

TCP connection timeout 1134H

Connection number acquisition error 1155H

Receive buffer securement error 1157H

UDP/IP send failed 1165H

TCP/IP send failed 1166H

12 RAS FUNCTIONS 12.2 Self-Diagnostics Function 173

17

12.3 Error Clear This function clears all the existing continuation errors at once.

Errors that can be cleared This function can be used to clear only the continuation errors listed in the following table.

Error name Error code Power shutoff 1000H

Power shutoff (either of the redundant power supply modules) 1010H

Failure (either of the redundant power supply modules) 1020H

Invalid power supply module 1030H

Power supply module configuration error 1031H

ROM write count error 1080H

Battery error 1090H

Memory card access error 1100H

SNTP clock setting error 1120H

Default gateway/gateway IP address error 1124H

Own node port number error 1128H

Open specification port number error 1129H

Specified IP address error 112DH

Connection establishment failed 112EH

Socket communications response send error 1133H

TCP connection timeout 1134H

IP address error 1152H

Connection number acquisition error 1155H

Receive buffer securement error 1157H

UDP/IP send failed 1165H

TCP/IP send failed 1166H

Unsend data send error 1167H

PID operation error 11A0H to 11B8H

Module moderate error 1200H, 1210H

Another CPU module moderate error 1220H

Inter-module synchronization processing error 1240H, 1241H

Multiple CPU synchronization processing error 1260H, 1262H

Annunciator ON 1800H

Operation continuation error 1810H

Receive queue full 1830H

Receive processing error 1831H

Transient data error 1832H

Constant scan time error 1900H

Network configuration mismatch 1B00H

Extension cable failure 1B48H, 1B4AH

Engineering tool

Clears the error.

A continuation error occurs.

A continuation error occurs.

No continuation error occurs.

Power shutdown Battery failure Constant scan time exceeded

4 12 RAS FUNCTIONS 12.3 Error Clear

12

When the write protect switch of the SD memory card is enabled, an error of the memory card access error, which is generated when an event history is held, can be cleared. Note that an error will not be detected again even if the event history is stored due the occurrence of event after resetting an error.

File name specification error 1BB0H

Program execution time error 1BC0H

Memory card error 2120H, 2121H

Module verification error 2400H, 2401H

Fuse blown error 2420H

Module major error 2441H, 2442H, 2450H

Another CPU module major error 2461H, 2462H, 2470H

Inter-module synchronization signal error 2610H

Multiple CPU synchronization signal error 2630H

I/O number or network number specification error 2800H, 2801H, 2802H, 2803H, 2804H, 2805H, 2806H, 2807H, 2810H

Device, label, or buffer memory specification error 2820H, 2821H, 2822H, 2823H, 2824H

File name specification error 2840H, 2841H, 2842H

Operation error 3400H, 3401H, 3402H, 3403H, 3404H, 3405H, 3406H, 3420H, 3421H, 3422H, 3423H, 3426H, 3430H, 3460H, 3461H, 34A0H

Error name Error code

12 RAS FUNCTIONS 12.3 Error Clear 175

17

How to clear errors Errors can be cleared in two ways:

Using the engineering tool Clear errors with the module diagnostics function of GX Works3. ( GX Works3 Operating Manual)

The event history of error clear using the engineering tool is stored in the CPU module connected.

Using SM/SD Clear errors by operating SM/SD.

1. Check SD0 (Latest self-diagnostic error code) to identify what errors are detected.

2. Clear the cause of each of the currently detected continuation errors.

3. Turn on SM50 (Error reset) to clear the errors. When multiple continuation errors have occurred, all the errors are cleared at once.

Precautions This section describes some precautions to take when using the error clear function: Since the function clears all of the currently detected continuation errors at once, errors that should not yet be cleared may

be cleared. Use the RST instruction to reset each annunciator individually. Running the error clear function does not remove the cleared errors from the event history. The cause of an error which occurred in a module other than the target CPU module for the error clear cannot be eliminated

even though the error is cleared using this function. For example, when "Module verification error" (error code: 2400) or "Module major error" (error code: 2450) occurred, the error cause cannot be eliminated even though the error is cleared in the CPU module using this function. To eliminate the error cause, clear the error of the target module and reset the CPU module.

6 12 RAS FUNCTIONS 12.3 Error Clear

12

12.4 Event History Function The CPU module collects and stores event information from each module, such as errors detected by the module, operations performed on the module, device/label data write operations*1, and network errors.* 2

Once errors and operations are stored, they can be checked chronologically. This function helps to determine the causes of problems that have occurred in the equipment/devices, check the update status of the programmable controller control data, and detect unauthorized access.

*1 When "Save Device/Label Operations" is set in Event History Setting, device/label data write operations are saved. ( Page 183 Device/label data write operation saving) Before using the device/label operation save setting, check the versions of the CPU module and engineering tool. ( Page 700 Added and Enhanced Functions)

*2 If the CPU module is operated online using the engineering tool, there are times when processing performed automatically by the system is saved as an event.

The event history information is constantly collected regardless of the operating state of the CPU module. There are occasions, however, when the event history information cannot be collected due to a major error in a module, a base unit error, a cable failure, or some other cause.

The information of events that occurred in the host CPU module and modules which are managed by the host CPU module are sampled by the CPU module in a batch and saved.

The event information that is held in the CPU module is displayed with an engineering tool.Engineering tool

12 RAS FUNCTIONS 12.4 Event History Function 177

17

Event history setting Under normal circumstances, the event history function can be used with its default settings and need not be manually configured. The storage memory and size settings for event history files can be changed as needed. ( Page 179 Event history file)

[CPU Parameter] [RAS Setting] [Event History Setting]

Window

Displayed items

*1 It cannot be set in the R00CPU. *2 This item is not displayed on the R00CPU, R01CPU, or R02CPU.

For use in any of the following environments, use of an SD memory card for the save destination memory is recommended because the number of events that occur becomes large. When file data write operations and device/label data write operations are performed frequently When the communication status changes frequently When device data write operations are periodically performed from a programmable controller of another

station or from another CPU module*3

The number of writes to the data memory is limited to 100000 times. In any of the above cases, when data memory is used for the save destination memory, be careful about the number of writes to data memory.

*3 When "Save Device/Label Operations" is set in Event History Setting. Note that when device data write operations are performed periodically, the number of events registered in the history becomes large, and event history logging may be restricted. ( Page 182 Event history logging restriction)

Item Description Setting range Default Save Destination Specify the storage location of event history files. ( Page 179

Storage memory) Data Memory Memory Card*1

Data Memory

Set Save Volume of Per File Specify the storage capacity per event history file. ( Page 179 File size)

1 to 2048K bytes (in 1K bytes)

128K Byte

Save Device/Label Operations*2 Specify this item when saving device/label data write operations. ( Page 183 Device/label data write operation saving)

Do not save Save

Do not save

8 12 RAS FUNCTIONS 12.4 Event History Function

12

Logging of the event history This section describes events saving for the event history.

Event history file The storage memory and file size for event history files can be changed in event history setting. ( Page 178 Event history setting)

Storage memory Choose either the data memory or SD memory card.* 1

If the storage memory is the SD memory card: when the write protect switch of the SD memory card is enabled, an event history will not be stored. (It is possible to read the event history file in SD memory card using the engineering tool.) Therefore, if the write protect switch of the SD memory card is changed into "Disabled Enabled" during operation, the write error to the SD memory card occurs when the event for storing into event history is generated (SD memory card available event is registered) after the write protect switch is enabled. An error that has occurred can be checked by using the module diagnostics of the engineering tool immediately after its occurrence. However, these errors are not stored in the event history after powering off and on or reset of the CPU module. *1 For the R00CPU, only the data memory can be selected as the storage memory.

File size The size for event history files can be changed in event history setting ( Page 178 Event history setting). If the storage size exceeds the specified size, records are deleted in order from the oldest one and the latest one is stored. An event history file size is obtained from the following calculation formula. Event history file size = File header size + Event history management information size + (Number of records Size per event history record)

*1 Because the contents of detailed information may differ depending on the event to be saved or the detailed information may include a variable-length file name, the size per event history record is variable.

The number of events to be saved in the event history file differs depending on the event type to be saved. When the event history file size is 128K bytes (default), 1365 events can be registered if programs (whose program name is 8 characters (12 characters including a period and extension)) are written to the CPU module using the engineering tool. [Calculation formula] 128 bytes 1024 = 131072 bytes 131072 bytes - (20 bytes + 12 bytes) = 131040 bytes 131040 bytes 96 bytes = 1365 events

Element Size File header size 20 bytes

Event history management information size 12 bytes

Size per event history record 40 bytes minimum*1

12 RAS FUNCTIONS 12.4 Event History Function 179

18

Ex.

The table below shows the size of each element when 100 programs (whose program name is 8 characters (12 characters including a period and extension)) are written to the CPU module by the following operating procedure.

Operating procedure 1. Turn on the power in the STOP state.

2. Write the system parameter, CPU parameter, module parameter, and 100 programs (whose program name is 8 characters (12 characters including a period and extension)) to the CPU module using the engineering tool.

3. Switch the CPU module to the RUN state.

Element Size (byte) File header 20

Event history management information 12

Event to be saved Power-on and reset 40

Operating status change (STOP) 40

Writing files/folders (SYSTEM.PRM) 96

Writing files/folders (CPU.PRM) 88

Writing files/folders (UNIT.PRM) 88

Writing files/folders (MAIN_001.PRG to MAIN_100.PRG) 9600

Operating status change (RUN) 40

Total 10024

0 12 RAS FUNCTIONS 12.4 Event History Function

12

When files are created An event history file is created when: The CPU module is turned off and on (if there is no event history file or after the event history settings are changed). The CPU module is reset (if there is no event history file or after the event history settings are changed). Initialization of the SD memory card (when no event history file exists)*1

Write of parameters (when no event history file exists, or after an event history setting is changed). *1 When a parameter is stored in the data memory, the event history file is created on the SD memory card, according to the event history

setting.

When a new event history file is generated, the "Event history file generation" (00420) is logged. When a new event history file is generated during the logging restriction of the event history, the "Event history logging restriction" (00421) is also logged.

The following table shows how the event history is treated depending on operation.

The following table shows how the event history is treated at removal and installation of a SD memory card when the SD memory card is specified as the storage memory.

When parameters take effect Any changed parameters take effect when: The CPU module is powered on The CPU module is reset

Any changed parameters written in the storage memory with the CPU module in the STOP state does not take effect when the CPU module operating state is changed from STOP to RUN. In this case, the changed parameters will take effect the next time the CPU module is powered off and on or is reset.

Loss of event history information If events are detected frequently, or the CPU module is powered off or reset immediately after the detection of events, some events may not be collected and lost. When event loss occurs, "*HST LOSS*" appears in the "Event Code" field of the engineering tool.

Operation Operation for the event history Memory initialization When this event occurs, the event history is stored into the internal memory. If the internal memory reaches the maximum

number of event history records it can store, all subsequent events are lost. ( Page 181 Loss of event history information)

Event history creation The event history, which has been stored in the internal memory during absence of the event history file, is stored into the data memory or the SD memory card (If any event was lost, it is logged as "*HST LOSS*").

Operation Operation for the event history Removal of the SD memory card When this event occurs, the event history is stored into the internal memory. If the internal memory reaches the maximum

number of event history records it can store, all subsequent events are lost. ( Page 181 Loss of event history information)

Installation of the SD memory card

The event history, which have been stored in the internal memory during absence of the SD memory card, is stored to the SD memory card. If the re-inserted SD memory card contains an event history file of the same file size, the CPU module continues to store the event history information. If the file size is different, the CPU module removes the existing event history file and creates a new event history file.

12 RAS FUNCTIONS 12.4 Event History Function 181

18

Event history logging restriction When the number of minor events from the CPU module or intelligent function module such as link-up and link-down exceeds the upper limit value, event history logging is restricted (stopped).* 1*2

When the number of events for which logging is restricted decreases to the lower limit value or below, event history logging is restarted. The error codes of moderate and major errors that occur in the CPU module are logged in the event history.

*1 For models and firmware versions that support the event history logging restriction, refer to the following. Page 700 Added and Enhanced Functions

*2 Event history logging is not restricted (stopped) in CPU module events for the following CPU modules. The R00CPU, R01CPU, and R02CPU with firmware version "11" or earlier The programmable controller CPU with firmware version "43" or earlier (except for R00CPU, R01CPU, and R02CPU)

Events not supported by the logging restriction The following events are not subject to the logging restriction.* 1

Events of the self-diagnostics for major errors from the intelligent function module *1 For the following CPU modules, CPU module events are not subjected to the logging restriction, either.

The R00CPU, R01CPU, and R02CPU with firmware version "11" or earlier The programmable controller CPU with firmware version "43" or earlier (except for R00CPU, R01CPU, and R02CPU)

How to check whether event history logging is restricted When event history logging is restricted, SM1464 (Event history logging restriction status) turns on. SM1466 turns on when the event history logging of the CPU module is restricted and the event category is error (minor error), and SM1467 turns on when the event history logging of the CPU module is restricted and the event category is information or warning. Modules on which event history logging is restricted can be identified in SD1464 to SD1467 (Module information on event history logging restriction).

Modules from which event history information is collected Event history information is collected from the CPU module and other modules installed on the same base unit (i.e., the main base unit plus any additional extension base units). Event history information may or may not be collected from devices on the network depending on the specifications of the network modules used to connect to them. Refer to the manuals of the respective modules for more information including the coverage of event history collection regarding devices on the network. For a multi-CPU system, note that each CPU module logs only events detected on the modules under its control. On Q series modules, only errors of which even type is "System" are stored. (The above applies only to Q series modules that support the module error collection (function).)

Events logged by the CPU module Information logged in the event history includes operation initiator and other detailed information for troubleshooting purposes. For events that are logged in the event history on the CPU module, refer to the event history. ( Page 563 Event List)

Item Condition Upper limit value 600 events/minute

Lower limit value 300 events/minute

2 12 RAS FUNCTIONS 12.4 Event History Function

12

Device/label data write operation saving

When "Save Device/Label Operations" is enabled in Event History Setting, device/label data write operations are saved. ( Page 178 Event history setting)

Before using the device/label operation save setting, check the versions of the CPU module and engineering tool. ( Page 700 Added and Enhanced Functions)

When multiple device points or multiple devices/labels are written, some device/label names and written values may not be shown.

Target operations The device/label data write operations of the following operations and functions are saved.

*1 When writing the data with write notification, the write notification device is also saved. *2 The read notification device is saved.

Applicable commands for writing device/label data through SLMP The following table shows the applicable commands for writing device/label data through SLMP.

This function cannot be used in the R00CPU, R01CPU, and R02CPU.

Operation and function Remarks Operation from the engineering tool

Changing current values of devices and labels from the watch window or with the other methods

The written values are saved up to 128 words.

Changing the status (active/inactive) of blocks and steps of an SFC program

Writing data to the device memory

Operation using SLMP Writing device/label data

Operation using a GOT Writing device/label data

Other operations Writing device data from a programmable controller of another station*1, reading data from programmable controller of another station (with read notification)*2, and writing device data from another CPU module

Writing device data using the simple CPU communication function

Writing device data using the predefined protocol support function

Type Operation Command Subcommand Remarks Device Write 1401 001

003 The written values are saved up to 128 words.

000 002

Write Random 1402 001 003

The number of data sets to be saved varies depending on the device specified.000

002

Write Block 1406 000 002

The written values are saved up to 128 words per block. The number of data sets to be saved varies depending on the devices specified.

Label Array Label Write 141A 0000 The written element data are saved up to 128 words. The number of data sets to be saved varies depending on the number of array points specified.

Label Write Random 141B 0000 The number of data sets to be saved varies depending on the label assignment destination. The written strings are saved up to 128 words.

Extend Unit Write 1601 0000 The written values are saved up to 128 words.

12 RAS FUNCTIONS 12.4 Event History Function 183

18

Applicable instructions for writing device data from a programmable controller of another station or from another CPU module

The following table shows the applicable instructions for writing device data from a programmable controller of another station or from another CPU module.

*3 For the display of detailed information, refer to the following. Page 184 Detailed information

Target device The following table shows the target devices. The write operations are also saved when writing data with index modification or indirect specification.

Note that for write operation by specifying label names, label memory areas (such as GV, LV, LLV, and UV) may be displayed as device names. For details on the label memory, refer to the following. GX Works3 Operating Manual

Target label The labels to be saved are all labels that can be specified by the engineering tool and SLMP.

Detailed information The detailed information of an event history displays a device/label name, the number of write points, and written values. ( Page 561 Detailed information)

Major classification Classification Instruction name Remarks Writing device data from another station

Module dedicated instructions

Writing data to programmable controller of another station

JP.WRITE, GP.WRITE The written values are saved up to 128 words.

Writing data to program controller of another station (with write notification)

JP.SWRITE, GP.SWRITE

Reading data from programmable controller of another station (with read notification)

JP.SREAD, GP.SREAD

Writing data to target station J(P).RIWT, G(P).RIWT

Writing device data from another CPU module

Multiple CPU dedicated instructions

Writing device data to another CPU module

D(P).DDWR, M(P).DDWR

Type Device Bit device X, DX, Y, DY, M, L, F, SM, V, B, SB, T (contact), T (coil), ST (contact), ST (coil), C (contact), C (coil), LT (contact), LT (coil),

LST (contact), LST (coil), LC (contact), LC (coil), FX, FY, Jn\X, Jn\Y, Jn\SB, Jn\B, BLn\S, SA\X, SA\Y, SA\M, SA\B, SA\T(contact), SA\T(coil), SA\ST(contact), SA\ST(coil), SA\C(contact), SA\C(coil)

Word device T (current value), ST (current value), C (current value), D, SD, W, SW, RD, R, ZR, Z, FD, Un\G, Jn\W, Jn\SW, U3En\G, U3En\HG SA\D, SA\W

Double-word device LT (current value), LST (current value), LC (current value), LZ

Item Name displayed on window Description Device/Label Device name information A specified device name is displayed.

Device name information (user-specified)

Device name information (target device) The name and address of a device actually accessed is displayed. When a device is specified with index modification, if the accessed device is within the specified device range, the device name is displayed. If out of the specified device range, the address is displayed. When a device is specified with indirect specification, the accessed address is displayed.

Label name information A specified label name is displayed.

Label name information (user-specified)

Target bit No. When a bit of a word device is specified with indirect specification, the accessed bit number is displayed. The same applies when a bit is specified with index modification and the accessed bit is out of the specified device range, the accessed bit number is displayed.

Number of write points Number of points The number of write points is displayed.

Written value Written value The written values for the number of write points is displayed.

4 12 RAS FUNCTIONS 12.4 Event History Function

12

Viewing the event history The event history can be viewed using the menus of the engineering tool. For operating procedures and how to interpret the displayed information, refer to the following: GX Works3 Operating Manual

Clearing the event history The event history can be cleared from the event history window. Once the event history is cleared, the CPU module deletes all the event history information stored in the specified storage memory. For operating procedures and other details, refer to the following: GX Works3 Operating Manual

When clearing of the event history is executed, the "Event history clear" (20200) is logged. When an event history file is executed clear during the logging restriction of the event history, the "Event history logging restriction" (00421) is also logged.

Precautions

Clearing the event history during execution of another function No event history can be cleared during execution of the following functions. Check that the following functions are not being executed and then clear the event history. CPU module data backup/restoration function iQ Sensor Solution data backup/restoration function

Reading the event history during execution of another function No event history can be read during execution of the following function. Check that the following function is not being executed and then read the event history. CPU module data restoration function

Logging of event history When event history logging is restricted, the relevant special relay ( Page 182 How to check whether event history logging is restricted) turns on. Eliminate the event causes from the target module. The target module can be identified in SD1464 to SD1467 (Module information on event history logging restriction). Whether event history logging is restricted or not can also be checked in "Event history logging restricted" (00421) in "Event History" window of the engineering tool.

Execution of other functions while event history logging is restricted When the CPU module is restored by turning on SM1354 while event history logging is restricted, event history logging is restarted after the completion of the restoration. When event history logging is restarted and event history from a module is frequently logged again, logging the history of events occurring on the target module is stopped (restricted).

12 RAS FUNCTIONS 12.4 Event History Function 185

18

Change of the event history setting The following table shows the operation when the event history setting is changed after the CPU module starts, and written to the CPU module.

Therefore, to save a past event history, before changing the event history setting, save data by using the [Create File] button in the event history window of the engineering tool.

[Diagnostics] [System Monitor] [Event History] button [Create File] button

Device data write operation from another station or another CPU module When "Save Device/Label Operations" is set in Event History Setting, many event updates occur. Depending on the timing, events that occurred cannot be checked with the engineering tool.

12.5 Program Cache Memory Auto Recovery Function If the contents of memory of the CPU module have been rewritten by itself due to the factors such as excessive electrical noise, the program cache memory recovers the corresponding areas automatically during the run of the program. This function becomes active with RUN state of the CPU module and works during the run of the program. No special settings are required as the system performs this task automatically.

Changed item Operation Save Destination With the original file left as is, an event history file is generated in the enabled save destination (drive).

Set Save Volume of Per File The event history file is discarded and regenerated.

Save Device/Label Operations With the original file left as is, EVENT.LOG is generated when the file is not saved, and EVEN2.LOG is generated when the file is saved.

6 12 RAS FUNCTIONS 12.5 Program Cache Memory Auto Recovery Function

13

13 REMOTE OPERATION The operating status of the CPU module can be changed using an engineering tool or program, or dedicated instructions from the module. The following types of remote operation are available: Remote RUN/STOP Remote PAUSE Remote RESET

13.1 Remote RUN/STOP This function externally changes the CPU module status to RUN or STOP with the RUN/STOP/RESET switch of the CPU module set to RUN. This function is useful to RUN or STOP a CPU module located in an unaccessible place, or to RUN or STOP a CPU module located on the control panel by using an external signal.

Executing method The following methods are available to execute remote RUN/STOP:

Using a contact Set RUN contact in the RUN-PAUSE contact setting. ( Page 189 Setting RUN-PAUSE Contacts) When the END processing for the scan where the RUN contact is turned on is executed, SM203 (STOP contact) turns on to change the CPU module status to STOP and stop the operation. When the RUN contact is turned off, the CPU module exits the STOP state and resumes the program operation from the step 0.

Using an engineering tool Perform remote RUN/STOP with the remote operation of the engineering tool. ( GX Works3 Operating Manual)

By an external device using SLMP Perform remote RUN/STOP with the SLMP command. ( SLMP Reference Manual)

Using the module dedicated instructions Perform remote RUN/STOP with the dedicated instructions of a network module. ( MELSEC iQ-R Programming Manual (Module Dedicated Instructions))

(1) When the RUN contact is turned off, the CPU module status changes to RUN and the program is resumed from the step 0.

(2) SM203 turns on when the END processing for the scan where the set RUN contact is turned on is executed.

(3) When the RUN contact is turned on, the CPU module executes the operation until the END instruction and enters the STOP state.

(1)0 0

ON

OFF

ON

OFF SM203

END

RUN

(2)

(3)

STOP RUN

END

Setup RUN contact

RUN/STOP state

13 REMOTE OPERATION 13.1 Remote RUN/STOP 187

18

Precautions This section describes the precautions on using remote RUN/STOP. When remote RUN is performed during execution of the data logging function, it may fail. In that case, wait for a while and

retry remote RUN. If remote RUN still cannot be executed, check whether remote RUN is acceptable and retry remote RUN ( Page 298 About remote operation)

When the RUN contact, which is specified in the RUN-PAUSE contact setting, is turned off during execution of the data logging function, it may take time to return to the RUN state.

13.2 Remote PAUSE This function externally changes the CPU module status to PAUSE with the RUN/STOP/RESET switch of the CPU module set to RUN. Use this in a process control and other situations to keep the CPU module status in RUN even when changing the status of the output (Y) to STOP.

Executing method The following methods are available to execute remote PAUSE:

Using a contact Set PAUSE contact in "RUN-PAUSE Contact Setting". ( Page 189 Setting RUN-PAUSE Contacts) When the END processing for the scan where the PAUSE contact is turned on is executed, SM204 (PAUSE contact) turns on. When the CPU module executes until the END instruction for the scan next to that where the PAUSE contact is turned on, its status changes to PAUSE, and the operation stops. When the PAUSE contact is turned off, the CPU module exits the PAUSE status and resumes the program operation from the step 0.

Using an engineering tool Perform remote PAUSE with the remote operation of the engineering tool. ( GX Works3 Operating Manual)

By an external device using SLMP Perform remote PAUSE with the SLMP command. ( SLMP Reference Manual)

(1) When the PAUSE contact is turned off, the CPU module exits the PAUSE state and resumes the program operation from the step 0.

(2) SM204 turns on when the END processing for the scan where the set PAUSE contact is turned on is executed.

(3) When the CPU module executes until the END instruction for the scan next to that where the PAUSE contact is turned on, its status changes to PAUSE, and the operation stops.

ON

(1)

OFF

SM204 ON

OFF

0 END 0

END

RUNPAUSERUN

(3)

(2)

0 END 0 END

Setup PAUSE contact

RUN/PAUSE state

8 13 REMOTE OPERATION 13.2 Remote PAUSE

13

13.3 Setting RUN-PAUSE Contacts RUN-PAUSE contacts can be set. RUN-PAUSE contacts are used to perform remote RUN or STOP, or remote PAUSE using a contact.

[CPU Parameter] [Operation Related Setting] [RUN-PAUSE Contact Setting]

Window

Displayed items

When setting the PAUSE contact, be sure to also set the RUN contact. (The PAUSE contact cannot be set alone.)

Item Description Setting range Default RUN Set the contact that controls RUN for the CPU module. R00CPU, R01CPU, and R02CPU: X0 to X1FFF

Other CPU modules: X0 to X2FFF

PAUSE Set the contact that controls PAUSE for the CPU module. R00CPU, R01CPU, and R02CPU: X0 to X1FFF Other CPU modules: X0 to X2FFF

13 REMOTE OPERATION 13.3 Setting RUN-PAUSE Contacts 189

19

13.4 Remote RESET This function externally resets a CPU module in the STOP state (including that stopped due to an error). Even when the RUN/ STOP/RESET switch of a CPU module is set to RUN, the CPU module can be reset in the STOP state.

To perform the remote RESET operation when "Execution Target" of the remote operation is set to "All Stations Specified" or "Specify Group No.", ensure that the CPU module set in "Specify Connection Destination Connection" of the engineering tool is in the STOP state. (Even if a CPU module in the STOP state exists on the specified network, the remote RESET does not operate.)

Enabling remote RESET Performing remote RESET requires setting for enabling remote reset.

[CPU Parameter] [Operation Related Setting] [Remote Reset Setting]

Window

Displayed items

Executing method

Using an engineering tool Perform remote RESET with the remote operation of the engineering tool. ( GX Works3 Operating Manual)

By an external device using SLMP Perform remote RESET with the SLMP command. ( SLMP Reference Manual)

Item Description Setting range Default Remote RESET Set whether or not to enable the remote RESET. Disable

Enable Disable

0 13 REMOTE OPERATION 13.4 Remote RESET

14

14 BOOT OPERATION The files stored on the SD memory card are transferred to the storage memory which is automatically determined by the CPU module when the CPU module is powered off and on or is reset.

This function cannot be used in the R00CPU.

14.1 Boot Operation Procedure The boot operation procedure is as follows.

1. Configure the boot setting. ( Page 193 Configuring the Boot Setting)

2. Insert an SD memory card to the CPU module.

3. Write the boot setting and boot file to the SD memory card. ( Page 194 Writing Boot Settings and Boot Files)

4. Power off and on, or reset the CPU module.

(1) The boot operation is executed according to the boot file setting when the CPU module is powered on or is reset.

(1)

CPU_SYS.PRM MAIN.PRG

CPU module

Engineering tool

Built-in memory of the CPU module

SD memory card

Program memory

The CPU module automatically detects the memory type.

Data memory Device/label memory

14 BOOT OPERATION 14.1 Boot Operation Procedure 191

19

14.2 Specifiable File Types The files which can be booted are as follows. System parameter CPU parameter Module parameter Module extension parameter Module extension parameter for protocol setting Remote password Global label setting file Initial global label value file Program file Initial local label value file FB/FUN file Device comment line Initial device value file

14.3 Allowed Maximum Number of Boot Files The maximum number of boot file settings which can be specified is 512. However, because more than one file is bootable for a single setting, the maximum number of boot files is the same as the number of files which can be stored in the transfer destination memory.

2 14 BOOT OPERATION 14.2 Specifiable File Types

14

14.4 Configuring the Boot Setting Configure the necessary settings for the boot operation.

[Memory Card Parameters] [Boot Setting]

Operating procedure

Displayed items

"Boot Setting" window 1. Click "Detailed Setting" on the "Boot File Setting" window.

"Boot File Setting" window 2. Click the "Type" column. The maximum number of boot files that can be specified is the same as the number of files that can be stored in the storage memory.

"Add Type" window 3. Select type for the boot file. (Multiple selection is possible.)

"Boot File Setting" window 4. Set the data name (file name).

Item Description Setting range Default Operation Setting at CPU Built-in Memory Boot

Sets whether or not to clear the CPU built-in memory (program memory and data memory) upon file transfer from the SD memory card.

Do Not Clear Clear

Do Not Clear

Boot File Setting Sets the file used for boot operation from the SD memory card.

14 BOOT OPERATION 14.4 Configuring the Boot Setting 193

19

14.5 Writing Boot Settings and Boot Files Use the following functions of the engineering tool.

*1 The engineering tool with version 1.070Y supports this function.

The boot settings and boot files cannot be written with a user-data-write operation of the engineering tool.

For details, refer to the following. GX Works3 Operating Manual

14.6 Operation When Security Functions Are Enabled This section describes the operation when security functions are enabled.

When a security key is set When a security key is set to the boot target program file and the security key of the program file does not match with that of the CPU module, a boot error occurs. Also, when no security key is written to the CPU module, a boot error occurs as well.

When a file password is set If a file password is set on both the source boot file and destination file, the file can be transferred only when the passwords match. Furthermore, the file transfer does not work if a file password is set only on either one.

Function Description Write to PLC Use this function to write the data to the SD memory card inserted into the CPU module. Click [Online] [Write to PLC] on

the menu bar.

Write to Memory Card*1 Use this function to write the data to the SD memory card inserted into the computer. Click [Tool] [Memory Card] [Write to Memory Card] on the menu bar.

Security key of boot target program file

Security key of CPU module Security key match/mismatch Boot program execution

Set Written Match Execute

Written Not match Not execute (boot error)

Not written Not execute (boot error)

Transferring boot file Transferred boot file Password match/ mismatch

Transfer

File File password setting File File password setting Existing Set Existing Set Match Yes

Mismatch No

Not set No

Not existing Yes

Not set Existing Set No

Not set Yes

Not existing Yes

4 14 BOOT OPERATION 14.5 Writing Boot Settings and Boot Files

14

14.7 Precautions This section describes the precautions when using the boot operation. When a parameter file is set as boot file, it overwrites the parameter file inside the transfer destination CPU module. In

addition, if a parameter file is not set as boot file even when stored on the SD memory card, the CPU module operates in accordance with the settings in the parameter file inside it.

If a program in the program memory is changed online during boot operation, the change is also reflected in the transfer source program on the SD memory card.

Note the model of the program written on the SD memory card (program specified in the boot file settings) and the model of the CPU module must be the same.

For the boot file setting, check that the setting is consistent with the program/label setting. When the file is read from the programmable controller after the boot operation without consistency, conversion may not function properly due to lack of consistency in project data.

14 BOOT OPERATION 14.7 Precautions 195

19

15 MONITOR FUNCTION This chapter describes the functions for checking the CPU module operation.

15.1 Real-Time Monitor Function This function monitors the contents of a specified device/label of the CPU module in real time at a specified interval or a desired timing. The function can be set with GX LogViewer, where the value changes of a specified device/label can be shown graphically. Saving the set data and displayed graphs makes it possible to simplify the settings and check the graphs at a later time.

Before executing the function, check the versions of the CPU module and GX LogViewer used. ( Page 700 Added and Enhanced Functions)

For details on the function, refer to the following. GX LogViewer Version 1 Operating Manual

Item Description Reference Circuit monitor Checks the status of the running program on the program editor. GX Works3 Operating Manual

Device/buffer memory batch monitor Checks the current values of the device and buffer memory in a batch.

Watch Registers a device and label and checks the current values.

Program monitor list Checks the processing time of the running program.

Interrupt program monitor list Checks the number of executions of the interrupt program used in the program.

Real-time monitor Monitors the contents of a specified device/label of the CPU module in real time at a specified interval or a desired timing.

GX LogViewer Version 1 Operating Manual

Scan time measurement Measures the processing time of the set program section and displays it on the engineering tool.

Page 197 Scan Time Measurement GX Works3 Operating Manual

Scan time clear Clears values of the scan time at a desired timing without stopping the CPU module.

Page 588 Fixed scan function information

GX Works3 Operating Manual

Specified program monitor Checks (monitors) device/label values in the program specified by the engineering tool on the program editor and changes current values.

Page 202 Specified Program Monitor

GX Works3 Operating Manual

GX LogViewer

Data in the specified device/label are monitored in real time.

6 15 MONITOR FUNCTION 15.1 Real-Time Monitor Function

15

15.2 Scan Time Measurement This function measures the processing time of the set program section and displays it on the engineering tool. The time required for the subroutine and interrupt programs can be measured.

Before using scan time measurement, check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

Target programs The target programs include ladder programs and SFC programs. For details on operation when each program is measured, refer to the following. GX Works3 Operating Manual

Execution procedure While the target program is displayed, execute this function from the "Scan Time Measurement" window. For details on the menu operation, refer to the following. GX Works3 Operating Manual

Minimum unit of measurement time The minimum unit of measurement time is 1s (0.001ms).

(1) Displays the scan time of the specified range.

(1)

Ladder program

Engineering tool

"Scan Time Measurement" window

15 MONITOR FUNCTION 15.2 Scan Time Measurement 197

19

Operating specifications The scan time is measured while the operating status of the CPU module is the RUN state. When the CPU module is in the

STOP state, the current value is 0ms and other values are the ones immediately before the CPU module enters the STOP state. (The values are not updated while the CPU module is in the STOP state.)

The measurement starts from the start step of the scan subsequent to the scan where the start request receives. When a subroutine program is executed in the measurement range specified by the main program, the execution time of

the subroutine program is also included in the measurement range. Also, when an interrupt program, fixed scan execution type program, or event execution type program triggered by occurrence of an interrupt is executed in the measurement range specified by the main program, the execution time of an interrupt program, fixed scan execution type program, or event execution type program triggered by occurrence of an interrupt is added accordingly to the scan time of the measurement range.

When the start step is specified between the FOR and NEXT instructions, scan time measurement is performed with the measurement range from the execution of the first start step instruction to the execution of the end step instruction.

When the start step is 8 and the end step is 13

END

A subroutine program has been called.

Main program

Subroutine program

Measurement range

Start End

END

An interrupt has occurred.

Interrupt program

Measurement range

Start End

Main program

FOR K2

NEXT

3

10

11

6

8

14 END

Program example

Start step: 8

End step: 13

8 15 MONITOR FUNCTION 15.2 Scan Time Measurement

15

Precautions Use the program written to the CPU module. If the program on the engineering tool and the program written to the CPU

module do not match, an error occurs. However, if the program is changed using the engineering tool and restored again, the program is judged to be different from the program in the CPU module. In that case, the program must be read from the CPU module before being executed.

The scan time measurement cannot be executed from multiple external devices simultaneously. Any scan time measurement executed after the first one will result in an error. The scan time measurement executed first will continue to measure normally.

Measurement may not be executed depending on the program configuration. In that case, the CPU module returns a response without updating the value, and the displayed value is not updated. Therefore, specify the start and end steps in a program configuration in which measurement start and stop can be executed within one scan. The following shows an example of when measurement cannot be executed.

When the branch instruction such as the JMP instruction is specified for the end step When the start step is 3 and the end step is 6

When the END instruction is executed without executing the end stop after the execution of the start step When the start step is 3 and the end step is 9

(1) The end stop is not executed due to the JMP instruction. (2) Measurement cannot be performed because only the start step is executed.

JMP P0

0

7

10

3

5

13 END

P0

Program example

Start step: 3

End step: 6

END

JMP P0

3 9

0

7

12

3

5

13 END

P0

10

(1)

(2)

Start step End step

Start

Program example

Start step: 3

End step: 9

15 MONITOR FUNCTION 15.2 Scan Time Measurement 199

20

When the end step is executed before the start step When the start step is 3 and the end step is 8

(1) The start step is executed after the execution of the end step by the CALL instruction. (2) Because the end step is not executed after the execution of the start step, measurement cannot be performed. When the END instruction is executed by executing the end step without executing the start step When the start step is consecutively executed (except for when any start step exists between the FOR and NEXT instructions ( Page 198 Operating specifications))

(1) Measurement cannot be performed when the start step is executed repeatedly. When the IRET instruction, FEND instruction, BREAK instruction, or RET instruction is specified for the end step When the start step is 4 and the end step is 12

(1) When the scan time in an interrupt program is measured, do not specify the IRET instruction for the end step.

END

3 8

(2)

0

6

3

5

10

RET

CALL P0

END

FEND

9

(1)

P0

Start step End step

End Start

Program example

Start step: 3

End step: 8

(1)

ENDStart End + 1Start

4 12

3

10

12

4

7

13 END

I31

IRET

EI

FEND

0

1

(1)

Start step End step

Program example

Start step: 4

End step: 12

0 15 MONITOR FUNCTION 15.2 Scan Time Measurement

15

When the start step is not the head step of the ladder block containing the specified step, or when the end stop is not the last step of the ladder block containing the specified step, correct the start/end step with the engineering tool.

If the program change is executed by the online program change or the file batch online change while scan time measurement is being executed, scan time measurement is interrupted. The program change by the online program change or the file batch online change is completed normally.

If scan time measurement is executed while the program change is being executed by the online program change or the file batch online change, scan time measurement cannot be performed. The program change by the online program change or the file batch online change is completed normally.

END

SM400

INC D0

Y0

X10

0

10

12

X0

X0

X1

INC D1

Start

End

End

Start

Step correction

Step correction

Program example

15 MONITOR FUNCTION 15.2 Scan Time Measurement 201

20

15.3 Specified Program Monitor This function checks (monitors) device/label values in the program specified by the engineering tool on the program editor and changes current values. Device/label values after the specified program is executed can be checked with this function, enabling debugging on a program basis.

To use the specified program monitor, check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

(1) The CPU module is executing three programs whose program names are "A", "B", and "C". (The order of program execution is A B C END processing A B ...)

(2) Specify program A using the monitor status bar. (3) Global device and global label values, and file register values of each program for program A can be checked. For current value change, values after

program A is executed will be changed.

(1)

(2)

(3)

A

B

C

END processing

Program A

Program B

Program C

Engineering tool

2 15 MONITOR FUNCTION 15.3 Specified Program Monitor

15

Setting the engineering tool When using the specified program monitor, in the option settings of the engineering tool, set "After the execution of specified program" under "Timing to Execute Monitor Function and Modify Value Function" to "Yes".

[Tool] [Options] [Monitor] [Common Item] [Timing to Execute Monitor Function and Modify Value Function] For details, refer to the following. GX Works3 Operating Manual

When a program for calling a subroutine exists When a program for calling a subroutine exists, to monitor or perform current value change on a local device on the subroutine side, a program to be specified varies depending on whether SM776 (Local device setting at CALL) is turned on or off.

Precautions The precautions for the specified program monitor are mentioned below. Monitoring cannot be performed if a program not stored in the CPU module is specified. Only one instance of the specified program monitor can be executed with one engineering tool. The specified program

monitor cannot be executed on multiple programs. When simultaneously executing the specified program monitor on separate personal computers with multiple engineering

tools, the specified program monitor can be executed from up to eight engineering tools. When not executing the specified program monitor, there is no limit to the number of simultaneous executions of monitoring and current value change.

When simultaneously executing the specified program monitor on the same personal computer with multiple engineering tools, whether to execute the monitor function of the engineering tool that was operated later can be selected. If selected, an error occurs for the engineering tool being executed.

When the initial execution type program, standby type program, fixed scan execution type program, or event execution type program (interrupt occurrence) is specified with the specified program monitor, it is executed in the same timing as the timing when no program is specified.

When the communication whose target is the device/label access service processing is performed while the specified program monitor is running, the scan time is extended because the processing is performed twice in one scan: after the specified program is performed and at a normal timing such as during the END processing.

The scan time extension can be reduced by preventing other communication while the specified program monitor is running.

To specify a program whose trigger type for the event execution type program is set to "ON of bit data (TRUE)" or "Passing time" using the specified program monitor, specify in a state in which the trigger is established. If the program is specified in a state in which the trigger is not established, the specified program monitor cannot be executed.

When the execution of the specified program monitor and the state in which the operating status of the CPU module is STOP overlap, if a file register whose "Use File Register of Each Program" is enabled is specified and an attempt is made to access the file register from other devices such as an external device, access is made to the file register of the program specified with the specified program monitor. If the write destination is changed, disable the specified program monitor before access.

While the specified program monitor is running, if the CPU module is set to STOP and the execution order of the target program is changed or the target program is deleted by using the program setting of the CPU parameter, do not write to the CPU module and execute RUN. Otherwise, the specified program monitor may not operate for the specified program.

SM776 setting Program to be specified OFF Specify the call source program.

ON Specify the call destination program.

15 MONITOR FUNCTION 15.3 Specified Program Monitor 203

20

16 TEST FUNCTION

16.1 External Input/Output Forced On/Off Function External inputs/outputs can be forcibly turned on and off from the engineering tool. This function enables input devices to be turned on and off regardless of the on/off state of the external inputs and enables the external outputs to be turned on and off regardless of the operation result of a program.

The external input/output forced on/off function is available for MELSEC iQ-R series modules and Q series modules mounted on an extension base unit.

Before executing the external input/output forced on/off function, check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

(External input) (External output)

(1) Turn off X0 forcibly. (2) The input device is turned off regardless of the on/off state of the external input. (3) Turn on Y0 forcibly. (4) The external output is turned on regardless of the operation result of the program.

(2)

(1)

(4)

(3)

4 16 TEST FUNCTION 16.1 External Input/Output Forced On/Off Function

16

Devices that allow forced on/off registration The following lists the devices that allow forced on/off registration.

Number of device points that allows forced on/off registration A maximum of 32 points can be registered for input devices and output devices in total.

Inputs/outputs for which forced on/off can be set The following describes the inputs/outputs for which forced on/off can be set.

Input After the refreshed data from the module is reflected, the input devices for which forced on/off registration is set are forcibly turned on or off.

Output The following external outputs are turned on or off by refreshing output devices that have been forcibly turned on or off.* 1

Refresh target output of modules mounted on the base unit Link refresh target output of network modules Link refresh target output of CC-Link IE Field Network Basic *1 When no modules are mounted on the base unit (no refresh targets), no data is output to the external outputs.

Device Range Input R00CPU, R01CPU, and R02CPU: X0 to X1FFF (8192 points)

Other CPU modules: X0 to X2FFF (12288 points)

Output R00CPU, R01CPU, and R02CPU: Y0 to Y1FFF (8192 points) Other CPU modules: Y0 to Y2FFF (12288 points)

16 TEST FUNCTION 16.1 External Input/Output Forced On/Off Function 205

20

Operation method of forced on/off Use the engineering tool for the forced on/off operation.

[Debug] [Register/Cancel Forced Input/Output]

Window

Displayed items

Item Description Device Enter target devices (X, Y).

[Register Forced ON] button Registers forced on for the entered devices (X, Y).

[Register Forced OFF] button Registers forced off for the entered devices (X, Y).

[Cancel Registration] button Cancels forced on/off for the registered devices (X, Y).

[Update Status] button Displays the latest on/off states.

[Cancel All Registrations] button Batch-cancels forced on/off for the registered devices (X, Y).

6 16 TEST FUNCTION 16.1 External Input/Output Forced On/Off Function

16

Behavior in forced on/off registration The following describes the behavior in forced on/off registration.

Behavior of an input device Registering forced on/off turns on or off the input device regardless of the status of the external input. When an input device for which the forced on/off has been registered is changed in the program, the input device is turned on and off in accordance with the operation result of the program.

*1 If the forced on/off is registered for a device set to perform link refresh, the device value may be updated at the timing of refresh. Thus, a different value from the operation result may be displayed when the device value is monitored (performed in END processing).

Behavior of an output device Registering forced on/off turns on or off the external output regardless of the operation result of the program. When an output device has been changed in the program, the output device is turned on and off in accordance with the operation result of the program. Therefore, the on/off states between the output device and external output may differ.

*1 If the forced on/off is registered for a device set to perform link refresh, the device value may be updated at the timing of refresh. Thus, a different value from the operation result may be displayed when the device value is monitored (performed in END processing).

CPU module operating status Forced on/off registration is allowed regardless of the CPU module operating status. However, when a stop error has occurred, the external outputs are turned off regardless of the forced on/off registration setting. While the operating status of the CPU module is STOP due to a stop error, forced on/off is enabled only for the input devices. If the CPU module is powered off and on or is reset, all the forced on/off registration information will be canceled.

Operation Change in the input device in the program Behavior of an input device Forced on registration Changed The input device is on when the program operation at every scan

starts. The input device is turned on or off in accordance with the operation

result of the program after the program operation at every scan started.*1

Not changed The on state is held.

Forced off registration Changed The input device is off when the program operation at every scan starts.

The input device is turned on or off in accordance with the operation result of the program after the program operation at every scan started.*1

Not changed The off state is held.

Operation Change in the output device in the program

Behavior of outputs

Behavior of an output device Behavior of an external output Forced on registration Changed The output device is on when the program

operation at every scan starts. The output device is turned on or off in

accordance with the operation result of the program after the program operation at every scan started.*1

The external output is turned on regardless of the operation result of the program.

Not changed The on state is held.

Forced off registration Changed The output device is off when the program operation at every scan starts.

The output device is turned on or off in accordance with the operation result of the program after the program operation at every scan started.*1

The external output is turned off regardless of the operation result of the program.

Not changed The off state is held.

16 TEST FUNCTION 16.1 External Input/Output Forced On/Off Function 207

20

Forced on/off timing The following table lists the timing to reflect the registered data in the forced on/off registration settings to the input/output devices or external outputs.

*1 For the precautions for using the direct access device, refer to the following. Page 211 Precautions

*2 At input/output refresh execution where input/output refresh is registered for each program, and for interrupt programs. *3 When an output device or external output is specified as a refresh device in multiple CPU refresh and the forced on/off function is

executed, the device is not forcibly turned on or off.

Inputs/outputs for which forced on/off can be set

Reflection timing for the input devices Reflection timing for the output devices or external outputs

Input/output of the modules mounted on the base unit

END processing (at input refresh) At COM instruction execution (at input refresh) At instruction execution using the direct access input (DX) (LD, LDI,

AND, ANI, OR, ORI, LDP, LDF, ANDP, ANDF, ORP, ORF, LDPI, LDFI, ANDPI, ANDFI, ORPI, ORFI)*1

At execution of the RFS instruction and MTR instruction At execution of instructions used in the interrupt by the system

(UDCNT1, UDCNT2, SPD) At program execution*2

At execution of the inter-module synchronization cycle program (I44) At execution of the multiple CPU synchronization program (I45) and

non-execution of the multiple CPU synchronization program (I45) (at END processing)*3

END processing (at output refresh) At COM instruction execution (at output

refresh) At instruction execution using the direct

access output (DY) (OUT, SET, DELTA(P), RST, PLS, PLF, FF, MC, SFT(P))*1

At execution of the RFS instruction and MTR instruction

At execution of instructions used in the interrupt by the system (PLSY, PWM)

At program execution*2

At execution of the inter-module synchronization cycle program (I44)

Input/output of the CPU module assigned to RX and RY of the CC-Link IE TSN master/local module

END processing (at link refresh) At ZCOM instruction execution (at link refresh)

Input/output of the CPU module assigned to LX and LY of the CC-Link IE Controller Network module or MELSECNET/H network module

END processing (at link refresh of the CC-Link IE Controller Network module or MELSECNET/H network module) At COM instruction execution (at link refresh of the CC-Link IE Controller Network module or MELSECNET/H

network module) At ZCOM instruction execution (at link refresh of the CC-Link IE Controller Network module or MELSECNET/H

network module)

Input/output of the CPU module assigned to RX and RY of the CC-Link module

END processing (at link refresh) At COM instruction execution (at link refresh) At ZCOM instruction execution (at link refresh)

Input/output of the CPU module assigned to RX and RY of the CC-Link IE Field Network module

END processing (at link refresh) At COM instruction execution (at link refresh) At ZCOM instruction execution (at link refresh) At execution of the inter-module synchronization cycle program (I44)

Input/output of the CPU module assigned to RX and RY of the CC-Link IE Field Network Basic

END processing (at link refresh) At COM instruction execution (at link refresh)

8 16 TEST FUNCTION 16.1 External Input/Output Forced On/Off Function

16

Checking the forced on/off execution status The execution status of the forced on/off can be checked in the following ways.

Engineering tool The execution status can be checked with the [Update Status] button of the engineering tool. ( Page 206 Operation method of forced on/off)

FUNCTION LED The FUNCTION LED of the CPU module flashes by registering forced on/off (every 200ms).

The LED indicator follows the status of the external input/output forced on/off function even when the LED Display Setting has been set and other functions that use the FUNCTION LED are being executed. ( Page 172 LED display setting)

The display status of the FUNCTION LED can be checked with "Module Information List" in the module diagnostics. ( GX Works3 Operating Manual)

Special register SD1488 (Debug function usage status) can be used to check whether the external input/output forced on/off function is used. ( Page 602 List of Special Register Areas)

16 TEST FUNCTION 16.1 External Input/Output Forced On/Off Function 209

21

Behavior in cancellation of forced on/off Forced on/off registration can be canceled for each input/output device individually.

Behavior of the device

CPU module operating status Forced on/off registration can be canceled regardless of the CPU module operating status.

LED status The following describes the LED status after forced on/off registration is canceled.

*1 When other functions that use the FUNCTION LED are being executed, the LED indicator changes its status in accordance with the status of the functions.

Inputs/outputs for which forced on/off can be set

Change in input/output devices in the program

Changed Not changed Input Input from the modules mounted on the

base unit The input device is turned on or off in accordance with the on/off state of the modules.

Input from RX of CC-Link IE TSN The input device is turned on or off in accordance with the on/off state refreshed from CC-Link IE TSN.

Input from LX of CC-Link IE Controller Network or MELSECNET/H

The input device is turned on or off in accordance with the on/off state refreshed from CC-Link IE Controller Network and MELSECNET/H.

Input from RX of CC-Link The input device is turned on or off in accordance with the on/off state refreshed from CC-Link.

Input from RX of CC-Link IE Field Network

The input device is turned on or off in accordance with the on/off state refreshed from CC-Link IE Field Network.

Input from RX of CC-Link IE Field Network Basic

The input device is turned on or off in accordance with the on/off state refreshed from CC-Link IE Field Network Basic.

Input other than above (input without modules actually mounted)

The input device is turned on or off in accordance with operation result of the program.

The input device is turned on or off in accordance with the registered on/off state.

Output Output to the modules mounted on the base unit

The operation result of the program is output. Data is output in accordance with the registered on/off state.

Output to RY of CC-Link IE TSN

Output to LY of CC-Link IE Controller Network or MELSECNET/H

Output to RY of CC-Link

Output to RY of CC-Link IE Field Network

Output to RY of CC-Link IE Field Network Basic

Output other than above (output without modules actually mounted)

The output device is turned on or off in accordance with operation result of the program. (Refresh to external output is not executed.)

The output device is turned on or off in accordance with the registered on/off state. (Refresh to external output is not executed.)

Forced on/off registration status of when the registration is canceled

FUNCTION LED status

Registered on/off information is remaining. Flashing (every 200ms)

No registered on/off information is remaining. Off*1

0 16 TEST FUNCTION 16.1 External Input/Output Forced On/Off Function

16

Behavior in batch-cancellation of forced on/off registrations All the forced on/off registrations can be canceled in a batch.

Behavior of the device The behavior of the device is the same as that of cancellation of forced on/off (for each device). ( Page 210 Behavior of the device)

CPU module operating status The behavior of the device is the same as that of cancellation of forced on/off (for each device). ( Page 210 CPU module operating status)

LED status The following describes the LED status after forced on/off registration is canceled in a batch.

*1 When other functions that use the FUNCTION LED are being executed, the LED indicator changes its status in accordance with the status of the functions.

Precautions The following describes precautions for using the external input/output forced on/off function. Multiple engineering tools connected to the network can be used to register forced on/off for the same CPU module. In this

case, note the following.

If a direct device is used in a program, forced on/off registration is reflected when an instruction is executed.

Ex.

When X0 is forcibly turned off

When the external input/output forced on/off function is executed while the program of high-speed internal timer interrupt (I48, I49) is executed, the interval of programs of high-speed internal timer interrupt is short, and a large number of forced on/off is registered, the scan time will increase and a WDT error may occur.

Execution of interrupt programs which are executed at a fixed scan may delay depending on the number of forced on/off registrations and the number of refresh points of each refresh processing.

When forced on/off is registered in the multiple CPU system configuration, registration is allowed for input/output devices*2 and external outputs regardless of the out-of-group I/O fetch setting*1. Note, however, that the devices of other CPU modules and the external outputs controlled by other CPU modules are not turned on or off even if forced on/off is registered from the host CPU for the external outputs controlled by other CPU modules. Only the devices of the host CPU module are turned on or off.

*1 For the out-of-group I/O fetch setting, refer to the following. Page 370 Out-of-group I/O fetch setting

*2 Except when the on/off state of the input/output devices is changed by using the output instruction

Forced on/off registration status of when the registration is canceled

FUNCTION LED status

No registered on/off information is remaining. Off*1

The forced on/off state registered last is handled as the on/off state of input/output devices. Since the on/off state displayed in engineering tools may differ from that of the CPU module, update the on/off state displayed in engineering tools.

When the input device (X0) is used When the direct input device (DX0) is used

Set X0 by using the SET instruction. Turn on X0 because the SET instruction is being executed.

Set X0 by using the SET instruction. Reflect the registered off information. Turn off X0 although the SET instruction is being executed.

16 TEST FUNCTION 16.1 External Input/Output Forced On/Off Function 211

21

16.2 Device Test with Execution Conditions Using the engineering tool, device/label values can be set for each execution of specified steps of programs. This function enables to debug a specific ladder block without modifying the program even when the program is configured as shown in the example below.

Before using the device test with execution conditions, check the version of the CPU module and the engineering tool used. ( Page 700 Added and Enhanced Functions)

(1) The device is operated in accordance with the registered settings. (M0 of the step number 10 is on.)

(1)

Program : MAIN Step number : 10 Device : M0 State : ON

Registration

Engineering tool

2 16 TEST FUNCTION 16.2 Device Test with Execution Conditions

16

Operation when device test with execution conditions is registered The device test with execution conditions can forcibly change device/label values (status) of specified locations. Specify a location of a device/label value (status) to be changed with a program name and a step number. In addition, specify a device/label and its value (status) to be changed with a device/label name and a setting value. Changes made to the device/label value (status) take effect in the specified step and later. However, when the device/label value (status) is changed due to operations of the program or other factors in the specified step and later, the device/label value (status) is changed accordingly. In the device test with execution conditions, a device/label value is changed in a specified step regardless of whether or not the instruction execution conditions are satisfied in the specified step. In the following example, the D0 value is changed to 35 regardless of the status (on/off) of M0.

Operation when device test with execution conditions is disabled The device/label value (status) when the registration is disabled is held. (It is not returned to the value (status) before execution of the device test with execution conditions.)

(1) The device test with execution conditions that sets D0 to 35 and is executed before execution of the instruction is registered to the step (100). (2) The device value in the specified step is changed regardless of the value (on/off) of M0.

OFF ON

D0

M0

10 35

+ K10

(1)

D0 M0

(100)

(2)

CPU module operation

Program

16 TEST FUNCTION 16.2 Device Test with Execution Conditions 213

21

Data that can be set The following tables list the data that can be set for the device test with execution conditions.

Devices that can be set

*1 For bit devices, digit specification is allowed for K1 to K8 only. *2 For word devices, bit specification is allowed. *3 A local device, indirectly-specified device, or index-modified device can also be specified. *4 The word devices of the other CPU modules, U3En\G and U3En\HG, can be specified in the engineering tool, however, the setting value

is not reflected in the CPU module. If U3En\G is specified, an error will occur.

Labels that can be set

*1 Only labels that exist in the read project can be specified. *2 Labels of a program block can be specified. *3 Digit-specified labels cannot be specified. *4 Bit specification is allowed. *5 Specify the array element. *6 Specify the structure member.

Type Device*3

Bit device*1 X, DX, Y, DY, M, L, F, SM, V, B, SB, T (contact), ST (contact), C (contact), LT (contact), LST (contact), LC (contact), FX, FY, Jn\X, Jn\Y, Jn\SB, Jn\B

Word device*2 T (current value), ST (current value), C (current value), D, SD, W, SW, RD, R, ZR, Z, FD, Un\G, Jn\W, Jn\SW, U3En\G*4, U3En\HG*4

Double-word device LT (current value), LST (current value), LC (current value), LZ

Type*1*2 Class Data type Global label VAR_GLOBAL

VAR_GLOBAL_RETAIN Primitive data type Bit*3

Word (signed)*4

Double word (signed) Word (unsigned)*4

Double word (unsigned) Single-precision real number Double-precision real number Timer type Retentive timer type Counter type Long timer type Long retentive timer type Long counter type

Array*5

Structure*6

Local label VAR VAR_RETAIN

4 16 TEST FUNCTION 16.2 Device Test with Execution Conditions

16

Programs that can be set Only ladder programs can be set for the device test with execution conditions.

Maximum number of devices/labels that can be set A total of 32 devices/labels can be set for the device test with execution conditions.

Checking execution status of device test with execution conditions The execution status can be checked in the following ways.

Engineering tool The execution status can be checked by displaying the list of registered settings with the engineering tool.

FUNCTION LED The FUNCTION LED of the CPU module flashes (every 200ms) by registering the device test with execution conditions.

When the device test with execution conditions is registered, the FUNCTION LED flashes regardless of the LED Display Setting in the RAS Setting. Even when the LED Display Setting has been set and other functions that use the FUNCTION LED are being executed, the LED indication at the registration of the device test with execution conditions takes priority. The LED indication is reset to the original state when the registration is disabled. (The LED indication follows the status of other functions that use the FUNCTION LED.) ( Page 172 LED display setting)

The display status of the FUNCTION LED can be checked with "Module Information List" in the module diagnostics. ( GX Works3 Operating Manual)

Special register SD1488 (Debug function usage status) can be used to check the usage status of the device test with execution conditions. ( Page 633 Debug function)

16 TEST FUNCTION 16.2 Device Test with Execution Conditions 215

21

Registration of device test with execution conditions This section describes how to register the device test with execution conditions.

Registration method Specify each field in the "Register Device Test with Execution Condition" window.

[Debug] [Device Test with Execution Condition] [Register]

Window

Setting data

Registration of multiple device tests with execution conditions to the same step Multiple device tests with execution conditions can be registered to one step. However, device tests with execution conditions that have the same device/label name and the same execution timing cannot be registered to one step. When such device tests with execution conditions are registered, the existing registration is overwritten with new registration.

Two device tests with execution conditions having different execution timing can be registered to one step even when they have the same device/label name.

Different device modification (bit specification of word device, digit specification of bit device, or index modification) is handled as different device name. Therefore, two device tests with execution conditions having different device modification can be registered to one step.

When bit device/bit type label is specified When word device/word type label is specified

Item Description Device/Label Set a device or a label to be registered. ( Page 214 Data that can be set)

Data Type Specify a data type. ( Page 214 Data that can be set)

[Forced ON] button These buttons appears when the data type is set to bit data. Click either button to register the forced on/off.[Forced OFF] button

Setting Value This field appears when the data type is set to word data. Enter a setting value in decimal or hexadecimal format. When setting a hexadecimal value, prefix the numerical value with "H". (Example: "H16", "H1F") Click the [Setting] button to register the value.

[Setting] button

Execution Condition Program Block Specify a program block.

Step No. Specify a step number for each program. To specify the step number, specify the start step of the instruction.

Execution Timing Specify whether to change the device/label value before or after the execution of the instruction of the specified step. ( Page 220 Execution timing)

6 16 TEST FUNCTION 16.2 Device Test with Execution Conditions

16

Checking and disabling settings from list window From the "Check/Disable Register Device Test with Execution Condition" window, the following operations can be performed: checking the registered settings, disabling selected settings, registering/disabling settings in batch, and reading/writing registered settings from/to a file.

[Debug] [Device Test with Execution Condition] [Check/Disable Register]

Window

Displayed items

The registered settings of the device test with execution conditions can be collectively disabled by the following operation in the engineering tool: [Debug] [Device Test with Execution Condition] [Batch Disable]

Item Description PLC Operation for Device Test Condition

[Update Status] button Click this button to read the registered settings of the device test with execution conditions in the CPU module. No data is read when this operation is performed with no settings registered.

[Disable Selected Conditions] buttons

Click this button to disable the selected registration of the device test with execution conditions that has been read from the CPU module by using the [Update Status] button.

[Batch Register] button All the existing registered settings of the device test with execution conditions in the CPU module are disabled by clicking this button, and the settings that have been read by using the [Update Status] button or [Read File] button are registered to the CPU module.

[Batch Disable] button Click this button to collectively disable the registered settings of the device test with execution conditions in the CPU module.

File Operation [Read File] button Click this button to read the registered settings of the device test with execution conditions, which have been saved by using the [Write File] button, and list them on the window.

[Write File] button Click this button to save the registered settings of the device test with execution conditions listed on the window into a file in the personal computer.

16 TEST FUNCTION 16.2 Device Test with Execution Conditions 217

21

Disabling device test with execution conditions In addition to the operations from the engineering tool, the following operations can be used to disable the device test with execution conditions. Powering off and on Resetting the CPU module Writing a program to the CPU built-in memory by writing data to the programmable controller while the CPU module is in

the STOP state*1*4

Deleting a program in the CPU built-in memory by deleting data in the programmable controller while the CPU module is in the STOP state*1

Initializing the CPU built-in memory while the CPU module is in the STOP state*1

Changing a program in the CPU built-in memory using the following SLMP commands while the CPU module is in the STOP state*1

Changing a program in the CPU built-in memory using the following FTP commands while the CPU module is in the STOP state*1

Restoring a program using the CPU module data backup/restoration function*1*4

Changing a program online (the online change (ladder block)*6 or the file batch online change) ( Page 221 Operation during online change)

Writing a global label to the CPU built-in memory by writing data to the programmable controller while the CPU module is in the STOP state*2*4

Deleting a global label in the CPU built-in memory by deleting data in the programmable controller while the CPU module is in the STOP state*2

Changing a global label in the CPU built-in memory using the following SLMP commands while the CPU module is in the STOP state*2*4

Changing a global label in the CPU built-in memory using the following FTP commands while the CPU module is in the STOP state*2

Restoring a global label using the CPU module data backup/restoration function*2*4

Writing CPU parameters to the CPU built-in memory by writing data to the programmable controller while the CPU module is in the STOP state*3*4

Deleting CPU parameters in the CPU built-in memory by deleting data in the programmable controller while the CPU module is in the STOP state*5

Changing the CPU parameter in the CPU built-in memory using the following SLMP commands while the CPU module is in the STOP state

Changing the CPU parameter in the CPU built-in memory using the following FTP commands while the CPU module is in the STOP state*5

Restoring a CPU parameter using the CPU module data backup/restoration function*3*4

Deleting a file (Delete File) (1822) Copying a file (Copy File) (1824)

Deleting a file (delete, mdelete) Changing a file name (rename)

Deleting a file (Delete File) (1822) Copying a file (Copy File) (1824)

Deleting a file (delete, mdelete) Changing a file name (rename)

Deleting a file (Delete File) (1822)*5

Copying a file (Copy File) (1824)*3

Deleting a file (delete, mdelete)

8 16 TEST FUNCTION 16.2 Device Test with Execution Conditions

16

*1 The registered settings of device test with execution conditions for the program to be changed are disabled when the operating status of the CPU module is changed from STOP to RUN after the operation. (They are not disabled at the completion of the operation.)

*2 All the registered settings that specify global labels are disabled when the operating status of the CPU module is changed from STOP to RUN after the operation. (They are not disabled at the completion of the operation.)

*3 When the CPU parameters are changed, all the registered settings that specify local devices or local labels are disabled when the operating status of the CPU module is changed from STOP to RUN after the operation. (They are not disabled at the completion of the operation.)

*4 When the same programs, global labels, or CPU parameters are written, the registered settings are not disabled. *5 All the registered settings of device test with execution conditions are disabled when the operating status of the CPU module is changed

from STOP to RUN after the operation. (They are not disabled at the completion of the operation.) *6 When the online change (ladder block) is performed while the CPU module is in the STOP state, the device test with execution

conditions registered for the program to be changed is disabled when the operating status of the CPU module is changed from STOP to RUN after the operation. (They are not disabled at the completion of the operation.)

16 TEST FUNCTION 16.2 Device Test with Execution Conditions 219

22

Execution timing Select whether to change the device/label value before or after the execution of the instruction of the specified step when registering the device test with execution conditions.

When the device test with execution conditions is registered with the step of the specific instruction specified, depending on the setting of the execution timing, the device/label may not be changed even if the specified step is executed. When the step of the following instructions is specified and the execution timing is set to "Before executing instruction", the device/label value is not changed by the device test with execution conditions even when execution conditions of the instruction are satisfied and the specified step is passed.

*1 When the execution timing is set to "After executing instruction", the device/label is changed when the execution condition of the instruction is not satisfied.

FOR instruction, NEXT instruction, FOR to NEXT instruction loop When the device test with execution conditions is registered with the step for the FOR instruction, the NEXT instruction, or the FOR to NEXT instruction loop specified, the timing to change the device/label differs from that when other instructions are specified.

END instruction When the step for the END instruction is specified, the execution timing cannot be set to "After executing instruction".

Program (1) The device test with execution conditions that sets 20 in D0 in step (100) is registered.

Setting of execution timing Operation of CPU module Before execution of the instruction in step (101)

(2) A value in D0 is changed to 20.

After execution of the instruction in step (101)

(3) A value in D0 is changed to 20.

Classification Instruction name Stop STOP*1

Jump CJ*1, SCJ*1, GOEND*1, JMP

Loop BREAK(P)*1

Ending a program FEND

Calling a subroutine program CALL(P)*1, FCALL(P)*1, ECALL(P)*1, EFCALL(P)*1, XCALL*1

Return RET, IRET

Instruction for specified step Specification detail of execution timing

Set to "Before executing instruction" Set to "After executing instruction" FOR Executed only once before starting the loop processing Executed only once after starting the loop processing

(Specified devices are changed before the execution of the program that is between the FOR and NEXT instructions.)

NEXT Executed only once after starting the loop processing (Specified devices are changed after the execution of the program that is between the FOR and NEXT instructions.)

Executed only once after ending the loop processing

FOR to NEXT instruction loop Executed only once before execution of the instruction at specified step in the FOR to NEXT instruction loop

Executed only once after execution of the instruction at specified step in the FOR to NEXT instruction loop

+ K100

(1)

D0 M0

(100)

+ K100 D0 M0

(100)

D0 10 20 120

(2)

+ K100 D0 M0

(100)

D0 10 110 20 (3)

0 16 TEST FUNCTION 16.2 Device Test with Execution Conditions

16

Operation during online change This section describes the operation performed during the online change of the CPU module to which the device test with execution conditions is registered.

Online change (ladder block) (without adding or deleting instruction) If a part to be changed by the online change (ladder block) includes registrations of the device test with execution conditions, such registrations are disabled. When the Registrations 1 to 3 of the device test with execution conditions are registered for the steps as shown below, the Registration 2 is disabled upon the execution of the online change (ladder block). The Registrations 1 and 3 are not disabled because the steps to which they are registered are not included in the part to be changed.

Registration 1 Registration 2

Registration 2

Registration 3

Before

Registration 1

Disabled

Registration 3

After

AND X12 is changed to AND X15.

16 TEST FUNCTION 16.2 Device Test with Execution Conditions 221

22

Online change (ladder block) (with adding instruction) When an instruction is added by the online change (ladder block), the registration of the device test with execution conditions of the instruction immediately after the instruction to be added is disabled. In the following example, an instruction is added by the online change (ladder block). In this case, when the device test with execution conditions is registered to the instruction immediately after the added instruction, the relevant registrations are disabled upon the execution of the online change (ladder block).

However, when an instruction to be added is adjacent to an instruction to be changed, the registration of the device test with execution conditions of the instruction immediately after the instruction to be added is not disabled. In the following example, an instruction to be added is adjacent to an instruction to be changed. Therefore, even when the device test with execution conditions is registered to the instruction immediately after the instruction to be added, the relevant registration is not disabled by the execution of the online change (ladder block).

(1) The registration of the device test with execution conditions of the instruction immediately after the instruction to be added is disabled.

(1) Although this instruction is located immediately after the added instruction, the registration of the device test with execution conditions is not disabled because the added instruction is adjacent to the changed instruction.

(2) The registration of the device test with execution conditions is disabled because the instruction is changed.

(1)

Registration 1 Registration 2 Registration 3

Before

Registration 1

Disabled

Registration 3Registration 2

After

AND M15 is added.

(2)

(1)

Registration 1 Registration 2 Registration 3

Before

Registration 1

Disabled

Registration 3Registration 2

After

AND X11 is changed to AND X16. AND M15 is added.

2 16 TEST FUNCTION 16.2 Device Test with Execution Conditions

16

Online change (ladder block) (with deleting instruction) When an instruction is deleted by the online change (ladder block), registrations of the device test with execution conditions for the deleted instruction and for the instruction immediately after the deleted instruction are disabled. In the following example, an instruction is deleted by the online change (ladder block). In this case, when the device test with execution conditions is registered to the instruction immediately after the deleted instruction, the relevant registrations are disabled upon the execution of the online change (ladder block).

However, when an instruction to be deleted is adjacent to an instruction to be changed, registration of the device test with execution conditions of the instruction immediately after the instruction to be deleted is not disabled. In the following example, an instruction to be deleted is adjacent to an instruction to be changed. Therefore, even when the device test with execution conditions is registered to the instruction immediately after the instruction to be deleted, the relevant registration is not disabled by the execution of the online change (ladder block).

(1) The registration of the device test with execution conditions is disabled because the instruction is located immediately after the deleted instruction. (2) The registration of the device test with execution conditions is disabled because the instruction where it is registered is deleted.

(1) Although this instruction is located immediately after the deleted instruction, the registration of the device test with execution conditions is not disabled because the deleted instruction is adjacent to the changed instruction.

(2) The registration of the device test with execution conditions is disabled because the instruction where it is registered is changed. (3) The registration of the device test with execution conditions is disabled because the instruction where it is registered is deleted.

(2)

(1)

Registration 1 Registration 2 Registration 3

Before

Registration 1 Registration 2

Disabled Disabled

Registration 3

After

AND M15 is deleted.

(3)(2)

(1)

Registration 1 Registration 2 Registration 3

Before

Registration 1 Registration 2

DisabledDisabled

Registration 3

After

AND X11 is changed to AND X16. AND M15 is deleted.

16 TEST FUNCTION 16.2 Device Test with Execution Conditions 223

22

Addition/deletion/change of labels by the online change (ladder block) When SM940 (Operation setting of the device test with execution conditions) is off, if local labels or program files are

added, deleted, or changed and the online change (ladder block) is performed, all the registrations that specify local labels of the relevant program file are disabled. When SM940 is on, the registrations are not disabled.* 1

When SM940 is off, if global labels are added, deleted, or changed and the online change (ladder block) is performed, all the registrations that specify global labels are disabled. When SM940 is on, the registrations are not disabled.* 1

*1 If reassignment of local labels/global labels which are used in the program is performed when SM940 is on, registrations including reassigned labels are disabled. When SM940 is on, do not delete or change local labels or global labels registered to device tests with execution conditions. If deleted or changed, registered settings may not be read correctly.

File batch online change All the device tests with execution conditions registered to the target program for the file batch online change are disabled. When global labels are added, deleted, or changed and the file batch online change is performed, all the registrations that specify global labels are disabled.

4 16 TEST FUNCTION 16.2 Device Test with Execution Conditions

16

Precautions This section describes the precautions on the use of the device test with execution conditions.

Operation when devices/labels cannot be registered When multiple devices/labels are registered to the device test with execution conditions, none of the devices/labels are registered if there is even one device/label or execution condition (program block, step number, or execution timing) that cannot be registered.

Operation from multiple engineering tools Multiple engineering tools connected to the network can be used to register the device test with execution conditions for the same CPU module. However, registration may fail if done simultaneously. If registration fails, register again. When the device tests with execution conditions are registered to the same device/label in the same location, the status (value) that is registered later takes effect. Before registering the device test with execution conditions from multiple engineering tools, update the data using "Update Status".

Mutual exclusion This section describes the mutual exclusion between the device test with execution conditions and other functions.

Device range check The following table lists the details of the device range check for each specification.

Specification of local device When local devices are registered to the device test with execution conditions, the write destination of the device values vary depending on the value of SM776 (Local device setting at CALL) and SM777 (Local device setting in interrupt programs). (Page 591 Instruction related)

Using together with interrupt programs When a step number in an interrupt program is specified as an execution condition of a device test with execution conditions, the processing time of the interrupt program increases by the processing time of the device test with execution conditions. For example, when the interrupt interval of I49 set in the parameter of "Interrupt Setting from Internal Timer" under "Fixed Scan Interval Setting" is as short as 0.05ms and a step number in I49 is specified as an execution condition of a device test with execution conditions, the processing time of the interrupt program may exceed the time set in "Fixed Scan Interval Setting". Therefore, a WDT error may occur due to continuous execution of the interrupt program. For how to reduce processing time of interrupt programs, refer to descriptions of interrupt programs. ( Page 99 Interrupt Program)

Other functions Operation Online change When the device test with execution conditions is registered or disabled during execution of the online change, an

error occurs and registering or disabling the device test with execution conditions fails.

Real-time monitor When execution of these functions is set for the same step as that specified by the device test with execution conditions, the device test with execution conditions is executed first.Data logging

Item Description Specification of device name by index modification

When an index-modified device is registered to the device test with execution conditions, the device range check is not performed. Therefore, the device value is not changed under the following conditions. The index-modified device is across the boundary of the device area. The index-modified device is out of the device range.

Specification of device name by indirect specification

When an indirectly-specified device is registered to the device test with execution conditions, the device range check is not performed. Therefore, the device value is not changed under the following conditions. The indirectly-specified device is across the boundary of accessible areas. The indirectly-specified device is out of the range accessible.

Specification of file register When file registers are registered to the device test with execution conditions, whether or not the register files are assigned and the range of the file registers are not checked. Therefore, file register values are not changed under the following conditions. File register files are not assigned. Specified device numbers of file register is out of the file register range.

16 TEST FUNCTION 16.2 Device Test with Execution Conditions 225

22

17 DATA LOGGING FUNCTION This function collects data at a specified interval or a desired timing and stores them as a file on the SD memory card or function memory*1. The entire data logging function allows the entry of up to 10 data logging settings.

*1 For the CPU modules that can use the function memory, refer to the availability of storage location. ( Page 259 Availability) *2 For details on the data to be collected, refer to the following. ( Page 230 Data to Be Collected) *3 For details on continuous logging and trigger logging, refer to the following. ( Page 237 Logging Type)

Without an SD memory card, the data logging can be performed by using the function memory and the file transfer together to save the data. ( Page 264 When the data storage destination memory is the function memory)

For the procedures for operating and configuring this function in CPU Module Logging Configuration Tool, refer to the following.

CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series)

This function cannot be used in the R00CPU.

The data logging function can be configured with CPU Module Logging Configuration Tool of the supported version (listed in the table below) or any later version.

CPU module Supported version of CPU Module Logging Configuration Tool R04CPU, R08CPU, R16CPU, R32CPU, R120CPU "1.35M" or later

R01CPU, R02CPU "1.76E" or later

2014/04/10 10:15:18 2014/04/10 10:15:19 2014/04/10 10:15:20 2014/04/10 10:15:21 2014/04/10 10:15:22

OFF, 10 ON, 11 ON, 12 ON, 11 OFF, 10

SD memory card

CPU module

Word device/label

Bit device/label

Data logging file

Trigger logging (when conditions are satisfied)*3

Continuous logging (always)*3

Interval of the collection

Target data*2

Function memory*1

or

6 17 DATA LOGGING FUNCTION

17

17.1 Data Logging Procedure This section describes the data logging procedure.

1. Install CPU Module Logging Configuration Tool. ( CPU Module Logging Configuration Tool/GX LogViewer Installation Instructions (BCN-P5999-0506))

2. Launch CPU Module Logging Configuration Tool.

3. When specifying a label as the target data, import the project of the engineering tool to CPU Module Logging Configuration Tool.

4. Configure the data logging setting. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

5. If auto logging is used, configure the common settings (auto logging common settings). ( Page 285 Auto logging common setting)

6. When the storage destination of the data logging files is the SD memory card, insert an SD memory card into the CPU module, and power up the module.

7. Connect the CPU module to a personal computer.

8. Write the data logging setting to the SD memory card or data memory.

9. Switch the CPU module to RUN state to start the data logging.

10. Stop the data logging and read the data logging file.

11. Check the file into which data has been read.

To start data logging, always click the [Start] button in the "Logging Status and Operation" window of CPU Module Logging Configuration Tool. The data logging cannot be started even when the setting is written and power is turned off and on or the CPU module is reset (except for the auto logging).

For the operation procedures for CPU Module Logging Configuration Tool, refer to the following. CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series)

17 DATA LOGGING FUNCTION 17.1 Data Logging Procedure 227

22

17.2 Specifications This section describes the data logging specifications.

Item Specifications Reference Number of data logging settings 10*1

Data collection

Collection interval Every scan operation Time specification Interrupt occurrence Condition specification (device/label specification, step No.

specification)

Page 232 Data Collection Conditions

Number of points for collection Maximum of 1280 (128 per setting)

AND conjunction AND conjunction of the device/label specification and step No. specification is enabled.

Logging type Continuous logging Trigger logging

Page 237 Logging Type

Data processing

Trigger logging

Trigger condition Condition specification (device/label change specification, step No. specification)

When trigger instruction executed

Page 238 Operating procedure for trigger logging

AND conjunction AND conjunction of the device/label change specification and step No. specification is enabled.

Trigger logging range Number of records specified before and after the trigger establishment

Number of trigger establishments (number of events that can be handled as trigger)

One time

Number of records SD memory card Maximum of 1000000 CPU built-in memory (function memory) Maximum of 50000

File output File name Additional information plus file number Page 242 Data Logging File

File storage format Unicode text file CSV file*3

Binary file

Data type Bit Word (signed) Double word (signed) Word (unsigned) Double word (unsigned) Single-precision real number Double-precision real number String Numeric string Time

Data output format

Unicode text file Decimal format Hexadecimal format Decimal fraction format Exponential format

CSV file Decimal format Hexadecimal format Decimal fraction format Exponential format

Binary file Word (signed) Double word (signed) Word (unsigned) Double word (unsigned) Single-precision real number Double-precision real number

Storage location of data logging files SD memory card CPU built-in memory (function memory)*2

Page 259 Storage location of data logging files

8 17 DATA LOGGING FUNCTION 17.2 Specifications

17

*1 When the storage destination of the data logging files is the function memory, up to two data loggings can be executed simultaneously even though 10 data loggings can be set. However, up to 10 data loggings can simultaneously be executed depending on the firmware version and production information of the CPU module. ( Page 700 Added and Enhanced Functions)

*2 When using the CPU built-in memory (function memory) as the storage location, check the firmware version of the CPU module and the version of the CPU Module Logging Configuration Tool. ( Page 700 Added and Enhanced Functions) The data logging file stored in the CPU built-in memory can be transferred to the FTP server by using the data logging file transfer function. (Page 273 Data Logging File Transfer (Auto Transfer to FTP Server)) If the data logging file transfer function is not set, the files are transferred to the data memory. ( Page 282 Data Logging File Transfer to Data Memory)

*3 Check the firmware version of the CPU module and the version of CPU Module Logging Configuration Tool. ( Page 700 Added and Enhanced Functions)

Output file handling

Storage file switching

File switching timing Number of records File size Condition specification*3

Page 267 Switching to a storage file

Maximum number of storage files

1 to 65535

Data logging file transfer function This function automatically transfers data logging files to the FTP server.

Page 273 Data Logging File Transfer (Auto Transfer to FTP Server)

Operation settings when entering into RUN mode This function sets data logging operations when entering into RUN mode after the data logging setting is registered.

Page 283 Setting Behavior at the Time of Transition to RUN

Auto logging When inserting an SD memory card, which holds data logging setting, into the CPU module, the data logging automatically starts based on the data logging setting information on the SD memory card.

Page 284 Auto Logging

SD memory card replacement SD memory cards can be replaced using the SD memory card forced disable function even when the data logging is in progress.

Page 288 SD Memory Card Replacement

Item Specifications Reference

17 DATA LOGGING FUNCTION 17.2 Specifications 229

23

17.3 Data to Be Collected This section describes the data to be collected by data logging.

Number of data points The data logging function can collect up to 1280 data records. (10 settings 128 records)*1

*1 Duplicate data records are counted as distinct.

Data type The following table shows the number of data records for each data type.

*1 The entered character code are output. *2 The specified size can be 1 to 256. If the specified size is an odd number, the number of data records is rounded to the next higher

integer. Example: The number of data records is 3 if the specified size is 5.

Data to be collected The following table lists the data to be collected.

*1 When specifying the local device, global label, or local label, check the versions of the CPU module, engineering tool, and CPU Module Logging Configuration Tool. ( Page 700 Added and Enhanced Functions)

When specifying a label, save the project of the engineering tool that contains the label in advance because the project is imported into CPU Module Logging Configuration Tool.

To use a device and a label at the same time, specify them in different data logging settings. To specify the local devices of multiple programs, specify them in different data logging settings. To specify the local labels of multiple programs, specify them in different data logging settings.

Data type Number of data points Bit 1

Word (signed) 1

Double word (signed) 2

Word (unsigned) 1

Double word (unsigned) 2

Single-precision real number 2

Double-precision real number 4

Time 2

String*1 Specified size/2*2

Numeric string Specified size/2*2

Data Description Global device In a single data logging setting, the device and label cannot be specified at the same time.

Local device*1 In a single data logging setting, only the local device of a single program can be specified. In a single data logging setting, the device and label cannot be specified at the same time.

Global label*1 In a single data logging setting, the label and device cannot be specified at the same time.

Local label*1 In a single data logging setting, only the local label of a single program can be specified. In a single data logging setting, the label and device cannot be specified at the same time.

0 17 DATA LOGGING FUNCTION 17.3 Data to Be Collected

17

Devices to be collected The following table lists the devices that can be specified as the collected data.

*1 An index modified device and indirectly specified device cannot be specified. *2 For bit devices, digit specification is allowed for K1 to K8 only. *3 For word devices, bit specification is allowed. *4 To specify the local device, use "Program name/#Device name". (Example: "MAIN/#M1") *5 To specify these devices with CPU Module Logging Configuration Tool, use T (contact): TS, T (coil): TC, ST (contact): STS, ST (coil):

STC, C (contact): CS, C (coil): CC, LT (contact): LTS, LT (coil): LTC, LST (contact): LSTS, LST (coil): LSTC, LC (contact): LCS, and LC (coil): LCC.

*6 The device can be collected by using the CPU module where the SFC function can be used. ( Page 700 Added and Enhanced Functions)

Labels to be collected The following table lists the labels that can be specified to be collected.* 1*2

*1 A label with a name of 256 characters or less can be specified. When the local label is specified (program block name/label name), the "program block name/" part is counted as the number of characters.

*2 Only labels in the read project of the engineering tool can be specified. *3 Specify the label with "Program block name/Label name". (Example: "ProgPou/label_w1") *4 Digit-specified labels cannot be specified. *5 Bit specification is allowed. *6 For the label of timer type and counter type, specify the element name. (S: contact, C: coil, N: current value)

Global label example: "label_w1.S" Local label example: "ProgPou/label_w1.S"

*7 Specify the array element. If the array element is not specified, it is handled as the start of the array ([0]). ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

*8 Specify the structure member. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

When specifying a label, save the project of the engineering tool that contains the label in advance because the project is imported into CPU Module Logging Configuration Tool.

Type Device*1

Bit device*2 X, DX, Y, DY, M*4, L, F, SM, V*4, B, SB, T (contact)*4*5, T (coil)*4*5, ST (contact)*4*5, ST (coil)*4*5, C (contact)*4*5, C (coil)*4*5, LT (contact)*4*5, LT (coil)*4*5, LST (contact)*4*5, LST (coil)*4*5, LC (contact)*4*5, LC (coil)*4*5, FX, FY, Jn\X, Jn\Y, Jn\SB, Jn\B, BLn\S*6

Word device*3 T (current value)*4, ST (current value)*4, C (current value)*4, D*4, SD, W, SW, RD, R, ZR, Z, FD, Un\G, Jn\W, Jn\SW, U3En\G, U3En\HG

Double-word device LT (current value)*4, LST (current value)*4, LC (current value)*4, LZ

Type Class Data type Global label VAR_GLOBAL

VAR_GLOBAL_RETAIN Primitive data type/array*7

Bit*4

Word (signed)*5

Double word (signed) Word (unsigned)*5

Double word (unsigned) Single-precision real number Double-precision real number Time String Timer type*6

Retentive timer type*6

Counter type*6

Long timer type*6

Long retentive timer type*6

Long counter type*6

Structure*8

Local label*3 VAR VAR_RETAIN

17 DATA LOGGING FUNCTION 17.3 Data to Be Collected 231

23

17.4 Data Collection Conditions This section describes the timing when data is collected and the conditions under which data is collected.

Each scan Data are collected during the END processing of each scan.

Time specification Specify the collection time interval. Specify the timing of data collection using advanced settings as well.

Data collection at specified time interval Data are collected at specified time interval.

Ex.

10 milliseconds (10ms)

Data collection conditions Description Each scan Collects data during the END processing of each scan.

Time specification

Data collection at specified time interval Collects data at specified time interval.

Data collection during the END processing after specified time interval

Collects data during the END processing after specified time interval.

Interrupt occurrence Collects data at specified time interval after the execution of an interrupt program.

Condition specification

Device/label specification Collects data when the monitored data meets the specified condition during the END processing.

Step No. specification Collects data when the specified condition is met immediately before the execution of the specified step.

0 END 0 END 0 END 0 END 0 ENDProgram

Scan time Scan time Scan time Scan time Scan time

END processing END processing END processing END processing END processing

Sampling Sampling Sampling Sampling Sampling

10ms 10ms 10msSet time

Sampling Sampling

2 17 DATA LOGGING FUNCTION 17.4 Data Collection Conditions

17

Data collection during the END processing after specified time interval This option causes data collection to be performed at the timing of the END processing rather than during the course of program execution. Ensure that the "Scan time" is less than "Time specification". If the scan time is longer than the specified time and the collection interval or the collection timing occurs more than once during the same scan, data is collected only once during the END processing. Data collection is performed on a scan by scan basis, which is the same behavior as when "Each scan" is used.

Ex.

10 milliseconds (10ms)

Interrupt occurrence Data are collected at specified time interval after the execution of an interrupt program. The time interval is specified by "Interrupt cycle specified sampling intervals" "Interval". Interrupt pointers which can be specified are I28 to I31, I44, I45, I48, and I49.

Ex.

When multiple CPU synchronous interrupt (I45) is used (multiple CPU synchronous interrupt is set to 0.22 milliseconds (0.22ms) and interval to 3):

Since data collection is performed at the timing of the execution of the interrupt program, data is collected only when all of the following conditions are met: The specified interrupt meets the operating condition. The specified interrupt pointer exists in the program. The current state is an EI state and the interrupt mask of the interrupt pointer has been reset.

0 END 0 END 0 END 0 END 0 END

10ms 10ms 10ms

Program

END processing

Sampling

END processing END processing

Sampling

END processing END processing

Set time

1 scan

0.22ms 0.22ms0.22ms 0.22ms0.22ms0.22ms 0.22ms Sampling

Interrupt program execution

Interrupt

Sampling

Interrupt program execution

Interrupt

Interrupt program execution

Interrupt

Interrupt program execution

Interrupt

Sampling

Interrupt program execution

Interrupt

Interrupt program execution

Interrupt

Interrupt program execution

Interrupt

Fixed scan communication cycle

17 DATA LOGGING FUNCTION 17.4 Data Collection Conditions 233

23

Condition specification Specify the data collection timing according to the device/label data conditions and step number. The AND condition using a combination of "Device specification", "Label specification", and "Step No. specification" results in the collection of data at the time when both conditions are established.

Device/label specification Data are collected when the monitored data meets the specified condition during the END processing.

To collect data continuously while the conditions are met The following conditional formula causes the data logging function to collect data continuously while the conditions are met: =: When the current value of the monitored data is equal to the comparison value : When the current value of the monitored data is not equal to the comparison value : When the current value of the monitored data is equal to or larger than the comparison value >: When the current value of the monitored data is larger than the comparison value : When the current value of the monitored data is equal to or smaller than the comparison value <: When the current value of the monitored data is smaller than the comparison value

To collect data only when the state changes The following conditional formula causes the data logging function to collect data only during the END processing for the scans where the conditional formula is met. It does not collect data for any single scan where the conditional formula is not met during the END processing (even if the conditional formula is met before the END processing is initiated). : When the specified data turns off and on : When the specified data turns on and off At change: When the current value of the specified data changes

(1) During the END processing, the data logging function does not collect data because the conditions are not met.

(1) The data logging function does not collect data because there has been no change in state since the last scan.

0 END 0 END 0 END 0 END 0 END

(1)

1 scan

Program

END processing

Sampling

END processing

Sampling

END processing END processing

Word value Set value Current value Set value Current valueSet value = Current value

END processing

0 END 0 END 0 END 0 END 0 END

(1)

Word value

1 scan

Program

END processing

Sampling Sampling

END processing END processing END processing END processing

Set value = 0 (initial value) Set value = 2Set value = 1

4 17 DATA LOGGING FUNCTION 17.4 Data Collection Conditions

17

Specifying the monitored data For monitored data, the following devices and labels can be specified.* 1

*1 When specifying the local device, global label, or local label, check the versions of the CPU module, engineering tool, and CPU Module Logging Configuration Tool. ( Page 700 Added and Enhanced Functions)

The data types that can be selected include bit/word (unsigned), word (signed), double word (unsigned), and double word (signed).

*2 An index modified device and indirectly specified device cannot be specified. *3 For bit devices, digit specification is not supported. *4 For word devices, bit specification is allowed. *5 To specify the local device, use "Program name/#Device name". (Example: "MAIN/#M1") *6 To specify these devices with CPU Module Logging Configuration Tool, use T (contact): TS, ST (contact): STS, C (contact): CS, LT

(contact): LTS, LST (contact): LSTS, and LC (contact): LCS. *7 The device can be collected by using the CPU module where the SFC function can be used. ( Page 700 Added and Enhanced

Functions)

*8 A label with a name of 256 characters or less can be specified. When the local label is specified (program block name/label name), the "program block name/" part is counted as the number of characters.

*9 Only labels in the read project of the engineering tool can be specified. *10 Specify the label with "Program block name/Label name". (Example: "ProgPou/label_w1") *11 Digit-specified labels cannot be specified. *12 Bit specification is allowed. *13 Only the contacts and current values can be specified. *14 For the label of timer type and counter type, specify the element name. (S: contact, N: current value)

Global label example: "label_w1.S" Local label example: "ProgPou/label_w1.S"

*15 Specify the array element. If the array element is not specified, it is handled as the start of the array ([0]). ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

*16 Specify the structure member. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

Type Device*2

Device Bit device*3 X, Y, M*5, L, F, SM, V*5, B, SB, T (contact)*5*6, ST (contact)*5*6, C (contact)*5*6, LT (contact)*5*6, LST (contact)*5*6, LC (contact)*5*6, FX, FY, Jn\X, Jn\Y, Jn\SB, Jn\B, BLn\S*7

Word device*4 T (current value)*5, ST (current value)*5, C (current value)*5, D*5, SD, W, SW, RD, R, ZR, Z, FD, Un\G, Jn\W, Jn\SW, U3En\G, U3En\HG

Double-word device LT (current value)*5, LST (current value)*5, LC (current value)*5, LZ

Type Class Data type Label*8*9 Global label VAR_GLOBAL

VAR_GLOBAL_RETAIN Primitive data type/array*15

Bit*11

Word (signed)*12

Double word (signed) Word (unsigned)*12

Double word (unsigned) Timer type*13*14

Retentive timer type*13*14

Counter type*13*14

Long timer type*13*14

Long retentive timer type*13*14

Long counter type*13*14

Structure*16

Local label*10 VAR VAR_RETAIN

17 DATA LOGGING FUNCTION 17.4 Data Collection Conditions 235

23

Step No. specification Data are collected when the specified condition is met immediately before the execution of the specified step.

To collect data continuously while the execution conditions are met The following execution conditions cause the data logging function to collect data continuously while the execution condition are met: Always: The specified step is executed regardless of the state immediately before the execution of it. In the specified condition satisfied: The specified step is executed if the state immediately before the execution is a running

state. In the specified condition not satisfied: The specified step is executed if the state immediately before the execution is not a

running state.

To collect data only when the execution conditions are met The following execution conditions cause the data logging function to collect data only when the execution conditions are met: On the rising edge of the specified condition: The specified step is executed if the state changes from non-running to

running immediately before the execution of it. On the falling edge of the specified condition: The specified step is executed if the state changes from running to non-

running immediately before the execution of it.

If the specified step is contained between FOR and NEXT loop of instructions, the data logging function collects the data for only the first iteration of the loop where the specified conditions are met.

Since the step number cannot be checked in the following programs, the step number cannot be specified. Program having multiple parts ST program FB program SFC program

(1) The data logging function collects data because the state immediately before the execution of the specified step is a running state.

(2) It does not collect data because the state immediately before the execution of the specified step is not a running state.

(1) The data logging function collects data because the state changes from running to non-running immediately before the execution of the specified step.

(2) The data logging function does not collect data because there has been no change in state since the last scan.

(1)

(2)

(1)

0 END 0 END 0 END 0

Execution

Not execution

Program

Sampling Sampling

END processing END processing END processing

Status just before the execution of the specified step

0 END 0 END 0 END 0

(1)

(2)

Execution

Not execution

Program

Sampling

END processing END processing END processing

Status just before the execution of the specified step

6 17 DATA LOGGING FUNCTION 17.4 Data Collection Conditions

17

17.5 Logging Type The following table describes available methods of data collection:

Operating procedure for continuous logging In continuous logging, the CPU module stores specified data in its internal buffer at a specified collection interval or timing and, at the time of a file save operation, it saves the data in a data logging file residing in the storage memory.

1. Write the settings into data memory or SD memory card using CPU Module Logging Configuration Tool.

2. Operate CPU Module Logging Configuration Tool to start data logging. The data logging settings are registered and continuous logging begins. (The special relay (data logging start) turns on.)

3. Data collection finishes upon reaching "Number of files to be saved" specified as part of the "Stop" setting configured in "Operation when exceeds the number of files".

4. Specify the desired file in the storage memory to read the results of data logging.

In continuous logging, data logging files are continuously created, thus allowing the user to read the results of data logging any time without having to wait for the completion of collection.

To stop continuous logging The user can completely stop data logging by instructing CPU Module Logging Configuration Tool to stop data logging and unregister the data logging settings stored in the CPU module. (The special relay (data logging start) turns off.)

To suspend/resume continuous logging The user can suspend data logging with the data logging settings remaining intact by doing either of the following: Instruct CPU Module Logging Configuration Tool to suspend data logging (the special relay (data logging start) turns off). Turn off and on the special relay (Data logging suspend/resume flag). To resume continuous logging from suspension, do either of the following: Instruct CPU Module Logging Configuration Tool to resume data logging (the special relay (data logging start) turns on). Turn on and off the special relay (Data logging suspend/resume flag).

Logging type Data collection method Application Continuous logging Continuously collects specified data at specified interval or timing. Allows the user to continuously monitor the content of

specified data.

Trigger logging Collects specified data at specified interval or timing and extracts a specified number of data records before and after the satisfaction of a trigger condition.

Allows the user to monitor the content of specified data before and after the satisfaction of a trigger condition.

17 DATA LOGGING FUNCTION 17.5 Logging Type 237

23

Operating procedure for trigger logging In trigger logging, the CPU module stores specified data in its internal buffer at a specified collection interval or timing; it extracts a specified number of data records before and after the satisfaction of a trigger condition and saves the extracted data in a data logging file residing in the storage memory. Note that data collection is performed not only at the specified collection interval or timing but also when a trigger condition is met. In addition, once a trigger condition is met, any subsequent trigger conditions are ignored.

1. Write the settings into data memory or SD memory card using CPU Module Logging Configuration Tool.

2. Instruct CPU Module Logging Configuration Tool to start data logging. The data logging settings are registered and trigger logging begins. (The special relay (data logging start) turns on.)

3. Wait until the trigger condition is met. (Trigger standby)

4. The data specified in CPU Module Logging Configuration Tool is collected. (Trigger condition met)

5. Data collection is completed by collecting as much data as the number of records specified in CPU Module Logging Configuration Tool and writing the collected data into the storage memory.

6. Specify the desired file in the storage memory to read the results of data logging.

Trigger Condition The following table lists the conditions to be used as a trigger.

The AND condition using a combination of "Device/Label change specification" and "Step No. specification" results in the collection of data at the time when both conditions are established.

Device/label change specification A trigger occurs when the monitored data meets the specified condition.

Trigger condition Description Condition specification Device/label change

specification A trigger occurs when the monitored data meets the specified condition.

Step No. specification A trigger occurs when the specified condition is met immediately before the execution of the specified step.

When trigger instruction executed A trigger occurs when the LOGTRG instruction is executed.

Conditional formula Description When the specified data turns off and on

When the specified data turns on and off

= When the monitored data is equal to the comparison value, regardless of whether or not its current value is equal.

When the monitored data is not equal to the comparison value, regardless of whether or not its current value is equal.

When the monitored data is greater than or equal to the comparison value, regardless of whether or not its current value is equal.

> When the monitored data is greater than the comparison value, regardless of whether or not its current value is equal.

When the monitored data is less than or equal to the comparison value, regardless of whether or not its current value is equal.

< When the monitored data is less than the comparison value, regardless of whether or not its current value is equal.

At change When the current value of the specified data changes

8 17 DATA LOGGING FUNCTION 17.5 Logging Type

17

Specifying the monitored data For the device and label change specification, monitored data can be configured to be collected from the devices and labels listed in the following table.* 1

*1 When specifying the local device, global label, or local label, check the versions of the CPU module, engineering tool, and CPU Module Logging Configuration Tool. ( Page 700 Added and Enhanced Functions)

The data types that can be selected include bit/word (unsigned), word (signed), double word (unsigned), and double word (signed). If double word (unsigned) or double word (signed) is specified, a trigger occurs only when as much data as one double word is written. No trigger occurs when only the upper or lower word of a double word is written.

*2 An index modified device and indirectly specified device cannot be specified. *3 For bit devices, digit specification is not supported. *4 For word devices, bit specification is allowed. *5 To specify the local device, use "Program name/#Device name". (Example: "MAIN/#M1") *6 To specify these devices with CPU Module Logging Configuration Tool, use T (contact): TS, ST (contact): STS, C (contact): CS, LT

(contact): LTS, LST (contact): LSTS, and LC (contact): LCS.

*7 A label with a name of 256 characters or less can be specified. When the local label is specified (program block name/label name), the "program block name/" part is counted as the number of characters.

*8 Only labels in the read project of the engineering tool can be specified. *9 Specify the label with "Program block name/Label name". (Example: "ProgPou/label_w1") *10 Digit-specified labels cannot be specified. *11 Bit specification is allowed. *12 Only the contacts and current values can be specified. *13 For the label of timer type and counter type, specify the element name. (S: contact, N: current value)

Global label example: "label_w1.S" Local label example: "ProgPou/label_w1.S"

*14 Specify the array element. If the array element is not specified, it is handled as the start of the array ([0]). ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

*15 Specify the structure member. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

Type Device*2

Device Bit device*3 X, Y, M*5, L, F, SM, V*5, B, SB, T (contact)*5*6, ST (contact)*5*6, C (contact)*5*6, LT (contact)*5*6, LST (contact)*5*6, LC (contact)*5*6, FX, FY

Word device*4 T (current value)*5, ST (current value)*5, C (current value)*5, D*5, SD, W, SW, RD, R, ZR, Z, FD

Double-word device LT (current value)*5, LST (current value)*5, LC (current value)*5

Type Class Data type Label*7*8 Global label VAR_GLOBAL

VAR_GLOBAL_RETAIN Primitive data type/array*14

Bit*10

Word (signed)*11

Double word (signed) Word (unsigned)*11

Double word (unsigned) Timer type*12*13

Retentive timer type*12*13

Counter type*12*13

Long timer type*12*13

Long retentive timer type*12*13

Long counter type*12*13

Structure*15

Local label*9 VAR VAR_RETAIN

17 DATA LOGGING FUNCTION 17.5 Logging Type 239

24

Step No. specification A trigger occurs when the specified condition is met immediately before the execution of the specified step.

If the specified step is contained between FOR and NEXT loop of instructions, only the first iteration of the loop where the specified conditions are met is handled as a trigger.

Since the step number cannot be checked in the following programs, the step number cannot be specified. Program having multiple parts ST program FB program SFC program

When a step number in an interrupt program is specified, the trigger condition may not be met.

When trigger instruction executed A trigger occurs when the LOGTRG instruction is executed. ( MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks))

When the LOGTRG instruction is used in an interrupt program, the trigger condition may not be met.

Execution condition Description Always Executes the specified step regardless of the state immediately before the execution of it.

In the specified condition satisfied Executes the specified step if the state immediately before the execution is a running state.

In the specified condition not satisfied Executes the specified step if the state immediately before the execution is not a running state.

On the rising edge of the specified condition

Executes the specified step if the state changes from non-running to running immediately before the execution of it.

On the falling edge of the specified condition

Executes the specified step if the state changes from running to non-running immediately before the execution of it.

(1) The state changes from non-running to running immediately before the execution of the specified step.

0 END 0 END 0 END 0

(1)

Execution

Not execution

Program

Sampling

Trigger occurrence

END processing END processing END processing

Data sampling before trigger Data sampling after trigger

Status just before the execution of the specified step

0 17 DATA LOGGING FUNCTION 17.5 Logging Type

17

To stop trigger logging The user can completely stop data logging by instructing CPU Module Logging Configuration Tool to stop data logging and unregister the data logging settings stored in the CPU module. (The special relay (data logging start) turns off.)

To suspend/resume trigger logging The user can suspend data logging with the data logging settings remaining intact by doing either of the following: Instruct CPU Module Logging Configuration Tool to suspend data logging (the special relay (data logging start) turns off). Turn off and on the special relay (Data logging suspend/resume flag). To resume trigger logging from suspension, do either of the following: Instruct CPU Module Logging Configuration Tool to resume data logging (the special relay (data logging start) turns on). Turn on and off the special relay (Data logging suspend/resume flag).

Number of records Specify the number of records to be collected before and after the satisfaction of a trigger condition. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

*1 This number includes the record exactly at the time when the trigger condition is met.

After starting data logging, if the trigger condition is met before data collection of the specified number of records (before trigger) is completed, the number of sampled records will be less than the specified.

Collected data

Trigger condition occurrence

Number of records before trigger

Number of records after trigger*1

Trigger logging start

Total number of records

Trigger logging completion

17 DATA LOGGING FUNCTION 17.5 Logging Type 241

24

17.6 Data Logging File This section describes data logging files.

Storage format of data logging files The following storage formats are available for data logging files.

*1 When setting the data logging file storage format to the CSV file format, check the firmware version of the CPU module and the version of the CPU Module Logging Configuration Tool. ( Page 700 Added and Enhanced Functions)

*2 If any character that cannot be converted to ASCII or Shift-JIS is used in the data name (device/label name), device comment, or program name, the corresponding data is output as "." (single-byte period).

File format Application Reference Unicode text file format This is a file format which can be opened in generic-purpose application programs such

as Excel and Notepad. GX LogViewer is also available for displaying data. Page 243 Unicode text file output type

CSV file format*1*2 This is a file format which can be opened in generic-purpose application programs such as Excel and Notepad. GX LogViewer is also available for displaying data. Select this format when saving data together with the output data of MELSEC-Q series.

Page 248 CSV file output format

Binary file format Comparing the Unicode text file format, the size of files is small and therefore quicker access to files is provided. GX LogViewer is also available for displaying data.

Page 254 Binary file output format

2 17 DATA LOGGING FUNCTION 17.6 Data Logging File

17

Data output format This section describes each of file output types.

Unicode text file output type This section describes the format specifications of the Unicode text file output type and output content of each data. Format specifications

*1 When double quotation marks (" ") and/or commas (,) are included in the output data, the following processing occurs: When the data includes commas (,), whole data is enclosed by double quotation marks (" "). When the data includes double quotation marks (" "), another set of double quotation marks will be appended to each of them.

File format example Output items can be specified. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

*2 Information on the program name row appears when the version of CPU Module Logging Configuration Tool is "1.82L" or later and local devices or labels are specified. When the version is "1.76E" or earlier, or the version is "1.82L" or later and only global devices are specified, the information on the program name row does not appear.

Item Description Delimiter Tab

Return code CRLF (0x0D, 0x0A)

Character code Unicode

Character encoding schema UTF-16 (Little-Endian)

Field data Not enclosed by double quotation marks (" ") Double quotation marks (" ") and commas (,) cannot be used in each data.*1

[LOGGING]

LOG01

DATETIME[YYYY/MM/DD hh:mm:ss.sss]

TIME(UTC+09:00)

2014/10/01 12:01:00,000

2014/10/01 12:02:00,000

2014/10/01 12:03:00,000

2014/10/01 12:04:00,000

2014/10/01 12:05:00,000

2014/10/01 12:06:00,000

2014/10/01 12:07:00,000

RCPU_2

INTERVAL

100

100

100

100

100

100

100

100

4

4

4

4

4

4

4

4

1

1

1

1

1

1

1

1

1 1234

2 1234

3 1234

1

0

0

1

0

0

4

5

6

0

0

0

0

0

0 *

INTERVAL[s]

3 4 5

STEP NO. PROGRAM NO. PROGRAM NAME

7

INDEX

2

SHORT[DEC.0] BIT[1;0] TRIGGER[*]

INDEX D1

0

0

0

6

BIT[1;0]

M0 M1 TriggerPROGRAM NAME

MAIN

PROGRAM NO.STEP NO.

2014/10/01 12:00:00,000

7

8

0

0

0

0

0

0

Data rows

File information row Comment row

Data name row

Data type information row

Device comment row Program name row*2

File type Model information_ file version

No. for data type information row

No. for data name row No. for program name row*2 No. for data start row

No. for device comment row No. for comment row

Date column Data collection interval column

Execution step No. column Execution program name column

Data columnsExecution program No. column

Index column Trigger occurrence information column

Start contact

17 DATA LOGGING FUNCTION 17.6 Data Logging File 243

24

Output content for each data File-related information is displayed.

Ex.

The total size of the file information row can be obtained by the following equation: (when comment is output) 14(file type) + 12(model information_file version) + 2(data type information row number) + 2(data name row number) + 2(device comment row number) + 2(data start row number) + 2(comment row number) + 10(the number of tabs) + 4(CR + LF) = 50 bytes Comments are displayed.

*3 Double quotation marks (" "), commas (,), and semicolons (;) cannot be used.

Ex.

The total size of the comment row can be obtained by the following equation: Character size of the specified comment (depending on the specified character string) + 4(CR + LF) The data type for each column is displayed. This information is output in the following format: (Data type)[(Additional information)].

Item Description Size File type [LOGGING] is output. 14 bytes

Model information_file version When the version of CPU Module Logging Configuration Tool is "1.82L" or later and local devices or labels are specified, "RCPU_2" is displayed in the file version, which shows the model information. When the version of CPU Module Logging Configuration Tool is "1.76E" or earlier, or the version is "1.82L" or later and only global devices are specified, "RCPU_1" is displayed in the file version, which shows the model information.

12 bytes

No. for data type information row Numerical value indicating the position of the data type information row from the top of the file is placed.

2 bytes

No. for data name row Numerical value indicating the position of the data name row from the top of the file is placed. 2 bytes

No. for device comment row Numerical value indicating the position of the device comment row from the top of the file is placed.

2 bytes

No. for data start row Numerical value indicating the starting position of the data row from the top of the file is placed.

2 bytes

No. for comment row Numerical value indicating the position of the comment row from the top of the file is placed. When the comment row is not output, this field is blank.

0 to 2 bytes

No. for program name row Numerical value indicating the position of the program name row from the top of the file is placed.

2 bytes

Item Description Size Comment Comment specified in CPU Module Logging Configuration Tool is output (the comment can

contain up to 256 characters.*3 When no comment is set, a blank row is output). 0 to 512 bytes

Item "Data type" output content Size "Additional information" output content

Size

Date column DATETIME 16 bytes Format is output. [YYYY/MM/DD hh:mm:ss.sss]

6 to 68 bytes

Data collection interval column

INTERVAL 16 bytes No additional information 0 bytes

Execution step No. column STEP NO. 16 bytes

Execution program number column

PROGRAM NO. 22 bytes

Execution program name column

PROGRAM NAME 24 bytes

Index column INDEX 10 bytes

4 17 DATA LOGGING FUNCTION 17.6 Data Logging File

17

Ex.

The size of the data type information row is determined by the following equation when data logging of 128 points of data (signed 16-bit integer, decimal format) is performed (The following sections in the "Output" window are set to be output: "Date" (the output format is YYYY/MM/DD hh:mm:ss.sss), "Data sampling interval", "Execution step No.", "Execution program name or execution program No.", and "Index"). (16 + 50)(date column) + 16(data collection interval column) + 16(execution step No. column) + 22(execution program number column) + 24(execution program name column) + 10(index column) + (10 + 14) 128(data column) + 264(the number of tabs) + 4(CR + LF) = 3494 bytes The data name for each column is displayed.

*4 When the data column is specified and the multidimensional array label is specified, if the index of the array includes comma (,), the data size will increase than the data name string size.

Ex.

The size of the data name row is determined by the following equation when data logging of 128 data points from D100 to D227 is performed (The following sections in the "Output" window are set to be output: "Date", "Data sampling interval", "Execution step No.", "Execution program name or execution program No.", and "Index"). 28(date column) + 24(data collection interval column) + 16(execution step No. column) + 22(execution program number column) + 24(execution program name column) + 10(index column) + (6 128)(data column) + 264(the number of tabs) + 4(CR + LF) = 1138 bytes

Data column Bit type: BIT 6 bytes Bit type: [1;0] 10 bytes

16-bit integer (unsigned): USHORT 12 bytes For decimal format: [DEC.0] 14 bytes

16-bit integer (signed): SHORT 10 bytes

32-bit integer (unsigned): ULONG 10 bytes For hexadecimal format: [HEX] 10 bytes

32-bit integer (signed): LONG 8 bytes

Single-precision floating point (32-bit): FLOAT

10 bytes For exponent expression: [EXP. (number of digits of decimal part)]

14 to 16 bytes

Double-precision floating point (64-bit): DOUBLE

12 bytes

Character string type: STRING 12 bytes Character string type, numeric string type: the specified data length value (unit: bytes) is output.

6 to 10 bytes

Numeric string type: RAW 6 bytes

Time: TIME 8 bytes No additional information 0 bytes

Trigger occurrence information column

TRIGGER 14 bytes [(string occurred)] is output (semicolons (;), double quotation marks (" "), and commas (,) cannot be used).

6 to 516 bytes

Item Description Size Date column TIME (time zone) is output. 28 bytes

Data collection interval column INTERVAL[us] is output. 24 bytes

Execution step No. column STEP NO. is output. 16 bytes

Execution program number column PROGRAM NO. is output. 22 bytes

Execution program name column PROGRAM NAME is output. 24 bytes

Index column INDEX is output. 10 bytes

Data column The specified data name is output. 1 to 512 bytes*4

Trigger occurrence information column Trigger is output. 14 bytes

Item "Data type" output content Size "Additional information" output content

Size

17 DATA LOGGING FUNCTION 17.6 Data Logging File 245

24

The program name row for each column is displayed. (This row appears when the version of CPU Module Logging Configuration Tool is "1.82L" or later and local devices or labels are specified. If the version is "1.76E" or earlier, or the version is "1.82L" or later and only global devices are specified, this row does not appear.)

Ex.

The size of the program name row is determined by the following equation when data logging of 128 data points from D100 to D227 is performed (The following sections in the "Output" window are set to be output: "Date", "Data sampling interval", "Execution step No.", "Execution program name or execution program No.", and "Index". Also, devices from D200 to D227 are specified as the local device of the program No.1 of "MAIN"). 0(date column) + 0(data collection interval column) + 0(execution step No. column) + 0(execution program number column) + 0(execution program name column) + 0(index column) + (0 100 + 8 28)(data column) + 264(the number of tabs) + 4(CR + LF) = 492 bytes The device comment row for each column is displayed.

*5 When "Output device comment" is selected in "Device comment output" of the output settings and double quotation marks (" ") and/or commas (,) are included in a device comment, the size of data in use becomes larger than the size of the character string of the device comments.

Ex.

The size of the device comment row is determined by the following equation when data logging of 128 data points from D100 to D227 is performed (The following sections in the "Output" window are set to be output: "Date" (the output format is YYYY/ MM/DD hh:mm:ss.sss), "Data sampling interval", "Execution step No.", "Execution program name or execution program No.", "Index", and "Device comment output" (only for devices from D200 to D227)). 0(date column) + 0(data collection interval column) + 0(execution step No. column) + 0(execution program number column) + 0(execution program name column) + 0(index column) + (0 100 + 14 28)(data column) + 264(the number of tabs) + 2(CR + LF) = 660 bytes

Item Description Size Date column No output (blank). 0 bytes

Data collection interval column

Execution step No. column

Execution program number column

Execution program name column

Index column

Data column When the collected data is a local device or local label, the specified program name (no extension) is displayed. When the collected data is a global device or global label, this field is blank.

0 to 120 bytes

Trigger occurrence information column No output (blank). 0 bytes

Item Description Size Date column No output (blank). 0 bytes

Data collection interval column

Execution step No. column

Execution program number column

Execution program name column

Index column

Data column When "Output device comments for data" is selected in the output setting, the comment with the specified comment number is displayed. When "Output each program device comment" is selected (when bit 9 of the added-data information is turned on), the comment with the specified comment number in the device comment file for each program is output only for the local device. When the device comment file for each program or the comment of the corresponding program does not exist, the comment of the device comment file is output. When comments are not output, this field is blank.

0 to 2048 bytes*5

Trigger occurrence information column No output (blank). 0 bytes

6 17 DATA LOGGING FUNCTION 17.6 Data Logging File

17

The collected data value is displayed. All the data items collected during a single collection is displayed in a single row.

*6 When single-precision real number or double-precision real number is specified, if the numerical value to be output does not fall into the range -2147483648.0 to 4294967295.0, it is displayed in an equivalent format to "exponential format and the number of decimal part digits is nine".

Ex.

The size of the data type information row is determined by the following equation when data logging of 128 points of data from D100 to D227 (unsigned word type, decimal format) is performed (The following sections in the "Output" window are set to be output: "Date" (the output format is YYYY/MM/DD hh:mm:ss.sss), "Data sampling interval", "Execution step No.", "Execution program name or execution program No.", and "Index"). 46(date column) + 24(data collection interval column) + 12(execution step No. column) + 6(execution program number column) + 200(execution program name column) + 20(index column) + (12 128)(data column) + 264(the number of tabs) + 4(CR + LF) = 2112 bytes

Item Description Size Date column Information is output according to the data row output character string specified in the format. 2 to 64 bytes

Data collection interval column

The time interval from the previous collection time to the current collection time is output. If the maximum display range is exceeded, the count returns to 1 and starts again to output a new time interval (unit: s, display range: 1 to 100000000000).

2 to 24 bytes

Execution step No. column

The step No. executed on the engineering tool at the time interval and timing in which data was collected is output. With the collection condition "Each scanning cycle" specified, the resulting output is the step No. at the time of execution of END instruction in the last executed program in the scan. With the collection condition "Interrupt occurrence" specified, the resulting output is the step No. at the time of execution of IRET instruction in the interrupt program. If the system operation (such as system interrupt) is running during collection interval and collection timing or the FB program is in running, "0" is output.

2 to 12 bytes

Execution program number column

The program No. executed on the engineering tool at the time interval and timing in which data was collected is output. With the collection condition "Each scanning cycle" specified, the resulting output is the program number of the last executed program in the scan. If two or more system operations, such as collection timing and system interrupt, occur simultaneously, is output.

2 to 6 bytes

Execution program name column

The program name (no extension) executed on the engineering tool at the time interval and timing in which data was collected is output. With the collection condition "Each scanning cycle" specified, the resulting output is the program name of the last executed program in the scan. If a program name with the same program number has already been in the file, a null value is output. If two or more system operations, such as collection timing and system interrupt, occur simultaneously, "* SYSTEM" is output.

0 to 200 bytes

Index column A value which increments in ascending order from 1 is output. When it exceeds the upper limit, it returns to 1 and increments again (range: 1 to 4294967295).

2 to 20 bytes

Data column When bits are specified: bit On = 1 and bit Off = 0 are output. 2 bytes

When unsigned/signed word type is specified: data value is output according to the specified output type.

Decimal format: 2 to 22 bytes Hexadecimal format: 2 to 16

bytes Decimal fraction format: 2 to 42

bytes Exponential format: 10 to 42

bytes

When unsigned/signed double word type, single-precision real number, or double-precision real number is specified: data value is output according to the specified output type.

Decimal format: 2 to 22 bytes*6

Hexadecimal format: 2 to 16 bytes

Decimal fraction format: 2 to 52 bytes

Exponential format: 10 to 44 bytes

When character string is specified: the specified character string is output. 2 to 256 bytes

When numeric string is specified: the character string which represented by the hexadecimal in increments of a byte is output without clearance.

4 to 1024 bytes

When time is specified: T#-24d20h31m23s648ms to T#24d20h31m23s647ms is displayed. 26 to 40 bytes

Trigger occurrence information column

The specified character string is output when the trigger occurs. In other cases, no character string is output.

0 to 512 bytes

17 DATA LOGGING FUNCTION 17.6 Data Logging File 247

24

CSV file output format The following table lists the format specifications of the CSV file output format and output content of each data. Format specifications

*1 When double quotation marks (" ") and/or commas (,) are included in the output data, the following processing occurs: When the data includes commas (,), whole data is enclosed by double quotation marks (" "). When the data includes double quotation marks (" "), another set of double quotation marks will be appended to each of them.

File format example Output items can be specified. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

*2 Information on the program name row appears when the version of CPU Module Logging Configuration Tool is "1.82L" or later and local devices or labels are specified. When the version is "1.76E" or earlier, or the version is "1.82L" or later and only global devices are specified, the information on the program name row does not appear.

Item Description Delimiter Comma (,)

Return code CRLF (0x0D, 0x0A)

Character code ASCII

Character encoding schema Shift-JIS

Field data Not enclosed by double quotation marks (" ") Double quotation marks (" ") and commas (,) cannot be used in each data.*1

[LOGGING]

LOG01

DATETIME[YYYY/MM/DD hh:mm:ss.sss]

TIME(UTC+09:00)

2014/10/01 12:01:00,000

2014/10/01 12:02:00,000

2014/10/01 12:03:00,000

2014/10/01 12:04:00,000

2014/10/01 12:05:00,000

2014/10/01 12:06:00,000

2014/10/01 12:07:00,000

RCPU_2

INTERVAL

100

100

100

100

100

100

100

100

4

4

4

4

4

4

4

4

1

1

1

1

1

1

1

1

1 1234

2 1234

3 1234

1

0

0

1

0

0

4

5

6

0

0

0

0

0

0 *

INTERVAL[s]

3 4 5

STEP NO. PROGRAM NO. PROGRAM NAME

7

INDEX

2

SHORT[DEC.0] BIT[1;0] TRIGGER[*]

INDEX D1

0

0

0

6

BIT[1;0]

M0 M1 TriggerPROGRAM NAME

MAIN

PROGRAM NO.STEP NO.

2014/10/01 12:00:00,000

7

8

0

0

0

0

0

0

Data rows

File information row Comment row

Data name row

Data type information row

Device comment row Program name row*2

File type Model information_ file version

No. for data type information row

No. for data name row No. for program name row*2 No. for data start row

No. for device comment row No. for comment row

Date column Data collection interval column

Execution step No. column Execution program name column

Data columnsExecution program No. column

Index column Trigger occurrence information column

Start contact

8 17 DATA LOGGING FUNCTION 17.6 Data Logging File

17

Output content for each data File-related information is displayed.

Ex.

The total size of the file information row can be obtained by the following equation: (when comment is output) 9(file type) + 6(model information_file version) + 1(data type information row number) + 1(data name row number) + 1(device comment row number) + 1(data start row number) + 1(comment row number) + 6(the number of commas) + 2(CR + LF) = 29 bytes Comments are displayed.

*3 Double quotation marks (" "), commas (,), and semicolons (;) cannot be used.

Ex.

The total size of the comment row can be obtained by the following equation: Character size of the specified comment (depending on the specified character string) +2(CR + LF)

Item Description Size File type [LOGGING] is output. 9 bytes

Model information_file version When the version of CPU Module Logging Configuration Tool is "1.82L" or later and local devices or labels are specified, "RCPU_2" is displayed in the file version, which shows the model information. When the version of CPU Module Logging Configuration Tool is "1.76E" or earlier, or the version is "1.82L" or later and only global devices are specified, "RCPU_1" is displayed in the file version, which shows the model information.

6 bytes

No. for data type information row Numerical value indicating the position of the data type information row from the top of the file is placed.

1 byte

No. for data name row Numerical value indicating the position of the data name row from the top of the file is placed. 1 byte

No. for device comment row Numerical value indicating the position of the device comment row from the top of the file is placed.

1 byte

No. for data start row Numerical value indicating the starting position of the data row from the top of the file is placed.

1 byte

No. for comment row Numerical value indicating the position of the comment row from the top of the file is placed. When the comment row is not output, this field is blank.

0 to 1 bytes

No. for program name row Numerical value indicating the position of the program name row from the top of the file is placed.

1 byte

Item Description Size Comment Comment specified in CPU Module Logging Configuration Tool is output (the comment can

contain up to 256 characters.*3 When no comment is set, a blank row is output). Since the comment is stored in Unicode, the data is converted to ASCII and Shift-JIS. If any characters that cannot be converted to ASCII or Shift-JIS are specified, the conversion fails and those characters will be output as periods (.).

0 to 512 bytes

17 DATA LOGGING FUNCTION 17.6 Data Logging File 249

25

The data type for each column is displayed. This information is output in the following format: (Data type)[(Additional information)].

Ex.

The size of the data type information row is determined by the following equation when data logging of 128 points of data (signed 16-bit integer, decimal format) is performed (The following sections in the "Output" window are set to be output: "Date" (the output format is YYYY/MM/DD hh:mm:ss.sss), "Data sampling interval", "Execution step No.", "Execution program name or execution program No.", and "Index"). (8 + 25)(date column) + 8(data collection interval column) + 8(execution step No. column) + 11(execution program number column) + 12(execution program name column) + 5(index column) + (5 + 7) 128(data column) + 132(the number of commas) + 2(CR + LF) = 1745 bytes

Item "Data type" output content Size "Additional information" output content

Size

Date column DATETIME 8 bytes Format is output. [YYYY/MM/DD hh:mm:ss.sss]

3 to 34 bytes

Data collection interval column

INTERVAL 8 bytes No additional information 0 bytes

Execution step No. column STEP NO. 8 bytes

Execution program number column

PROGRAM NO. 11 bytes

Execution program name column

PROGRAM NAME 12 bytes

Index column INDEX 5 bytes

Data column Bit type: BIT 3 bytes Bit type: [1;0] 5 bytes

16-bit integer (unsigned): USHORT 6 bytes For decimal format: [DEC.0] 7 bytes

16-bit integer (signed): SHORT 5 bytes

32-bit integer (unsigned): ULONG 5 bytes For hexadecimal format: [HEX] 5 bytes

32-bit integer (signed): LONG 4 bytes

Single-precision floating point (32-bit): FLOAT

5 bytes For exponent expression: [EXP. (number of digits of decimal part)]

7 to 8 bytes

Double-precision floating point (64-bit): DOUBLE

6 bytes

Character string type: STRING 6 bytes Character string type, numeric string type: the specified data length value (unit: bytes) is output.

3 to 5 bytes

Numeric string type: RAW 3 bytes

Time: TIME 4 bytes No additional information 0 bytes

Trigger occurrence information column

TRIGGER 7 bytes [(string occurred)] is output (semicolons (;), double quotation marks (" "), and commas (,) cannot be used). Since the string occurred is stored in Unicode, the data is converted to ASCII and Shift-JIS. If any characters that cannot be converted to ASCII or Shift-JIS are specified, the conversion fails and those characters will be output as asterisks (*).

3 to 514 bytes

0 17 DATA LOGGING FUNCTION 17.6 Data Logging File

17

The data name for each column is displayed.

*4 When the data column is specified and the multidimensional array label is specified, if the index of the array includes comma (,), the data size will increase than the data name string size.

Ex.

The size of the data name row is determined by the following equation when data logging of 128 data points from D100 to D227 is performed (The following sections in the "Output" window are set to be output: "Date", "Data sampling interval", "Execution step No.", "Execution program name or execution program No.", and "Index"). 14(date column) + 12(data collection interval column) + 8(execution step No. column) + 8(execution program number column) + 12(execution program name column) + 5(index column) + (4 128)(data column) + 132(the number of commas) + 2(CR + LF) = 705 bytes The program name row for each column is displayed. (This row appears when the version of CPU Module Logging Configuration Tool is "1.82L" or later and local devices or labels are specified. If the version is "1.76E" or earlier, or the version is "1.82L" or later and only global devices are specified, this row does not appear.)

Ex.

The size of the program name row is determined by the following equation when data logging of 128 data points from D100 to D227 is performed (The following sections in the "Output" window are set to be output: "Date", "Data sampling interval", "Execution step No.", "Execution program name or execution program No.", and "Index". Also, devices from D200 to D227 are specified as the local device of the program No.1 of "MAIN"). 0(date column) + 0(data collection interval column) + 0(execution step No. column) + 0(execution program number column) + 0(execution program name column) + 0(index column) + (0 100 + 4 15)(data column) + 132(the number of commas) + 2(CR + LF) = 194 bytes

Item Description Size Date column TIME (time zone) is output. 14 bytes

Data collection interval column INTERVAL[us] is output. 12 bytes

Execution step No. column STEP NO. is output. 8 bytes

Execution program number column PROGRAM NO. is output. 8 bytes

Execution program name column PROGRAM NAME is output. 12 bytes

Index column INDEX is output. 5 bytes

Data column The specified data name is output. Since the data name is stored in Unicode, the data is converted to ASCII and Shift-JIS. If any characters that cannot be converted to ASCII or Shift-JIS are specified, the conversion fails and those characters will be output as periods (.).

1 to 512 bytes*4

Trigger occurrence information column Trigger is output. 7 bytes

Item Description Size Date column No output (blank). 0 bytes

Data collection interval column

Execution step No. column

Execution program number column

Execution program name column

Index column

Data column When the collected data is a local device or local label, the specified program name (no extension) is displayed. When the collected data is a global device or global label, this field is blank. Since the program name is stored in Unicode, the data is converted to ASCII and Shift-JIS. If any characters that cannot be converted to ASCII or Shift-JIS are specified, the conversion fails and those characters will be output as periods (.).

0 to 120 bytes

Trigger occurrence information column No output (blank). 0 bytes

17 DATA LOGGING FUNCTION 17.6 Data Logging File 251

25

The device comment row for each column is displayed.

*5 When "Output device comment" is selected in "Device comment output" of the output settings and double quotation marks (" ") and/or commas (,) are included in a device comment, the size of data in use becomes larger than the size of the character string of the device comments.

Ex.

The size of the device comment row is determined by the following equation when data logging of 128 data points from D100 to D227 is performed (The following sections in the "Output" window are set to be output: "Date" (the output format is YYYY/ MM/DD hh:mm:ss.sss), "Data sampling interval", "Execution step No.", "Execution program name or execution program No.", "Index", and "Device comment output" (only for devices from D200 to D227)). 0(date column) + 0(data collection interval column) + 0(execution step No. column) + 0(execution program number column) + 0(execution program name column) + 0(index column) + (0 100 + 7 15)(data column) + 132(the number of commas) + 2(CR + LF) = 239 bytes

Item Description Size Date column No output (blank). 0 bytes

Data collection interval column

Execution step No. column

Execution program number column

Execution program name column

Index column

Data column When "Output device comments for data" is selected in the output setting, the comment with the specified comment number is displayed. When "Output each program device comment" is selected (when bit 9 of the added-data information is turned on), the comment with the specified comment number in the device comment file for each program is output only for the local device. When the device comment file for each program or the comment of the corresponding program does not exist, the comment of the device comment file is output. When comments are not output, this field is blank. Since the device comment is stored in Unicode, the data is converted to ASCII and Shift-JIS. If any characters that cannot be converted to ASCII or Shift-JIS are specified, the conversion fails and those characters will be output as periods (.).

0 to 2048 bytes*5

Trigger occurrence information column No output (blank). 0 bytes

2 17 DATA LOGGING FUNCTION 17.6 Data Logging File

17

The collected data value is displayed. All the data items collected during a single collection is displayed in a single row.

*6 When single-precision real number or double-precision real number is specified, if the numerical value to be output does not fall into the range -2147483648.0 to 4294967295.0, it is displayed in an equivalent format to "exponential format and the number of decimal part digits is nine".

Ex.

The size of the data type information row is determined by the following equation when data logging of 128 points of data from D100 to D227 (unsigned word type, decimal format) is performed (The following sections in the "Output" window are set to be output: "Date" (the output format is YYYY/MM/DD hh:mm:ss.sss), "Data sampling interval", "Execution step No.", "Execution program name or execution program No.", and "Index"). 23(date column) + 12(data collection interval column) + 6(execution step No. column) + 3(execution program number column) + 100(execution program name column) + 10(index column) + (6 128)(data column) + 132(the number of commas) + 2(CR + LF) = 1056 bytes

Item Description Size Date column Information is output according to the data row output character string specified in the format. 2 to 64 bytes

Data collection interval column

The time interval from the previous collection time to the current collection time is output. If the maximum display range is exceeded, the count returns to 1 and starts again to output a new time interval (unit: s, display range: 1 to 100000000000).

1 to 12 bytes

Execution step No. column

The step No. executed on the engineering tool at the time interval and timing in which data was collected is output. With the collection condition "Each scanning cycle" specified, the resulting output is the step No. at the time of execution of END instruction in the last executed program in the scan. With the collection condition "Interrupt occurrence" specified, the resulting output is the step No. at the time of execution of IRET instruction in the interrupt program. If the system operation (such as system interrupt) is running during collection interval and collection timing or the FB program is in running, "0" is output.

1 to 6 bytes

Execution program number column

The program No. executed on the engineering tool at the time interval and timing in which data was collected is output. With the collection condition "Each scanning cycle" specified, the resulting output is the program number of the last executed program in the scan. If two or more system operations, such as collection timing and system interrupt, occur simultaneously, is output.

1 to 3 bytes

Execution program name column

The program name (no extension) executed on the engineering tool at the time interval and timing in which data was collected is output. With the collection condition "Each scanning cycle" specified, the resulting output is the program name of the last executed program in the scan. If a program name with the same program number has already been in the file, a null value is output. If two or more system operations, such as collection timing and system interrupt, occur simultaneously, "* SYSTEM" is output. Since the program name is stored in Unicode, the data is converted to ASCII and Shift-JIS. If any characters that cannot be converted to ASCII or Shift-JIS are specified, the conversion fails and those characters will be output as periods (.).

0 to 120 bytes

Index column A value which increments in ascending order from 1 is output. When it exceeds the upper limit, it returns to 1 and increments again (range: 1 to 4294967295).

1 to 10 bytes

Data column When bits are specified: bit On = 1 and bit Off = 0 are output. 1 byte

When unsigned/signed word type is specified: data value is output according to the specified output type.

Decimal format: 1 to 6 bytes Hexadecimal format: 1 to 4 bytes Decimal fraction format: 1 to 21 bytes Exponential format: 3 to 21 bytes

When unsigned/signed double word type, single-precision real number, or double-precision real number is specified: data value is output according to the specified output type.

Decimal format: 1 to 11 bytes*6

Hexadecimal format: 1 to 8 bytes Decimal fraction format: 1 to 26 bytes Exponential format: 3 to 22 bytes

When character string is specified: the specified character string is output. 1 to 256 bytes

When numeric string is specified: the character string which represented by the hexadecimal in increments of a byte is output without clearance.

1 to 256 bytes

When time is specified: T#-24d20h31m23s648ms to T#24d20h31m23s647ms is displayed. 13 to 20 bytes

Trigger occurrence information column

The specified character string is output when the trigger occurs. In other cases, no character string is output. Since the trigger occurrence information is stored in Unicode, the data is converted to ASCII and Shift-JIS. If any characters that cannot be converted to ASCII or Shift-JIS are specified, the conversion fails and those characters will be output as asterisks (*).

0 to 512 bytes

17 DATA LOGGING FUNCTION 17.6 Data Logging File 253

25

Binary file output format The following figure shows the configuration of the binary format and details of each data. Configuration figure of binary format (when the version of CPU Module Logging Configuration Tool is "1.82L" or later and

local devices or labels are specified)

Header

Data

(1) Identification code: Fixed to 4 bytes (fixed to "MRDB")

(2) File version: 1 byte (fixed to 2)

(3) File type: 1 byte (fixed to 1)

(4) Model information: 16 bytes

(5) Added-data information: 2 bytes

Head-data information

(6) Comment size: Fixed to 2 bytes

(7) Comment: (Comment size) bytes

(8) Number of collected data: 2 bytes

Last-data information

Head-record data

Latest record data

: Whether or not to export can be selected.

(9) Data information size: 2 bytes

(10) Data type: 2 bytes

(11) Output type: 2 bytes

(12) Data information setting: 2 bytes

(13) Data length: 2 bytes

(14) Data name length: 2 bytes

(31) Program name: (Program name length) bytes

(15) Data name: (Data name length) bytes

(16) Device comment name length: 2 bytes

(17) Device comment name: (Device comment name length) bytes

(29) Device code: 16 bytes

(30) Program name length: 2 bytes

(20) Date data: 8 bytes

(18) Record start flag (FFFFH): (2 bytes)

(19) Record data length: 2 bytes

(21) Data collection interval: 8 bytes

(22) Step No.: 4 bytes

(23) Program No.: 2 bytes

(24) Program name length: 2 bytes

(25) Program name: (Program name length) bytes

(26) Index: 4 bytes

(27) Trigger occurrence flag: 2 bytes

(28) Head data: (Data length) bytes

(28) Last data: (Data length) bytes

(18) Record end flag (FFFEH): 2 bytes

(Collected data from the second one to the second-to-last)

(Records from the second one to the second latest)

(Collected data from the second one to the second-to-last)

4 17 DATA LOGGING FUNCTION 17.6 Data Logging File

17

Configuration figure of binary format (when the version of CPU Module Logging Configuration Tool is "1.76E" or earlier, or the version is "1.82L" or later and only global devices are specified)

Header

Data

(1) Identification code: Fixed to 4 bytes (fixed to "MRCB")

(2) File version: 1 byte (fixed to 1)

(3) File type: 1 byte (fixed to 1)

(4) Model information: 16 bytes

(5) Added-data information: 2 bytes

Head-data information

(6) Comment size: Fixed to 2 bytes

(7) Comment: (Comment size) bytes

(8) Number of collected data: 2 bytes

Last-data information

Head-record data

Latest record data

: Whether or not to export can be selected.

(9) Data information size: 2 bytes

(10) Data type: 2 bytes

(11) Output type: 2 bytes

(12) Data information setting: 2 bytes

(13) Data length: 2 bytes

(14) Data name length: 2 bytes

(15) Data name: (Data name length) bytes

(16) Device comment name length: 2 bytes

(17) Device comment name: (Device comment name length) bytes

(20) Date data: 8 bytes

(18) Record start flag (FFFFH): (2 bytes)

(19) Record data length: 2 bytes

(21) Data collection interval: 8 bytes

(22) Step No.: 4 bytes

(23) Program No.: 2 bytes

(24) Program name length: 2 bytes

(25) Program name: (Program name length) bytes

(26) Index: 4 bytes

(27) Trigger occurrence flag: 2 bytes

(28) Head data: (Data length) bytes

(28) Last data: (Data length) bytes

(18) Record end flag (FFFEH): 2 bytes

(Collected data from the second one to the second-to-last)

(Records from the second one to the second latest)

(Collected data from the second one to the second-to-last)

17 DATA LOGGING FUNCTION 17.6 Data Logging File 255

25

Details of each data

No. Item Description Size (byte) (1) Identification code When the version of CPU Module Logging Configuration Tool is "1.82L" or later and local devices or

labels are specified, "MRDB" is always output to identify the file. When the version of CPU Module Logging Configuration Tool is "1.76E" or earlier, or the version is "1.82L" or later and only global devices are specified, "MRCB" is always output to identify the file.

4

(2) File version When the version of CPU Module Logging Configuration Tool is "1.82L" or later and local devices or labels are specified, file version 2 is displayed. When the version of CPU Module Logging Configuration Tool is "1.76E" or earlier, or the version is "1.82L" or later and only global devices are specified, file version 1 is displayed.

1

(3) File type The file type is output. (fixed to 1: Continuous/trigger logging) 1

(4) Model information The module model name that outputted binary file is output. RCPU is output to the first eight bytes and 00H is output to the last eight bytes.*1

16

(5) Added-data information

The output selection setting for the data that can be output is output.

b0 1: Output date and time data. 0: Do not output date and time data.

b1 1: Output a data collection interval. 0: Do not output a data collection interval.

b2 1: Output an execution step No. 0: Do not output an execution step No.

b3 1: Output an execution program name and No. 0: Do not output an execution program name or No.

b4 1: Output a trigger flag. 0: Do not output a trigger flag.

b5 1: Output index. 0: Do not output index.

b6 1: Output device comments. 0: Do not output device comments.

b7 1: Output comments. 0: Do not output comments.

b9 1: Output device comments for each program. 0: Do not output device comments for each program.

2

(6) Comment size The comment length of (7) Comment is output. 2

(7) Comment The comment specified in the setting is output in Unicode. 2 to 512

(8) Number of collected data

The number of data points of the data information ((9) to (17) and (29) to (31)) for data logging is output. 2

(9) Data information size The total size of the data information ((9) to (17) and (29) to (31)) for data logging is output. 2

(10) Data type The numeric value shown below is output depending on the data type. 0000H: Bit 0001H: Word (signed) 0002H: Double word (unsigned) 0003H: Word (signed) 0004H: Double word (unsigned) 0005H: Single-precision real number 0006H: Double-precision real number 0007H: String 0008H: Numeric string 0009H: Time

2

(11) Output format The same numerical value as the value in (10) Data type is output. However, when the data type is bit, character string, numeric string, or time, FFFFH is output because the output type cannot be specified.

2

(12) Data information setting

The data-related information is output.

b2 1: Device comment specified 0: Device comment not specified

b3 1: Device code specified 0: Device code not specified

b4 1: Program name length/program name specified 0: Program name length/program name not specified

2

(13) Data length The data length of data is output. When the data type is the bit type, it will be output as two bytes. 2

(14) Data name length The length of the data name specified in the setting is output. 2

(15) Data name The data name specified in the setting is output in Unicode. 2 to 512

b9 b7 b6 b5 b4 b3 b2 b1 b0

b4 b3 b2

6 17 DATA LOGGING FUNCTION 17.6 Data Logging File

17

*1 The following capacity values are output to based on the model. Example: R08CPU, R08ENCPU: = 08

(16) Device comment name length

The length of the device comment name specified in the setting is output. 2

(17) Device comment name

The device comment name specified in the setting is output in Unicode. When "Output each program device comment" is selected, the comment with the specified comment number in the device comment file for each program is output only for the local device. When the device comment file for each program or the comment of the corresponding program does not exist, the comment of the device comment file is output.

0 to 2048

(18) Record start flag, record end flag

The flags for identifying the start and end of the record are output. The FFFFH is output for record start while the FFFEH is output for record end as the fixed flag.

2

(19) Record data length The total size of (20) Day and time data to (28) Last data is output. 2

(20) Date data The Day and time data is output. 8

(21) Data collection interval

The time interval from the previous collection time to the current collection time is output. (Unit: s, Display range: 1 to 100000000000 (When it exceeds the max value, it returns to "1" and incrementing runs again.)) After logging collection is started, 0 is stored at the first collection.

8

(22) Step No. The step No. executed on the engineering tool at the timing in which data was collected is output. With the collection condition "Each scanning cycle" specified, the resulting output is the step No. at the time of execution of END instruction in the last executed program in the scan. With the collection condition "Interrupt occurrence" specified, the resulting output is the step No. at the time of execution of IRET instruction in the interrupt program. If the system operation (such as system interrupt) is running during collection interval and collection timing or the FB program is in running, "0" is output.

4

(23) Program No. The program No. (FB File No.) executed on the engineering tool at the timing in which data was collected is output. With the collection condition "Each scanning cycle" specified, the resulting output is the program number of the last executed program in the scan. If system operation (such as system interrupt) is running at collection interval and collection timing, "0" is output.

2

(24) Program name length

The name length of a program that is executed at the time interval and timing in which data was collected is output. If the same program number or program name has already been in the file, "0" is output.

2

(25) Program name The program name (no extension) that is executed at the time interval and timing in which data was collected is output in Unicode. With the collection condition "Each scanning cycle" specified, the resulting output is the program name of the last executed program in the scan. If system operation (such as system interrupt) is running at collection interval and collection timing, "* SYSTEM" is output.

0 to 200

(26) Index The index number ranging from 1 to 4294967295 of data, which was collected by the data logging function, is output. When it exceeds the max value, it returns to "1" and incrementing runs again. If missing occurs in processing data, index will be reassigned from 1 again.

4

(27) Trigger occurrence flag

The trigger occurrence information is output.

b0 1: A trigger has occurred. 0: No trigger has occurred.

2

(28) Data Data collected by the data logging function is output corresponding to (13) Data length and (10) Data type. When bits are specified: bit On = 1 and bit Off = 0 are output. When word type (signed/unsigned) or double-word type (signed/unsigned) is specified: the data

values are output in the specified unit. When single-precision real number or double-precision real number is specified: data value is output

in the specified unit. ( Page 258 Numerical value range for each output type) When character string type is specified: the character string with the specified size is output. If the

character string terminator "0" exists in the middle of data, NULL is generated on from said point onward until the terminator of the specified size.

When numeric string type is specified: the data value with the specified size is output. When time is specified: T#-24d20h31m23s648ms to T#24d20h31m23s647ms is output.

Bit: 2 Word (signed/

unsigned): 2 Double word

(signed/ unsigned): 4

Single-precision real number: 4

Double-precision real number: 8

String/numeric string: 1 to 256

Time: 4

(29) Device code The device code of the device/label specified in the setting is output. 16

(30) Program name length

The length of the program name specified in the setting is output. (When a global device or global label is specified, "0" is output.)

2

(31) Program name The specified program name (no extension) is output in Unicode. (When a global device or global label is specified, the program name is not output.)

0 to 120

No. Item Description Size (byte)

b15 b0to Year: Last 2 digits of the year, Month: 1 to 12 Day: 1 to 31, Time: 0 to 23 Minute: 0 to 59, Second: 0 to 59 Millisecond: 0 to 999

Year Day

Minute

Month Time

Second Millisecond

b0

17 DATA LOGGING FUNCTION 17.6 Data Logging File 257

25

Numerical value range for each output type This section describes the numerical value ranges that can be output for each output type.

Integer type The following table lists the numerical value ranges that can be expressed for each integer type.

Real number type The following table lists the numerical value ranges that can be expressed for each real number type.

When the value of the data exceeds the numerical value range, the following rule is applied to the output. When the value exceeds the upper limit of the positive value, +Inf is output. When the value falls below the lower limit of the negative value, -Inf is output. When the value is between the upper limit of the negative value and the lower limit of the positive value, 0 is output.

Output format Lower limit Upper limit Word (unsigned) 0 65535

Word (signed) -32768 32767

Double word (unsigned) 0 4294967295

Double word (signed) -2147483648 2147483647

Output format Negative value Positive value

Lower limit Upper limit Lower limit Upper limit Single-precision real number

-3.4028235E+38 -1.401298E-45 1.401298E-45 3.4028235E+38

Double-precision real number

-1.79769313486231570E+308 -4.94065645841246544E-324 4.94065645841246544E-324 1.79769313486231570E+308

Output format -Inf 0 +Inf Single-precision real number 0xff800000 0x00000000 0x7f800000

Double-precision real number 0xfff0000000000000 0x0000000000000000 0x7ff0000000000000

8 17 DATA LOGGING FUNCTION 17.6 Data Logging File

17

Storage location of data logging files Select an SD memory card or the function memory for the storage location. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series)) The number of data logging settings and the number of records vary, depending on the storage location. For details, refer to the functional specifications. ( Page 228 Specifications)

Availability The following table lists available CPU module models by each storage location. : Applicable, : Not applicable

*1 When using the function memory as the storage location, check the firmware version of the CPU module and the version of the CPU Module Logging Configuration Tool. ( Page 700 Added and Enhanced Functions) The data logging file stored in the function memory can be transferred to the FTP server by using the data logging file transfer function. (Page 273 Data Logging File Transfer (Auto Transfer to FTP Server)) If the data logging file transfer function is not set, the files are transferred to the data memory. ( Page 282 Data Logging File Transfer to Data Memory)

Data logging into different storage locations (SD memory card and function memory) cannot be executed simultaneously.

When the storage location is the function memory, up to two data loggings can be executed simultaneously. (Up to 10 data loggings can be set.) The maximum number of data loggings that can be executed simultaneously is ten, depending on the firmware version and production information of the CPU module. ( Page 700 Added and Enhanced Functions)

CPU module Storage location

SD memory card Function memory R01CPU, R02CPU

R04CPU, R08CPU, R16CPU, R32CPU, R120CPU R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, R120ENCPU

*1

17 DATA LOGGING FUNCTION 17.6 Data Logging File 259

26

Folder configuration of SD memory cards The following figure shows the folder configuration of the SD memory card attaching to a CPU module.

*1 Folder names cannot be modified. *2 Do not create folders/files under the $MELPRJ$ and LOGGING folders using a personal computer and other devices. *3 To remove unnecessary folders, use the following methods:

Use a personal computer. Logging File Operation ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R series))

$MELPRJ$

LOGGING

/

LOG01

LOG02

LOG03

LOG01.BIN

00000101

00000001

LOG02.BIN

LOG03.BIN

00000001.BIN

00000002.BIN

Stack file (setting No.1)

Stack file (setting No.2)

Stack file (setting No.3)

*1 *2

*1 *2 *3

*3

0 17 DATA LOGGING FUNCTION 17.6 Data Logging File

17

17.7 States of the Data Logging Function The data logging function has the data logging state. The data logging state can be checked by CPU Module Logging Configuration Tool. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

Data logging states The following table lists all the possible data logging states.

*1 CPU Module Logging Configuration Tool displays "Saving the logging data" as the data logging state until saving of collected data completes. After the completion, the state changes to each of three states.

*2 The execution of another function includes: Execution of data logging with the same trigger conditions (trigger conditions = the specified conditions) Auto logging Online program change

Data logging states Description Stop*1 Data logging settings are unregistered and data collection is inactive.

Stop (after collection) Transition from "Collection completed" to "Stop" has occurred due to the execution of another function*2.

Stop (after error) Transition from "Error" to "Stop" has occurred due to the execution of another function*2.

RUN waiting (no collection) Data collection has not yet begun because the operating status of the CPU module is not in the RUN state.

Start waiting (no collection) Data collection is inactive, waiting for the start command.

Pause*1 Data logging is suspended and data collection has not yet been started. (The data logging settings remain intact.)

Condition waiting (no collection) Data logging settings are registered and waiting for the first collection timing.

Collecting Continuous logging is active and collecting data.

Trigger waiting (Collecting before trigger) Data logging settings are registered, data collection is being performed, and waiting until the trigger condition is met.

Collecting after trigger Trigger logging is active and collecting data after the trigger condition is met.

Collection completed*1 Continuous logging: Data collection has finished upon reaching "Number of files to be saved" specified as part of the "Stop" setting configured in "Operation when exceeds the number of files". (The data logging settings remain intact.)

Trigger logging: Trigger logging has finished collecting data as much as the specified number of records. (The data logging settings remain intact.)

Error Data logging has failed due to the occurrence of an error.

17 DATA LOGGING FUNCTION 17.7 States of the Data Logging Function 261

26

LED status Whether the data logging function is active or not can be checked by the LED of the CPU module.

*1 The LED status when the data storage destination memory is the SD memory card.

For the FUNCTION LED indication, the following cases have priority over the function above. When the external input/output forced on/off function is executed (in registration) ( Page 209

FUNCTION LED) When program restoration information is not written ( Page 686 Checking the program restoration

information write status) After the external input/output forced on/off function has been executed (after the registration is canceled) and program restoration information has been written, the LED indicator follows the status of the data logging function. ( Page 172 LED display setting)

States of the Data Logging Function LED status

FUNCTION LED CARD READY LED*1

CARD ACCESS LED*1

Data logging settings have been registered by the start operation from CPU Module Logging Configuration Tool.

After registering the auto logging common setting, an SD memory card that stores the setting for which the auto logging function is enabled has been inserted.

On On Off

All of the registered data logging sessions are in the state "RUN waiting (no collection)", "Start waiting (no collection)", "Pause", "Condition waiting (no collection)", or "Trigger waiting (Collecting before trigger)".

One or more of the registered data logging sessions are in the state "Collecting" (including the data being saved) or "Collecting after trigger" (including the data being saved).

Flashes slowly (every one second)

On On (when the SD memory card is accessed)

All of the registered data logging sessions have finished (or failed due to an error).

Flashes at normal rate (every 200ms)

On Off

2 17 DATA LOGGING FUNCTION 17.7 States of the Data Logging Function

17

17.8 Steps Until the Collected Data Is Saved This section describes the steps until the collected data is saved.

When the data storage destination memory is the SD memory card The following figure shows the flow of data when the data storage destination memory is the SD memory card.

(1) The collected data is temporarily stored in the specified internal buffer. ( Page 265 Internal buffer) (2) The data stored in the internal buffer is stored into the SD memory card at the timing of a file save operation. (3) With the file transfer setting, data logging files can be transferred from the SD memory card to the FTP server. ( Page 273 Data Logging File Transfer

(Auto Transfer to FTP Server))

(1) (2)

(3)

(2)

First collected data

Second collected data

First collected data

Second collected data

Device/ label area

Setting 1

Setting 2

Internal buffer

First collected data

Second collected data

First collected data

Second collected data

Setting 1

Setting 2

Data collection of the specified device/label

Inside the CPU module SD memory card

Ethernet

17 DATA LOGGING FUNCTION 17.8 Steps Until the Collected Data Is Saved 263

26

When the data storage destination memory is the function memory The following figure shows the flow of data when the data storage destination memory is the function memory.

(1) The collected data is temporarily stored in the specified internal buffer. ( Page 265 Internal buffer) (2) The data stored in the internal buffer is stored into the function memory at the timing of a file save operation. (3) With the file transfer setting, data logging files can be transferred from the function memory to the FTP server. ( Page 273 Data Logging File Transfer

(Auto Transfer to FTP Server)) (4) Without the file transfer setting, data logging files are transferred to the data memory upon completion or stopping of the data logging (including when an

error occurs). ( Page 282 Data Logging File Transfer to Data Memory)

(1)

(3)

(4)

(2)

(2)

First collected data

Second collected data

First collected data

Second collected data

Device/ label area

Setting 1

Setting 2

Internal buffer Function memory

First collected data

Second collected data

First collected data

Second collected data

Setting 1

Setting 2

Data collection of the specified device/label

Inside the CPU module

Ethernet

Data memory

4 17 DATA LOGGING FUNCTION 17.8 Steps Until the Collected Data Is Saved

17

Internal buffer The internal buffer is a system area used to temporarily store collected data. The collected data is temporarily stored in the internal buffer and stored in the specified data storage destination memory at the time of a file save operation.

Internal buffer capacity setting Set the capacity of the area (internal buffer) used by the system to temporarily store the results of data logging and memory dump processing. The capacity can be set individually for each data logging setting number (1 to 10).

[CPU Parameter] [Memory/Device Setting] [Internal Buffer Capacity Setting]

This function cannot be used in the R00CPU.

For trigger logging, increasing the internal buffer capacity allows an increase in the number of collected data before trigger and also helps to prevent processing overflow. If the free space in the internal buffer is still insufficient after increasing the internal buffer capacity, use the following workarounds: Increase the data collection interval or timing. Reduce the number of data records to be collected. Lower the frequency of file switching.

Window

17 DATA LOGGING FUNCTION 17.8 Steps Until the Collected Data Is Saved 265

26

Displayed items

*1 Leaving this field blank allows the setting to be unused (0K bytes). *2 A reduced capacity of the internal buffer decreases the extension of scan time, but it takes time to complete.

The internal buffer is also consumed in the real-time monitor function. Set the total of the internal buffer to no more than 3072K bytes including the internal buffer to be consumed in the real-time monitor function as well. The internal buffer for the real-time monitor function can be set with GX LogViewer. ( GX LogViewer Version 1 Operating Manual)

Amount of internal buffer consumed This value can be calculated by multiplying "Number of data points" by 2 bytes. Note, however, that additional space is consumed by columns configured for output, as indicated below: Date/time column: 10 bytes Data collection interval column: 8 bytes Execution step No. column: 10 bytes Execution program No. column: 2 bytes Index column: 4 bytes

Ex.

When data logging is configured to collect as much data as one setting x 128 records and output all of the columns (i.e., maximum allowable configuration): 128 2 + (10 + 8 + 10 + 2 + 4) = 290 bytes

Item Description Setting range Default Total Capacity Shows the total of the internal buffer capacity set in the

data logging function and the memory dump function. 60 to 3072K bytes 1536K bytes

Data Logging Function

Total Capacity Shows the total of the internal buffer capacity used for the data logging function.

1280K bytes

Setting No.1 to 10

The internal buffer capacity used for each Setting No. of the data logging settings

Each setting range: 32 to 3040K bytes (in increments of 1K bytes)*1

Total setting range: 32 to 3040K bytes

128K bytes

Memory Dump Function Set the internal buffer capacity used for the memory dump function.

32 to 3040K bytes (in increments of 1K bytes)*2

256K bytes

6 17 DATA LOGGING FUNCTION 17.8 Steps Until the Collected Data Is Saved

17

Switching to a storage file The data collected by data logging is temporarily stored in a stack file. The stack file can be switched to a storage file to free the space in the SD memory card.

How file switching works File switching works as follows:

1. The CPU module writes collected data into a stack file (such as LOG01.BIN).

2. It changes the file name when the storage file switching condition is met.* 1*2

3. It creates a new stack file.

4. It continues to write collected data into the newly created stack file.

*1 The file name format can be customized. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

*2 The file number of the most recent storage file is stored in the special register (Latest storage file number).

LOG01.BIN

LOG01.BIN LOG01_00000001.BIN

:

:

Stack file

Device data collection

Stack file

Device data collection

Storage file

File switching

CPU module

CPU module

17 DATA LOGGING FUNCTION 17.8 Steps Until the Collected Data Is Saved 267

26

File switching condition The following table lists the setting items that can be used to specify the file switching condition.

*1 File switching occurs before the file grows beyond the specified size. *2 When setting specified conditions, check the firmware version of the CPU module and the version of the CPU Module Logging

Configuration Tool. ( Page 700 Added and Enhanced Functions) However, file switching occurs regardless of the setting when: the number of records has reached the maximum number; the file size has reached the maximum size; the CPU module is stopped or suspended/resumed: or data logging is started and there is an existing stack file.

Trigger logging does not require the configuration of these settings because the stack file is automatically switched to a storage file after as much data as the specified number of records is written into the stack file. SM1218 (logging data storage file switching in progress) can be used to check if storage file switching is in progress.

Condition specification When the specified condition changes to being met, the stack file is switched to the storage file. Monitored data For monitoring data, the following can be set. The data types that can be selected include bit/word (unsigned), word (signed), double word (unsigned), and double word (signed).

*1 An index modified device and indirectly specified device cannot be specified. *2 For bit devices, digit specification is not supported. *3 For word devices, bit specification is allowed. *4 To specify the local device, use "Program name/#Device name". (Example: "MAIN/#M1") *5 To specify these devices with CPU Module Logging Configuration Tool, use T (contact): TS, ST (contact): STS, C (contact): CS, LT

(contact): LTS, LST (contact): LSTS, and LC (contact): LCS. Conditional formula The following symbols can be specified for the conditional formula.

Setting item Description Number of records Specify the number of records within the following range.

When the data storage destination memory is the SD memory card: 1 to 65500 When the data storage destination memory is the function memory: 1 to 12000

File size*1 Specify the number of kilobytes within the following range. When the data storage destination memory is the SD memory card: 10 to 16384K bytes When the data storage destination memory is the function memory: 10 to 1024K bytes

Condition*2 Specify the following data. ( Page 268 Condition specification) Monitored data Conditional formula: , , =, , , >, , <, At value change Condition values

Type Device*1

Device Bit device*2 X, Y, M*4, L, F, SM, V*4, B, SB, T (contact)*4*5, ST (contact)*4*5, C (contact)*4*5, LT (contact)*4*5, LST (contact)*4*5, LC (contact)*4*5, FX, FY

Word device*3 T (current value)*4*5, ST (current value)*4*5, C (current value)*4*5, D*4, SD, W, SW, RD, R, ZR, FD

Double-word device LT (current value)*4*5, LST (current value)*4*5, LC (current value)*4*5

=: When the current value of the monitored data is equal to the comparison value : When the current value of the monitored data is not equal to the comparison value : When the current value of the monitored data is equal to or larger than the comparison value >: When the current value of the monitored data is larger than the comparison value : When the current value of the monitored data is equal to or smaller than the comparison value <: When the current value of the monitored data is smaller than the comparison value : When the specified data turns off and on : When the specified data turns on and off At value change: When the current value of the specified data changes

8 17 DATA LOGGING FUNCTION 17.8 Steps Until the Collected Data Is Saved

17

Storage file The CPU module creates a subfolder ("storage file container folder") under the file storage folder and writes storage files to that storage file container folder. One storage file container folder can contain up to 256 storage files. When the files contained in the current storage file container folder reach the maximum number, the CPU module creates a new storage file container folder at the time of next storage file switching and begins writing storage files to that new folder. The number of files that can be contained in one file storage folder is configurable within the range of 1 to 65535.

The base folder name of a storage file container folder is an eight-digit (hexadecimal) number. This number matches the lowest of the serial numbers of the files contained in the directory. Date and time stamps can be appended to the folder name.

Storage file name The following describes the storage file name. The base file name is an eight-digit (hexadecimal) serial number.*1

*1 The same number is not used in the same file storage folder. If storage files have already existed when a new storage file is created by switching a stack file to a storage file, the number added one to the largest serial number among existing storage files becomes the name of the new storage file.

The following extra information can be added to the base file name. Up to 64 characters (including an extension and the period) can be a file name, combining any of the following.

*2 When using an above formatted string as it is, enclose a character string with double-quotation marks (" ") to add it. Example: When adding the character string "address" to the file name, "address" address_00000001.bin can be used. However, when a character string that contains double quotation marks (" ") is specified, the maximum number reduces by the number of the double quotation marks.

*3 When adding a device value, check the firmware version of the CPU module and the version of the CPU Module Logging Configuration Tool. ( Page 700 Added and Enhanced Functions)

Date type A date type can be selected from the following.

Extra information Details on extra information Remarks Simple setting Storage folder name Name of a folder where storage files are stored An underscore (_) is added

between each information.Date Date information in YYYYMMDD format YYYY: Year (four digits) MM: Month (two digits) DD: Day (two digits)

Time Time information in hhmmss format hh: Hour (two digits) mm: Minute (two digits) ss: Second (two digits)

Optional setting String Any string*2

Date Date information added by specifying the following strings YYYY: Year (four digits) YY: Year (two digits) MM: Month (two digits) DD: Day (two digits)

Day of week Day of the week information added by specifying the following strings ddd: Day of week (three digits)

(Sunday: Sun, Monday: Mon, Tuesday: Tue, Wednesday: Wed, Thursday: Thu, Friday: Fri, Saturday: Sat)

Time Time information added by specifying the following strings hh: Hour (two digits) mm: Minute (two digits) ss: Second (two digits)

Device value*3 The data value of the specified device can be added to the beginning of the file name by the number of digits specified (in the range of 1 to 5).

Add date type Description Date to establish file switching condition Date and time information when the storage file switching condition is met is added.

File creation date Date and time information when the file is created as a stack file (when the previous file switching is executed) is added.

17 DATA LOGGING FUNCTION 17.8 Steps Until the Collected Data Is Saved 269

27

Processing of file switching may take time depending on the setting. In this case, a date and time, which is closer to present than the timestamp of the first record in the data logging file, is added even though "File creation date" is selected for "Add date type".

When "File creation date" is selected for "Add date type", a second information (two digits) added to a file name is always even number.

After a data logging stops (completes) and restarts, the serial number (eight digits) of the base file name starts from 1 again in the following two cases: where the setting to delete data logging files after transfer is completed by using the data logging file transfer function or where the CPU built-in memory is specified as the file storage destination for transferring the files to the data memory (without using the data logging file transfer function). If the storage file name consists of the serial number only, the existing files in the transfer destination may be overwritten. It is recommended to add a date and time to the file name.

Device value The data value of the specified device can be added to the beginning of the file name by the number of digits specified (in the range of 1 to 5). The timing to obtain the device value varies depending on the add date type. ( Page 269 Storage file name) The date and time when the file switching condition is met is added when "Date to establish file switching condition" is selected, and the date and time when the stack file is created is added when "File creation date" is selected. If the device value cannot be obtained upon file switching or stack file creation, no data is added to the storage file name. The following table describes the types of the data that can be selected for adding to the file name.

*1 If the number of digits in the device data value exceeds the specified number of digits, only the specified number of digits are displayed from the small end. If the number of digits is insufficient, the remainder is supplemented with 0. Example 1: When the device value is K123 and five digits are specified, "00123" is displayed. Example 2: When the device value is K12345 and three digits are specified, "345" is displayed.

*2 If the number of characters in the device data value exceeds the specified number of characters, only the specified number of characters are displayed from the beginning. If the number of characters is insufficient, the remainder is not supplemented. If invalid data is included in the specified number of characters, valid characters are displayed. Example: When the device value is "ABC" and five characters are specified, "ABC" is displayed. Example: When the device value is "ABCDE" and three characters are specified, "ABC" is displayed.

The following describes the devices that can be specified for a device value.

*3 An index modified device, indirectly specified device, and local device cannot be specified.

Data type Effective data Remarks Word (unsigned) Fixed decimal format (0 to 65535)*1

String Single-byte alphabetical characters*2 Characters in the file format that was specified in the storage format for data logging files.

Type Device*3

Word device T (current value), ST (current value), C (current value), D, SD, W, SW, RD, R, ZR, Z

0 17 DATA LOGGING FUNCTION 17.8 Steps Until the Collected Data Is Saved

17

When the maximum number of storage files to be saved is exceeded Either "Overwrite" or "Stop"*1 can be selected as the action to take when the maximum number of storage files is exceeded. *1 This settings is not configurable for trigger logging.

When "Overwrite" is selected When the storage file switching condition is met after the specified maximum number of storage files is exceeded, the CPU module deletes the file with the lowest serial number and creates a new file that has a serial number incremented by one from the highest serial number, allowing data logging to continue. In addition, if deleting the file with the lowest serial number results in an empty folder, the CPU module deletes that folder as well.

When "Stop" is selected As described in the following table, the action differs depending on when the specified maximum number of storage files is exceeded.

*1 When an attempt is made to register the data logging settings again, the CPU module enters into the data logging completed state. A special relay area (Data logging end) turns on to indicate that data logging is completed.

The files deleted by "Delete files completed transfer" in the data logging file transfer setting are counted as the number of storage files. (Temporary stored files are counted as the number of storage files although they are not stored in the SD memory card or function memory.) When "Overwrite" is selected, the file being transferred may be deleted with the data logging file transfer setting. It is recommended to set "Stop"

Occurrence timing Occurrence condition Behavior When data logging is started

There exist more storage files than the specified maximum number when data logging is started.

If an attempt is made to register the data logging settings by the start operation from CPU Module Logging Configuration Tool, an error occurs, resulting in failure to run data logging.

If an attempt is made to register*1 the data logging settings from outside CPU Module Logging Configuration Tool, a special relay area (data logging error) turns on and a special register area (data logging error cause) stores its error cause, resulting in failure to run data logging.

While data logging is running

The specified maximum number of storage files is reached due to file switching upon the satisfaction of the storage file switching condition.

Data logging stops and enters into the completion state with the data logging settings remaining intact. A special relay area (Data logging end) turns on to indicate that data logging is completed.

17 DATA LOGGING FUNCTION 17.8 Steps Until the Collected Data Is Saved 271

27

17.9 Missing Data The term "missing data" means that some of the collected data is missing, resulting in data discontinuity.

Conditions under which missing data occurs Missing data occurs under the following conditions:

*1 Failure to collect data at the specified collection interval/timing due to the execution of a long-running instruction (such as FMOV) does not cause processing overflow or missing data.

*2 The following operation also is included: Online operation which displays data by operation such as read from the programmable controller performed from an engineering tool (retrieval and display of a list of files on the CPU module) View of the event history (retrieval of the event history from the CPU module)

Processing overflow In normal cases when the usage of the internal buffer reaches the specified maximum capacity, the CPU module overwrites the data stored in the storage memory on a first-in first-out basis. If the internal buffer becomes full before all of the data stored in it is saved to the storage memory, however, the CPU module does not overwrite the existing data and stops storing data in the internal buffer, thus resulting in missing data. This situation is referred to as processing overflow. Upon the occurrence overflow, the special register (Number of processing overflow occurrences) stores the number of times when processing overflow occurred.

Item Description Processing overflow Processing overflow has occurred due to failure to keep up with the specified collection interval/timing.*1

Operations for the CPU module The CPU module has been stopped and run with "Operation at transition to RUN" set to "Auto Start".

The CPU module has been turned off and on with "Operation at transition to RUN" set to "Auto Start".

The CPU module has been reset and run with "Operation at transition to RUN" set to "Auto Start".

Operation from engineering tools, CPU Module Logging Configuration Tool, and external devices via protocols such as FTP, SLMP, and MC

When the CPU module is suspended and restarted, and operation for displaying the logging state is performed from CPU Module Logging Configuration Tool

File read*2, write, delete, or verification

2 17 DATA LOGGING FUNCTION 17.9 Missing Data

17

17.10 Data Logging File Transfer (Auto Transfer to FTP

Server) This function automatically transfers data logging files to the FTP server. An SD memory card as the temporary storage destination is not required by setting the CPU built-in memory (function memory*1) as the data storage destination while using this function.

*1 For the CPU modules that can use the function memory, refer to the availability of storage location. ( Page 259 Availability)

This function cannot be used in the R00CPU. Before executing the function, check the versions of the CPU module and CPU Module Logging

Configuration Tool used. ( Page 700 Added and Enhanced Functions)

An FTP server is required for the data logging file transfer function. For details on the server, refer to the manual for the server used.

The operation of this function is checked with the following FTP server.

Item Supported operating system FTP server whose operation is checked by Mitsubishi Microsoft Internet Infomation Services(IIS)

The supported operating systems are as follows: Microsoft Windows 10 Microsoft Windows 8.1 Microsoft Windows 8 Microsoft Windows 7

LOG02_ 00000001 .txt

LOG01_ 00000001 .txt

LOG03_ 00000001 .txt

LOG01_ 00000001 .txt

LOG02_ 00000001 .txt

LOG03_ 00000001 .txt

CPU module

FTP server

Data logging file

CPU module

Data logging file

CPU module

Data logging file

Ethernet

17 DATA LOGGING FUNCTION 17.10 Data Logging File Transfer (Auto Transfer to FTP Server) 273

27

Transfer specifications and start timing of the data logging file Data logging files are transferred at the file switching timing in the data logging function.

Transfer specifications of the data logging file Data logging files are transferred one by one from each setting number (folder). If multiple files exist in multiple setting numbers, a file which has the smallest serial number in the lowest setting number is

transferred. Only one file per setting number can be the standby file. For example, in the following data structure, files are transferred from the file . (Files are transferred in order from ... .)

If an error occurs during a file transfer, the data logging file caused the error is omitted from the standby files. A following file in the same setting number becomes a new standby file.

If the file switching timing occurs during a file transfer, the file that has been being transferred becomes a standby file. If the data logging operation is completed or the user has operated CPU Module Logging Configuration Tool to stop data

logging, the data logging file transfer is stopped at the completion of the transfer of the stored data logging files.

LOG01

LOG02

LOG03

00000001.txt

00000002.txt

00000002.txt

00000003.txt

00000004.txt

00000001.txt

00000002.txt

00000001.txt

00000002.txt

00000001.txt 00000001.txt 00000001.txt

File storage folder

Data logging setting No.1

Data logging setting No.1

Data logging setting No.3

Data logging setting No.2

Data logging setting No.1

Data logging setting No.2

Data logging setting No.3

Standby

FirstLast

During file transfer

4 17 DATA LOGGING FUNCTION 17.10 Data Logging File Transfer (Auto Transfer to FTP Server)

17

Start timing of file transfer After data logging is started, the transfer of the files created at the file switching timing in the data logging function starts. When the transfer is started, special relay areas SM1219 to SM1309 (Data logging file transfer execution status flag) for each setting number turn on. They turn off after all the files are transferred.

SM1211: Data logging setting No.1 Data logging start SM1219: Data logging setting No.1 Data logging file transfer execution status flag SD1217: Data logging setting No.1 Data logging file transfer error cause *1 SM1219 does not turn off until all the files are transferred.

Procedure for file transfer FTP server setting Set the login name, password, and home directory to the FTP server. Authorize the user of the data logging file transfer function to read/write files. ( Manual for the server used)

Engineering tool setting 1. Set the IP address of the CPU module. Set the subnet mask and default gateway as necessary.

[Navigation window] [Parameter] CPU module [Module Parameter] [Basic Settings] [Own Node Settings] [IP Address]

2. To specify an FTP server with the server name, set "To Use or Not to Use DNS Server Settings" to "Use" by using the engineering tool.

[Navigation window] [Parameter] CPU module [Module Parameter] [Application Settings] [DNS Settings]

3. Set an address of the DNS server.

Window

Displayed items

Setting item Description Setting range Default DNS server 1 IP address Set the IP address of the DNS server 1 in the

decimal format. 0.0.0.1 to 223.255.255.254 Blank

DNS server 2 IP address Set the IP address of the DNS server 2 in the decimal format.

0.0.0.1 to 223.255.255.254 Blank

ON OFF

ON OFF

0 0

SM1211

SM1219

SD1217

*1

Setting No. 1

Data logging start File switching File switching File switching Data logging stop

17 DATA LOGGING FUNCTION 17.10 Data Logging File Transfer (Auto Transfer to FTP Server) 275

27

Setting of CPU Module Logging Configuration Tool 1. Select the "Transferring files to the FTP server" check

box in "File transfer" of CPU Module Logging Configuration Tool.

( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

2. Click the [Server Setting] button.

3. Configure the server setting. To specify the FTP server with the server name, the DNS setting is required. ( Page 275 Engineering tool setting)

4. Click the [File Transfer Test] button to execute the file transfer test to the FTP server. Before operating the system, execute the file transfer test and ensure the connection with the FTP server. ( Page 277 File transfer test)

5. Set the timeout time and other items on the "File transfer" window. ( Page 278 Setting on the "File transfer" window)

6. Write the setting from CPU Module Logging Configuration Tool.

( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series)) 7. The transfer is started at the logging file switching

timing. ( Page 275 Start timing of file transfer)

6 17 DATA LOGGING FUNCTION 17.10 Data Logging File Transfer (Auto Transfer to FTP Server)

17

File transfer test Check the communication status and settings by transferring a test file from the CPU module to the FTP server. The file transfer to the FTP server can be checked before system operation.

Procedure for the file transfer test The following describes the procedure for the file transfer test.

1. Configure the transfer destination server setting in CPU Module Logging Configuration Tool. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

2. Click the [File Transfer Test] button in the "FTP Setting" window to execute the file transfer test.

3. Check the execution result.

4. Check that the test file is transferred to the FTP server. ( Page 277 Structure of a test file)

Structure of a test file The following table lists structures of a test file to be transferred to the FTP server.

File transfer test specification The FTP server connection request timeout time is fixed to 10 seconds. Even if the file transfer test fails due to a communication error, the retry is not executed. Even if the file transfer test fails, the error is not stored in the file transfer error history. ( CPU Module Logging

Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

Precautions File transfer tests cannot be executed simultaneously with another configuration tool. Execute the file transfer test after the

file transfer test from another configuration tool is completed. If the engineering tool is operated or monitored from the same connection destination of the same computer during the file

transfer test, the operation or monitoring will be executed after the file transfer test completion.

Item Description Example Test file name MELSEC_CPU_FTP_TEST_**.txt

** indicates the data logging setting number (two digits, with zero-padding).

For setting No.1 MELSEC_CPU_FTP_TEST_01.txt

Contents of the test file The IP address of the CPU module, test execution date, and test execution time are described. For the date and time, the clock data in the CPU module is used.

For IP address: 192.168.3.39, date: October 01, 2017, time: 11:22:33 192.168.3.39_20171001_112233

17 DATA LOGGING FUNCTION 17.10 Data Logging File Transfer (Auto Transfer to FTP Server) 277

27

Setting on the "File transfer" window FTP server connection request timeout time Set the waiting time from when the connection request from the CPU module to the FTP server is sent to when the response is received. If no response is received from the FTP server within the connection request timeout time, an error occurs.

File transfer retry time Set the time to retry the file transfer when the file transfer fails due to an error caused by communication failure such as the network error between the CPU module and the FTP server. The data logging file failed to be transferred is in the standby state and the retry starts. The file is resent until the file transfer retry time elapses. Even when the file transfer fails again due to a communication error, the file will be on standby for the reverse transfer again without an error of the data logging file transfer function.

Ex.

When a data logging file of the data logging setting No.1 has not been transferred due to a network failure

The retry ends when the network is recovered and retry of the file transfer succeeds.

00000001.txt00000001.txt 00000001.txt00000001.txt

Data logging setting No.3

Data logging setting No.2

Data logging setting No.1

Data logging setting No.1

Standby Transfer failed

Transfer order FirstLast

8 17 DATA LOGGING FUNCTION 17.10 Data Logging File Transfer (Auto Transfer to FTP Server)

17

Matching the folder structure of the transfer destination FTP server with the CPU module When the data logging file is transferred, the directory is automatically created in the specified folder path of the FTP server so that the structure is the same as the storage destination ( Page 260 Folder configuration of SD memory cards). If the same file exists, the file will be overwritten. When the folder structure is matched with the CPU module The folder path (1) specified in the server setting, folder structure (2), logging files transferred (3). In the folder structure (2), subdirectories (4) are created.

When the folder structure is not matched with the CPU module The folder structure of the FTP server consists of the storage destination structures of the data logging file excluding the subdirectory. The folder path (1) specified in the server setting, folder structure (2), logging files transferred (3).

LOG01 00000001

00000001.txt

00000002.txt

00000100.txt

/

00000101.txt

00000102.txt

00000101

(1) (3)(2)

(4)

File storage folder

LOG01

00000001.txt

00000002.txt

00000100.txt

/

00000101.txt

00000102.txt

(1) (3)(2)

File storage folder

17 DATA LOGGING FUNCTION 17.10 Data Logging File Transfer (Auto Transfer to FTP Server) 279

28

Deleting files completed transfer At the completion of data logging file transfer, transferred files are automatically deleted. If there is no file in the saved file storage folder (subdirectory) as a result of the file deletion, the saved file storage folder (subdirectory) is deleted while data logging is stopped.

If the function memory is specified as the data storage destination, files are deleted after the transfer regardless of the setting.

Even if "Delete files completed transfer" is specified, data logging stops when the number of files stored by the data logging function exceeds the maximum value of the number of files to be saved. To consecutively execute data logging, set a large number of files to be saved.

LOG01

LOG02

LOG03

00000001.txt

00000002.txt

00000002.txt

00000003.txt

00000004.txt

00000001.txt

00000002.txt

00000001.txt

00000002.txt

00000001.txt 00000001.txt 00000001.txt

File storage folder

Data logging setting No.1

Data logging setting No.1

Data logging setting No.3

Data logging setting No.2

Data logging setting No.1

Data logging setting No.2

Data logging setting No.3

Transfer order

Standby

FirstLast

Transfer completed

0 17 DATA LOGGING FUNCTION 17.10 Data Logging File Transfer (Auto Transfer to FTP Server)

17

Data logging file transfer status The file transfer status, the data logging name, and the IP address of the file transfer destination FTP server can be checked. They can be checked on the data logging file transfer status window of CPU Module Logging Configuration Tool. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

File transfer error log Error history including the date and time of error occurrence, data logging No., and the error codes can be checked. They can be checked on the file transfer error log window of CPU Module Logging Configuration Tool. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

Stopping the data logging file transfer After data logging is stopped, the data logging file transfer stops when no standby file for the data logging file transfer is left. However, after data logging is stopped, if the data logging file transfer is being retried and does not stop, the file transfer in progress can be stopped by following the procedure below.

1. Set the data logging setting number for SD1203 (Data logging file transfer stop information). Multiple data logging setting numbers can be set for SD1203.

2. Turn off and on SM1203 (Data logging file transfer stop request). When multiple data logging setting numbers are specified for SD1203 and SM1203 is turned off and on, SM1203 turns off after the data logging file transfer of all the data logging setting numbers stops.

3. At the completion of the file transfer stop processing, an error is stored in each data logging file transfer error cause of the files being transferred and in the standby (retry) state.

For the file transfer stopped by the stop request, files which have not been transferred cannot be transferred even if the data logging of the same setting number is restarted and the file transfer is executed. To transfer files which have not been transferred, the procedure differs depending on the data storage destination. When the data storage destination is the SD memory card, transfer the files to the server by using the FTP server function. When the data storage destination is the function memory, transfer the files to the data memory by using SM653 (File transfer to data memory request) and transfer the files to the server by using the FTP server function.

When the data logging status of the data logging setting No. which has been set by SD1203 (Data logging file transfer stop information) is other than stop, or the data logging file transfer is not enabled in the data logging setting, turning off and on SM1203 (Data logging file transfer stop request) does not execute the stop processing and SM1203 turns off.

When the data logging is in the collection completed state or when an error occurs, file transfer cannot be stopped by SM1203 (Data logging file transfer stop request). To stop file transfer, stop the data logging function.

17 DATA LOGGING FUNCTION 17.10 Data Logging File Transfer (Auto Transfer to FTP Server) 281

28

17.11 Data Logging File Transfer to Data Memory When the function memory*1 is specified for the data storage destination memory without setting of the file transfer, the data is transferred from the function memory to the data memory at the logging completion or stop (including when an error occurs) as shown below.

*1 For the CPU modules that can use the function memory, refer to the availability of storage location. ( Page 259 Availability)

Behavior when the free space in the data memory is full When multiple data logging files exist in the function memory and the free space in the data memory is full by only transferring some of the files, an error occurs and the files remaining are not transferred. In this case, files that have not been transferred are not deleted from the function memory.

Starting data logging during the data transfer to the data memory The data logging cannot be started during the data transfer to the data memory. An error occurs when starting the data logging. (Page 302 Starting data logging during the data transfer to the data memory) An error during the data transfer to the data memory is stored in SD1217 (Data logging file transfer error cause). ( Page 626 Data logging function)

(1) At the logging completion or stop (including when an error occurs), the data is transferred from the function memory to the data memory. When data logging is suspended or waiting for RUN without collection, the data is not transferred to the data memory.

(2) Data in the function memory is automatically deleted after completion of the transfer. (3) The data logging files transferred to the data memory can be read by engineering tool or displayed by GX LogViewer.

(1)

(2)

(3)

First collected data

Second collected dataDevice/ label area

Setting 1

Internal buffer Function memory

First collected data

Second collected data

Setting 1

First collected data

Second collected data

Setting 1Data collection of the specified device/label

Inside the CPU module

Data memory

2 17 DATA LOGGING FUNCTION 17.11 Data Logging File Transfer to Data Memory

17

17.12 Setting Behavior at the Time of Transition to RUN After the data logging settings are registered by the start operation of data logging, set the behavior of data logging when the following user operations to switch the operating status of the CPU module to RUN are performed (transition to RUN). ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series)) Powering off and on and switching the operating status to RUN Resetting and switching the operating status to RUN Switching the operating status from STOP to RUN

The logging operation can be set individually for each setting number (1 to 10).

Behavior at the time of a transition to RUN The behavior can be selected from the following.

Auto start The data logging automatically starts after the user operation of starting data logging in CPU Module Logging Configuration Tool and switching the operating status of the CPU module to RUN.

[Online] [Logging Status and Operation]

Start by user operation The data logging status becomes "Start waiting (no collection)" after the user operation of starting data logging in CPU Module Logging Configuration Tool and switching the operating status of the CPU module to RUN. To start data logging, operate CPU Module Logging Configuration Tool to start data logging again.

[Online] [Logging Status and Operation]

When the auto logging is used, the behavior of the data logging is always "Auto Start", even if the behavior at transition to RUN is set to "Start by User Operation". ( Page 284 Auto Logging)

Data logging behavior that occurs after operating status of CPU module has changed Data logging does not continue when the operating state of the CPU module changes from RUN to STOP or PAUSE after it has been started. The data logging status changes to "RUN waiting (no collection)" and data collection is stopped.

17 DATA LOGGING FUNCTION 17.12 Setting Behavior at the Time of Transition to RUN 283

28

17.13 Auto Logging When inserting an SD memory card, which holds data logging setting, into the CPU module, the data logging automatically starts based on the data logging setting information on the SD memory card.

How to use auto logging This section describes how to use auto logging.

1. Prepare an SD memory card that contains data logging settings as well as common settings (auto logging common settings) in which auto logging is enabled.

2. Insert the SD memory card prepared in step 1 into the CPU module while it is running.

3. When the SD memory card is inserted, data logging starts automatically. (CARD READY LED and CARD ACCESS LED turn on.)

4. Check that auto logging is completed on the engineering tool or using the LED*1 on the CPU module.

5. Remove the SD memory card. *1 When "Data Logging Function" is set in the LED indicator setting, the FUNCTION LED flashes every 200ms. If the executed function

has higher priority of the FUNCTION LED than the function set in the LED indicator setting, the data logging function status is not displayed. ( Page 172 LED display setting)

Even when the data logging stop operation is performed after auto logging starts, auto logging does not end until when the SD memory card is removed.

To use auto logging, the auto logging common setting file and data logging setting file for operation are required in the SD memory card.

Write the auto logging common setting file to the SD memory card only when using auto logging. When auto logging is not used, delete the auto logging common setting file. ( CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series))

4 17 DATA LOGGING FUNCTION 17.13 Auto Logging

17

Auto logging common setting The following window configures the required settings for using the auto logging function.

Window

Displayed items

Item Description Setting range Default Enable the auto logging function Select this item to use auto logging. Not checked

Auto logging terminate condition

Data logging stop Select the condition to complete the auto logging operation. ( Page 286 Conditions for auto logging completion)

When all data loggings stop

When any of the data loggings stops

When all data loggings stop

Timer Complete with timer

Select this checkbox to stop the auto logging operation by a timer.

Elapsed time Specify the time interval from the start of the data logging until stopping it.

1 to 86400 seconds

17 DATA LOGGING FUNCTION 17.13 Auto Logging 285

28

Auto logging start conditions Auto logging starts in the following cases.

Inserting the SD memory card with the auto logging setting while the CPU module is running Auto logging starts when the SD memory card with the auto logging setting is inserted while the CPU module is running. (When the CPU module is in the STOP state, auto logging starts by changing the state from STOP to RUN.) If data logging is in progress before the SD memory card with the auto logging setting is inserted, auto logging does not start.

Inserting the SD memory card with the auto logging setting while the CPU module is off or being reset, and powering on or resetting the CPU module

Auto logging starts when the CPU module is powered on or reset after the SD memory card with the auto logging setting is inserted while it is off or being reset. If data logging is in progress, powering on or resetting the CPU module executes auto logging instead of the data logging.

Conditions for auto logging completion Auto logging completes when a completion condition is met as described in the following table. These completion conditions can also be configured in combination with each other. When they are configured in combination, auto logging completes as soon as one of the conditions is met.

When "Data logging stop" is selected Auto logging is assumed to be completed if all the settings or any of auto logging stops*1. *1 Here the term "stop" means one of the following:

Continuous logging: When the "Number of files to be saved" setting configured in the save setting has been exceeded and data logging has been completed. Trigger logging: When as much data as the number of records specified in "Number of records" has been collected, the collected data has been written to the SD memory card, and data logging has been completed. When the user has operated CPU Module Logging Configuration Tool to stop data logging.

If "When any of the data loggings stops" is selected, the behavior of any other data logging sessions than stopped is the same as the behavior that occurs upon the elapse of the time configured using "Complete with timer".

When completing auto logging for continuous logging, do not select "Overwrite" for the operation at the time when the number of files exceeds the save setting because doing so results in failure to stop data logging; instead, select "Stop".

When "Complete with timer" is selected When the operating time since the start of data logging reaches the specified time, the CPU module completes auto logging by moving all the data collected so far from the internal buffer to the SD memory card. If trigger logging has not yet collected as much data as the number of records specified "Number of logging lines", however, the CPU module does not store any data including the collected data.

The timer is cleared to zero when auto logging is suspended and resumed by stopping and running the CPU module or turning off and on the CPU module or resetting it before the completion of auto logging. If auto logging is suspended by the turning off and on of the special relay (Data logging suspend/resume flag), the timer continues to run even while data logging is suspended.

Completion condition Description Data logging stop Choose one of the following:

When all data loggings stop When any of the data loggings stops

Complete with timer Auto logging is stopped when the specified time has elapsed after the start of data logging. Elapsed time setting range: 1 second to 86400 seconds (unit: second)

6 17 DATA LOGGING FUNCTION 17.13 Auto Logging

17

Conditions under which auto logging does not start Doing any of the following operations once auto logging is completed does not start auto logging: Turn off and on the power Reset STOP to RUN state If data logging is in progress before the SD memory card with the auto logging setting is inserted, auto logging does not start as well.

Behavior of auto logging at the time of a transition to RUN If some, not all, of data logging sessions configured using auto logging have been completed when entering into the RUN mode, only the uncompleted data logging sessions are started.

Behavior of auto logging that occurs when an error is generated When an error is generated, auto logging behaves as follows:

When an error is generated at the start of auto logging (Registration of the data logging settings has failed.)

If auto logging cannot be started (registration has failed), it behaves in the same way as when it is completed.

When an error has occurred during the execution of auto logging An error that occurs during the execution of auto logging does not constitute the auto logging completion condition since it does not prevent data logging from being resumed. If such an error is resulting from an online change during the execution of auto logging, however, it constitutes the auto logging completion condition because it prevents data logging from being resumed.* 1

*1 Applies only when "When all data loggings stop" is selected as part of the auto logging completion condition.

17 DATA LOGGING FUNCTION 17.13 Auto Logging 287

28

17.14 SD Memory Card Replacement SD memory cards can be replaced using the SD memory card forced disable function even while data logging is in progress. Page 132 How to forcibly disable the SD memory card with a special relay Only the data saving to an SD memory card is stopped while this function is being executed. The data collection keeps working. (Data collection continues in accordance with the settings registered when data logging is started.) With the setting for the file transfer, an error occurs when the SD memory card is replaced during the file transfer. ( Page 537 Codes of errors detected by other than the self-diagnostic function (4000H to 4FFFH))

If SD memory card replacement causes processing overflow, make adjustments by changing the collection interval, internal buffer capacity, or other settings.

Behavior during SD memory card replacement If the internal buffer becomes full during the time between SD memory card replacement and the resumption of data writes to the SD memory card, processing overflow occurs resulting in missing data.

Storage file numbers after SD memory card replacement The numbering of the first storage file created after SD memory card replacement differs depending on the storage file switching condition, as described in the following table.

*1 While the data logging file transfer function is used, numbering begins at 00000001 only when the "Delete files completed transfer" is disabled in the "File transfer" setting of CPU Module Logging Configuration Tool.

If the new SD memory card contains a "LOGGING" folder and its subfolders, folder deletion takes time, possibly resulting in missing data. Ensure that the new SD memory card does not contain a "LOGGING" folder.

Logging state during SD memory card replacement SD memory cards can be replaced without depending on the current data logging state. SD memory card replacement results in the deletion of the LOGGING folder if the data logging state is other than below: Stop Stop (after collection) Stop (after error)

Operations during SD memory card replacement If one of the following operations is performed during the time between the removal and installation of SD memory cards, any data collected during that time will not be stored in the new SD memory card. STOP to RUN state*1

Power-on to RUN state*1

Reset*1

Suspend data logging Stop data logging *1 An error is generated if data logging was previously running based on the setting file contained in the replaced SD memory card.

Storage file switching condition Storage file numbers after SD memory card replacement Overwrite Numbering continues from the number of the last storage file contained in the replaced SD memory card.

Stop Numbering begins at 00000001.*1

8 17 DATA LOGGING FUNCTION 17.14 SD Memory Card Replacement

17

Operations after SD memory card replacement If the SD memory card was replaced while data logging was running based on the data logging setting file contained in the SD memory card, the data logging setting file contained in the new SD memory card is used when data logging is started by one of the following operations. If the new SD memory card does not contain the data logging setting file, data logging is not started. STOP to RUN state Power-on to RUN state RESET to RUN state Data logging start

Stack file remaining in the replaced SD memory card Replacing an SD memory card that contains a stack file may result in the storage file remaining in the replaced SD memory card along with storage files. If the stack file is remaining in the replaced SD memory card, recover the latest data contained in the stack file by doing the following: Retrieve the data from the stack file and combine the data with a storage file. Save the stack file as a storage file.

17 DATA LOGGING FUNCTION 17.14 SD Memory Card Replacement 289

29

17.15 SD Memory Card Life When the Data Logging Function Is Used

An SD memory card has a life (restriction on writing data). The following shows the calculation method of an SD memory card life when the data logging function is used. Note that the actual life of the card varies depending on the use conditions and environment. Therefore, use the calculated life as a rough standard for the replacement of the card.

Calculation formula of SD memory card life SD memory card life (year) = Total size of data that can be written (G bytes) Size of data to be written per year (G bytes/ year)

Total size of data that can be written Capacity Number of writes*1

*1 For the capacity of applicable SD memory cards and the number of writes, refer to the following. MELSEC iQ-R Module Configuration Manual

Size of data to be written per year The size of data to be written per year is obtained by the following formula. Size of data to be written per year (G bytes/year) = ((DS1*1 + 6144) DN1 + + (DSn*1 + 6144) DNn + (DCS1*1 + 6144) DCN1 + + (DCSn*1 + 6144) DCNn) 1073741824 *1 Round up DSn and DCSn to a multiple of 512.

DSn, DNn, DCSn, and DCNn are obtained as follows.

Data logging data size per record (DSn) Binary file output format: Refer to the data. ( Page 254 Binary file output format) Unicode text file format: Refer to the data row. ( Page 243 Unicode text file output type)

Number of records for data logging per year (DNn) Continuous logging: DNn = 60 60 24 365 Collection interval and timing (seconds)*1 Operating rate*2

Trigger logging: DNn = Total number of records*3

*1 The value that is determined depending on the condition set in "Sampling" when "Continuous logging" is selected for the logging type. (When the value is determined in milliseconds, convert the value into seconds.)

*2 Calculate the ratio using the operating time per year of the CPU module. For example, if the operating time per year is 5000 hours, the operating rate is calculated as follows: 5000 (24 365) = 0.57.

*3 The value set in "Number of logging lines" when "Trigger logging" is selected for the logging type.

Header size of data logging (DCSn) Binary file output format: Refer to the header. ( Page 254 Binary file output format) Unicode text file format: Refer to the file information row to device comment row. ( Page 243 Unicode text file output type)

Number of file switching times for the data logging per year (DCNn) Calculate this number with an estimated number according to the save setting of the data logging and system operations. For example, when 1000 records are set in "Number of records" of "File switching timing" in the save setting and "Each scanning cycle" is specified for "Sampling interval" in the sampling setting, the time interval of the file switching is obtained by multiplying the scan time by 1000. Therefore, the number of file switching times for the data logging per year is obtained by the following formula: 60 60 24 365 (Scan time (second) 1000)

0 17 DATA LOGGING FUNCTION 17.15 SD Memory Card Life When the Data Logging Function Is Used

17

17.16 Errors Generated During Data Logging No diagnostic error occurs if an error occurs during data logging, the SM applicable to the special relay (data logging error) setting No. turns on, and the error cause is stored in the SD applicable to the special register (data logging error cause) setting No.

17.17 Special Relay and Special Register Used by the Data Logging Function

For details on the special relay and special register areas used by the data logging function, refer to the following: Special relay: Special relay areas relating to the data logging function (Page 595 Data logging function) Special register: Special register areas relating to the data logging function ( Page 626 Data logging function)

17 DATA LOGGING FUNCTION 17.16 Errors Generated During Data Logging 291

29

17.18 Precautions to Take When Using the Data Logging Function

This section describes precautions to take when using the data logging function.

Mutual exclusion of the data logging function This section describes the mutual exclusion of the data logging function.

When another function is executed during the execution of the data logging function The following table lists the cases where another function is executed during the execution of the data logging function.* 1

Function that has been already executed

Function to be executed later

Behavior

Data logging function Data logging function When the data logging is started using CPU Module Logging Configuration Tool to the same data logging setting number via another route, the data logging to be executed later cannot be executed. However, the data logging to be executed later can be executed to a data logging setting number different from the data logging setting number currently being executed.

The data conditions cannot be specified as the trigger conditions for multiple trigger conditions at the same time.

For the execution of multiple data loggings, the data logging settings stored in different target memory areas cannot be executed at the same time.

Auto logging The auto logging cannot be executed during the execution of the data logging. (Even though an SD memory card where the auto logging setting is written is inserted, the auto logging does not start.)

Online change (ladder block)

When a step number is specified as the collection start condition or trigger condition A data logging error occurs. The online change (ladder block) is completed.

When a label is specified as the collection start condition, data collection target, or trigger condition When the bit of the corresponding setting No. of SD940 (Stop direction at file change on label

specification) is on, changing the global label setting file (when the global label is specified) or the program file (when the local label is specified) to files different from the ones at the start operation of data logging causes a data logging error.

The online change (ladder block) is completed.

File batch online change

When a step number is specified as the collection start condition or trigger condition A data logging error occurs. File batch online change is completed.

When a label is specified as the collection start condition, data collection target, or trigger condition When the bit of the corresponding setting No. of SD940 (Stop direction at file change on label

specification) is on, changing the global label setting file (when the global label is specified) or the program file (when the local label is specified) to files different from the ones at the start operation of data logging causes a data logging error.

File batch online change is completed.

CPU module data backup function

The CPU module data backup function cannot be executed while a logging setting file is being written/deleted or a logging setting is being registered/cleared.

CPU module data restoration function

The CPU module data restoration function cannot be executed while a logging setting file is being written/read/deleted or a logging setting is being registered/cleared.

iQ Sensor Solution data backup/ restoration function

The iQ Sensor Solution data backup/restoration function cannot be executed while a logging setting file is being written/deleted or a logging setting is being registered/cleared.

Function specified in the internal buffer capacity setting*2

If the internal buffer capacity setting is changed to execute the subsequent function, attempting to start the subsequent function results in an error. The data logging continues to function normally.

Function not specified in the internal buffer capacity setting

If the condition "Total capacity that is set in the internal buffer capacity setting + Internal buffer capacity that is set in other than the internal buffer capacity setting > 3072K bytes" is satisfied, attempting to start the subsequent function results in an error. The data logging continues to function normally.

If the internal buffer capacity setting is changed to execute the subsequent function, attempting to start the subsequent function results in an error. The data logging continues to function normally.

Auto logging Data logging function Another data logging cannot be executed during the execution of the auto logging. Even if data logging is started by using CPU Module Logging Configuration Tool, another data

logging cannot be executed until the SD memory card with the auto logging setting is removed.

Data logging function (when the storage location is the function memory)

File batch online change

The file batch online change cannot be executed during data logging (when the storage location is the function memory).

2 17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function

17

*1 The data logging function is being executed in the following states where the data logging status remains intact or when the save status is "Saving". RUN waiting (no collection) Condition waiting (no collection) Start waiting (no collection) Pause Collecting Trigger waiting (Collecting before trigger) Collecting after trigger In the states other than the above, although the functions can be executed, the registration of the data logging setting executed first is canceled when the data logging function or another function is executed.

*2 The data logging function is not included here.

When the data logging function is executed during the execution of another function The following table lists the cases when the data logging function is executed during the execution of another function.

*1 The data logging function is not included here. *2 The CPU module data backup/restoration function executed during data logging *3 It is executed when the trigger logging data collection is completed or data collection for the specified number of storage files is

completed.

Data logging file transfer (when the storage location is the function memory)

File batch online change

The file batch online change cannot be executed during data logging file transfer (when the storage location is the function memory).

Data logging function (Transfer to the data memory)

CPU module data backup function

The CPU module data backup function cannot be executed during data logging file transfer to the data memory.

CPU module data restoration function

The CPU module data restoration function cannot be executed during the data logging file transfer to the data memory.

Function that has been already executed

Function to be executed later

Behavior

Online change (ladder block) Data logging function When a step number is specified as the collection start condition or trigger condition or when a label is specified as the collection start condition, data collection target, or trigger condition The online change (ladder block) is completed. The data logging cannot be executed. (An error occurs when the start operation of the data

logging is performed during the online change (ladder block).)

File batch online change When a step number is specified as the collection start condition or trigger condition or when a label is specified as the collection start condition, data collection target, or trigger condition File batch online change is completed. The data logging cannot be executed. (An error occurs when the start operation of the data

logging is performed during the file batch online change.)

CPU module data backup function

While the CPU module data backup function is being executed, a logging setting file cannot be written/deleted or a logging setting cannot be registered/cleared.

CPU module data restoration function

While the CPU module data restoration function is being executed, a logging setting file cannot be written/read/deleted or a logging setting cannot be registered/cleared.

iQ Sensor Solution data backup/restoration function

While the iQ Sensor Solution data backup/restoration function is being executed, a logging setting file cannot be written/deleted or a logging setting cannot be registered/cleared.

Function specified in the internal buffer capacity setting*1

If the internal buffer capacity setting is changed to execute data logging, attempting to start data logging results in an error. The function already in execution continues to function normally.

Function not specified in the internal buffer capacity setting

If the internal buffer capacity setting is changed to execute data logging, attempting to start data logging results in an error. The function already in execution continues to function normally.

CPU module data backup function*2

Data logging function (Transfer to the data memory)*3

While the CPU module data backup function is being executed, a data logging file cannot be transferred to the data memory.

CPU module data restoration function*2

While the CPU module data restoration function is being executed, a data logging file cannot be transferred to the data memory.

Function that has been already executed

Function to be executed later

Behavior

17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function 293

29

When a file operation related to the data logging is performed during the execution of the data logging function

The following table lists the cases when a file operation related to the data logging is performed during the execution of the data logging function.

When an attempt is made to write the data logging setting file during the execution of another function

The following table lists the cases when an attempt is made to write the data logging setting file during the execution of another function.

Locations from which data logging can be performed Data logging cannot be performed from multiple locations to the same setting number. The CPU module supports data logging performed concurrently at a maximum of 10 locations assigned to setting numbers 1 to 10.

Retention and clearance of data logging settings After the data logging is started, the registered data logging settings are latched. Thus, if the data logging is started (registered) before powering off and on or resetting the CPU module, register the settings again when performing the following operations to the CPU module; Powering off and on and switching the operating status to RUN; Resetting and switching the operating status to RUN; Switching the operating status from STOP to RUN. As a result, data logging can be executed again with the registered data logging setting. However, the registration of the data logging settings is canceled in the following cases. (The corresponding SM number to the data logging setting number among relevant special relay areas (data logging preparation) turns off.) The CPU module is turned off and on or is reset without an SD memory card that contains the data logging setting file. The replaced SD memory card does not contain the data logging setting file and the CPU module is turned off and on or is

reset.* 1

*1 If the data logging setting file contained in the replacement (new) SD memory card is different from that contained in the replaced (old) SD memory card, register the data logging setting file contained in the replacement SD memory card.

It is necessary to register the data logging settings again by the user operation of starting data logging in CPU Module Logging Configuration Tool.

Target file File operation Behavior Data logging setting file/common setting file

Write/delete During execution of the data logging function, data cannot be written/deleted to/in the data logging setting file/common setting file being used.

Folder delete Folders cannot be deleted from the $MELPRJ$ folder in which the data logging setting files and the common setting file are stored.

Initialize During execution of the data logging function, the memory storing the data logging setting files and the common setting file being used cannot be initialized.

Data logging file Write/delete/folder delete During execution of the data logging function, data cannot be written/deleted to/in or folders cannot be deleted from the data logging file being used.

Initialize During execution of the data logging function, the memory storing the data logging file being used cannot be initialized.

Function that has been already executed

Behavior

Online change (ladder block) When a label is specified as the collection start condition, data collection target, or trigger condition The online change (ladder block) is completed. The data logging setting file cannot be written.

File batch online change When a label is specified as the collection start condition, data collection target, or trigger condition File batch online change is completed. The data logging setting file cannot be written.

4 17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function

17

Behavior that occurs when trigger logging is resumed If data logging is stopped or collection is suspended before the completion of trigger logging and subsequently data logging is run again, data collection begins from the initial state before trigger logging, rather than continuing from the last time.

Stopping/suspending data logging using CPU Module Logging Configuration Tool After data logging is stopped or suspended from CPU Module Logging Configuration Tool, all the data in the internal buffer are saved into the target memory. If a small number of records or a small file size is specified as part of the storage file switching condition, saving data to the target memory may take longer.

Error that occurs when the data logging is started Behavior when an error occurs at the start of the multiple data logging settings at the same time is as follows: If the start operation is performed by using CPU Module Logging Configuration Tool, the CPU module runs data logging for

the setting files that have been successfully registered. If the auto logging is started, the CPU module does not run any data logging session.

Behavior upon change of the internal buffer capacity When the internal buffer capacity is changed during execution of the data logging function, note that: If the internal buffer capacity for the setting number of the running data logging is left empty to disable the capacity, an error

occurs when the data logging is stopped and restarted (write to the programmable controller does not cause an error). If the internal buffer capacity of the setting number of the running data logging is changed to a smaller value, data may be

lost when the data logging is stopped and restarted.

Trigger condition at the start operation of data logging Ensure that the trigger condition is not met during the registration of the data logging settings by the start operation of data logging. If the trigger condition is met, the data logging settings cannot be registered.

When file register is specified as device/label in condition specification After registration of data logging, do not change the file name and block number of the file register file in the following cases; the file register is specified as the device or the global label where the file register is assigned as the label for the condition specification in the "Sampling" and "Trigger" settings. Doing so may possibly result in failure to successfully collect data logging results.

When the data collection condition is set to "Time specification" If "Time specification" is selected for the data collection condition, data collection is performed as an interrupt processing operation and therefore special care should be taken when configuring the data collection interval, the data collection timing, and the data logging processing time per scan. In the following cases, scans may take a longer time, possibly resulting in a WDT error: The collection interval and the collection timing are so short that data logging is frequently performed during a single scan. The data to be collected is so much that the data logging processing time per scan is long.

17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function 295

29

Numbering of the storage files used during data logging If one or more numbered storage files already exist in the file storage folder The new file is given a file name that uses a number incremented by one from the highest number among the existing files. When the setting for files that has been completed to transfer is specified to delete in the file transfer setting, numbering to new storage files starts from 1 because no files exist in the folder at the time of restarting data logging.

If one or more storage file folders exist but no storage files in them A new file is stored into a folder with the lowest number and given the same number as the folder. However, if there are 258 or more folders, a new folder is created and the file in it is given the same number as the new folder. When the file that has been completed to transfer is specified to delete in the file transfer setting, the existing folders are deleted if no files exist in the folders when the data logging stops. (The existing folders are not deleted while the data logging is in progress.)

Behavior that occurs while collected data is stored in the target memory If one of the following operations is performed while collected data is stored in the target memory, any unsaved data is cleared and not reflected to the results: Powering off and on the CPU module Reset If one of the following operations is performed, unsaved data continues to be stored in the target memory: Changing the operating status of the CPU module from RUN to STOP Suspending the data logging by turning off and on of the special relay areas SM1312 to SM1321 (Data logging setting No.1

to 10 Data logging suspend/resume flag) Stopping/suspending data logging from within CPU Module Logging Configuration Tool Issuing the LOGTRGR instruction

Creating files and folders Under the "LOGGING" folder that contains data logging setting files and data logging files, do not attempt to create files or folders using a personal computer or other device. Doing so may result in deletion of files and folders.

When collection is performed at the specified time When "Time specification" is selected for the data collection condition and the collection at the specified time is selected rather than data collection during the END processing, check the collection interval by referring to the information reported in the collection interval column. Do not rely on the information reported in the date/time column because it may be incorrect due to clock accuracy error.

Changing the clock data Whatever changes, such as advancing or reverting the clock, are made to the clock data of the CPU module during data logging, the CPU module performs data collection at the specified collection interval/timing, but the date/time column in the output file reports the changed clock data.

Events that are not recognized as a trigger condition For trigger logging, the following events are not recognized as a trigger condition: A second trigger condition is met after the first trigger condition is met. The data condition specified as part of the trigger condition is met within the I49 interrupt program.

If a data condition is specified as part of the trigger condition, any trigger condition met during the execution of the I49 interrupt program will not be recognized as a trigger condition. In this case, using I48 instead of I49 allows for avoiding the timing when the condition is not met.

6 17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function

17

Access to an SD memory card or the function memory If data logging is performed with a setting that the data collection interval is short or the number of records to be collected is large, access (read/write) to an SD memory card or the function memory occurs so frequently that a delay occurs in completing the access. To avoid such a delay, use the following workarounds: Increase the data collection interval/timing. Reduce the number of data records to be collected. Lower the frequency of file switching.

Access to the CPU module during data logging When the multiple data logging settings are started at the same time (when the multiple data logging settings are registered again at the same time), a time-out error may occur in communications or a dedicated instruction issued from a peripheral to the CPU module. Take measures such as increasing the time-out time period of the peripheral, reducing some data logging settings, and stopping the other functions.

Behavior at parameter change when functions consuming the internal buffer are active If the internal buffer capacity setting is changed during the execution of the functions that consume the internal buffer, attempting to start data logging results in an error, where the data logging fails to start.

CPU module operation when registering the data logging Note that the operating status of the CPU module is not changed until the following data logging registration or data save processing is completed. (The operating status may not be switched to STOP immediately.) While saving the data in the internal buffer by changing the operating status of the CPU module from RUN to STOP or

operation to stop/pause data logging from CPU Module Logging Configuration Tool When the multiple data logging settings are started at the same time (when the multiple data loggings are registered again

at the same time) When the data logging is started with any unused folders remaining in the storage memory The waiting time for the operation status change of the CPU module is shortened by reducing the number of data logging settings and deleting unused folders.

Unicode text file To view the data, use a software application with Unicode support. The data may be displayed incorrectly in a software application with no Unicode support. To open a Unicode text file with multiple lines of comments in Microsoft Excel, be sure to drag and drop the file on the Microsoft Excel window; otherwise, the content of the file may be displayed incorrectly in Microsoft Excel.

Function that consumes the internal buffer other than data logging

Data logging

Function in execution

Function in execution An error occurs. Data logging is not allowed to start.

Internal buffer capacity setting changed (by changing the parameters of internal buffer capacity setting)

Data logging stopped (by clicking [Stop] button)

Data logging attempted to start (by clicking [Start] button)

17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function 297

29

Registration of the available devices User device, system device, file register, and index register The data logging settings can be registered when devices of the CPU module exist. When a device number outside the range is specified, an error occurs at the registration.

Module access device (buffer memory) and link direct device The data logging settings can be registered when the buffer memory and devices of the target module exist. When the target module is not mounted or a device number outside the range is specified even with the target module mounted, an error occurs at the registration.

Local device The data logging settings can be registered when the target program name and devices in the target program exist. When a device number outside the range of the target program is specified, an error occurs at the registration.

Local index register, local long index register, and file register in which "Use File Register of Each Program" is set

The program name cannot be specified for the following devices. Local index register Local long index register File register in which "Use File Register of Each Program" is set To perform data logging of the above devices, transfer the data of the above devices to the global device on the program using the engineering tool beforehand. For the data logging device, specify the global device where the data is transferred. The data to be logged is the data specified in the data collection condition.

File operation during execution of data logging This section describes file operation during execution of data logging.

About remote operation When remote RUN is performed while the data logging function is in the following execution status, the remote RUN may fail. In that case, wait for a while and retry remote RUN. If remote RUN still cannot be executed, check whether remote RUN is acceptable and retry remote RUN.

Target file File operation Behavior Data logging setting file Write During execution of data logging, it is not possible to write/delete data to/in

the data logging setting file being used.Delete

Initialize During execution of data logging, it is not possible to initialize the memory storing the data logging setting file being executed.

Folder delete Folders cannot be deleted from the $MELPRJ$ folder in which the data logging setting file is stored.

Data Logging File Write During execution of data logging, it is not possible to write/delete data to/in and delete folders from the data logging setting file being used.Delete

Folder delete

Initialize During execution of data logging, it is not possible to initialize the memory storing the data logging setting file being executed.

Execution state of data logging function The situation to accept remote RUN Saving data in the internal buffer into a storage location in progress No special relay (Data logging data saving in progress) is on.

After the start operation of data logging by CPU Module Logging Configuration Tool (Registration of the data logging setting in progress)

The special relay (data logging preparation) and the special relay (data logging start) corresponding to the setting number of the data logging setting, which is being registered in the way shown in the left column, are on.

After data logging is started by auto logging (Registration of the auto logging setting in progress)

SM1200 (Auto logging setting file and registration status) is on.

8 17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function

17

RUN operation through switching operation or the RUN contact During execution of data logging, when the status of the CPU module is switched from STOP to RUN with the RUN/STOP/ RESET switch, or when the RUN contact that is specified in the RUN-PAUSE contact setting turns off, it may take time to return to the RUN state.

Using together with interrupt programs When occurrence of an interrupt is specified as the data collection condition of data logging, the processing time of the interrupt program increases because the processing time of the data logging function is added. When the sampling method of the recording function is set to use the trigger instruction in an interrupt program, the processing time of the interrupt program also increases because the sampling processing time for the recording function is added. For this reason, a WDT error may occur if an interrupt interval of I49 set in the parameter of "Interrupt Setting from Internal Timer" under "Fixed Scan Interval Setting" is too short (such as 0.05ms) and occurrence of I49 is specified as the data collection condition, since the processing time of the interrupt program becomes longer than the set interrupt period and the END instruction cannot be executed due to the continuous execution of the interrupt program. For how to reduce processing time of interrupt programs, refer to Saving/restoring of the file register (R) block number. ( Page 111 Saving/restoring of the file register (R) block number)

Data logging using the function memory as the data storage destination Power-off or reset during data logging During data logging using the function memory as the data storage destination, do not power off or reset the CPU module. During data logging, if the CPU module is powered off or reset before completion of the data transfer to the data memory (before data logging is completed or stopped), all the data logging data (data logging files) in the function memory are deleted. When the data logging file transfer function is used, all data logging data in the standby state are deleted as well. When data logging is restarted after power-off or reset, a new data logging file is given a file name that uses a number incremented by one from the end number of data logging file in the function memory before power-off or reset.

Starting data logging during the file batch online change Do not start the data logging using the function memory as the data storage destination during the file batch online change. Otherwise, an error occurs at the start operation of data logging.

17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function 299

30

Data logging file transfer (FTP server auto transfer) Operations and functions that cannot be performed While the following operation or function is being executed, the data logging file transfer function cannot be executed. Auto logging

Data collection performance The performance of the data collection is decreased compared to when the data logging file transfer function is not used. As a result, missing may occur in the data logging setting in which no missing has occurred. When a missing has occurred, the frequency of missing may be increased. ( Page 272 Switching to a storage file)

SD memory card during data logging file transfer If the SD memory card is specified as the data storage destination of data logging files, an SD memory card cannot be replaced during data logging file transfer. ( Page 288 Conditions under which missing data occurs) If the SD memory card forced disable function is executed or the SD memory card is removed during data logging file transfer, a file transfer error occurs.

Powering off and on or a reset operation during file transfer If the CPU module is powered off and on or is reset during data logging file transfer, data logging files being transferred may remain in the FTP server. The files being transferred and in the standby (retry) status are not transferred again.

File transfer at power-off or reset The files being transferred and in the standby (retry) status when the CPU module is powered off or reset are not transferred again after the power-on or reset.

Error at "Overwrite" operation of the data logging file When "Overwrite" is selected for the operation at the time when the number of files exceeds the maximum number of files to be saved, the file being transferred may be overwritten and a file transfer error may occur if the Ethernet line is busy. To ensure the file transfer, configure the following settings.

1. Set a large value for "Number of files to be saved".

2. Set "Stop" for "Operation when exceeds the number of files".

3. Configure the setting to delete files that complete data logging file transfer. ( Page 280 Deleting files completed transfer)

Port number when using the socket communications function For the data logging file transfer function, the own station port numbers F230H to FFFEH are used. Thus, do not specify the own station port numbers F230H to FFFEH for the connection establishment instruction (SP.SOCOPEN) of the socket communications function while the data logging file transfer function is executed. Otherwise, the instruction may be completed with an error.

SLMP communications For the SLMP communications, port numbers set with the parameters take a priority. Thus, the SLMP communications are not affected by this function even if F230H to FFFEH are specified for the own station port number with the parameters.

File transfer processing time The file transfer processing time differs depending on the Ethernet line load ratio (network congestion), the operating status and system configuration of other communication functions.

Communications during the data logging file transfer Since the Ethernet communication load is high during the data logging file transfer, the behavior is as follows. When other communication functions such as MELSOFT connection and SLMP communications are executed using UDP,

data may be lost at UDP reception and timeout and other errors may occur. Use TCP for communications while this function is executed.

When other communication functions such as MELSOFT connection and SLMP communications are executed, their completion are delayed.

0 17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function

17

A data logging file with a file transfer error If a communication error, a file access error, or a file transfer stop error occurs during the file transfer, the data logging files being transferred may remain in the FTP server. Do not refer to those data logging files since the data is not guaranteed. (Data logging files in which a file transfer error has occurred can be checked in the file transfer error history.)

Data logging stop operation at logging out from the FTP server Even when the data logging file is transferred successfully, a data logging file transfer error occurs if the operation to stop data logging file transfer function is performed before logging out from the FTP server or logout fails.

Timing for DNS setting To enable the DNS setting, the CPU module needs to be powered off and on or reset. Therefore, when DNS is set during logging, data in the function memory is deleted if the function memory is specified as the data logging file storage destination. Configure the DNS setting before the logging starts.

When the function memory is specified for the data storage destination When the function memory is specified for the data storage destination, do not power off or reset the CPU module until the file transfer is completed. Doing so deletes all the data logging files which have not been transferred (standby) in the function memory.

File access during the data logging file transfer Do not read files in the SD memory card during the file transfer. The transferred files can be read from the server. If a data

logging file in the CPU module is read by using GX LogViewer during the data logging file transfer, the file being read may be deleted by the setting to delete the transferred files and a file read error may occur.

When a file is accessed (read/write) during the data logging file transfer, the completion for the file access may be delayed depending on the number of files.

Starting data logging during the file transfer Since the data logging of the same setting number cannot be started during the file transfer to the FTP server, start data logging after completion of the file transfer. Otherwise, an error occurs at the start operation of data logging.

17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function 301

30

Data transfer to the data memory Free space in the data memory When the transfer to the data memory is set, delete data by user data operation in the engineering tool to free up space in the data memory for storing the transferred data logging files. When a file transfer error occurs due to out of data memory space during transfer to the data memory, free up the required space and turn off and on SM653 (File transfer to data memory request) to transfer the data to the data memory again. Check the required free space for transfer to the data memory as follows. Required free space for transfer to the data memory = Function memory capacity*1 - Function memory free area capacity*2. *1 The size can be checked in SD648/SD649 (Function memory capacity). *2 The size can be checked in SD650/SD651 (Function memory free space capacity).

The data logging file in the function memory are not deleted by transferring data to the data memory by using SM653. Thus, after transferring data to the data memory by using SM653, it is recommended to turn off and on SM652 (Function memory clear request) and delete unnecessary files in the function memory for the next data logging.

When the CPU module is in the STOP state and data logging is in the pause state When the CPU module is in the STOP state, and the data logging is in the pause state, data is not transferred to the data memory. Turn off and on SM653 (File transfer to data memory request) as necessary and transfer data to the data memory again.

Power-off or reset during the data transfer to the data memory When an error occurs during the data transfer to the data memory, all data logging files in the function memory are deleted

when the CPU module is powered off or reset. Turn off and on SM653 (File transfer to data memory request) as necessary and transfer data to the data memory again.

During the data transfer to the data memory, a temporary file "LOGGING_T.TMP" is created and file name is changed after completion of the file transfer. Therefore, if the CPU module is powered off or reset during the transfer, the temporary file may remain. In that case, delete the file by user data operation in the engineering tool.

Starting data logging during the data transfer to the data memory Since the data logging of the same setting number cannot be started during the data transfer to the data memory, start data logging after completion of the file transfer. Otherwise, an error occurs at the start operation of data logging.

2 17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function

17

Data in the CPU module when a device/label is specified Before starting the data logging, write the following data to the CPU module from the engineering tool.

In the following cases, data cannot be written with CPU Module Logging Configuration Tool.

CPU parameter at the start operation of data logging When performing data logging in which the local device or local label specifying the program name (execution order) in the program setting of the CPU parameter is specified, do not change and write the CPU parameter to the CPU module after writing the data logging setting file. An error occurs during data logging registration after the CPU parameter is written. Change the internal buffer capacity in the CPU parameter used for data logging before writing the data logging setting file.

Change of the file when a label is specified Do not perform the following operations after the registration of the data logging setting by starting the data logging or between the completion of writing the data logging setting file and the registration of the data logging setting.

These operations change assignment of labels, and thus the data logging may not be performed to the specified label. If a file is changed, perform either of the following operations. Import the project of the engineering tool to CPU Module Logging Configuration Tool again, and then write the data logging

setting again. Read the file from the CPU module with "Online Data Operation" of the engineering tool. Save the project with the

engineering tool and import the project to CPU Module Logging Configuration Tool again, and then write the data logging setting again.

Using SD940 (Stop direction at file change on label specification) can prevent the data logging to a different file. Turning on the bit of SD940 corresponding to the data logging setting No. being executed generates an error at the following timings. When the data logging is being executed: At writing a program file or global label setting file When the data logging is stopped or paused: At the registration of the data logging after a program file or

global label setting file is written For details on SD940, refer to the following. Page 624 Latch area

Device/label specification Data required to be written When a local device is specified The CPU parameter including the program name specified with CPU Module Logging Configuration Tool

When a global label is specified Project data that is read using CPU Module Logging Configuration Tool (global label setting file)

When a local label is specified Project data that is read using CPU Module Logging Configuration Tool (the program file with the corresponding program name)

The CPU parameter including the program name specified with CPU Module Logging Configuration Tool

Device/label specification Description When a local device is specified The CPU parameters do not exist in the CPU module.

The program name specified is not set in the program setting in the CPU parameters.

When a global label is specified The global label setting file does not exist in the CPU module. The global label setting file in the CPU module and the project that is read using CPU Module Logging Configuration

Tool (global label setting file) do not match.

When a local label is specified The CPU parameters and the program file which has the corresponding program name do not exist in the CPU module. The program name is not set in the program setting in the CPU parameters. The program file which has the corresponding program name in the CPU module and the project that is read using CPU

Module Logging Configuration Tool (the program file which has the corresponding program name) do not match.

Label specification Description When a global label is specified Writing the global label setting file where a global label is added, changed, or deleted.

When a local label is specified Writing a program file where a program is changed (including addition, change, and deletion of a local label).

17 DATA LOGGING FUNCTION 17.18 Precautions to Take When Using the Data Logging Function 303

30

18 DEBUG FUNCTION This chapter describes the functions used for debugging.

18.1 Memory Dump Function This function stores device values of the CPU module at any given timing. Checking data at the desired timing through the function facilitates the analysis of troubles, the occurrence of which depends on a particular condition.

This function cannot be used in the R00CPU. Before executing the function, check the versions of the CPU module and engineering tool used. (

Page 700 Added and Enhanced Functions)

Item Description Reference Online change (ladder block) Changes and writes a part of the program and data online. Page 155 Online change (ladder

block)

Memory dump function Stores device values of the CPU module at any given timing. Page 304 Memory Dump Function

(1) Perform memory dump settings. (2) Enters a wait state for the trigger after the memory dump setting file has been written. (3) Establishment of the trigger condition (4) Start of data collection (5) The LED on the front of the CPU module allows memory dump status to be checked. ( Page 310 LED status) (6) The memory dump file is stored in the SD memory card. ( Page 309 Memory dump file)

(1)

(3)

(5)

(6)

(4)

Engineering tool Power-on

Time

Devices

SD memory cardDevice/label memory

(2)

4 18 DEBUG FUNCTION 18.1 Memory Dump Function

18

Object data This section describes the data to be collected by memory dump.

Data to be collected Of the devices listed below, all devices that are within the range specified in the device settings are subject to the collection.

*1 Includes local devices as well. Note that to the memory dump file, the program names of collected local devices are output. *2 All file registers that exist in the device/label memory are collected. *3 The CPU module where the SFC function can be used supports this device. ( Page 700 Added and Enhanced Functions)

Trigger condition The following table lists the conditions to be used as a trigger. Set the trigger condition in the memory dump settings. ( GX Works3 Operating Manual)

On the occurrence of consecutive triggers, if data collection due to the previous occurrence of trigger is completed and the status is "Trigger-wait not collected", the next trigger is recognized as a trigger again. Note that events other than the above are not recognized as a trigger condition.

A trigger can be generated with trigger conditions combined. ( Page 307 Combining trigger conditions)

Device specification Data are collected when the specified monitoring target data (bit data) turns on during the END processing. Even though the value of the monitoring target data changes during a single scan, if the value during the END processing is same as that during the last END processing, it is not recognized as a trigger. Completion bits (including error completion bits) used in dedicated instructions cannot be used as a trigger.

For monitoring data, the following devices can be specified.

*1 A local device, index modified device, and indirectly specified device cannot be specified. *2 Word devices allow bit specification only. *3 In the engineering tool, specify TS as T (contact), STS as ST (contact), CS as C (contact), LTS as LT (contact), LSTS as LST (contact),

and LCS as LC (contact).

Type Device*1

Bit device X, Y, M, L, B, F, SB, V, T (contact), T (coil), LT (contact), LT (coil), ST (contact), ST (coil), LST (contact), LST (coil), C (contact), C (coil), LC (contact), LC (coil), FX, FY, SM, BLn\S*3

Word device T (current value), ST (current value), C (current value), D, W, SW, FD, SD, R*2, ZR*2, Z, RD

Double-word device LT (current value), LST (current value), LC (current value), LZ

Trigger condition Description Device specification Data are collected when the specified monitoring target data (bit data) turns on during the END processing.

Error code specification Data are collected when an error occurs in the specified CPU module.

Type Device*1

Bit device X, Y, M, L, F, SM, V, B, SB, T (contact)*3, ST (contact)*3, C (contact)*3, LT (contact)*3, LST (contact)*3, LC (contact)*3, FX, FY

Word device*2 D, SD, W, SW, R, ZR, FD, RD

END END

Trigger occurrence

Data condition

1 scan

Program

Data sampling starts.

18 DEBUG FUNCTION 18.1 Memory Dump Function 305

30

Error code specification With a specified error code of the CPU module as a trigger, data is to be collected. The occurrence timing of trigger varies depending on the error type: continuation error or stop error.

At the occurrence of a continuation error The occurrence timing of trigger is at the time of END processing of the scan where an error has occurred.

In the following situations, the occurrence of a continuation error that is specified as a trigger condition is not recognized as a trigger, with no data collection: After the occurrence of a continuation error that is specified as a trigger condition, the same error, or a continuation error,

has occurred again. In the situation that a continuation error of 15 or more has occurred, a continuation error that is specified as a trigger

condition has occurred. Being recognized as a trigger requires the error to be cleared.

At the occurrence of a stop error The occurrence timing of trigger is at the time of occurrence of an error.

To specify an annunciator number as a trigger condition, employ device specification to specify any desired annunciator number.

RUN

END END

RUN/STOP state

A continuation error occurs. Trigger occurrence

Error

1 scan

Program

Data sampling starts.

RUN STOPRUN/STOP state

A stop error occurs. Trigger occurrence

Error

Program

Data sampling starts.

6 18 DEBUG FUNCTION 18.1 Memory Dump Function

18

Combining trigger conditions A trigger can be generated with trigger conditions combined. This combination is based on an OR condition. The establishment of a condition, either device specification or error code specification, results in data collection.

Procedure for memory dump This section describes the procedure for memory dump. Note that each operation of the memory dump function is performed with the engineering tool.

[Debug] [Memory Dump] For how to view and operate the window, refer to the following. GX Works3 Operating Manual

1. Configure the memory dump settings by the menu operation in the engineering tool.

2. Writing the memory dump setting file results in a wait state for the trigger. Whether the CPU module is in a RUN state, STOP state (a stop error also included*1), or PAUSE state, a wait state for the trigger results.

*1 Limited to where the trigger condition is device specification.

If the memory dump setting file is stored, putting the CPU module back into operation (powering off and on, or resetting) results in a wait state for the trigger.

The engineering tool allows the memory dump status to be checked. The event history also allows checking whether or not in a wait state for the trigger.

3. Establishment of the trigger condition initiates data collection, saving the memory dump file to the SD memory card.

4. The contents of the memory dump file (collected device data) can be checked with the engineering tool.

END END END END END END

On error

Data condition

Collecting after trigger (collecting/saving)

Program

Condition established

Trigger generated

Condition established

Condition established

Trigger generated

The established condition is not recognized as a trigger because collecting after trigger (collecting/saving) is in progress.

18 DEBUG FUNCTION 18.1 Memory Dump Function 307

30

Flow of data collection Collected data is stored in the internal buffer, where the data is partitioned at END processing and saved in the SD memory card.

The size of data to be collected per END processing is determined according to the capacity setting of the internal buffer ( Page 265 Internal buffer capacity setting) and the individual area size of devices from which data is to be collected. Data is collected and partitioned into the groups per END processing, as in the table below. If the capacity of an individual area exceeds the internal buffer capacity, collected data in the individual area is further partitioned. The first 1K byte in the internal buffer is used as the system area, and thus the collection size per END processing is determined to a value of the internal buffer capacity minus 1K byte.

Effect on the scan time The greater the number of collected points, the longer the scan time. For the increase in scan time due to the collected points, refer to the processing time. ( Page 659 Memory dump function)

Partition area Remarks Device area If the total value of devices exceeds the internal buffer capacity, the amount by which the internal buffer capacity is

exceeded is collected at the next END processing in order from the top device, not collected at the current END processing.

Local device (at each program) If the total value of local devices of programs concerned exceeds the internal buffer capacity, the amount by which the internal buffer capacity is exceeded is collected at the next END processing in order from the top device, not collected at the current END processing.

File register (at each file)

Refresh memory Refresh memory area

Condition establishment timing

Condition establishment

Program

Internal buffer

SD memory card Finish Writing of sampling data

Program END processing

Trigger occurrence

8 18 DEBUG FUNCTION 18.1 Memory Dump Function

18

Memory dump file This file stores data that is collected through memory dump (collection result by memory dump). Data collected by one execution is saved in one file. The memory dump file is saved in a binary format and stored under the "MEMDUMP" folder.

Save file name The file name can be arbitrarily set within a range of 64 characters (extension and period included) together with an auto- assigned number (00 to 99). Specify the save file name in the memory dump settings. ( GX Works3 Operating Manual)

Ex.

MEMDUMP_00*1

*1 Between a specified file name (MEMDUMP) and an auto-assigned number (00), the single-byte underscore (_) is added. When the memory dump function is registered, the debug folder (DEBUG (fixed)) and the memory dump folder (MEMDUMP (fixed)) are created in the SD memory card. The memory dump file (result file) is stored in the memory dump folder. One folder can contain a maximum of 100 files. If any file does not exist in creating a save file, the file with the number 00 is created. If any file already exists in creating a save file, the behavior is as follows:

*2 If the corresponding file number is 99, a file with file number 00 is created.

Number of files Behavior For less than 100 Creates a file*2 assigning the number obtained by adding 1 to the number of the file where the creation date and time is the latest.

For 100 (maximum) Deletes the file where the creation date and time is the oldest and creates a new file using the deleted number as it is.

18 DEBUG FUNCTION 18.1 Memory Dump Function 309

31

States of the memory dump function The state of the memory dump function is reflected in the memory dump status. The engineering tool allows the memory dump status to be checked. ( GX Works3 Operating Manual)

Memory dump status The following table lists the memory dump status.

LED status Whether the memory dump function is active or not can be checked by the LED of the CPU module.

To let the FUNCTION LED indicate the status while the memory dump function is used, setting "LED Display Setting" in "RAS Setting" of the CPU parameter is required. ( Page 172 LED display setting) For the FUNCTION LED indication, the following cases have priority over the function above. When the external input/output forced on/off function is executed (in registration) ( Page 209

FUNCTION LED) When program restoration information is not written ( Page 686 Checking the program restoration

information write status) After the external input/output forced on/off function has been executed (after the registration is canceled) and the program restoration information has been written, the LED display follows the status of the memory dump function.

Memory dump status Description Trigger-wait not collected A state that data is not yet collected and establishment of the trigger condition is being waited

Collecting after trigger A state that collection of the data after trigger is in progress (includes a state that collected data is being saved in the target memory)

Collection completed A state that collection of a specified data is completed

Error A state that a memory dump error occurs and memory dump fails

State of the memory dump function

LED status

FUNCTION LED CARD READY LED CARD ACCESS LED Trigger-wait not collected On On Off

Collecting after trigger Flashes slowly (every one second) On Turns on when the SD memory card is accessed

Collection completed Flashes at normal rate (every 200ms) On Off

0 18 DEBUG FUNCTION 18.1 Memory Dump Function

18

Sizes of files used for the memory dump function This section shows the sizes of files used for the memory dump function.

Capacity of the memory dump setting file The capacity of the memory dump setting file varies depending on the length of the save file name. The following formula is used for the calculation: Capacity of memory dump setting file = (((Number of characters of save file name*1 2 bytes + 1201 bytes (fixed)) + 3) 4)*2 4 *1 Except for the period and extension. *2 The remainder is discarded.

Capacity of the memory dump file The capacity of the memory dump file is given by the total of the following items: Capacity of memory dump file = Volume of header + Volume of data of program file name + Volume of device data + Volume of local device data + Volume of data of file register file name + Volume of file register data

Volume of header The volume of header is given by: Volume of header = 1088 bytes (fixed)

Volume of data of program file name The volume of data of program file name is given by the total of the following items. Note that this data is always created in the memory dump file regardless of the settings of CPU parameters. Volume of data of program file name = 16 bytes (fixed) + (Number of programs (2 bytes (length of program file name) + 130 bytes (program file name))

Volume of device data The volume of device data is given by the total of the following items. Note that this data is always created in the memory dump file regardless of the settings of CPU parameters. Volume of device data = 682 bytes (fixed) + Volume of collected device data The volume of collected device data is given by the following: Volume of collected device data = (Total number of points of bit devices 8) + (Total number of points of word devices 2) + (Total number of points of word devices 4)

Volume of local device data The volume of local device data is given by the total of the following items. Note that this data is not created in the memory dump file unless local devices are set in the CPU parameters. Volume of local device data = 16 bytes (fixed) + (Number of programs 4 bytes) + (Number of programs Volume of local device contents)

Volume of data of file register file name The volume of data of file register file name is given by the total of the following items. Note that this data is not created in the memory dump file unless a file register file exists in the device/label memory. Volume of data of file register file name = 16 bytes (fixed) + (Number of file register files (2 bytes (length of file register file name) + 130 bytes (file register file name)

Volume of file register data The volume of file register data is given by the total of the following items. Note that this data is not created in the memory dump file unless a file register file exists in the device/label memory. Volume of file register data = Number of file register files (148 bytes (fixed) + (Number of file registers 2))

Item Calculation method Volume of local device contents 418 bytes (fixed) + Volume of collected local device data

Volume of collected local device data (Total number of points of bit devices 8) + (Total number of points of word devices 2) + (Total number of points of word devices 4)

18 DEBUG FUNCTION 18.1 Memory Dump Function 311

31

Special relay and special register used in the memory dump function For details, refer to the following. Special relay: Special relay relating to the memory dump function ( Page 598 Memory dump function) Special register: Special register relating to the memory dump function ( Page 633 Memory dump function)

Precautions for the memory dump function This section describes precautions to take when using the memory dump function.

Mutual exclusion of the memory dump function The mutual exclusion of the memory dump function is as follows. The following table lists the cases when another function is executed during the execution of the memory dump function*1.

*1 The state where the memory dump function is in execution includes the memory dump status of "Collecting after trigger" or the save status of "Saving in progress".

*2 The memory dump function is not included. The following table lists the cases when the memory dump function is executed during the execution of another function.

*3 The memory dump function is not included.

Function that has been already executed

Function to be executed later

Behavior

Memory dump function CPU module data backup function

The CPU module data backup function cannot be executed while memory dump is being registered/cleared.

CPU module data restoration function

The CPU module data restoration function cannot be executed while a memory dump file or memory dump setting file is being read or memory dump is being registered/cleared.

iQ Sensor Solution data backup/restoration function

The iQ Sensor Solution data backup/restoration function cannot be executed while memory dump is being registered/cleared.

Function specified in the internal buffer capacity setting*2

If the internal buffer capacity setting is changed to execute the subsequent function, attempting to start the subsequent function results in an error. The memory dump continues to function normally.

Function not specified in the internal buffer capacity setting

If the condition "Total capacity that is set in the internal buffer capacity setting + Internal buffer capacity that is set in other than the internal buffer capacity setting > 3072K bytes" is satisfied, attempting to start the subsequent function results in an error. The memory dump continues to function normally.

If the internal buffer capacity setting is changed to execute the subsequent function, attempting to start the subsequent function results in an error. The memory dump continues to function normally.

Function that has been already executed

Function to be executed later

Behavior

CPU module data backup function

Memory dump function While the CPU module data backup function is being executed, memory dump cannot be registered/cleared.

CPU module data restoration function

While the CPU module data restoration function is being executed, a memory dump file or memory dump setting file cannot be read or memory dump cannot be registered/cleared.

iQ Sensor Solution data backup/restoration function

While the iQ Sensor Solution data backup/restoration function is being executed, memory dump cannot be registered/cleared.

Function specified in the internal buffer capacity setting*3

If the internal buffer capacity setting is changed to execute memory dump, attempting to start memory dump results in an error. The function already in execution continues to function normally.

Function not specified in the internal buffer capacity setting

If the internal buffer capacity setting is changed to execute memory dump, attempting to start memory dump results in an error. The function already in execution continues to function normally.

2 18 DEBUG FUNCTION 18.1 Memory Dump Function

18

The following table shows the cases where the file operation related to the memory dump function is executed while the memory dump function is in execution.*4

*4 The state where the memory dump function is in execution includes the memory dump status of "Collecting after trigger" or the save status of "Saving in progress".

Behavior at parameter change when functions consuming the internal buffer are active If the internal buffer capacity setting is changed during the execution of functions that consume the internal buffer, attempting to start memory dump results in an error, where the memory dump fails to start.

Operation on each individual file Write, read, and delete are possible on each file. In addition, folder/file all delete and folder delete are possible on the memory or folder in which files are stored. The following table shows whether each operation is possible or not depending on the execution status of memory dump. : Operation possible, : Operation not possible

*1 The state where the memory dump function is in execution includes the memory dump status of "Collecting after trigger".

Where to carry out memory dump Concurrent execution from multiple sources is not allowed. In the CPU module, execution at a time from only one source is possible.

Trigger condition during the registration of memory dump If a trigger condition is established during the registration of memory dump, the memory dump settings can be registered. A second establishment of the trigger condition is recognized as a trigger condition there.

When file register is specified as specification device in the condition specification After registering memory dump, do not change the file name of the file registers and the block number of the file registers. Doing so may result in a failure to successfully collect the memory dump results.

Target file File operation Behavior Memory dump setting file Write Settings that are subsequently written during the execution of the memory dump function are

reflected after the completion of save, not reflected immediately.

Delete If the memory dump setting file is subsequently deleted during the execution of the memory dump function, the memory dump settings are cleared after the completion of save.

Initialize Initialization fails on the memory dump setting file during the execution of the memory dump function.

Folder delete Folder delete fails on the folder in which the memory dump setting file is stored.

Memory dump file Write, read, delete, initialize, and folder delete

Write, read, delete, initialize, and folder delete fails on the memory dump file during the execution of the memory dump function.

File type Operation to be performed

Read Write/delete Folder/file all deletion Folder delete

Not during execution*1

During execution*1

Not during execution*1

During execution*1

Not during execution*1

During execution*1

Not during execution*1

During execution*1

Memory dump setting file

Memory dump file

Function that consumes the internal buffer other than memory dump

Memory dump

Function in execution

Function in execution An error occurs. Memory dump is not allowed to start.

Internal buffer capacity setting changed (by changing the parameters of internal buffer capacity setting)

Memory dump setting file deleted

Memory dump setting file written

18 DEBUG FUNCTION 18.1 Memory Dump Function 313

31

Creating files and folders Under the "MEMDUMP" folder containing memory dump files, do not create any files or folders using a personal computer or other device. Doing so may result in deletion of files and folders.

Access to the SD memory card The SD memory card is so frequently accessed that a delay occurs in completing the access to the SD memory card (read/ write).

4 18 DEBUG FUNCTION 18.1 Memory Dump Function

19

19 DATABASE FUNCTION This function manages the data such as product information or production information as a database in an SD memory card of the CPU module.

This function cannot be used in the R00CPU, R01CPU, and R02CPU.

Database access instruction The database access instructions allow the databases of product information and production information to be created, input, updated, edited, searched, transacted, and rolled back.

CPU module database access (from external device) function The CPU module database access function enables operations such as table creation and record operation/search of the database built in an SD memory card inserted into the CPU module.

DBSELECT

DBINSERT

1234 1235

1 2

2017/4/28 15:40:30

2017/4/28 15:41:15

81 79

99 100

58 60

80 40

1 2

100 90

60 40

Read the data of product ID = 2.

Database (Product information table)

Database (Production information table)

Database is built in an SD memory card.

Product information

Production information

Write the processing data to the production result.

Product number

Product ID Result(X) Result(Y) Result(Z)Processing date

Product ID Product name Size(X) Size(Y) Size(Z)

Product name 1

Product name 2

Ethernet

Product information

Production information

19 DATABASE FUNCTION 315

31

19.1 Specifications

Database specifications The following table lists specifications of databases which the user can create.

*1 For the programmable controller CPU with firmware version earlier than "28", up to 16 fields can be created per table. *2 For the programmable controller CPU with firmware version earlier than "28", up to 100000 records can be created per table. *3 For the programmable controller CPU with firmware version earlier than "28", up to 16 tables can be created per database. *4 For rough standards of the access time depending on the database size, refer to the following.

Page 671 Database function processing time

Data type The following table lists the data types that can be used in the table created by using the database access instructions and the corresponding data types for the CPU module database access function.

The following table lists the data types that can be used in the table created by the CPU module database access function and the corresponding data types for the database access instructions.

Item Description The maximum number of fields 128 fields per table*1

The maximum number of records No limitation (they can be created up to the capacity of the SD memory card)*2*4

The maximum number of tables 32 tables per database*3

The maximum number of databases No limitation (they can be created up to the capacity of the SD memory card)

The maximum number of concurrently connectable databases (number of connections)

4

The maximum number of characters of a field name 32 single-byte alphabetical characters

The maximum number of characters of a table name 32 single-byte alphabetical characters

Corresponding data type Page 316 Data type

Data type that can be used in the table created by using the database access instruction

Range Corresponding data type for the CPU module database access function

BOOL: Bit 0, 1 BOOLEAN: Bit

WORD: Unsigned 16-bit numerical value 0 to 65535 INT: Unsigned 16-bit numerical value

DWORD: Unsigned 32-bit numerical value 0 to 4294967295 BIGINT: Unsigned 32-bit numerical value

INT: Signed 16-bit numerical value -32768 to 32767 INT: Signed 16-bit numerical value

DINT: Signed 32-bit numerical value -2147483648 to 2147483647 BIGINT: Signed 32-bit numerical value

REAL: Single-precision real number E1.175495-38 to E3.402823+38 REAL: Single-precision real number

LREAL: Double-precision real number E2.22507385850721-308 to E1.79769313486231+308 DOUBLE PRECISION: Double-precision real number

STRING: String (Shift-JIS code) Number of supported characters: 1 to 124 NLSCHAR: String (Unicode)

WSTRING: String (Unicode) Number of supported characters: 1 to 124 NLSCHAR: String (Unicode)

Data type that can be used in the table created by the CPU module database access function

Range Corresponding data type for the database access instruction

BOOLEAN: Bit 0, 1 BOOL: Bit

INT: Signed 16-bit numerical value -32768 to 32767 INT: Signed 16-bit numerical value

BIGINT: Signed 32-bit numerical value -2147483648 to 2147483647 DINT: Signed 32-bit numerical value

REAL: Single-precision real number E1.175495-38 to E3.402823+38 REAL: Single-precision real number

DOUBLE PRECISION: Double-precision real number

E2.22507385850721-308 to E1.79769313486231+308 LREAL: Double-precision real number

NLSCHAR: String (Unicode) Number of supported characters: 1 to 124 WSTRING: String (Unicode)

6 19 DATABASE FUNCTION 19.1 Specifications

19

To input the data to the field of STRING using the CPU module database access function, use the data type of NLSCHAR. (Although the data is managed as Unicode in the database of the CPU module, it is converted to Shift-JIS code on the device of the CPU module.)

To input the data in the data type of WORD or DWORD to the field using the CPU module database access function, the data must be within the range of WORD: 0 to 65535 or DWORD: 0 to 4294967295.

Available operations The following table lists the operations that can be performed with the database functions. : Can be performed, : Cannot be performed

For details on the database access instructions, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks) For the available SQL commands for the CPU module database access function, refer to the following. Page 689 List of Available SQL Commands for CPU Module Database Access Function

The user cannot execute multiple database access instructions simultaneously. If they are executed simultaneously, instructions other than the first one will be completed with an error.

Even though the operation can be performed for the database of the CPU module by the SQL command, an error occurs on the application side when it cannot be performed in the application. In this case, check the details of the error and perform the operation within the range of the specifications of the application again.

Operation Description Database access instruction CPU module database access function

Availability and instruction symbol

Availability and application

Database Connection Connects to the specified database. DBOPEN(P) Microsoft Access, Excel, user-created applicationDisconnection Disconnects from the specified database. DBCLOSE(P)

Import Imports the specified data from the specified Unicode text file to create a database.

DBIMPORT(P)

Export Exports the specified data in the specified database into a Unicode text file.

DBEXPORT(P)

Table Add Adds a table to the database. Microsoft Access

Record Access Accesses the specified table in the database. Microsoft Access

Add Adds a record to the specified table of the database.

DBINSERT(P) Microsoft Access

Update Updates the value of the specified record on the specified table in the database.

DBUPDATE(P) Microsoft Access

Acquire (Search) Acquires the value of the specified record on the specified table in the database.

DBSELECT(P) Excel

Delete Deletes the specified record on the specified table in the database.

DBDELETE(P) Microsoft Access

Transaction Start Starts a transaction for the specified database.

DBTRANS(P) Microsoft Access (The transaction range depends on the application.)

Commit Commits a transaction for the specified database.

DBCOMMIT(P) Microsoft Access (The transaction range depends on the application.)

Rollback Performs rollback on the specified database. DBROLBAK(P) Microsoft Access (The transaction range depends on the application.)

Database operation by a desired SQL User-created application

19 DATABASE FUNCTION 19.1 Specifications 317

31

19.2 Database Access Instruction Usage procedure This section describes the procedure to use the database function.

Creating databases To construct a database on an SD memory card, create a Unicode text file which defines the configuration of the database and its tables, store the file on the SD memory card, and execute the DBIMPORT(P) instruction, specifying the created Unicode text file.

1. Create a Unicode text file which defines the configuration of a database and its tables. ( Page 319 Creating Unicode text files)

2. Write the created Unicode text file to the SD memory card. For details on how to write Unicode text files (write of user data), refer to the following.

GX Works3 Operating Manual

3. By executing the DBIMPORT(P) instruction with the created Unicode text file specified, the database folder is created on the same layer as the Unicode text file and the database is constructed. ( Page 322 Folder configuration of databases)

The DBEXPORT(P) instruction enables the user to check the contents of a database by exporting it to a Unicode text file. Also, when the user wants to add more than one record or field to a database, the user can change the configuration of the database by exporting it to a Unicode text file, editing the file, and executing the DBIMPORT(P) instruction to get the database back to the system.

Operating databases First, the user must execute the DBOPEN(P) instruction to connect to the database which the user wants to work on. Also, after finishing database operation, the user must execute the DBCLOSE(P) instruction to disconnect from the database.

1. Execute the DBOPEN(P) instruction to connect to the database which the user wants to work on (connect to the database by specifying the folder which was created in Step 3 of the database creation procedure). When the execution is finished, a value including the "database ID number" is returned.

Since the database ID number must be specified for performing database operation, use the database ID number to be returned when the DBOPEN(P) instruction is executed.

2. Once the connection to the database is established, perform operation (addition, update, search, or deletion) of the database. To perform database operation, the user must specify the "database ID number" of the target database in each instruction.

3. When database operation is finished, execute the DBCLOSE(P) instruction to disconnect from the database.

The user can use a transaction when the user wants to perform multiple operations for a database as a set and update the database at once. ( Page 322 Transactions for databases)

8 19 DATABASE FUNCTION 19.2 Database Access Instruction

19

Creating Unicode text files When the DBIMPORT(P) instruction is executed, a database is created on an SD memory card, according to setting details in the tab-delimited format of Unicode text file. The user must create Unicode text files on an SD memory card.

Setting details of Unicode text file The following table lists items which must be specified in a Unicode text file to create a database.

*1 The termination character, NULL, is not counted in the number of characters. *2 The length of characters is represented by single-byte characters. For double-byte character strings, one double-byte character should

be counted as two single-byte characters. *3 For the programmable controller CPU with firmware version earlier than "28", the maximum number is 16.

Item Description Database name Specify a database name, using single-byte alpha-numeric characters.

Within 32 characters Not case-sensitive The following characters cannot be used: " # % * + , / : ; < = > ? [ \ ] | ' { } & ~ $ @ ^

Table definition start tag Specify the tag,

, using a single-byte lower-case characters. When defining more than one table, enclose each table with
and
.

Table name Specify a table name, using single-byte alpha-numeric characters. Within 32 characters Not case-sensitive The following characters cannot be used: " # % * + , / : ; < = > ? [ \ ] | ' { } & ~ $ @ ^ The maximum number of tables is 32.*3

Field name Specify the name of each field of each record, using single-byte alpha-numeric characters, and in the tab-delimited format. The maximum number of characters which can be used for each field name is 32. Case-sensitive The following characters cannot be used: " and ' The maximum number of fields is 128.*3

Data type Specify the data type of each field in the tab-delimited format. The data types which can be specified are as follows. They must be specified using upper-case characters. BOOL WORD DWORD INT DINT REAL LREAL STRING: Specify the number of characters after a colon (:) (For example, when the number of characters is 16, the user

can specify like that: "STRING: 16"). The range of the number of characters is 1 to 124.*1*2

WSTRING: Specify the number of characters after the colon (:) The range of the number of characters is 1 to 124.*1

Key constraint Specify the key constraint on each field, using single-byte alphabetical characters. Between key constraints, a tab must be inserted as a delimiter. One of the following can be specified: 0: None 1: Primary key (used to uniquely identify each record) (When a primary key is specified, its key name also must be

specified after a colon (:) (e.g. "1: pk1"). Key names must be up to 16 single-byte alphabetical characters and are case sensitive.)

2: NOT NULL constraint (When this setting is selected, setting values cannot be left unspecified by skipping specification of primary keys or foreign keys. This value is used to set a restriction.)

3: Foreign key (used to refer to the field of another table) (When a foreign key is specified, a table name, which is to be associated with the key name, also must be specified after a colon (:), like that: "3: Key Name: Table Name" (e.g. "3: fk1: tb2"). Key names must be up to 16 single-byte alphabetical characters and are case sensitive.)

Index Specify 0 (single-byte numeric character) when any indexes are not specified. When an index is specified, the name of the index and a field name must be specified using a colon (:) between them, like that: "Index Name: Field Name" (e.g. "id1: field1"). Index names must be up to 16 single-byte alphabetical characters and are case sensitive. The maximum number of indexes is 128.*3

For fields with a primary or foreign key constraint, indexes are automatically set, and it is not necessary to specify indexes by this setting (if specified, the DBIMPORT(P) instruction is completed with an error).

Setting value Specify the setting value of each field in the tab-delimited format. Characters or numbers which will be set to each field must match with the specified data type ( Page 319 Creating

Unicode text files, Page 320 Format of setting values in Unicode text) Individual records are set by row.

Table definition end tag Specify the tag, , using a single-byte lower-case characters.

19 DATABASE FUNCTION 19.2 Database Access Instruction 319

32

Specifications of the character code for Unicode text files are as follows: Character encoding schema: UTF-16 (Little-Endian) BOM: Yes

Format of setting values in Unicode text

*1 "E" can be specified in lower case. *2 The exponent part must always have a sign.

Configuration of Unicode text files

[Tab] in the figure represents a tab character and it is entered using the key on the keyboard in practice. Line breaks, comments, tabs, and spaces are processed as follows.

Item Description WORD, DWORD, INT, DINT

The value must be specified in the decimal format (e.g. 0, 1, 111, -111).

BOOL The value must be 0 or 1.

REAL, LREAL The value must be specified in the following exponential format (e.g. 1.0e-01, 1.0E+01): Mantissa + E*1 + Exponent part*2

Item Description Line break The line break code is CR+LF.

Lines consisting of only line breaks are ignored.

Comment A row beginning with "//" is regarded as a comment. The maximum number of characters in a comment row is 2048 (including two characters for the line break code).

Tab Tabs cannot be used for database names, table names, field names, key constrains, and setting values. Tabs are recognized as delimiters.

Space Spaces between tabs and printable characters are not recognized as a part of settings. Spaces between printable characters are recognized as spaces.

Database name

Set value k [Tab] Set value 2 [Tab] ... [Tab] Set value n

Table name 1 Field name 1 [Tab] Field name 2 [Tab] ... [Tab] Field name n Data type 1 [Tab] Data type 2 [Tab] ... [Tab] Data type n Key restriction 1 [Tab] Key restriction 2 [Tab] ... [Tab] Key restriction n Index 1 [Tab] Index 2 [Tab] ... [Tab] Index n Set value 1 [Tab] Set value 2 [Tab] ... [Tab] Set value n
Table name 2 (The subsequent setting is the same as the setting of Table name 1.)

0 19 DATABASE FUNCTION 19.2 Database Access Instruction

19

Ex.

Example of the Unicode text file format (Database name: database1, Table name: product-info1)

Unicode text files can be created using a text editor or spreadsheet software program. The method for saving Unicode text files in Notepad or Excel is as follows: In the text editor (Notepad, an accessory of Windows 7 or later), select [Save As] from the [File] menu, and

select "Unicode" as the character code to save the file. In the spreadsheet software program (Excel 2010), select [Save As] from the [File] menu, and select

"Unicode" as the file type to save the file. When a Unicode text file is created using a spreadsheet software program, tabs are automatically inserted by saving the file. Therefore, it is not necessary to insert tabs into the file in the spreadsheet software program.

proid1 proinfo1 proinfo2 proinfon

1

1001

1010

abcd

abcd

abcd

efgh

efgh

efgh

pqrs

pqrs

pqrs tuv

Key restriction: Main key Data type: INT Data type: STRING, Number of characters: 124

Key restriction: None

//Database name database1

//nth record 1010 [Tab] abcd [Tab] efgh [Tab] ... [Tab] pqrs

//Table name product-info1 //Field name proid1 [Tab] proinfo1 [Tab] ... [Tab] proinfon //Data type INT [Tab] STRING: 124 [Tab] ... [Tab] STRING: 124 //Key restriction 1: pk1 [Tab] 0 [Tab] ... [Tab] 0 //Index 0 //Record //First record 1 [Tab] abcd [Tab] efgh [Tab] ... [Tab] pqrs //Second record 1001 [Tab] abcd [Tab] efgh [Tab] ... [Tab] pqrs tuv

19 DATABASE FUNCTION 19.2 Database Access Instruction 321

32

Transactions for databases Use a transaction (the DBTRANS(P) instruction and the DBCOMMIT(P) instruction) to perform multiple operations for a database as a set and update the database at once. The DBTRANS(P) instruction starts a transaction, and the DBCOMMIT(P) instruction groups the results of the following instructions together to update the target database at once. The target of a transaction must be a single database. If a transaction is executed for more than one database, transaction

instructions for the second and later databases are completed with errors. When the CPU module is powered off or is reset in the period from the start of a transaction (execution of the DBTRANS(P)

instruction) to the commit of the transaction (execution of the DBCOMMIT(P) instruction), the database is automatically rolled back to the status before the start of the transaction. However, if a database access instruction is completed with an error, the database is not roll backed to the previous status.

To cancel the running transaction processing and reset the database to the status before the start of the transaction, perform a rollback (the DBROLBAK(P) instruction). A rollback is an operation which resets the target database to the previous status by executing the DBROLBAK(P) instruction in the period from the start of the transaction to the commit of the transaction. When the DBCLOSE(P) instruction is executed without the DBCOMMIT(P) instruction or the DBROLBAK(P) instruction, the transaction is committed during execution of the DBCLOSE(P) instruction.

1. Execute the DBOPEN(P) instruction to connect to a database.

2. Execute the DBTRANS(P) instruction to start a transaction.

3. Operate the database.

4. To commit the transaction, execute the DBCOMMIT(P) instruction. When committing the transaction is not necessary, execute the DBROLBAK(P) instruction to restore to the state before the start of the transaction (rollback).

5. Execute the DBCLOSE(P) instruction to disconnect from the database.

Folder configuration of databases The database folder for storing database files is generated at the same level in the folder hierarchy as the Unicode text file which is specified in the DBIMPORT(P) instruction. Also, the database folder is given the same names as the database. The length of a database folder path name must be up to 128 characters, including the drive name and a colon (:) prefixed to the path name.

Operation of files/folders in the database folder Files and folders in the database folder are used for database access instructions. They should not be changed, deleted, and newly created. Otherwise, database access instructions may be completed with errors. In that case, delete the relevant database folder.

DATABASE ABC.txt

DB_ABC

Root directory

Unicode text file defining database Database name: DB_ABC

If the Unicode text file "ABC.txt" is specified using the DBIMPORT instruction, the DB_ABC folder is created at the same level, and the database file of the database "DB_ABC" is created in the DB_ABC folder.

Database file

Database file

Database file

2 19 DATABASE FUNCTION 19.2 Database Access Instruction

19

Timing of database update Once execution of a database access instruction is completed, the target database is updated. However, during transaction, the database is not updated each time execution of an instruction is completed. Instead, all changes during the transaction are applied to the database at once when the DBCOMMIT(P) instruction is executed.

Precautions This section describes precautions on using the database function.

Free space of SD memory card required for execution of database access instruction To execute a database access instruction, the SD memory card must have at least 10MB of free space. When a database access instruction is performed and if the SD memory card does not have enough free space, the instruction is completed with an error.

When the SD memory card is write-protected Before using database access instructions, check that the write protection of the SD memory card used is disabled. If a database access instruction is performed while the SD memory card is write protected, the instruction is completed with an error.

When the CPU module database access function is used The database access instructions can be executed while SM1498 (CPU module database start-up flag) is on.

When the database is being operated by another function Before creating a database by using the DBIMPORT(P) instruction, check that the same database is not being operated by another function. If the DBIMPORT(P) instruction is executed specifying a name of a database in the SD memory card while the same database is operated by another function, the DBIMPORT(P) instruction may be completed with an error and the database operation in another function may fail. After the DBIMPORT(P) instruction is completed with an error, if the database operated by another function cannot be operated, the database may be broken. Power off and on or reset the CPU module, and build the database again by using the DBIMPORT(P) instruction.

Combination of the firmware version and database For the combination of the firmware version of the programmable controller CPU that creates a database and that of the programmable controller CPU that can operate the database, refer to the following. Page 341 Combination of the firmware version and database

Removal of the SD memory card Do not remove the SD memory card while connecting to a database by using the DBOPEN(P) instruction or executing a database access instruction. Otherwise, the database access instruction is completed with an error.

19 DATABASE FUNCTION 19.2 Database Access Instruction 323

32

19.3 CPU Module Database Access (from External Device) Function

The CPU module database access function operates a database, that is built in an SD memory card inserted into the CPU module, from an application on a personal computer through the Ethernet port of the CPU module. To use the CPU module database access function, install CPU Module Database Access Driver into a personal computer. ( CPU Module Database Access Driver Installation Instructions)

In the CPU module database access function, the CPU module operates as the ODBC server and the personal computer operates as the ODBC client. ODBC (Open Database Connectivity) is the standard API that allows applications to connect with the database management system (DBMS) to acquire and write the data.

Before using the CPU module database access function, check the version of the CPU module and the engineering tool used. ( Page 700 Added and Enhanced Functions)

Usage procedure This section describes the procedure for operating the database by using the CPU module database access function.

Construction of usage environment Engineering tool 1. Module parameter setting of the CPU module Set whether or not to use the CPU module database access function, login name, and password in the module parameter of the CPU module. ( Page 326 Built-in database access setting)

2. Update of the built-in database access setting in the CPU module Write the module parameter to the CPU module, and then power off and on or reset the CPU module.

CPU Module Database Access Driver 1. Obtaining CPU Module Database Access Driver For CPU Module Database Access Driver, please consult your local Mitsubishi representative.

2. Installing CPU Module Database Access Driver Install CPU Module Database Access Driver into the personal computer. ( CPU Module Database Access Driver Installation Instructions)

The installer of CPU Module Database Access Driver has the 32-bit or the 64-bit version. Choose the installer depending on the supported bit of the application (Microsoft Access, Excel, user-created application) used for the CPU module database access function. For example, when using Microsoft Access with 32-bit version, use the 32-bit installer of CPU Module Database Access Driver even though the 64-bit OS is used.

Procedure Description Construction of usage environment Construct the environment to use the CPU module database access function.

Database access setting Configure this setting to create or change a database of the CPU module.

Database operation Operate a database of the CPU module from a personal computer.

4 19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function

19

Database access setting 1. Creating a database Create a database in an SD memory card of the CPU module. ( Page 327 Creating a database)

2. Adding a database to the ODBC data source Add the created database of the CPU module to the ODBC data source of the personal computer. ( Page 328 Adding a database to the ODBC data source)

Database operation 1. Checking the start-up of the ODBC server Check that SM1498 (CPU module database start-up flag) is on. When SM1498 is on, the ODBC server of the CPU module is active. The ODBC server starts and SM1498 turns on when: An SD memory card storing the database folder is inserted to the CPU module, and the CPU module is powered off and on

or is reset. An SD memory card storing the database folder is inserted to the CPU module powered-on when SD1498 (Start-up status

of CPU module database) is 0H. Whether or not the ODBC server has been started up can be checked in SD1498 (Start-up status of CPU module database).

The active ODBC server stops when: The SD memory card is disabled (SD memory card forced disable) or the SD memory card is removed. The CPU module is powered off. The data memory is initialized. Free space of the SD memory card is less than 10MB.

2. Connecting to a database Start an application (Microsoft Access, Excel, or the user-created application) on a personal computer and connect it to a database specified with the application. ( Page 330 Application example)

3. Operating a database Operate an application on a personal computer to operate a database. ( Page 330 Application example)

The SD memory card is accessed when the ODBC server is started up. This may lengthen the processing time of other functions that use the SD memory card.

19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function 325

32

Built-in database access setting To use the CPU module database access function, set "To Use or Not to Use the Built-in Database Access" of the module parameter to "Use" with the engineering tool.

[Navigation window] [Parameter] CPU module [Module Parameter] [Application Settings] [Built-in Database Access Setting]

Window

Displayed items

*1 Single-byte alphabetical characters and special characters (excluding " # % * + , / : ; < = > ? [ \ ] | ' { } & ~ $ @ ^) can be input. *2 A space cannot be used as the first character.

Item Description Setting range

Default

To Use or Not to Use the Built-in Database Access Set whether to use the CPU module database access function.

Use Not Use

Not Use

Login Name A user name to be used for the authentication at the access to a database

1 to 31 characters*1*2

RCPU

Advanced Settings

Password Setting Current Password A password to be used for the authentication at the access to a database

0 to 31 characters*1

RCPU

New Password A new password to be set 0 to 31 characters*1

Confirm New Password

A password for confirmation. The password can be changed only when this password matches a new password.

0 to 31 characters*1

Built-in Database Access Timer Setting

Message Monitoring Timer

A monitoring timer for until the first message is sent from the personal computer after the connection establishment

1 to 16383s 5

Connection Monitoring Timer

A monitoring timer for until the CPU module disconnects the personal computer after the CPU module recognizes that the personal computer stops accessing to the CPU module

1 to 16383s 1800

6 19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function

19

Creating a database This section describes the procedure for creating a database to be used with the CPU module database access function. A database can be created with the following methods. Storing the database folder DBIMPORT(P) instruction (a database access instruction)

Storing the database folder Store the database folder in an SD memory card.

1. For the database folder, please consult your local Mitsubishi representative.

2. Create the CPUDB folder directly under the root directory of the SD memory card from the personal computer. (1)

3. Store the database folder (default database name: my_db_vv*1) in the CPUDB folder. (2) *1 "vv" indicates the version of the database folder.

The name of the database folder stored is recognized as the database name. The maximum number of characters in the folder path to the database folder is 128. The characters that can be used for a database name is the same as the Unicode text file specified by using the DBIMPORT(P) instruction. ( Page 319 Setting details of Unicode text file)

Only the CPUDB folder directly under the root directory can be used as the storage location of the database. In the CPUDB folder, store database folders only.

Up to 32 folders can be stored in the CPUDB folder. If data other than the database folder or 33 database folders or more is stored in the CPUDB folder, starting up of the

ODBC server is failed and an error code is stored in SD1498 (Start-up status of CPU module database).

Precautions Do not change, delete, or create a file and folder in the database folder from the personal computer. Otherwise, the CPU module database access function and database access instructions are completed with an error. If the above mentioned operations are performed from the personal computer, delete the database folder in the CPU module and create the new one.

DBIMPORT(P) instruction (a database access instruction) Use the DBIMPORT(P) instruction and create a database in an SD memory card according to the setting of the Unicode text file. For details on the Unicode text file, refer to the following. Page 319 Setting details of Unicode text file For details on the DBIMPORT(P) instruction, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

CPUDB my_db_vv

(1) (2)

XYZ_DB

Root directory

Up to 32 folders

19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function 327

32

Adding a database to the ODBC data source This section describes the procedure for adding a created database of the CPU module to the ODBC data source in the personal computer. (Examples of Windows 7 are shown below. Names of windows and menus may differ depending on the version of the OS.)

When the 64-bit OS is used, the ODBC Data Source Administrator of a 32-bit or 64-bit version can be used. Choose the appropriate one depending on the supported bit of the application used with the CPU module database access function. For the 64-bit OS, the ODBC Data Source Administrator can be started from the following. (When the start-up drive is C) 64-bit version: C:\WINDOWS\System32\odbcad32.exe 32-bit version: C:\WINDOWS\SysWOW64\odbcad32.exe

1. Select [Start] [Control Panel] [System and Security] [Administrative Tools] [Data Sources (ODBC)] on the personal computer and start the ODBC Data Source Administrator.

2. Click [User DSN] the [Add] button to display the "Create New Data Source" window.

3. Select "MELSEC iQ-R CPU Module Database Driver", and click the [Finish] button.

4. Set the database of the CPU module on the "Data Source Name Setup" window. ( Page 329 Data Source Name Setup)

8 19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function

19

Data Source Name Setup Set the database of the CPU module connected from the personal computer.

Window

Displayed items

*1 If they are not set, input them at login to connect to the database.

Click the [Test] button to perform a connection test of the database of the CPU module in accordance with the setting.

Item Description Data Source Name Set the identification name (any character string) for specifying the connection target database from the application.

Input 1 to 32 characters in single-byte or double-byte alphanumeric characters. Characters except for * ! ( ) = \ ? , [ ] can be used.

Description Input the comment. Input none, up to 1023 single-byte alphanumeric characters, or up to 512 double-byte characters.

Server Set the IP address of the CPU module to be connected.

Port Set 61461. (Default setting is 61461. Do not change the value.)

Database Set the absolute path of the database to be connected. For example, input the following for the database folder, my_db_vv, stored in the CPUDB folder directly under the root directory of the SD memory card.

2:\CPUDB\my_db_vv ("2:\" indicates the root directory of the SD memory card. "vv" indicates the version of the database folder.)

Default Authorization Login Name*1 Set the login user to access the database which is set. Input the user name which is set in the module parameter. ( Page 326 Built-in database access setting)

Password*1 Input the password which is set in the module parameter. ( Page 326 Built-in database access setting)

19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function 329

33

Application example This section describes the examples of database operations of the CPU module from applications in the personal computer using the CPU module database access function. (Names of windows and menus may differ depending on the version of the OS and application.)

The following table lists the applications whose connection to the database has been checked.

Creating a table by using an application The following provides an example to create a recipe table in a database of the CPU module by using Microsoft Access.

Item Description Application Reference Table creation Create a table in a database of the CPU module from the

personal computer. Microsoft Access Page 330 Creating a table by

using an application

Record operation Edit a database of the CPU module from the personal computer.

Microsoft Access Page 333 Record operation from an application

Record search Search a database of the CPU module from the personal computer.

Excel Page 335 Record search from an application

Database operation with the user-created application

Create a database access application using the ODBC classes of Microsoft .NET Framework.

User-created application Page 337 User-created application

Application Version Microsoft Access Microsoft Office 2010, 2013, 2016

Excel

User-created application Application created by using Microsoft .NET Framework 4.5

Ethernet

0 19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function

19

*1 Rename the ID field.

1. Start Microsoft Access and select "Blank database".

2. Add the following fields.

Field name Data type Data type for when the data is exported to the database of the CPU module

proID*1 AutoNumber type: Long integer INT

Enduser Numeric type: Long integer INT

TargetX Numeric type: Single-precision floating point type REAL

TargetY Numeric type: Single-precision floating point type REAL

TargetZ Numeric type: Single-precision floating point type REAL

3. Name the table "RecipeTable" and save it. After saving, close the table.

4. Right-click on RecipeTable, and select [Export] [ODBC Database].

5. When the window to specify the export destination is displayed, click the [OK] button.

6. On the window for selecting the data source, click the [Machine Data Source] tab and select the data source of the CPU module.

When the default user is not set to the ODBC data source, input the user name and password.

When no data source of the CPU module is displayed in the window, add a database of the CPU module to the ODBC data source. ( Page 328 Adding a database to the ODBC data source)

19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function 331

33

To set the details that cannot be set with Microsoft Access, send desired SQL commands to the database of the CPU module.

Clicking the [Create] tab [Query Design] of Microsoft Access displays the "Show Table" window, so click the [Close] button. The [Query Tools] tab becomes enabled. Select [Pass-Through].

Selecting [Pass-Through] enables the query tab and allows input of SQL commands to be sent to the database of the CPU module directly. For available SQL commands for the CPU module database access function, refer to the following. Page 689 List of Available SQL Commands for CPU Module Database Access Function

7. The result of export is displayed, and the table is added to the database of the CPU module.

2 19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function

19

Record operation from an application The following provides an example of record operation such as synchronizing, writing, and deleting of the data by connecting to the database of the CPU module by using Microsoft Access.

1. Start Microsoft Access and select the [External Data] tab [ODBC Database].

2. When the window to select the method for storing the data in the database, select "Link to the data source by creating a linked table", and click the [OK] button.

3. On the window for selecting the data source, click the [Machine Data Source] tab and select the data source of the CPU module.

When the default user is not set to the ODBC data source, input the user name and password.

When no data source of the CPU module is displayed in the window, add a database of the CPU module to the ODBC data source. ( Page 328 Adding a database to the ODBC data source)

Ethernet

19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function 333

33

4. On the window for selecting table, select a table to be operated and click the [OK] button to display the contents of the table.

(1) Select a cell to change the value. (2) Select a row to delete the record. (3) Add a new record.

5. When the value is changed or the record is deleted, the database of the CPU module is changed according to the operation.

(3)

(2)

(1)

4 19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function

19

Record search from an application The following provides an example to search the record that matches the specified condition from the production data stored in the database by connecting to the database of the CPU module by using Excel.

1. Start Excel, and select the [Data] tab [From Other Sources] [From Microsoft Query].

2. On the window for selecting the data source, select the data source of the CPU module.

When the default user is not set to the ODBC data source, input the user name and password.

When no data source of the CPU module is displayed in the window, add a database of the CPU module to the ODBC data source. ( Page 328 Adding a database to the ODBC data source)

3. On the window for selecting columns of the query wizard, select the field to be output.

4. On the window for filtering data of the query wizard, set the search condition.

Ethernet

19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function 335

33

When the file used in the above procedure is saved, the search condition is also saved. Click the [Data] tab [Refresh All] in Excel to acquire the data in the same condition from the database of the CPU module once more.

5. On the window for setting the sort order of the query wizard, set the condition to sort the output data.

6. Set the output destination. Then, the search result is output.

6 19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function

19

User-created application The following describes a sample program for accessing the database of the CPU module with the SQL command using the ODBC class of Microsoft .NET Framework.

Overview of the sample program This sample program performs the condition search in the database of the CPU module using the value of the Judge field as its key, and displays the acquired search result in a list and graph (scatter plot).

(1) Specify the database source name to be connected. (2) Specify the Judge field value to be searched. (3) Click the [Search] button to search the record with the same value as the one specified by "JudgeValue" in the database specified by "DataSource". (4) The acquired record is displayed in the list. (5) The X value and Y value of the acquired record are displayed in a graph (scatter plot).

Ethernet

(4)

(2)

(1) (3) (5)

19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function 337

33

Database configuration of the sample program The following describes the database configuration to be searched by the sample program.

The following table lists the records of CheckData table.

Item Description Server name (IP address of CPU module) 192.168.3.39

Database folder path 2:\Database\SampleDB

Database name SampleDB

Table name to be searched CheckData

SerialNo Enduser X Y Z Judge 20170428010 A 494 500 497 1

20170428011 B 500 495 492 1

20170428012 C 493 510 510 1

20170428013 A 492 490 510 1

20170428014 B 526 502 458 0

20170428015 C 509 508 501 1

20170428016 A 484 539 498 0

20170428017 B 469 510 539 0

20170428018 C 501 499 509 1

20170428019 A 493 502 497 1

20170428020 B 458 507 453 0

20170428021 C 508 497 493 1

20170428022 A 495 506 504 1

20170428023 B 506 505 490 1

20170428024 C 535 474 526 0

20170428025 A 507 509 509 1

8 19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function

19

Source code of the sample program The following describes the source code of the sample program. Development environment: Visual Studio 2015 Programming language: C# namespace iQ_R_DB_Access { public partial class FrmMain : Form { public FrmMain() { InitializeComponent();

// Range setting of X-/Y-axis on a graph chart1.ChartAreas[0].AxisX.Minimum = 400; chart1.ChartAreas[0].AxisX.Maximum = 600; chart1.ChartAreas[0].AxisY.Minimum = 400; chart1.ChartAreas[0].AxisY.Maximum = 600;

// Initial value (all) set to the judge value of search target cmbJudge.SelectedIndex = 2; }

///

/// Operation when the Search button is clicked /// Records that match the judge value specified by the combo box are acquired and displayed in a list and a scatter plot of X and Y field values. /// /// /// private void btnSearch_Click(object sender, EventArgs e) { // The number of fields (the number of fields on the CheckData table) int len = 6;

// Acquiring the data source name string strConnect = txtDataSourceName.Text.ToString(); // ODBC connection information management class OdbcConnectionStringBuilder o = new OdbcConnectionStringBuilder(); o.Dsn = strConnect; // Creating the connection object OdbcConnection cn = new OdbcConnection(o.ConnectionString);

// SQL statement string strQuery = GetSQL(); // Creating the command object OdbcCommand cmd = new OdbcCommand(strQuery, cn);

// Initializing the list dtRecord.Rows.Clear(); // Initializing the graph chart1.Series[0].Points.Clear();

try { // Connecting to DB cn.Open();

// Creating the data reader object OdbcDataReader reader = cmd.ExecuteReader();

19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function 339

34

// Processing the search results one record at a time for (int recordnum = 0; reader.Read(); recordnum++) { // Adding a blank row to the list dtRecord.Rows.Add();

Setting the number of rows to be inserted into the list recordnum = dtRecord.Rows.Count-2; Storing acquired records into the list one field at a time for (int i = 0; i < len; i++) { // Adding search results into the list dtRecord.Rows[recordnum].Cells[i].Value = reader.GetValue(i); }

// Plotting values of X and Y fields on the graph chart1.Series[0].Points.AddXY(Convert.ToInt32(dtRecord.Rows[recordnum].Cells[2].Value), Convert.ToInt32(dtRecord.Rows[recordnum].Cells[3].Value)); } } catch (OdbcException ex) { MessageBox.Show(ex.ToString()); } finally { // Disconnecting from DB cn.Close(); } }

///

/// Generating the SQL statement from the value in the combo box /// public string GetSQL() { string strSQL = "";

switch (cmbJudge.SelectedIndex) { case 0: // The search target is records of Judge = 0. strSQL = "SELECT SerialNo, Enduser, X, Y, Z, Judge FROM CheckData WHERE Judge=0"; break; case 1: // The search target is records of Judge = 1. strSQL = "SELECT SerialNo, Enduser, X, Y, Z, Judge FROM CheckData WHERE Judge=1"; break; case 2: // Acquiring all the records strSQL = "SELECT SerialNo, Enduser, X, Y, Z, Judge FROM CheckData"; break;

default: strSQL = "SELECT * FROM CheckData"; break; } return strSQL; } } }

0 19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function

19

Precautions This section describes the precautions for using the CPU module database access function.

Database creation When creating a database in the CPUDB folder, use characters that can be specified only. If the characters that cannot be specified are used to create the database, the table cannot be accessed by the database access instructions. For the characters that can be specified, refer to the following. Page 319 Setting details of Unicode text file

Combination of the firmware version and database The following table lists the combination of the firmware version of the programmable controller CPU that creates the database and that of the programmable controller CPU where the operation of the database is available. : Available, : Not available

*1 If the database that has been operated with the programmable controller CPU with firmware version "28" or later is operated with the programmable controller CPU with firmware version earlier than "28", the operation is completed with an error.

Number of connections that can be operated simultaneously Up to four connections can be operated with the CPU module database access function simultaneously. However, if an application such as Microsoft Access uses several connections, four applications may not connect with the database of the CPU module simultaneously. If an attempt was made to connect with the database with all the connections used, an error occurs in the application and the database cannot be connected. In this case, end unused applications connected with the database and connect again.

Several simultaneous accesses When several applications access the same database in the CPU module, the database processing becomes slow.

Access to the same table When the database access instructions or the CPU module database access function access the same table, the function executed first locks the table, and an error may occur in the function executed later. For the database access instruction, an error code is stored in the completion status.

Definition change of the same database When the database definition is changed with "CREATE TABLE" or "DROP TABLE" in a single database from several applications using the CPU module database access function, the application executed first locks the database and an error may occur in the function executed later.

Database Availability

The programmable controller CPU with firmware version earlier than "28"

The programmable controller CPU with firmware version "28" or later

Database created with the programmable controller CPU with firmware version earlier than "28"

*1

Database created with the programmable controller CPU with firmware version "28" or later

19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function 341

34

Completion with an error during database access Do not power off or reset the CPU module during the access to a database of the CPU module. Otherwise, the change is not reflected on the database that is being executed.

Files created with this function Do not create, change, and delete the ODBC server setting file (netserver.cfg), database path file (dbmaintainpath.txt), and error database check file (ErrorDB.txt) created with the CPU module database access function. Otherwise, the CPU module database access function or database access instruction is completed with an error. If the above mentioned operations are performed, delete the database folder in the CPU module and create the new one.

Removal of the SD memory card To remove the SD memory card while the ODBC server is active, execute the SD memory card forced disable and check that CARD READY LED is off before removing the SD memory card. (Failure to do so may result in a failure of databases.) Since databases stop after the execution of the SD memory card forced disable, databases of the CPU module cannot be accessed. (The error code is stored in SD1498.) To access the databases of the CPU module again, insert the SD memory card and power off and on or reset the CPU module.

Free space of the SD memory card To use the CPU module database access function, the SD memory card must have at least 20MB of free space. When the free space of the SD memory card becomes 20MB or less while the CPU module database access function is used, SM1497 (Memory card free space flag for CPU module database) turns on. When the free space of the SD memory card becomes 10MB or less, the ODBC server of the CPU module stops and the error code is stored in SD1498 (Start-up status of CPU module database). When the ODBC server stops because the SD memory card does not have enough free space, secure the free space of the SD memory card using the online operation and power off and on or reset the CPU module. Powering off and on or resetting the CPU module starts the ODBC server.

When the SD memory card is write-protected To use the CPU module database access function, the user must ensure that write protection of the SD memory card is off. When the SD memory card is write-protected, the CPU module database access function cannot update the database and the error code is stored in SD1498.

2 19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function

19

When the load of the CPU module is high When the CPU module database access function is used with high circuit load to the Ethernet port of the CPU module by other functions or high access load to the SD memory card, a timeout error may occur in the application on the personal computer side. In this case, eliminate the cause of the error and execute this function.

Errors Errors detected by the CPU module The CPU module starts the ODBC server based on the setting of the module parameter. When the CPU module fails to start the ODBC server, the error code is stored in SD1498 (Start-up status of CPU module database). For the error code to be stored, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

Errors detected by the personal computer When an error occurs during the access to the database of the CPU module, the CPU module returns the error message to the personal computer. In this case, check the error message displayed on the personal computer and eliminate the cause of the error. The error causes are as follows. The built-in database access setting of the module parameter is disabled. The ODBC server of the CPU module is not started. (SM1498 is not on.) The communication between the Ethernet port of the CPU module and the personal computer is not established. There is no database to be accessed. Multiple accesses are simultaneously performed to an access target database. A broken database is being accessed. The database is accessed when the circuit load of the Ethernet port of the CPU module or the access load to the SD

memory card are high.

19 DATABASE FUNCTION 19.3 CPU Module Database Access (from External Device) Function 343

34

20 PID CONTROL FUNCTION This chapter describes the PID control function. PID control is applicable to process control in which factors such as flow rate, velocity, air flow volume, temperature, tension, and mixing ratio must be controlled. The control for maintaining the control object at the preset value is shown in the diagram below: PID control via the PID control instructions is implemented by combining the CPU module with the A/D converter module and D/A converter module.

*1 SV: Set value *2 PV: Process value *3 MV: Manipulated value

In the PID control, the PID operation is executed to compare the value set beforehand (SV) with the digital value (process value (PV)) in which the analog value measured by a sensor is read from the A/D converter module. PID operation utilizes proportional operation (P), integral operation (I), and derivative operation (D) in combination, thereby calculating the manipulated value (MV) quickly and accurately so that a process value (PV) is to be equivalent to a set value (SV). A larger difference between the process value (PV) and set value (SV) results in a faster speed to reach the set value (SV) quickly by increasing the manipulated value (MV) and a smaller difference between the process value (PV) and set value (SV) results in a slower speed to reach the set value (SV) accurately by decreasing the manipulated value (MV). The calculated manipulated value (MV) is written to the D/A converter module and output to the external device.

For the PID control, use the PID operation instruction. To execute the same PID control as that of the MELSEC-Q series and MELSEC-L series, use the PID control instructions. For details on the comparison between the PID operation instruction and PID control instructions, instruction specifications, PID control, and programming, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

SV

PV

MV

PV

*3

*2

*1

*2 Automatic/manual switching

Manual MV

PID operation Automatic MV

PID control instruction Inside the CPU module

D/A converter module

A/D converter module

Controlled system

Sensor

Set value

4 20 PID CONTROL FUNCTION

20

MEMO

20 PID CONTROL FUNCTION 345

34

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION

This function backs up data such as program files, a parameter file, and device/label data*1 of a CPU module to an SD memory card. The data backed up in the SD memory card can be restored as required. *1 Module access devices and buffer memory are excluded.

The following table lists the backup and restoration methods of the CPU module data backup/restoration function.

The restoration function modifies programs, parameters, or device/label data of the CPU module. After restoration, check the restored data carefully before an actual operation. (Check the data with an engineering tool.)

This function cannot be used in the R00CPU, R01CPU, and R02CPU. When using the CPU module data backup/restoration function, check the versions of the CPU module and

engineering tool used. ( Page 700 Added and Enhanced Functions)

Function Reference Backup function Backup processing triggered by turning on SM1351 Page 353 Backup processing triggered by turning on SM1351

Automatic backup using SD944 Page 354 Automatic backup using SD944

Restoration function Restoration processing triggered by turning on SM1354 Page 361 Restoration processing triggered by turning on SM1354

Automatic restoration using SD955 Page 362 Automatic restoration using SD955

CPU

Backup

20160102

20160101

00001

00002

$MELPRJ$ Program memory

Device/label data

Device/label data

Program memory

Backup

Restoration

Data memory

Data memory

Device/label memory

Device/label memory

SD memory card CPU module

6 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION

21

Backup data Backup data is saved in an SD memory card. The following shows the folder structure of backup data.

No. Folder type Folder name Number of storable folders

Description

(1) Backup data folder

Backup (Fixed) 1 A folder for storing all backup data

(2) CPU data folder CPU (Fixed) 1 A folder for storing backup data of the CPU module

(3) Date folder Automatically determined*1

Folder name format: YYYYMMDD YYYY: Year when the data was backed up (four digits) MM: Month when the data was backed up (two digits) DD: Day when the data was backed up (two digits)

Depends on the capacity of the SD memory card used*2 or 1 to 100 folders

Folders for storing backup data by date For the setting of the upper limit value for the number of CPU module backup data, the number of backup data indicates the number of date folders. ( Page 351 Setting the upper limit value for the number of CPU module backup data)

(4) Number folder Automatically determined*1

Folder name: Sequentially numbered from 00001 to 32767 (five digits)

Depends on the capacity of the SD memory card used*2

Folders for storing information per backup data. Each backup data created on a date is stored in sequentially numbered folders.

(5) Drive folder Drive0 (Fixed), Drive3 (Fixed), and Drive4 (Fixed) One set of the folders in a number folder

Folders for storing folders/files stored in each drive of the backup target CPU module by each drive

(6) System file for backing up CPU module data

$BKUP_CPU_INF.BSC One folder in a number folder

Files for storing the information required at restoration of data, such as a list of backup data and identification information of the CPU module

(7) Backup data file for backing up CPU module data

BKUP_CPU.BKD One folder in a number folder

The following data is stored. Data on operations of the data logging setting Data for restarting the SFC program from the

block and step where the processing was stopped

(8) Device/label data file for backing up CPU module data

BKUP_CPU_DEVLAB.BKD One folder in a number folder

Device/label data is stored.

Drive0 MAIN.PRG

FB.PFB

0000120160101CPU

00002

20160102

Drive3 FILEREG.QDR

LOGCOM.QLG

Drive4 $MELPRJ$ MAIN.PRG

MEMDUMP.DPS

$BKUP_CPU_INF.BSC

BKUP_CPU.BKD

BKUP_CPU_DEVLAB.BKD

(2)(1)

$MELPRJ$ Backup

(3) (4) (5)

(6)

(7)

(8)

/ Root directory

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 347

34

*1 Date folders and number folders are automatically named by the CPU module. *2 The maximum number of storable folders is 32767. *3 When bit 2 of SD955 (Restoration function setting) is set to on at the backup processing, the file is generated if it is not in the CPU folder,

and the setting information stored is updated if it is. (When bit 2 of SD955 is set to off at the backup processing, the file is not generated.)

Backup/restoration target data Backup target data is all target data in the CPU module. ( Page 348 Backup/restoration target files) Restoration target data is set with SD954 (Restoration target data setting). ( Page 359 Restoration target data)

Backup/restoration target drives Target drives are Drive0 (Program memory), Drive3 (Device/label memory), and Drive4 (Data memory). Drive2 (SD memory card) is not a target drive.

Backup/restoration target files The following table lists backup/restoration target files. : Available, : Not available

All folders/files in the CPU built-in memory are backup/restoration targets.

The number of CPU module backup data that can be stored in an SD memory card The number of CPU module backup data that can be stored in an SD memory card is 32767. This number is equal to the maximum number of storable folders. The number of files that can be backed up and restored (the number of backup source data files) depends on the maximum number of files of each model or drive.

File type Backup/restoration Program

FB file

CPU parameter

System parameter

Module parameter

Memory card parameter

Device comment

Device initial value

Global label setting file

Initial label value file Initial global label value file

Initial local label value file

File register

Event history

Device data storage file

General-purpose data

Data logging setting file Common setting file

Individual setting file

Memory dump setting file

Remote password

System file for the iQ Sensor Solution data backup/restoration function

Backup data file for the iQ Sensor Solution data backup/restoration function

Slave station parameter file

ODBC server setting file

Recording setting file

8 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION

21

Backup/restoration target device data : Available, : Not available

*1 Whether to restore these areas can be set to the bit 14 of SD955 (Restoration function setting). *2 Areas used by the system may be overwritten after restoration. *3 Includes local devices. *4 Includes the local index register. *5 Device data may be overwritten depending on the mounting status (I/O refresh) of each module or the refresh settings.

Classification Device name Symbol Backup*5 Restoration*5

User device Input X

Output Y

Internal relay M *3 *3

Link relay B

Annunciator F

Link special relay SB

Edge relay V *3 *3

Step relay S

Timer T *3 *3

Retentive timer ST *3 *3

Long timer LT *3 *3

Long retentive timer LST *3 *3

Counter C *3 *3

Long counter LC *3 *3

Data register D *3 *3

Link register W

Link special register SW

Latch relay L

System device Function input FX

Function output FY

Function register FD

Special relay SM *1*2

Special register SD *1*2

Link direct device Link input Jn\X

Link output Jn\Y

Link relay Jn\B

Link special relay Jn\SB

Link register Jn\W

Link special register Jn\SW

Module access device Module access device Un\G

CPU buffer memory access device

CPU buffer memory access device U3En\G *2

U3En\HG *2

Index register Index register Z *4 *4

Long index register LZ *4 *4

File register File register R/ZR

Refresh data register Refresh data register RD

Nesting Nesting N

Pointer Pointer P

Interrupt pointer I

Other devices Network No. specification device J

I/O No. specification device U

SFC block device BL

SFC transition device TR

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 349

35

Backup/restoration target label data : Available, : Not available

*1 For module labels, data may be overwritten to the write areas from a module to the CPU module when the refresh settings have been made.

*2 Device data may be overwritten depending on the mounting status (I/O refresh) of each module or the refresh settings.

Progress of the backup/restoration processing The progress of the backup/restoration processing can be checked in SD1350 (Number of uncompleted folders/files of CPU module data backup/restoration) or SD1351 (Progression status of CPU module data backup/restoration). However, the progress of the automatic restoration cannot be checked with the special register.

*1 When program files are restored, the progress in SD1351 stops while data is being written to the program memory in the restoration processing because the data is transferred from the program cache memory to the program memory. The progress of data transfer to the program memory can be checked in SD629 (Program memory write (transfer) status).

Classification Backup*2 Restoration*2

Global label (including module labels) *1

Global label with latch specified

Local label

Local label with latch specified

Special register Description SD1350 Displays the number of remaining backup/restoration target folders and files.

When the backup/restoration processing is started, the total number of backup/restoration folders and files is stored.

When the backup/restoration processing is completed, 0 is stored.

SD1351 Displays the progress of the backup/restoration processing in percentage (0 to 100%).*1

0 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION

21

21.1 Backup Function This function backs up data of a specified CPU module in an SD memory card.

The backup function operates even when the CPU module is in the RUN state. When executing the backup function with the CPU module in the RUN state, do not change device/label data during execution of the function. Doing so may cause data inconsistency of the device/label data and the contents of the backup data may unintentionally change.

Setting the upper limit value for the number of CPU module backup data When the backup processing has not been executed (when no backup data folder (CPU data folder) exists in the SD memory card), the upper limit value for the number of CPU module backup data can be set. The number of CPU module backup data in the upper limit value setting is the number of date folders. The upper limit value for the number of CPU module backup data is enabled by turning on the bit 5 of SD944 (Enable the upper limit value for the number of CPU module backup data). The set value can be checked in SD960 (Upper limit status for the number of CPU module backup data). When the bit 5 of SD944 is turned off, no upper limit value setting is applied.

If data folders are created more than the capacity of the SD memory card before the number of them reaches the upper limit value for the number of CPU module backup data, the backup processing is completed with an error and the data cannot be backed up to reach the upper limit value.

Special relay/Special register Description SM960 This relay specifies an operation of backup when the number of CPU module backup data reaches the upper

limit value. (This relay is valid only when the bit 5 of SD944 is on.) Off: The oldest date folder is deleted, and the backup operation continues. On: The backup operation does not continue if the upper limit value for the number of CPU module backup

data is exceeded. (In this case, the backup is completed with an error.)

Bit 5 of SD944 Set to enable or disable the upper limit value for the number of CPU module backup data. Off: Disable (No limit (Date folders are created within the maximum capacity of the SD memory card.) On: Enable

SD960 This register displays the value (1 to 100) set in SD1353. If the bit 5 of SD944 is off, 0 is stored in this special register (SD).

SD1353 Set the upper limit value (1 to 100) for the number of CPU module backup data.

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.1 Backup Function 351

35

Operation of the special relay and special register The following figure shows the operations of the special relay and special register of when the upper limit value for the number of CPU module backup data has been set. Check the following at the timing on when the bit 5 of SD944 (Enable the upper limit value for the number of CPU module backup data) is turned on, and enable the upper limit value for the number of CPU module backup data. The backup processing has not been executed (when no backup data folder (CPU data folder) exists in the SD memory

card). The value set in SD1353 (Upper limit value setting for the number of CPU module backup data) is within the range (1 to

100).

(1) The upper limit value for the number of CPU module backup data is set. (0 10)

ON

SM1351

OFF

END END

OFF

SM1350

SD944(bit5)

0 10

0 10

ON

(1)

SD1353

SD960

ON

END

OFF

2 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.1 Backup Function

21

Backup processing triggered by turning on SM1351 Data in the CPU module is backed up at a desired timing.

Operating procedure Data in the CPU module is backed up by turning on SM1351.

1. To set the upper limit value for the number of CPU module backup data, follow the steps below. Set SD1353 (Upper limit value for the number of CPU module backup data). Set SM960 (Upper limit operation setting flag for the number of CPU module backup data). Turn on the bit 5 of SD944 (Backup function setting). For the upper limit value for the number of CPU module backup data, refer to the following. Page 351 Setting the upper limit value for the number of CPU module backup data

2. Turn on SM1351 (CPU module data backup execution request).

If the backup processing is completed with an error and SM953 (CPU module data backup error check flag) turns on, check SD953 (Backup error cause), take actions, and then back up the data again as required.

The execution status of the backup processing can be checked in SD1350 (Number of uncompleted folders/ files of CPU module data backup/restoration) and SD1351 (Progression status of CPU module data backup/ restoration). ( Page 350 Progress of the backup/restoration processing)

(1) A backup execution request is sent. (2) The system turns on SM1350 (CPU module data backup status flag). (3) The system turns off SM1351 after the backup processing is completed. (4) The system turns off SM1350.

ON

SM1351

OFF

END END END END ENDEND ENDEND END

ON OFF

(1) (3)

(2)

(4)

SM1350

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.1 Backup Function 353

35

Automatic backup using SD944 Data in the CPU module can be automatically backed up at a preset execution timing. Set the execution timing of the automatic backup with SD944 (Backup function setting). Multiple execution timing settings can be set.

Since the special register set for the automatic backup is a latch area, setting data is held.

Retrying the automatic backup Set whether to retry the automatic backup when the automatic backup is executed during execution of an operation or function that cannot be executed ( Page 357 Operations and functions that cannot be performed). The retry interval is three minutes and the number of retries is 10.

The setting of the bit 10 of SD944 (Backup function setting) cannot be changed during execution of the automatic backup. The retry setting of the automatic backup is enabled at the following timing. When the bit 0, bit 1, or bit 15 of SD944 turns on

Operating procedure (when date and time are specified) Data is automatically backed up on the specified date and time.

1. Set the upper limit value for the number of CPU module backup data. (The setting method and operating procedure for the upper limit value are the same as those for the upper limit value for the backup processing triggered by turning on SM1351.) ( Page 353 Operating procedure)

2. Set the date and time with SD947 to SD949.

3. To retry the automatic backup, turn on the bit 10 of SD944 (Backup function setting). For the retry of the automatic backup, refer to the following.

Page 354 Retrying the automatic backup

4. Turn on the bit 0 of SD944. If the backup processing is completed with an error and SM953 (CPU module data backup error check flag) turns on, check SD953 (Backup error cause), take actions, and then back up the data again as required.

Bit pattern of SD944 Execution timing Bit 0: On On the time set in SD948 and SD949 on the day set in SD947

Bit 1: On On the time set in SD950 and SD951 on the day of the week set to SD952

Bit 15: On When a stop error has occurred in the CPU module

Special relay/Special register Description SM961 This relay turns on when the retry of the automatic backup is completed with an error after the retry of the

automatic backup for the number of retries was attempted. This relay turns off at the start of the automatic backup. (This relay does not turn off when SM1351 (CPU module data backup execution request) is on.) Off: Retry not executed/Retry being executed On: Retry failed

SM1356 This relay turns on during execution of the retry of the automatic backup. This relay turns on at the start of the retry of the automatic backup and turns off when the retry of the automatic backup is started or the retry of the automatic backup for the number of retries is attempted without execution of an operation or function that cannot be executed. Off: Retry is not being executed. On: Retry is being executed.

Bit 10 of SD944 Set whether to retry the automatic backup. Off: Retry is not executed. On: Retry is executed.

Special register Description SD947 Set the date when the data is to be automatically backed up.

SD948 Set the time (hour) when the data is to be automatically backed up.

SD949 Set the time (minute) when the data is to be automatically backed up.

4 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.1 Backup Function

21

In months that does not have the specified date, the automatic backup is not executed. For example, when SD947 has been set to "31", the months when the automatic backup is executed are January, March, May, July, August, October, and December.

If the time less than 1 hour from the start time of daylight saving time has been set with the daylight saving time function, the automatic backup is not executed.

Operating procedure (when time and day of the week are specified) Data is automatically backed up on the specified time on the specified day of the week.

1. Set the upper limit value for the number of CPU module backup data. (The setting method and operating procedure for the upper limit value are the same as those for the upper limit value for the backup processing triggered by turning on SM1351. ( Page 353 Operating procedure))

2. Set the time and day of the week with SD950 to SD952.

3. To retry the automatic backup, turn on the bit 10 of SD944 (Backup function setting). For the retry of the automatic backup, refer to the following.

Page 354 Retrying the automatic backup

4. Turn on the bit 1 of SD944. If the backup processing is completed with an error and SM953 turns on, check SD953, take actions, and then back up the data again as required.

If the time less than 1 hour from the start time of daylight saving time has been set with the daylight saving time function, the automatic backup is not executed.

Operating procedure (when a stop error has occurred in the CPU module) Data is automatically backed up when a stop error occurs in the CPU module.

1. Set the upper limit value for the number of CPU module backup data. (The setting method and operating procedure for the upper limit value are the same as those for the upper limit value for the backup processing triggered by turning on SM1351. ( Page 353 Operating procedure))

2. To retry the automatic backup, turn on the bit 10 of SD944 (Backup function setting). For the retry of the automatic backup, refer to the following.

Page 354 Retrying the automatic backup

3. Turn on the bit 15 of SD944. If the backup processing is completed with an error and SM953 turns on, check SD953, take actions, and then back up the data again as required.

If a major error has occurred, the automatic backup may not be performed.

Checking backup errors When an error has occurred, a diagnostic error is not detected and an error code is stored in SD953 (Backup error cause). ( Page 502 List of Error Codes)

Special register Description SD950 Set the time (hour) when the data is to be automatically backed up.

SD951 Set the time (minute) when the data is to be automatically backed up.

SD952 Set the day of the week when the data is to be automatically backed up. b0: Sunday, b1: Monday, b2: Tuesday, b3: Wednesday, b4: Thursday, b5: Friday, b6: Saturday

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.1 Backup Function 355

35

Precautions The following describes the precautions for the backup function.

Prohibited operation during execution of the backup processing Do not perform the following operations during execution of the backup processing. Removing and inserting the SD memory card Powering off or resetting the CPU module The above mentioned operations leave the backup data in the SD memory card in an incomplete state which is middle of the backup processing. Do not use these data for a restoration. If these data are used, the restoration is completed with an error.

Suspending backup processing The following operation can suspend a backup processing. Setting the SD memory card forced disable Suspending a backup processing leaves the backup data in the SD memory card in an incomplete state which is middle of the backup processing. Do not use these data for a restoration. If these data are used, the restoration is completed with an error.

Device/label data To execute the backup processing, do not change device/label data during execution of the processing. Since device/label data is divided into multiple scans and backed up, changes in the device/label data may cause data inconsistency.

When labels accessible from external devices have been set in the CPU module For the CPU module with firmware version "24" or earlier, the backup cannot be executed if labels accessible from external devices have been set in the CPU module by access label settings from external devices. Check that no such labels have been set in the CPU module and then execute the backup processing.

When parameter settings were changed before execution of the backup processing When programs or parameter settings were changed, check that operations are performed with the new programs and parameter settings and then execute the backup function. If the backup processing is executed without the check of the operations with the new programs and parameter settings, the restoration processing may not be executed.

Changing backup target data Do not change backup target data in the CPU module during execution of the backup processing. If the target data was changed during execution of the backup processing, the changes will not applied.

Special relay and special register that function as flags to execute other functions Before executing the backup processing, turn off the special relay and special register that function as flags to execute other functions. If the backup processing is executed when they are on, the corresponding function request may turn on and the function may be executed at the restoration of data in the special relay and special register.

Data protected by security functions File password function Unlock the file passwords of the files in the backup target CPU module. If any files to which file passwords have been set exist in the CPU module, the files are not backed up.

Security key authentication function Locked programs are backed up in the locked state regardless of whether security keys have been written or not.

6 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.1 Backup Function

21

Timing for setting the upper limit value for the number of CPU module backup data Set the upper limit value for the number of CPU module backup data before execution of the backup processing. When the backup processing has been executed (a CPU data folder exists in the SD memory card) and the bit 5 of SD944 (Enable the upper limit value for the number of CPU module backup data) is turned on, an error will occur. Even though the backup processing has been executed, turning on the bit 5 of SD944 can disable the upper limit value for the number of CPU module backup data. To set the upper limit value for the number of CPU module backup data again, replace the SD memory card with another one where no CPU data folder exist, or turn off and on the bit 5 of SD944 after deleting the backup data folder.

SFC program status Do not change the status of the SFC program, such as step active status and transition conditions during execution of the backup processing. If the status of the SFC program was changed, the backup processing is completed with an error.

Time required for completing the backup processing The backup processing takes more time depending on the size of data or the number of folders/files stored in the CPU module.

Operations and functions that cannot be performed While the following operations or functions are being executed, the backup processing cannot be executed. The following operations and functions cannot be executed during execution of the backup processing.

Operation or function Operation from the engineering tool Initializing the CPU built-in memory/SD memory card

Clearing values (Devices, labels, file registers, latches)

Writing data to the programmable controller (including online change of files)

Deleting data in the programmable controller

User data operation Writing user data

Deleting user data

Creating a folder

Deleting a folder

Changing a folder name

Online change (online change (ladder block))

Event history function (Clearing event history)

File password function

Security key authentication function (Writing/deleting a security key to/in the CPU module)

Predefined protocol support function (Writing protocol setting data)

Memory dump function (Registering/clearing memory dump)

Firmware update function (Firmware update using the engineering tool)

Operation using the CPU module logging configuration tool

Data logging function (Writing/deleting a logging setting file, registering/clearing a logging setting, stopping a logging)

Deleting a logging file

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.1 Backup Function 357

35

*1 The operation performed only for opening a file to write data *2 It is executed when the trigger logging data collection is completed or data collection for the specified number of storage files is

completed.

Backup during execution of the backup processing The backup processing triggered by turning on SM1351 or automatic backup cannot be executed during execution of the backup processing. (The latter backup processing is ignored.)

Data logging function and backup When the CPU built-in memory (function memory) is specified for the data storage destination memory in the data logging function, the function memory is cleared after the CPU module is powered off or the RESET state is cleared. Thus, data logging files are also cleared. To prevent data logging files from being lost, back up the files after the completion of file transfer by the data logging file transfer function.

Others SLMP MC protocol

Clearing the remote latch (Remote Latch Clear)

Creating a new file (New File)

Writing data to a file (Write File)

Deleting a file (Delete File)

Copying a file (Copy File)

Changing a file attribute (Change File State)

Changing file creation date (Change File Date)

Opening a file (Open File)*1

File transfer from an Ethernet-equipped module (FTP server)

Writing a file (put, mput, pm-write)

Deleting a file (delete, mdelete)

Changing a file name (rename)

Changing a file attribute (change)

File transfer function (FTP server) of the built-in Ethernet function

File transfer function (FTP client) of the built-in Ethernet function

Changing an IP address

iQ Sensor Solution data backup/restoration function

System operation setting with SD384

Transfer to the data memory with special relay

Data logging file transfer to data memory*2

Operation or function

8 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.1 Backup Function

21

21.2 Restoration Function This function restores backup data in the SD memory card to the CPU module.

Restoration target folder Set restoration target data among backup data in the SD memory card with SD956 (Restoration target date folder setting) to SD958 (Restoration target number folder setting). The latest backup data can be restored with the bit 13 of SD955 (Restoration function setting).

*1 The latest data is the backup data with the largest number in the latest date folder.

Restoration target data Restoration target data is set with SD954 (Restoration target data setting).

Restoration of the special relay and special register Set whether to restore the special relay and special register with the bit 14 of SD955.

However, the special relay/special register areas listed below are not restored even when the bit 14 of SD955 is on.

Special register Description Bit 13 of SD955 Set the restoration function setting with bit patterns.

Off: Data specified with the restoration target folders is restored. On: The latest data is restored.*1

SD957, SD956 Specify a date folder of the restoration target data in BCD. SD957 (upper): Year, SD956 (lower): Month and date

SD958 Specify the folder number (00001 to 32767) of restoration target data.

Value of SD954 Restoration target data setting 0 All target data

1 Only device/label data

2 All target data excluding device/label data

Bit 14 of SD955 Restoration target data setting Off The special relay and special register are not restored.

On The special relay and special register are restored.

CPU module Special relay/Special register Programmable controller CPU Special relay/special register areas for the CPU module data backup/restoration function

SM953, SM959, SM961, SM1350, SM1351, SM1353, SM1354, SM1356, SD953, SD959, SD1350, SD1351, SD1353

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.2 Restoration Function 359

36

Operation setting after restoration As an operation after the restoration processing, set whether to operate the CPU module in the status at the backup processing or to operate the CPU module in the initial status with the bit 15 of SD955. The following table lists the operations of each item to be performed according to the operation setting after restoration.

*1 When the firmware version of the CPU module at the backup processing is different from that of at the restoration processing, the SFC program will be started from the block 0 and step 0 regardless of the operation setting after the restoration.

Note that this setting is invalid since the device initial value file, initial global label value file, initial local label value file, event history file, and SFC program are not restored when the value in SD954 (Restoration target data setting) is 1 (restoration target data are only device/label data).

For the operation setting after restoration, specify the operation at a completion of restoration. When the CPU module is switched from STOP to RUN, values of devices are changed according to the operation of the device memory at an operating status change of the CPU module. ( Page 121 Operation Processing When Operating Status Is Changed)

Item Operation setting after restoration

Operating the CPU module in the status at data backup (bit 15 of SD955 = On)

Operating the CPU module in the initial status (bit 15 of SD955 = Off)

Device initial value The device initial value is not set after the restoration processing.

The device initial value is set after the restoration processing. (The device data at data backup will be overwritten with the device initial value.)

Initial values of global/local labels The initial values of global/local labels are not set after the restoration processing.

The initial values of global/local labels are set after the restoration processing. (The label data at data backup will be overwritten with the initial value of the initial global/ local value.)

SFC program*1 When "Resume Start" was selected before data backup, the SFC program is resumed after restoration processing.

The SFC program is not resumed after restoration processing even though "Resume Start" was selected before data restoration.

Event history The event history at data backup is set. The event history at data backup is not set, a new file is created and a restoration event is registered.

0 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.2 Restoration Function

21

Restoration processing triggered by turning on SM1354 Backup data is restored at a desired timing.

Use the restoration function by turning on SM1354 to check the backup data and to test before actual operation. To operate the system using the backup data, use the automatic restoration with SD955. ( Page 362 Operating procedure)

The restoration processing triggered by turning on SM1354 (CPU module data restoration execution request) can be executed only when the CPU module is the STOP state.

Operating procedure 1. Set restoration target data with SD954 (Restoration target data setting).

2. Set a restoration target folder in the areas from SD956 (Restoration target date folder setting) to SD958 (Restoration target number folder setting). (These settings are not required when the bit 13 of SD955 is on.)

3. Set each setting with the bit 13 to 15 of SD955.

4. Set the CPU module to the STOP state.

5. Turn on SM1354.

If the restoration processing is completed with an error and SM959 (CPU module data restoration error check flag) turns on, check SD959 (Restoration error cause), take actions, and then restore the data again as required.

The execution status of the restoration processing can be checked in SD1350 (Number of uncompleted folders/files of CPU module data backup/restoration) and SD1351 (Progression status of CPU module data backup/restoration). ( Page 602 List of Special Register Areas)

(1) A restoration execution request is sent. (2) The system turns on SM1353 (CPU module data restoration status flag). (3) The system turns off SM1354 after the restoration processing is completed. (4) The system turns off SM1353.

ON

SM1354

OFF

END END END END ENDEND ENDEND END

ON OFF

(1) (3)

(2)

(4)

SM1355

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.2 Restoration Function 361

36

Automatic restoration using SD955 Backup data is automatically restored when the CPU module is powered on or is reset.

Initialization at the automatic restoration Set whether or not to initialize drives other than the SD memory card at execution of the automatic restoration with the bit 1 of SD955 (Restoration function setting). This setting is enabled only when SD954 (Restoration target data setting) is set to 0 (All target data).

Operating procedure 1. Set the data to restore in SD954.

2. Set a restoration target folder in the areas from SD956 (Restoration target date folder setting) to SD958 (Restoration target number folder setting). (These settings are not required when the bit 13 of SD955 is on.)

3. Set values to the bit 1 and bits from 13 to 15 of SD955.

4. Turn on the bit 0 of SD955.

5. Power off and on or reset the CPU module. If the restoration processing is completed with an error and SM959 (CPU module data restoration error check flag) turns on, check SD959 (Restoration error cause), take actions, and then restore the data again as required.

Since the special register set for the automatic restoration is a latch area, setting data is held. SD955 holds its setting even after the CPU module is powered on or is reset. Thus, if the CPU module is

powered on or is reset while the bit 0 of SD955 is on, the automatic restoration is executed again. Not to perform the automatic restoration when the CPU module is powered on or is reset next time, turn off the bit 0 of SD955 after a restoration is completed and then power on or reset the CPU module.

Checking restoration errors When an error occurs in the restoration processing triggered by turning on SM1354, a diagnostic error is not detected and

an error code is stored in SD959 (Restoration error cause). ( Page 502 List of Error Codes) When an error occurs at the automatic restoration using SD955, a diagnostic error is detected. The error code is also

stored in SD959. ( Page 502 List of Error Codes)

Bit 1 of SD955 Restoration target data setting Off Not initialized

On Initialized

2 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.2 Restoration Function

21

Precautions The following describes the precautions for the restoration function.

Prohibited operation during execution of the restoration processing Do not perform the following operations during execution of the restoration processing. Removing and inserting the SD memory card Powering off or resetting the CPU module The above mentioned operations leave the data in the CPU module in an incomplete state which is middle of the restoration processing. Do not run the CPU module with this incomplete state. Doing so may cause an unintended operation. Restore the data again or format each drive in the CPU module, and clear devices/labels before writing programs or parameters to the programmable controller.

Suspending the restoration processing The following operation can suspend a restoration processing. Setting the SD memory card forced disable Suspension during a restoration leaves the data in the CPU module in an incomplete state which is middle of the restoration processing. Do not run the CPU module with this incomplete state. Doing so may cause an unintended operation. Restore the data again or format each drive in the CPU module, and clear devices/labels before writing programs or parameters to the programmable controller.

Model name of the CPU module to which data is restored Restore the data to the CPU module whose model name is the same as that of the CPU module where the backup data has been stored. If not, the data cannot be restored.

When labels accessible from external devices have been set in the CPU module For the programmable controller CPU with firmware version "24" or earlier, the restoration cannot be executed if labels accessible from external devices have been set in the CPU module by access label settings from external devices. Check that no such labels have been set in the CPU module and then execute the restoration processing. For the programmable controller CPU with firmware version "25" or later, the restoration by turning on SM1354 cannot be executed if labels accessible from external devices have been set in the CPU module or in a backed up data from external devices. When the restoration is required, execute the automatic restoration using SD955.

Automatic restoration using SD955 and functions that cannot be executed Do not set both of the automatic restoration using SD955 and the boot operation at a time. If the CPU module is powered on or is reset with both of the automatic restoration using SD955 and the boot operation set, the automatic restoration using SD955 does not function.

Status of the restoration destination CPU module If the status of the restoration destination CPU module differs from that of the CPU module at the backup processing (such as programs or parameters), the restoration may not be executed. When the backup data to be restored is backed up in a different status from that of the restoration destination CPU module, store 0 (All the target data) to SD954 (Restoration target data setting) and execute the automatic restoration.

When the same name folder or file exists in the restoration target CPU module If the name of a folder or file in the restoration target CPU module and the name of a folder or file in backup data are identical, the folder or file in the module will be overwritten by that in the backup data.

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.2 Restoration Function 363

36

Changing the operating status during execution of restoration During execution of the restoration processing, the CPU module remains in the STOP state even though the RUN/STOP/ RESET switch is changed from the STOP to RUN position or the remote RUN or the remote PAUSE is executed. If the operating status of the CPU module is changed, the status will changes to the set status after the restoration processing is completed.

Time required for completing the restoration processing The restoration processing takes more time depending on the number of backup data sets (folders), file size, and the number of files in the SD memory card. In a multiple CPU system, if the automatic restoration has taken time and an error has occurred in another CPU module, another error may occur in the CPU module to which the automatic restoration was executed after the completion of the restoration. In that case, shorten the time for restoration. Change the setting of SD954 (Restoration target data setting) to only the device data that is to be cleared at a system start-up, and execute the automatic restoration again.

Monitoring stop at restoration Stop monitoring before executing the restoration processing. When the restoration processing is executed, programs, parameters, and device/label values may not be properly monitored because they are changing.

Reflecting restored data Some of the parameters are reflected only when the CPU module is powered on or is reset. If the restoration processing is executed while the CPU module is in the STOP state and then is switched to the RUN state, the CPU module may not operate with the backup data. In that case, power on or reset the CPU module. For device/label data, since device/label data except for latch-specified devices/labels is initialized when the CPU module is powered on or is reset, restore the device/label data again as required.

Abnormal completion of restoration Since the restoration processing will be completed with an error, do not execute the restoration processing in the following cases. The name of a file in the restoration destination CPU module and the name of a file in backup data are identical, and a file

password has been set. Data in a backup folder has been deleted. (Do not delete the data in backup folders that are likely to be used for

restoration.) Backup data has problems. (Backup data has been changed or the CPU module was powered off during execution of the

backup processing.)

Instruction executed at the rising/falling edge when data is restored When the program file is restored by turning on SM1354, the execution status of instructions is undefined and the instructions executed at the rising/falling edge may not work properly. To operate the system by restoring the backup data, use the automatic restoration with SD955.

When the special relay and special register are restored When a restoration is operated with the setting to restore the special relay and special register, the system will be operated with the values (time, day of the week, day, time, and the upper limit value of the number of backup data for the automatic backup set to the backup function setting) before restoration. (The backup function setting will not be re-set although the special register areas are overwritten by the restoration.) To operate the system with the restored backup function setting, set the backup function setting again.

4 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.2 Restoration Function

21

Data protected by security functions File password function Unlock the file passwords of the files in the backup target CPU module. If any files to which file passwords have been set exist in the CPU module, the files are not restored.

Security key authentication function Locked programs can be restored regardless of whether security keys have been written or not. However, when the security key has not been written to the CPU module after the restoration processing, the program cannot be executed. Restore unlocked backup data or set the same security key.

When the SFC program is restarted from where the program was stopped Specify the continue start. When the continue start has not been specified, the SFC program will be started from the block 0 and step 0 even though the bit 15 of SD955 is on (the continue start is executed).

When the IP address change function is used If the backup processing is executed with the IP address stored in the IP address storage area (system memory), the IP address will be changed at the following timing in the restoration processing. Restoration processing triggered by turning on SM1354: When the CPU module is powered on or is reset after the

restoration processing Automatic restoration using SD955: When the restoration processing is executed

Operations and functions that cannot be performed While the following operations or functions are being executed, the restoration processing cannot be executed. The following operations and functions cannot be executed during execution of the restoration processing.

Operation or function Operation from the engineering tool

Initializing the CPU built-in memory/SD memory card

Clearing values (Devices, labels, file registers, latches)

Reading data from the programmable controller

Writing data to the programmable controller (including online change of files)

Verifying data with the programmable controller

Deleting data in the programmable controller

User data operation Reading user data

Writing user data

Deleting user data

Creating a folder

Deleting a folder

Changing a folder name

Online change (online change (ladder block))

Event history function (Updating event history data, clearing event history)

File password function

Security key authentication function (Writing/deleting a security key to/in the CPU module)

Predefined protocol support function (writing/reading/verifying protocol setting data)

Memory dump function (Memory dump setting/reading results, registering/clearing memory dump)

Firmware update function (Firmware update using the engineering tool)

Operation using the CPU module logging configuration tool

Data logging function (Writing/reading/deleting a logging setting file, registering/clearing a logging setting, stopping a logging)

Deleting a logging file

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.2 Restoration Function 365

36

*1 It is executed when the trigger logging data collection is completed or data collection for the specified number of storage files is completed.

Operation of when the data logging function is used If data is backed up during execution of the data logging function and the function has been set to be started automatically when the operating status of the CPU module is changed to RUN, the data logging function will be automatically executed when the status of the CPU module changes to RUN after the restoration processing. To restart the data logging function after the restoration processing without the above setting, use the CPU module logging configuration tool. When the CPU built-in memory (function memory) is specified for the data storage destination memory, the function memory is not backed up. Therefore, when the data logging is restarted after the restoration processing, the logging files are deleted after the CPU module is powered off or the RESET state is cleared, and the logging file number starts from 1 at the storage file switching.

Restoration during execution of the restoration processing The restoration processing triggered by turning on SM1354 cannot be executed during execution of the restoration processing. (The latter restoration processing is ignored.)

When the CPU module database access function is used When the data is backed up with the CPU module data backup/restoration function and restored by turning on SM1354 while using the CPU module database access function, power off and on or reset the CPU module regardless of the completion status of the restoration. (For the automatic restoration by SD955, the CPU module is not required to be powered off and on or reset.)

Others SLMP MC protocol

Remote latch clear (Remote Latch Clear)

Creating a new file (New File)

Writing data to a file (Write File)

Deleting a file (Delete File)

Copying a file (Copy File)

Changing a file attribute (Change File State)

Changing file creation date (Change File Date)

Opening a file (Open File)

Reading a file (Read File)

File transfer from an Ethernet-equipped module (FTP server)

Reading a file (get, mget)

Writing a file (put, mput, pm-write)

Deleting a file (delete, mdelete)

Changing a file name (rename)

Changing a file attribute (change)

File transfer function (FTP server) of the built-in Ethernet function

File transfer function (FTP client) of the built-in Ethernet function

Changing an IP address

iQ Sensor Solution data backup/restoration function

System operation setting with SD384

Transfer to the data memory with special relay

Data logging file transfer to data memory*1

Operation or function

6 21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.2 Restoration Function

21

Restoration of when the data allocation in the program file is different The data allocation in the program file differs depending on the firmware version of the CPU module. ( Page 125 Data allocation and procedure of read/write operations) When the data backed up using the CPU module with the conventional data allocation is restored to the CPU module with the new data allocation, the restoration processing is completed successfully. In this case, data allocation in the CPU module is different. Therefore, an error occurs when the CPU module is powered off and on or is reset, or the module operating status is changed from STOP to RUN after the restoration processing. When the data backed up using the CPU module with the new data allocation is restored to the CPU module with the conventional data allocation, the restoration processing may be completed with an error. In this case, an error occurs when the CPU module is powered off and on or is reset, or the module operating status is changed from STOP to RUN after the restoration processing.

21 CPU MODULE DATA BACKUP/RESTORATION FUNCTION 21.2 Restoration Function 367

36

22 MULTIPLE CPU SYSTEM FUNCTION With multiple CPU modules mounted on the base unit, each of the CPU modules controls their own assigned I/O modules and intelligent function modules. In addition, the CPU modules communicate with each other.

For details on the concept of the multiple CPU system configuration specification (System configuration specifications such as the mounting position of the CPU modules and assignment of CPU number/IO number), refer to the MELSEC iQ-R Module Configuration Manual.

For the start-up (Setting, operating procedures, etc) of the Multiple CPU system, refer to the GX Works3 Operating Manual.

The startup time of the multiple CPU system may be slowed, depending on the configuration of installed modules, boot operation, functions performed before CPU modules enter into the RUN state (e.g. setting of initial device/label values), the configuration of system parameters and CPU parameters (e.g. the number of programs to run).

When diagnostics of the SD memory card is performed due to operation such as power-off during access to the SD memory card, the startup time of the multiple CPU system may be slowed.

Create a program so that only one CPU module accesses the Q series module, if possible. If multiple CPU modules access the Q series module simultaneously, the scan time (including the execution processing of interrupt programs) may be extended due to access waiting time.

Before using the multiple CPU system function with the RnENCPU, check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

8 22 MULTIPLE CPU SYSTEM FUNCTION

22

22.1 Out-of-group I/O Fetch The access range to the controlled module is different from that to the non-controlled module. To fetch the data which cannot be accessed, use the out-of-group I/O fetch function.

Accessing controlled module The access range to the controlled module of the CPU module is the same as that to the single CPU system, and I/O refresh for the controlled module and/or reading/writing to buffer memory of the intelligent function module are enabled.

Accessing non-controlled module Access to the non-controlled module of the CPU module is limited to reading input (DX) and buffer memory of the intelligent function module. Note that On/Off data of input (X)/output (Y) of the non-controlled module can be fetched using the out-of- group I/O Fetch function. ( Page 370 Out-of-group I/O fetch setting) : Accessible, : Not accessible

*1 Cannot read from CPU modules which are synchronized through the inter-module synchronization function.

Precautions An error is not detected in reading input (DX) for the non-controlled module and buffer memory of the intelligent function module.

Communication method

Access target Access range

When "Import" is selected in the settings for out-of-group I/O fetch

When "Not Imported" is selected in the settings for out- of-group I/O fetch

Communication through refresh

Input (X) Read to another CPU module

*1 (Non-processing)

Output (Y) Write to another CPU module

(Non-processing)

Read to another CPU module

*1

The buffer memory of the intelligent function module

Read (Cannot be specified from engineering tools)

(Cannot be specified from engineering tools)Write

Link direct device Read (Cannot be specified from engineering tools)

(Cannot be specified from engineering tools)Write

Communication through direct access

Input (DX) Read to another CPU module

Output (DY) Write to another CPU module

(Non-processing) (Non-processing)

Read to another CPU module

(Cannot be specified) (Cannot be specified)

The buffer memory of the intelligent function module

Read

Write (An error occurs in the CPU module.)

(An error occurs in the CPU module.)

Link direct device Read (An error occurs.) (An error occurs.)

Write

22 MULTIPLE CPU SYSTEM FUNCTION 22.1 Out-of-group I/O Fetch 369

37

Out-of-group I/O fetch setting In this menu item, whether or not out-of-group I/O status is fetched can be specified.

[System Parameter] [Multiple CPU Setting] [Other PLC Control Module Setting] [I/O Setting Outside Group]

Window

Displayed items

Fetching input (X) When "Import" is selected for "Input Status Outside Group" in "I/O Setting Outside Group", the input refresh before the start of the program operation fetches On/Off data from the input module and/or intelligent function module controlled by other CPU modules.

Modules from which input (X) can be fetched Input (X) can be fetched from the following modules mounted on the base/extension base unit. Input module I/O combined module*1

Intelligent function module *1 Data in the areas assigned to the output portion (area not used) are not fetched. On/Off state is maintained.

Input (X) cannot be fetched from the Q series modules.

Fetching output (Y) When "Import" is selected for "Output Status Outside Group" in "I/O Setting Outside Group", the output refresh before the start of the program operation fetches On/Off data output to the output module and/or intelligent function module controlled by other CPU modules into output (Y) for the host CPU module.

Modules from which output (Y) can be fetched Output (Y) can be fetched from the following modules mounted on the base/extension base unit. Output module I/O combined module Intelligent function module

Output (Y) cannot be fetched from the Q series modules.

Item Description Setting range Default Input Status Outside Group Specify whether or not out-of-group input status is fetched. Not Imported

Import Not Imported

Output Status Outside Group Specify whether or not out-of-group output status is fetched. Not Imported Import

Not Imported

0 22 MULTIPLE CPU SYSTEM FUNCTION 22.1 Out-of-group I/O Fetch

22

Output to output/intelligent function module On/off data cannot be output to non-controlled modules. When turning on or off output of the output module and/or intelligent function module controlled by other CPU modules by the program or others, the output is turned on or off within the CPU module. However, it is not output to output/intelligent function module.

Accessing buffer memory of intelligent function module Reading data on buffer memory The following instructions can be used to read data stored in the buffer memory of the intelligent function module. FROM instruction Instruction using the CPU module access device (Un\Gn)

Writing data to buffer memory The following instructions cannot be used to write data to the buffer memory of the intelligent function module. TO instruction Instruction using the CPU module access device (Un\Gn)

Accessing a module by using link direct devices The CPU module can access only to modules under its control by using link direct devices. Non-controlled modules cannot be accessed.

22 MULTIPLE CPU SYSTEM FUNCTION 22.1 Out-of-group I/O Fetch 371

37

22.2 Operation Settings This section describes the operation settings of the multiple CPU system function.

Stop setting An operating status, whether to stop the operation of all the CPU modules or not, if a major or moderate error occurs in any of the CPU modules is set.

[System Parameter] [Multiple CPU Setting] [Operation Mode Setting] [Stop Setting]

Window

Displayed items

Applicable errors to the stop setting The following table lists the applicable errors to the setting that specifies the operation of all the CPU modules of when a major or moderate error has occurred in any of the CPU modules.

Item Description Setting range Default PLC No.1 Set whether to stop the operation of all the CPU modules or not

if a major or moderate error occurs in CPU No.1. Major: All Station Stop, Moderate:

All Station Stop Major: All Station Stop, Moderate:

All Station Continue Major: All Station Continue,

Moderate: All Station Continue

Major: All Station Stop, Moderate: All Station Stop

PLC No.2 Set whether to stop the operation of all the CPU modules or not if a major or moderate error occurs in CPU No.2.

PLC No.3 Set whether to stop the operation of all the CPU modules or not if a major or moderate error occurs in CPU No.3.

PLC No.4 Set whether to stop the operation of all the CPU modules or not if a major or moderate error occurs in CPU No.4.

Error name Error code Another CPU module moderate error 1220H

Another CPU module major error 2461H, 2462H, 2470H

2 22 MULTIPLE CPU SYSTEM FUNCTION 22.2 Operation Settings

22

Synchronous startup setting Startup time is synchronized among the CPU modules. This setting eliminates the need for an interlock program that monitors the startup time of another CPU module when accessing it. Note, however, that the startup of the entire system delays because the system starts up with the last CPU module.

[System Parameter] [Multiple CPU Setting] [Operation Mode Setting] [Synchronous Startup Setting]

Window

Displayed items

Group setting for the synchronized start-up is available. For example, a setting in which only CPUs No.1 and No.2 start synchronously within a multiple CPU system with four CPU modules is possible.

If a reserved (empty) CPU is specified to synchronize, it is skipped and the other CPUs in the group start synchronously.

This setting is designed to access to each CPU module without interlock in the multiple CPU system. It is not intended to be used for starting operation processing at the same time across CPU modules after startup.

Item Description Setting range Default PLC No.1 Set the CPU modules whose startup time is synchronized in

the multiple CPU system. Synchronize Do not Synchronize

Synchronize

PLC No.2

PLC No.3

PLC No.4

22 MULTIPLE CPU SYSTEM FUNCTION 22.2 Operation Settings 373

37

Program to check start-up of each CPU module It is recommended to create a program that checks start-up of each CPU module using SM220 to SM223 (CPUs No.1 to No.4 preparation completed) when the multiple CPU synchronized startup is disabled. If a certain instruction is issued against a CPU module that has not started, the instruction executes no processing.

Ex.

Program to check start-up of CPU module of CPU No.2

To synchronize the start of operation processing across CPU modules, a program is required to check whether individual CPU modules are ready to start operation processing or not.

The following is an example of the configuration of a program which synchronizes the start of operation processing across CPU modules and programs which should start operation processing synchronously.

Program Execution type Description Program to synchronize the start of operation processing

Scan This is a program used to synchronize the start of operation processing across all CPU modules. This program must be specified as one for running at the beginning of the scan execution type of program. Also, when all the CPU modules are ready to start operation processing, the flag indicating an operation start turns on for only one scan.

Program to start operation processing synchronously

Event This is a program which should be executed when all the CPU modules are ready to start operation processing. This program must be specified as an event execution type program which is triggered when the operation start flag is turned on.

SM221

Access CPU No.2.

MOV U3E1\HG100 D0

Programs for synchronizing the operation starts among each CPU module

Programs whose operation starts are to be synchronized

Project of the CPU No.1 Project of the CPU No.2 Project of the CPU No.3 Project of the CPU No.4

4 22 MULTIPLE CPU SYSTEM FUNCTION 22.2 Operation Settings

22

Program example Devices to be used for programs to start operation processing synchronously

Example of a program to synchronize the start of operation processing

Device to be used Application M0 Flag that indicates the operation processing is ready to be started (after a flag that indicates the operation start turns on, this flag

turns off.)

M1 Flag that indicates an operation start (this flag turns on for only one scan.)

U3En\G2048 The synchronization counter of each CPU module (n=0: CPU No.1, n=1: CPU No.2, n=2: CPU No.3, n=3: CPU No.4)

D2 to D9 The storage location for values of the synchronization counter of each CPU module

M2 to M9 The operation processing start wait state of each CPU module

22 MULTIPLE CPU SYSTEM FUNCTION 22.2 Operation Settings 375

37

Clock data CPUs No.2 to No.4 automatically synchronize their clock data to the one set for CPU No.1 (even if setting up clock data individually for each CPU, they will be overwritten). Therefore, simply setting up the clock data for CPU No.1 allows to manipulate a unified clock data across the entire multiple CPU system ( Page 148 Time Setting)

As with clock data, the same settings as those for CPU No.1 apply to CPU Nos. 2 to 4. Time zone setting ( Page 150 Setting Time Zone) Daylight saving time setting ( Page 151 Daylight Saving Time Function)

6 22 MULTIPLE CPU SYSTEM FUNCTION 22.2 Operation Settings

22

22.3 Multiple CPU Parameter Checking Whether the same setting is configured for between the system parameter of each CPU module and multiple CPU refresh number of points of CPU parameter is checked by the multiple CPU system at the timing shown below. However, as for the fixed scan communication setting and inter-module synchronization setting, checking is done only for the module using the functions. At power-on At reset of the CPU No.1 At operating status change (STOP to RUN) after parameter change

Ex.

An error occurs in the module of each CPU No 2 and 3, and the module of each CPU No 1 and 4 starts up normally when parameter checking. (Operation in error)

: there is setting (if the number immediately next is the same number, it refers to the same parameter) , : there is no setting

Timing Parameters to check Checking conditions for CPU No.1

Checking conditions for CPU No.2 and over

At power-on or reset of the CPU No.1

System parameters (other than fixed scan communication setting and inter- module synchronous setting)

Checking is not conducted. Compares with the parameters of the CPU of the lowest number.

Settings of fixed scan communication Checking is not conducted by the CPU module of the number for which the fixed scan communication setting is not configured. The CPU module of the number for which the fixed scan communication setting is configured will compare the parameters with those of the CPU of the lowest number.

Inter-module synchronization setting Checking is not conducted by the CPU module of the number for which the Inter- module synchronization setting is not configured. The CPU module of the number for which the Inter-module synchronization setting is configured will compare the parameters with those of the CPU of the lowest number.

CPU parameters (number of points of refresh settings)

Checking is not conducted by the CPU module of the number for which the fixed scan communication setting is not configured. The CPU module of the number for which the fixed scan communication setting is configured will compare the parameters with those of the CPU of the lowest number.

At operating status change (STOP to RUN) after parameter change

Compares with the parameters of the host CPU module before parameters are changed.

Item Setting conditions for the CPUs of each number

PLC No.1 PLC No.2 PLC No.3 PLC No.4 With or without the setting for each parameter

System parameters (other than fixed scan communication setting and inter-module synchronous setting)*1

1 5 1 1

Settings of fixed scan communication*2 2 2 6

Inter-module synchronization setting*3 3 3

CPU parameters (number of points of refresh settings)*4 4 4

*1

*3

*2

*4

*3

*4

*1

*2

*1

*2

*1

CPU No.1

System parameter

CPU parameter

CPU No.2

System parameter

CPU parameter

CPU No.3

System parameter

CPU parameter

CPU No.4

System parameter

CPU parameter

Check

Check

Check

Check

A verification mismatch occurs.

A verification mismatch occurs.

22 MULTIPLE CPU SYSTEM FUNCTION 22.3 Multiple CPU Parameter Checking 377

37

22.4 Data Communication Between CPU Modules CPU modules within a multiple CPU system can send and transfer data to each other. The refresh communication and direct access communication enable data writing or reading between CPU modules. The following table lists the data communication method.

Memory to be used CPU buffer memory is utilized for data communication between the CPU modules.

Memory configuration of CPU buffer memory This section describes the memory configuration of CPU buffer memory.

*1 Data cannot be written to the areas of other CPU modules.

Communication method Application Description Data communication with CPU buffer memory

This method is used when data is sent or received at the timing of each CPU module.

The CPU module for sending the data writes data into the CPU Buffer memory of the host CPU module. The CPU module for receiving data reads data from the CPU Buffer memory of the sender CPU module (other CPU modules).

Data communication with fixed scan communication area

This method is used when data is sent or received through adjusting the timing between CPU modules.

The CPU module for sending the data writes data into the fixed scan communication area (send area) of the host CPU module. The CPU module for receiving data reads data from the fixed scan communication area (receive area) of the host CPU module of the send source CPU module.

Memory Communication method

Description Area size

CPU buffer memory Communication through direct access

This area is used to read/write data from/to the areas of the host CPU module or other CPU modules.*1 ( Page 390 Communication through direct access)

512K words fixed

Refresh area Communication through refresh

Data communication is conducted through refresh at END processing. ( Page 386 Communication through refresh)

Fixed scan communication area

Communication through direct access

This area communicates the data to the fixed scan communication area of the host CPU module, and is used when the host CPU module area and another CPU module area transfer the data at the fixed scan communication cycles. ( Page 390 Communication through direct access)

It is possible to change within the range of 0 to 24K words in total. The send area as per unit can be set within the range of 0 to 12K words. ( Page 381 Setting fixed scan communication area)

The Refresh Area in the Fixed Scan Communication Area

Communication through refresh

The refresh operation is conducted at the fixed scan communication cycle. ( Page 386 Communication through refresh)

CPU buffer memory

Refresh area

Refresh area

Fi xe

d sc

an c

om m

un ic

at io

n ar

ea

Send area of CPU No.4

Refresh area

Send area of CPU No.3

Refresh area

Send area of CPU No.2

Refresh area

Send area of CPU No.1

8 22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules

22

Avoidance of 64-bit data inconsistency To avoid 64-bit data inconsistency, access the CPU buffer memory by specifying the start address as a multiple of four similarly to the device to be specified.

(1) The CPU module assures a 64-bit data and write the data to the CPU buffer memory. (TO U3E0 K2052 D0 K4) (2) The CPU module assures a 64-bit data and write the data to the CPU buffer memory. (TO U3E0 K2056 D4 K4) (3) The CPU module assures a 64-bit data and read the data from the CPU buffer memory. (FROM U3E0 K2052 D100 K4) (4) The CPU module assures a 64-bit data and read the data from the CPU buffer memory. (FROM U3E0 K2056 D104 K4)

D4

D0

G2048

G2052

G2056 D104

D100

(1)

(2)

(3)

(4)

Device

4 words (64 bits)

4 words (64 bits)

4 words (64 bits)

4 words (64 bits)

Device

CPU buffer memory

CPU No.1 CPU No.2

22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules 379

38

Checking for the memory configuration This section describes the CPU buffer memory configuration of each CPU No. The refresh setting can be configured in both the CPU parameter and the window shown below. ( Page 389 Refresh settings)

[System Parameter] [Multiple CPU Setting] [Communication Setting between CPUs] [CPU Buffer Memory Setting] [Detailed Setting]

Window

Displayed items

Item Description Setting range Default [Set] button of each refresh area This menu item sets up the refresh settings used for data communication

between CPU modules. (The settings are linked with the refresh settings of CPU parameter)

0 points

[Send/Receive Direction Display between CPUs] button

Click the button and arrows that indicate the send/receive direction appear.

0 22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules

22

Setting the data communication with fixed scan communication area This section describes the setting for making the data communication with fixed scan communication area.

Setting whether or not it should be used To communicate data with the fixed scan communication area, "Enable" must be set to "Fixed Scan Communication Function".

[System Parameter] [Multiple CPU Setting] [Communication Setting between CPUs] [Fixed Scan Communication Function]

Window

Displayed items

Setting fixed scan communication area This menu item sets up the range of send area for each CPU in the fixed scan communication area (the refresh area and the total of areas used for direct access communication). Only the fixed scan communication area can be changed with the parameter settings. The other areas are not configurable.

[System Parameter] [Multiple CPU Setting] [Communication Setting between CPUs] [Fixed Scan Communication Area Setting]

Window

Displayed items

*1 The max area size that can be set through setting of the fixed scan communication area differs depending on the fixed scan communication cycle.

Item Description Setting range Default Fixed Scan Communication Function

Specify whether or not the fixed scan communication function should be used.

Not Use Use

Not Use

Item Description Setting range Default Total [K Word] View the total value. Entire system: 0 to 24K words*1

PLC No. 1 [Start XY: U3E0] Set the send area size for CPU No.1. 0 to 12K words 0K word

PLC No. 2 [Start XY: U3E1] Set the send area size for CPU No.2. 0 to 12K words 0K word

PLC No. 3 [Start XY: U3E2] Set the send area size for CPU No.3. 0 to 12K words 0K word

PLC No. 4 [Start XY: U3E3] Set the send area size for CPU No.4. 0 to 12K words 0K word

Fixed scan communication cycle Max area size that can be set through setting of the fixed scan communication area

0.10ms 12K points

0.15ms 20K points

Except for shown above 24K points

22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules 381

38

When there exists a CPU module for which "Disable" is set to "Fixed Scan Communication Function", if the send area of the fixed scan communication area is set to a CPU module for which "Disable" is set to "Fixed Scan Communication Function" (unspecified) in the parameter setting on the host CPU module, no error is generated because the unspecified CPU module is considered as a reserved one for future configuration. Example: in four module configuration with the host CPU module is set to CPU No.1 and the fixed scan communication function of CPU No.4 set to "Disable"

(1) Since the setting does not allow fixed scan communication, this CPU module does not send data to the other CPU modules although send areas have been reserved. This CPU module does not receive data from the other CPU modules.

(1)

Send area of CPU No.1

Send area of CPU No.2

(Receive area of CPU No.1)

Send area of CPU No.3

(Receive area of CPU No.1)

Send area of CPU No.4

(Receive area of CPU No.1)

Send area of CPU No.2

Send area of CPU No.3

Send area of CPU No.4

Fixed scan communication area

Fixed scan communication area

CPU No.1 (host CPU module)

CPU No.2 (another CPU module)

Setting: Establish fixed scan communication.

Setting: Establish fixed scan communication.

Setting: Establish fixed scan communication.

Setting: Do not establish fixed scan communication.

Send area of CPU No.1

Send area of CPU No.2

Send area of CPU No.3

Send area of CPU No.4

Fixed scan communication area

CPU No.3 (another CPU module)

Send area of CPU No.1

Fixed scan communication area

CPU No.4 (another CPU module)

2 22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules

22

Fixed scan communication setting This menu item sets up the interval for data transfer between CPU modules. The data transfer interval can be synchronized with the timing for inter-module synchronization cycle ( MELSEC iQ-R Inter-Module Synchronization Function Reference Manual)

[System Parameter] [Multiple CPU Setting] [Fixed Scan Communication Setting] [Fixed Scan Interval Setting of Fixed Scan Communication]

Window

Displayed items

*1 This item is not displayed on the R00CPU, R01CPU, and R02CPU.

The send image for the fixed scan communication can be reviewed through the "Fixed Scan Communication Function Operation Image Display".

The minimum value for the fixed scan interval setting that can be set in the R00CPU, R01CPU, and R02CPU is 0.50ms. Therefore, when building the multiple CPU system including the R00CPU, R01CPU, and R02CPU, set the interval to 0.50ms or more for the CPU module to be used with.

Error detection setting When data is communicated among the CPU modules in a multiple CPU system, some data writing timing may lead to a failure of the complete data communication in the fixed scan communication cycle after the data writing and data inconsistency may occur. In this setting, set whether to detect a continuation error or not in this case. ( Page 169 Error detection setting)

Item Description Setting range Default 0.05ms Unit Setting Specify whether to set the fixed scan communication

cycle in increments of 0.05ms. Not Set Set

Not Set

Fixed Scan Interval Setting (Not Set by 0.05ms) Select the fixed scan communication cycle from the drop-down list. The same option should be specified only for CPU modules which will use the fixed scan communication function.

0.222ms*1

0.444ms*1

0.888ms 1.777ms 3.555ms 7.111ms

0.888ms

Fixed Scan Interval Setting (Set by 0.05ms) Specify the fixed scan communication cycle freely in increments of 0.05ms.

R00CPU, R01CPU, R02CPU: 0.50 to 10.00ms

Other CPU modules: 0.10 to 10.00ms

R00CPU, R01CPU, R02CPU: 0.50ms

Other CPU modules: 0.10ms

Fixed Scan Communication Function and Inter- module Synchronization Function

Set whether the fixed scan communication cycle cooperates with the inter-module synchronization cycle.

Not Cooperated Cooperate

Not Cooperated

22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules 383

38

Module-by-module data guarantee In data communication, data is handled in units of 64 bits. Therefore, when data larger than 64 bits is handled, old and new data may be mixed for each CPU module depending on the timing between data reading by the host CPU module and data writing by other CPU modules/data receiving from other CPU modules. (Data inconsistency) To avoid this problem, the system conducts the refresh operation by exchanging handshake signals between the CPU modules for guaranteeing refresh data on a module-by-module basis.

1 2 3

10 11

50 51

100 101 102

1

1 1 1

1 1

1 1

1 101 101

1

1

1 2 3

10 11

50 51

100 101 102

10

50

100

1 2 3

10 11

50 51

100 101 102

100

50

100

01 D0,D1

0 0 0 0 0

D0,D1

0 0 0 0 0

0 0 0 0 0

D0,D1

0 0 0 0 0

D0,D1

0 0 0 0 0

SM 400 DINC D0

01

01 01 01

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

:

Data change when the CPU module unit guarantee is disabled

(Scan) First scan Second scan Third scan

10th scan 11th scan

50th scan 51st scan

100th scan 101st scan 102nd scan

(Value) (Scan)

First scan

Fifth scan

10th scan

(Value)(Scan) First scan Second scan Third scan

10th scan 11th scan

50th scan 51st scan

100th scan 101st scan 102nd scan

(Value)

Device memory CPU buffer memory Device memory Device memory Device memory

(Scan)

First scan

(Value)(Scan)

First scan

Second scan

(Value)

Time: (The time axis is based on the CPU No.1.)

The CPU reflects (refreshes) the data in the END processing of each scan.

(Scan) First scan Second scan Third scan

10th scan 11th scan

50th scan 51st scan

100th scan 101st scan 102nd scan

(Value) (Scan)

First scan

(Value)

CPU No.1 CPU No.2 CPU No.3

(Scan) First scan Second scan Third scan

10th scan 11th scan

50th scan 51st scan

100th scan 101st scan 102nd scan

(Value)

Device memory CPU buffer memory

Data change when the CPU module unit guarantee is enabled

Device memory Device memory Device memory

(Scan)

First scan

(Value)(Scan)

First scan

(Value)

CPU No.4

Time: (The time axis is based on the CPU No.1.)

CPU No.1

Device

CPU buffer memory

Device Device Device

Program

(2) The CPU No.1 reflects (refreshes) the data in the END processing of the CPU No.1.

The CPU module unit guarantee is enabled: (3) The CPU No.1 does not update (refresh) the data in the END processing until the other CPU modules receive the data.

The CPU module unit guarantee is enabled: (5) The CPU No.2 does not update (refresh) the data in the END processing until the CPU No.3 and 4 receive the data.

The CPU module unit guarantee is enabled: (9) All the CPU modules have received the data, and the CPU No.1 updates (refreshes) the data in the END processing. 1 101

(4) The CPU No.2 reflects (refreshes) the data in the END processing of the CPU No.2.

(6) The CPU No.3 reflects (refreshes) the data in the END processing of the CPU No.3.

(8) The CPU No.4 reflects (refreshes) the data in the END processing of the CPU No.4.

The CPU module unit guarantee is enabled: (7) The CPU No.3 does not update (refresh) the data in the END processing until the CPU No.4 receives the data.

(1) The data is written from the program.

Scan time: 1ms

CPU No.2

CPU buffer memory

Scan time: 10ms

CPU No.3

CPU buffer memory

Scan time: 50ms

CPU No.4

CPU buffer memory

Scan time: 100ms

4 22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules

22

Prevention of data inconsistency by module-by-module data guarantee The following table shows the preventive control against data inconsistency according to the presence or absence of module- by-module data guarantee. : With the preventive control against data inconsistency by the system, : Without the preventive control against data inconsistency by the system*1

*1 The countermeasure by the program is required. ( Page 393 Data assurance by program) *2 Limited to the case of access within the multiple CPU synchronous interrupt program (I45). ( Page 395 When accessing fixed scan

communication area)

Module-by-module data guarantee Set up the module-by-module data guarantee.

[System Parameter] [Multiple CPU Setting] [Communication Setting between CPUs] [PLC Unit Data]

Window

Displayed items

For communications by the direct access with the CPU buffer memory other than the fixed scan communication area, data is not guaranteed on a module-by-module basis even when this setting is enabled, because the data on the CPU buffer memory of other CPU modules is directly read after execution of the read instruction.

Data send/receive timing coincides with an update interval of the CPU module with the slowest scan time, because the next send/receive starts only after all CPU modules have completed data reception.

Communication method CPU buffer memory Fixed scan communication area

Module-by-module data guarantee enabled

Module-by-module data guarantee disabled

Module-by-module data guarantee enabled

Module-by-module data guarantee disabled

Communication through refresh

Communication through direct access *2

Item Description Setting range Default PLC Unit Data Specify whether data is guaranteed on a module-by-module

basis. Disable Enable

Disable

22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules 385

38

Communication through refresh The device data for each CPU module is written/read only by the parameter settings. Using refresh areas allows data communication between all or a part of the CPU modules in the multiple CPU system, thereby enabling devices of other CPU modules to be used by the host CPU module.

Types of refresh The following table shows the types of refresh.

*1 The fixed scan communication area is refreshed on the cycle specified in the fixed scan communication setting. *2 Refresh fails if the multiple CPU synchronous interrupt program (I45) does not exist on the program.

The following figure shows the timing of each refresh.

Refresh timing Application Memory to be used At the END processing For data communication of devices in synchronization with the scan CPU buffer memory

At the execution of multiple CPU synchronous interrupt program (I45)*1*2

For data communication of devices at the period specified in the fixed scan communication setting

Fixed scan communication area

END END

:

:

:

:

0.888ms 0.888ms 0.888ms 0.888ms

Refresh with the CPU buffer memory (set) Refresh with the CPU buffer memory (read) Refresh with the fixed scan communication area (read) Refresh with the fixed scan communication area (set)

Sequence scan

Program

Multiple CPU communication cycle

Cycle that is set for the multiple CPU communication cycle setting

Time

1 scan1 scan

6 22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules

22

Refresh using CPU buffer memory At the END processing of the host CPU module, device data of the host CPU module is written to the refresh area within the CPU buffer memory on the host CPU module. The data written to the refresh area is transferred to the device of another CPU module at the END processing of another CPU module.

Ex.

When CPU No.1 refreshes 32 points (B0 to B1F) and CPU No.2 refreshes 32 points (B20 to B3F):

Refresh using fixed scan communication areas At the period specified in the fixed scan communication setting, the device data of the host CPU module is written to the refresh area within the fixed scan communication area of the host CPU module. The data written to the refresh area is sent to the refresh area within the fixed scan communication area of another CPU, which in turn reads the transferred data into the device.

Ex.

When CPU No.1 refreshes 32 points (B0 to B1F) and CPU No.2 refreshes 32 points (B20 to B3F):

CPU No.1 CPU No.2

CPU buffer memory CPU buffer memory

Refresh area Refresh area

Write with END processing of CPU No.1 Write with END processing of CPU No.2

Read with END processing of CPU No.2

Read with END processing of CPU No.1

Device B0 to B1F (for CPU No.1)

B20 to B3F (for CPU No.2)

Device B0 to B1F (for CPU No.1)

B20 to B3F (for CPU No.2)

CPU No.1

CPU buffer memory

Fixed scan communication area of CPU No.1

Refresh area

Fixed scan communication area of CPU No.2

Refresh area

The data is written to the refresh area.

B20 to B3F (for CPU No.2)

The data is read from the refresh area.

B0 to B1F (for CPU No.1)

Device

CPU No.2

CPU buffer memory

Fixed scan communication area of CPU No.1

Refresh area

Fixed scan communication area of CPU No.2

Refresh area

The data is written to the refresh area.

B20 to B3F (for CPU No.2)

The data is read from the refresh area.

B0 to B1F (for CPU No.1)

Device

The data is sent to CPU No.2.

The data is sent to CPU No.1.

22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules 387

38

Executing refresh Refresh is executed when the CPU module is in RUN and/or STOP (PAUSE) state. For details on the behavior when the CPU module is in stop error state, refer to CPU module operation upon error detection setting. ( Page 170 CPU module operation upon error detection setting)

Behavior during the multiple CPU synchronous interrupt program (I45) execution If refresh is set to be performed during the multiple CPU synchronous interrupt program (I45) execution, the refresh behavior when the CPU module is in RUN state varies depending on either of the following conditions. ( Page 397 Multiple CPU Synchronous Interrupt) A program (I45 to IRET) which includes the multiple CPU synchronous interrupt program (I45) exists. Event execution type program exists. The following table lists the refresh behaviors. : Execute refresh, : Not execute refresh

*1 The PSCAN/PSTOP instruction changes after the next scan, and the POFF instruction changes after the next two scans. : Execute refresh, : Not execute refresh, : Execution disabled

*2 Not affect to the behavior. *3 Operates with the pre-change parameters. *4 Operates with the post-change parameters.

Configurable data This section lists the configurable data with the refresh settings.

Maximum number of settings Maximum of 32 settings can be configured per CPU module for any refresh setting.

Data number of points Data number of points can be configured within the number of points assigned to the area (within the send range of the fixed scan communication area) in increments of two points. Device duplication between multiple setting numbers is not allowed.

Execution type Refresh behavior Refresh behavior after the program control instruction is executed

STOP state RUN state RUN state Other than event execution type

The I45 interrupt pointer doesn't exist

The I45 interrupt pointer exists

Event execution type (I45 interrupt specified) (stop after changing the execution type*1)

Execution type Refresh behavior triggered by operating status change of the CPU module

RUN state

Upon addition of the I45 interrupt pointer during online program change

Upon removal of the I45 interrupt pointer during online program change

RUN to STOP state

STOP state

After the refresh setting is changed; when parameters are written

STOP to RUN state

Power off to on/ Reset

Other than event execution type

The I45 interrupt pointer doesn't exist

*3

The I45 interrupt pointer exists

*2 *3 *3 *4

Event execution type (I45 interrupt specified)

*2 *3 *3 *4

8 22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules

22

Data that can be specified The device other than local device can be specified. However, when "Use File Register of Each Program" is enabled, file registers cannot be specified. Doing so may prevent the device from operating at file registers for each program depending on the CPU operating status.

*1 This device can be specified only in units of 16 points (one word).

Refresh settings The refresh can be set up with "Refresh Setting between Multiple CPUs" in "CPU Parameter".

[CPU Parameter] [Refresh Setting between Multiple CPUs]

Operating procedure

Set a blank column for "Head" and "End" and set only number of points so that the setting by which auto refresh is not conducted can be configured. (It is possible to perform setting which does not allow the refresh data of other CPU modules, which is unwanted for the host CPU module, to be obtained.)

Enabling timing of refresh settings The refresh settings are enabled at the following timing: When CPU module is powered off and on or is reset.

CPU module operating status and refresh behavior When the refresh timing coincides with the period specified in the fixed scan communication setting, the refresh behavior depends on the operating status of the CPU module.

*1 In the disabling interrupt state by the DI instruction, the refresh is not operational, because the multiple CPU synchronous interrupt program (I45) does not work.

Type Devices that can be specified Bit device*1 X, Y, M, L, B

Word Device D, W, R, ZR, RD

"Refresh Setting between Multiple CPUs" window 1. Click "Detailed Setting" at the execution timing for each refresh.

"Detailed Setting" window 2. Enter the start/end of the device.

CPU module operating status Refresh enabled/disabled Refresh timing

CPU buffer memory Fixed scan communication area

RUN (including a continuation error period)

Execute refresh During the END processing Before and after the multiple CPU synchronous interrupt program (I45) execution*1

STOP (including a stop error period due to a moderate error)

Execute refresh During the END processing During the END processing

STOP (major error period) Not execute refresh

PAUSE Execute refresh During the END processing During the END processing

22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules 389

39

Communication through direct access This method uses programs to communicate with other CPU modules. The following table lists the communications using the direct access method.

Specification method thorough CPU buffer memory access device Specify the CPU buffer memory as "U3En\Gn" or the fixed scan communication area as "U3En\HGn" when accessing the memory or area. ( Page 438 CPU Buffer Memory Access Device)

Obtaining information stored on the CPU buffer memory Access the CPU buffer memory.

Obtaining information stored on the fixed scan communication area for other CPUs Access the fixed scan communication area on the host CPU module. Obtain data sent to the fixed scan communication area on the host CPU module at the fixed scan communication cycle.

Communication method Description Instruction to be used Communication using CPU buffer memory Data between CPU modules are transferred using

any area on the CPU buffer memory. FROM/TO instruction DFROM/DTO instruction Instruction using the CPU buffer memory access

device (U3En\G)

Communication using the fixed scan communication area

Data between CPU modules are transferred using the fixed scan communication area.

Instruction using the CPU buffer memory access device (U3En\HG)

Communication by a dedicated instruction Data between CPU modules in the multiple CPU system are transferred and/or control commands are sent to other CPU modules by using a dedicated instruction.

DDWR/DDRD instruction and others

CPU No.1 CPU No.2 CPU No.3 Host CPU module

U3E0\G0

U3E0\G8000

(U3E1\)*1 G0

U3E0\HG0

U3E0\HG1024

(U3E1\)*1 HG0

U3E2\HG0

U3E2\HG1024

CPU buffer memory

Send area of CPU No.1

Receive area of CPU No.2

Receive area of CPU No.3

Send area of CPU No.2

Receive area of CPU No.1

Receive area of CPU No.3

Receive area of CPU No.1

Receive area of CPU No.2

Send area of CPU No.3Fi

xe d

sc an

c om

m un

ic at

io n

ar ea

Fi xe

d sc

an c

om m

un ic

at io

n ar

ea

Fi xe

d sc

an c

om m

un ic

at io

n ar

ea

Acquire information on other CPU modules.

CPU buffer memory

CPU buffer memoryU3E2\G0

U3E2\G8000

0 22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules

22

Communication using CPU buffer memory and fixed scan communication area This section describes the communication using CPU buffer memory and fixed scan communication area.

Available area for communication The following area can be used for communication.

Instructions to be used for communication Communication with each CPU module is enabled by issuing the following read/write instructions to each area. Write instruction: the instructions using the CPU buffer memory access device*1 and the TO/DTO instruction Read instruction: the instructions using the CPU buffer memory access device*1 and the FROM/DFROM instruction *1 Specify "U3En\G" when accessing the CPU buffer memory and "U3En\HG" when accessing the fixed scan communication area.

Data communication behavior When using an area within the CPU buffer memory Data written to the area within the CPU buffer memory on the host CPU module using the write instruction can be read by other CPU modules using the read instruction. Unlike the refresh, data registered during the instruction execution can be directly read.

Ex.

When data written to the CPU buffer memory on the CPU No.1 using the write instruction is read by CPU No.2 using the read instruction:

Area Description CPU buffer memory All the CPU buffer memory area except for the refresh area is available. The start address of the available area for each CPU

module varies depending on the refresh settings. The end address of the area is fixed by CPU module models.

Fixed scan communication area

All the fixed scan communication area except for the refresh area is available. The start address of the available area for each CPU module is HG0 and the end address varies depending on the refresh settings.

D0 D100

SM400 SM400

1

2

1

2

CPU No.1

CPU buffer memory

Data written using a write instruction

Refresh area

Write using a write instruction

Program

Execution of a write instruction

Read using a read instruction

CPU No.2

Execution of a read instruction

CPU buffer memory

Refresh area

Program

Device Device

Program Program

U3E0\G1000 Send data of CPU No.1

Send program

MOV U3E0\G1000 D100

Receive program

CPU No.1 (programmable controller CPU) CPU No.2 (programmable controller CPU)

MOV D0 U3E0\G1000

22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules 391

39

When using an area within the fixed scan communication area Data written to the area within the fixed scan communication area on the host CPU module using the write instruction is sent to other CPU modules at the period specified in the fixed scan communication setting. Other CPU modules read the received data using the read instruction. Unlike the refresh, data registered during the instruction execution can be directly read.

Ex.

When data written to the fixed scan communication area on the CPU No.1 using the write instruction is read by CPU No.2 using the read instruction:

1

2 3D0

SM400 SM400

D100

1

2

3

CPU No.1 CPU No.2

CPU buffer memory CPU buffer memory

Fixed scan communication area of CPU No.1

Refresh area

Fixed scan communication area of CPU No.2

Execution of a write instruction

Write using a write instruction

The data is transferred at multiple CPU

communication cycle.

The send data is transferred to CPU No.2.

Fixed scan communication area of CPU No.1

Refresh area

Refresh area

Refresh area

Fixed scan communication area of CPU No.2

Program

Read using a read instruction

Execution of a read instruction

Device

Fixed scan communication area

Send data of CPU No.1

U3E0\HG0

Program Send program Program

Send data of CPU No.1

The data is transferred at multiple CPU

communication cycle.

U3E0\HG0 Device

Fixed scan communication area

MOV U3E0\HG0 D100

Receive program

CPU No.1 (programmable controller CPU) CPU No.2 (programmable controller CPU)

Program

MOV D0 U3E0\HG0

2 22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules

22

Data assurance by program This section describes how to avoid the inconsistency of data larger than 64 bits using the program. To set up the module-by- module data guarantee using the parameters, use the multiple CPU setting. ( Page 385 Module-by-module data guarantee)

Data assurance in communication through the refresh Inconsistency of transferred data can be avoided by setting the interlock device to a transfer number lower than the one for the transferred data, because data is transferred in descending order from the highest setting number in the refresh settings.

Ex.

Interlock program in communication by refresh Parameter settings

Program example

CPU No.1 refresh setting Direction CPU No.2 refresh setting

CPU No.

Transfer No.

Send/receive range for each CPU module

Send/receive device setting

CPU No.

Transfer No.

Send/receive range for each CPU module

Send/receive device setting

Number of points

start end start end Number of points

start end start end

CPU No.1

Transfer No.1

2 0 1 M0 M31 CPU No.1

Transfer No.1

2 0 1 M0 M31

Transfer No.2

10 2 11 D0 D9 Transfer No.2

10 2 11 D100 D109

CPU No.2

Transfer No.1

2 0 1 M32 M63 CPU No.2

Transfer No.1

2 0 1 M32 M63

M100 M0 M32

M0

M0

M0

M32

M32M32

SET M0

RST M0

RST M100

RST M32

SET M32

Write instruction

Send program (CPU No.1) Receive program (CPU No.2)

Set send data for D0 to D9.

Operation using receive data (D0 to D9)

22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules 393

39

Data assurance for communication through direct access The behavior varies depending on the area to be accessed.

When accessing CPU buffer memory: The program reads data in ascending order from the start address of the CPU buffer memory other than the refresh area, and the write instruction writes send data in descending order from the end address of the CPU buffer memory other than the refresh area. Therefore data inconsistency can be avoided by setting an interlock device at the start position of data to be communicated.

Ex.

Interlock program in communication by direct access (when accessing CPU buffer memory) Program example

(1) CPU No.1 creates send data. (2) CPU No.1 turns on the data setting complete bit. [Data transfer with CPU No.2 END processing] (3) CPU No.2 detects send data setting complete. (4) CPU No.2 performs receive data processing. (5) CPU No.2 turns on receive data processing complete. [Data transfer with CPU No.1 END processing] (6) CPU No.1 detects receive data processing complete, and turns off the data setting complete bit. [Data transfer with CPU No.2 END processing] (7) CPU No.2 detects that send data setting complete is turned off, and turns off receive data processing complete.

M0

RST G2048.0

SET G2048.0

RST M0

SET G2048.0

RST G2048.0

(1) (4)

(5)

(6) (7)

(2)

(3) Write instruction

Send program (CPU No.1) Receive program (CPU No.2)

Set send data for user setting areas (U3E0\G2049 to U3E0\G2057).

Operation using receive data (U3E0\G2049 to U3E0\G2057)

U3E0\ G2048.0

U3E1\ G2048.0

U3E1\ G2048.0

U3E0\ G2048.0 U3E0\

U3E0\

U3E0\ G2048.0

U3E1\ G2048.0

U3E0\ G2048.0

U3E1\ G2048.0

U3E1\

U3E1\

4 22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules

22

When accessing fixed scan communication area When accessing within the multiple CPU synchronous interrupt program (I45), enabling the setting of module-by-module data guarantee eliminates the need of an interlock circuit. When this refresh area is accessed within a program other than the above, or when the setting of module-by-module data guarantee is disabled, an interlock circuit is required, as with the access to the CPU buffer memory. ( Page 384 Module-by-module data guarantee) The program reads data by transferring it in the order that it is written to the CPU buffer memory (fixed scan communication area). Data inconsistency can be prevented by using devices written after the transfer data for interlocks, regardless of the device type or address.

Ex.

Interlock program in communication by direct access (when accessing fixed scan communication area) Program example

Also, with instructions such as BMOV instructions that involve writing data with two or more words to the CPU buffer memory, data is written from the end address to the start address. If combining and writing send data with interlock signals with a single instruction, data inconsistency can be prevented with an interlock signal at the start of the data.

(1) CPU No.1 creates send data. (2) CPU No.1 turns on the data setting complete bit. [Data transfer with multiple CPU communication cycle] (3) CPU No.2 detects send data setting complete. (4) CPU No.2 performs receive data processing. (5) CPU No.2 turns on receive data processing complete. [Data transfer with multiple CPU communication cycle] (6) CPU No.1 detects receive data processing complete, and turns off the data setting complete bit. [Data transfer with multiple CPU communication cycle] (7) CPU No.2 detects that send data setting complete is turned off, and turns off receive data processing complete.

M0

RST HG10.0

SET HG10.0

RST M0

SET HG0.0

RST HG0.0

(1) (4)

(5)

(6) (7)

(2)

(3) Write instruction

Send program (CPU No.1) Receive program (CPU No.2)

Set send data for user setting areas (U3E0\HG0 to U3E0\HG9).

Operation using receive data (U3E0\HG0 to U3E0\HG9)

U3E0\ HG10.0

U3E1\ HG0.0

U3E1\ HG0.0

U3E0\ HG10.0 U3E0\

U3E0\

U3E0\ HG10.0

U3E1\ HG0.0

U3E0\ HG10.0

U3E1\ HG0.0

U3E1\

U3E1\

22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules 395

39

Communication between CPU modules in error state The following section describes communication between CPU modules in an error state.

Behavior in receive data error state A CPU module receiving illegal data due to noise and/or failure discards the received data. If a received data is discarded, the receive-side CPU module keeps the last data received before discarding. When the CPU module receives the next correct data, it updates the received data.

Refresh execution in an error state The following table lists the refresh and send/receive operation between CPU modules when the host CPU module detects a self diagnostic error. If one of the CPU modules enters into stop error state, the other CPU modules which are not in stop error state keep data stored before the stop error occurs.

*1 This item indicates data transfer between user devices and the fixed scan communication area on the host CPU module. *2 This item indicates data communication between the fixed scan communication areas on the host CPU module and other CPU modules. *3 When an error occurs during normal operation, normal data generated immediately before the error occurs is continued to be sent

between the fixed scan communication areas on the host CPU module and other CPU modules. *4 If the consistency check fails due to a parameter change in normal operation, refresh and data send/receive between the CPU modules

are continued.

Error Refresh*1 Data communication between CPU modules*2

Minor error

Moderate error Causes other than the following item

Parameter error for fixed scan communication function (including the consistency check during start-up)

*3*4 *3*4

Major error *3 *3

6 22 MULTIPLE CPU SYSTEM FUNCTION 22.4 Data Communication Between CPU Modules

22

22.5 Multiple CPU Synchronous Interrupt This function triggers an interrupt program at the fixed scan communication cycle set in a parameter. An interrupt program executed at the fixed scan communication cycle is called a multiple CPU synchronous interrupt program. Using the multiple CPU synchronous interrupt enables synchronizing with the fixed scan communication cycle so that data communication between CPU modules can be made. (It allows synchronizing the data communication timing between CPU modules.)

The operation methods required when an interrupt factor occurs and the program creating methods are the same as those for normal interrupt program. ( Page 99 Interrupt Program)

Data reading of other CPU modules (refresh): Data sent from other CPU modules is read to a device or a label. (Data is read from the receive area of the host CPU module.)

Operation processing: The multiple CPU synchronous interrupt program is executed. Data sending of other CPU modules (refresh): Data to be sent to other CPU modules is written from a device or a label. (Data is written to the send area of

the host CPU module.)

CPU module (CPU No.1)

Multiple CPU synchronous interrupt program

Refresh Operation processing Refresh

PauseNormal program

Multiple CPU synchronous interrupt program

Send data of CPU No.2

Send data of CPU No.1

Receive area of CPU No.1

Read Write

Send area of CPU No.1

CPU module (CPU No.2)

Multiple CPU synchronous interrupt program

Refresh Operation processing Refresh

Execution time of the multiple CPU synchronous interrupt program

PauseNormal program

Multiple CPU synchronous interrupt program

Pause

Multiple CPU synchronous interrupt program

Refresh Operation processing Refresh

Receive area of CPU No.2

Send area of CPU No.2

Read Write

Send data of CPU No.2

Multiple CPU synchronous interrupt program

Refresh Operation processing Refresh

Pause

Fixed scan communication area

Fixed scan communication area

Execution time of the multiple CPU synchronous interrupt program

Fixed scan communication cycle Fixed scan communication cycle

22 MULTIPLE CPU SYSTEM FUNCTION 22.5 Multiple CPU Synchronous Interrupt 397

39

Execution timing The multiple CPU synchronous interrupt program (I45) is executed at the timing for the fixed scan communication cycle. The fixed scan communication cycle can be changed through the fixed scan communication setting. ( Page 383 Fixed scan communication setting)

It is also possible to perform refresh during the multiple CPU synchronous interrupt program (I45) in execution. ( Page 386 Communication through refresh)

Multiple interrupt For the multiple interrupt of the multiple CPU synchronous interrupt program, refer to the multiple interrupt function. ( Page 114 Multiple interrupt function)

Precautions The precautions for the multiple CPU synchronous interrupt program are mentioned below. Create a multiple CPU synchronous interrupt program so that it has the execution processing time shorter than the fixed

scan communication cycle. If the interrupt program has the execution processing time equal to or longer than the cycle, the multiple CPU synchronous interrupt interval cannot be guaranteed. ( Page 100 Operation upon occurrence of an interrupt factor) The execution time of the multiple CPU synchronous interrupt program (I45) can be monitored using the RAS setting of the CPU parameter. ( Page 169 Error detection setting)

To send data successfully in the next fixed scan communication cycle, select "Detect" for "Program Execution Section Exceed (I45)" in "RAS Setting" of [CPU Parameter]. ( Page 169 Error detection setting) With this setting, when data is written with the multiple CPU synchronous interrupt program after the host CPU module starts data transfer, SM484 (Execution section excess error flag for multiple CPU synchronization interrupt program) is turned on and the number of data sending errors in the next cycle is stored in SD484 (Number of execution section excess errors for multiple CPU synchronization interrupt program). In addition, when the data is written while the data cannot be sent in the fixed scan communication cycle set in a parameter, an error can be detected. (The CPU module continues its operation.)

(1) CPU No.1 receives send data (A) of CPU No.2 in the next scan. (2) CPU No.1 receives send data (B) of CPU No.2 after two scans. (3) SM484 turns on and SD484 counts up because CPU No.2 continuously executes its program even after the start of data communication. (4) Send data (A) of CPU No.2 is written. (5) Send data (B) of CPU No.2 is written. (6) This data is sent in the next scan because it has been written before data update. (7) This data is sent after two scans because it has been written after data update.

(7)(6)

(4) (5)

(3)

(1) (2)

Data communication section by system

Send data of CPU No.2

Fixed scan communication cycle

Multiple CPU synchronous interrupt program of the CPU No.1

Multiple CPU synchronous interrupt program of the CPU No.2

Fixed scan communication cycle

8 22 MULTIPLE CPU SYSTEM FUNCTION 22.5 Multiple CPU Synchronous Interrupt

23

23 SECURITY FUNCTION This function serves to protect the user property stored in a personal computer and the user property inside modules in the MELSEC iQ-R series system against threats such as theft, tampering, faulty operation, and unauthorized execution due to the unauthorized access by an outsider. Use an appropriate security function according to the purpose as shown in the following table:

*1 These functions disable the password authentication for a certain duration of time after a certain number of failed authentication attempts. For details, refer to the manuals for each function.

(1) Protection is provided against theft, tampering, and faulty operation resulting from unauthorized access by an outsider. (Protection for user property on a personal computer)

(2) Protection is provided against theft, tampering, faulty operation, and unauthorized execution resulting from unauthorized access by an outsider. (Protection for user property in CPU modules)

Data to be protected Purpose Function Reference GX Works3 Project Prevents unauthorized access to programs (in units

of POU). (A password is used.) Block password function GX Works3 Operating Manual

Prevents unauthorized access to programs (in units of program file). (A security key is used.) Project data locked with a security key can only be viewed with an engineering tool for which the same security key has been registered.

Security key authentication function for a project

CPU module Program Prevents unauthorized execution of programs. (A security key is used.) Programs locked with a security key can only be executed at modules for which the same security key has been set.

Security key authentication function for a CPU module

Page 400 Security key authentication for a CPU module

File Prevents unauthorized read and write of files. (A password is used.)

File password function*1 GX Works3 Operating Manual MELSEC iQ-R Ethernet User's

Manual (Application) SLMP Reference Manual MELSEC iQ-R Serial

Communication Module User's Manual (Application)

Access Blocks access from an invalid IP address by identifying the IP address of an external device via Ethernet.

IP filter function MELSEC iQ-R Ethernet User's Manual (Application)

Restricts access via Ethernet that is taking a different route from specific communication routes. (A password is used.)

Remote password function*1

Device data Protects arbitrary device data from being tampered with. (Writing to devices from engineering tools and GOTs is disabled.)

Write-protect function for device data (from outside the CPU module)

Page 401 Write-Protect Function for Device Data (from Outside the CPU Module)

GX Works3 Operating Manual

GOT

(2)

(1)

User property

User property

Engineering tool

Personal computer

MELSEC iQ-R series system

Internet/ intranet

Personal computer (at another location)

23 SECURITY FUNCTION 399

40

If a personal computer with a security key registered is abused by an outsider, there is no way to prevent the outflow of the program property, and thus the user needs to take adequate measures as shown below: Preventive measures against the theft of a personal computer (for example, wire locking) Management of users of the personal computer (for example, deletion of unnecessary user accounts, strict

control of login information, and implementation of fingerprint authentication) Furthermore, if a personal computer with a security key registered has failed, the locked project data cannot be viewed and edited. We assume no responsibility whatsoever for any damage or loss to the user and any other individual or organization, resulting from such a situation. Therefore, the user needs to take adequate measures as shown below: Import the registered security key to another personal computer. Export the registered security key to a file and store the file in a safe place.

Security key authentication for a CPU module This function prevents an unauthorized execution of programs written in a CPU module. The operations are restricted by detecting a mismatch between the security key of the program file written in a CPU module and the security key of a CPU module.

If the security key of only one program does not match the security key of the CPU module, all the other programs in the CPU module are not executed as well. The security key written in the CPU module is retained even after power-off of the CPU module. For details, refer to the following. GX Works3 Operating Manual

Program file

Key A

No key, or key B

Program execution

Key A

Program executionKey A

Program file

0 23 SECURITY FUNCTION

23

23.1 Write-Protect Function for Device Data (from Outside the CPU Module)

This function disables writing to devices from engineering tools and GOTs. Protected devices and their ranges can be set by the user. Therefore, desired device data can be protected from tampering. Even when the write-protect range is set, the operation of the set CPU module and device data writing by the execution of functions (internal device data writing such as device data writing by instructions) are not disabled.

This function applies to a global label to which a device is assigned. Therefore, when a device assigned to a global label is protected from writing, write processing cannot be performed.

When using the write-protect function for device data (from outside the CPU module), check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

: Can be written, : Cannot be written

M0, D0: M200, D10000:

M0: M200:

D0: D10000:

D0: D10000:

M

D

M0

M200 D0

D10000 M0, D0: M200, D10000:

M0, D0: D10000:

Writing device data from an external device

Internal operations by using instructions Setting of initial device values Link refresh

Writing device data from the engineering tool

Writing device data from GOT

Simple PLC communication function (writing data to a destination device)

Writing device data by using network dedicated module dedicated instructions

Boot operation: CPU module data backup/restoration function:

Device memory

: Writing enabled : Writing disabled

23 SECURITY FUNCTION 23.1 Write-Protect Function for Device Data (from Outside the CPU Module) 401

40

Setting method Set the write-protect range in "Device Setting" of the CPU parameter.

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Detailed Setting] [Device Setting] [Detailed Setting]

Window

*1 The device assignment method can be changed to "Points/Start" by right-clicking in the setting window and selecting "Setting Method".

Target devices The following table lists the devices to which write-protect ranges can be set with this function. Note that the following devices includes the digit-specified bit devices and the bit-specified word devices.

*1 X and Y that are accessed in direct mode (DX and DY) are also included. *2 Specify the write-protect range for the file register in ZR.

(1) One range can be set per device by specifying "Start" and "End".* 1

Type Device User device Bit X*1, Y*1, M, B, F, SB, V, S, L

Bit/word T, ST, C

Bit/double word LT, LST, LC

Word D, W, SW

File register Word R*2, ZR

(1)

2 23 SECURITY FUNCTION 23.1 Write-Protect Function for Device Data (from Outside the CPU Module)

23

Operations and functions The following table lists the operations and functions that cannot be executed for devices in the write-protect range.

*1 This function cannot be executed when the device memory clear is specified. *2 When this function is enabled, the files cannot be written. *3 The file register file and initial device value file cannot be written or changed. *4 In "Account Settings" of "Web Server Settings", set "Write Device" to "Enable".

Operation using SLMP Device write processing is disabled when the write-protect range is set in the device write using SLMP. In addition, device write processing is disabled when the following commands are executed in the operations such as the predefined protocol support function, SLMP frame send instruction, or access from an external device.

*1 Device write processing is disabled only when a device is assigned to a label. *2 Device write processing is disabled only when the device memory clear is specified.

Write processing is disabled when a file write using SLMP is performed to the device initial value file and file register file. In addition, write processing is disabled when the following commands are executed in the operations such as the SLMP frame send instruction or access from an external device.

*3 Write processing is disabled only when the open mode is for writing (0100H).

Operation and function Operation from the engineering tool Current value change in the watch window

Remote operation Remote RUN*1

CPU memory operation Device/label memory value clear Device/label zero clear

File register zero clear

Device/label/file register latch clear

Writing data to the programmable controller

Device memory

Device initial value*2

File register

Operation using a GOT Device write

File write

Operation using SLMP Device write using SLMP

File write/change using SLMP*3

Operation using FTP File write using the file transfer function (FTP server)*3

Operation using instructions Device write from another CPU module

Device write from the programmable controller of another station

Remote RUN at device memory clear specification from the programmable controller of another station

Other operations Device write using the simple CPU communication function

Predefined protocol support function

Device test using the Web server function*4

Type Operation Command Subcommand Device Write 1401 000, 001

002, 003

Write Random 1402 000, 001

002, 003

Write Block 1406 000

002

Label Array Label Write 141A*1 0000

Label Write Random 141B*1 0000

Remote Control Remote Run 1001*2 0000

Remote Latch Clear 1005 0000

Type Operation Command Subcommand File New File 1820 0000, 0040

Copy File 1824 0000, 0004, 0040

Open File 1827*3 0000, 0004, 0040

Write File 1829 0000

23 SECURITY FUNCTION 23.1 Write-Protect Function for Device Data (from Outside the CPU Module) 403

40

Operation using the file transfer function (FTP server) Write processing is disabled when a file write using the file transfer function (FTP server) is performed to the initial device value file and the file register file.

*1 Write processing is disabled when the file extension is changed to DID or QDR. *2 Write processing is disabled only when the device clear is specified.

Operation using instructions Write processing is disabled when the device write is performed by a multiple CPU dedicated instruction or a module dedicated instruction (including a device clear instruction (dedicated instruction)) to devices in the write-protect range.

*1 Writing to notification devices is also disabled. *2 Write processing is disabled only when the device clear is specified.

Precautions When this function is enabled, a device write operation with indirect specification cannot be performed. Perform a device

write operation with normal device specification. (Do not use indirect specification.) When this function is enabled and writing to the file register is disabled, perform a device write operation specifying the ZR

device. If the R device is specified, a device write operation may not be disabled. When this function is enabled, a device write operation with index modification cannot be performed when the write-protect

range is set in the accessible area. When the write-protect range exists in the accessible area, perform a device write operation with normal device specification. (Do not use index modification.)

When this function is enabled, CPU parameters that disables the function and the device memory where values are set to the write-protect device in the CPU module cannot be written to the programmable controller at the same time. Write CPU parameters to disable the function, and then write the device memory where the values are set to the programmable controller.

Function Command Subcommand Writing to file put

mput

File name change rename*1

FTP server subcommand send (RUN operation) quote*2 run

Major classification Classification Instruction name Writing device data from another station

Module dedicated instruction Writing data to the programmable controller on another station

JP.WRITE, GP.WRITE

Writing data to the programmable controller on another station (with notification)*1

JP.SWRITE, GP.SWRITE

Reading data from the programmable controller on another station (with notification)*1

JP.SREAD, GP.SREAD

Writing data to the target station J(P).RIWT, G(P).RIWT

Writing device data from another CPU module

Multiple CPU dedicated instruction Writing device data to another CPU module

D(P).DDWR, M(P).DDWR

Clearing device data another station Module dedicated instruction Remote RUN*2 J(P).RRUN, G(P).RRUN, Z(P).RRUN, J(P).REQ, G(P).REQ

4 23 SECURITY FUNCTION 23.1 Write-Protect Function for Device Data (from Outside the CPU Module)

24

24 SEQUENCE SCAN SYNCHRONIZATION SAMPLING FUNCTION

This function allows a module to collect data of the CPU module in synchronization with the sequence scan of the CPU module. This function is available to the following modules: MES interface module (high-speed access) High speed data logger module (high-speed collection) C intelligent function module (data sampling in sequence scan) High speed data communication module (high-speed collection) The following table lists the number of modules that can execute this function on a single CPU module and the total number of collectable points.

For details on the function using the sequence scan synchronization sampling function and collectable data for each module, refer to the manual for the module used.

Precautions Use points in 8K-point increments to use all of the total number of points that can be collected. The points are assigned in 8K-point increments as follows: 6K points used 8K points to be assigned 9K points used 16K points to be assigned

Item R00CPU, R01CPU, R02CPU Other CPU module Number of executable modules Two Four

Total number of collectable points 16K points 32K points

24 SEQUENCE SCAN SYNCHRONIZATION SAMPLING FUNCTION 405

40

MEMO

6 24 SEQUENCE SCAN SYNCHRONIZATION SAMPLING FUNCTION

25

25 ROUTING SETTING The user can configure any communication route to perform transient transmission to stations in a different network. This setting can be used when the system has a network module which does not support dynamic routing or when it is necessary to clearly specify a communication route.

25.1 Setting Method The user must specify the following: The network number and the station number of the own network (relay station) which will be pass through to another network, and the network number of the final arrival network (destination station). The maximum 238 routing settings can be specified.

[CPU Parameter] [Routing Setting]

Window

Displayed items

The S(P).RTWRITE instruction can be used to temporarily change or add a routing setting during operation (setting made by the S(P).RTWRITE instruction is cleared when the CPU module is powered off or reset). Also, the S(P).RTREAD instruction can be used to read setting details of the parameters. For details on these instructions, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

Item Description Setting range

Default

Relay Station Network Number Sets the network number of the first relay station to pass through to the destination station.

1 to 239

Station No. Sets the station number of the first relay station to pass through to the destination station.

0 to 120

Target Station Network Number Sets the network number of the final arrival network. 1 to 239

Relay station

Network No. Station No.

Destination station

Network No.

Own station Other station

Network No. Network No.

Station No.

Relay station

25 ROUTING SETTING 25.1 Setting Method 407

40

25.2 Setting Example The following is an example of the routing setting.

Ex.

Transient transmission from the request source (Network No.1) to the target (Network No.3) via Network No.2.

25.3 Precautions The precautions on the routing setting are as follows: For the multiple CPU system configuration, the same routing setting must be used for all CPUs.

(1) Network No.: 1 Station No.0

(2) Network No.: 1 Station No.3

(3) Network No.: 2 Station No.0

(4) Network No.: 2 Station No.6

(5) Network No.: 3 Station No.7

Network No.1 Network No.2 Network No.3

Station

Request source

Relay station 1

Relay station 2

Destination station

(1)

(2)

(3)

(4)

(5)

(6)

(1)

Request route Response route

(2)

(3)

(4)

(5)

Relay station Destination station

Network No. Station No. Network No.

1 3 3

The data is transferred to the relay station (2) of the own network to go to the network No.3.

Destination stationRelay station Network No. Station No. Network No.

2 6 3

The data is transferred to the relay station (4) of the own network to go to the network No.3.

The data has been transferred to the network No.3, and is to be transferred to (6).

The data has been transferred to the network No.1, and is to be transferred to (1).

Relay station Destination station

Network No. Station No. Network No.

2 0 1

The data is transferred to the relay station (3) of the own network to go to the network No.1.

Destination stationRelay station Network No. Station No. Network No.

3 7 1

The data is transferred to the relay station (5) of the own network to go to the network No.1.

Request source Destination stationRelay station 2Relay station 1

(6) Network No.: 3 Station No.0

8 25 ROUTING SETTING 25.2 Setting Example

26

26 FIRMWARE UPDATE FUNCTION This function enables users to update the firmware versions of modules by using firmware update files. (For the firmware update file, please consult your local Mitsubishi representative.) The following two methods for updating firmware are available.

For the module models that support this function, precautions that are common to those modules, and update procedure, refer to the following. MELSEC iQ-R Module Configuration Manual

Before using the firmware update function, check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

Update method Description Update using the engineering tool Firmware versions of multiple modules can be changed at a time by using the engineering tool.

Update using an SD memory card The firmware version of a module can be changed just using an SD memory card. Dedicated software is not required.

26 FIRMWARE UPDATE FUNCTION 409

41

Precautions This section describes the precautions for the CPU module when using the firmware update function.

Incompatible firmware and CPU modules The following table shows incompatible combinations of firmware and CPU modules.

*1 A module whose first and second digits from the left of the production information are "43" or later

When the RnENCPU is updated To update the firmware version from "49" (CPU part)/"46" (network part) or earlier to "54" (CPU part)/"52" (network part) or later, follow the procedure below. Update using the engineering tool

1. First update the firmware version of the CPU part alone to "54" or later.

2. Then, update the firmware version of the network part to "52" or later. (Updating the CPU part and the network part simultaneously generates an error. Always update the CPU part before updating the network part.)

Update using an SD memory card

1. First update the firmware version to "54" (CPU part)/"50" (network part).

2. Update the firmware version to the desired one.

CPU module 3rd and 4th digits from left of production information

Incompatible firmware version

R04CPU "18" or later "33" or earlier

"19" or later "47" or earlier

R08CPU "19" or later "33" or earlier

"20" or later "47" or earlier

R16CPU "19" or later "33" or earlier

"20" or later "47" or earlier

R32CPU "16" or later "33" or earlier

"17" or later "47" or earlier

R120CPU "16" or later "33" or earlier

"17" or later "47" or earlier

CPU module 3rd and 4th digits from left of production information

Incompatible firmware version

CPU part Network part R04ENCPU "32" or later "47" or earlier

"37"*1, "38" or later "51" or earlier

R08ENCPU "30" or later

"35"*1, "36" or later "51" or earlier

R16ENCPU "27" or later

"32"*1, "33" or later "51" or earlier

R32ENCPU "30" or later

"33"*1, "34" or later "51" or earlier

R120ENCPU "22" or later

"25"*1, "26" or later "51" or earlier

0 26 FIRMWARE UPDATE FUNCTION

PA R

T 7

PART 7 DEVICES, LABELS, AND CONSTANTS

This part consists of the following chapters.

27 DEVICES

28 LABELS

29 LATCH FUNCTION

30 DEVICE/LABEL INITIAL VALUE SETTINGS

31 CONSTANTS

411

41

27 DEVICES This chapter describes the devices.

27.1 Device List This section lists the devices.

Classification Type Device name Symbol Number of points of Default

Parameter-set range Notation

User device Bit Input X 12K points*5 Unchangeable Hexadecimal

Bit Output Y 12K points*5 Hexadecimal

Bit Internal relay M 12K points*5 Changeable ( Page 414 Device Setting)

Decimal

Bit Link relay B 8K points Hexadecimal

Bit Annunciator F 2K points Decimal

Bit Link special relay SB 2K points Hexadecimal

Bit Edge relay V 2K points Decimal

Bit Step relay*3 S 0 points Decimal

Bit/word Timer T 1K points*5 Decimal

Bit/word Retentive timer ST 0 points Decimal

Bit/double word Long timer LT 1K points*5 Decimal

Bit/double word Long retentive timer LST 0 points Decimal

Bit/word Counter C 512 points*5 Decimal

Bit/double word Long counter LC 512 points*5 Decimal

Word Data register D 18K points*5 Decimal

Word Link register W 8K points Hexadecimal

Word Link special register SW 2K points Hexadecimal

Bit Latch relay L 8K points Decimal

System Device Bit Function input FX 16 points Unchangeable Hexadecimal

Bit Function output FY 16 points Hexadecimal

Word Function register FD 5 points 4 words Decimal

Bit Special relay SM 4K points Decimal

Word Special register SD 4K points Decimal

Link Direct Device Bit Link input Jn\X 160K points (Max.)*1*6 Unchangeable Hexadecimal

Bit Link output Jn\Y 160K points (Max.)*1*6 Hexadecimal

Bit Link relay Jn\B 640K points (Max.)*1*6 Hexadecimal

Bit Link special relay Jn\SB 5120 points (Max.)*1*6 Hexadecimal

Word Link register Jn\W 2560K points (Max.)*1*6 Hexadecimal

Word Link special register Jn\SW 5120 points (Max.)*1*6 Hexadecimal

Module access device

Word Module access device Un\G 268435456 points (Max.)*1 Unchangeable Decimal

CPU buffer memory access device

Word CPU buffer memory access device

U3En\G 268435456 points (Max.)*1 Unchangeable Decimal

U3En\HG 12288 points maximum Changeable Decimal

Index register Word Index register Z 20 points Changeable ( Page 440 Index register setting)

Decimal

Double word Long index register LZ 2 points Decimal

File register Word File register R/ZR 0 points Changeable Decimal

Refresh data register

Word Refresh data register RD 512K points Changeable Decimal

Nesting Nesting N 15 points Unchangeable Decimal

Pointer Pointer P 8192 points*2 Changeable ( Page 449 Pointer setting)

Decimal

Interrupt pointer I 1024 points Unchangeable Decimal

2 27 DEVICES 27.1 Device List

27

*1 These are the maximum points that can be handled in the CPU module. The number of points actually used differs depending on the

module used. *2 The default number of points is 16384 for the R120CPU and R120ENCPU. *3 The device can be collected by using the CPU module where the SFC function can be used. ( Page 700 Added and Enhanced

Functions) *4 Can be used as a device comment in the SFC program. *5 The default number of points for the R00CPU, R01CPU, and R02CPU are as follows.

Input (X), Output (Y), Internal relay (M): 8K points Timer (T): 2K points Long timer (LT), Long counter (LC): 0 point Counter (C): 1K points Data register (D): 12K points SFC block device (BL): 128 points

*6 The maximum number of points differs depending on the "Link Direct Device Setting" of the engineering tool. Before using the "Link Direct Device Setting", check the version of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

Other devices Network No. specification device

J Unchangeable Decimal

I/O No. specification device

U Hexadecimal

SFC block device*3 BL 320 points*5 Decimal

SFC transition device*3*4 TR 0 points Decimal

Classification Type Device name Symbol Number of points of Default

Parameter-set range Notation

27 DEVICES 27.1 Device List 413

41

27.2 Device Setting The number of points of each user device can be changed ( Page 416 User Device)

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Detailed Setting] [Device Setting] [Detail Setting]

Window

Specify each item so that the total number of points for each user device does not exceed the capacity of the device area. ( Page 127 Device/label memory area setting)

(1) The capacity of each area can be changed. ( Page 127 Device/label memory area setting) (2) The number of points of user devices can be changed.

(1)

(2)

4 27 DEVICES 27.2 Device Setting

27

Range of use of device points The following table lists the range of use of device points to be set in the device setting.

*1 This is the maximum number of points for the R120CPU with an extended SRAM cassette (16MB) (NZ2MC-16MBS). The number of points varies depending on the model of the CPU module used, whether to use an extended SRAM cassette, and the type of its cassette.

*2 The CPU module where the SFC function can be used supports this device. ( Page 700 Added and Enhanced Functions)

Type Device name Symbol Range of use*1 Increment of setting Bit Input X X0 to X2FFF

Bit Output Y Y0 to Y2FFF

Bit Internal relay M M0 to M161882111 64 points

Bit Link relay B B0 to B9A61FFF 64 points

Bit Annunciator F F0 to F32767 64 points

Bit Link special relay SB SB0 to SB9A61FFF 64 points

Bit Edge relay V V0 to V32767 64 points

Bit Step relay*2 S S0 to S16383 1024 points

Word Timer T T0 to T8993439 32 points

Word Retentive timer ST ST0 to ST8993439 32 points

Word Long timer LT LT0 to LT2529407 1 points

Word Long retentive timer LST LST0 to LST2529407 1 points

Word Counter C C0 to C8993439 32 points

Word Long counter LC LC0 to LC4761215 32 points

Word Data register D D0 to D10117631 4 points

Word Link register W W0 to W9A61FF 4 points

Word Link special register SW SW to SW9A61FF 4 points

Bit Latch relay L L0 to L32767 64 points

27 DEVICES 27.2 Device Setting 415

41

27.3 User Device This chapter describes the user device.

Input (X) This device provides the CPU module with commands and/or data using an external device, such as pushbutton, transfer switch, limit switch, and digital switch.

Concept of input Assume that one virtual relay Xn is incorporated into the CPU module for each input point. In the program, a normally open contact and normally closed contact for the Xn are used.

Also, the input can be used as a target re-flesh (CPU module side) device of the remote input (RX), such as the CC-Link IE Field Network.

Output (Y) This device outputs the control results of the program to various devices, such as external signal light/digital HMI/ electromagnetic switch (contactor)/solenoid.

1 2 3

0 1 2 3 4 5

7 8 9 A B C

E D

F

6

0 1 2 3 4 5

7 8 9 A B C

E D

F

6

Push-button switch

Selector switch

Digital switch

Input (X)

CPU module

PB2

PB1

X0 X0

X1

X0F

X1

XF

PB16

~

Input circuit (external device) Program

Programmable controller

Virtual relay

CPU module

Output (Y)

Signal light

Digital indicator

Contactor

6 27 DEVICES 27.3 User Device

27

Internal relay (M) This device is used as an auxiliary relay within the CPU module. The following operations turn off all the internal relays. Turning power of the CPU module off and on Reset Latch clear

Latch relay (L) This device is an auxiliary relay which enables latching (data retention during power failure). This device is used within the CPU module. This device latches operation results (ON/OFF information) even after the following operations. Turning power of the CPU module off and on Reset

Link relay (B) This device is used as a CPU side device when refreshing bit data between the network module, such as the CC-Link IE Controller Network module and the CPU module.

Refreshing network modules using link relay Data are transferred/received between the link relay (B) within the CPU module and the link relay (LB) of the network module, such as the CC-Link IE Controller Network module. The refresh range is specified using parameters on the network module. The part which is not used for refreshing can be used for other applications.

Annunciator (F) This device is an internal relay used for a customer-created program which detects malfunction/failure of the equipment. When the annunciators are turned on, SM62 (Annunciator) is turned on, the number of activated annunciators and their device numbers are stored in SD62 (Annunciator number) to SD79 (Table of detected annunciator numbers).

Ex.

Failure detection program

Also the number of the annunciator turned on first (the number stored in SD62) is registered in the event history.

Only one annunciator number is registered in the event history while power is turned on.

(1) Outputs the annunciator number of the annunciator that turned on. (2) ON detection of the annunciator

SD62BCDP SM62

SET F5

K4Y20

X0 X10 SM62

SD62 SD63 SD64 SD65

SD79

0

0

OFF ON

0 5 0 1 0 5

(1)

(2)

27 DEVICES 27.3 User Device 417

41

On/off method for annunciator Annunciators are turned on by either the SET Finstruction or the OUT F instruction. Annunciators are turned off by the RST Finstruction or the LEDR instruction or the BKRST instruction.

When the annunciators are turned on/off using any methods (e.g. the MOV instruction) other than shown above, the operation is the same as that of internal relays. As a result, SM62 is not turned on and annunciator numbers are not stored into SD62 and SD64 (Table of detected annunciator numbers) to SD79.

Operations when annunciators are turned on 1. The annunciator numbers turned on are stored sequentially into SD64 to SD79.

2. The annunciator number stored into SD64 is stored into SD62.

3. SD63 value (Number of annunciators) is incremented by one.

Operations when annunciators are turned off 1. The number of the annunciator deactivated is removed, and the numbers of annunciators, which were lined up behind

the removed one, move forward one by one.

2. When the annunciator number stored into SD64 is turned off, the annunciator number newly stored into SD64 is stored into SD62.

3. The value of SD63 is decremented by one. When the SD63 value gets decremented to 0, SM62 is turned off.

0

0

0

0

0

0

0

SD62

SD63

SD64

SD65

SD66

SD67

SD79

50

1

50

0

0

0

0

50

2

50

25

0

0

0

50

3

50

25

1023

0

0

SET F50 SET F25 SET F1023

50

2

50

1023

0

0

0

RST F25

8 27 DEVICES 27.3 User Device

27

If more than 16 annunciators are turned on, the 17th annunciator onwards are not stored into SD64 to SD79. However, if the numbers of annunciators registered in SD64 to SD79 are turned off, the lowest numbers, which are not registered in SD62 to SD79, of the numbers of annunciators which were turned on for the 17th on and after, are stored into SD64 to SD79.

(1) Annunciators have been stored for the maximum number (16). (2) Because annunciators have been stored for the maximum number, the value does not change. (3) The smallest number is stored. (4) Turn on the 17th device. (5) Turn on the 18th device. (6) Turn off the first device.

Link special relay (SB) The communication status and error detection status of network modules, such as the CC-Link IE Controller Network module, are output to the link special relay (J\SB) on the network. The link special relay (SB) is a device for using as a refreshing target of link special relays in the network. The part which is not used for refreshing can be used for other applications.

(1) The network status is checked.

SET F100

SD62 10

10 11

25 25 25 50

16 10

10 11

16 10

10 11

16 11

11 12

16SD63 SD64 SD65

SD62 SD63 SD64 SD65

SD62 SD63 SD64 SD65

SD62 SD63 SD64 SD65

SD79

~ ~ ~ ~ ~ ~ ~ ~

SD79 SD79 SD79

SET F50 RST F10

(2)(1)

(4) (5) (6)

(3)

SB0065

SB65

SB0065

SB SB

(1)

Refresh Set the own station link status.

CC-Link IE Controller Network module

Program

Used in a program.

CPU module

27 DEVICES 27.3 User Device 419

42

Edge relay (V) The edge relay is a device that memorizes operation results (on/off information) from the head of the ladder block, allowing its use only by the EGP/EGF instruction. This device is executed for various objectives such as the rising (off and on) detection in the structured programs by the index modification.

*1 Edge relay V0Z1 memorizes on/off information of X0Z1.

Step relay (S) This device is used when specifying SFC program steps. This device is also used when specifying step No. through such methods as verifying (monitor, current value changes) SFC programs with SFC control instructions or the engineering tool. ( MELSEC iQ-R Programming Manual (Program Design))

This device is designed only for SFC programs, and cannot be used as a substitute for an internal relay in a sequence program. If it is used, an error may occur, causing a system failure.

(1) When X1 is rising, this device is turned on for one scan duration.

SM400

X0Z1 V0Z1

SM400

*1 *1

MOV K0 Z1

FOR K10

M0Z1

INC Z1

NEXT Return to the FOR instruction.

Clear the index register (Z1).

Specify the number of repeats (10 times).

Turn on M0Z1 for 1 scan by the rise of X0Z1.

Increment (+1) of the index register (Z1)

X0

M0

V0

X1

M1

V1

OFF

OFF

OFF

OFF

OFF

OFF

ON

ON

ON

ON

ON

ON

(1)

Z1 = 0

Z1 = 1

1 scan

1 scan

0 27 DEVICES 27.3 User Device

27

Timer This device starts measurement when the timer coil is turned on. When the current value reaches a setting value, time is up and the contact is turned on. This timer is an up-timing type device and therefore the current value matches a setting value when the timer time is up.

Types of timers There are two types of timers: timer (T) which retains the current value in 16-bit units and long timer (LT) which retains it in 32- bit units. The timer (T) and the long timer (LT) are different devices and the number of device points can be set for each of them. In addition, there are the retentive timer (ST) and the long retentive timer (LST), both of which retain the current value even if the coil is turned off.* 1

*1 For the timer (T)/long timer (LT), the current value returns to 0 when the coil is turned off.

Timer (T) This device starts measurement when the coil of the timer is turned on. When the timer current value matches a setting value, time is up and the timer contact is turned on. When the timer coil is turned off, the current value returns to 0 and the timer contact is turned off.

Long timer (LT) This device can count from 0 to 4294967295 to measure the time. If the measuring unit is set to 0.01ms, the measurable time range of this device is from 0 to about 11.9 hours. The current value of the long timers is updated by adding a difference of the counter which is used in the system when the OUT LT instruction is executed. Proper time can be measured even when the coil instruction of the long timer cannot be executed once per scanning because the counters used in the system count asynchronously with scanning. When the long timer coil is turned on, measurement starts and when the long timer current value matches a setting value, time is up and the long timer contact is turned on. When the long timer coil is turned off, the current value returns to 0 and the long timer contact is turned off.

*1 This figure shows the example when the long timer time limit value setting is 0.01ms.

For the long timer contact to be turned on after the long timer coil is turned on, the next coil must be executed after the long timer coil turned off and on. The long timer contact is not turned on simultaneously when the long timer coil is off and on.

The long timer (LT) can be used in interrupt programs. ( Page 99 Interrupt Program)

Types of timers Timer Current value = 16 bits Timer (T) Low-speed timer

High-speed timer

Retentive timer (ST) Low-speed retentive timer

High-speed retentive timer

Current value = 32 bits Long timer (LT)

Long retentive timer (LST)

X0 X0 OFF

OFF

OFF

ON

ON

ON

K10

T0

T0

Y10

Coil of T0 (1))

1 second

Contact of T0 (2))

1)

2)

1ms

X0 X0 OFF

OFF

OFF

ON

ON

ON

K100

LT0

LT0

Y10

Coil of LT0 (1))

Contact of LT0 (2))

1)

2)

27 DEVICES 27.3 User Device 421

42

Retentive timer (ST) This device counts the sum of time duration in which the coil is turned on. When the retentive timer coil is turned on, measurement starts and when the timer current value matches a setting value (when time is up), the retentive timer contact is turned on. The current value and the contact on/off state is retained even when the retentive timer coil is turned off. When the coil is turned on again, measurement starts with the retained current value. To clear the retentive timer current value and turn off the contact, issue the RST ST instruction.

Long retentive timer (LST) This device counts the sum of time duration in which the coil is turned on. When the long retentive timer coil is turned on, measurement starts and when the timer current value matches a setting value (when time is up), the contact is turned on. The current value and the contact on/off state is retained even when the long retentive timer coil is turned off. When the coil is turned on again, measurement starts with the retained current value. To clear the long retentive timer current value and turn off the contact, issue the RST LST instruction.

The long retentive timer (LST) can be used in interrupt programs. ( Page 99 Interrupt Program)

Low-speed/high-speed timer (T/ST) The low-speed timer and high-speed timer are the same device which is set to a low speed or high speed timer by writing the instruction accordingly to specify it on the timer. For example, specifying OUT T0 generates a low-speed timer and specifying OUTH T0 produces a high-speed timer even when using the same T0 device. This also applies to the retentive timer.

(1) Even though the coil (1)) turns off, the current value is held. (2) Even though the coil (1)) turns off, the contact remains on.

(1) Even though the coil turns off, the current value is held. (2) Even though the coil turns off, the contact remains on.

0 01 150 150 151 199 200

X0

X0

X1

K200

ST0

ST0

ST0

Y10

RST

OFF

OFF

OFF

ON

ON

(1)

(2)

1)

3)

2)

Instruction execution RST ST0 instruction (3))

Contact of ST0 (2))

Current value of ST0

Coil of ST0 (1))

15 seconds 5 seconds

0 1 150 150 151 199 200 0

ON

ON

OFFX0

OFF

OFF

1.5ms 0.5ms

(2)

(1)

Coil of LST0

Current value of LST0

Contact of LST0

RST LST0 instruction

Instruction execution

2 27 DEVICES 27.3 User Device

27

Timer time limit value Although the low-speed timer and high-speed timer are the same device, timer limit value are different depending on how to specify the timer device (how to write the instruction). For example, specifying OUT T0 generates a low-speed timer and specifying OUT H T0 produces a high-speed timer even when using the same T0 device. This also applies to the retentive timer. The long timer cannot be set to a low-speed or high speed device. The time limit value for each timer is set in "Timer Limit Setting".

Timer limit setting The following window is to set the timer time limit values.

[CPU Parameter] [Operation Related Setting] [Timer Limit Setting]

Window

Displayed items

Timer current value and the measurable range This sections describes the timer current value and the measurable range.

Timer (T/ST) The current value range is 0 to 32767. The measurable time range is from 0 to (timer time limit value 32767).

Long timer (LT/LST) The setting range of the current value is 0 to 4294967295, which is the same as the range of unsigned 32-bit integers. The measurable time range is from long timer time limit value to (timer time limit value 4294967295).

Handling timers When executing the timer coil (the OUT T instruction), the timer coil is turned on/off, the current value is updated, and the contact is turned on/off.

Item Description Setting range Default Low Speed Timer/Low Speed Retentive Timer

Set the timer time limit value of T and ST used for the low-speed timer and low-speed retentive timer.

1 to 1000ms (unit: 1ms) 100ms

High Speed Timer/High Speed Retentive Timer

Set the timer time limit value of T and ST used for the high-speed timer and high-speed retentive timer.

0.01 to 100ms (unit: 0.01ms) 10.00ms

Long timer/Long retentive timer Set the timer time limit value of LT and LST used for the long timer and long retentive timer.

0.001 to 1000ms (unit: 0.001ms) 0.001ms

27 DEVICES 27.3 User Device 423

42

Accuracy of timers This sections describes the accuracy of timers.

Timer (T/ST) The scan time value measured by the END instruction is added to the current value when the OUT T instruction is executed. If the timer coil is turned off when the OUT T instruction is executed, the current value is not updated. The maximum response accuracy of the timer (the time duration from capture of an input (X) to output of it) is "2 scan time + timer time limit setting".

Ex.

Timer limit setting = 10ms, setting value of T0 = 8 (10ms 8 = 80ms), scan time = 25ms

(1) 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) (2) Timing on when the coil of the timer turns on (3) Input fetching timing

X0 T0

K8

21 1 1 2 1 1 2 212

ON OFF

OFF

OFF

ON

ON

OFF ON

3 2 3 3

2 3 2 3 2 3

25ms 25ms 25ms 25ms 25ms 25ms

0+2=2 2+3=5 5+2=7 7+3=10

(1)

(2)

(3)

Program

External input of X0

X0 of the CPU module

Coil of T0

Contact of T0

Scan time

Measurement at 10ms interval

Count by the END instruction

Current value of T0

END processing

END processing

END processing

END processing

END processing

END processing

4 27 DEVICES 27.3 User Device

27

Long timer (LT/LST) In the following program, the accuracy of Tp (the time duration from the long timer coil activation to long timer contact activation) is (Ts-Tu) Tp < (Ts + Tu).

(1) Cp is updated. (2) LT0 is initialized to 0. (3) The result of (Ct - Cp) is added.: 0 + (12 - 10) = 2 (4) The result of (Ct - Cp) is added.: 2 + (13 - 12) = 3 (5) The result of (Ct - Cp) is added.: 3 + (15 - 13) = 5 Tp: time duration from the long timer coil activation to long timer contact activation Ts: setting value of the long timer Tu: time limit value of the long timer

M1

M0 K5

LT0

LT0

ON

ON

10 11 12 13 14

10 12

0 2

15

13

3

15

5

ON

ON

16 17

(1)

(2) (3) (4) (5)

(1) (1)

M0

LT0 (coil)

LT0 (contact)

M1

Previous count value of LT0 (Cp)

Current value of LT0

Counter used in system (Ct)

LT0 coil Execution of (OUT LT0 instruction) M1 coil Execution of (OUT M1 instruction)

Process value of LT0 (Tp)

27 DEVICES 27.3 User Device 425

42

Data configuration of long timer (LT/LST) The long timer (LT) and the long retentive timer (LST) use four words (64 bits) for each point. If the most significant two words are changed in a program, it is impossible to measure the time properly, because they are used by the system.

The current value of the long timer (LT) and the long retentive timer (LST) is 32-bit data. It can be specified by the instructions which can specify signed or unsigned 32 bit data. (It cannot be specified with the BK + Instruction.)

Precautions This section describes the precautions when using the timer and long timer.

Precautions about timer usage Do not describe more than one coil (the OUT T instruction) on the same timer during a single scanning. Doing so results

in improper measurement because the timer current value is updated when the coil for each timer is executed. When timer is not used for data collection for each scan: While the coil on a timer (e.g. T1) is turned on, the timer coil (the

OUT T instruction) cannot be skipped by the instructions such as the CJ. When the timer coil is skipped, proper measurement is impossible because the timer current value is not updated. In addition, when the timer exists in a subroutine program, be sure to execute a subroutine call including T1 coil only once for each scanning operation while the coil of the timer (e.g. T1) is turned on. Otherwise proper measurement is impossible.

The timer cannot be used in the initial execution type program, the fixed scan execution type program, or the event execution type program where the occurrence of an interrupt is set to be a trigger. The timer can be used in standby type programs if the coil of timer (OUT T instruction) is executed one time for one scan using a subroutine program.

The timer cannot be used in interrupt programs. The timer can be used in subroutine programs or FB programs if the coil of timer (OUT T instruction) is executed one time for one scan.

When setting value is 0: The contact is turned on when the OUT T instruction is executed. Even when the setting value is increased after the timer time is up, the timer status does not change (time continues to be

up) and the timer does not operate. Do not set the timer setting value to 32768 or above. If used when set to 32768 or above, the timer contact may not turn on.

Precautions about long timer usage This section describes the precautions when using long timers (LT/LST). The long timer cannot be used in initial execution type programs. Even when the setting value is increased after the long timer time is up, the long timer status does not change (time

continues to be up) and the long timer does not operate.

LT0 +0

+1

+2

+3

+4

+5

+6

+7

LT1

1 word (16 bits)

Current value of LT0

(2 words)

Used in system.

Current value of LT0

(2 words)

Used in system.

6 27 DEVICES 27.3 User Device

27

Timer setting value and timer limit setting When the condition is "Timer setting value < Scan time + Timer limit setting", the coil and the contact may be turned on at the same time depending on the timing when the coil turns on. When the condition is not satisfied, reduce the timer limit setting value to satisfy the condition.

Ex.

When changing the low-speed timer to high-speed timer and reducing the timer limit setting value (scan time: 20ms)

The following shows an example of when the coil and the contact are turned on at the same time when the condition is "Timer setting value < Scan time + Timer limit setting".

Ex.

In the case where the values are set as follows (timer setting value: 1 (1 100ms), scan time: 20ms, and timer limit setting: 100ms), when the coil of the timer (T0) turns on in the next scan after the coefficient of the END instruction becomes equal to or higher than the timer setting value, the coil and the contact turns on at the same time because the timer current value becomes equal to the timer setting value at startup of the timer.

Before change (low-speed timer)

Timer limit setting Low Speed Timer/Low Speed Retentive Timer: 100ms Timer setting value (100ms 1 = 100ms) < Scan time (20ms) + Timer limit setting (100ms)

After change (high-speed timer)

Timer limit setting High Speed Timer/High Speed Retentive Timer: 10.00ms Timer setting value (10.00ms 10 = 100ms) < Scan time (20ms) + Timer limit setting (10ms)

(1) The coefficient of the END instruction becomes equal to or higher than the timer setting value. Therefore, when the coil turns on during this period, the contact also turns on at the same time.

(T0 ) K1

(T0 ) H K10

20ms 20ms 20ms

END

0 0 0 1

0 0 1 0

OFF ON

ON

ON OFF

OFF

X0

Coil of T0

Contact of T0

END END END

X0 K1 T0

Count at execution

of the END instruction

100ms counting

1

Current value of T0

Program

Timer setting value Scan time

(20ms) Timer limit setting

(100ms) Timer setting value

(1 100ms)

(1)

27 DEVICES 27.3 User Device 427

42

Ex.

In the case where the values are set as follows (timer setting value: 2 (2 100ms), scan time: 110ms, and timer limit setting: 100ms), when the coil of the timer (T0) turns on in the next scan after the coefficient of the END instruction becomes equal to or higher than the timer setting value, the coil and the contact turns on at the same time because the timer current value becomes equal to the timer setting value at startup of the timer.

(1) The coefficient of the END instruction becomes equal to or higher than the timer setting value. Therefore, when the coil turns on during this period, the contact also turns on at the same time.

X0

Coil of T0

Contact of T0

Count at execution

of the END instruction

100ms counting

Current value of T0

Program

Timer setting value Scan time (110ms)

Timer limit setting (100ms)

Timer setting value (2 100ms)

110ms 110ms 110ms

END

0 0 0 2

1 1 2 1

OFF ON

ON

ON OFF

OFF

END END END

X0 K2 T0

1 1 2 1

(1)

8 27 DEVICES 27.3 User Device

27

Counter This device counts the number of rising operation of the input condition in the program. The counter is an up-timing type device and therefore when the count value matches a setting value, the count reaches its upper limit and the contact is turned on.

Types of counters There are two types of counters: counter (C) which retains the counter values in 16-bit units and long counter (LC) which retains them in 32-bit units. The counter (C) and the long counter (LC) are different devices and the number of device points can be set for each of them.

Counter (C) This device uses one word for each point. The measurable range is 0 to 65535.

Long counter (LC) This device uses two words for each point. The measurable range is 0 to 429467295.

The long counter (LC) can be used in interrupt programs. ( Page 99 Interrupt Program)

Counting process When executing the counter coil (OUT Cinstruction / OUT LCinstruction), the counter coil is turned on/off, the current value is updated (count value +1), and the contact is turned on/off. The current value is updated (count value +1), when the counter coil input is rising (off and on). The current value is not updated when the coil input is turned off, on and on, and on and off.

X0 K10

X0 OFF

OFF

ON

ON

END END ENDOUT C0 OUT C0 OUT C0

C0

[Ladder example]

[Update timing of the current value]

Program

Coil of C0

Update of the current value Update of the current value

27 DEVICES 27.3 User Device 429

43

Resetting counters The counter current value is not cleared even when the counter coil input is turned off. To clear the counter current value (resetting) and turn off the contact, issue the RST C/RST LC instruction. When executing the RST C instruction, the counter value is cleared and the contact is turned off.

Precautions about counter reset When executing the RST C instruction, the coil for C is also turned off. If the execution condition for the OUT C instruction is turned on after the RST C instruction is executed, the coil of C is turned on and the current value is updated (count value +1) when the OUT C instruction is executed.

In the above ladder example, the coil of C0 is turned on by turning off and on M0 and as a result the current value is updated. When C0 count reaches its upper limit, C0 contact is turned on and C0 current value is cleared by execution of the RST C0 instruction. At this time C0 coil is also turned off. When M0 is turned on at the next scanning, the current value is updated because C0 coil is turned off and on during the OUT C0 instruction execution (the current value is changed to 1).

(1) The count value is cleared, and the contact turns off.

(1) The current value update contact turns on. (2) The current value is updated because the coil of C0 turns on. (3) The count value is cleared, and the contact turns off.

X0

RST C0

X0 OFF

OFF

(1) (1)

ON

END END ENDRST C0 RST C0 RST C0

[Ladder example]

[Reset timing of the counter]

Program

Execution

RST C0 instruction

C0

M0 K10 C0

RST C0

M0 OFF

OFF

ON

RST C0OUT C0 END

RST C0 OFF

(3)

(1) (2)

RST C0OUT C0 ENDEND

ON

Program

Coil of C0

The coil of C0 turns off.

0 27 DEVICES 27.3 User Device

27

To address the above problem, insert a normally closed contact of the execution condition for the OUT C0 instruction into the execution condition for the RST C0 instruction to prevent C0 coil from being turned off while the execution condition (M0) of the OUT C0 instruction is turned on as shown in the following ladder example.

Maximum counting speed for counters Counting is possible only when on/off time of the input condition is longer than the execution interval of the same OUT C instruction. Maximum counting speed for counters can be obtained by the following equation:

*1 Duty (n) is a value which expresses the ratio of on/off time of the count input signal as a percent (%) value.

C0 RST C0

M0 C0

K10

M0

100 T

1n

Maximum counting speed Cmax

[times/s]=

OFF

ON

T1 T2

T2

T1

100%

100%

T1+T2

T1+T2

When T1T2, n =

When T1

27 DEVICES 27.3 User Device 431

43

Data register (D) This device can store numerical values.

Link register (W) This device is used as a CPU module side device when refreshing word data between the network module, such as the CC- Link IE Controller Network module and the CPU module.

Refreshing network modules using link register Data are transferred/received between the link register (W) within the CPU module and the link register (LW) of the network module, such as the CC-Link IE Controller Network module. The refresh range is specified using parameters on the network module. The part which is not used for refreshing can be used for other applications.

Link special register (SW) Word data information on the communication status and error detection status of a network, such as CC-Link IE Controller Network, are output into the link special register (J\SW) on the network. The link special register (SW) is a device for using as a refreshing target of link special registers in the network. The part which is not used for refreshing can be used for other applications.

(1) The network status is checked.

SW0A0.3 SW

SW

SW00A7

SW00A0

SW00A7

SW00A0

(1) Used in a program.

CC-Link IE Controller Network module

Refresh Stores the baton pass status of each station.

CPU module

2 27 DEVICES 27.3 User Device

27

27.4 System Device The system device is used by the system. Assignment/capacity is fixed and cannot optionally be altered.

Function device (FX/FY/FD) This device is used for the subroutine programs with argument passing. Data is written/read between the subroutine call sources with argument passing and the subroutine programs with argument passing. When using the function device in a subroutine program, the device used in each subroutine program call source can be determined. As a result, when using the same subroutine program, it can be used without being aware of the call source of other subroutine programs.

Function input (FX) This device is used when passing on/off data to a subroutine program. In the subroutine program, bit data specified in a subroutine call instruction with argument passing are captured and used for operation. All the bit data specification devices of the CPU module are available.

Function output (FY) This device is used when passing operation results (on/off data) in a subroutine program to a subroutine program call source. Operation results are stored into the device specified in the subroutine program with argument passing. The bit data specification device other than the CPU module input (X) are available.

Function register (FD) This device is used for writing/reading between the subroutine call source and the subroutine program. The input/output condition of the function register is automatically identified by the CPU module. "Source data" in a subroutine program means data inputted into the subroutine program. "Destination data" in a subroutine program means data outputted from the subroutine program. One point of a function register occupies maximum of four words and can store 16-bit data, 32-bit data, 64-bit data, single-precision real number, and double-precision real number. However the number of words to be used depends on the instruction in the subroutine program. For example, for the destination of addition instruction (+instruction) of 16-bit signed integer, one word is used.

Besides, for the destination of addition instruction (ED+instruction) of double-precision real number, four words are used. (1) The data is stored in one point of D0.

(1) The data is stored in four points of D0 to D3.

CALL P0 D0 P0 + ZR0 K10 FD0

D0 D1 D2 D3 D4

(1)

CALL P0 D0 P0 ED+ ZR0 E1.0-3 FD0

D0 D1 D2 D3 D4

(1)

27 DEVICES 27.4 System Device 433

43

Special relay (SM) This is the internal relay for which the specification is defined in the CPU module, where the status of the CPU module is stored. ( Page 579 List of Special Relay Areas)

Special register (SD) This is the internal register for which the specification is defined in the CPU module, where the status (diagnostics information, system information, etc) of the CPU module is stored. ( Page 602 List of Special Register Areas)

27.5 Link Direct Device This device directly accesses link relays and/or link registers of the network module in the CC-Link IE Controller Network and/ or CC-Link IE Field Network.

Specification method Specify a link direct device as shown below: The link register 10 (W10) of the network number 2 can be specified as "J2\W10".

For bit devices, digit specification is allowed. (Example: J1\K1X0, J10\K4B0)

Device No. Input Output Link relay Link register Link special relay Link special register From SW0

Network No.1 to 239

Specification method: J\

From SB0 From W0 B0 From Y0 From X0

4 27 DEVICES 27.5 Link Direct Device

27

Specification range All the link devices of the network module can be specified. The link devices which fall outside the range specified with "Refresh Setting" can also be specified. For the following modules, specify the "Extended Mode (iQ-R Series Mode)" in the "Link Direct Device Setting" of the CPU parameter. (Default setting is "Q Series Compatible Mode".)*1

CC-Link IE TSN master/local module Motion module CC-Link IE Controller Network-equipped module to which the link points extension is set.*2

[CPU Parameter] [Memory/Device Setting] [Link Direct Device Setting]

Window

When the network module to be administered contains any of the following modules when specifying the link direct device, set the "Extended Mode (iQ-R Series Mode)" to the "Link Direct Device Setting". CC-Link IE TSN master/local module Motion module CC-Link IE Controller Network-equipped module to which the link points extension is set.*2

Other modules operate in the both mode.

*1 Before using, check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions) *2 Applies when the "Link points extended setting" of the module parameter is set to "Extend" and the extended link device is specified.

( MELSEC iQ-R CC-Link IE Controller Network User's Manual (Application))

Specification range for writing Writing should be done in the range which is within the link device range specified as a send range of network parameters, and outside the range specified as the refresh range for "Refresh Setting".* 1

Note that writing in the range specified as the refresh range overwrites link device data of the network module during refresh process. When writing data to a writing range of another station using the link direct device, data is overwritten with received data during data reception from another station.

*1 There is only one network module to which the link direct device can write data for each network number. When more than one network module with the same network number is mounted, the network module with the lowest slot number is the target for writing by the link direct device.

Specification range for reading Data can be read from the entire range of link devices of the network module.* 1

*1 There is only one network module for which reading is allowed with the link direct device for each network number. When more than one network module with the same network number is mounted, the network module with the lowest slot number is the target for reading by the link direct device.

LB0B0

CPU module Network module

Link device range

Sending range

Write range

Refresh range

27 DEVICES 27.5 Link Direct Device 435

43

Difference from link refresh The following table shows the difference between the link direct device and link refresh.

Item Link direct device Link refresh Description method in program

Input Jn\K4X0... X0...

Output Jn\K4Y0... Y0...

Link relay Jn\K4B0... B0...

Link register Jn\W0... W0...

Link special relay Jn\K4SB0... SB0... Or module label

Link special register Jn\SW0... SW0... Or module label

Access range in relation to network module All the link devices for each network module The range specified in "Refresh Setting"

Guarantee range of access data In word (16-bit) units In word (16-bit) units

6 27 DEVICES 27.5 Link Direct Device

27

27.6 Module Access Device This device directly accesses from the CPU module to the buffer memory of the intelligent function module mounted on the main base unit and extension base unit. Specify this device with 'Un\Gn'. (Example: U5\G11)

When reading/writing the buffer memory data using the module access device more than twice within a program, the processing speed can be increased by conducting read/write operations at a single point of the program using the FROM/TO instruction. When data is written using more than one module access device:

When data is written at a single point of the program using the TO instruction:

(1) Store data to devices such as the data register (D). (2) Write data to only one point in the program.

Precautions The following describes the precautions for when the module access device is used. If data is written to the refresh-target memory using a program while the refresh function is being used, the CPU module

overwrites the data in the target memory at the execution of the refresh function. Thus, the expected operation may not be acquired. When the refresh function is used, do not write the data directly to the refresh-target memory but write it to the refresh-source memory.

*1 When the data is transferred from the CPU module to the module, the target memory is the buffer memory or link device. When the data is transferred from the module to the CPU module, the target memory is the specified device of the CPU module.

Specified item Value to be specified Un Start I/O number of intelligent function modules Upper two digits when a start I/O number is described in three digits

(00H to FFH) Example: 1F stands for X/Y1F0

Gn Buffer memory address 0 to 268435455 (decimal)

MOVP K0

MOVP K10

MOVP K5

MOVP K100

U0\ G10

U0\ G11

U0\ G12

U0\ G13

MOVP K0 D0

MOVP K10 D1

MOVP K5 D2

MOVP K100 D3

T0 H0 K10 D0 K4 (2)

(1)

27 DEVICES 27.6 Module Access Device 437

43

27.7 CPU Buffer Memory Access Device This device accesses memory used by the built-in function of the CPU module, such as data writing/reading between CPU modules on the multiple CPU system and Ethernet function ( Page 390 Specification method thorough CPU buffer memory access device)

Specification method Specify this device with 'Un\Gn'. (Example: U3E1\G4095, U3E2\HG1024)

Specified item Value to be specified Un (I/O number of the CPU module) CPU No.1 3E0

CPU No.2 3E1

CPU No.3 3E2

CPU No.4 3E3

G (CPU buffer memory area) CPU buffer memory G

Fixed scan communication area HG

n (CPU buffer memory address) 0 to 268435455 (decimal)

8 27 DEVICES 27.7 CPU Buffer Memory Access Device

27

27.8 Index Register (Z/LZ) This device is used for the index modification of the device. The index modification is the indirect specification using the index register. Specify the device with the number obtained from "Device number of device targeted for modification" + "Contents of index register".

16-bit index modification The device number is modified using the index register (Z). The modification range for the device in the case of the 16-bit index modification is -32768 to 32767.

Ex.

Modifying D0 with Z0

32-bit index modification The device number is modified using the long index register (LZ). The modification range for the device in the case of the 32- bit index modification is -2147483648 to 2147483647.

Ex.

Modifying D0 with LZ0

In addition, 32-bit index modification with ZZ expression using two index registers is also available.

(1) Access D0Z0 = D100.

(1) Access D0LZ0 = D100000.

D100Z10

Index register number for modification Modified target device

MOV K100 Z0

INC Z0

MOV W0 D0Z0

SM402

M10

(1)

D100LZ1

Index register number for modification Modified target device

DMOV K100000 LZ0

DINC LZ0

MOV W0 D0LZ0

SM402

M10

(1)

27 DEVICES 27.8 Index Register (Z/LZ) 439

44

Device for which index modification can be performed The following table lists the devices that can be targeted for index modification.

*1 The devices can be used for the contact, coil and current value. *2 For network numbers and the specification source of I/O numbers, 32-bit index modification cannot be performed. *3 When the devices are used as an interrupt pointer, index modification cannot be performed. *4 The device can be specified by using the CPU module where the SFC function can be used. ( Page 700 Added and Enhanced

Functions)

Index register setting The following window allows to specify the number of points for the index register (Z) and long index register (LZ) and the range where they are used as a local device. The total number of points of the index register (Z) and the long index register (LZ) must be set to 24 words.

[CPU Parameter] [Memory/Device Setting] [Index Register Setting]

Window

Displayed items

Item Description 16-bit index modification X, DX, Y, DY, M, L, B, F, SB, V, S*4, T*1, LT*1, ST*1, LST*1, C*1, LC*1, D, W, SW, SM, SD, Jn\X, Jn\Y, Jn\B, Jn\SB,

Jn\W, Jn\SW, Un\G, U3En\G, U3En\HG, R, ZR, RD, P*3, I*3, BL*4, BLn\S*4, J, U, K, H

32-bit index modification M, B, SB, T*1, LT*1, ST*1, LST*1, C*1, LC*1, D, W, SW, Jn\B*2, Jn\W*2, Un\G*2, U3En\G*2, U3En\HG*2, R, ZR, RD, K, H

Item Description Setting range Default Number of points setting

Total Points Check the total number of points for index register and long index register.

Index register (Z) Set the number of points for the index registers. 0 to 24 points (in two-point increments)

20 points

Long index register (LZ) Set the number of points for the long index registers. 0 to 12 points (in one-point increments)

2 points

Local setting

Number of points setting

Local Index register (Z) Set the number of points for index registers used as a local device. Set within the range of the index register.

0 to 24 points (in one-point increments)

0 points

Local long index register (LZ) Set the number of points for long index registers used as a local device. Set within the range of the long index register.

0 to 12 points (in one-point increments)

0 points

Head Index register (Z) Set the start number for the local index registers. Set within the range of the index register.

0 to 23 0

Long index register (LZ) Set the start number for the local long index registers. Set within the range of the long index register.

0 to 11 0

0 27 DEVICES 27.8 Index Register (Z/LZ)

27

Combination of index modification This section describes the combination of index modification.

Modification order for the device specification and index modification According to the priority order shown below, the device specification (digit specification, bit specification, indirect specification) and index modification can be applied. However, some word devices may not follow the priority order shown below.

Specification method combined with device specification The device targeted for specification is modified in order of: 1st modification, 2nd modification and then 3rd modification. Besides, the following contents can be used only for the device for which the 1st modification can be applied. (For example, index modification + digit specification is impossible for the function input (FX).)

Precautions This section describes the precautions on using index modification.

Index modification between the FOR and NEXT instructions Between the FOR instruction and the NEXT instruction, pulse output is provided through the edge relay (V). However, pulse output by the PLS, PLF, or pulse conversion (P) instruction is not available ( Page 420 Edge relay (V))

Index modification by the CALL instruction In the CALL instruction, pulse output is provided through the edge relay (V). However, pulse output by the PLS, PLF, or pulse conversion (P) instruction is not available ( Page 420 Edge relay (V))

Device range check for index modification For details on the device range check when index modification is performed, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

Change of the index modification range due to switching from 16-bit to 32-bit To change the index modification range for switching from 16-bit to 32-bit, the user must: Review the index modification block(s) within the program. To perform the 32-bit index modification specification with ZZ expression, review the range of the index register (Z). Note

that the range within the LZ cannot be specified. For 32-bit index modification with ZZ expression, because the specified index register (Zn) and the immediately following

index register (Zn+1) are used, caution must be taken to prevent duplicated index registers from being used. Review the number of points of the index register (Z) and that of the long index register (LZ), which are specified in "Index

Register Setting" ( Page 440 Index register setting)

Order of priority When the device targeted for the device specification and index modification is the bit device

When the device targeted for the device specification and index modification is the word device

High Low

1: Index modification 2: Digit specification

1: Index modification 2: Indirect specification 3: Bit specification

Device targeted for specification 1st modification 2nd modification 3rd modification Example Bit device Index modification Digit specification K4M100Z2

Word device Index modification Bit specification D10Z2.0

Index modification Indirect Specification @D10Z2

Bit specification Index modification D10.8Z2

Indirect Specification Bit specification @D10.8

Index modification Indirect Specification Bit specification @D10Z2.8

Indirect Specification Bit specification Index modification @D10.8Z2

27 DEVICES 27.8 Index Register (Z/LZ) 441

44

When values are stored in the index registers For 16-bit index modification using the index register (Z), the range is -32768 to 32767. Therefore, when values within the range from 32768 to 65535 are stored in the index register (Z) for an instruction which processes unsigned data, the instruction does not work in design because the range of the index modification will be -32768 to 32767. For the range of values larger than or equal to 32768, the long index register (LZ) must be used so that 32-bit-based index modification can be applied.

Ex.

Operation for Index modification

(1) When the value 65535 is stored in the index register (Z), D50000(-1) to D49999 are accessed because the value is turned into -1 when an index modification is performed.

(2) When a value larger than or equal to 32768 is used for an index modification, the value must be stored in the long index register (LZ). In doing so, the value 65535 is used as such for an index modification using the long index register (LZ) and D50000 (65535) to D115535 become accessible.

D17231 D17232

D49999 D50000

D82767 D82768

D115535

-32768

Z0

-2147483648

LZ0

2147483647

32767

(1)

(2)

Device/label memory

SM400 +P_U K65535 Z0

MOV K100 D50000Z0

SM400 D+P_U K65535 LZ0

MOV K100 D50000LZ0

(1) When unexpected operation is executed (2) When proper operation is executed

2 27 DEVICES 27.8 Index Register (Z/LZ)

27

27.9 File Register (R/ZR) This device is a word device for extension. This device is specifically a file register file which exists in the file storage area on the device/label memory.

Specification method There are two types of the specification methods for the file register: block switching and serial number methods.

Block switching method In this method the number of points of file register being used is specified by being divided in increments of 32K point (R0 to R32767). When using more than one block, specification is conducted by switching to the block number used by the RSET instruction. "R" is used as the device symbol. The range of "R" is from R0 to R32767. However in the following cases the upper limit of the device number is "block size (unit: word) -1". The file register file size is smaller than 64K bytes. The file register file size is not a multiple of 64K bytes and the end block is specified in the RSET instruction.

Serial number method In this method file registers having more than 32K points are specified using serial device numbers. File registers of the multiple blocks can be used as consecutive file registers. "ZR" is used as the device symbol. The range of ZR is from ZR0 to (file register file size (unit: word) -1).

D0 R0MOV

D0 R0MOV

R0

R0

RSET K1

RSET K2

R32767

R32767

R0 Specify R0 of the block 1.

Specify R0 of the block 2.

Block 0

Block 1

Block 2

MOV D0 ZR32768

MOV D0 ZR65536

ZR0

ZR32767 ZR32768

ZR65535 ZR65536

(Block 0)

(Block 1)

(Block 2)

27 DEVICES 27.9 File Register (R/ZR) 443

44

Setting file registers This section describes the settings required to use the file registers.

Configuration procedure This section describes the procedure to use the file registers.

1. Set the file register usage with [CPU Parameter].

2. To use the file register for each program, previously create the device memory which will become the file register file. ( GX Works3 Operating Manual)

3. When using the file registers, which are common for all programs, a file register file with the name and capacity set in the file register setting is created.* 1

*1 If the capacity is not set, it must be set when creating a file register file and writing it to the programmable controller in the same manner as the procedure 2.

4. Write parameters and file register files into the CPU module.

File register setting This setting must be completed before using the file registers.

[CPU Parameter] [File Setting] [File Register Setting]

Window

Displayed items

Precautions To access the CPU module from either of the following modules or engineering tools, the size of the file register needs to be 5696K words or less with an extended SRAM cassette (NZ2MC-16MBS) of 16MB. C Controller module MES interface module GOT2000 (when the programmable controller program monitor (R ladder) is used) Engineering tool version 1.015R or earlier CPU Module Logging Configuration Tool version 1.49B or earlier GX LogViewer version 1.49B or earlier MX Component version 4.10L or earlier

Clearing file registers To clear the file registers, use the following methods ( Page 135 Memory Operation) Clearing in the program: write 0 into the file register range to be cleared. Clearing with engineering tool: clear them using engineering tool ( GX Works3 Operating Manual)

Item Description Setting range Default Use Or Not Setting Specify whether or not file registers should be used. Not Use

Use File Register of Each Program Use Common File Register in All Programs

Not Use

Capacity Specify the capacity of the file register in increments of 1K words when "Use Common File Register in All Programs" is selected.

This value depends on whether or not the extended SRAM cassette is mounted and its capacity. ( Page 128 The setting range of the capacity of each area)

File name Assign a file name to the file register when "Use Common File Register in All Programs" is selected.

1 to 60 characters

4 27 DEVICES 27.9 File Register (R/ZR)

27

27.10 Refresh Data Register (RD) This device is provided for using as a refreshing target of buffer memory on the various devices, such as an intelligent function module. Refresh Data Register (RD) is assigned into the refresh memory area. ( Page 131 Refresh memory)

Refresh memory setting [CPU Parameter] [Memory/Device Setting] [Refresh Memory Setting]

Window

Displayed items

Item Description Setting range Default Total Points Check the total number of points for the refresh data register and

the assigned area. 1024K Point

Refresh Data Register (RD) area Set the number of points of refresh data register. 0 to 1024K points (in one-point increments)

512K Point

Module Label Assignment Area Set the number of points for the module label assigned area. 0 to 1024K points (in one-point increments)

512K Point

Intelligent function module CPU module

Refresh memory

Refresh

Buffer memory

Module label-assigned area

Refresh data register (RD)

27 DEVICES 27.10 Refresh Data Register (RD) 445

44

27.11 Nesting (N) This device is used in the master control instructions (the MC/MCR instruction)*1 and enables the programming of operation conditions in a nesting structure. Specify this device from outside the nesting structure starting with the lowest number (in ascending order from N0 to N14).

*1 This instruction creates an effective ladder-switching program using opening/closing the common rail of the ladders.

M15N0

B

C

A M15N0MC

M16N1MC

N2MCR

N1MCR

M17N2MC

N0MCR

M16N1

M17N2Control range of the nesting N0

Control range of the nesting N1

Control range of the nesting N2

Specify the nesting in ascending order.

Execute when the condition A is satisfied.

Execute when the condition A and B are satisfied.

Specify the nesting in descending order.

Execute when the condition A, B, and C are satisfied.

Execute when the condition A and B are satisfied.

Execute when the condition A is satisfied.

Execute regardless of the conditions of A, B, and C.

6 27 DEVICES 27.11 Nesting (N)

27

27.12 Pointer (P) This device is used in the jump instructions (the CJ/SCJ/JMP instruction) and/or subroutine program call instructions (such as the CALL instruction). There are two types of pointer: the global pointer and the local pointer. Use the pointer when: Specifying the jump destination and label of the jump instructions (the CJ/SCJ/JMP instruction). Specifying the call destination and label (the head of subroutine program) of the subroutine call instructions (such as the

CALL instruction).

Global pointer This is the pointer which enables calling by the subroutine call instruction from all the program being executed.

Effective use of number of points The number of points for global pointers can be obtained with the following formula: "pointer number of points specified by the parameter" - "the total point number of local pointer being used for each program".

Precautions This section describes the precautions when the global pointer is used. A global pointer with the same pointer number cannot be set as a label in multiple points.

CALL P1000 P1000

CALL P1001 P1001

RET

RET

Program 1 (Program group A) Program 3 (Program group C)

Program 2 (Program group B)

27 DEVICES 27.12 Pointer (P) 447

44

Local pointer This is the pointer to be independently used in each program where the same pointer number can be used. This pointer is specified in the following format: # (pointer number) (Example: #P0) ( Page 455 Specification method for the local devices).

Effective use of number of points Local pointer number of points are shared among all the programs. The range of the local pointer number of points used by each program is from P0 to the maximum value of the local pointer being used in that program. For example, even when a program actually uses only P99, 100 points (P0 to P99) are considered to be used. When using local pointers in multiple programs, they can be effectively used by using them in ascending order from P0 in each program group.

(1) The local pointers with the same number can be used between different programs.

CALL #P0

CALL #P1

CALL #P0

CALL #P1

FEND FEND

RET RET

RET RET

#P0 #P0

#P1 #P1

(1)

Program 1 Program 2

Program A

P0 to P99 are used in the program.

One-hundred points of P0 to P99 are occupied.

Program B

P100 to P199 are used in the program.

Two-hundred points of P0 to P199 are occupied.

When P100 to P199 are used, 100 points are occupied.

Program C

P299 is used in the program.

Three-hundred points of P0 to P299 are occupied.

When P0 is used, one point is occupied.

The total of 600 points are used.

8 27 DEVICES 27.12 Pointer (P)

27

Pointer setting The following menu item is to set pointers.

[CPU Parameter] [Memory/Device Setting] [Pointer Setting]

Window

Displayed items

*1 Up to the number of "Total points of pointer device area" - "Number of points of global pointer". *2 The default number of points is 32768 for the R120CPU and R120ENCPU. *3 The default number of points is 8192 for the R120CPU and R120ENCPU. *4 The default number of points is 16384 for the R120CPU and R120ENCPU.

Specify a pointer number which is equal to or lower than "(end number of the pointer range specified in the parameter) - (number of points of the global pointers)".

27.13 Interrupt Pointer (I) This device is used as a label located at the head of the interrupt program. This pointer can be used in all the programs being executed.

Setting the execution type of program to the event execution type eliminates the need to write (I) the interrupt pointer. ( Page 91 Interrupt occurrence by the interrupt pointer (I))

Item Description Setting range Default Global Pointer Start Set the start number of the global pointer. P0 and over*1 0

Total Points Check the total number of points for the pointer.

16384 points*2

Global Pointer Set the number of points of the global pointer. R120CPU, R120ENCPU: 0 to 32768 points (in increments of 1 point)

Other CPU modules: 0 to 16384 points (in increments of 1 point)

4096 points*3

Local Pointer Set the number of points of the local pointer. 4096 points*3

Pointer Type Label Set the number of points for the pointer type label assignment area.

8192 points*4

IRET

Interrupt pointer (interrupt program label)

Interrupt program

27 DEVICES 27.13 Interrupt Pointer (I) 449

45

Interrupt factors of the interrupt pointer numbers The interrupt factors of the interrupt pointer numbers are indicated.

The priority for the interrupt pointer numbers and interrupt factors The priority for the interrupt pointer numbers and interrupt factors are indicated.

The interrupt priority is the order which is executed at the time of the multiple interrupt. ( Page 114 Interrupt priority)

The interrupt priority order is the order which is executed when the interrupt factor with the same interrupt priority is generated. ( Page 117 Multiple interrupt execution sequence)

Interrupt factor Interrupt pointer number Description Interrupt from module I0 to I15 This is a pointer used for modules which have the interrupt function.

Interrupt by the internal timer I28 to I31 This interrupt pointer is used in fixed scan interrupts by the internal timer.

Inter-module synchronous interrupt I44 This fixed scan interrupt pointer is used in the inter-module synchronization function.

Multiple CPU synchronous interrupt I45 This fixed scan interrupt pointer is used in the multiple CPU synchronization function.

High-speed internal timer interrupt 2 I48 This interrupt pointer is used in fixed scan interrupts by the internal timer and can be specified in a shorter interval than interrupt pointer numbers I28 to I31.

High-speed internal timer interrupt 1 I49

Interrupt from module I50 to I1023 This is a pointer used for modules which have the interrupt function.

Interrupt pointer number Interrupt factor Interrupt priority Interrupt priority order

I0 Interrupt from module 1st point 5 to 8 9

I1 2nd point 10

I2 3rd point 11

I3 4th point 12

I4 5th point 13

I5 6th point 14

I6 7th point 15

I7 8th point 16

I8 9th point 17

I9 10th point 18

I10 11th point 19

I11 12th point 20

I12 13th point 21

I13 14th point 22

I14 15th point 23

I15 16th point 24

I28 Interrupt by the internal timer 4 8

I29 7

I30 6

I31 5

I44 Inter-module synchronous interrupt 3 4

I45 Multiple CPU synchronous interrupt 3

I48 High-speed internal timer interrupt 2 2 2

I49 High-speed internal timer interrupt 1 1 1

I50 to I1023 Interrupt from module 5 to 8 25 to 998

0 27 DEVICES 27.13 Interrupt Pointer (I)

27

27.14 Network No. Specification Device (J) This device is used when specifying a network number with the Link dedicated instruction. ( MELSEC iQ-R Programming Manual (Module Dedicated Instructions))

27.15 I/O No. Specification Device (U) This device is used when specifying an I/O number with the intelligent function module dedicated instruction. ( MELSEC iQ-R Programming Manual (Module Dedicated Instructions))

27.16 SFC Block Device (BL) This device is used when specifying SFC program blocks. This device is also used when specifying step No. through such methods as verifying (monitor, current value changes) SFC programs with SFC control instructions or the engineering tool. ( MELSEC iQ-R Programming Manual (Program Design))

27.17 SFC Transition Device (TR) This device is used when specifying SFC program transition conditions. This device can only be used for device comments for transition conditions. ( MELSEC iQ-R Programming Manual (Program Design))

27.18 Global Device This device can be shared by all the programs. All the devices that do not set as local device are handled as global device.

27.19 Local Device This device can be used independently in each program. When creating multiple programs, programming can be completed without being aware of devices used in other programs.

The local device area must be reserved independently from the global device area. Therefore a local device and global device with the same device number can exist.

MOV K3 #D100

MOV K1 D100

MOV K4 #D100

MOV K2 D100

D0

D99 D100

D199 D200

D300

#D100

#D199

#D100

#D199

Program execution

Program A

Program B

END processing

Global device

The value is K1 K2

Local device

For the program A For the program B

The value is K4.The value is K3.

27 DEVICES 27.14 Network No. Specification Device (J) 451

45

Devices available as local device The following devices are available as local devices. Internal relay (M) Edge relay (V) Timer (T, LT, ST, LST) Counter (C, LC) Data register (D) Pointer (P)

Because the index register (Z, LZ) saves/returns during program execution, it should be regarded separately as the local index register unlike other local devices. ( Page 439 Index Register (Z/LZ))

Local device area The CPU module reserves the local device area on the device/label memory based on the number of points setting of the local device when: CPU module is powered off and on or is reset. Operating status of the CPU module is changed from STOP to RUN.

When local device is used in subroutine program Local devices to be used vary depending on whether SM776 (Local device setting at CALL) is turned on or off. Local index register to be used is also determined according to the SM776 setting.

In terms of on/off setting for SM776, the value (on or off) used when the subroutine call occurs is considered to be effective. Therefore when on/off setting for SM776 is switched in the subroutine program, the modified value (on or off) is not effective until the next subroutine call occurs.

On/off setting for SM776 cannot be specified for each program file because it is enabled for each CPU module.

SM776 Local device to be used Off Uses local devices of the program file from which subroutine program is called.

On Uses local devices of the program file into which the subroutine program is stored.

2 27 DEVICES 27.19 Local Device

27

When local device is used in interrupt and other programs When using a local device for an interrupt program / a fixed scan execution type program / an event execution type program triggered by occurrence of an interrupt, turn on SM777 (Local device setting in interrupt programs). The programs will not function properly if SM777 is turned off.

Ex.

Operation if SM777 turned on in following setting

For local index register, the register of the program file which has been executed before these programs is used regardless of the SM777 setting.

For SM777, the value (on/off) set at the execution of an interrupt program / a fixed scan execution type program / an event execution type program triggered by occurrence of an interrupt is valid. For this reason, when the set value is changed while a program is being executed, the value changed does not become valid until the next time any of these programs is executed.

On/off setting for SM777 cannot be specified for each program file because it is enabled for each CPU module.

When the local device monitor is executed, the monitor switches to the applicable local device. Consequently, if SM777 is off, when an interrupt occurs immediately after switching, and a local device is accessed, the local device being monitored by the local device monitor is used. (The local device for the program being run prior to the interrupt (program immediately before END) is not accessed.)

Clearing local device Local device can be cleared to 0 by the following operations: CPU module is powered off and on or is reset. CPU module status is changed from STOP to RUN. CPU module status is changed from PAUSE to RUN.

Program name Execution type Local device use/not use A Scan Not Use

B Scan Use

C Scan Use

X Fixed scan Use

(1) Uses the program X local device.

A ENDC A BB C END

X XX

(1) (1) (1)

Execution program

Local device

For X

For B

For C

For X

For C

For X

For B For B

For C

27 DEVICES 27.19 Local Device 453

45

Setting method for the local devices Set the range where each device will be used as a local device and also set whether or not it should be used.

Range setting The range setting for local devices is common to all the programs. Therefore the range for local devices cannot be set for each program.

Operating procedure

Configure the setting range of the local device within the range which has been set for the number of device points. The number of local devices used is calculated by the following calculation formula. Set the number of local devices used so that the number is equal to or less than the capacity of the local device area. Total number of local devices used = ((A 16) + B + (C 2) + (D 4) + ((E 2) 16)) F A: Number of points of the local devices M and V B: Number of points of the local devices D, T (current value), ST (current value), and C (current value) C: Number of points of the local device LC (current value) D: Number of points of the local devices LT and LST E: Number of points of the local devices T (contact/coil), ST (contact/coil), C (contact/coil), and LC (contact/

coil) F: Number of programs using the local device

Setting unit The increment of setting of a local device is the same as that of a global device. ( Page 415 Range of use of device points)

"Device/Label Memory Area Detailed Setting" window 1. Click "Detailed Setting" on the "Device Setting" window.

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Detailed Setting] [Device Setting] [Detail Setting]

"Device Setting" window 2. Set the range where each device will be used as a local device.

4 27 DEVICES 27.19 Local Device

27

Setting whether or not it should be used Whether or not local devices should be used can be set for each program. Since the local device area of program for which "Do not use" has been set is not assured, it can suppress unnecessary consumption of device/label memory.

[CPU Parameter] [Program Setting]

Operating procedure

Do not use local devices in a program which is configured not to use local devices.

Specification method for the local devices To specify the local device in the program, add "#".

Ex.

For example, #D100, K4#M0, and @#D0 can be used.

Local device is listed with a preceding # symbol in the program. This symbol is helpful to differentiate local devices from global devices.

Precautions This section describes the precautions when using local devices. Like global devices, the timer (T, LT, ST, LST) and counter (C, LC) specified as a local device cannot be checked for the

device range. Therefore when operates the address in the index modification or indirect specification, be careful not to exceed the specified device range.

Accessing the range including both global and local devices by the index modification is not allowed. When the range of the 32-bit index modification is across the setting ranges of local devices of the index register, proper

index modification is impossible. Local devices are not latched.

"Program Setting" window 1. Click "Detailed Setting" on the "Program Setting" window.

"Detailed Setting" window 2. Click "Detailed Setting" of "Device/File Use or not".

"Setting of Device/File Use Or Not" window 3. Set whether or not it should be used for each program in the setting of "Local Device Local Index Register Use or not".

27 DEVICES 27.19 Local Device 455

45

27.20 Indirect Specification Specify the device using the indirect address of device. Store the indirect address of device to be specified into the device for indirect specification, and write as "@ + Device for indirect specification".

Besides, specifying a bit of a word device allows the indirect specification for the instruction that specifies bits.

The indirect specification can be used in the device/label memory or refresh memory.

Indirect address of device To specify, use the 32-bit data, and to hold the value, use the device of two words. The indirect address of the device can be obtained with the ADRSET instruction. The ADRSET instruction specifies the indirect address of the device using instructions that handle 32-bit data. For the ADRSET instruction, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

When the block or the file of the file register is switched through the RSET or QDRSET instruction, the indirect address refers to the one of the block or the file before they are switched. To allow the indirect address in the device for indirect specification to specify the block or file after the file register is switched, specify the ADRSET instruction to obtain the indirect address again after block or file are switched.

Devices that can allow indirect specification This section lists devices that can allow indirect specification.

*1 Also can be used for the local device. (e.g.: @#D0) *2 The indirect address of device can be obtained for the local device as well. (e.g.: ADRSET #D0 D100) *3 Devices that cannot be used as operands of instructions cannot be used even when they are indirectly specified.

(1) The indirect address of D0 is read into D100, D101.

(2) The indirect address is used to indirectly specify D0.

(1) The indirect address of D0 is read into D100, D101.

(2) The indirect address is used to output at the 0th bit of D0 which was indirectly specified using the indirect address.

Type Device*3

Devices that can allow indirect specification where @ is added*1 T, ST, C, D, W, SW, FD, SD, Un\G, Jn\W, Jn\SW, U3En\G, U3En\HG, R, ZR, RD

Device that can acquire the indirect address through the ADRSET instruction*2

X, Y, M, L, B, F, SB, T, ST, C, D, W, SW, FX, FY, FD, SM, SD, R, ZR, RD

SM402

ADRSET D0 D100

M0

MOV @D100 D1

1000H D0

D100

D101 1000H

(1) (2)

Device for the indirect specification (D100, D101)

Indirect specification

Indirect address Device memory

SM402 ADRSET D0 D100

M0 @D100.0

1000H

1000H

(1)

D0.0

D0

(2)

D100 D101

Device for the indirect specification (D100, D101)

Bit specification of the device specified indirectly

Indirect address

Device memory

6 27 DEVICES 27.20 Indirect Specification

28

28 LABELS A label is a variable consisting of a specified string used in I/O data or internal processing. Programs can be created without considering the size of devices and buffer memory by using labels. For this reason, a program using labels can be reused easily even in a system having a different module configuration. When labels are used, there are some precautions on programming and functions used. For details, refer to the following. Page 471 Precautions

There are two types of labels described in this manual. Global labels Local labels There are other types of labels available in addition to the global labels and local labels. [System labels] A system label is a label that provides the same data in all projects compatible with iQ Works. It can be referenced from the GOT and the CPU modules and Motion controllers on other stations, and used for monitoring and accessing data. For details, refer to the following. Let's start iQ Works Version 2 [Module labels] A module label is a label defined uniquely by each module. A module label is automatically generated by the engineering tool from the module used, and can be used as a global label. For details, refer to the following. Function Block Reference for the module used

28.1 Global Labels A global label is a label that provides the same data within a single project. It can be used in all programs in the project. A global label can be used in program blocks and function blocks. The settings of a global label include a label name, class, and data type. By opening global labels, they can be referenced from GOT and other stations, and can be used for monitoring and accessing data.

Device assignment Devices can be assigned to global labels.

28.2 Local Labels A local label is a label that can be used only in the declared POU. Local labels outside the declared POU cannot be used. The settings of a local label include a label name, class, and data type.

Item Description Label to which no device is assigned Programming without being aware of devices is possible.

Defined labels are allocated to the label area or latch label area in the device/label memory.

Label to which a device is assigned If a device is to be programmed as a label against a device that is being used for input or output, the device can be assigned directly.

Defined labels are allocated to the device area in the device/label memory.

28 LABELS 28.1 Global Labels 457

45

28.3 Classes The label class indicates from which POU and how a label can be used. Different classes can be selected depending on the type of POU.

Global label

Class Description Applicable POU

Program block

Function block (FB)

Function (FUN)

VAR_GLOBAL A common label that can be used in both program blocks and function blocks

VAR_GLOBAL_CONSTANT A common constant that can be used in both program blocks and function blocks

VAR_GLOBAL_RETAIN A latch type label that can be used in both program blocks and function blocks

Local label

Class Description Applicable POU

Program block

Function block (FB)

Function (FUN)

VAR A label that can be used within the range of a declared POU. This label cannot be used in other POUs.

VAR_CONSTANT A constant that can be used within the range of a declared POU. This label cannot be used in other POUs.

VAR_RETAIN A latch type label that can be used within the range of a declared POU. This label cannot be used in other POUs.

VAR_INPUT A label that inputs a value into a function or function block. This label receives a value, and the received value cannot be changed in a POU.

VAR_OUTPUT A label that outputs a value from a function or function block

VAR_OUTPUT_RETAIN A latch type label that outputs a value from a function block

VAR_IN_OUT A local label that receives a value and outputs the value from a POU. The value can be changed in a POU.

VAR_PUBLIC A label that can be accessed as the public variable from other POUs

VAR_PUBLIC_RETAIN A latch type label that can be accessed as the public variable from other POUs

8 28 LABELS 28.3 Classes

28

28.4 Data Types The data types of a label are classified according to the bit length, processing method, and value range. There are two data types. Primitive data type Generic data type (ANY type)

Primitive data type The following table lists the data types included in the primitive data type.

*1 For the number of significant digits and input range of real number data input by the engineering tool, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

*2 The time type is used in a time data type function of standard functions. For standard functions, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

*3 For the notation of time, refer to the following. Page 490 Notation of time

The bit data in the word type label can be used by specifying a bit number. The bit type array label can be used as 16-bit or 32-bit data by specifying the number of digits. For the bit specification and digit specification methods, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

Data type Description Value range Bit length

Bit BOOL Represents the alternative status, such as on or off.

0 (FALSE), 1 (TRUE) 1 bit

Word [unsigned]/bit string [16 bits]

WORD 16-bit array 0 to 65535 16 bits

Double word [unsigned]/bit string [32 bits]

DWORD 32-bit array 0 to 4294967295 32 bits

Word [signed] INT Positive and negative integer values -32768 to 32767 16 bits

Double word [signed] DINT Positive and negative double- precision integer values

-2147483648 to 2147483647 32 bits

Single-precision real number*1

REAL Numerical values of decimal places (single-precision real number values)

-2128 to -2-126, 0, 2-126 to 2128

E-3.402823+38 to E-1.175495-38, 0, E1.175495-38 to E3.402823+38

32 bits

Double-precision real number*1

LREAL Numerical values of decimal places (double-precision real number values)

-21024 to -2-1022, 0, 2-1022 to 21024

E-1.79769313486231+308 to E-2.22507385850721-308, 0, E2.22507385850721-308 to E1.79769313486231+308

64 bits

Time*2 TIME Numerical values as day, hour, minute, second, and millisecond

T#-24d20h31m23s648ms to T#24d20h31m23s647ms*3

32 bits

String STRING Characters represented by ASCII code or Shift JIS code

255 one-byte characters maximum Variable

String [Unicode] WSTRING Characters represented by Unicode 255 characters maximum Variable

Timer TIMER Structure corresponding to the device, timer (T)

Page 460 Timer and counter data types

Retentive timer RETENTIVETIMER Structure corresponding to the device, retentive timer (ST)

Long timer LTIMER Structure corresponding to the device, long timer (LT)

Long retentive timer LRETENTIVETIMER Structure corresponding to the device, timer (LST)

Counter COUNTER Structure corresponding to the device, counter (C)

Long counter LCOUNTER Structure corresponding to the device, counter (LC)

Pointer POINTER Type corresponding to the device, pointer (P) ( Page 447 Pointer (P))

28 LABELS 28.4 Data Types 459

46

Timer and counter data types The data types of the timer, counter, long counter, retentive timer, long retentive timer, and long timer are the structures having a contact, coil, or current value.

*1 The unit of the current value is set in CPU parameters ("Timer Limit Setting"). For details on the operation of each device, refer to the following. Page 412 DEVICES The specification method of each member is the same as that of the structure data type. ( Page 466 Structures)

Data type Member name

Member data type Description Value range

Timer TIMER S Bit Indicates a contact. The operation is the same as the contact (TS) of a timer device.

0 (FALSE), 1 (TRUE)

C Bit Indicates a coil. The operation is the same as the coil (TC) of a timer device.

0 (FALSE), 1 (TRUE)

N Word [unsigned]/bit string [16 bits]

Indicates the current value. The operation is the same as the current value (TN) of a timer device.

0 to 65535*1

Retentive timer RETENTIVETIMER S Bit Indicates a contact. The operation is the same as the contact (STS) of a retentive timer device.

0 (FALSE), 1 (TRUE)

C Bit Indicates a coil. The operation is the same as the coil (STC) of a retentive timer device.

0 (FALSE), 1 (TRUE)

N Word [unsigned]/bit string [16 bits]

Indicates the current value. The operation is the same as the current value (STN) of a retentive timer device.

0 to 65535*1

Long timer LTIMER S Bit Indicates a contact. The operation is the same as the contact (LTS) of a long timer device.

0 (FALSE), 1 (TRUE)

C Bit Indicates a coil. The operation is the same as the coil (LTC) of a long timer device.

0 (FALSE), 1 (TRUE)

N Double word [unsigned]/bit string [32 bits]

Indicates the current value. The operation is the same as the current value (LTN) of a long timer device.

0 to 4294967295*1

Long retentive timer LRETENTIVETIMER S Bit Indicates a contact. The operation is the same as the contact (LSTS) of a long retentive timer device.

0 (FALSE), 1 (TRUE)

C Bit Indicates a coil. The operation is the same as the coil (LSTC) of a long retentive timer device.

0 (FALSE), 1 (TRUE)

N Double word [unsigned]/bit string [32 bits]

Indicates the current value. The operation is the same as the current value (LSTN) of a long retentive timer device.

0 to 4294967295*1

Counter COUNTER S Bit Indicates a contact. The operation is the same as the contact (CS) of a counter device.

0 (FALSE), 1 (TRUE)

C Bit Indicates a coil. The operation is the same as the coil (CC) of a counter device.

0 (FALSE), 1 (TRUE)

N Word [unsigned]/bit string [16 bits]

Indicates the current value. The operation is the same as the current value (CN) of a counter device.

0 to 65535

Long counter LCOUNTER S Bit Indicates a contact. The operation is the same as the contact (LCS) of a long counter device.

0 (FALSE), 1 (TRUE)

C Bit Indicates a coil. The operation is the same as the coil (LCC) of a long counter device.

0 (FALSE), 1 (TRUE)

N Double word [unsigned]/bit string [32 bits]

Indicates the current value. The operation is the same as the current value (LCN) of a long counter device.

0 to 4294967295

0 28 LABELS 28.4 Data Types

28

Generic data type (ANY type) The generic data type is the data type of the labels which summarize several primitive data types. Generic data types are used when multiple data types are allowed for function and function block arguments and return values. Labels defined in generic data types can be used in any sub-level data type. For the types of generic data types and the primitive data types, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

Definable data types and initial values The following tables list the definable data types and initial value setting possibilities for each label class.

*1 The pointer type cannot be defined. *2 None of the timer, retentive timer, long timer, long retentive timer, counter, and long counter types can be defined.

The initial value of the global label where the device has been assigned follows that in the device. The initial value of the function block follows the local label setting within the function block. The initial value of the structure type follows that of the structure definition.

Global label

Class Definable data type Initial value setting possibility

VAR_GLOBAL Primitive data type, array, structure, function block

VAR_GLOBAL_CONSTANT Primitive data type*1*2

VAR_GLOBAL_RETAIN Primitive data type*1, array, structure

Local label (program block)

Class Definable data type Initial value setting possibility

VAR Primitive data type, array, structure, function block

VAR_CONSTANT Primitive data type*1*2

VAR_RETAIN Primitive data type*1, array, structure

Local label (function)

Class Definable data type Initial value setting possibility

VAR Primitive data type*2, array, structure

VAR_CONSTANT Primitive data type*1*2

VAR_INPUT Primitive data type*1*2, array, structure

VAR_OUTPUT

Return value

Local label (function block)

Class Definable data type Initial value setting possibility

VAR Primitive data type, array, structure, function block

VAR_CONSTANT Primitive data type*1*2

VAR_RETAIN Primitive data type*1, array, structure

VAR_INPUT

VAR_OUTPUT

VAR_OUTPUT_RETAIN

VAR_IN_OUT

VAR_PUBLIC

VAR_PUBLIC_RETAIN

28 LABELS 28.4 Data Types 461

46

28.5 Arrays An array represents a consecutive aggregation of same data type labels as a single name. Primitive data types and structures can be defined as arrays.

Ex.

Array image and setting in engineering tool

bLabel3 [0,0,0] [0,0,1] [0,0,3]

[0,1,0] [0,1,1]

[0,4,0] [0,4,3]

[0,0,2]

[0,1,2] [0,1,3]

[0,4,1] [0,4,2]

[1,0,0] [1,0,1] [1,0,3][1,0,2]

bLabel1 [0] [1] [3][2] bLabel2 [0,0] [0,1] [0,3]

[1,0] [1,1]

[4,0] [4,3]

[0,2]

[1,2] [1,3]

[4,1] [4,2]

[5,0,0] [5,0,1] [5,0,3][5,0,2]

[5,4,3]

Label name Index

One-dimensional array (The number of elements is 4.) Two-dimensional array (The number of elements is 5 4.)

Three-dimensional array (The number of elements is 6 5 4.)

Settings in the engineering tool

2 28 LABELS 28.5 Arrays

28

Defining arrays Array elements When an array is defined, the number of elements, or the length of array, must be determined. For the range of the number of elements, refer to the following. Page 465 Range of the number of array elements

Dimension number of multidimensional array Up to three-dimensional array can be defined.

Definition format The following table lists definition format. The range from the array start value to the array end value is the number of elements.

Initial value One initial value can be set for a single array definition. (Different initial values cannot be set for each element.) The same initial value is stored in all the array elements.

How to use arrays To use an array, add an index enclosed by '[ ]' after each label name to identify individual labels. An array with two or more dimensions should be represented with indexes delimited by a comma (,) in '[ ]'.

The following table lists the types of indexes that can be specified for arrays.

Number of array dimensions

Format Remarks

One dimension Array of primitive data type/structure name (array start value..array end value) For the primitive data type:

Page 459 Primitive data type For the structure name: Page 466 Structures

[Definition example] Bit (0..15)

Two dimensions Array of primitive data type/structure name (array start value..array end value, array start value..array end value)

[Definition example] Bit (0..1, 0..15)

Three dimensions

Array of primitive data type/structure name (array start value..array end value, array start value..array end value, array start value..array end value)

[Definition example] Bit (0..2, 0..1, 0..15)

Type Specification example Remarks Constant bLabel1[0] An integer can be specified.

Device bLabel1[D0] A word device, double-word device, decimal constant, or hexadecimal constant can be specified. (ST, LST, G, and HG cannot be specified.)

Label bLabel1[uLabel2] The following data types can be specified. Word [unsigned]/bit string [16 bits] Double word [unsigned]/bit string [32 bits] Word [signed] Double word [signed]

Expression bLabel1[5+4] Expressions can be specified only in ST language.

bLabel1 [0] bLabel2 [0,3]

Label name Index

28 LABELS 28.5 Arrays 463

46

The data storage location becomes dynamic by specifying a label for the array index. This enables arrays to be used in a program that executes loop processing. The following is a program example that consecutively stores "1234" in the "uLabel4" array.

The element number of the array can be omitted in ladder diagram. If the element number is omitted, it is regarded as the start number and converted. For example, when the defined label name is "boolAry" and the data type is "Bit (0..2, 0..2)", the operation of "boolAry[0,0]" is the same as that of "boolAry".

When a multidimensional array is specified as setting data of instructions, functions, and function blocks that use arrays, the rightmost element is regarded as a one-dimensional array.

bLabel1 INC wLabel3

bLabel2 MOV K1234 uLabel4[wLabel3]

bLabel3

wLabel1 wLabel2[0] [1] [3] [0,0] [0,3]

[1,0]

[0,1]

[1,1]

[3,0] [3,3]

[2] [0,2]

[1,2] [1,3]

[2,3][2,2][2,1][2,0]

[3,2][3,1]

BMOV wLabel1 wLabel2 K3

4 28 LABELS 28.5 Arrays

28

Range of the number of array elements The maxim number of array elements varies depending on the data type.

Precautions When an interrupt program is used When a label or device is specified for the array index, the operation is performed with a combination of multiple instructions. For this reason, if an interrupt occurs during operation of the label defined as an array, data inconsistency may occur producing an unintended operation result. To prevent data inconsistency, create a program using the DI/EI instructions that disables/enables interrupt programs as shown below.

For the DI/EI instructions, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

Array elements When accessing the element defined in an array, access it within the range of the number of elements. If a constant out of the range defined for the array index is specified, a compile error will occur. If the array index is specified with data other than a constant, a compile error will not occur. The processing will be performed by accessing another label area or latch label area.

Data type Setting range Bit Word [unsigned]/bit string [16 bits] Word [signed]

1 to 2147483648

Double word [unsigned]/bit string [32 bits] Double word [signed] Single-precision real number Time

1 to 1073741824

Timer Counter Retentive timer Long counter Long retentive timer Long timer

1 to 32768

Double-precision real number 1 to 536870912

String 1 to 67108864

String [Unicode] 1 to 33554432

Structure type Function block

1 to 32768

DI

EI

Program of the label defined as an array

28 LABELS 28.5 Arrays 465

46

28.6 Structures A structure is a data type containing one or more labels and can be used in all POUs. Members (labels) included in a structure can be defined even when their data types are different.

Creating structures To create a structure, first define the structure, and then define members in the structure.

How to use structures To use a structure, register a label using the defined structure as the data type. To specify each member in a structure, add the member name after the structure label name with a period '.' as a delimiter in between.

Ex.

Specifying a member in the structure

When labels are registered by defining multiple data types in a structure and used in a program, the order the data is stored after operation is not the order the data types were defined. When programs are converted using the engineering tool, labels are classified into type and data type, and then assigned to the memory (memory assignment by packing blocks).

GX Works3 Operating Manual If the label of a structure is specified for an instruction that uses control data (a group of operands that

determines operation of the instruction), the labels are not assigned in the order defined by packing blocks.

Member (label 1)

Member (label 2)

Member (label 3)

Member (label 4)

Structure

stLabel1 . bLabel1

Structure label name Member name

6 28 LABELS 28.6 Structures

28

Structure arrays A structure can also be used as an array.

When a structure is declared as an array, add an index enclosed by '[ ]' after the structure label name. A structure array can also be specified as an argument of a function or function block.

Ex.

Specifying an element of a structure declared as an array

Data types that can be specified The following data types can be specified as structure members. Primitive data type Pointer type Array Other structures

Types of structures Each of the following labels is predefined as a structure.

Type Reference Module label Function Block Reference for the module used

Timer type Page 459 Data Types

Retentive timer type

Counter type

Long timer type

Long retentive timer type

Long counter type

Member (label 1)

Member (label 2)

Member (label 3)

Member (label 4)

Structure label [1]

Member (label 1)

Member (label 2)

Member (label 3)

Member (label 4)

Structure label [2]

Member (label 1)

Member (label 2)

Member (label 3)

Member (label 4)

Structure label [3]

Member (label 1)

Member (label 2)

Member (label 3)

Member (label 4)

Structure label [4]

stLabel [0] . bLabel1

Structure label name

Member name Index

28 LABELS 28.6 Structures 467

46

28.7 Label Access Setting from External Device Set the parameters to enable external devices, such as GOT and SLMP-compatible devices, to specify global label names.

This function cannot be used in the R00CPU, R01CPU, and R02CPU.

GOT

Ethernet

1234Hz

External devices such as a monitoring device and personal computer (such as SLMP and MC protocol) Communication using label names and program languages such as C language and VB is possible.

External devices such as a monitoring device and personal computer GOT (GT Works3)

Label names can be specified for objects and figures.

CPU module

Configure the setting to allow the access from external devices.

Frequency

Start Stop

8 28 LABELS 28.7 Label Access Setting from External Device

28

The CPU modules with the firmware version "40" or later control global labels in the global label settings by block. One global label setting is shown as one block as below.

Set the global label setting for each label used with GOT in units of blocks. When "Perform the label name resolution in global label block unit" is selected in the GT Designer3 setting, the label name resolution after online change is processed efficiently. However, during online change that involves addition of blocks, label names are resolved collectively, not in units of blocks. For the GT Designer3 setting, refer to the following. GT Designer3 (GOT2000) Screen Design Manual The following shows an example of access to three GOT units. "Global": Global label setting that compiles labels accessed from multiple GOTs (GOT to GOT) "Global1": Global label setting that compiles labels accessed from GOT "Global2": Global label setting that compiles labels accessed from GOT "Global3": Global label setting that compiles labels accessed from GOT In this case, because global labels in each global label setting are accessed in units of blocks, the number of times of updating label communication data from GOT decreases.

Global label block

Navigation window

1 block

1 block

1 block

GOT GOT GOT

Global

Global1

Global2

Global3

Ethernet Engineering tool

CPU module

Global label setting of each block

28 LABELS 28.7 Label Access Setting from External Device 469

47

Configuration procedure This section describes the configuration procedure to enable access by specifying the global label from external devices.

Operating procedure

Data storage to the data memory, not using the SD memory card, does not need the setting of procedure 3.

Label communication data storage location and operation at the time of each setting operation This section describes the storage location for label communication data and the accessibility according to the setting of whether to use the file/data in a memory card. : Access from external device possible (Communication memory indicated in parentheses) : Access from external device not possible (Generates communication error)

*1 An error occurs in the CPU module.

File operation The label communication data can be written from an engineering tool. Reading and deleting*1 are not possible. *1 Deleting an entire folder is possible.

"Global Label Setting" window 1. Set the label in "Global Label Setting" and select the "Access from External Device" checkbox.

2. Check the capacity of the label communication data.

"Setting of File/Data Use or Not in Memory Card windows 3. Enable "Data for Label Communication" to use the label communication data stored in the SD memory card (or store the label communication data in the SD memory card).

[Memory Card Parameters] [Setting of File/Data Use or Not in Memory Card] [Data for Label Communication]

4. Write parameters, global label setting, and global label assignment information files to the CPU module.

Label communication data storage location

When "Enable" is set in the setting for the usage status of the file/data in a memory card

When "Disable" is set in the setting for the usage status of the file/data in a memory card

Data Memory *1 (Data memory)

SD memory card (SD memory card)

Data memory and SD memory card (SD memory card) (Data memory)

0 28 LABELS 28.7 Label Access Setting from External Device

28

28.8 Precautions

Functions with restrictions The following functions have restrictions on the use of labels.

*1 Global labels can be used as devices by assigning a device. *2 Global labels or local labels can be specified depending on the CPU module for the data logging function. For the CPU modules which

support the label specification, refer to the following. Page 700 Added and Enhanced Functions

Defining and using a global label with a device assigned Define a global label following the procedure below, and use it when the functions having restriction on the use of labels are executed. Since the device area in the device/label memory is used, secure the device area capacity.

1. Secure the device area to be used.

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Setting]

2. Define a label as a global label, and assign a device manually.

3. Use the label defined in step 2 for the functions having no restrictions on the use of labels. Use the device assigned to the label for the function having restrictions on the use of labels.

Copying the value of a label used to a different device If a device cannot be assigned to a global label, copy the value of the label to a different device and use the device for the function having restrictions on the use of labels. Since the device area in the device/label memory is used, secure the device area capacity.

1. Secure the device area to be used.

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Setting]

2. Create a program using the label. The following is the program example for copying the data. (The data logging function uses the data in udLabel1.)

3. Use the device where the data has been transferred in step 2 for the function having restrictions on the use of labels. (In the program example in step 2, use D0.)

The number of steps increases because of the transfer instruction. (The scan time increases.) Decide the transfer instruction position considering the timing of writing data to the label and executing the

function.

Item Description CPU parameter Trigger of an event execution type program

Refresh setting among multiple CPU modules Use devices because global labels nor local labels cannot be specified for these functions.*1

Module parameter Predefined protocol support function

Refresh setting of intelligent function module Refresh setting of network module (SB/SW only)

Use module labels for these functions. Use devices if module labels are not used.*1

Refresh setting of network module (other than SB/SW)

Use devices because global labels nor local labels cannot be specified for these functions.*1

Data logging function Memory dump function Real-time monitor function

Use devices if there is a possibility for using these functions because global labels nor local labels cannot be specified for these functions.*1*2

In addition, if a device cannot be assigned to a global label, add the transfer instruction (copying the global label to a different device) on the scan program so that the instruction is executed every scan, and use that device.

28 LABELS 28.8 Precautions 471

47

Precautions for creating programs When specifying a label as an operand used in instructions, match the data type of the label with that of the operand. In addition, when specifying a label as an operand used in instructions that control continuous data, specify the data range used in instructions within the data range of the label.

Ex.

SFT(P) instruction

Ex.

SER(P) instruction

Specify a label which has a larger data range than the search range (n) points.

Restrictions on naming labels The following restrictions apply when naming labels. Start the name with a character or underline (_). Numbers cannot be used at the beginning of label names. Reserved words cannot be used. For details on the reserved words, refer to the following. GX Works3 Operating Manual

Program of external devices When the global label which is set to the "Access from External Device" is deleted or the online change including label name change is executed, change the program of external devices that refer to the global label deleted/changed.

SET bLabel[0]

SFTP bLabel[1]

SET wLabel1.0

SFTP wLabel1.1

To shift the bits correctly, specify the array of the bit type label.

Specify the bit number of the word type label.

or

123

10

500

20

123

wLabel1[0]

wLabel1[1]

wLabel1[n+1]

-123

Start device number of search range

Data matched

Search range: (n) points

2 28 LABELS 28.8 Precautions

29

29 LATCH FUNCTION

29.1 Latch with Battery The data in each device/label of the CPU module is cleared to its default value in the following cases: When the CPU module is powered off and on When the CPU module is reset When a power failure exceeding the allowable momentary power failure time occurs The data in each device/label with latch setting is retained by using the battery on the CPU module unit even under the above described conditions. For this reason, control can be continued with the retained data even if the power of the CPU module is turned off or a power failure exceeding the allowable momentary power failure time occurs while the data is managed by a sequential control.

The R00CPU, R01CPU, and R02CPU retain the data in each device/label with latch setting without a battery during power failure. The other programmable controller CPUs retain the data in each device/label with latch setting without a battery during power failure by inserting a battery-less option cassette to the CPU module. ( Page 480 Latch with Battery-less Option Cassette)

Types of latch The following types of latch are available: Latch (1): Data in this range can be cleared by a latch clear operation Latch (2): Data in this range cannot be cleared by a latch clear operation

29 LATCH FUNCTION 29.1 Latch with Battery 473

47

Applicable devices and labels This section describes the devices/labels that can be latched.

Applicable devices The devices below can be latched. However, local devices cannot.

*1 When "Use Common File Register in All Programs" is enabled, any of the number of points is registered within the range for Latch (2). Also, the range can be specified in "Latch (2)" of "Latch Range Setting" (values out of the specified range are cleared to 0).

When "Use File Register of Each Program" is enabled, the latch range for file registers cannot be specified (the whole range for file registers is retained).

When the file register file which should be used is changed by the QDRSET instruction, the latch range setting for file registers is disabled. After the change, the whole range for file registers is retained regardless of the latch range setting.

Applicable labels The labels below can be latched.

Device Specification method Applicable latch type Internal relay (M) Specify the latch range. Latch (1) or Latch (2)

Link relay (B) Specify the latch range. Latch (1) or Latch (2)

Annunciator (F) Specify the latch range. Latch (1) or Latch (2)

Edge relay (V) Specify the latch range. Latch (1) or Latch (2)

Timer (T)/Long timer (LT)/Retentive timer (ST)/Long retentive timer (LST)

Specify the latch range. Latch (1) or Latch (2)

Counter (C) and Long counter (LC) Specify the latch range. Latch (1) or Latch (2)

Data register (D) Specify the latch range. Latch (1) or Latch (2)

Link register (W) Specify the latch range. Latch (1) or Latch (2)

Latch relay (L) Specify the number of points (latch is performed the same number of times as the specified number of points).

Latch (2) only

File register (R, ZR) Specify the number of points (latch is performed the same number of times as the specified number of points). Specify the latch range.*1

Latch (2) only

Label type Class Global label VAR_GLOBAL_RETAIN

Local label of a program block VAR_RETAIN

Local label of a function block VAR_RETAIN

VAR_OUTPUT_RETAIN

VAR_PUBLIC_RETAIN

4 29 LATCH FUNCTION 29.1 Latch with Battery

29

Setting latch on devices Multiple latch ranges can be set for a device type. A total of 32 latch ranges between latch (1) and latch (2) can be set. However, the ranges of latch (1) and latch (2) must not overlap.

Setting a latch range Set the device to latch, its range, and the latch type.

Operating procedure

"Device Setting" window 1. Click "Detailed Setting" on the "Device Setting" window.

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Detailed Setting] [Device Setting] [Detailed Setting]

2. In the "Device Setting" window, select the type of latch for the target device. The "Latch Range Setting" window is displayed.

"Latch Range Setting" window 3. Check the tab for the latch type, select the device to set and set the latch range (Start, End).

29 LATCH FUNCTION 29.1 Latch with Battery 475

47

Setting the latch interval The user can specify the operation which should be performed at a latch interval ( Page 478 Setting the latch interval) within the effective range of the latch interval setting*1. *1 The effective range of the latch interval means the range of devices which is enabled on the "The Valid Range of Latch Interval Setting"

window. For other ranges (ranges of devices which are not enabled on the "The Valid Range of Latch Interval Setting" window), this setting is not applied, the END processing is accelerated, and latching is performed in real time.

[CPU Parameter] [Memory/Device Setting] [Device Latch Interval Setting]

Operating procedure

Displayed items

"The Valid Range of Latch Interval Setting" window 1. On the "Valid Range Confirmation of Latch Interval Setting" window, check the effective range for the latch timing setting. Specify the latch interval operation within the effective range.

"Device Latch Interval Setting" window 2. In "Latch Interval Operation Setting", select the timing of the latch processing. When "Time Setting" is selected, specify the time interval of latching.

Item Description Setting range Default Latch Interval Operation Setting Sets the timing of the latch processing. Per Scan

Time Setting Time Setting

Interval Setting at Time Setting Sets the time interval of latching (when "Time Setting" is selected).

1 to 2000ms (in units of 1ms) 10ms

Valid Range Confirmation of Latch Interval Setting

Shows the effective range for the latch interval setting.

6 29 LATCH FUNCTION 29.1 Latch with Battery

29

For device latching, increasing the device range in the device setting of CPU parameters eliminates the latch processing from the END processing for the devices and enables real-time latching. For example, assume the following configuration for R04CPU: (1) 0K word is specified for the file storage area and 168K words for the device area in "Device/Label Memory Area Capacity Setting", (2) 100K points is specified for the data register (D) on the "Device Setting" window, and (3) D33151 and later are specified as the latch target devices. In this configuration, D33152 and later data registers (D) can be latched in real time as well as the devices (W, SW, and L) which are out of the effective range.

(1) D33152 or later areas of the data register (D) and areas of the devices (W, SW, and L) in disabled ranges can be latched in real time.

(1)

29 LATCH FUNCTION 29.1 Latch with Battery 477

47

Timing of the latch processing The timing of the latch processing is determined based on the effective range of the latch interval setting and the operation setting for the specified latch interval ( Page 476 Setting the latch interval) When set to "Time Setting" Latch processing is started in the END processing executed after the set time.

The more the latch points, the more it takes to complete the latch processing. If the set time elapses while latch processing is still executing, the next one is executed in the END processing that follows the completion of the previous latch processing. Set a latch interval longer than the latch processing time so that the specified time does not elapse during latch processing.

If the latch interval is shorter than the scan time, latch timing occurs more than once within one scan. However, latch processing is executed once during the END processing.

When set to "Per Scan" Latch processing is executed in the END processing of every scan. This setting allows to always retain the device of the previous scan because the devices are latched at every scan. However, it may increase the scan time.

0

0

100 300200

200

400

300

10ms10msTime setting (For 10ms)

Device memory (Values from D0 to D99)

Backup power area (Values from D0 to D99)

Program

1 scan Time elapsed Time elapsed

Write 400 to D0 to D99.

Write 300 to D0 to D99.

Write 200 to D0 to D99.

Write 100 to D0 to D99.

Data at this time is latched.

Data at this time is latched.

Latch processing

Powering off (resetting) the module at this time holds D0 to D99 = 200.

Latch processing

100

1000

200

200

300

300

Device memory (Values from D0 to D99)

Backup power area (Values from D0 to D99)

Write 100 to D0 to D99.

Write 200 to D0 to D99.

Write 300 to D0 to D99.

Program

Each scan 1 scan

Latch processing

Latch processing

Latch processing

Latch processing

Latch processing

Latch processing

Data at this time is latched.

Data at this time is latched.

Data at this time is latched.

Powering off (resetting) the module at this time holds D0 to D99 = 200.

1 scan 1 scan

8 29 LATCH FUNCTION 29.1 Latch with Battery

29

Setting latch on labels This section describes latch setting on labels.

Operating procedure

Clearing latch range data Latch range data is cleared by either of the operations below. ( Page 135 Memory Operation) Latch clear: Performed from the engineering tool. ( GX Works3 Operating Manual) Latch clear by program: Execute the RST instruction for latched devices, or clear by transferring K0 by using the MOV or

FMOV instruction.

Precautions This section describes the precautions when using the latch function. When using a CPU module other than the R00CPU, R01CPU, and R02CPU, the data in a device/label within the latch

range is retained by using the battery on the CPU module unit. Therefore, data cannot be retained during power failure if this battery runs out. Use the battery-less option cassette for retaining the data without a battery during power failure. ( Page 480 Latch with Battery-less Option Cassette)

If the latch range and number of device points are modified by using parameters, latch is performed on the modified latch range. However, if the value of the parameter setting the latch range is different between the previous and current operations because the CPU module was powered off and on or is reset, and the latch range has been increased, the device range in the increased portion is not latched.

Label edit window 1. In the label edit window, specify "RETAIN" for label attribute.

"Device/Label Memory Area Detailed Setting" window 2. There are two types of latch for labels: latch (1) and latch (2). Select one. The selected latch type is applied to labels of all latch attributes.

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Detailed Setting] [Latch Type Setting of Latch Type Label]

29 LATCH FUNCTION 29.1 Latch with Battery 479

48

29.2 Latch with Battery-less Option Cassette Programmable controller CPUs retain the data in each device/label with latch setting without a battery during power failure by inserting a battery-less option cassette to the CPU module. The applicable devices and labels and the latch setting are the same as the ones for the latch with the battery. ( Page 473 Latch with Battery)

This function cannot be used for the R00CPU, R01CPU, and R02CPU because these CPUs do not need a battery-less option cassette to retain data in latch-set devices/labels during power failure.

Usage procedure This section describes how to use the latch with the battery-less option cassette.

Setup procedure Insert/remove a battery-less option cassette / a battery while the programmable controller is powered off.

1. Insert a battery-less option cassette to the CPU module.

2. Remove the battery from the CPU module. When disconnecting the connector, pull out the connector part so as not to damage the battery cable.

3. Mount the CPU module on the base unit.

4. Power on the programmable controller.

5. Monitor SM624 (Battery-less option cassette insertion flag) and check that it is on.

Insertion of the battery-less option cassette can be checked from the following items in the engineering tool. "Product Information List" in "System Monitor" "Module Information List" in "Module Diagnostics"

6. Set "Mounted" for "Battery-less Option Cassette Setting" in "CPU Parameter" with the engineering tool.

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Setting] [Cassette Setting] [Battery- less Option Cassette Setting]

7. Set "Battery Error" of "CPU Parameter" as "Not Detected".

[CPU Parameter] [RAS Setting] [Error Detections Setting] [Battery Error]

8. Set "Time Setting" in "Module Parameter".

[Module Parameter] [Application Settings] [Time Setting] The clock data is initialized when the battery-less option cassette is initialized. Clock data cannot be retained during power failure when no battery is mounted. Therefore, set "Time Setting (SNTP Client)". ( MELSEC iQ-R Ethernet User's Manual (Application))

Open the cassette cover (1) located on the side of the CPU module. Hold the top and bottom of the protruded part (2) of the battery-less option cassette (with the notched edge facing to the right). Insert the cassette straight to the connector, taking care not to tilt it. Check the connection for looseness. Close the cassette cover (1).

(1)

(2)

0 29 LATCH FUNCTION 29.2 Latch with Battery-less Option Cassette

29

9. Write the set parameter to the CPU module, and then power off and on, or reset the CPU module.

10.When the uninitialized error is displayed, use the engineering tool to initialize the battery-less option cassette. After the initialization, power off and on, or reset the CPU module.

[Online] [CPU Memory Operation] Select "Device/Label Memory" on the "Memory Management" window, and click the [Initialization] button.

If the battery-less option cassette is initialized during execution of the latch with the battery-less option cassette, only the files in the file storage area in the device/label memory are deleted.

11. Monitor SM625 (Battery-less function execution flag) and check that it is on.

Clearing procedure Remove/insert a battery-less option cassette / a battery while the programmable controller is powered off.

1. Read the data on the device/label memory from the CPU module, and save it in advance using the engineering tool in advance. (When the battery-less option cassette is removed, all of the data on the device/label memory are erased.)

2. Power off the programmable controller.

3. Remove the CPU module from the base unit.

4. Remove the battery-less option cassette from the CPU module.

5. Install a battery to the CPU module.

6. Mount the CPU module on the base unit.

7. Power on the programmable controller.

8. Set "Not Mounted" for "Battery-less Option Cassette Setting" in "CPU Parameter" with the engineering tool.

[CPU Parameter] [Memory/Device Setting] [Device/Label Memory Area Setting] [Cassette Setting] [Battery- less Option Cassette Setting]

9. Set "Battery Error" of "CPU Parameter" to "Detect".

[CPU Parameter] [RAS Setting] [Error Detections Setting] [Battery Error]

10.Write the CPU parameter to the CPU module, and then power off and on, or reset the CPU module.

Open the cassette cover (1) located on the side of the CPU module. Hold the top and bottom of protruded part (2) of the battery-less option cassette and pull it straight, taking care not to tilt it. Close the cassette cover (1).

(1)

(2)

29 LATCH FUNCTION 29.2 Latch with Battery-less Option Cassette 481

48

Precautions This section describes precautions on using the latch with the battery-less option cassette. When a battery-less option cassette is inserted, the current consumption of the CPU module increases by 0.15A at

maximum. Insert or remove a battery-less option cassette while the programmable controller is powered off. If it is inserted or removed

while the programmable controller is powered on, a stop error occurs in the CPU module and data may not be retained. Clock data cannot be retained during power failure when no battery is mounted. Therefore, it is recommended to set "Time

Setting (SNTP Client)" in the module parameter. ( MELSEC iQ-R Ethernet User's Manual (Application)) The scan time during the execution of the latch with a battery-less option cassette is longer than the scan time of when the

latch with a battery-less option cassette is not executed. As for the instructions specifying the data retained during power failure such as the file register for the arguments, the instruction processing time will be longer. ( Page 647 Processing Time, MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks))

When the latch with a battery-less option cassette is canceled, the data retained during power failure by using the battery- less option cassette with latch setting is not taken over.

The extended SRAM cassette and battery-less option cassette cannot be used together.

2 29 LATCH FUNCTION 29.2 Latch with Battery-less Option Cassette

30

30 DEVICE/LABEL INITIAL VALUE SETTINGS This function sets the initial values of devices and labels used in the program directly (not via the program) to the devices, labels, and buffer memory areas of intelligent function modules.

(1) If initial device values are used, a program to set data to the devices becomes unnecessary.

SM402 MOV H100 D0

MOV H2020 D1

(1)

CPU module

Device initial value setting Device memory

CPU module

30 DEVICE/LABEL INITIAL VALUE SETTINGS 483

48

30.1 Setting Initial Device/Label Values This section describes the settings required to use initial device/label values.

Setting initial device values This section describes the settings of initial device values.

Setting procedure The procedure for using initial device values is as follows.

1. First, the user must create an initial device value file. To set initial values to a local device, create an initial device value file with the same name as the program which sets these values, and specify the range of the values. To set initial values to a global device, create an initial device value file (with any name) which sets these initial values, and specify the range of the values.

2. On the device memory, set up initial device value data within the range specified in the initial device value file. ( GX Works3 Operating Manual)

3. In the "Device Memory Register Diversion", select the device memory which was set up in Step 2. Setting "Device Memory Register Diversion" enables data set up on the device memory to be used as initial device values for the device which is specified in the initial device value file.

( GX Works3 Operating Manual)

4. Configure CPU parameters. ( Page 484 Initial value setting)

5. Write the set initial device value file and the CPU parameters to the CPU module. ( GX Works3 Operating Manual)

6. The data in the specified initial device value file is automatically set to the specified device or buffer memory of the intelligent function module when the CPU module is powered off and on, reset, or the status changes from STOP to RUN.

Initial value setting Configure the initial value setting.

[CPU Parameter] [File Setting] [Initial Value Setting]

Window

Displayed items

*1 If noting is specified, initial global device values are not applied. *2 It cannot be set in the R00CPU. *3 If "Target Memory" is set to "Memory card", boot a target file from the SD memory card with the boot operation. ( Page 191 BOOT

OPERATION) *4 If "Setting of Device Initial Value Use Or Not" is set to "Use" and the specified initial global device value file does not exist, an error

occurs. If the other file (initial local device value file, initial global label value file, or initial local label value file) does not exist, an initial value is not applied, but an error does not occur.

Item Description Setting range Default Target Memory Sets the storage memory for the initial device value file,

initial global label value file, and initial local label value file. Data Memory Memory Card*2*3

Data Memory

Setting of Device Initial Value Use Or Not Selects whether or not to use initial device values.*4 Not Used Use

Not Used

Global Device Initial Value File Name Sets the name of the initial global device value file.*1 60 characters or less

4 30 DEVICE/LABEL INITIAL VALUE SETTINGS 30.1 Setting Initial Device/Label Values

30

Applicable range of initial device value files The applicable range of initial device value files is as follows.

Number of initial device value settings and maximum range of one range Up to 1000 ranges can be set in one initial device value file. Up to 8000 data points can be set in one range.

Setting initial label values This section describes the settings of initial label values. For labels assigned to a device, the initial value setting follows the initial device value.

Setting procedure The procedure for using initial label values is as follows.

1. Set up initial label values using a global label and local label.

2. Configure CPU parameters ( Page 484 Initial value setting).

3. The CPU parameters, programs, initial global label value file, and initial local label value file are written to the CPU module.

( GX Works3 Operating Manual)

4. The data in the specified initial global label value file and initial local label value file is automatically set to the specified label when the CPU module is powered off and on, reset, or the status changes from STOP to RUN.

Target device Applicable range Global device Initial device values set up in the initial value file of the global device are used.

Buffer memory

Local device Initial device values set up in the initial value file of the local device (Program Name.DID) are used.

File register When "Use File Register of Each Program" is set, initial device values set up in the initial value file of the local device (Program Name.DID) are used. If there is a program which doesn't have its file register (a file register with the same name as the program), it is not assumed as an error but the initial device values are not used.

When a common file register is used across all programs, initial device values set up in the initial value file of the global device are used.

30 DEVICE/LABEL INITIAL VALUE SETTINGS 30.1 Setting Initial Device/Label Values 485

48

30.2 Applicable Devices/Labels For details on devices/labels to which initial device/label values can be set, refer to the following. GX Works3 Operating Manual

30.3 Precautions This section describes the precautions when using the initial device/label value setting. When initial device values or initial label values are overlapped with the latch range, these initial values take precedence

over the latch range. Therefore, even if a device or label is already latched, its values are changed to the specified initial values.

The initial device value and label initial value are also set when the CPU module status changes from STOP to RUN. Therefore, the initial device value and initial label value cannot be used for areas that are not desirable to be set when the CPU module status changes from STOP to RUN (because they should be set when the power is turned off and on, and changed by the program). By using the MOV instruction, for example, create a program to set an initial value to the specified device or label. In addition, if it is a module access device, make sure to write the initial value in the buffer memory by using the TO instruction.

To make the CPU module hold a device only when its values fall into the range of device initial setting (such as module access device and link direct device), the start-up time between the device and the CPU module must be synchronized using the CPU parameter, "Module Synchronous Setting".

[CPU Parameter] [Operation Related Setting] [Module Synchronous Setting]

Window

6 30 DEVICE/LABEL INITIAL VALUE SETTINGS 30.2 Applicable Devices/Labels

31

31 CONSTANTS This section describes constants.

31.1 Decimal Constant (K) Use this type of constants when specifying decimal data in a program. Specify the decimal constant using K character (e.g. K1234). The specification range depends on the argument data type of the instruction using the decimal constant as shown in the following table:

31.2 Hexadecimal Constant (H) Use this type of constants when specifying hexadecimal data in a program. Specify the hexadecimal constant using H character (e.g. H1234). To specify data in BCD, specify each digit of hexadecimal value with numerical characters 0 to 9. The specification range depends on the argument data type of the instruction using the hexadecimal constant. The range is H0 to HFFFF for 16-bit data size, and H0 to HFFFFFFFF for 32-bit data size.

Argument data type of the instruction Specification range for decimal constant

Data size Data type name 16 bit Word (signed) K-32768 to K32767

Word (unsigned)/bit string (16 bit) K0 to K65535

16-bit data K-32768 to K65535

32 bit Double word (signed) K-2147483648 to K2147483647

Double word (unsigned)/bit string (32 bit) K0 to K4294967295

32-bit data K-2147483648 to K4294967295

31 CONSTANTS 31.1 Decimal Constant (K) 487

48

31.3 Real Constant (E) Use this type of constants when specifying a real number in a program. There are two types of real numbers: single-precision real number and double-precision real number. Specify it using Echaracter. (e.g. E1.234).

Setting range for real numbers The setting ranges are different between the single-precision real number and double-precision real number.

Specification range for single-precision real numbers The following is the specification range for single-precision real numbers. -2128 < device -2-126, 0, 2-126 device < 2128

(E-3.40282347+38 to E-1.17549435-38, 0, E1.17549435-38 to E3.40282347+38)

Specification range for double-precision real number The following is the specification range for single-precision real numbers. -21024 < device -2-1022, 0, 2-1022 device < 21024

(E-1.7976931348623157+308 to E-2.2250738585072014-308, 0, E2.2250738585072014-308 to E1.7976931348623157+308)

For the number of significant digits and input range of real number data input by the engineering tool, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

Processing when operation is in progress This section describes the processing when operation is in progress.

When overflow and/or underflow occurs: If an overflow and/or underflow occurs when the operation is in progress, the following process is performed: When overflow occurs: An error is returned. When underflow occurs: 0 is returned (no error occurs).

When a special value is input: When a special value*1 is used for the input data operation, an error is returned. Note that when "-0" is generated during the operation is in progress, it is handled as "+0," and therefore "-0" is not returned as an operation result. *1 The special values include -0, denormalized number, nonnumeric number, and .

31.4 Character String Constant The character string can be specified by enclosing it with single quotation marks (' ') or double quotation marks (" "). (Example: "ABCDE") Note that the NULL character (00H) becomes the termination character.

For details on character string data, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

8 31 CONSTANTS 31.3 Real Constant (E)

31

31.5 Notation of Constants This section describes the notation of constants.

In the notation of binary, octal, decimal, hexadecimal, and real numbers, the numbers can be separated using an underscore (_) to make programs easy to see. For example, the double word [unsigned] in the notation of binary is as follows. 2#1100_1100_1100_1100 The separations by underscores (_) are ignored in program processing.

Type Notation Example Applicable data type Boolean value Set "FALSE" or "TRUE". TRUE, FALSE Bit

Add "K" or "H" before "0" or "1". K0, K1, H0, H1

Integral Binary Add "2#" before a binary number. 2#0010, 2#01101010, 2#1111_1111

Word [unsigned]/bit string [16 bits] Double word [unsigned]/bit string

[32 bits] Word [signed] Double word [signed]

Octal Add "8#" before an octal number. 8#0, 8#337, 8#1_1

Decimal Directly enter a signed or unsigned decimal number. 123, +123, -123, 12_3

Add "K" before a signed or unsigned decimal number. K123, K-123

Hexadecimal Add "16#" before a hexadecimal number. 16#FF, 16#1_1

Add "H" before a hexadecimal number. HFF, HEAD

Real number Decimal notation

Directly enter a signed or unsigned real decimal number with a decimal point.

2.34, +2.34, -2.34, 3.14_15

Single-precision real number Double-precision real number

Add "E" before a signed or unsigned real decimal number with a decimal point.

E2.34, E-2.34

Exponential notation

Add "E" and a signed or unsigned exponent (decimal) at the end of the real number.

1.0E6, 1.0E-6

Add a signed exponent (decimal) at the end of the real number with "E".

E1.001+5, E1.001-6

String String Enclose a string in single quotation marks (' '). 'ABC' String

String [Unicode]

Enclose a string in double quotation marks (" "). "ABC" String [Unicode]

Time Add "T#" or "TIME#" at the beginning. ( Page 490 Notation of time)

T#1h, T#1d2h3m4s5ms, TIME#1h

Time

31 CONSTANTS 31.5 Notation of Constants 489

49

Notation of time In the notation of time, add "T#" or "TIME#" at the beginning of the value specified in units of time; d (day), h (hour), m (minute), s (second), and ms (millisecond). The following table lists the effective range for each unit of time.

Special character (escape sequence) "$" is used as an escape sequence in a string. The following characters can be input as escape sequences with "$".

If the two hexadecimal digits following "$" do not correspond to the ASCII code, a conversion error occurs.

Item Effective range d (day) 0 to 24

h (hour) 0 to 23

m (minute) 0 to 59

s (second) 0 to 59

ms (millisecond) 0 to 999

Each unit of time can be omitted sequentially from the beginning to the end or in reverse order. T#31m23s, T#31m0s648ms

A sign can be added only before the first unit of time. T#-31m23s

An unsigned real decimal number with a decimal point can be used for the last unit of time. The values after the decimal point of ms (millisecond) are rounded down.

T#-24d20h31m23s648.123 ms (The time is treated as T#-24d20h31m23s648 ms.) T#1.2345 ms (The time is treated as T#1 ms.)

Only for the first unit of time other than d, the following values within the effective range can be input. h: 0 to 596 m: 0 to 35791 s: 0 to 2147483 ms: 0 to 2147483647

Symbol used in a string or printer code Escape sequence $ $$

' $'

" $"

Line feed $L or $l

Line break $N or $n

Page feed $P or $p

Return $R or $r

Tab $T or $t

Two hexadecimal digits and characters that correspond to the ASCII code Two hexadecimal digits following $

0 31 CONSTANTS 31.5 Notation of Constants

PA R

T 8

PART 8 TROUBLESHOOTING

This part consists of the following chapters.

32 TROUBLESHOOTING PROCEDURE

33 TROUBLESHOOTING BY SYMPTOM

34 ERROR CODES

35 EVENT LIST

491

49

32 TROUBLESHOOTING PROCEDURE This section describes errors that may occur during system operation, error causes, and actions to be taken. For the troubleshooting specific to each module, refer to the manual for the module used.

Saving the program and devices at the time of an error helps to analyze the error cause. For reading data from the programmable controller, refer to the following. GX Works3 Operating Manual

When the system has any trouble, perform troubleshooting in the following order.

1. Check the LED status of the power supply module. ( MELSEC iQ-R Module Configuration Manual)

2. Check the LED status of the CPU module. ( Page 493 LED status of the CPU module)

3. Check the LED status of each I/O module and intelligent function module. ( User's Manual (Application) for the module used)

4. Connect an engineering tool, and execute the system monitor function. The error module can be identified. ( Page 494 System monitor)

5. Select the error module, and execute the module diagnostics function. The error cause and the action to be taken can be displayed. ( Page 494 Module diagnostics)

6. If the error cause cannot be identified by the module diagnostics, check the executed operations and detected error logs on the event history window. ( Page 495 Event history)

7. If the error cause cannot be identified in steps 1 to 6, perform troubleshooting by symptom. ( User's Manual (Application) for the module used)

2 32 TROUBLESHOOTING PROCEDURE

32

32.1 Troubleshooting with LED Indicators Check the LED status of each module as primary diagnostics.

LED status of the CPU module The following table lists the check points on the LED status of the CPU module. The error status can be checked visually using the READY LED and ERROR LED.

The LED status can also be checked on the module diagnostics window using the engineering tool. ( GX Works3 Operating Manual)

LED indicator Error status Program execution status

Description Action

READY ERROR

On Off No error Continued Normal operation

On Minor error A minor error or warning has been detected. Program execution and data communications with network stations are continued.

Identify the error cause using the engineering tool, and take an action.

Flashing Moderate error Stopped A programming error, parameter setting error, or temporal noise has been detected. Program execution and data communications with network stations are stopped.

Identify the error cause using the engineering tool, and take an action.

Off On/ flashing

Major error A hardware failure has been detected. No operation cannot be performed.

Perform troubleshooting for the error module. If the problem still exists after troubleshooting, replace the error module. ( Page 496 When the READY LED of the CPU Module Turns Off)

Off Hardware failure

A hardware failure has been detected. No operation cannot be performed.

Check that the power is supplied to the system. If the power is supplied properly, the possible cause is a hardware failure. Perform troubleshooting for the error module. If the problem still exists after troubleshooting, replace the error module. ( Page 496 When the READY LED of the CPU Module Turns Off)

No error Power is not supplied or power went out.

Flashing Off No error The READY LED is flashing every 2s: Initial processing is being performed.

32 TROUBLESHOOTING PROCEDURE 32.1 Troubleshooting with LED Indicators 493

49

32.2 Troubleshooting Using the Engineering Tool Check the error or history using the engineering tool, and identify the error cause. More detailed information on the error as well as the error cause and action to be taken can be checked by using the engineering tool. The engineering tool has the following functions for troubleshooting.

For details on each function, refer to the following. GX Works3 Operating Manual

System monitor This function displays the module configuration, and detailed information and error status of each module. For the error module identified, the module diagnostics function can be executed from this window.

[Diagnostics] [System Monitor]

When the RnENCPU is used, information of the RnENCPU (CPU part) and RnENCPU (network part) is displayed individually. When an error occurs, the module diagnostics function can be executed for each module.

Module diagnostics This function diagnoses the module. (The current error and its details can be checked.) Information required for troubleshooting, such as the current error, details and cause of the error, and action to be taken, are displayed. The incorrect parameter setting and program error location can also be identified by selecting the error and clicking the [Error Jump] button. On the [Module Information List] tab, the LED status and the switch status of the target module can be checked.

[Diagnostics] [System Monitor] Double-click the error module.

In a multiple CPU system, when the I/O assignment setting in a system parameter differs from the configuration of the modules actually mounted, correct information may not be displayed on "Module Information List".

Function Description System monitor Displays the module configuration, and detailed information and error status of each module. ( Page 494

System monitor)

Module diagnostics Diagnoses the module. (The current error and its details can be checked.) ( Page 494 Module diagnostics)

Event history Displays the event information collected by the CPU module, such as errors occurred in each module, executed operations, and network errors. ( Page 495 Event history)

4 32 TROUBLESHOOTING PROCEDURE 32.2 Troubleshooting Using the Engineering Tool

32

Event history This function displays the event information, such as errors occurred in the module(s) mounted, executed operations, and network errors. Since information collected before the CPU module is powered off or reset can also be displayed, the error cause can be identified based on the past operations and errors. The displayed information can also be saved in CSV file format.

[Diagnostics] [System Monitor] [Event History] button

Use this function for the following purposes: To check the error status and identify the cause of error occurred in machinery or equipment To check when and how the program and parameters of the programmable controller have been changed To check for unauthorized access

For details on this function and collected information, refer to the following. Page 177 Event History Function

32 TROUBLESHOOTING PROCEDURE 32.2 Troubleshooting Using the Engineering Tool 495

49

33 TROUBLESHOOTING BY SYMPTOM If any function of the CPU module does not operate as designed, perform troubleshooting by checking the following items. If the ERROR LED or USER LED is on or flashing, eliminate the error cause using the engineering tool.

33.1 When the POWER LED of the Power Supply Module Turns Off

For troubleshooting, refer to the following: MELSEC iQ-R Module Configuration Manual

33.2 When the READY LED of the CPU Module Turns Off

Check the following:

If the READY LED of the CPU module does not turn on even after the items above are checked and the actions are taken, the possible cause is a hardware failure of the power supply module. Please consult your local Mitsubishi representative.

Check item Action Check if the CPU module is mounted on the main base unit properly. Remove the CPU module from the main base unit, and mount it back on the

main base unit.

Check if the READY LED of another module is on. If the READY LED of another module is on, the CPU module detected a major error. Replace the CPU module.

Check if the READY LED turns on when the power supply module is replaced and the power is restored to the system. (Check the LED status after the power supply module on the extension base unit is also replaced.)

If the READY LED turns on, an error has occurred in the power supply module(s) before the replacement. Replace the power supply module.

Check if the READY LED does not turn on even after the power supply module is replaced and the power is restored to the system. (Check the LED status after the power supply module on the extension base unit is also replaced.)

If the READY LED does not turn on, an error has occurred in a module other than the power supply module. Repeatedly supply power to the system, returning the modules back to the system one by one. The last module mounted immediately before the READY LED turned off has been failed. Replace the module.

Check if the system was powered on immediately after power-off. Wait for five seconds or longer after power-off and power on the system again.

6 33 TROUBLESHOOTING BY SYMPTOM 33.1 When the POWER LED of the Power Supply Module Turns Off

33

33.3 When the Specific Extension Base Unit Cannot Be

Recognized For troubleshooting, refer to the following: MELSEC iQ-R Module Configuration Manual

33.4 When the Specific Q Series Extension Base Unit Cannot Be Recognized

For troubleshooting, refer to the following: MELSEC iQ-R Module Configuration Manual

33.5 When Data Cannot Be Written to the Programmable Controller

Check the following:

If data cannot be written to the programmable controller even after the items above are checked and the actions are taken, the possible cause is a hardware failure. Please consult your local Mitsubishi representative.

Check item Action Check if password is not registered. Authenticate a password using the engineering tool.

Check if the SD memory card is write-protected while the SD memory card is being targeted for writing.

Clear the write-protect for the SD memory card.

When the target of the write is an SD memory card, check that the SD memory card has been formatted.

Carry out formatting for the SD memory card.

Check if the data to be written exceeds the capacity of CPU built-in memory or SD memory card.

Check the CPU built-in memory or SD memory card for their free space.

33 TROUBLESHOOTING BY SYMPTOM 33.3 When the Specific Extension Base Unit Cannot Be Recognized 497

49

33.6 When Data Cannot Be Read from the Programmable Controller

Check the following:

If data cannot be read from the programmable controller even after the items above are checked and the actions are taken, the possible cause is a hardware failure. Please consult your local Mitsubishi representative.

33.7 When the Operating Status of the CPU Module Cannot Be Changed

Check the following:

If the CPU module operating status cannot be changed even after the items above are checked and the actions are taken, the possible cause is a hardware failure. Please consult your local Mitsubishi representative.

33.8 When the Ethernet Function Cannot Be Used For troubleshooting, refer to the following: MELSEC iQ-R Ethernet User's Manual (Application)

33.9 When the CC-Link IE Field Network Basic Function Cannot Be Used

For troubleshooting, refer to the following: CC-Link IE Field Network Basic Reference Manual

Check item Action Check if password is not registered. Authenticate a password using the engineering tool.

Check if the target memory to be read is correctly specified. Check the read target memory (CPU built-in memory, SD memory card, or intelligent function module).

Check if program restoration information has not been written. When program restoration information has not been written, data cannot be read from the programmable controller. When writing data to the programmable controller, write program restoration information.

Check item Action Check if a stop error has been occurred. Check the error cause using an engineering tool and eliminate the error

cause.

Check if the online change processing is left suspended. Execute the online change again.

8 33 TROUBLESHOOTING BY SYMPTOM 33.6 When Data Cannot Be Read from the Programmable Controller

33

33.10 When the CPU Module Database Access Function

Cannot Be Used When the data source name cannot be set Check the following:

When the connection test fails When the connection test fails at the data source setting, check the following:

When the ODBC server of the CPU module cannot be connected When the ODBC server of the CPU module cannot be connected from the personal computer, check the following:

When the connection is disconnected When the connection of the personal computer and the CPU module to the ODBC server is disconnected, check the following:

Check item Action Check if use prohibited characters are used in "Data Source Name". Set "Data Source Name" without using prohibited characters.

Check if the number of use prohibited characters in "Data Source Name" exceeds the range of use.

Set "Data Source Name" with the number of characters within the range of use.

Check item Action Check if the CPU module supports the CPU module database access function.

Check that the CPU module supports the CPU module database access function. ( Page 700 Added and Enhanced Functions)

Check if the IP address of the CPU module set in "Server" is correct. Set the correct IP address of the CPU module in "Server". ( Page 328 Adding a database to the ODBC data source)

Check if 61461 is set in "Port". Set 61461 in "Port". ( Page 328 Adding a database to the ODBC data source)

Check if the absolute path of the database of the CPU module set in "Database" is correct.

Set the correct absolute path of the database in "Database". ( Page 328 Adding a database to the ODBC data source)

Check item Action Check if "invalid login/password" is displayed in the error message on the personal computer.

Check that the login name and password that are set in the module parameter of the engineering tool match those that are input to connect to the server. ( Page 326 Built-in database access setting)

Check if "cannot open connection to server; open init timeout" is displayed in the error message on the personal computer.

Check that the correct data source is selected to connect to the database of the CPU module.

Check if "Communication link failure" is displayed in the error message on the personal computer.

The maximum number of concurrently connectable databases (number of connections) is used ( Page 316 Database specifications) End unused applications connected with the database of the CPU module and connect with the database again.

Check item Action Check if the built-in database access timer setting in the module parameter of the engineering tool is too short.

Set the longer time for the built-in database access timer setting. ( Page 326 Built-in database access setting)

33 TROUBLESHOOTING BY SYMPTOM 33.10 When the CPU Module Database Access Function Cannot Be Used 499

50

34ERROR CODES The CPU module stores the corresponding error code in the special register (SD) upon detection of an error by the self- diagnostic function. If an error occurs when the data communications are requested from the engineering tool, intelligent function module, or network system connected, the CPU module returns the corresponding error code to the request source. The error details and cause can be identified by checking the error code. The error code can be checked in either of the following ways: Module diagnostics of the engineering tool ( GX Works3 Operating Manual) Special register (SD0 (Latest self-diagnostics error code), SD10 to SD25 (Self-diagnostic error number)) ( Page 602

List of Special Register Areas) This section describes errors that may occur in the CPU module and actions to be taken for the errors.

34.1 Error Code System All error codes are given in hexadecimal format (4 digits) (16-bit unsigned integer). The type of error includes the error, which is detected through the self-diagnostic function of each module, and the common error, which is detected during data communications between modules. The following table lists the error detection type and the error code ranges.

Error detection type Range Description By the self-diagnostic function of each module

Minor error 1000H to 1FFFH Error code specific to each module, such as self-diagnostic errors

Moderate error

2000H to 3BFFH

Major error 3C00H to 3FFFH

During data communications between modules 4000H to 4FFFH Error in the CPU module

6F00H to 6FFFH Error in the redundant function module

7000H to 7FFFH Error in the serial communication module

B000H to BFFFH Error in the CC-Link module

C000H to CFBFH Error in the Ethernet-equipped module

CFC0H to CFFFH Error in CC-Link IE Field Network Basic

D000H to DFFFH Error in the CC-Link IE Field Network module or CC-Link IE TSN master/ local module

E000H to EFFFH Error in the CC-Link IE Controller Network module

F000H to FFFFH Error in the MELSECNET/H network module or MELSECNET/10 network module

0 34 ERROR CODES 34.1 Error Code System

34

Detailed information Upon detection of an error by the self-diagnostic function, the detailed information of the error cause is stored together with an error code. The detailed information can be checked using the engineering tool. The following detailed information is added to each error code. (Up to two types of information are stored together with an each error code. The types differ depending on the error code.) Detailed information 1 and 2 for the latest error code can also be checked in the special register (SD). ( Page 602 List of Special Register Areas)

*1 The step number which is displayed in the error location information, is the one that is counted from the start of the file. It may differ from the step number of the program which is displayed in error jump of the engineering tool.

Detailed information Item Description Detailed information 1 Error location information*1 Information on the location in a program

Drive/file information Information on the corresponding drive name and file name

Parameter information Information on the parameter, such as parameter storage location and parameter type

System configuration information Information on the system configuration, such as I/O numbers and power supply numbers

Frequency information Information on the frequency, such as the number of writes to memory

Time information Information on time

Failure information Information on failures

Detailed information 2 Drive/file information Information on the corresponding drive name and file name

Annunciator information Information on the annunciator areas

Parameter information Information on the parameter, such as parameter storage location and parameter type

System configuration information Information on the system configuration, such as I/O numbers and power supply numbers

Program error information Program error code

34 ERROR CODES 34.1 Error Code System 501

50

34.2 Operation When an Error Occurs There are two types of errors: continuation errors and stop errors.

Stop error If a stop error occurs, the CPU module stops its operation and the operating status changes to STOP. Modules can communicate with the CPU module even after the stop error occurs in the CPU module. The external output of each module is controlled in accordance with the output mode setting in error. ( Page 169 CPU module operation upon error detection setting) Besides, if the stop error occurs when the multiple CPU system is configured, the stop error target CPU module (all CPU modules or only the corresponding CPU module) can be set in parameter. ( Page 372 Stop setting)

Continuation error If a continuation error occurs, the CPU module continues its operation. (The operating status remains the same.)

34.3 How to Clear Errors Continuation errors can be cleared. For the error clear method, refer to the following. Page 174 Error Clear

34.4 List of Error Codes Codes of errors detected by the self-diagnostic function (1000H to 3FFFH) The following table lists error codes detected by the self-diagnostic function.

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

1000H Power shutoff A momentary power failure has occurred.

The power supply has been shut off.

Continue Check the power supply status. Always

1010H Power shutoff (either of the redundant power supply modules)

Power has been shut off or the power supply voltage has dropped in either of the redundant power supply modules on the redundant power supply base unit. Or, only one redundant power supply module is mounted.

Continue Check the power supplied to the power supply modules on the base unit.

Check that two power supply modules are mounted on the base unit. If the same error code is displayed again, the possible cause is a hardware failure of the power supply module. Please consult your local Mitsubishi representative.

System configuration information

Always

1020H Failure (either of the redundant power supply modules)

A failure has been detected in either of the redundant power supply modules on the redundant power supply base unit.

Continue The possible cause is a hardware failure of the power supply module. Please consult your local Mitsubishi representative.

System configuration information

Always

1030H Invalid power supply module

An invalid power supply module has been mounted on the redundant power supply base unit.

Continue Mount only applicable power supply modules. If the same error code is displayed again, the possible cause is a hardware failure of the power supply module. Please consult your local Mitsubishi representative.

System configuration information

Always

1031H Power supply module configuration error

A power supply module other than the redundant power supply module has been mounted on the redundant power supply base unit.

Continue Mount only applicable power supply modules. If the same error code is displayed again, the possible cause is a hardware failure of the power supply module. Please consult your local Mitsubishi representative.

System configuration information

Always

2 34 ERROR CODES 34.2 Operation When an Error Occurs

34

1080H ROM write count error

The number of writes to the flash ROM (data memory, program memory, and system memory (memory used by the system when the CPU module executes its function)) exceeded 100000 times.

Files are frequently written by the event history function.

(Number of writes > 100000)

Continue Replace the CPU module. Frequency information

At power-on, at RESET, at write

1090H Battery error The voltage of the battery built in the CPU module has dropped below the specified value.

The connector of the battery built in the CPU module is disconnected.

The connector of the battery built in the CPU module is not securely connected.

Continue Replace the battery. Connect the battery connector to

use the file storage area in the device/label memory or the latch function.

Check the connection status of the battery connector. If it is loose, securely connect the connector.

Always

1100H Memory card access error

Data cannot be written to the memory card because the write protect switch is locked.

Continue Unlock the write protect switch of the memory card.

Always

1120H SNTP clock setting error

Time setting has failed when the CPU module is powered on or reset.

Continue Check if the time is correctly set in parameter.

Check if the specified SNTP server is operating normally and there is no failure on the network accessing the SNTP server computer.

At power-on, at RESET

1124H Default gateway/ gateway IP address error

The default gateway is not set correctly.

The gateway IP address is not set correctly.

The default gateway/gateway IP address (network address after the subnet mask) is different from that of the IP address of the own node.

Continue Correct the default gateway IP address.

Set the same network address as that of the IP address.

Parameter information

Always

1128H Own node port number error

The port number is incorrect. Continue Correct the port number. Always

1129H Open specification port number error

The port number setting of the external device is incorrect.

Continue Correct the port number of the external device.

Always

112CH All-station specification error

Request with all stations specification failed.

Continue Execute request with the currently specified station.

Always

112DH Specified IP address error

The IP address setting of the external device for the open processing is incorrect.

Continue Correct the IP addresses. Check if the class of the IP address

is set to A/B/C.

Always

112EH Connection establishment failed

A connection could not be established in the open processing.

Continue Check the operation of the external device.

Check if the open processing has been performed in the external device.

Check and correct the port number of the module, IP address/port number of the external device, and opening method.

When the firewall is set in the external device, check if the access is permitted.

Check if the Ethernet cable is disconnected.

Always

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 503

50

1133H Socket communications response send error

The response send failed during socket communications.

Continue Check the operation of the external device or switching hub.

Since there may be congestion of packets on the line, send data after a certain period of time.

Check if the Ethernet communication load is high because of the Ethernet functions being executed. Use the Ethernet functions so that the communication load is reduced.

Check if the connection cable is disconnected.

Check that there is no connection failure with the switching hub.

Always

1134H TCP connection timeout

A TCP ULP timeout error has occurred in the TCP/IP communication. (The external device does not send an ACK response.)

Continue Check the operation of the external device.

Check and correct the TCP ULP timeout value.

Since there may be congestion of packets on the line, send data after a certain period of time.

Check if the Ethernet communication load is high because of the Ethernet functions being executed. Use the Ethernet functions so that the communication load is reduced.

Check if the connection cable is disconnected.

Always

1152H IP address error The IP address is not set correctly. Continue Correct the IP addresses. Parameter information

Always

1155H Connection number acquisition error

The specified connection was already closed in TCP/IP communications.

Open processing is not performed.

Continue Perform the open processing for the specified connection.

Check if the open processing has been performed in the external device.

Always

1157H Receive buffer securement error

The specified connection was already closed in UDP/IP communications.

Open processing is not performed.

Continue Perform the open processing for the specified connection.

Check if the open processing has been performed in the external device.

Always

1165H UDP/IP send failed

Data was not sent correctly with UDP/ IP.

Continue Check the settings for connection with the external device.

Check the operation of the external device or switching hub.

Since there may be congestion of packets on the line, send data after a certain period of time.

Check if the Ethernet communication load is high because of the Ethernet functions being executed. Use the Ethernet functions so that the communication load is reduced.

Check if the connection cable is disconnected.

Check that there is no connection failure with the switching hub.

Execute a PING test. If the test completes with an error, take an action to correct the error.

Always

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

4 34 ERROR CODES 34.4 List of Error Codes

34

1166H TCP/IP send failed

Data was not sent correctly with TCP/ IP.

Continue Check the settings for connection with the external device.

Check the operation of the external device or switching hub.

Since there may be congestion of packets on the line, send data after a certain period of time.

Check if the Ethernet communication load is high because of the Ethernet functions being executed. Use the Ethernet functions so that the communication load is reduced.

Check if the connection cable is disconnected.

Check that there is no connection failure with the switching hub.

Execute a PING test. If the test completes with an error, take an action to correct the error.

Always

1167H Unsend data send error

Unsent data found, but could not be sent.

Continue Check the settings for connection with the external device.

Check the operation of the external device or switching hub.

Since there may be congestion of packets on the line, send data after a certain period of time.

Check if the Ethernet communication load is high because of the Ethernet functions being executed. Use the Ethernet functions so that the communication load is reduced.

Check if the connection cable is disconnected.

Check that there is no connection failure with the switching hub.

Execute a PING test. If the test completes with an error, take an action to correct the error.

Always

11A0H PID operation error

A value outside the range (TS 0) was specified for the sampling time (TS).

Continue Check and correct the sampling time (TS) value.

Error location information

At instruction execution

11A1H PID operation error

A value outside the range ( < 0 or 100 ) was specified for the input filter constant ().

Continue Check and correct the input filter constant () value.

Error location information

At instruction execution

11A2H PID operation error

A value outside the range (KP < 0) was specified for the proportional gain (KP).

Continue Check and correct the proportional gain (KP) value.

Error location information

At instruction execution

11A3H PID operation error

A value outside the range (TI < 0) was specified for the integral time (TI).

Continue Check and correct the integral time (TI) value.

Error location information

At instruction execution

11A4H PID operation error

A value outside the range (KD < 0 or 201 KD) was specified for the derivative gain (KD).

Continue Check and correct the derivative gain (KD) value.

Error location information

At instruction execution

11A5H PID operation error

A value outside the range (TD < 0) was specified for the derivative time (TD).

Continue Check and correct the derivative time (TD) value.

Error location information

At instruction execution

11A6H PID operation error

A value less than or equal to the operation cycle was specified for the sampling time (TS).

Continue Check and correct the sampling time (TS) value.

Error location information

At instruction execution

11A7H PID operation error

A process value variation (PV) overflow occurred.

Continue Check and correct the control data setting values.

Error location information

At instruction execution

11A8H A deviation (EV) overflow occurred.

11A9H An integral calculation value overflow occurred.

11AAH A derivative gain (KD) value overflow occurred.

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 505

50

11ABH PID operation error

A differential calculation value overflow occurred.

Continue Check and correct the control data setting values.

Error location information

At instruction execution

11ACH A PID operation result overflow occurred.

11ADH PID operation error

A value smaller than the output lower limit setting value was specified for the output upper limit setting value.

Continue Check and correct the output upper limit setting value or output lower limit setting value.

Error location information

At instruction execution

11AEH PID operation error

A value smaller than 0 was specified for the input variation amount warning setting value or output variation amount warning setting value.

Continue Change the input variation amount warning setting value or output variation amount warning setting value to a value greater than 0.

Error location information

At instruction execution

11AFH PID operation error

The deviation when starting auto tuning (step response method) became 150 or less.

The deviation when finishing auto tuning (step response method) was 1/3 or greater than the deviation when starting.

Continue Check and correct the control data. If the deviation when starting auto

tuning (step response method) is not 150 or more, specify a set value for auto tuning.

Error location information

At instruction execution

11B0H PID operation error

The movement direction assumed from the relationship between the set value and process value when starting auto tuning (step response method) and the output value movement direction do not match.

Continue Perform auto tuning again after correcting the relationship between the set value, auto tuning (step response method) output value, and process value.

Check and correct the control data.

Error location information

At instruction execution

11B1H PID operation error

The input value (PV) did not change correctly, and auto tuning (step response method) did not function normally.

Continue Set a long time for the sampling time (TS).

Set a larger value for the input filter constant ().

Check the input value (PV).

Error location information

At instruction execution

11B2H PID operation error

A value equal to or lower than the output lower limit (LLV) was specified for the auto tuning (limit cycle method) output upper limit (ULV).

Continue Check and correct the output upper limit (ULV) and output lower limit (LLV) values.

Error location information

At instruction execution

11B3H PID operation error

A value outside the range (SHPV < 0) was specified for the auto tuning (limit cycle method) process value threshold (hysteresis) width (SHPV).

Continue Check and correct the process value threshold (hysteresis) width (SHPV) setting value.

Error location information

At instruction execution

11B4H PID operation error

The system area used for auto tuning (limit cycle method) was rewritten.

Continue Check whether the occupied system area has been rewritten with the PID instruction.

Error location information

At instruction execution

11B5H PID operation error

As the auto tuning (limit cycle method) process time was exceeded, it was not possible to properly acquire the and on time. (on > , on < 0, < 0)

Continue Increase the difference (ULV-LLV) between the auto tuning output value upper and lower limits, or reduce the input filter constant () and auto tuning process value threshold (hysteresis) width (SHPV) values.

Error location information

At instruction execution

11B6H PID operation error

An overflow occurred with the proportional gain (KP) calculated when performing auto tuning (limit cycle method).

Continue Ensure that the process value (PV) change increases.

Reduce the difference (ULV-LLV) between the auto tuning output value upper and lower limits.

Error location information

At instruction execution

11B7H PID operation error

The integral time (TI) calculated when performing auto tuning (limit cycle method) was outside the 0 to 32767 range.

Continue Increase the difference (ULV-LLV) between the auto tuning output value upper and lower limits, or reduce the input filter constant () and auto tuning process value threshold (hysteresis) width (SHPV) values.

Error location information

At instruction execution

11B8H The derivative time (TD) calculated when performing auto tuning (limit cycle method) was outside the 0 to 32767 range.

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

6 34 ERROR CODES 34.4 List of Error Codes

34

1200H Module moderate error

A moderate error has been notified from the intelligent function module connected.

Stop/ continue

Check the detailed information (system configuration information) of the error by executing module diagnostics using the engineering tool, identify the error module, and eliminate the error cause.

System configuration information

Always

1210H An inter-module synchronous signal error has been notified from the intelligent function module connected.

Continue

1220H Another CPU module moderate error

A moderate error has been notified from another CPU module.

Stop/ continue

Check the detailed information (system configuration information) of the error by executing module diagnostics using the engineering tool, identify the error module, and eliminate the error cause.

Check the mounting status and reset status of other CPU modules.

System configuration information

Always

1240H Inter-module synchronization processing error

The execution interval of a synchronous interrupt program has exceeded the set value.

The inter-module synchronous interrupt program (I44) did not complete within the inter-module synchronization cycle.

Continue Check the detailed information (time information) of the error by executing module diagnostics using the engineering tool, check the time setting, and take the following actions:

(1) Check and correct the processing of the interrupt program (I44) so that it can be completed within the period specified in the fixed scan interval setting.

(2) Check and correct the fixed scan interval setting value.

Time information

At interrupt occurrence

1241H Inter-module synchronization processing error

The execution interval of a synchronous interrupt program has exceeded the set value.

A cycle where the inter-module synchronous interrupt program (I44) was not executed was detected.

Continue Check and correct the interrupt disable sections and the interrupt programs with a high priority so that the inter-module synchronous interrupt program can be executed.

At interrupt occurrence

1260H Multiple CPU synchronization processing error

The execution interval of a synchronous interrupt program has exceeded the set value.

The multiple CPU synchronous interrupt program (I45) did not complete within the multiple CPU fixed scan communication cycle.

Continue Check the detailed information (time information) of the error by executing module diagnostics using the engineering tool, check the time setting, and take the following actions:

(1) Check and correct the processing of the interrupt program (I45) so that it can be completed within the period specified in the fixed scan interval setting.

(2) Check and correct the fixed scan interval setting value.

Time information

At interrupt occurrence

1262H The program execution section of a synchronous interrupt program has been exceeded.

The multiple CPU synchronous interrupt program (I45) did not complete within the program execution section.

1800H Annunciator ON The annunciator (F) on status has been detected.

Continue Check the detailed error information (annunciator information) by executing module diagnostics using the engineering tool, and correct the program corresponding to the displayed annunciator number.

Error location information and annunciator information

At instruction execution

1830H Receive queue full

The number of transient receive request exceeded the upper limit of simultaneously processable requests.

Continue Reduce the frequency of transient transmission, and perform transmissions again.

Increase the frequency of transient transmission by using the COM instruction.

Always

1831H Receive processing error

Transient reception failed. Continue Reduce the frequency of transient transmission, and perform transmissions again.

System configuration information

Always

1832H Transient data error

Too much transient transmission processing exists and transient transmission cannot be performed.

Continue Correct the number of transient transmission executions.

Always

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 507

50

1900H Constant scan time error

The scan time exceeded the constant scan time set in the CPU parameters.

Continue Check and correct the constant scan time setting.

Time information

At END instruction execution

2000H Module configuration error

The module type set in the system parameters ("I/O Assignment Setting") differs from that of the module actually mounted.

Stop Re-set the module type in the system parameters in accordance with the CPU module or intelligent function module actually mounted.

System configuration information

At power-on, at RESET

2001H Module configuration error

The I/O numbers set in the system parameters ("I/O Assignment Setting") are overlapping between modules.

Stop Re-set the I/O numbers in the system parameters in accordance with the intelligent function module or I/O module actually mounted.

System configuration information

At power-on, at RESET

2002H Module configuration error

The number of points assigned to the intelligent function module in the system parameters ("I/O Assignment Setting") is smaller than that of the module actually mounted.

Stop Re-set the number of points in the system parameters in accordance with the intelligent function module actually mounted.

System configuration information

At power-on, at RESET

2004H Module configuration error

Nine or more CC-Link IE Controller Network modules and/or MELSECNET/H network modules are mounted in the entire system. (The CC-Link IE built-in Ethernet interface module is included if the module is used as a CC-Link IE Controller Network module.)

Five or more MELSECNET/H network modules are mounted in the entire system.

Stop Reduce the number of CC-Link IE Controller Network modules and/or MELSECNET/H network modules to eight or less in the entire system. (The CC-Link IE built-in Ethernet interface module is included if the module is used as a CC-Link IE Controller Network module.)

Reduce the number of MELSECNET/H network modules to four or less in the entire system.

System configuration information

At power-on, at RESET

2005H Module configuration error

Two or more interrupt modules (QI60) with no interrupt pointer setting are mounted.

The interrupt pointer numbers are overlapping in the interrupt module (QI60) with no interrupt pointer setting and a module with an interrupt pointer setting.

Stop Mount only one QI60 in the entire system.

Configure the interrupt pointer setting for the QI60.

Correct the interrupt pointer setting.

System configuration information

At power-on, at RESET, at STOP RUN state

2006H Module configuration error

A module is mounted on the 65th slot or later.

Stop Remove the module mounted on the 65th slot or later.

System configuration information

At power-on, at RESET

2007H Module configuration error

A module is mounted on the slot whose number is later than that specified in the system parameters ("I/O Assignment Setting").

Stop Remove the module mounted on the slot whose number is later than that specified in the system parameters.

System configuration information

At power-on, at RESET

2008H Module configuration error

A module is mounted over or across the maximum number of I/O points (4096).

Stop Remove the module mounted over or across the maximum number of I/ O points (4096).

Replace the module mounted on the last slot with the one that does not exceed the maximum number of I/O points (4096).

System configuration information

At power-on, at RESET

2009H Module configuration error

There is no response from the I/O module or intelligent function module accessed.

Stop Check and correct the I/O assignment setting in the system parameters.

Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the I/O module or intelligent function module. Please consult your local Mitsubishi representative.

System configuration information

Always

200AH Module configuration error

Several different series of MELSECNET/H network modules are managed by one CPU module.

Stop The series of MELSECNET/H network modules that are managed by one CPU module should be the same.

System configuration information

At power-on, at RESET

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

8 34 ERROR CODES 34.4 List of Error Codes

34

200BH Module configuration error

Recorder module or camera recorder module for which the module parameters have not been set is mounted.

There are two or more recorder modules or camera recorder modules that are set to "main".

The recorder module or camera recorder module that is set to "main" does not exist.

The CPU module or the recorder module that does not support the "sub" of the camera recorder module is mounted.

Stop Remove the recorder module or the camera recorder module for which the module parameters have not been set.

Use only one recorder module or one camera recorder module set to "main".

Mount the recorder module or the camera recorder module set to "main".

Check the firmware version of the module and use the appropriate version.

System configuration information

At power-on, at RESET

2020H Module configuration error

There is a mounted module that is not supported, or there is a mounted module that is not supported by the network type (module model name) set in system parameters ("I/O Assignment Setting").

Stop Remove the unsupported module if any.

Check whether modules are supported by the network type (module model name) set in the system parameters.

If all the modules are supported, the possible cause is a hardware failure of the CPU module, base unit, I/O module, or intelligent function module. Please consult your local Mitsubishi representative.

System configuration information

At power-on, at RESET

2021H Module configuration error

In a multiple CPU system, the control CPU of the Q series intelligent function module incompatible with the multiple CPU system is set to other than CPU No.1.

Stop Replace the Q series intelligent function module with the one (function version B) compatible with the multiple CPU system.

Set the control CPU of the Q series intelligent function module incompatible with the multiple CPU system to CPU No.1.

System configuration information

At power-on, at RESET

2022H Module configuration error

A power supply module other than the redundant power supply module has been mounted on the redundant power supply base unit.

Stop Mount only the redundant power supply module. If the same error code is displayed again, the possible cause is a hardware failure of the power supply module, CPU module, or base unit. Please consult your local Mitsubishi representative.

System configuration information

At power-on, at RESET

2040H CPU module configuration error

The number of CPU modules set in the system parameters ("I/O Assignment Setting") differs from the number of CPU modules actually mounted.

The CPU module is mounted on the slot different from the one specified in the system parameters (I/O assignment setting).

Two or more Safety CPUs are mounted.

Stop Correctly set the number of CPU modules (including the empty setting) in the system parameters in accordance with the number of CPU modules actually mounted.

Correctly set the system parameters so that the setting and actual CPU module mounting status will be the same.

Mount only one Safety CPU.

System configuration information

At power-on, at RESET

2041H CPU module configuration error

The CPU module is not mounted on the slot that is set for the CPU module in the system parameters ("I/O Assignment Setting").

The CPU module is mounted on the slot that is set for empty in the system parameters ("I/O Assignment Setting").

An I/O module or intelligent function module is mounted between the CPU modules.

Arrangement of CPU modules mounted is not appropriate to configure a multiple CPU system.

Stop Check and correct the I/O assignment setting in the system parameters.

Correctly set the number of CPU modules (including the empty setting) in the system parameters in accordance with the number of CPU modules actually mounted.

Remove the I/O module or intelligent function module mounted between the CPU modules.

System configuration information

At power-on, at RESET

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 509

51

2043H CPU module configuration error

The CPU module is mounted on the inapplicable slot.

Stop Mount the CPU module on the applicable slot (CPU slot or I/O slot 0 to 6).

Remove the CPU module from the inapplicable slot.

System configuration information

At power-on, at RESET

2044H CPU module configuration error

The host CPU No. set in the system parameters ("I/O Assignment Setting") differs from the one determined by the mounting position of the CPU module.

Stop Re-set the host CPU No. in the system parameters in accordance with the mounting position of the CPU module.

System configuration information

At power-on, at RESET, at STOP RUN state

2046H CPU module configuration error

Another CPU module was accessed, but there was no response.

Stop Check and correct the I/O assignment setting in the system parameters.

Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of another CPU module. Please consult your local Mitsubishi representative.

System configuration information

Always

2050H CPU module configuration error

An unsupported CPU module is mounted.

Stop Remove the unsupported CPU module. If all the CPU modules are supported, the possible cause is a hardware failure of the CPU module or base unit. Please consult your local Mitsubishi representative.

System configuration information

At power-on, at RESET

2060H Base unit configuration error

Eight or more extension base units are connected.

Stop Reduce the number of extension base units to seven or less.

System configuration information

At power-on, at RESET

2061H Base unit configuration error

Any of the following base units is connected: QA1S3B, QA1S5B/ QA1S6B, QA6B, QA6ADP+A5B/ A6B, or QA1S6ADP-S1+A1S5B/ A1S6B.

Stop Remove the inapplicable base unit: QA1S3B, QA1S5B/QA1S6B, QA6B, QA6ADP+A5B/A6B, and QA1S6ADP-S1+A1S5B/ A1S6B.

System configuration information

At power-on, at RESET

2063H Base unit configuration error

Extension base unit levels are overlapping.

Stop Check and correct the level setting of the extension base units.

System configuration information

At power-on, at RESET

2070H Base unit configuration error

An unsupported base unit is connected.

A GOT is bus-connected to the Q series extension base unit.

Stop Check the firmware version of the CPU module, and replace the CPU module with the one supporting the use of redundant extension base units.

Disconnect the unsupported base unit. If all the base units are supported, the possible cause is a hardware failure of the CPU module or base unit. Please consult your local Mitsubishi representative.

Disconnect the GOT bus-connected to the Q series extension base unit.

System configuration information

At power-on, at RESET

2080H Inter-module synchronization configuration error

An inter-module synchronization signal error has been detected.

Stop The possible cause is a hardware failure of the CPU module, base unit, or module (I/O module or intelligent function module) connected. Please consult your local Mitsubishi representative.

System configuration information

At power-on, at RESET

2100H Memory error No extended SRAM cassette is inserted.

The capacity of extended SRAM cassette set in does not match "Extended SRAM Cassette Setting" in the CPU parameter with the actual capacity of the cassette inserted.

Stop Check that an extended SRAM cassette is inserted. Or, correct the capacity set in "Extended SRAM Cassette Setting" in the CPU parameter so that it matches with the actual capacity of the cassette inserted. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or extended SRAM cassette. Please consult your local Mitsubishi representative.

Drive/file information, parameter information

At power-on, at RESET

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

0 34 ERROR CODES 34.4 List of Error Codes

34

2101H Memory error An extended SRAM cassette or a battery-less option cassette is inserted or removed while the programmable controller is powered on.

Stop Do not insert or remove an extended SRAM cassette or a battery-less option cassette during operation.

Check if an extended SRAM cassette or a battery-less option cassette is securely inserted to the CPU module. If the same error code is displayed again, the possible cause is a hardware failure of the extended SRAM cassette or battery- less option cassette. Please consult your local Mitsubishi representative.

Drive/file information

Always

2102H Memory error An error has been detected in the extended SRAM cassette or the battery-less option cassette.

Stop Check if an extended SRAM cassette or a battery-less option cassette is securely inserted to the CPU module. If the same error code is displayed again, the possible cause is a hardware failure of the extended SRAM cassette, battery- less option cassette, or CPU module. Please consult your local Mitsubishi representative.

Drive/file information

Always

2103H Memory error An unsupported extended SRAM cassette or battery-less option cassette is inserted.

Stop Replace the extended SRAM cassette or battery-less option cassette with the one supported by the CPU module.

Drive/file information

Always

2104H Memory error A battery-less option cassette with the factory default settings or one that was used in another CPU module is inserted.

Stop Initialize the battery-less option cassette. (To initialize the battery, use the engineering tool and select [Online] - [CPU Memory Operation] - [Device/Label Memory].) If the same error code is displayed again, the possible cause is a hardware failure of the battery-less option cassette or CPU module. Please consult your local Mitsubishi representative.

At power-on, at RESET

2105H Memory error "Battery-less Option Cassette Setting" in the CPU parameter is set as " "Mounted", but no battery-less option cassette is inserted.

Stop Check that a battery-less option cassette is inserted. Or, correct "Battery-less Option Cassette Setting" in the CPU parameter. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or battery- less option cassette. Please consult your local Mitsubishi representative.

Drive/file information, parameter information

At power-on, at RESET

2106H Memory error "Battery-less Option Cassette Setting" in the CPU parameter is set as " "Not Mounted", but a battery-less option cassette is inserted.

Stop Remove the battery-less option cassette. Or, correct "Battery-less Option Cassette Setting" in the CPU parameter. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Drive/file information, parameter information

At power-on, at RESET

2120H Memory card error

The memory card was removed without the card being disabled.

Stop/ continue

Disable the memory card, and then remove it.

Drive/file information

Always

2121H Memory card error

An error has been detected in the memory card.

Stop/ continue

Format the memory card, re-insert the memory card, or replace the memory card. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Drive/file information

Always

2122H Memory card error

The CPU module did not start because the memory card was not restored during the startup processing.

Stop Reset the CPU module. If the same error code is displayed again, the possible cause is a hardware failure of the memory card. Replace the memory card.

Drive/file information

At power-on, at RESET

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 511

51

2150H Initial processing time error

Since the initial processing takes time, the host CPU in a multiple CPU system cannot respond to communication requests from other CPU modules in initial communications. (Other CPU modules cannot start up.)

Stop Take the following action to shorten the initial processing time. Check and correct the restoration

setting and the number of files to be restored if the automatic data restoration function is being executed.

At power-on, at RESET

2160H IP address duplication error

Overlapping IP addresses have been detected.

Stop Check and correct the IP addresses. Always

2180H Invalid file An invalid file has been detected. Stop Check the detailed information (drive/file information) of the error by executing module diagnostics using the engineering tool, select the correct file name, and write the specified file to the CPU module. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Drive/file information

At power-on, at RESET, at STOP RUN state

2181H Invalid file Due to firmware update or restoration (after the firmware update) of the CPU module, a program file of which file structure is not supported by the new version of the firmware or the operation mode of the CPU module has been written.

Stop After reading program files from the programmable controller, format the memory and write the program files. Then, reset the CPU module and run it again.

Drive/file information

At power-on, at RESET

2182H Invalid file The program file is incorrect. Or, the program file is not correctly written.

Stop Write the program file to the CPU built-in memory again.

Drive/file information

At power-on, at RESET

21A0H File specification error

The file specified in the CPU parameters does not exist.

The memory card is disabled by tuning on SM606 (SD memory card forced disable instruction).

The file register file does not exist in the specified memory when the file register setting is set to "Use Common File Register in All Programs" and the file capacity is not set in the CPU parameters ("File Setting").

The file specified in the memory card parameters ("Boot Setting") does not exist in the memory card.

Stop Turn off SM606. (Cancel the disabled state.)

Check the detailed information (drive/file information) of the error by executing module diagnostics using the engineering tool, select the correct file name, and write the specified file to the CPU module. If the same error code is displayed again, the possible cause is a hardware failure of the device/label memory in the CPU module, memory card, or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Drive/file information, parameter information

At instruction execution, at interrupt occurrence, at power-on, at RESET, at STOP RUN state, at END instruction execution

21A1H File specification error

The file specified in parameter cannot be created.

Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool, and correct the name and size of the file corresponding to the displayed parameter number.

Check the detailed information (drive/file information) of the error by executing module diagnostics using the engineering tool, and take the following actions:

(1) Format the corresponding drive. (2) Delete unnecessary files on the

corresponding drive to increase free space.

(3) Unlock the corresponding drive if it is locked.

Drive/file information, parameter information

At write, at power-on, at RESET, at STOP RUN state

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

2 34 ERROR CODES 34.4 List of Error Codes

34

21A2H File specification error

The CPU module model set to the file using the engineering tool differs from that of the CPU module actually mounted.

Stop Check the detailed information (drive/file information) of the error by executing module diagnostics using the engineering tool, and correct the CPU module model set to the file in accordance with that of the CPU module actually mounted.

Drive/file information

At write, at power-on, at RESET, at STOP RUN state

2200H Parameter error The system parameter file and CPU parameter file do not exist.

The memory card parameter file or module extension parameter file stored in the memory card cannot be accessed because the memory card is disabled by turning on SM606 (SD memory card forced disable instruction).

Stop Write the system parameter file and CPU parameter file to the CPU module.

Turn off SM606. (Cancel the disabled state.)

Parameter information

At power-on, at RESET, at STOP RUN state

2220H Parameter error The parameter setting is corrupted. Parameters that the firmware version

of the corresponding CPU does not support are written.

Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool, and write the displayed parameter setting to the CPU module. If the same error code is displayed again, the possible cause is a hardware failure of the data memory in the CPU module, memory card, or module (SIL2 function module, safety function module, I/O module, or intelligent function module) connected. Please consult your local Mitsubishi representative.

Check the firmware version of the CPU module and use a supported product. Then, write parameters again.

Parameter information

At power-on, at RESET, at STOP RUN state, at write

2221H Parameter error The set value is out of range. Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool and correct the parameter setting corresponding to the displayed number. If the same error code is displayed again, the possible cause is a hardware failure of the data memory in the CPU module, memory card, or module (SIL2 function module, safety function module, I/O module, or intelligent function module) connected. Please consult your local Mitsubishi representative.

Parameter information

At power-on, at RESET, at STOP RUN state, at END instruction execution, at instruction execution, at module access

An unsupported parameter exists. Other than 1 is set to the group number

in the CC-Link IEF Basic setting. For the simple CPU communication

function, "Initial Communication Setting" is enabled.

Stop Check the firmware version of the CPU module and use a supported product. Use the product in a supported category. Set the number of occupied stations

so that the total number is 16 stations or less, and set 1 to the group number.

Disable "Initial Communication Setting".

Parameter information

At power-on, at RESET, at STOP RUN state, at END instruction execution, at instruction execution, at module access

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 513

51

2222H Parameter error Use of the function that is not supported by the module is enabled in parameter.

The module is non-operational. Parameters that the firmware version

of the module does not support were written.

Stop Remove the unsupported module if any.

Use functions supported by the module.

Check the status of the module. Check the firmware version of the

module and use a supported product.

Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool and correct the parameter setting corresponding to the displayed number. If the same error code is displayed again, the possible cause is a hardware failure of the data memory in the CPU module, memory card, or module (SIL2 function module, safety function module, I/O module, or intelligent function module) connected. Please consult your local Mitsubishi representative.

Parameter information

At power-on, at RESET, at STOP RUN state

2223H Parameter error The parameter that needs a reset of the CPU module was modified and overwritten.

Stop Reset the CPU module and run it again.

Parameter information

Always

2224H Parameter error A memory area cannot be ensured. A global label setting file exists when

the label assignment area set in the CPU parameters is 0K word.

Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool, display the error-detected area by clicking the [Error Jump] button, and increase the capacity of the area. (If the capacity of the area cannot be increased, decrease the capacity of other areas.)

Reduce the number of labels or local devices used.

If no global label is used, delete the global label setting file.

Parameter information

At write, at power-on, at RESET, at STOP RUN state

2225H Parameter error The CPU module model set to the project using the engineering tool differs from that of the CPU module actually mounted.

The operation set in the memory card parameters cannot be performed.

(The boot function cannot be executed.)

Stop Correct the CPU module model set to the project in accordance with the CPU module actually mounted.

Delete the memory card parameter settings.

Remove the memory card so that the operation set in the memory card parameters will not be performed. (Do not execute the boot operation.)

Parameter information

At write, at power-on, at RESET, at STOP RUN state

2226H Parameter error The SFC setting in the CPU parameters is incorrect. (Block 0 was set to start automatically, however, block 0 does not exist.)

Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool and correct the parameter setting corresponding to the displayed number.

Parameter information

At power-on, at RESET, at STOP RUN state, at SFC program execution

2227H Parameter error The execution type of the SFC program set in the CPU parameter program settings is other than the scan execution type.

Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool and correct the parameter setting corresponding to the displayed number.

Parameter information

At power-on, at RESET, at STOP RUN state

2228H Parameter error The memory area set by the parameter cannot be secured.

Stop Check the firmware version of the CPU module and use a supported product. Then, write parameters again.

Parameter information

At power-on, at RESET, at STOP RUN state

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

4 34 ERROR CODES 34.4 List of Error Codes

34

2240H Parameter error (module)

In a multiple CPU system, the I/O module or intelligent function module controlled by another CPU module is specified in the module parameters.

Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool and correct the parameter setting corresponding to the displayed number. If the same error code is displayed again, the possible cause is a hardware failure of the data memory in the CPU module or the module (I/O module or intelligent function module) connected. Please consult your local Mitsubishi representative.

Parameter information

At power-on, at RESET, at STOP RUN state

2241H Parameter error (module)

The I/O numbers set in the system parameters differ from those of the module actually mounted.

The target module is not mounted on the slot where the system parameters and module parameters are set.

The module type set in parameter differs from that of the module actually mounted.

Stop Check if the system configuration displayed on the system monitor window of the engineering tool match the actual system configuration.

Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool and correct the parameter setting corresponding to the displayed number. If the same error code is displayed again, the possible cause is a hardware failure of the data memory in the CPU module or the module (I/O module or intelligent function module) connected. Please consult your local Mitsubishi representative.

Parameter information

At power-on, at RESET, at STOP RUN state, at END instruction execution, at instruction execution, at module access

2242H Parameter error (module)

The intelligent function module has detected a module parameter error.

Stop Check the detailed information (system configuration information) of the error by executing module diagnostics using the engineering tool, and check the module corresponding to the displayed I/O number. If the same error code is displayed again, the possible cause is a hardware failure of the data memory in the CPU module or the intelligent function module connected. Please consult your local Mitsubishi representative.

System configuration information

At power-on, at RESET, at STOP RUN state

2260H Parameter error (network)

Network numbers are overlapping. Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool and correct the parameter setting corresponding to the displayed number. If the same error code is displayed again, the possible cause is a hardware failure of the data memory in the CPU module or the intelligent function module connected. Please consult your local Mitsubishi representative.

Parameter information

At power-on, at RESET

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 515

51

2261H Parameter error (network)

Different network types (CC IE Control extended mode/normal mode) are set between the control station and the normal station.

Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool and correct the parameter setting corresponding to the displayed number. If the same error code is displayed again, the possible cause is a hardware failure of the data memory in the CPU module or the intelligent function module connected. Please consult your local Mitsubishi representative.

Parameter information

At power-on, at RESET, at STOP RUN state

2262H Parameter error (network)

When the station number of the MELSECNET/H network module is 0, parameters of PLC to PLC network are set.

The station type set in the module parameters differs from that of the module actually mounted.

Parameters that the firmware version of the CC-Link IE TSN master/local module does not support are written.

Stop Correct the station number of the MELSECNET/H network module.

Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool and correct the parameter setting corresponding to the displayed number. If the same error code is displayed again, the possible cause is a hardware failure of the data memory in the CPU module or the intelligent function module connected. Please consult your local Mitsubishi representative.

Check the firmware version of the CC-Link IE TSN master/local module and use a supported product. Then, write parameters again.

Parameter information

At power-on, at RESET, at STOP RUN state

2263H Parameter error (network)

Even though the CC-Link IE module or MELSECNET/H network module is mounted, a different CC-Link IE module or MELSECNET/H network module is set in the system parameters ("I/O Assignment Setting"), or CC-Link IE module or MELSECNET/H network module parameters have not been set.

Stop Set the system parameters and module parameters. If the same error code is displayed again, the possible cause is a hardware failure of the data memory in the CPU module or the intelligent function module connected. Please consult your local Mitsubishi representative.

Parameter information

At power-on, at RESET, at STOP RUN state

2280H Parameter error (refresh)

The refresh setting is not set correctly. (Data were refreshed exceeding the file register capacity.)

The refresh settings (number of points) are different from those of other numbered CPU modules.

Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool, and correct the parameter setting corresponding to the displayed number so that the data are refreshed within the specified device range. (Take the following actions: increase the number of file register points, create a file register file having a capacity for all of the target data to be refreshed, or reduce the refresh device range.)

Rewrite the refresh settings (number of points) in the CPU parameters for all the CPU modules. (Use the same number of points in the refresh settings for all the CPU modules.)

Parameter information

At power-on, at RESET, at STOP RUN state, at END instruction execution, at instruction execution, at module access

2281H Parameter error (refresh)

A device that cannot be used as a refresh device is specified.

Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool and correct the parameter setting corresponding to the displayed number.

Parameter information

At power-on, at RESET, at STOP RUN state

2282H The number of specified refresh points is invalid.

2283H The total number of refresh points exceeded the maximum limit.

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

6 34 ERROR CODES 34.4 List of Error Codes

34

22E0H Parameter verification error

In a multiple CPU system, the system parameter settings of the host CPU module differ from those of other CPU modules.

In a multiple CPU system, the system parameter settings are overwritten only to the host CPU module, and the settings differ from those of other CPU modules.

Stop Check the detailed information (parameter information) of the error by executing module diagnostics using the engineering tool, and correct the system parameter settings corresponding to the displayed number for the CPU No.2 and later. The settings need to be the same among all the CPU modules. (The module synchronization setting and fixed scan communication setting need to be the same between the CPU modules that use these functions.)

When the system parameter settings are changed, update the settings of all the CPU modules connected. (The system parameter settings must be same in all the CPU modules.)

Parameter information, system configuration information

At write, at power-on, at RESET, at STOP RUN state

2300H Security key authentication error

The security key set to the program does not match the one registered to the CPU module (or cassette).

Stop Check and correct the security key setting.

Drive/file information

At power-on, at RESET, at STOP RUN state2301H The security key is set to the program,

but it is not registered to the CPU module (or cassette).

2302H Security key authentication error

The security key set to the file is corrupted and does not match the one registered to the CPU module.

The security key registered to the CPU module is corrupted and does not match the one set to the file.

Stop Write the file to the CPU module again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

At power-on, at RESET, at STOP RUN state

2303H Security key authentication error

The security key is registered to the CPU module and cassette.

Stop Check and correct the security key setting.

At power-on, at RESET, at STOP RUN state

2320H Remote password setting error

The start I/O number of the remote password target module is set to other than 0H to 0FF0H.

There is a problem on the slot specified by the start I/O number of the remote password setting.

(1) No module is mounted. (2) The mounted intelligent function

module does not support the remote password setting.

Stop Set the start I/O number of the remote password target module within the range 0H to 0FF0H.

On the specified slot, mount an intelligent function module that supports the remote password setting.

System configuration information

At power-on, at RESET, at STOP RUN state

2321H Remote password setting error

In a multiple CPU system, the module controlled by another CPU module is specified by the start I/O number of the remote password setting.

Stop Check and correct the remote password setting.

System configuration information

At power-on, at RESET, at STOP RUN state

2400H Module verification error

The module information at power-on differs from the information of modules actually mounted.

The I/O module or intelligent function module is not mounted properly or was removed during operation.

Stop/ continue

Check the detailed information (system configuration information) of the error by executing module diagnostics using the engineering tool and check the module corresponding to the displayed slot number.

Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the error module. Please consult your local Mitsubishi representative.

System configuration information

Always

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 517

51

2401H Module verification error

A CPU module, I/O module, or intelligent function module was mounted on the base unit during operation.

Stop/ continue

Check the detailed information (system configuration information) of the error by executing module diagnostics using the engineering tool and check the module corresponding to the displayed slot number.

Do not mount a CPU module, I/O module, nor intelligent function module during operation.

Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the error module. Please consult your local Mitsubishi representative.

System configuration information

Always

2420H Fuse blown error

The output module with a blown fuse has been detected.

Stop/ continue

Check the FUSE LED of each output module, and replace the one with the FUSE LED on.

Check the detailed information (system configuration information) of the error by executing module diagnostics using the engineering tool, and replace the module corresponding to the displayed slot number.

System configuration information

Always

2440H Module major error

In a multiple CPU system, the control CPU setting in the system parameters is different from that of other CPU modules.

In a multiple CPU system, other CPU modules (SIL2 Process CPU or Safety CPU) have detected a parameter verification error.

An error has been detected in the I/O module or intelligent function module during the initial processing.

Stop Correct the system parameter settings for the CPU No.2 and later in accordance with those of the CPU No.1.

Eliminate the error cause of another CPU module (Safety CPU or SIL2 Process CPU).

Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the error module. Please consult your local Mitsubishi representative.

System configuration information

At power-on, at RESET

2441H Module major error

An error has been detected in the I/O module or intelligent function module when the instruction was executed.

Stop/ continue

Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the error module. Please consult your local Mitsubishi representative.

Error location information, system configuration information

At instruction execution

2442H An error has been detected in the I/O module or intelligent function module during the END processing.

Stop/ continue

System configuration information

At module access

2443H An error has been detected in the I/O module or intelligent function module.

Stop

2450H Module major error

A major error has been notified from the intelligent function module connected.

The I/O module or intelligent function module is not mounted properly or was removed during operation.

Stop/ continue

Take measures to reduce noise. Check the connection status of the

extension cable. Check the detailed information

(system configuration information) of the error by executing module diagnostics using the engineering tool and check the module corresponding to the displayed slot number.

Reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the error module. Please consult your local Mitsubishi representative.

System configuration information

Always

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

8 34 ERROR CODES 34.4 List of Error Codes

34

2460H Another CPU module major error

An error has been detected in another CPU module during the initial processing.

Stop Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the host CPU module or another CPU module where the error has been detected. Please consult your local Mitsubishi representative.

System configuration information

At power-on, at RESET

2461H An error has been detected in another CPU module when the instruction was executed.

Stop/ continue

Error location information, system configuration information

At instruction execution

2462H An error has been detected in another CPU module during the END processing.

Stop/ continue

System configuration information

At END instruction execution

2463H An error has been detected in another CPU module.

Stop System configuration information

At power-on, at RESET

2470H A major error has been notified from another CPU module.

Stop/ continue

System configuration information

Always

2480H Multiple CPU error

In a multiple CPU system, an error has been detected in the CPU module where "Stop" is set in the operation mode setting parameter.

Any CPU module other than CPU No.1 is mounted in the inapplicable slot.

(An error occurs in the CPU module mounted in the inapplicable slot.)

Stop Check the detailed information (system configuration information) of the error by executing module diagnostics using the engineering tool, identify the error module, and eliminate the error cause.

Remove the CPU module from the inapplicable slot.

System configuration information

Always

2481H Multiple CPU error

In a multiple CPU system, any CPU module other than CPU No.1 was disconnected from the base unit during operation. Or, any CPU module other than CPU No.1 was reset.

Stop Check the mounting status and reset status of the CPU modules other than CPU No.1.

System configuration information

Always

24C0H System bus error

An error was detected on the system bus.

Stop Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module, base unit, extension cable, or module (I/O module or intelligent function module) connected. Please consult your local Mitsubishi representative.

System configuration information

At module access24C1H

24C2H System bus error

The I/O module or intelligent function module is not mounted properly or was removed during operation.

An error was detected on the system bus.

Stop Check the detailed information (system configuration information) of the error by executing module diagnostics using the engineering tool and check the module corresponding to the displayed slot number.

Check the connection status of the extension cable.

Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module, base unit, extension cable, or module (I/O module or intelligent function module) connected. Please consult your local Mitsubishi representative.

System configuration information

Always

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 519

52

24C3H System bus error

An error was detected on the system bus.

Stop Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module, base unit, extension cable, or module (I/O module or intelligent function module) connected. Please consult your local Mitsubishi representative.

System configuration information

At module access

24C4H System bus error

An error was detected on the system bus.

Stop Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the base unit, extension cable, or module (I/O module or intelligent function module) connected. Please consult your local Mitsubishi representative.

System configuration information

At module access

24C5H

24C6H System bus error

An error was detected on the system bus.

Stop Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or extension cable. Please consult your local Mitsubishi representative.

At module access

24C8H System bus error

An error was detected on the system bus.

Stop Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the extension cable, or module (I/O module or intelligent function module) connected. Please consult your local Mitsubishi representative.

At power-on, at RESET

24D0H System bus error

The extension level setting of the Q series extension base unit is overlapping with that of any other extension base units.

An unsupported base unit is connected.

Incorrect connections of the extension cables have been detected in the redundant extension base unit.

An error was detected on the system bus.

Stop Check and correct the level setting of the Q series extension base unit.

Check the connection status of the extension cable.

Check that the 10m mark is printed on the base unit connected when using the ten-meter extended cables (RC100B). ( MELSEC iQ-R Module Configuration Manual)

Disconnect the unsupported base unit.

Check the detailed information (system configuration information) of the error by executing module diagnostics using the engineering tool and identify the extension cables incorrectly connected. Connect the OUT1 connector to the IN1 connector of the next level, and connect the OUT2 connector to the IN2 connector of the next level.

Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module, base unit, or extension cable. Please consult your local Mitsubishi representative.

System configuration information

Always

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

0 34 ERROR CODES 34.4 List of Error Codes

34

24E0H System bus error

An error was detected on the system bus.

Stop Take measures to reduce noise. Check the mounting status and

reset status of the CPU modules other than CPU No.1.

Reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or base unit. Please consult your local Mitsubishi representative.

System configuration information

Always

2500H WDT error The scan time exceeded the execution monitoring time set in parameter.

The initial (1st) scan time exceeded the execution monitoring time set in the CPU parameters.

The execution time of the fixed scan interrupt program exceeded the interrupt execution interval.

Stop Check the detailed information (time information) of the error by executing module diagnostics using the engineering tool, check the time setting, and take the following actions:

(1) Check and correct the program so that it can be executed within the execution monitoring time set in parameter.

(2) Change the execution monitoring time setting to an appropriate value.

Check and correct the fixed scan interrupt program so that the processing completes within the interrupt execution interval.

If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Time information

Always

2501H The scan time exceeded the execution monitoring time set in parameter.

The 2nd or later scan time exceeded the execution monitoring time set in the CPU parameters.

The execution time of the fixed scan interrupt program exceeded the interrupt execution interval.

2520H Invalid interrupt Even though an interrupt was requested, there is no interrupt factor.

Stop Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module, base unit, or module (I/O module or intelligent function module) connected. Please consult your local Mitsubishi representative.

System configuration information

At interrupt occurrence

2521H

2522H Invalid interrupt An interrupt was requested from the module with no interrupt pointer setting.

Stop Check and correct the interrupt pointer setting in the module parameters.

Take measures so that no interrupt is requested from the module with no interrupt pointer setting.

Check and correct the interrupt setting in the buffer memory of the intelligent function module.

Correct the BASIC program executed in the QD51.

System configuration information

At interrupt occurrence

2610H Inter-module synchronization signal error

An execution interval error of the synchronization interrupt program has been detected.

An inter-module synchronization error has been detected.

Stop/ continue

Check the module set as the inter- module synchronous master.

Correct the inter-module synchronous master settings.

Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module, base unit, extension cable, or module (I/O module or intelligent function module) connected. Please consult your local Mitsubishi representative.

Always

2611H An inter-module synchronization error has been detected.

An error of the module set as the inter- module synchronous master has been detected.

Stop System configuration information

At power-on, at RESET, at END instruction execution

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 521

52

2630H Multiple CPU synchronization signal error

An execution interval error of the synchronization interrupt program has been detected.

A multiple CPU synchronization error has been detected.

Stop/ continue

Take measures to reduce noise. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or base unit. Please consult your local Mitsubishi representative.

Always

2631H A multiple CPU synchronization error has been detected.

Stop System configuration information

At power-on, at RESET, at END instruction execution

2800H I/O number or network number specification error

The specified I/O number is out of range (other than 0 to FFH, 3E0 to 3E3H).

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Error location information

At instruction execution

2801H The I/O number of the module that does not exist was specified.

Stop/ continue

Error location information, system configuration information

At instruction execution

2802H I/O number or network number specification error

The I/O number of the module that does not support the instruction was specified.

The dedicated instruction specified in the program cannot be executed in the specified module or mode.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Check the execution propriety (including support status and execution mode) of the dedicated instruction, referring to the manual for the target module.

Error location information, system configuration information

At instruction execution

2803H I/O number or network number specification error

The I/O number of the module that cannot be specified in the instruction was specified.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Error location information, system configuration information

At instruction execution

2804H The specified network number is out of range (other than 1 to 239).

2805H The network number that does not exist was specified.

2806H I/O number or network number specification error

An I/O module or intelligent function module controlled by another CPU module was specified.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Delete the link direct device that specifies a network module controlled by another CPU module from the program.

Specify a network module controlled by host CPU module by using the link direct device.

Error location information, system configuration information

At instruction execution

2807H I/O number or network number specification error

The module cannot be identified in the instruction that requires a specification of the I/O module or intelligent function module.

(There is a mistake in the string specifying the module.)

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Error location information

At instruction execution

2810H I/O number or network number specification error

The I/O module or intelligent function module specified in the instruction cannot execute the instruction.

Stop/ continue

The possible cause is a hardware failure of the I/O module or intelligent function module specified in the instruction. Please consult your local Mitsubishi representative.

Error location information, system configuration information

At instruction execution

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

2 34 ERROR CODES 34.4 List of Error Codes

34

2820H Device, label, or buffer memory specification error

The device or label area used in the instruction exceeded the specified range.

The file register file is not set or was accessed without setting it in the CPU parameters (file setting).

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Set the file register file in parameter, and access the file.

Error location information

At instruction execution, at END instruction execution

2821H Device, label, or buffer memory specification error

The device or label areas used in the instruction to store data are overlapping.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Error location information

At instruction execution

2822H The device or label that cannot be used in the instruction was specified.

Error location information

2823H The buffer memory area of the module specified in the instruction exceeded the specified range.

The module specified in the instruction does not have buffer memory.

2824H The access prohibited area in the buffer memory was accessed.

2840H File name specification error

The file specified in the instruction does not exist.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Check the detailed information (drive/file information) of the error by executing module diagnostics using the engineering tool, create the specified file, and write it to the CPU module. Or, set all the required files in the CPU parameters (file setting).

Error location information, drive/file information

At instruction execution

2841H File name specification error

The program file specified in the instruction is not set in the CPU parameters (program setting).

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Check the detailed information (drive/file information) of the error by executing module diagnostics using the engineering tool, and set the specified program file in the CPU parameter.

Error location information, drive/file information

At instruction execution

2842H File name specification error

A file that cannot be specified with the instruction was specified.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Check the detailed information (drive/file information) of the error by executing module diagnostics using the engineering tool, and check the specified file.

Error location information, drive/file information

At instruction execution

3000H Boot function execution error

The boot setting in the memory card parameters is incorrect.

Stop Check and correct the boot setting in the memory card parameters.

Drive/file information

At power-on, at RESET

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 523

52

3001H Boot function execution error

When the boot function was executed, the file format processing failed.

Stop Reset the CPU module and execute the boot function again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Drive/file information

At power-on, at RESET

3003H Boot function execution error

When the boot function was executed, the file passwords did not match.

Stop Check and correct the file password settings of the transfer source and transfer destination files.

Delete the boot setting.

Drive/file information

At power-on, at RESET

3004H Boot function execution error

When the boot function was executed, the CPU built-in memory capacity was exceeded.

Stop Check and correct the boot setting. Delete unnecessary files in the CPU

built-in memory. Clear the CPU built-in memory by

selecting "Clear" to "Operation Setting at CPU Built-in Memory Boot" in the memory card parameters, and execute the boot function.

Drive/file information

At power-on, at RESET

3005H Boot function execution error

When the boot function is executed, the security key registered in the CPU module (or cassette) does not match the one that locks the boot source program.

When the boot function is executed, the security key is not registered in the CPU module (or cassette) even though the boot source program is locked with the security key.

The program files and FB files that are written to an SD memory card using the memory card operation of the engineering tool is set to boot targets.

Stop Check and correct the security key setting.

Delete the boot settings from the memory card parameter.

Write the boot target program files and FB files to the SD memory card on the CPU module using the online data operation of the engineering tool.

Drive/file information

At power-on, at RESET

3010H Data restoration function execution error

The model of the restoration target CPU module differs from the model of the backup source CPU module.

Stop Execute the data restoration function to the CPU module whose model is the same as that of the backup source CPU module.

Turn off bit 0 of SD955 to disable the automatic data restoration function.

CPU module data backup/ restoration folder information

At power-on, at RESET

3011H Data restoration function execution error

Reading of backup data from an SD memory card completed with an error.

Stop Replace an SD memory card, and execute the function again.

The backup data may have been corrupted. Execute the data restoration function using another backup data.

Turn off bit 0 of SD955 to disable the automatic data restoration function.

CPU module data backup/ restoration folder information, drive/file information

At power-on, at RESET

3012H Data restoration function execution error

Writing of backup data to the CPU built-in memory completed with an error.

Stop The possible cause is a hardware failure of the restoration target CPU module. Execute the data restoration function to another CPU module.

CPU module data backup/ restoration folder information, drive/file information

At power-on, at RESET

3013H Data restoration function execution error

The system file does not exist in the backup data to be restored.

File(s) in the system file information does not exist in the folder of the backed up data.

Stop The backup data may have been corrupted. Execute the data restoration function using another backup data.

Turn off bit 0 of SD955 to disable the automatic data restoration function.

CPU module data backup/ restoration folder information

At power-on, at RESET

3014H Data restoration function execution error

Data was restored to the CPU module where the same data with a file password has already been stored.

Stop Delete file passwords, and execute the CPU module data backup/ restoration function.

Turn off bit 0 of SD955 to disable the automatic data restoration function.

CPU module data backup/ restoration folder information

At power-on, at RESET

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

4 34 ERROR CODES 34.4 List of Error Codes

34

3015H Data restoration function execution error

A folder with a value that matches the restoration target date folder setting value or number folder setting value does not exist in the SD memory card.

The restoration target data setting value is out of range.

The restoration target date folder setting value or number folder setting value is out of range.

Stop Check and correct the restoration target date folder setting value or number folder setting value, and execute the function again.

Check and correct the restoration target data setting value, and execute the function again.

Turn off bit 0 of SD955 to disable the automatic data restoration function.

CPU module data backup/ restoration folder information

At power-on, at RESET

3016H Data restoration function execution error

The automatic data restoration function was executed with the CPU module where an SD memory card was not inserted.

Stop Insert or re-insert an SD memory card, and execute the function again.

Turn off bit 0 of SD955 to disable the automatic data restoration function.

CPU module data backup/ restoration folder information

At power-on, at RESET

3017H Data restoration function execution error

The automatic data restoration function was executed exceeding the maximum memory capacity of the CPU module.

The automatic data restoration function was executed exceeding the maximum number of files that can be stored in the CPU module.

Stop Execute the function so that the maximum memory capacity will not be exceeded.

Execute the function so that the maximum number of storable files will not be exceeded.

Turn off bit 0 of SD955 to disable the automatic data restoration function.

CPU module data backup/ restoration folder information

At power-on, at RESET

3018H Data restoration function execution error

The status (such as programs, parameters, and file structure) of the CPU module differs from that of when the data backup function was executed.

Stop Match the CPU module status to the one at the time of backup, and execute the function again.

Set all data as the backup/ restoration target data, and execute the data restoration function.

Turn off bit 0 of SD955 to disable the automatic data restoration function.

CPU module data backup/ restoration folder information

At power-on, at RESET

3100H Program error The program includes any instruction that cannot be used or decoded in the CPU module.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Take measures to reduce noise. Write the program to the CPU

module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Error location information

At power-on, at RESET, at STOP RUN state, at instruction execution

3101H Program error The program contains a dedicated SFC program instruction even although it is not an SFC program.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Take measures to reduce noise. Write the sequence program(s) and

FB program(s) to the CPU module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Error location information

At write, at power-on, at RESET, at STOP RUN state

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 525

52

3120H Program error The CPU module does not support the dedicated instruction executed.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Check the firmware version of the CPU module and use a supported product.

Error location information

At power-on, at RESET, at STOP RUN state, at instruction execution

3121H Program error The number of devices used in the dedicated instruction specified in the program is incorrect.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Error location information

At instruction execution

3122H Program error The function block or function specified in the program does not exist.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Take measures to reduce noise. Write the sequence program(s) and

FB program(s) to the CPU module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Error location information

At instruction execution

3130H Program error The link direct device specified in the instruction cannot be executed.

Stop Check and correct the link direct device setting of the CPU parameter.

Error location information

At instruction execution

3140H END instruction error

The END (FEND) instruction does not exist in the program.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Take measures to reduce noise. Write the sequence program(s) and

FB program(s) to the CPU module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Error location information

At power-on, at RESET, at STOP RUN state

3141H FB/FUN program error

The structure of FB/FUN program is incorrect.

Stop Take measures to reduce noise. Write the sequence program(s) and

FB program(s) to the CPU module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Error location information

At instruction execution

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

6 34 ERROR CODES 34.4 List of Error Codes

34

3142H Temporary area error

The temporary area was used incorrectly.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and check the program.

Take measures to reduce noise. Write the sequence program(s) and

FB program(s) to the CPU module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Error location information

At instruction execution

3160H to 3163H

SFC program block, step error

The SFC program configuration is illegal.

Stop Take measures to reduce noise. Write the SFC program to the CPU

module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Error location information

At power-on, at RESET, at STOP RUN state, at SFC program execution

3170H SFC program block, step error

The number of SFC program steps exceeds the total number of step relays (S).

Stop Correct the program so that the number of SFC program steps does not exceed the total number of step relays (S).

Check and correct the number of device setting step relays (S) in the CPU parameters.

Error location information

At power-on, at RESET, at STOP RUN state, at SFC program execution

3171H SFC program block, step error

The total number of SFC program blocks (max. step No. + 1) exceeds the total number of step relays (S).

Stop Correct the program so that the total number of SFC program blocks (max. step No. + 1) does not exceed the total number of step relays (S).

Check and correct the number of device setting step relays (S) in the CPU parameters.

Error location information

At power-on, at RESET, at STOP RUN state, at SFC program execution

3180H SFC program configuration error

The SFC program configuration is illegal.

Stop Take measures to reduce noise. Write the SFC program to the CPU

module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Error location information

At power-on, at RESET, at STOP RUN state, at SFC program execution

3190H At SFC program execution

3191H

3192H SFC program configuration error

A self step number was specified for the specification destination step number for the jump transition.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Take measures to reduce noise. Write the SFC program to the CPU

module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Error location information

At SFC program execution

3193H A self step number was specified for the specification destination step number for the reset step.

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 527

52

31A0H SFC program block, step specification error

An attempt was made to start an SFC program block that was already running.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Turn on Start/stop SFC program (SM321) if it is off.

Error location information

At SFC program execution

31A1H SFC program block, step specification error

A non-existent SFC program block was specified.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Turn on SM321 (Start/stop SFC program) if it is off.

Check the SFC program has existed.

Check the execution status of the SFC program.

Error location information

At instruction execution, at SFC program execution

31A2H SFC program block, step specification error

The specified block exceeds the range that can be used in the SFC program.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Turn on SM321 (Start/stop SFC program) if it is off.

Error location information

At instruction execution

31B1H SFC program block, step specification error

A non-existent SFC program step was specified.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Turn on SM321 (Start/stop SFC program) if it is off.

Check the SFC program has existed.

Check the execution status of the SFC program.

Error location information

At instruction execution, at SFC program execution

31B2H SFC program block, step specification error

The specified step exceeds the range that can be used in the SFC program.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Turn on SM321 (Start/stop SFC program) if it is off.

Error location information

At instruction execution

31B3H SFC program block, step specification error

The number of simultaneous active block steps that can be specified in the SFC program exceeds the permissible value.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Error location information

At instruction execution, at SFC program execution

31B4H The total number of simultaneous active steps that can be specified in the SFC program exceeds the permissible value.

At instruction execution, at SFC program execution

31B5H A SET Sn/BLm\Sn and RST Sn/ BLm\Sn instruction were specified for the self step in the step operation output.

At instruction execution

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

8 34 ERROR CODES 34.4 List of Error Codes

34

3200H Program execution error

Memory/Device Setting set in the CPU parameters differ from those assigned to the sequence programs, FB programs, and global label setting file. (After Memory/Device Setting were modified, only the CPU parameters were written to the CPU module.)

Stop After Memory/Device Setting are modified, write the sequence program file(s), FB file(s), and global label setting file together with the CPU parameter file to the CPU module.

If no global label is used, delete the global label setting file.

Drive/file information

At power-on, at RESET, at STOP RUN state

3201H Program execution error

Even though no program is set in the CPU parameters, multiple program files exist.

Stop Set a program in the CPU parameter.

Delete unnecessary program files.

Drive/file information

At power-on, at RESET, at STOP RUN state

3202H Program execution error

The program file is incorrect. Or, the program file is not written properly.

For the subroutine type FB, "Use MC/ MCR to Control EN" of "Inherent Property" is set to "Yes".

In the option settings of the engineering tool, "Use Phase Processing Instructions" is set to "Yes".

Stop Write the program file to the CPU built-in memory again.

Set "Use MC/MCR in EN Control" in "Inherent Property" of subroutine- type FB to "No" and write the program file to the CPU built-in memory again.

Replace the CPU module with the one that supports the use of the subroutine-type FB for which "Use MC/MCR in EN Control" of "Inherent Property" is set to "Yes".

Set "Use Phase Processing Instructions" to "No" in the option settings of the engineering tool and write the program file to the CPU built-in memory again.

Replace the CPU module with the one that supports the use of the phase processing instructions.

Drive/file information

At power-on, at RESET, at STOP RUN state

3203H Program execution error

No program file exists. Stop Check if the system parameter file, CPU parameter file, and program file exist.

Write the system parameter file, CPU parameter file, and program file to the CPU built-in memory.

Drive/file information

At power-on, at RESET, at STOP RUN state

3204H Program execution error

Two or more SFC programs were executed.

Stop Ensure that only one SFC program is executed.

Drive/file information

At SFC program execution

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 529

53

3205H Program execution error

After the global label setting file was modified, only the modified file was written to the programmable controller. Or, without writing the modified global label setting file, only the sequence program file(s) and FB file(s) were written to the programmable controller. (The global label setting file was not written to the programmable controller.)

After an FB file was modified, only the modified FB file was written to the programmable controller. Or, without writing the modified FB file, only the program file(s) and global label setting file were written. (The modified FB file was not written to the programmable controller.)

After the "Access from External Device" setting of the global label setting was changed, only the global label assignment information was written to the programmable controller. Or, after the "Access from External Device" setting was changed, only the sequence program file(s) and FB file(s) were written to the programmable controller. (The global label setting file was not written.)

When the "Access from External Device" setting is not selected, the sequence program file(s), FB file(s), and global label setting file are written to the programmable controller without initializing the memory where the global label assignment information file is stored.

Stop Write all the sequence program file(s), FB file(s), global label setting file, and global label assignment information file to the programmable controller.

If no global label is used, delete the global label setting file.

If the "Access from External Device" setting is not selected, initialize the memory where the global label assignment information file is stored, and write the sequence program file(s), FB file(s), and global label setting file to the programmable controller.

Drive/file information

At power-on, at RESET, at STOP RUN state

3206H Program execution error

After the sequence program was modified, only the modified sequence program file was written to the programmable controller. Or, without writing the modified sequence program file, only the initial local label value file was written to the programmable controller.

After the global label setting file was modified, only the modified file was written to the programmable controller. Or, without writing the modified global label setting file, only the initial global label value file was written.

Stop Write both the sequence program file(s) and initial local label value file to the programmable controller.

Write both the global label setting file and initial global label value file to the programmable controller.

If no initial global label value is used, delete the initial global label value file.

If no initial local label value is used, delete the initial local label value file.

Drive/file information

At power-on, at RESET, at STOP RUN state

3207H Program execution error

The signal flow area to be used in the FB program cannot be secured.

Stop Check the detailed information (drive/file information) of the error by executing module diagnostics using the engineering tool, and identify the error program file. Then, reduce the number of instructions that use the signal flow area of the FB program used in the sequence program file.

Drive/file information

At power-on, at RESET, at STOP RUN state

3220H SFC program execution error

Unable to execute the SFC program. Stop Take measures to reduce noise. Write the SFC program and CPU

parameters to the CPU module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Drive/file information

At power-on, at RESET, at STOP RUN state, at SFC program execution

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

0 34 ERROR CODES 34.4 List of Error Codes

34

3221H SFC program execution error

Unable to execute the SFC program. Stop Take measures to reduce noise. Write the SFC program to the CPU

module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Drive/file information

At power-on, at RESET, at STOP RUN state, at SFC program execution

3222H

32FEH License authentication error

A device or a label that is required for the license authentication does not exist.

Stop Please consult your local Mitsubishi representative.

Error location information

At instruction execution

32FFH License authentication error

The specified license key is incorrect. Stop Check the license key and specify correct one.

Error location information

At instruction execution

3300H Pointer setting error

The total number of points of local or global pointers used in the program exceeded the points set in the CPU parameters (pointer device area).

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Check and correct the pointer device area point setting in the CPU parameters.

Error location information

At power-on, at RESET, at STOP RUN state

3301H Pointer setting error

The total number of points of pointer- type labels used in the program exceeded the points set in the CPU parameters (pointer-type label assignment area).

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Check and correct the pointer-type label assignment area point setting in the CPU parameters.

Error location information

At power-on, at RESET, at STOP RUN state

3302H Pointer setting error

Multiple global pointers with the same number or pointer-type global labels are used in the program. (The pointer numbers or the labels are overlapping.)

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Error location information

At power-on, at RESET, at STOP RUN state

3303H Pointer setting error

Multiple local pointers with the same number or pointer-type local labels are used in the program. (The pointer numbers or the labels are overlapping.)

3320H Interrupt pointer setting error

The interrupt pointer numbers used in the files are overlapping.

3340H FOR-NEXT instruction error

The NEXT instruction was not executed even though the FOR instruction was executed. Or, there are more FOR instructions than NEXT instructions.

At END instruction execution

3341H FOR-NEXT instruction error

The NEXT instruction was executed even though the FOR instruction was not executed. Or, there are more NEXT instructions than FOR instructions.

At instruction execution

3342H FOR-NEXT instruction error

The BREAK instruction was executed even though the FOR instruction was not executed.

3360H Nesting depth error

The number of nesting levels in the subroutine program exceeded its limit (16).

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the number of nesting levels (16 or less).

Error location information

At instruction execution

3361H The number of nesting levels in the FOR instruction exceeded its limit (16).

3362H The number of nesting levels in the DI instruction exceeded its limit (16).

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 531

53

3363H Nesting depth error

The number of nesting levels in the function block or function exceeded its limit (32).

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the number of nesting levels (32 or less).

Error location information

At instruction execution

3380H Pointer execution error

The pointer specified in the instruction does not exist.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Error location information

At instruction execution

3381H The RET instruction does not exist in the executed subroutine program.

At END instruction execution

3382H The RET instruction exists before the FEND instruction in the main program.

At instruction execution

33A0H Interrupt pointer execution error

The interrupt pointer corresponding to the interrupt input does not exist.

Stop Check if the program corresponding to the interrupt pointer number set in the module parameters exists.

At instruction execution

33A1H Interrupt pointer execution error

The IRET instruction does not exist in the executed interrupt program.

The STOP instruction has been executed in an interrupt program.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Error location information

At instruction execution

33A2H The IRET instruction exists before the FEND instruction in the main program.

33A3H The IRET instruction or STOP instruction was executed in the fixed scan execution type program.

33A4H The IRET instruction or STOP instruction has been executed in an event execution type program.

33C0H FB/FUN execution error

Before the FB/FUN program ends, the call source program ended.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Take measures to reduce noise. Write the program to the CPU

module again. Then, reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Error location information

At instruction execution

33D0H Temporary area exceeded

The secured temporary area size exceeded its limit.

Stop Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the number of nesting levels in the function.

Error location information

At instruction execution

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

2 34 ERROR CODES 34.4 List of Error Codes

34

3400H Operation error Division where the divisor is zero was performed.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the program.

Error location information

At instruction execution

3401H Data that cannot be converted by using the data conversion instruction was input.

3402H The operation was performed with the invalid data (-0, denormalized number, NaN (not a number), or ).

3403H An overflow has occurred during the operation.

3404H A string that is not supported in the instruction was specified.

3405H The input data was out of range.

3406H The operation result is out of the output range. (The operation result of the instruction that concatenate character strings exceeded the allowable number of characters.)

3420H The link direct device, module access device, or CPU buffer memory access device is specified for both (s) and (d) used in the BMOV instruction.

Error location information

3421H Operation error When writing data to the data memory by using the SP.DEVST instruction, the number of writes per day exceeded the number set in SD771.

The value set in SD771 is out of range.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and check if the SP.DEVST instruction is used correctly in the program.

Execute the SP.DEVST instruction again on another day, or change the value in SD771.

Set the value in SD771 within the settable range.

Error location information

At instruction execution

3422H Operation error The structure of the PID control instruction is incorrect.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the PID control instruction structure.

Error location information

At instruction execution

3423H Operation error The size of data to be sent/received by the socket communications instruction exceeds the allowable range.

Stop/ continue

Check and change the send data size of the CPU module or the external device.

If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Error location information

At instruction execution

3424H Operation error A second SFC program was started with an instruction while an SFC program was running.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and check the SFC program execution status.

Error location information

At instruction execution

3425H Operation error The clock data specified with the DATEWR(P) instruction is less than 1 hour from the daylight saving time starting time.

Stop/ continue

Check the detailed error information (error location information) by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and correct the clock data specified with the instruction or the daylight saving time setting starting time.

Error location information

At instruction execution

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 533

53

3426H Operation error The specified file name (before a period) or extension includes two or more "*".

The specified file name (before a period) or extension includes "*" and "?'"

A wild card ("*", "?") is used in a location where it cannot not be used.

A file that cannot be transfered has been specified.

A file name is not specified. A delimiter for a drive number has

been specified with characters other than ":\" or ":/".

Stop/ continue

Check the usage of wild card characters.

Use a file that can be transferred. Specify a file name. Specify a delimiter for a drive

number with ":\" or ":/".

Error location information

At instruction execution

3427H Operation error The control data (d1) of the SP.FREAD and SP.FWRITE instruction are specified with an invalid combination between the execution/completion type and the data type specification.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and change the combination to a valid one.

Error location information

At instruction execution

3430H Operation error An instruction has been executed without setting parameters which are required when the instruction is executed.

Stop/ continue

Set parameters required to execute the instruction.

Error location information

At instruction execution

3440H Operation error In a multiple CPU system, the multiple CPU dedicated instruction (the one whose symbol starts with D(P)) was executed when "Do Not Use" was set to "Fixed scan communication function" in the system parameters ("Multiple CPU Setting").

Stop/ continue

Change "Fixed scan communication function" to "Use".

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and change the multiple CPU dedicated instruction to the one whose symbol starts with M(P).

Error location information

At instruction execution

3441H Operation error In a multiple CPU system, the number of data points was specified exceeding the multiple CPU dedicated instruction areas applicable for each CPU module.

Stop/ continue

Check the detailed information (error location information) of the error by executing module diagnostics using the engineering tool, display the error program (step) by clicking the [Error Jump] button, and change the number of data points for the multiple CPU dedicated instruction.

Error location information

At instruction execution

34A0H Operation error Response data of the socket communications instruction cannot be created.

Stop/ continue

Increase the request interval. Decrease the number of request

nodes. Wait for a response to the previous

request before sending the next request.

Correct the timeout value.

Error location information

At END instruction execution

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

4 34 ERROR CODES 34.4 List of Error Codes

34

3C00H Hardware failure

A hardware failure has been detected. Stop Take measures to reduce noise. Check the mounting status of the

CPU module, SIL2 function module, and safety function module.

Reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Failure information

Always

3C01H

3C02H At power-on, at RESET, at END instruction execution, at interrupt occurrence

3C03H Always

3C0FH Take measures to reduce noise. Check the mounting status of the

CPU module, SIL2 function module, and safety function module.

Reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module, extended SRAM cassette, battery-less option cassette, or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

3C10H Hardware failure

A hardware failure has been detected. Stop Take measures to reduce noise. Check the mounting status of the

CPU module, SIL2 function module, and safety function module.

Reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Failure information

At power-on, at RESET

3C11H At END instruction execution, at instruction execution

3C12H Hardware failure

The waveform of the voltage out of the specified range has been detected in the power supply module.

A hardware failure has been detected in the power supply module, CPU module, base unit, or extension cable. (In a redundant power supply system, the error is detected when two power supply modules failed.)

Stop Check the waveform of the voltage applied to the power supply module.

Check the mounting status of the CPU module.

Reset the CPU module and run it again. If the same error code is displayed again, the possible cause is a hardware failure of the power supply module, CPU module, base unit, or extension cable. Please consult your local Mitsubishi representative.

Failure information

Always

3C13H Hardware failure

A hardware failure has been detected. Stop Take measures to reduce noise. Check the mounting status of the

CPU module. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Failure information

Always

3C14H Hardware failure

A hardware failure has been detected. Stop Take measures to reduce noise. Check the mounting status of the

CPU module. Reset the CPU module and run it

again. If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Failure information

Always

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

34 ERROR CODES 34.4 List of Error Codes 535

53

3C20H Memory error An error has been detected in the memory.

Stop Take measures to reduce noise. Check the mounting status of the

CPU module, SIL2 function module, and safety function module.

Format the memory. Write all files to the CPU module. Then, reset the CPU module and run it again If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Failure information

At power-on, at RESET

3C21H At END instruction execution, at power-on, at RESET

3C22H

3C2FH Take measures to reduce noise. Check the mounting status of the

CPU module, SIL2 function module, and safety function module.

Format the memory. Write all files to the CPU module. Then, reset the CPU module and run it again If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Always

3C30H Memory error An error has been detected in the memory.

Stop Take measures to reduce noise. Check the mounting status of the

CPU module, SIL2 function module, and safety function module.

Format the memory. Write all files to the CPU module. Then, reset the CPU module and run it again If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Take measures to reduce noise. Check the mounting status of the

CPU module. Format the memory. Write all files to

the CPU module. Then, reset the CPU module and run it again If the same error code is displayed again, the possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

Failure information

At instruction execution

3C31H Always

3C32H

3E00H Operation circuit error

An error has been detected in the CPU module.

Stop Failure information

At power-on, at RESET

3E20H Program execution error

The entire program was executed without executing the END instruction.

Stop Take measures to reduce noise. Check the mounting status of the

CPU module, SIL2 function module, and safety function module.

Format the memory. Write all files to the CPU module. Then, reset the CPU module and run it again If the same error code is displayed again, the possible cause is a hardware failure of the CPU module or module (SIL2 function module or safety function module) connected. Please consult your local Mitsubishi representative.

Failure information

At END instruction execution

3E22H Program execution error

The FB/FUN program did not complete successfully.

At instruction execution

Error code

Error name Error details and cause Stop/ continue

Action Detailed information

Diagnostic timing

6 34 ERROR CODES 34.4 List of Error Codes

34

Codes of errors detected by other than the self-diagnostic function (4000H to 4FFFH) The following table lists the codes of errors, other than those detected by the self-diagnostic function of the CPU module.

Error codes returned to request source during communications with the CPU module Errors generated when the data communications are requested from the engineering tool, intelligent function module, or

network system connected Errors generated with the data logging function These error codes are not stored in SD0 because they are not detected by the self-diagnostic function of the CPU module.

Error code

Error name Error details and cause Action

4000H Common error Serial communication sum check error Connect the serial communication cable correctly. Take measures to reduce noise.

4001H Common error An unsupported request was executed. (The request was executed to the CPU module that does not support the request.)

Check the command data of the SLMP/MC protocol. Check the CPU module model name selected in the

engineering tool. Check the target CPU module model name. Check that the target network number is not duplicated.

4002H Common error An unsupported request was executed. Check the command data of the SLMP/MC protocol. Check the CPU module model name selected in the

engineering tool. Execute the request again. If the same error code is displayed again, the possible cause

is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

4003H Common error Command for which a global request cannot be performed was executed.

Check the command data of the SLMP/MC protocol.

4004H Common error All the operations to the CPU module are disabled because of the following reason: The CPU module is starting up.

Perform operations to the CPU module again after the start-up processing ends.

4005H Common error The amount of data handled according to a specified request is out of range.

Check the command data of the SLMP/MC protocol.

4006H Common error Initial communication has failed. When using serial communication, inquire of the external device manufacturer for support conditions.

When using serial communication, check the CPU module model name selected in the engineering tool.

When using Ethernet communication, shift the communication start timing.

4008H Common error The CPU module is BUSY. (The buffer is not vacant.) Execute the request again after the specified period of time has elapsed.

4010H CPU module operation error

The request cannot be executed because the CPU module is running.

Set the operating status of the CPU module to STOP, and execute the request again.

4013H CPU module operation error

The request cannot be executed because the CPU module is not in the STOP state.

Set the operating status of the CPU module to STOP, and execute the request again.

4021H File related error The specified drive (memory) does not exist or there is an error.

Check the specified drive (memory) status. Back up data in the CPU module, and then initialize the

memory.

4022H File related error The file with the specified file name or file No. does not exist.

The specified program block does not exist. When CPU Module Logging Configuration Tool is used The data logging was started in the following state. A program name (program No.) that does not exist was

specified.

Check the specified file name and file No. Check the specified program block name.

When CPU Module Logging Configuration Tool is used Check the specified program name.

4023H File related error The file name and file No. of the specified file do not match.

Delete the file and then recreate the file.

4024H File related error The specified file cannot be handled by a user. Do not access the specified file.

4025H File related error The specified file is processing the request from another engineering tool.

Forcibly execute the request. Or, execute the request again after the processing being performed ends.

4026H File related error The file password set in advance to the target drive (memory) must be specified.

Specify the file password set in advance, and then access to the drive (memory).

34 ERROR CODES 34.4 List of Error Codes 537

53

4027H File related error The specified range is larger than the file size. Check the specified range and access within that range.

4028H File related error The same file already exists. Forcibly execute the request. Or, change the file name and execute the request again.

4029H File related error The specified file capacity cannot be obtained. Review the specified file capacity, and execute the request again.

402AH File related error The specified file is abnormal. Back up data in the CPU module, and then initialize the memory.

402BH File related error The request cannot be executed in the specified drive (memory).

Set the operating status of the CPU module to STOP, and execute the request again.

402CH File related error The request cannot be executed currently. Execute the request again after a while.

402FH File related error Writing of a file did not complete. Back up data internally in the CPU module, and delete the corresponding file or initialize the drive 4. Then, write the file to the programmable controller again.

Write the program restoration information. Then, read the program files from the programmable controller again.

4030H Device specification error

The specified device is not supported. When CPU Module Logging Configuration Tool is used The data logging specifying a device that is not

supported was started.

Check the specified device.

4031H Device specification error

The specified device number is out of range. The CPU module does not support the specified

device. When CPU Module Logging Configuration Tool is used The data logging specifying a device number that does

not exist was started.

Check the specified device number. Check the device assignment of the CPU module. Check the specified device.

4032H Device specification error

The device modification was incorrectly specified. Or, the unusable device (TS, TC, SS, SC, CS, or CC) was specified in any of the following SLMP/MC protocol commands; Read random, Write random (in units of words), Entry monitor device, or Execute monitor.

When CPU Module Logging Configuration Tool is used The data logging specifying a device modification that

is not supported was started.

Check the device modification method. Check the specified device.

4033H Device specification error

Writing cannot be done because the specified device is for system use.

Do not write the data in the specified device, and do not turn on or off.

4034H Device specification error

The dedicated instruction cannot be executed since the completion device for the dedicated instruction does not turn on.

Since the completion device for the SREAD or SWRITE instruction does not turn on in the CPU module on the target station, execute the instruction again after setting the operating status of the CPU module on the target station to the RUN status.

4035H Device specification error

The request cannot be executed because the specified device is in the write-protect range.

Do not write data to the specified device. Check the setting of the write-protect function for device data

(from outside the CPU module) for the request destination CPU module, and execute the request to the available device range again.

Clear the setting of the write-protect function for device data (from outside the CPU module), and execute the request again.

4036H Device specification error

The request cannot be executed because the write- protect function for device data (from outside the CPU module) is enabled.

Check and correct the specified device, and execute the request again. Do not use indirect specification and index modification. Do not use the R device. (Use the ZR device.)

Clear the setting of the write-protect function for device data (from outside the CPU module), and execute the request again.

403FH Device specification error

The link direct device specified cannot be executed. Set the link direct device setting of the CPU parameter to the "Extended Mode (iQ-R Series Mode)".

4040H Intelligent function module specification error

The request cannot be executed to the specified intelligent function module.

Check whether the specified module is the intelligent function module having the buffer memory.

4041H Intelligent function module specification error

The access range exceeds the buffer memory range of the specified intelligent function module.

Check the start address and access number of points and access using a range that exists in the intelligent function module.

Error code

Error name Error details and cause Action

8 34 ERROR CODES 34.4 List of Error Codes

34

4042H Intelligent function module specification error

The specified intelligent function module cannot be accessed.

Check that the specified intelligent function module is operating normally.

Check the specified module for a hardware fault.

4043H Intelligent function module specification error

The intelligent function module does not exist in the specified position.

When CPU Module Logging Configuration Tool is used The data logging specifying a device that does not

exist or cannot be accessed was started.

Check the I/O number of the specified intelligent function module.

4044H Intelligent function module specification error

A control bus error occurred during access to the intelligent function module.

Check the specified intelligent function module and other modules and base units for a hardware fault.

4049H Intelligent function module specification error

A request cannot be processed because the module extension parameter of the positioning module is being used for the positioning control.

Turn off module ready (Yn+0) of the positioning module or execute the processing again after removing the extension parameter of the positioning module from the target data.

4050H Protect error The request cannot be executed because the write protect switch of the SD memory card is on.

Turn off the write protect switch.

4051H Protect error The specified drive (memory) cannot be accessed. Check the following and take action. Is the drive (memory) the one that can be used? Is the specified drive (memory) correctly installed?

4052H Protect error The specified file attribute is read only, so the data cannot be written.

Do not write data in the specified file. Or, change the file attribute.

4053H Protect error An error occurred when writing data to the specified drive (memory).

Check the specified drive (memory). Or, write data again after changing the corresponding drive (memory).

4054H Protect error An error occurred when deleting the data in the specified drive (memory).

Check the specified drive (memory). Or, delete data again after replacing the specified drive (memory).

4060H Online registration error

The online debug function (such as online change) and the data logging function are being executed with another engineering tool.

Data is being written to the flash ROM (data memory, program memory, and system memory) and the SD memory card.

The global label assignment information is being written to the programmable controller (data memory).

When CPU Module Logging Configuration Tool is used An attempt was made to write or delete data logging

settings or to execute data logging to the setting registered by another request source.

Execute the function again after the processing of the function executed from another engineering tool ends.

If the operation of another engineering tool is on hold, resume and finish the operation of another engineering tool, and then execute the function again.

Execute the function again after the completion of writing to the flash ROM and the SD memory card. If the same error code is displayed again, reset the CPU module.

4061H Online registration error

Settings for the online debug function (such as online change) are incorrect.

The CPU module is powered off or reset during the monitoring.

Register an online debug function (such as online change and external input/output forced on/off), and then execute the function.

Execute again after checking the communication route such as the communication cable.

Power on or reset the CPU module and execute the monitoring again.

4063H Online registration error

The registered number of locked files exceeded the maximum value.

Execute the request again after the file access from another engineering tool ends.

4064H Online registration error

The specified contents of the online debug function (such as the online program change), data logging function, memory dump function, or real-time monitor function are incorrect.

When CPU Module Logging Configuration Tool is used The trigger logging was started in a state that the

trigger condition has already been satisfied.

Check the set data of the online debug function (such as the online program change), data logging function, memory dump function, and real-time monitor function.

Execute again after checking the communication route such as the communication cable.

When CPU Module Logging Configuration Tool is used Clear the satisfied trigger condition, and execute the trigger

logging again.

4065H Online registration error

The device assignment information differs from the parameter.

The cassette set in the cassette setting in the CPU parameter differs from the one actually inserted.

An unsupported extended SRAM cassette or battery- less option cassette is inserted.

In the CPU module which operates in redundant mode, the number of device points of the step relay (S) is set to other than 0 in the device setting of the CPU parameters.

Check the device assignment of the CPU module or the device assignment of the request data.

Correct the cassette setting in the CPU parameters so that it matches with the cassette actually inserted.

Replace the extended SRAM cassette or the battery-less option cassette with the one supported by the CPU module.

Set the number of device points of the step relay (S) to 0 in the device setting of the CPU parameters.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 539

54

4066H Online registration error

The specified file password is incorrect. Check and specify the correct file password.

4067H Online registration error

Monitor communication has failed. Execute again after checking the communication route such as the communication cable.

4068H Online registration error

Operation is disabled because it is being performed with another engineering tool.

Execute the request again after the processing of the function executed from another engineering tool ends.

406AH Online registration error

The drive (memory) number other than 0 to 4 was specified.

Check the drive and specify the drive number correctly.

406BH Online registration error

Online operation was interrupted due to a CPU module error.

Check the status of the CPU module by executing the module diagnostics.

Identify the error, and take a corrective action referring to the troubleshooting section.

406CH Online registration error

The number of functions that can be executed simultaneously exceeds the limit.

Execute again after stopping the functions that are executed in another engineering tool.

406DH Online registration error

The operation cannot be performed because the operation is performed from the same activation source.

Execute again after the operation from the same activation source has completed.

406EH Online registration error

The specified operation cannot be maintained. Check and correct the operation.

4070H Verification error The program not yet corrected and the one corrected by online program change are different.

The execution program that was written to the programmable controller (including online change) or the execution program that was written by using online change operation differs from the program restoration information to be written.

Read the program from the CPU module to match it with that of the engineering tool, and then execute online change again.

Write the program including the program restoration information to the programmable controller (including online change), or execute online change.

4071H Verification error After the realtime monitor started, the CPU parameters in the CPU module has been changed or deleted.

Start the realtime monitor again. Write the project of GX Works3 at the time of the start of the

realtime monitor to the CPU module.

4072H Verification error After the realtime monitor started, the global label setting file in the CPU module or the sequence program file having a monitoring target program name has been changed or deleted.

Read the project of GX Works3 from the CPU module, save it, and load it into GX LogViewer. Then, start the realtime monitor again.

Write the project of GX Works3 at the time of the start of the realtime monitor to the CPU module.

Check and correct the SD940 setting.

4080H Any other error Request data error When CPU Module Logging Configuration Tool is used Request or setting data error

Check the request data that has been specified. When CPU Module Logging Configuration Tool is used Check the specified data, and write it to the CPU module

again.

4081H Any other error The search target data cannot be detected. Check the data to be searched.

4082H Any other error The specified command cannot be executed because it is being executed.

Execute the command again after the processing of the command from another engineering tool ends.

4083H Any other error An attempt was made to perform operation to the program not registered in parameter.

When CPU Module Logging Configuration Tool is used The data logging specifying the program that is stored

in the CPU module but not registered in the CPU parameters was started.

Register the program in parameter.

4084H Any other error The specified pointer (P or I) does not exist. Check if the pointer (P or I) exist in the data.

4085H Any other error The pointer (P or I) cannot be specified because the program is not specified in parameter.

Register the program to be executed in parameter first, and specify the pointer (P or I).

4086H Any other error The specified pointer (P or I) has already been added. Check and correct the pointer number to be added.

4087H Any other error The number of pointers (P or I) exceeds its limit. Check and correct the specified pointer (P or I).

4088H Any other error The specified step number is not at the head of the instruction.

The program differs from that stored in the CPU module.

When CPU Module Logging Configuration Tool is used The data logging specifying the step number that does

not exist or is not specified as the start number of the instruction was started.

Check and correct the specified step number. Read the program from the CPU module to match it with that

of the engineering tool, and then execute online change again.

Error code

Error name Error details and cause Action

0 34 ERROR CODES 34.4 List of Error Codes

34

4089H Any other error An attempt was made to insert/delete the END instruction by online program change.

Check the specified program file contents. Set the operating status of the CPU module to STOP, and

write the program.

408AH Any other error The file capacity exceeded after the online change was executed.

Check the capacity of the specified program file. Set the operating status of the CPU module to STOP, and

write the program.

408BH Any other error The remote request cannot be executed. Change the status of the CPU module so that the remote request can be executed, and execute the request again.

For remote operation, set the parameter to "Enable remote reset".

408DH Any other error The instruction code that cannot be handled exists. Check whether the model of the used CPU module is correct or not.

The program where online change was attempted includes the instruction that cannot be handled by the CPU module specified for the project. Check the program and delete the instruction.

408EH Any other error The write step is illegal. The program differs from that stored in the CPU

module.

Set the operating status of the CPU module to STOP, and write the program.

The starting position of online program change is not specified with the correct program step number. Check whether the engineering tool supports the model and version of the CPU module that is specified for the project.

Read the program from the CPU module to match it with that of the engineering tool, and then execute online the program change again.

40A0H SFC device specification error

A block No. outside the range was specified. Check the setting and correct it.

40A1H SFC device specification error

The number of blocks exceeds the range. Check the set quantity and correct it.

40A2H SFC device specification error

A step No. outside the range was specified. Check the setting and correct it.

40A3H SFC device specification error

The number of steps exceeds the range. Check the set quantity and correct it.

40A4H SFC device specification error

A sequence step No. outside the range was specified. Check the setting and correct it.

40A5H SFC device specification error

The specified device is outside the range. Check the set quantity and correct it.

40A6H SFC device specification error

The block specification pattern and step specification pattern are incorrect.

Check the setting and correct it.

40A7H SFC device specification error

R00CPU, R01CPU, R02CPU: A block No. that does not exist in the 0 to 127 range

was specified. CPU module other than above models: A block No. that does not exist in the 0 to 319 range

was specified.

Check the setting and correct it.

40A8H SFC device specification error

R00CPU, R01CPU, R02CPU: A step No. that does not exist in the 0 to 127 range was

specified. CPU module other than above models: A step No. that does not exist in the 0 to 511 range was

specified.

Check the setting and correct it.

40B0H SFC file related error

The drive (memory) specified with the SFC program file operation is incorrect.

Check the setting and correct it.

40B1H SFC file related error

The SFC program specified with the SFC program file operation does not exist.

Check the specified file name and correct it.

40B2H SFC file related error

The program specified with the SFC program file operation is not an SFC program.

Check the specified file name and correct it.

40B3H SFC file related error

An attempt was made to rewrite a dedicated SFC instruction by changing an SFC program online.

Set the operating status of the CPU module to STOP, and write the SFC program.

40B4H SFC file related error

An attempt was made to change or delete the active block.

Inactivate the target block.

40B5H SFC file related error

The number of SFC steps after the program change exceeded the maximum.

Reduce the number of SFC steps to be added and execute the online change again.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 541

54

40B6H SFC file related error

The specified block does not exist. Read the program from the CPU module to match it with that of the engineering tool, and then execute the online program change again.

40B7H SFC file related error

The online change cannot be executed to the standby type SFC program.

After setting the operating status of the CPU module to STOP, write the SFC program to the programmable controller.

40B8H SFC file related error

The device number of SFC information device is outside the range.

Check and correct the setting of the block information.

40B9H SFC file related error

The changed SFC program is incorrect. Execute again after checking the communication route such as the communication cable.

40BAH SFC file related error

The online change for each block cannot be executed to the SFC block whose number of sequential steps exceeds 32K steps.

To execute the online change for each block, the number of sequential steps of the target SFC block must be within 32K steps.

After setting the operating status of the CPU module to STOP, write the SFC program to the programmable controller.

40BBH SFC file related error

The online change cannot be executed because writing to the programmable controller in the STOP state has just completed or a program execution error has occurred.

After the operating status of the CPU module is changed from STOP to RUN, execute the online SFC block change or the online program change.

After preventing the program execution error from occurring, execute the online SFC block change or the online program change.

40BDH SFC file related error

Online change (SFC block) execution error Read the program from the CPU module to match it with that of the engineering tool, and then execute the online program change again.

After setting the operating status of the CPU module to STOP, write the SFC program to the programmable controller.

40BEH SFC file related error

The program cannot be changed online because the part to be changed has an active step (a step holding operations).

Omit the step from the part. Deactivate the step.

40C0H Label communication error

The specified label name does not exist. Check the label setting. If the "Access from External Device" checkbox is not selected, check the checkbox.

40C1H Label communication error

Label access with a label name has failed because the specified array element number is outside the range.

Specify the array element number within the set range.

40C2H Label communication error

Label access with a label name has failed because the bit array type label is not specified by bit specification.

Specify the label by bit specification, and access again.

40C3H Label communication error

Label access with a label name has failed because the word array type label is not specified by word specification.

Specify the label by word specification, and access again.

40C4H Label communication error

Label access with a label name has failed because the number of labels used in the program exceeded its limit.

Reduce the number of labels in the program, and access the labels multiple times.

40C5H Label communication error

Label access with a label name has failed because the global label setting file and global label assignment information do not match.

The request execution has failed because the global label is being modified by the CPU module specified.

Check the access from an external device of the specified global label setting, and write the global label setting file and the global label assignment information to the programmable controller together.

Execute the label access again after a while.

40C6H Label communication error

The request execution has failed because the global label is being modified by the CPU module specified.

After a while, write the data to the programmable controller/ execute online change or execute the label access again.

40C7H Label communication error

Although changes of the global label were written to the programmable controller, the reflection operation (STOP RUN or Power-on and reset) of the global label setting file is not performed.

The request cannot be executed because the data in the global label setting file being processed and the specified consistency check data are not the same.

Perform the reflection operation (STOP RUN or Power-on and reset) of the global label setting file.

Correct the details of the global label setting, and write the file to the programmable controller again.

40C8H Label communication error

Registration of a label definition has failed because the number of registered labels reached its limit.

Reduce the number of registered labels with the "Access from External Device" checkbox selected.

40C9H Label communication error

A label definition could not be registered because the registration target memory capacity has been exceeded its limit.

Reduce the number of registered labels with the "Access from External Device" checkbox selected.

If the data memory is specified as the registration target memory, change the memory to the SD memory card.

Change the settings of the functions that use the registration target memory.

Error code

Error name Error details and cause Action

2 34 ERROR CODES 34.4 List of Error Codes

34

40CAH Label communication error

A label definition could not be changed, added, or deleted because the label communication data does not exist in the CPU module.

When CPU Module Logging Configuration Tool is used An attempt was made to change, add, or delete labels

without creating the label communication data.

Write the label communication data to the programmable controller.

40CBH Label communication error

Data are not written to the CPU module because the data type of the specified label does not match the size of the write data.

Change the size of data written from the external device (SLMP/MC protocol device) so that it matches the data type of the label in the specified CPU module.

40CCH Label communication error

Online program change has failed because the global label setting file before modification and the global label assignment information do not match.

Write the global label setting file and the global label assignment information to the programmable controller together after modification.

40CEH Label communication error

An attempt was made to access a label that cannot be accessed with a label name.

Change the data type of the specified label to the one other than "Function Block" or "Pointer".

Change the class of the specified label to the one other than "VAR_GLOBAL_CONSTANT".

Specify a device that is not being modified. (Bit-specified word devices and digit-specified bit devices can be specified.)

Change the data type of the specified label to the one other than "Bit and two-dimensional array" or "Bit and three- dimensional array".

40D0H Label communication error

The target CPU module does not support "Access from External Device" of "Global Label Setting".

Disable "Access from External Device", and then write the data to the programmable controller again.

40D1H Label communication error

When the byte is specified for the unit for reading/ writing data, an odd-numbered value is specified for the read/write array data length.

Specify an even-numbered value for the read/write array data length.

4100H Any other error Hardware failure of the CPU module. Replace the CPU module.

4101H Any other error Serial communication connection was executed for a different CPU module series.

Check the CPU module series.

4103H Any other error The instruction written by online program change is incorrect or invalid.

Execute online program change again. Or, set the operating status of the CPU module to STOP, and write the program.

4104H Any other error An instruction(s) that cannot be executed by the CPU module set to process mode or redundant mode is included in the instructions targeted for online program change.

Delete the instruction(s) that cannot be executed, and execute the online program change function again. Or, set the operating status of the CPU module to STOP, and write the program.

4105H Any other error Hardware failure of the CPU module internal memory The possible cause is a hardware failure of the CPU module. Please consult your local Mitsubishi representative.

4108H Any other error The device monitor/test cannot be performed normally. Execute the function again. Check that the access prohibited area is not accessed, and execute the function again.

410AH Any other error The specified command cannot be executed because the online program change is being executed.

When CPU Module Logging Configuration Tool is used The data logging where a step No. is specified as the

collection start condition or trigger condition was started during the online program change.

The data logging where a label (global label or local label) is specified as the collection start condition, data collection target, or trigger condition was started during the online program change.

The data logging setting file where a label (global label or local label) is specified as the collection start condition, data collection target, or trigger condition was written during the online program change.

Execute the request again after the online program change.

410BH Any other error The monitor condition registration was cleared after the online program change was executed.

Execute the registration of monitoring condition again after the online program change.

410CH Any other error Writing to the specified data is not supported. Check that the version of the engineering tool used is correct. Check the settings and make a correction.

410EH Any other error When the execution status of the online program change is in error, the online program change command was issued.

Issue the online program change cancel command, and execute the function again.

410FH Any other error During the execution of the online program change function, the cancel command was issued by the same request source.

Issue the command again after the currently-performed processing ends.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 543

54

4110H CPU module error The request cannot be executed because the CPU module is in a stop error state.

Reset the CPU module and execute the request again.

4111H CPU module error The request cannot be executed because the other CPU modules, except the host CPU module, have not yet started in a multiple CPU system.

Execute the request again after all the other CPU modules have started.

4121H File related error The specified drive (memory) or file does not exist. Execute again after checking the specified drive (memory) or file.

4122H File related error The specified drive (memory) or file does not exist. Execute again after checking the specified drive (memory) or file.

4123H File related error The specified drive (memory) is abnormal. When CPU Module Logging Configuration Tool is used The data logging was started to the memory having an

error.

Initialize the memory, and restore the drive (memory) to its normal state.

4124H File related error The specified drive (memory) is abnormal. Initialize the memory, and restore the drive (memory) to its normal state.

4125H File related error The specified drive (memory) or file is performing processing.

Execute again after a while.

4126H File related error The specified drive (memory) or file is performing processing.

Execute again after a while.

4127H File related error File password mismatch Execute again after checking the file password.

4128H File related error File password mismatch with copy destination Execute again after checking the file password.

4129H File related error The request cannot be executed since the specified drive (memory) is ROM.

Execute again after changing the target drive (memory).

412AH File related error The request cannot be executed since the specified drive (memory) is ROM.

Execute again after changing the target drive (memory).

412BH File related error The specified drive (memory) is write-inhibited. Execute again after changing the write inhibit condition or drive (memory).

412CH File related error The specified drive (memory) is write-inhibited. Execute again after changing the write inhibit condition or drive (memory).

412DH File related error The specified drive (memory) does not have enough free space.

Execute again after increasing the free space of the drive (memory).

412EH File related error The specified drive (memory) does not have enough free space.

Execute again after increasing the free space of the drive (memory).

412FH File related error The drive (memory) capacity differs between the drive (memory) copy destination and copy source.

Execute again after checking the drive (memory) copy destination and copy source.

4130H File related error The drive (memory) type differs between the drive (memory) copy destination and copy source.

Execute again after checking the drive (memory) copy destination and copy source.

4131H File related error The file name of the file copy destination is the same as that of the copy source.

Execute again after checking the file names.

4132H File related error The specified number of files does not exist. Execute again after checking the specified data.

4133H File related error The specified drive (memory) has no free space. Execute again after increasing the free space of the drive (memory).

4134H File related error The attribute specification data of the file is wrong. Execute again after checking the specified data.

4135H File related error The date/time data of the engineering tool (personal computer) is out of range.

Execute again after checking the clock setting of the engineering tool (personal computer).

4136H File related error The specified file already exists. Execute again after checking the specified file name.

4137H File related error The specified file is read-only. Execute again after changing the condition of the specified file.

4138H File related error Simultaneously accessible files exceeded the maximum.

Execute again after decreasing file operations.

4139H File related error The size of the specified file has exceeded that of the existing file.

Execute again after checking the size of the specified file.

413AH File related error The specified file has exceeded the already existing file size.

Execute again after checking the size of the specified file.

413BH File related error The same file was simultaneously accessed from different engineering tools.

When CPU Module Logging Configuration Tool is used An operation was performed to a file being accessed.

Execute again after a while.

413CH File related error The specified file is write-inhibited. Execute again after changing the file condition.

Error code

Error name Error details and cause Action

4 34 ERROR CODES 34.4 List of Error Codes

34

413DH File related error The specified file capacity cannot be secured. Execute again after increasing the capacity of the specified drive (memory).

413EH File related error Operation is disabled for the specified drive (memory). Execute again after changing the target drive (memory).

413FH File related error The file is inhibited to be written to the file storage area. Execute again after changing the specified drive (memory).

414AH Intelligent function module specification error

In a multiple CPU system, operation was performed to a non-controlled intelligent function module or network module.

Execute the operation again from the control CPU of the target module.

414CH Intelligent function module specification error

The specified buffer memory address cannot be accessed.

Execute again after checking the buffer address.

4150H File related error An attempt was made to initialize the drive (memory) protected by the system.

Do not initialize the target drive (memory) as it cannot be initialized.

4151H File related error An attempt was made to delete the file/folder protected by the system.

Do not delete the target file as it cannot be deleted.

4160H Online registration error

The registered number of I/O devices of the forced on/ off target exceeded the maximum.

Cancel the registration of I/O devices of the forced on/off target that is not used.

4168H Online registration error

The number of registered settings of the device test with execution conditions has exceeded 32.

Disable the settings of the device test with execution conditions registered in the CPU module. Alternatively, reduce the number of executional conditioned device tests to be registered at a time.

4169H Online registration error

No settings of the device test with execution conditions are registered.

Check the number of registered settings of the device test with execution conditions in the CPU module, and disable the settings.

416AH Online registration error

The specified execution conditions do not exist. (Device test with execution conditions)

Check whether the execution conditions (program block, step No., and execution timing) specified for disabling settings are registered in the CPU module.

416BH Online registration error

Other than the ladder program was specified for the registration of the device test with execution conditions.

Check and correct the program block specified when the settings of the device test with execution conditions are registered or disabled.

41C1H File related error The format information data of the specified drive (memory) is abnormal.

The file information data may be corrupted. Back up data in the CPU module, and then initialize the

memory.

41C2H File related error File open specification data for file access is wrong. Execute again after checking the specification data.

41C3H File related error Simultaneously accessible files exceeded the maximum.

Execute again after decreasing file operations.

41C4H File related error Simultaneously accessible files exceeded the maximum.

Execute again after decreasing file operations.

41C5H File related error The specified file does not exist. When CPU Module Logging Configuration Tool is used When an attempt was made to re-register the data logging with the previous settings, the corresponding file did not exist.

Execute again after checking the file.

41C7H File related error The specified file/folder or drive (memory) does not exist.

Execute again after checking the file/folder or drive (memory).

41C8H File related error The size of the specified file has exceeded that of the existing file.

Execute again after checking the size of the specified file. If the error recurs after re-execution, the file information data

may be corrupted. Back up data in the CPU module, and then initialize the

memory.

41C9H File related error Access to the file sector has failed. The format information data of the target drive

(memory) is abnormal.

Back up data in the CPU module, and then initialize the memory.

41CAH File related error Access to the file sector has failed. The format information data of the target drive

(memory) is abnormal.

Back up data in the CPU module, and then initialize the memory.

41CBH File related error The file name is specified in a wrong method. Execute again after checking the file name.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 545

54

41CCH File related error The specified file does not exist. Or, the specified subdirectory does not exist.

When CPU Module Logging Configuration Tool is used The data logging was started in a state that sub-folders

for storing data logging files (or folders) cannot be created or accessed. Or, sub-folders cannot be created or accessed while the data logging is being performed or the logged data is being saved.

Execute again after checking the name of the file and subdirectory.

41CDH File related error An access to the file is prohibited in the system. When CPU Module Logging Configuration Tool is used The data logging was started in a state that files (or

folders) cannot be created or accessed because a file (or folder) with the same name exists. Or, files (folders) cannot be created or accessed while the data logging is being performed or the logged data is being saved.

Do not access the specified file or subdirectory. Execute again after checking the file and subdirectory. Execute again after checking the open mode of the file.

41CEH File related error The file cannot be written because the specified file is read-only.

Execute again after checking the attribute of the specified file.

41CFH File related error The specified drive (memory) has been used exceeding the capacity.

Execute again after checking the drive (memory) capacity.

41D0H File related error The specified drive (memory) has no free space. Or, the number of files in the directory of the specified drive (memory) has exceeded the maximum.

Execute again after increasing the free space of the drive (memory).

Delete files in the drive (memory), and execute the function again.

41D1H File related error The file name is specified in a wrong method. The SD memory card is being disabled by SM606 (SD

memory card forced disable instruction).

Execute again after checking the file name. If the error recurs after re-execution, the file information data

may be corrupted. Back up data in the CPU module, and then initialize the

memory. Cancel the SD memory card forced disable instruction.

41D5H File related error The file of the same name exists. Forcibly execute the request, or execute after changing the file name.

41D6H File related error The format information data of the specified drive (memory) is abnormal.

The file information data may be corrupted. Back up data in the CPU module, and then initialize the

memory.

41D7H File related error The format information data of the specified drive (memory) is abnormal.

The file information data may be corrupted. Back up data in the CPU module, and then initialize the

memory.

41D8H File related error The specified file is being accessed. Execute again after a while.

41DFH File related error The specified drive (memory) is write-protected. Execute again after canceling the write protect of the specified drive (memory).

41E0H File related error The specified drive (memory) is abnormal or does not exist.

Check that an SD memory card is inserted, and execute the function again.

Back up data, and then initialize the memory.

41E1H File related error Access to the SD memory card has failed. Back up data, and then write the data to the data memory.

41E4H File related error Access to the SD memory card has failed. Execute the operation again after checking that the SD memory card has been inserted.

Execute the operation again after replacing the SD memory card.

Back up data, and then initialize the memory.

41E7H File related error The format information data of the specified drive (memory) is abnormal.

The file information data may be corrupted. Back up data in the CPU module, and then initialize the

memory.

41E8H File related error The format information data of the specified drive (memory) is abnormal.

The file information data may be corrupted. Back up data in the CPU module, and then initialize the

memory.

41E9H File related error The specified file is being accessed. Execute again after a while.

41EBH File related error The file name is specified in a wrong method. Execute again after checking the file name.

41ECH File related error The file system of the specified drive (memory) is logically corrupted.

The file information data may be corrupted. Back up data in the CPU module, and then initialize the

memory.

41EDH File related error The specified drive (memory) does not have continuous free space. (The free space for file is sufficient but the continuous free space is insufficient.)

Execute again after deleting unnecessary files.

Error code

Error name Error details and cause Action

6 34 ERROR CODES 34.4 List of Error Codes

34

41EFH File related error Creation of the power failure backup data in the specified drive (memory) has failed.

Execute the operation again after checking that the SD memory card has been inserted.

41F0H File related error The power failure backup data of the specified drive (memory) are corrupted.

Execute the operation again after checking that the SD memory card has been inserted.

41F3H File related error The file size is larger than the following: the value to be acquired when 2 bytes are subtracted

from 4G bytes.

Specify a smaller value for the file size when creating a file or changing the file size. Alternatively, divide the file so that each file size is smaller.

41F4H File related error The request cannot be executed because the operation is prohibited by the system.

Do not request the file operation because it is prohibited by the system.

41F5H File related error The command for the (split storage) program was executed to the file other than the (split storage) program file. Or, the command not for the (split storage) program was executed to the (split storage) program file.

Check the command, and request the command applicable to the target file.

41F6H File related error The following files cannot be written because the write- protect function for device data (from outside the CPU module) is enabled. Initial device value file File register file

Do not write the specified file. Clear the setting of the write-protect function for device data

(from outside the CPU module), and execute the request again.

41F8H File related error The data is being accessed from another engineering tool.

Data are being written to the program memory or being transferred to the backup memory.

Access the file after the currently-performed processing ends.

41FAH File related error Program was written beyond the area where the program can be executed.

Execute again after reducing either the already written program or newly written program.

41FBH File related error The specified file is already being manipulated from the engineering tool.

Execute again after the currently performed operation is completed.

41FCH File related error An attempt was made to initialize the drive (memory) being used.

Stop all accesses to the specified drive (memory), and execute the request again.

41FDH File related error There are no data written to the data memory. Write all the required files to the programmable controller.

41FEH File related error The SD memory card has not been inserted. The SD memory card is being disabled. The SD memory card is being disabled by SM606 (SD

memory card forced disable instruction). When CPU Module Logging Configuration Tool is used The data logging was started when the CPU module is

in the following state: no SD memory card is inserted; the CARD READY.LED is not on (green); or the SD memory card is forcibly disabled.

Insert the SD memory card. Remove the SD memory card, and insert it again. Cancel the SD memory card forced disable instruction.

41FFH File related error The type of the SD memory card differs. Check the type of the SD memory card.

4269H Any other error The remote RUN (function) cannot be executed. Execute the function again after a while.

426AH Any other error The date and time data specified by an engineering tool (personal computer) are less than one hour from the start time of daylight saving time.

Specify the time to other than one less than one hour from the start time of daylight saving time using an engineering tool (personal computer). Then, execute the function again.

Check and Correct the start time of the daylight saving time setting.

426BH Any other error Initialization of the battery-less option cassette cannot be executed because, in the CPU parameters, the battery-less option cassette setting is set to "Not Mounted".

Set the battery-less option cassette setting to "Mounted", write the CPU parameters, execute the initialization again.

426CH Any other error The specified operation cannot be performed. Check the settings or the operating status of the recording function.

426DH Any other error The operation cannot be performed because the recording function is running.

Perform the operation after the recording function stops.

4270H Debug related function error

Data logging is being performed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data) to another memory.

Register data logging to the memory where the data logging is being performed. Or, stop the data logging being performed and register again.

When CPU Module Logging Configuration Tool is used Start the data logging to the memory where the data logging is

being performed. Or, stop the data logging being performed, and start the data logging.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 547

54

4271H Debug related function error

The specified data logging is already being performed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data).

Stop the data logging. Or, write, delete, or register data logging to the setting number where no data logging is being performed.

4272H Debug related function error

The trigger logging specifying the device as a trigger condition is being performed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data).

Change the trigger condition. Or, stop the trigger logging being performed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data), and register another trigger logging.

When CPU Module Logging Configuration Tool is used Change the trigger condition. Or, stop the trigger logging

being performed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data), and start another trigger logging.

4275H Debug related function error

Auto logging is being performed. After the auto logging, replace the SD memory card and execute again.

4276H Debug related function error

The function that cannot be executed during the data logging (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data) was executed.

Stop the data logging, and then execute the function.

4277H Debug related function error

The number of saved files exceeded the specified number.

When CPU Module Logging Configuration Tool is used The data logging was started in a state where the

number of saved files has exceeded the specified number. (The operation when the number of saved files exceeded is set to "Stop".) Or, the data logging was started in a state where the number of saved files has exceeded the specified number. (The operation when the number of saved files exceeded is set to "Overwrite".)

The number of files saved in the storage destination memory has exceeded the setting value. Delete files, or change the storage destination and then register.

When CPU Module Logging Configuration Tool is used The number of files saved in the storage destination memory

has exceeded the setting value. Delete files or change the storage destination, and then start the data logging.

4278H Debug related function error

An attempt was made to register data logging in a state where the saved file number has reached its maximum, FFFFFFFF. Or, the number reached to the maximum during the execution.

When CPU Module Logging Configuration Tool is used The data logging was started in a state where the

saved file number has reached its maximum, FFFFFFFF. Or, the number reached to the maximum during the execution.

The saved file number in the storage target memory has reached its maximum, FFFFFFFF. Delete files, or change the storage destination and then register.

When CPU Module Logging Configuration Tool is used The saved file number in the storage target memory has

reached its maximum, FFFFFFFF. Delete files or change the storage target memory, and then perform the data logging.

427AH Debug related function error

The common setting file is corrupted. When CPU Module Logging Configuration Tool is used The data logging was started to the memory where the

corrupted common setting file exists.

Write the common settings to the target memory again. When CPU Module Logging Configuration Tool is used Write the common settings to the target memory again.

427BH Debug related function error

The data logging with the same file storage destination is being performed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data).

When CPU Module Logging Configuration Tool is used The data logging with the same file storage destination

is being performed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data).

Stop the data logging destined for the same storage, and then register. Or, change the storage destination of the file, and then register.

When CPU Module Logging Configuration Tool is used Stop the data logging destined for the same storage, and then

perform another data logging. Or, change the storage destination of the file, and then register.

4280H File transfer function error

A file transfer test was executed from another CPU Module Logging Configuration Tool during execution of a file transfer test.

Execute the file transfer test again after the ongoing test is completed.

Error code

Error name Error details and cause Action

8 34 ERROR CODES 34.4 List of Error Codes

34

4282H Debug related function error

The registration was performed with the internal buffer capacity set to 0.

Check and correct the internal buffer capacity setting.

4283H Debug related function error

An attempt was made to register trigger logging in a state that the specified number of records before trigger has exceeded the number of records that can be collected within the internal buffer capacity.

Check and correct the internal buffer capacity setting. Reduce the number of records before trigger.

4284H Debug related function error

The error codes registered for memory dump are incorrect.

Check and correct the error codes.

4285H Debug related function error

A non-executable function has been executed during collection or save in memory dump.

Execute the function again after the completion of save in memory dump.

4289H Debug related function error

Items that cannot be set as data collection conditions are set.

Check and correct the data collection condition setting.

428AH Data logging function error

The data logging has started while Data is being written to the programmable controller online. The global label assignment information is being written to the programmable controller (data memory).

Start the data logging after the online data write to the programmable controller has completed.

Start the data logging after the writing of the global label assignment information to the programmable controller has completed.

428CH Data logging function error

Execution fails because any of the following files does not exist. CPU parameter file Global label setting file Program file with the target program name

Write the following files to the CPU module. CPU parameter file Global label setting file Program file with the target program name

4290H Data logging function error

The program file or global label setting file was changed during the realtime monitor where a label (global label or local label) is specified as a monitor target, timing condition, or trigger condition.

Do not change the program file or global label setting file during the realtime monitor where a label (global label or local label) is specified.

Stop the realtime monitor where a label (global label or local label) is specified.

Check and correct the setting of the special register (SD940), and execute the function again.

4291H Debug related function error

Online program change has been executed during the execution of the real-time monitor where a step number is specified as "Timing" or "Trigger condition".

After the completion of the online program change, check the step number specified and execute real-time monitor again.

4292H Debug related function error

Real-time monitor does not begin during the execution of real-time monitor.

Start real-time monitor after the stop of the real-time monitor being executed.

4293H Debug related function error

Execution fails because the internal buffer exceeds its maximum capacity.

Check and correct the settings of internal buffer capacity, and then try again.

4294H Debug related function error

Execution fails because the settings of internal buffer capacity has been changed during the execution of functions that consume the internal buffer.

Deactivate the functions that consume the internal buffer, and then try again. Or, restore the internal buffer capacity to the previous state, and then try again.

433CH Maintenance and inspection error

The error was not cleared. (Error clear was performed during execution of error clear.)

Execute again after a while. If the same error code is displayed again, the possible cause is a hardware failure of the target module. Please consult your local Mitsubishi representative.

433DH Maintenance and inspection error

The target module cannot handle the error clear. Check the target module. (Check the module in which the error occurred.)

4400H Security function error

A file protected by a password has been opened without unlocking the password.

Enter a correct password and perform password authentication.

4401H Security function error

Read password authentication has failed when required.

The file password format is incorrect.

Set a correct read password and perform password authentication.

Access the file with the correct method.

4402H Security function error

Write password authentication has failed when required.

The file password format is incorrect.

Set a correct write password and perform password authentication.

Access the file with the correct method.

4403H Security function error

Both passwords for reading and for writing that are set upon Create, Change, Delete, or Disable do not match the previous ones.

Set correct passwords for both reading and writing, and perform password authentication.

4404H Security function error

A file error was detected before or after performing Create, Change, or Delete.

Initialize the drive including the target file by initializing the memory.

Write the target file to the programmable controller again, and then register or cancel the file password.

4408H Security function error

Password authentication failed when access was required.

Set a correct password and perform password authentication again.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 549

55

4409H Security function error

Password authentication failed when access was required.

Set a correct password and perform password authentication again 1 minute later.

440AH Security function error

Password authentication failed when access was required.

Set a correct password and perform password authentication again 5 minutes later.

440BH Security function error

Password authentication failed when access was required.

Set a correct password and perform password authentication again 15 minutes later.

440CH Security function error

Password authentication failed when access was required.

Set a correct password and perform password authentication again 60 minutes later.440DH

440EH Security function error

The security function was activated and password authentication cannot be performed.

Set a correct password and perform password authentication again after a certain period of time.

440FH Security function error

An operation was performed to the firmware update prohibited file with a file password set.

Disable the file password setting.

4410H Security function error

The file of the locked CPU module is accessed without the security key authentication.

Register the security key which locks the CPU module to the engineering tool.

When the project is opened, lock the project with the security key which locks the CPU module.

When the CPU module is locked, the access control target file cannot be accessed using the following functions or external devices.

FTP server function SLMP/MC protocol GOT EZSocket

4412H Security function error

The security key cannot be registered to the CPU module due to the failure of the internal memory where the security key is registered. Or, the security key of the CPU module cannot be deleted.

Hardware failure of the CPU module. Replace the CPU module.

4413H Security function error

Since the CPU module is locked and 32 engineering tools are reading and writing programs simultaneously, another engineering tool cannot read or write programs.

Wait until the number of engineering tools which are reading and writing programs decreases to 31 or less, and read or write programs.

4414H Security function error

The request cannot be executed because the CPU module is locked.

Do not execute the request because it cannot be executed by the CPU module which is locked.

4415H Security function error

The request cannot be executed because the CPU module is not locked.

Do not execute the request because it cannot be executed by the CPU module which is not locked.

4416H Security function error

The request cannot be executed because the CPU module lock or unlock processing is being performed.

Execute the request again after the lock or unlock processing ends.

4417H Security function error

An attempt was made to write or delete the security key with no extended SRAM cassette or battery-less option cassette inserted in the CPU module.

Check that an extended SRAM cassette or battery-less option cassette is correctly inserted, and then perform the operation again.

4418H Security function error

The security key cannot be changed or deleted because any locked program exists in the CPU module.

Unlock all the programs in the CPU module.

4422H Security function error

The access target CPU module does not support the security key information stored in the engineering tool.

Change the security key information version of the engineering tool in accordance with the version supported by the target CPU module.

4424H Security function error

The security key set to the file written by executing the file batch online change function does not match the one registered to the CPU module (or extended SRAM cassette/battery-less option cassette).

Set the same security key registered to the CPU module to the file, and then execute the file batch online change function.

4425H Security function error

The file with a security key was written by executing the batch file online change function, but no security key is registered to the CPU module (or extended SRAM cassette/battery-less option cassette).

Clear the security key set to the file, and then execute the online change function.

4800H iQ Sensor Solution related error

The specified command cannot be executed because the iQ Sensor Solution data backup/restoration function is being executed.

Execute the command again after the processing of the data backup/restoration function ends.

Error code

Error name Error details and cause Action

0 34 ERROR CODES 34.4 List of Error Codes

34

4801H iQ Sensor Solution related error

When the iQ Sensor Solution data backup/restoration is requested, the target module does not exist.

When the iQ Sensor Solution data restoration is requested, the specified backup folder does not exist.

The value in the special register (SD) related to the iQ Sensor Solution data backup/restoration is out of range.

Check and correct the value in the special register, and execute the function again.

Check that the backup data created by the MELSEC iQ-R series module is specified.

4802H iQ Sensor Solution related error

The number of backup folders used by the iQ Sensor Solution data backup/restoration function has reached to its limit.

Delete an existing backup folder(s), and execute the function again.

Set "Automatic specification (Folder deletion supported)" in the special register for setting a backup target folder number.

4803H iQ Sensor Solution related error

The system file does not exist in the specified backup data, or the system file is corrupted.

Specify another backup data.

4804H iQ Sensor Solution related error

The backup file does not exist in the specified backup data, or the backup file is corrupted.

Specify another backup data.

4805H iQ Sensor Solution related error

When the iQ Sensor Solution data backup function is executed, no backup target device exists.

The data backup function was executed to a device which does not support the function.

Check and correct the value in the special register, and execute the function again.

Execute the function to a device which supports the function.

4806H iQ Sensor Solution related error

An SD memory card is in the following state while the function is being executed. An SD memory card is not inserted. An SD memory card is disabled by SM606 (SD

memory card forced disable instruction).

Insert or re-insert an SD memory card, and execute the function again.

Enable the SD memory card operation, and execute the function again.

4807H iQ Sensor Solution related error

Data communications cannot be performed with a target device of the iQ Sensor Solution data backup/ restoration function.

Check the operation of the target device. Check the network status between the target device, such as

cables, hubs, and routers. The line may be busy. Perform a retry after a while. Check and correct the communication timeout time of data

backup/restoration specified in the special register.

4808H iQ Sensor Solution related error

When the backup data is restored to the device supporting iQ Sensor Solution, data communications cannot be performed with the restoration target device.

When backup data is restored to the device supporting iQ Sensor Solution, the device of the specified backup data and the restoration target device do not match.

Check the operation of the target device. Check the connections and network status between the target

device, such as cables, hubs, and routers. The line may be busy. Perform a retry after a while. Check and correct the specified backup data and the device

supporting iQ Sensor Solution (manufacturer, model name, version) specified as the restoration target device.

4809H iQ Sensor Solution related error

The data backup/restoration function of iQ Sensor Solution was executed to the module which does not support the function.

Replace the module with the one which supports the function. Execute the function to the module which supports the

function.

480AH iQ Sensor Solution related error

The function was executed to the CC-Link module whose operation had been switched from the standby master station to master station.

After powering off and on the master station and standby master station, execute the function again.

480BH iQ Sensor Solution related error

The function was executed for the CC-Link module to which "Read Model Name of Slave Station" is not set in the setting of the automatic detection function of connected devices.

Select "Read Model Name of Slave Station" in the setting of the automatic detection function of connected devices, and execute the function again.

480CH iQ Sensor Solution related error

The specified command cannot be executed because the automatic detection of connected device function of iQ Sensor Solution is being executed.

Execute the command again after the automatic detection processing ends.

480DH iQ Sensor Solution related error

The specified command cannot be executed because the communication setting reflection function of iQ Sensor Solution is being executed.

A communication timeout occurred in a command of a device supporting iQ Sensor Solution.

Execute the command again after the communication setting reflection processing ends.

Check and correct the communication time check setting value using the engineering tool.

480EH iQ Sensor Solution related error

The specified command cannot be executed because the monitor function of iQ Sensor Solution is being executed.

The specified command cannot be executed because the sensor parameter read/write function of iQ Sensor Solution is being executed.

A communication timeout occurred in a command of a device supporting iQ Sensor Solution.

Execute the function again after a while. Execute the command again after the sensor parameter read/

write processing ends. Check and correct the communication time check setting

value using the engineering tool.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 551

55

4810H iQ Sensor Solution related error

The series of the CPU module where the iQ Sensor Solution data restoration function is to be executed differs from the series of the CPU module where the iQ Sensor Solution data backup function was executed. Or the restoration target module differs from the backup target module.

Check the series of the CPU module where the data backup function was executed and the backup target module.

4811H iQ Sensor Solution related error

The series of the CPU module where the iQ Sensor Solution data backup function is to be executed differs from the series of the CPU module where last time the function was executed. Or the last backup target module differs from the current backup target module.

Execute the data backup function to the module where the data backup function was executed last time.

Set a different folder number.

4812H iQ Sensor Solution related error

The functions that cannot be executed simultaneously with the data backup/restoration function of iQ Sensor Solution, such as the file transfer function (FTP server/ client), are being executed.

Execute the function again after a while.

4902H Any other error The communications have stopped because an error occurred in another simple CPU communication function setting No. for which the same communication destination is specified in the simple CPU communication function.

Eliminate the error cause of the simple CPU communication setting No. with an error.

4905H Any other error The capacity of label area used exceeded its limit. Check the program, delete the unused local and global label definitions, compile the program, and then write the program to the programmable controller.

Change the label area size in parameter, compile the program, and then write the program to the programmable controller.

4906H Any other error The file register data cannot be cleared by either of the following reasons: The QDRSET instruction was executed more than

once after the CPU module was powered on or reset. The file register setting parameter is set to the one

other than "Use Common File Register in All Programs".

If the QDRSET instruction is being executed, power on or reset the CPU module.

The operation cannot be performed if the file register setting parameter is not set to "Use Common File Register in All Programs".

4907H Any other error The target CPU module does not support "Access from External Device" of "Global Label Setting".

Disable "Access from External Device", and then write the data to the programmable controller again.

4908H Any other error The specified program execution type is not supported. Check the program execution type specified.

4909H Any other error A second SFC program has been started while an SFC program was running.

Check the execution status of the SFC program.

490AH Any other error An SFC program is stopped while "Stop Mode" is set to "Hold output after stop".

Set "Stop Mode" to "Stop output after stop".

490BH Any other error A program has started or stopped while the CPU module is in the STOP or PAUSE state.

Set the CPU module to the RUN state and execute the program again.

4A00H Network error Access to the specified station cannot be made since the routing parameters, network number/station, or network station <-> IP-related information setting are not set to the start source CPU module and/or relay CPU module.

For routing via a multiple CPU system, the control CPU module of the network module for data routing or the CPU module for data routing has not started.

The third byte of the IP address (network number) specified for the IP communication test is the same as that of the CPU module where the test is executed.

The CPU module that performs IP packet transfer is not the control CPU of the CC-Link IE module, which is on the path that IP packets travel.

Set the routing parameters, network number/station, or network station <-> IP-related information setting for accessing the specified station to the related stations.

Retry after a while. Or, start communication after checking that the system for data routing has started.

Do not use the same third byte of the IP address (network number) specified for the IP communication test with that of the CPU module where the test is executed.

Set the CPU module that performs IP packet transfer as the control CPU of the CC-Link IE module, which is on the path that IP packets travel.

4A01H Network error The network of the number set to the routing parameters does not exist.

The specified CPU module cannot be communicated through the network that is not supported by the CPU module.

Check and correct the routing parameters set to the related stations.

Set communication through the network that is supported by the specified CPU module.

4A02H Network error Access to the specified station cannot be made. Check the network module for error, or check that the modules are not in offline.

Check if the network numbers/PC numbers are correctly set.

4A03H Network error A request for network test was issued. Check the request of the SLMP/MC protocol.

Error code

Error name Error details and cause Action

2 34 ERROR CODES 34.4 List of Error Codes

34

4A05H Link related error (file related error)

121 stations or more are specified to the station number.

Check the station number.

4A10H Link related error (file related error)

The number of files in the specified folder exceeded the limit.

Reduce the number of files in the specified folder.

4A20H IP communication test error

The upper 2 bytes of the IP addresses do not match between the CPU module and the request destination device on the same path that IP packets travel.

The upper 2 bytes of the IP addresses do not match between the CPU module and the CC-Link IE module on the same path that IP packets travel.

The upper 2 bytes of the IP addresses do not match between the CC-Link IE modules on the same path that IP packets travel.

The upper 2 bytes of the IP addresses do not match between the request source device and the CPU module connected to the request destination device by Ethernet.

Check and correct the IP address settings of the CPU module. Check and correct the IP address of the request destination

device. Check and correct the IP address of the CC-Link IE module. Check and correct the IP address of the request source

device.

4A21H IP communication test error

The 3rd byte (Network No.) or 4th byte (Station No.) of the IP address of the CPU module is the number that is not available for CC-Link IE.

The 3rd byte (Network No.) or 4th byte (Station No.) of the IP address of the request destination device is the number that is not available for CC-Link IE.

Check and correct the IP address settings of the CPU module. Check and correct the IP address of the request destination

device.

4A22H IP communication test error

The IP address is not set to the CC-Link IE module on the path that IP packets travel.

Set the IP address to the CC-Link IE module used as a master station.

Check the communication status with the master station when the CC-Link IE module is used as a local station.

Replace the CC-Link IE module (master station) with the one that supports the IP packet transfer function.

Conduct the IP communication test again after the CC-Link IE module is started up.

Check and correct the IP address of the request destination device.

4A23H IP communication test error

The CPU module on the path that IP packets travel does not support the IP packet transfer function.

Routing parameters are set so that IP packets are routed to CPU modules that are incompatible with IP packet transfer.

Replace the CPU module with the one supporting the IP packet transfer function.

Correct routing parameter so that IP packets are routed to the CPU module that supports the IP packet transfer function.

Check and correct the IP address of the request destination device.

4A24H IP communication test error

The CC-Link IE module on the path that IP packets travel does not support the IP packet transfer function.

Routing parameters are set so that IP packets are routed to the network module that does not support the IP packet transfer function.

The 3rd byte (Network No.) of the IP address of the device on the path that IP packets travel is overlapping with the network No. of the module connected to the CPU module and does not support the IP packet transfer function.

The 3rd byte (Network No.) of the IP address of the request destination device is overlapping with the network No. of the module connected to the CPU module and does not support the IP packet transfer function.

Replace the CC-Link IE module with the one supporting the IP packet transfer function.

Correct routing parameter so that IP packets are routed to the CC-Link IE module that supports the IP packet transfer function.

Check and correct the setting so that the 3rd byte (Network No.) of the IP address of the device on the path that IP packets travel does not overlap with the network No. of the module connected to the CPU module and does not support the IP packet transfer function.

Check and correct the setting so that the 3rd byte (Network No.) of the IP address of the request destination device does not overlap with the network No. of the module connected to the CPU module and does not support the IP packet transfer function.

Check and correct the IP address of the request destination device.

4A25H IP communication test error

The IP packet transfer setting is not set. Routing parameters are set so that IP packets are

routed to the CPU module where IP packet transfer setting is not set.

Select "Use" for the IP packet transfer function setting in the CPU parameters.

Correct routing parameters so that IP packets are routed to the CPU module where IP packet transfer setting is set.

Check and correct the IP address of the request destination device.

4A27H IP communication test error

The CPU module that performs IP packet transfer is not the control CPU of the CC-Link IE module, which is on the path that IP packets travel.

Set the CPU module that performs IP packet transfer as the control CPU of the CC-Link IE module, which is on the path that IP packets travel.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 553

55

4A28H IP communication test error

In the system where the CPU module is connected to the request destination device over Ethernet, the request path and the response path of IP packets differ.

When multiple CC-Link IE modules with the same network number are connected in a multiple CPU system, the CC-Link IE module mounted on the lowest number slot is not set as a controlled module of the CPU module that transfers IP packets.

When multiple CC-Link IE modules with the same network number are connected in a single or multiple CPU system, the station number of the CC-Link IE module mounted on the lowest number slot is not set as a relay station number in routing parameter.

Correct the routing parameter setting so that IP packets travel the same path for both request and response transmission.

When multiple CC-Link IE modules with the same network number are connected in a multiple CPU system, set the module mounted on the lowest number slot as a controlled module that transfers IP packets.

When multiple CC-Link IE modules with the same network number are connected in a single or multiple CPU system, set the station number of the module mounted on the lowest number slot as a relay station number in routing parameter.

4A29H IP communication test error

The 3rd byte (network No.) of the IP address of the request destination device is overlapping with the 3rd byte of the IP address of the CPU module connected to the request source device over Ethernet.

Check and correct the IP address settings of the CPU module. Check and correct the IP address of the request destination

device.

4A2AH IP communication test error

An IP address of a device on CC-Link IE network or the CPU module is not specified.

Specify an IP address of a device on CC-Link IE network or the CPU module.

4B00H Target module error An error occurred in the access destination or the relay station.

The specified connection destination (request destination module I/O number) is incorrect.

The access destination CPU module has not started up.

The target CPU No. specified does not exist.

Check the error occurred in the specified access destination or the relay station, and take an action.

Check the connection destination (request destination module I/O number or PC number) in the request data of SLMP/MC protocol.

Check the stop error, and take an action. Check and correct the target CPU No.

4B02H Target module error The request is not addressed to the CPU module. Perform operation for the module that can execute the specified function.

4B03H Target module error The specified route is not supported by the specified CPU module version.

The communication target CPU module is not mounted.

A device mounted on the specified route does not support communications.

Check whether the specified route is supported or not. Check the mounting status of the CPU module. Check the stop error, and take an action.

4B04H Target module error The specified connection destination (request destination module I/O number) is not supported.

An invalid value is set as the start I/O number of the connection target module. Set the start I/O number of the target module correctly, and retry data communications.

4C00H Data logging function error

There is not enough free space for storing the result file in the target memory.

Increase the free space, and create the result file again.

4C01H Data logging function error

Writing of the result file to the target memory has not completed successfully because the SD memory card is write-protected.

Writing of the result file to the target memory has not completed successfully because the folder/file structure is incorrect.

Unlock the write protect switch of the SD memory card, and write the result file again.

Check that the target memory is broken. Check that the folder or file to be used in the target memory is

deleted.

4C02H Data logging function error

The SD memory card was removed while the data logging function was being executed (data logging status: Waiting RUN Not collected, Waiting to establish collection conditions Not collected, Waiting start Not collected, Pause, Collecting, Waiting trigger Collecting before trigger, Collecting after trigger, or Saving in progress). Or, writing to the SD memory card has not completed successfully.

Insert the SD memory card and execute the function again. Replace the SD memory card and execute the function again.

4C03H Data logging function error

The number of files in the root directory and subdirectory in the target memory exceeded the limit.

Increase the free space of the drive (memory), and execute the function again.

Delete files in the drive (memory), and execute the function again.

4C04H Data logging function error

During auto logging, a data logging was not registered due to a registration failure of the data logging with another setting number.

Clear the error, and start auto logging.

Error code

Error name Error details and cause Action

4 34 ERROR CODES 34.4 List of Error Codes

34

4C05H Data logging function error

The online change function was executed while the data logging function specifying the step number as a sampling or trigger condition was being executed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data).

Do not execute the online change function while the data logging function specifying the step number is being executed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data).

Stop the data logging function specifying the step number.

4C06H Data logging function error

System error Check the specified data, and write it to the CPU module again.

4C07H Data logging function error

A data logging is attempted to start with a data storage memory that is different from the one for the data logging already registered.

Check and correct the setting for the data logging to be started.

4C08H Data logging function error

Three or more of the data logging that the CPU built-in memory (function memory) is specified as the data storage memory are attempted to start.

Check and correct the setting for the data logging to be started.

Check that the version of the CPU module is designed to make it possible to start three or more settings of logging operation with "CPU built-in memory (function memory)" specified for the data storage destination memory.

4C09H Data logging function error

Free space in the target memory (data memory) is not enough.

Increase the free space in the target memory (data memory) and execute the function again.

4C0AH Data logging function error

The target drive (data memory) is abnormal Initialize the memory to bring the drive (data memory) back to normal state.

4C0BH Data logging function error

A data logging file that is being transferred is deleted. Reading from (an access to) a data logging file is

failed. The specified file does not exist. Or, the specified

subdirectory does not exist.

Check and correct the number of files to be saved in the file switching setting.

Check that the data logging file is not deleted. Check that an SD memory card is inserted. Check the file name and subdirectory name. Then, execute

the function again.

4C0CH Data logging function error

The data logging file transfer function is executed while the access to the SD memory card is forcibly disabled.

The SD memory card is removed during the data logging file transfer function is executed.

Clear the disabled state of the SD memory card and execute the function again.

Insert the SD memory card and execute the function again.

4C0DH Data logging function error

A data logging is attempted to start during a transfer of a result file.

Restart the data logging after the completion of the data logging file transfer function.

4C0EH Data logging function error

A file transfer is stopped by the data logging file transfer stop request.

Do not send the data logging file transfer stop request.

4C0FH Data logging function error

The program file or global label setting file was changed while the data logging function specifying the label (global label or local label) as the collection start condition, data collection target, or trigger condition was being executed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data).

Do not change the program file or global label setting file while the data logging function specifying the label (global label or local label) is being executed (data logging status: RUN waiting (no collection), Condition waiting (no collection), Start waiting (no collection), Pause, Collecting, Trigger waiting (collecting before trigger), Collecting after trigger, or Saving the logging data).

Stop the data logging specifying the label (global label or local label).

Check and correct the setting of SD940 (Stop direction at file change on label specification), and execute the function again.

4C10H CPU module data backup/restoration function error

The maximum allowable capacity is exceeded. The maximum allowable number of files is exceeded. The upper limit of the backup folder number is

exceeded. The maximum length (255 characters) of the file path is

exceeded.

Increase the free space of the SD memory card and CPU module, and execute the function again.

Delete files in the SD memory card and CPU module, and execute the function again.

Delete backup data in the SD memory card and CPU module, and execute the function again.

Check and correct the folder structure or folder/file names of backup target data, and execute the data backup function again.

4C11H CPU module data backup/restoration function error

An SD memory card is not inserted. An SD memory card is disabled by SM606 (SD

memory card forced disable instruction).

Insert or re-insert an SD memory card, and execute the function again.

Enable the SD memory card operation, and execute the function again.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 555

55

4C12H CPU module data backup/restoration function error

Reading/writing of data from/to an SD memory card completed with an error.

Check that an SD memory card is inserted, and execute the function again.

Replace an SD memory card, and execute the function again. The backup data may have been corrupted. Execute the data

restoration function using another backup data.

4C13H CPU module data backup/restoration function error

Reading/writing of data from/to the CPU built-in memory completed with an error.

Back up data in the CPU built-in memory, initialize the memory, and write the data back to the original memory. Then, execute the data backup/restoration function.

The possible cause is a hardware failure of the restoration target CPU module. Execute the data restoration function to another CPU module.

4C14H CPU module data backup/restoration function error

The CPU module data backup/restoration function cannot be executed because a file password is set to the data.

Data was restored to the CPU module where the same data with a file password has already been stored.

Delete file passwords, and execute the CPU module data backup/restoration function.

4C15H CPU module data backup/restoration function error

Any of the following functions that cannot be executed simultaneously with the CPU module data backup/ restoration function is being executed: the file transfer function (FTP), data backup/restoration (iQ Sensor Solution function), IP address change function, or firmware update function (via the engineering tool).

The CPU module data backup/restoration function is executed when the following functions are being executed. Online program change File transfer function (FTP server)

Execute the function again after a while.

4C16H CPU module data backup/restoration function error

The automatic backup setting by specification of day and time is turned on while the setting value (automatic backup date and time) are out of range.

The automatic backup setting by specification of time and day of the week is turned on while the setting value (automatic backup time and day of the week) are out of range.

Review the setting value (automatic backup date and time) and turn on the automatic backup setting by specification of day and time.

Review the setting value (automatic backup time and day of the week) and turn on the automatic backup setting by specification of time and day of the week.

4C17H CPU module data backup/restoration function error

The model of the restoration target CPU module differs from the model of the backup source CPU module.

Execute the data restoration function to the CPU module whose model is the same as that of the backup source CPU module.

4C18H CPU module data backup/restoration function error

Data was restored while the operating status of the CPU module is in RUN or PAUSE.

Change the operating status of the CPU module to STOP, and execute the function again.

4C19H CPU module data backup/restoration function error

The data restoration function was executed with backup files ($BKUP_CPU_INF.BSC and BKUP_CPU.BKD) not structured properly.

Data (file(s)) is missing in the backup file ($BKUP_CPU_INF.BSC) in the backup data folder.

The data restoration function was executed with a folder where no backup files ($BKUP_CPU_INF.BSC, BKUP_CPU.BKD, and BKUP_CPU_DEVLAB.BKD) are stored.

The backup data may have been corrupted. Execute the data restoration function using another backup data.

4C1AH CPU module data backup/restoration function error

A folder with a value that matches the restoration target date folder setting value or number folder setting value does not exist in the SD memory card.

The restoration target data setting value is out of range.

The restoration target date folder setting value or number folder setting value is out of range.

Check and correct the restoration target date folder setting value or number folder setting value, and execute the function again.

Check and correct the restoration target data setting value, and execute the function again.

4C1BH CPU module data backup/restoration function error

The data restoration function was executed to the CPU module whose status (such as programs, parameters, and file structure) differs from that of when the data backup function was executed.

Match the CPU module status to the one at the time of backup, and execute the function again.

Set all data as the restoration target data, and execute the automatic data restoration function.

4C1CH CPU module data backup/restoration function error

An SD memory card is not inserted. An SD memory card is disabled by SM606 (SD

memory card forced disable instruction). An SD memory card is write-protected.

Insert or re-insert an SD memory card, and execute the function again.

Enable the SD memory card operation, and execute the function again.

Cancel the write protection, and execute the function again.

Error code

Error name Error details and cause Action

6 34 ERROR CODES 34.4 List of Error Codes

34

4C1EH CPU module data backup/restoration function error

The status of the SFC program (such as step status and transition conditions) was changed during execution of the data backup function.

Take measures so that the status of the SFC program does not change during execution of the data backup function, and execute the function again.

4C1FH CPU module data backup/restoration function error

The specified command cannot be executed because the CPU module data backup/restoration function is being executed.

Execute the command again after the data backup/restoration processing ends.

4C20H CPU module data backup/restoration function error

The data backup/restoration function was executed while the CPU module was in a state where this function could not be executed.

Deselect the "Access from External Device" checkbox in the label setting window or delete labels with this item selected, and initialize the memory which is written the global label assignment information. Then, execute the data backup function again.

Initialize the memory where the global label assignment information is written and execute the restoration function again.

Check the firmware version of the CPU module and execute the automatic data restoration function again.

4C21H CPU module data backup/restoration function error

The number of backup data stored in an SD memory card exceeds the upper limit value.

Delete backup data in the SD memory card, and execute the function again.

Check and correct the settings of the upper limit value of the number of backup data, and execute the function again.

4C22H CPU module data backup/restoration function error

Bit 5 of SD944 has been turned on while the set value of SD1353 is out of the allowable range.

Check and correct the set value of SD1353, and turn on bit 5 of SD944.

4C23H CPU module data backup/restoration function error

Upper limit value of the number of the backup data cannot be changed because a CPU data folder has already been in an SD memory card.

After deleting the CPU data folder in the SD memory card and turning off bit 5 of SD944, turn on bit 5 of SD944 again.

4C24H CPU module data backup/restoration function error

The data cannot be backed up because more backup data than the upper limit value of the number of backup data exists in the SD memory card.

Delete the backup data exceeding the upper limit value, and execute the function again.

Check and correct the settings of the upper limit value of the number of backup data, and execute the function again.

4C40H File transfer function (FTP client) error

When files are specified by using wild card characters for the file transfer function instruction, the number of files matched exceeds the upper limit of the transferable number of files.

When files are specified by using wild card characters for the file transfer function instruction, no files are matched.

Check and correct the wild card specification. Check if the specified folder path exists.

4C43H File transfer function (FTP client) error

The number of processing completed files for sending or acquiring FTP client file is mismatched with the total number of processing files.

Execute the function again.

4C44H File transfer function (FTP client) error

The file transfer function (FTP client) is executed while the following functions are being executed. CPU module data backup/restoration function iQ Sensor Solution data backup/restoration function

Execute the File transfer function (FTP client) again after the mentioned function is completed.

4C50H Special relay and special register function error

The free space in the data memory is not enough. Increase the free space in the target memory (data memory) and execute the function again.

4C51H Special relay and special register function error

Writing to the data memory is not completed successfully.

Initialize the memory to bring the drive (data memory) back to normal state.

4C52H Special relay and special register function error

The function memory clear request or the data memory file transfer request is sent during a data logging.

Do not send the function memory clear request or the data memory file transfer request during a data logging.

4C53H Special relay and special register function error

The function memory clear request or the data memory file transfer request is sent during execution of the following functions. File batch online change Data transfer to the data memory Writing the global label assignment information to the

programmable controller (data memory)

Send the function memory clear request or the data memory file transfer request after the completion of the functions.

4C54H Special relay and special register function error

The request cannot be executed because the CPU module is not in the STOP state.

Set the operating status of the CPU module to STOP, and execute the request again.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 557

55

4C55H Special relay and special register function error

The number of files in the root directory and subdirectory in the data memory exceeded the limit.

Increase the free space in the data memory and execute the request again.

Delete files in the data memory, and execute the request again.

4C56H Special relay and special register function error

Reading from (an access to) a file is failed. The specified file does not exist. Or, the specified

subdirectory does not exist.

Check that the file is not deleted. Check the file name and subdirectory name. Then, execute

the function again.

4D40H Firmware update function error (Via engineering tool)

Access to the flash ROM of the module to be updated has failed.

Perform the firmware update to the module again.

4D41H Firmware update function error (Via engineering tool)

Access to the module to be updated has failed. The module is unable to perform the firmware update. An incorrect firmware update file (a firmware update

file not for the module to be updated) has been used. An invalid firmware update file has been used.

Check the following and perform the firmware update again. No hardware failure occurs in the base unit or the module. The module started up normally. The module is able to perform the firmware update. The correct firmware update file for the module is set in the

engineering tool. The name or contents of the firmware update file are not

changed from their original state.

4D44H Firmware update function error (Via engineering tool)

A firmware update file of the version that cannot be installed on the module used has been used.

The module does not support the firmware update. The module information cannot be read from the

module to be updated.

Use the module with a firmware version that supports the firmware update using the engineering tool.

Check if the module supports the firmware update. Check that the module is mounted properly, reset the CPU

module, and perform the firmware update again.

4D45H Firmware update function error (Via engineering tool)

The firmware update is disabled. Enable the firmware update and perform the operation again.

4D46H Firmware update function error (Via engineering tool)

The engineering tool and the CPU module are connected incorrectly. (The cable connection and/or connection settings in the engineering tool are not correct.)

Check the cable connection and/or the settings in the "Specify Connection Destination" window that the CPU No.1 is connected via USB or an Ethernet port ("Ethernet Port Direct Connection"/"Connection via HUB").

Check that the "Target PLC" is set to "Not Specified" in the "Specify Connection Destination" window of the engineering tool.

4D47H Firmware update function error (Via engineering tool)

The operation cannot be performed because the firmware update is being performed from another engineering tool.

The operation cannot be performed because the CPU No.1 was not reset after the last firmware update.

A communication error occurred in the last firmware update.

Perform the firmware update to the module again after the completion of the update from the other engineering tool.

Manually reset the CPU module and perform the firmware update again.

4D48H Firmware update function error (Via engineering tool)

The firmware update cannot be performed due to a CPU module stop error.

The module may be faulty.

Check the parameters. Check whether the module is mounted correctly. If the same error code is displayed again, please consult your

local Mitsubishi representative.

4D49H Firmware update function error (Via engineering tool)

The CPU No.1 has been powered off or reset during the firmware update processing.

The engineering tool has been exited or a communication error has occurred during the firmware update processing.

Perform the firmware update again.

4D4AH Firmware update function error (Via engineering tool)

The firmware update has been performed to the module that the CPU No.1 does not support.

The firmware update has been performed using the firmware update file that the CPU No.1 does not support.

An invalid firmware update file has been used.

Update the CPU No.1 to the latest firmware version and perform the firmware update again.

Ensure that the name or contents of the firmware update file is not changed from its original state.

4D4BH Firmware update function error (Via engineering tool)

The CPU modules of CPU No.2 and later do not support the firmware update using the engineering tool.

Update the CPU modules of CPU No.2 and later to the latest version by performing the firmware update using an SD memory card, and perform the operation again.

4D4CH Firmware update function error (Via engineering tool)

The module to be updated cannot be updated on the extension base unit.

The firmware update file set in the engineering tool cannot be used for the module on the engineering tool.

Mount the module to be updated to the main base unit and perform the firmware update again.

Set the correct firmware update file for the module to be updated in the engineering tool, and perform the firmware update again.

Error code

Error name Error details and cause Action

8 34 ERROR CODES 34.4 List of Error Codes

34

4D4DH Firmware update function error (Via engineering tool)

A firmware data error has been detected during the firmware update processing.

Perform the firmware update again.

4D4EH Firmware update function error (Via engineering tool)

The specified operation cannot be performed because the firmware update is being performed.

The specified operation cannot be performed because the CPU No.1 was not reset after the firmware update.

Reset the CPU module after the completion of the firmware update and perform the specified operation again.

4D4FH Firmware update function error (Via engineering tool)

The firmware update has been performed to the module controlled by the CPU module of CPU No.2 or later.

Set its control CPU to the CPU No.1 and perform the firmware update again.

Update the firmware of CPU No.1 to the latest version and perform the firmware update again.

4D50H Firmware update function error (Via engineering tool)

A remote operation has been performed to the CPU module of CPU No.2 or later during the firmware update processing.

The firmware update has been performed while the CPU module of CPU No.2 or later is the RUN state.

Reset the CPU module and perform the firmware update again.

Change the operating status of the CPU module of CPU No.2 or later to STOP. Reset the CPU module and perform the firmware update again.

4D52H Firmware update function error (Via engineering tool)

The control CPU does not support firmware updates using the engineering tool.

Update the control CPU to a version supporting the firmware update function, and perform the firmware update again.

4D53H Firmware update function error (Via engineering tool)

Performed an update on a module controlled by a CPU module executing another function.

Check that the control CPU is not executing another function, and perform the firmware update again.

Error code

Error name Error details and cause Action

34 ERROR CODES 34.4 List of Error Codes 559

56

Codes of errors detected by other than the self-diagnostic function (C000H to CFFFH) The following table lists the codes of errors related to the Ethernet-equipped module and CC-Link IE Field Network Basic. These error codes are not stored in SD0 because they are not detected by the self-diagnostic function of the CPU module.

Error code

Error name Error details and cause Action

C000H to CFBFH

MELSEC iQ-R Ethernet User's Manual (Application)

CFC0H Cyclic transmission error (master station)

Unable to execute cyclic transmission because multiple master stations exist in the same network address.

Check the existence status of master station in network.

CFC1H Cyclic transmission error (master station)

Unable to execute cyclic transmission because the error occurred in cyclic transmission.

Take measures to reduce noise. If the same error is displayed again, please contact your

local Mitsubishi representative.

CFC8H Cyclic transmission error (master station)

Unable to execute cyclic transmission because the slave station controlled by other master station exists.

Check the existence status of master station in network. Check the slave station where the error occurred.

CFC9H Cyclic transmission error (master station)

Unable to execute cyclic transmission because the slave station of the same IP address exists in the same network address.

Check the existence status of slave station in network. Check the slave station where the error occurred.

CFD0H Master station error

The port No. (61450) used in CC-Link IE Field Network Basic has already been used.

Check the port No. used in Ethernet function.

CFD1H Master station error

Invalid value has been set in subnet mask. Check the parameter setting.

CFE0H Cyclic transmission error (slave station)

The cyclic transmission was executed for the slave station controlled by other master station.

Check the existence status of master station in network. Check the slave station where the error occurred.

CFE1H Cyclic transmission error (slave station)

The unusable number of occupied stations has been specified from master station.

Check the number of occupied stations setting in master station parameter (Network Configuration Settings).

Check the slave station where the error occurred.

CFE8H Cyclic transmission error (slave station)

There is no response from slave station. Check the slave station disconnection detection setting in master station parameter (Network Configuration Settings).

Check the existence status of slave station in network. Check the slave station which is disconnected. Take measures to reduce noise.

CFE9H Cyclic transmission error (slave station)

The slave station of the same IP address has existed in the same network address.

Check the slave station where the error occurred

CFF0H Slave station error The error occurred in slave station. Check the slave station where the error occurred.

0 34 ERROR CODES 34.4 List of Error Codes

35

35 EVENT LIST The CPU module collects information, such as errors detected by the module; operations performed for the module; and network errors, from modules, and stores the collected data into the data memory or an SD memory card. ( Page 177 Event History Function) When an event occurs, its event code and details can be read by using an engineering tool.

For details on events occurred in each module, refer to the manual for the module used.

35.1 How to Read the Event List The event list contains the following information.

Detailed information The following table lists the details of information displayed in the detailed information 1 to 5.

Item Description Event code ID number assigned to an event

Event type Type of an event

Event category Category of an event

Detected event Description of a detected event

Detailed information 1 to 5 Details of a detected event

Detailed information

Item Description

Detailed information 1 Operation source information Information on the operation source Connection port (such as Ethernet and USB) I/O number CPU number (a number assigned to CPU modules in a multiple CPU system) Network number Station number IP address

Event history file information Information on the event history file

Module information Information on the target module (I/O number)

Firmware update information (RnCPU) Information (firmware versions before and after update) on the firmware update using an SD memory card for the RnCPU

Firmware update information (RnENCPU (CPU part))

Information (firmware versions before and after update) on the firmware update using an SD memory card for the RnENCPU (CPU part)

Daylight saving time status Information on the daylight saving time status (start/end)

CPU module data backup/restoration information

Information on the CPU module data backup/restoration function (operation, result, error, data specification, initialization, latest data, special relay, special register, operation mode)

CPU module data backup setting information Information on the CPU module backup setting (backup function setting, error codes)

Data backup/restoration information of iQ Sensor Solution

Information on the data backup/restoration function of iQ Sensor Solution (operation, target device, execution unit, target module, folder number setting method, total number of executions, number of successful executions, number of executions completed with an error, folder number)

Information on the execution status of the data backup/restoration function of iQ Sensor Solution

Information on the execution status of the data backup/restoration function of iQ Sensor Solution (result, error category, error code)

Information on the right to use the data backup/ restoration function of iQ Sensor Solution

Information on the right to use the data backup/restoration function of iQ Sensor Solution (right-to-use number, operation)

35 EVENT LIST 35.1 How to Read the Event List 561

56

Detailed information 2 Communication speed and communication mode

Information on the communication speed and the communication mode

Communication status Information on the communication status

Security key operation information Information on the corresponding security key

Remote password information Information on the corresponding remote password

File password information Information on the corresponding file password

Blocked IP address information Information on the blocked IP address

Drive/file information Information on the corresponding drive name and file name

Drive number and file name Information on the corresponding drive number and file name

Copy source drive/file information Information on the corresponding drive name and file name

Operation target information Information on the operation target: I/O number

Clock information (before change) Clock information before change

Remote operation type information Information on the remote operation type

Device/label information Information on device/label clearing

Device/label clearing information

Device name information Information on the device name

Device name information (user-specified) Information on the device name (at index modification/indirect specification)

Label name information Information on the label name

Label name information (user-specified) Information on the label name (at index modification/indirect specification)

Program start information Information on the start of a specified program

Program stop information Information on the stop of a specified program

Target folder information of the CPU module data backup/restoration function

Information on the data backup/restoration target folder (folder specification, date, number)

Target device information of the data backup/ restoration function of iQ Sensor Solution

Information on the data backup/restoration target device (station number, station sub-ID number, ID number, IP address)

Firmware update information (RnENCPU (network part))

Information (firmware versions before and after update) on the firmware update using an SD memory card for the RnENCPU (Network part)

Firmware update information Information (firmware versions before and after update, modules whose firmware versions are updated) on the firmware update that is performed using the engineering tool

Restricted event category Category of event subject to the event history logging restriction

Detailed information 3 Clock information (after change) Clock information after change

Copy destination drive/file information Information on the corresponding drive name and file name

Number of points Information on the number of points

Written value Information on the written value

Detailed information 4 Device name information (target device) Information (device name, address) on the device actually accessed

Written value Information on the written value

Detailed information 5 Target bit No. Information on the target bit number

Device name information (target device) Information (device name, address) on the device actually accessed

Detailed information

Item Description

2 35 EVENT LIST 35.1 How to Read the Event List

35

35.2 Event List The following table lists events related to the CPU module.

Event code

Event type

Event category

Detected event

Description Detailed information

1 2 3 4 5 00100 System Info Link-up The CPU module has

entered into the link-up state as a result of an operation such as connecting a network cable between the CPU module and an external device.

Operation source information

Communication speed and communication mode

00110 Communication start/end (TCP)

Data communications with an external device through TCP connection started. Or, data communications with an external device through TCP connection ended.

Communication status

00120 FTP connection start/end

FTP connection with an external device started. Or, FTP connection with an external device ended.

00130 Receive frame error

A receive frame error was detected.

00140 SNTP server time synchronization failure

Time setting by the time synchronization function failed because there was no response from the SNTP server.

00172 Co-recording trigger sending/ receiving

As the trigger has been notified from the module compatible with co- recording function, the module has notified the trigger to other modules.

00400 Power-on/reset The CPU module has been power-on or reset.

00410 Boot operation Boot operation was performed.

00420 Event history file generation

An event history file was generated.

Event history file information

00421 Event history logging restricted

Event history logging from the module was restricted.

Module information

Restricted event category*2

00430 SFC program continue start not possible

An SFC program could not be resumed, and an initial start was performed.

00450 Daylight saving time start/end

Daylight saving time started. Or, daylight saving time ended.

Daylight saving time status

35 EVENT LIST 35.2 Event List 563

56

00800 System Warning Link-down The CPU module has entered into the link- down state as a result of an operation such as disconnecting a network cable between the CPU module and an external device.

Operation source information

Communication speed and communication mode

00904 Socket communication send error

Sending a message over socket communication failed.

00906 Alive check error

The alive status of an external device could not be checked within the period specified by the response monitoring timer.

00907 Divided message receive timeout error

All the data could not be received within the period specified by the response monitoring timer.

Data of the total data length could not be received.

The remaining part of the message divided into the TCP/IP level could not be received within the period specified by the response monitoring timer.

00908 IP composition timeout error

An IP composition timeout error occurred. (The specified period of time expired without receiving all of the divided data.)

00909 TCP-specified port number error

A port number being used for opened connection was set (for TCP/IP).

0090A UDP-specified port number error

A port number being used for opened connection was set (for UDP/IP).

1000 and after

System Error When a self-diagnostic error occurs, the error is stored as an event.

Event code

Event type

Event category

Detected event

Description Detailed information

1 2 3 4 5

4 35 EVENT LIST 35.2 Event List

35

10100 Security Info Security key registration/ deletion

A security key was registered or deleted.

Operation source information

Security key operation information

10200 Remote password lock

The remote password was set.

Remote password information10201 Remote

password unlock

The remote password unlock processing was successfully completed.

10202 Remote password unlock failed

The remote password unlock processing failed.

10300 Access from an IP address blocked by the IP filter setting

An access from an IP address blocked by the IP filer setting was accepted.

Blocked IP address information

10400 File password registration/ change/deletion

A file password was successfully registered, changed, or deleted.

Operation source information

File password information

10401 File password registration/ change/deletion failed

Registration, change, or deletion of a file password failed.

10402 File password unlock

A file password was successfully unlocked.

10403 File password unlock failed

Unlock of a file password failed.

10500 Forced invalidation setting

Forced invalidation was set.

10501 Forced invalidation cancel

Forced invalidation was canceled.

Event code

Event type

Event category

Detected event

Description Detailed information

1 2 3 4 5

35 EVENT LIST 35.2 Event List 565

56

20100 Operation Info Error clear The error was cleared. Operation source information

Operation target information

20200 Event history clear

The event history was cleared.

20210 Scan time clear The scan time was cleared.

20300 SD memory card enabled

The SD memory card was enabled.

20301 SD memory card forcibly disabled

The SD memory card forced disable function was executed and the SD memory card became ready to be removed.

20400 Firmware update successful via SD memory card (RnCPU)

RnCPU firmware update using the SD memory card was performed and completed successfully.

Firmware update information (RnCPU)

20401 Firmware update failed via SD memory card (RnCPU)

RnCPU firmware update using the SD memory card was performed and was not completed successfully.

20414 Firmware update successful via engineering tool

Firmware update using the engineering tool was performed and completed successfully.

Operation source information

Firmware update information

20415 Firmware update failed via engineering tool

Firmware update using the engineering tool was performed and was not completed successfully.

20420 Firmware update successful via SD memory card (RnENCPU)

RnENCPU firmware update using the SD memory card was performed and completed successfully.

Firmware update information (RnENCPU (CPU part))

Firmware update information (RnENCPU (network part))

20421 Firmware update failed via SD memory card (RnENCPU)

RnENCPU firmware update using the SD memory card was performed and was not completed successfully.

20500 CPU module data backup succeeded

Data in the CPU module were successfully backed up.

CPU module data backup/ restoration information

Target folder information of the CPU module data backup/ restoration function

20501 CPU module data backup failed

Backup of data in the CPU module failed.

20502 CPU module data restoration succeeded

Data were successfully restored to the CPU module.

20503 CPU module data restoration failed

Restoration of data to the CPU module failed.

20510 CPU module data backup setting disabled

Backup function cannot be set

CPU module data backup setting information

Event code

Event type

Event category

Detected event

Description Detailed information

1 2 3 4 5

6 35 EVENT LIST 35.2 Event List

35

20600 Operation Info iQ Sensor Solution data backup succeeded

Data in the target device supporting iQ Sensor Solution were successfully backed up.

Information on the execution status of the data backup/ restoration function of iQ Sensor Solution

Target device information of the data backup/ restoration function of iQ Sensor Solution

20601 iQ Sensor Solution data backup failed

Backup of data in the target device supporting iQ Sensor Solution failed.

20602 iQ Sensor Solution data restoration succeeded

Data were successfully restored to the target device supporting iQ Sensor Solution.

20603 iQ Sensor Solution data restoration failed

Restoration of data to the target device supporting iQ Sensor Solution failed.

20610 iQ Sensor Solution data backup start/ cancel/end

The data backup processing of the target device supporting iQ Sensor Solution started, canceled, or ended.

Data backup/ restoration information of iQ Sensor Solution

20611 iQ Sensor Solution data restoration start/ cancel/end

The data restoration processing of the target device supporting iQ Sensor Solution started, canceled, or ended.

20620 Right-to-use acquisition/ release

The right to use the data backup/restoration function of iQ Sensor Solution was acquired or released.

Information on the right to use the data backup/ restoration function of iQ Sensor Solution

24000 Clock setting The clock data was set. Operation source information

Clock information (before change)

Clock information (after change)

24001 Remote operation request accepted

A remote request (RUN, STOP, or PAUSE) was accepted.

Remote operation type information

24100 Operating status change (RUN)

The operating status of the CPU module was changed to RUN.

24101 Operating status change (STOP)

The operating status of the CPU module was changed to STOP.

24102 Operating status change (PAUSE)

The operating status of the CPU module was changed to PAUSE.

24120 Starting the program

The program was started.

Operation source information

Program start information

24121 Stopping the program

The program was stopped.

Program stop information

24200 Creation of new folders, writes to files/folders*1

A new folder was created.

A new file was created or data was written to a file.

Drive/file information

24201 File copy*1 A file was copied. Copy source drive/file information

Copy destination drive/file information

24202 Folder/file rename*1

A folder name or file name was changed.

Event code

Event type

Event category

Detected event

Description Detailed information

1 2 3 4 5

35 EVENT LIST 35.2 Event List 567

56

24A00 Operation Info Write Device in word units (1 point)

Data was written to the device in word units.

Operation source information

Device name information

Written value

24A01 Device name information (user-specified)

Device name information (target device)*3

24A10 Write Device in bit units (1 point)

Data was written to the device in bit units.

Device name information

24A11 Device name information (user-specified)

Device name information (target device)*3

Target bit No.*3

24A20 Write Device in double-word units (1 point)

Data was written to the device in double-word units.

Device name information

24A21 Device name information (user-specified)

Device name information (target device)*3

24A40 Write Device in word units (n points)

Data was written to the device in word units.

Device name information

Number of points

Written value

24A50 Write Device in bit units (n points)

Data was written to the device in bit units.

24B00 Write Device in word units (1 point)

Data was written to the device in word units.

Written value

24B01 Device name information (user-specified)

Device name information (target device)*3

24B10 Write Device in bit units (1 point)

Data was written to the device in bit units.

Device name information

24B11 Device name information (user-specified)

Device name information (target device)*3

Target bit No.*3

24B20 Write Device in double-word units (1 point)

Data was written to the device in double-word units.

Device name information

24B21 Device name information (user-specified)

Device name information (target device)*3

24B30 Write Device in quad-word units (1 point)

Data was written to the device in quad-word units.

Device name information

24B31 Device name information (user-specified)

Device name information (target device)*3

Event code

Event type

Event category

Detected event

Description Detailed information

1 2 3 4 5

8 35 EVENT LIST 35.2 Event List

35

24B40 Operation Info Write Device in word units (n points)

Data was written to the device in word units.

Operation source information

Device name information

Number of points

Written value

24B50 Write Device in bit units (n points)

Data was written to the device in bit units.

24B60 Write Device in double-word units (n points)

Data was written to the device in double-word units.

24B70 Write Device in quad-word units (n points)

Data was written to the device in quad-word units.

24C00 Write Label in word units (1 point)

Data was written to the label in word units.

Label name information

Written value

24C01 Label name information (user-specified)

Device name information (target device)*3

24C10 Write Label in bit units (1 point)

Data was written to the label in bit units.

Label name information

24C11 Label name information (user-specified)

Device name information (target device)*3

Target bit No.*3

24C20 Write Label in double-word units (1 point)

Data was written to the label in double-word units.

Label name information

24C21 Label name information (user-specified)

Device name information (target device)*3

24C30 Write Label in quad-word units (1 point)

Data was written to the label in quad-word units.

Label name information

24C31 Label name information (user-specified)

Device name information (target device)*3

24C40 Write Label in word units (n points)

Data was written to the label in word units.

Label name information

24C41 Label name information (user-specified)

Written value*3

Device name information (target device)*3

2A200 Memory initialization*1

The memory was initialized.

Drive/file information

2A201 Device/label zero clear

Values in a device or label were cleared to zero.

Device/label information/ Device/label clearing information

2A202 Folder/file deletion*1

A folder or file was deleted.

Drive/file information

2A205 Battery-less option cassette initialization

The battery-less option cassette was initialized.

Drive number and file name

Event code

Event type

Event category

Detected event

Description Detailed information

1 2 3 4 5

35 EVENT LIST 35.2 Event List 569

57

*1 As for file-related events such as writing and deleting a file, the following files are targeted: Program file FB program file Parameter file Data logging setting file (common setting file, individual setting file) Memory dump setting file

*2 Detailed information 2 is stored only when detailed information 1 is CPU module (3E00H). *3 The information may not be displayed depending on the target device or label.

0 35 EVENT LIST 35.2 Event List

A

APPENDICES Appendix 1 External Dimensions

CPU module R00CPU, R01CPU, R02CPU

(Unit: mm)

98 10 6

4

110

154

145

27.8

24 13

APPX Appendix 1 External Dimensions 571

57

RnCPU (except for R00CPU, R01CPU, and R02CPU)

(Unit: mm)

98 10 6

4

110

154

27.8

27

2 APPX Appendix 1 External Dimensions

A

With the Q7BATN-SET

With the Q7BAT-SET (Unit: mm)

(Unit: mm)

98 34

(1 06

)

4

4

110 27.8

27.4

98 30

(1 06

)

4

4

110 27.8

27.4

APPX Appendix 1 External Dimensions 573

57

RnENCPU

(Unit: mm)

98 10 6

4

110

152

56

26 .5

4 APPX Appendix 1 External Dimensions

A

With the Q7BATN-SET

With the Q7BAT-SET (Unit: mm)

(Unit: mm)

98 34

(1 06

)

4

4

110 56

27.40.2

98 30

(1 06

)

4

4

110 56

27.40.2

APPX Appendix 1 External Dimensions 575

576 APPX Appendix 2 Compliance with EMC and Low Voltage Directives

Appendix 2 Compliance with EMC and Low Voltage Directives

Method of ensuring compliance To ensure that Mitsubishi Electric programmable controllers maintain the EMC and Low Voltage Directives or other regulations when incorporated into other machinery or equipment, certain measures may be necessary. Please refer to one of the following manuals. MELSEC iQ-R Module Configuration Manual (SH-081262ENG) Safety Guidelines (IB-0800525) Certification marks on the side of the programmable controller indicate compliance with the relevant regulations.

Additional measures To ensure that this product maintains the EMC and Low Voltage Directives or other regulations, please refer to the following. MELSEC iQ-R Module Configuration Manual (SH-081262ENG) Safety Guidelines (IB-0800525)

A

Appendix 3 Functional Availability By CPU Module Model

The following table lists the availability of functions by CPU module model. Rn: RnCPU, RnEN: RnENCPU, RnP(P): Process CPU (process mode), RnP(R): Process CPU (redundant mode), RnPSF: SIL2 Process CPU, RnSF: Safety CPU : Supported, : Not supported

Function Availability*1

Rn RnEN RnP(P) RnP(R) RnPSF RnSF Constant scan

Device/label access service processing setting

Device/label access service processing constant wait function

Interrupt function Multiple interrupt function

Output mode setting when the status changed from STOP to RUN

Device/label memory area setting

Internal buffer capacity setting *3

SD memory card forced disable *3

Clock function

Writing data to the CPU module Writing data to the programmable controller

Online change (ladder block)

Online change (files)

RAS function Scan monitoring function

Self-diagnostics function

FB hierarchy information

Error clear

Event history function

Online module change

Program cache memory auto recovery function

Remote operation

Boot operation *3

Monitor function Circuit monitor

Device/buffer memory batch monitor

Watch

Program monitor list

Interrupt program monitor list

Real-time monitor function

Scan time measurement

Scan time clear

Specified program monitor

Test function External input/output forced on/off function

Device test with execution condition

Data logging function *3

Recording function *2

Co-recording function

Debug function Memory dump function *3

SFC function

Database function Database access instruction *2

CPU module database access (from external device) function

*2

PID control function

Process control function

CPU module data backup/restoration function *2

APPX Appendix 3 Functional Availability By CPU Module Model 577

57

*1 Some functions have restrictions on the firmware version and the production information of the CPU module used or the version of the engineering tool used. Refer to the following. Page 700 Added and Enhanced Functions

*2 The R00CPU, R01CPU, and R02CPU does not support the use of these functions. *3 The R00CPU does not support the use of these functions.

Multiple CPU system function Out-of-group I/O fetch

Multiple CPU synchronized startup

Data communications between CPU modules

Multiple CPU synchronous interrupt

Security function User authentication function

Block password function

Security key authentication function

File password function

IP filter function

Remote password function

Write-protect function for device data (from outside the CPU module)

Sequence scan synchronization sampling function

Label initialization function Label initialization after converting all programs (reassignment)

Label initialization with label initial values

Routing setting

Label access setting from external device *2

Latch function Latch with a battery

Latch with a battery-less option cassette *2

Initial device/label value setting

Redundant function Operation mode change

System switching

Tracking transfer

Memory copy from control system to standby system

System consistency check

Program execution in both systems

Redundant system operation setting

Redundant function module communication test

Setting for redundant system with redundant extension base unit

Automatic standby system recovery

Replacement/addition of an extension cable (online)

Safety operation mode

Continuous RUN prevention in TEST MODE

Safety diagnostic function

Safety data identify check

Safety communication function

Ethernet function MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

SLMP communication function

Inter-module synchronization function

CC-Link IE Field Network Basic function CC-Link IE Field Network Basic Reference Manual

iQ Sensor Solution function iQ Sensor Solution Reference Manual

Firmware update function Update using the engineering tool

Update using an SD memory card *3

Function Availability*1

Rn RnEN RnP(P) RnP(R) RnPSF RnSF

8 APPX Appendix 3 Functional Availability By CPU Module Model

A

Appendix 4 List of Special Relay Areas The following table lists items in the list.

Do not change the data set by the system in a program or by a device test. Doing so may result in system down or communication failure.

Item Description No. Special relay number

Name Special relay name

Data stored Data stored in the special relay and its meaning

Details Detailed description of the data stored

Set by (setting timing) Set side of data (system or user) and timing when data is set by the system S: System U: User (program, engineering tool, GOT, or other testing operations from external device) U/S: User and system

Every END: Data is set every time END processing is performed. Initial: Data is set when initial processing is performed (e.g. powering on the system, changing the operating status from

STOP to RUN). Status change: Data is set when the status is changed. Error: Data is set when an error occurs. Instruction execution: Data is set when an instruction is executed. Request: Data is set when requested by a user (using the special relay). Writing: Data is set when a user performs a writing operation. During END: Data is set when END processing is performed. Power-on to RUN or STOP to RUN: Data is set when the operating status changes from power-on to RUN or from

STOP to RUN.

APPX Appendix 4 List of Special Relay Areas 579

58

Diagnostic information The following is the list of special rely areas relating to the diagnostic information.

No. Name Data stored Details Set by (setting timing)

SM0 Latest self-diagnostic error (including annunciator ON)

Off: No error On: Error

This relay turns on when the self-diagnostics returns an error (including the case when an error is detected by turning the annunciator ON).

The ON state is maintained even after the error has been later cleared.

S (Error)

SM1 Latest self-diagnostic error (not including annunciator ON)

Off: No error On: Error

This relay turns on when the self-diagnostics returns an error (not including the case when an error is detected by turning the annunciator ON).

The ON state is maintained even after the error has been later cleared.

S (Error)

SM50 Error reset OffOn:Error reset request OnOff:Error reset complete

This relay clears the error state when the mode transfers from off to on.

This relay switches from on to off when the error reset has been completed.

U/S (Status change)

SM51 Battery low latch Off: Normal On: Battery low

This relay switches to on when the battery voltage of the CPU module drops below the specified value.

The ON state is maintained even after the battery voltage has been later recovered to the normal value.

This relay synchronizes with BAT LED.

S (Error)

SM52 Battery low Off: Normal On: Battery low

This relay has the same function as SM51 except for switching to off after the battery voltage has been recovered to a normal value.

S (Error)

SM53 AC/DC DOWN Off: No AC/DC DOWN detection

On: AC/DC DOWN is detected

This relay switches to on when a momentary power failure within 20ms is detected while the AC power supply module is in use. This relay can be reset when power is turned off and on.

This relay switches to on when a momentary power failure within 10ms is detected while the DC power supply module is in use. This relay can be reset when power is turned off and on.

S (Error)

SM56 Instruction execution fault Off: Normal On: Instruction execution

fault state

This relay switches to on when an error which can be classified as instruction execution fault is returned.

The ON state is maintained even after the error has been later cleared.

S (Error)

SM60 Fuse Blown Off: Normal On: Fuse blown is detected

This relay is on when at least one output module is in fuse blown state and the ON state is maintained even after later recovering to the normal state.

The fuse blown state check is also done for output modules on the remote I/O station.

S (Error)

SM61 I/O module verification error Off: Normal On: Error

This relay switches to on when the state of the I/O module is different from one registered during power-on, and the ON state is maintained even after later recovering to the normal state.

I/O module verification is also done for modules on the remote I/O station.

S (Error)

SM62 Annunciator Off: Not detected On: Detected

This relay switches to on when at least one annunciator is turned on.

This relay returns to off when all the annunciators are turned off.

S (Instruction execution)

SM80 Detailed information 1: Flag in use

Off: Not used On: In use

This relay switches to on if the detailed information n exists when SM0 switched to on.

S (Status change)

SM112 Detailed information 2: Flag in use

0 APPX Appendix 4 List of Special Relay Areas

A

*1 There are restrictions on the firmware version of the supported CPU module. ( Page 700 Added and Enhanced Functions)

SM150*1 Power-off/power supply voltage drop detection

Off: Power-on/normal power supply voltage

On: Power-off/voltage drop detected/power supply module not mounted

This relay turns on when one or more of the power supply modules whose power has been shut off or power supply voltage has dropped (not including a momentary power failure), or one or more of empty slots for the power supply module are detected on the redundant power supply base unit.

This relay turns on if causes to turn on any bits of SD150 have been occurred.

This relay turns off if causes to turn on any bits of SD150 have been removed.

In a multiple CPU system, the flags are stored only to the CPU No.1.

S (Status change)

SM151*1 Power supply module failure detection

Off: Not detected/power-off/ no power supply module

On: Detected

This relay turns on when one or more power supply module failures have been detected on the redundant power supply base unit.

This relay turns on if causes to turn on any bits of SD151 have been occurred.

This relay turns off if causes to turn on any bits of SD151 have been removed.

In a multiple CPU system, the flags are stored only to the CPU No.1.

S (Status change)

SM152*1 Momentary power failure detection (power supply module 1)

Off: Not detected On: Detected

This relay 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, this relay remains on even if the power supply recovers from the momentary power failure.

This register monitors the status of the power supply module mounted on the main base unit and counts the number of momentary power failures.

This relay turns off the flags (SM152 and SM153) of the power supply 1 and 2 when the CPU module starts up.

When one of the two power supply modules is powered off, this relay turns off the corresponding flag to one powered off.

In a multiple CPU system, the flags are stored only to the CPU No.1.

S (Status change)

SM153*1 Momentary power failure detection (power supply module 2)

S (Status change)

SM154*1 Invalid power supply module Off: Valid/power-off/no power supply module

On: Invalid

This relay turns on when one or more of invalid power supply modules have been detected on the redundant power supply base unit.

This relay turns on if a factor to turn on any bits of SD154 have been occurred.

This relay turns off if all the factors to turn on any bits of SD154 have been removed.

In a multiple CPU system, the flags are stored only to the CPU No.1.

S (Status change)

No. Name Data stored Details Set by (setting timing)

APPX Appendix 4 List of Special Relay Areas 581

58

System information The following is the list of special relay areas relating to the system information.

No. Name Data stored Details Set by (setting timing)

SM203 STOP contact Off: Other than STOP state On: STOP state

This relay is on in STOP state. S (Status change)

SM204 PAUSE contact Off: Other than PAUSE state On: PAUSE state

This relay is on in PAUSE state. Note that this relay is on during the END processing of the scan which the specified PAUSE contact turns on if PAUSE state is generated at the PAUSE contact.

S (Status change)

SM210 Clock data set request OffOn:setting request is detected OnOff:setting is completed

Clock data stored in SD210 to SD216 is written into the CPU module when this relay is switched from off to on.

This relay switches from on to off when writing of clock data stored in SD210 to SD216 into the clock element is completed.

U/S (Status change)

SM211 Clock data set error Off: No error On: Error

This relay switches to on when an error is generated in values from SD210 to SD216, and to off when no error is generated.

S (Request)

SM213 Clock data read request Off: Non-processing On: Reading request

Clock data is loaded into SD210 to SD216 when this relay is in the ON state.

U

SM217*1 Daylight saving time status flag

Off: Not during daylight saving time

On: During daylight saving time

Turns on if during daylight saving time with daylight saving time function. Turns off if not during daylight saving time.

S (Status change)

SM220 CPU No.1 preparation completed

Off: Not completed On: Completed

This relay switches to on at the time when access from the CPU module on other CPUs to the CPU module for CPU No. n is enabled during power-on or resetting.

This relay is used as an interlock to access the CPU module for the CPU No. n when the multiple CPU synchronization setting is configured to asynchronous mode.

S (Status change)

SM221 CPU No.2 preparation completed

SM222 CPU No.3 preparation completed

SM223 CPU No.4 preparation completed

SM230 No.1 CPU error flag Off: CPU No.n normal On: CPU No.n stop error state

This relay is off when the CPU module for the CPU No.n is normal (including a continuation error period).

This relay is on when the CPU module for the CPU No.n is in stop error state.

S (Status change)

SM231 No.2 CPU error flag

SM232 No.3 CPU error flag

SM233 No.4 CPU error flag

SM240 No.1 CPU reset flag Off: CPU No.n not being reset On: CPU No.n in reset mode

This relay switches to off when the CPU module of the CPU No.1 is not being reset.

This relay is on while the CPU module of the CPU No.1 is being reset (including the case when the CPU module is removed from the base unit). Other CPUs also enter into reset mode.

S (Status change)

SM241 No.2 CPU reset flag This relay switches to off when the CPU module of the CPU No.2 is not being reset.

This relay is on while the CPU module of the CPU No.2 is being reset (including the case when the CPU module is removed from the base unit). Errors occur in the other CPU modules.

S (Status change)

SM242 No.3 CPU reset flag This relay switches to off when the CPU module of the CPU No.3 is not being reset.

This relay is on while the CPU module of the CPU No.3 is being reset (including the case when the CPU module is removed from the base unit). Errors occur in the other CPU modules.

S (Status change)

SM243 No.4 CPU reset flag This relay switches to off when the CPU module of the CPU No.4 is not being reset.

This relay is on while the CPU module of the CPU No.4 is being reset (including the case when the CPU module is removed from the base unit). Errors occur in the other CPU modules.

S (Status change)

2 APPX Appendix 4 List of Special Relay Areas

A

*1 There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. ( Page 700 Added and Enhanced Functions)

*2 There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. ( Page 700 Added and Enhanced Functions) For the R00CPU, R01CPU, and R02CPU, the operation setting status is always set to "program file/FB file/global label setting file" regardless of whether this relay is on or off.

SM384*1 System operation setting request

Off: Request accepted On: Request submitted

This relay is turned from off to on to send a setting request and write/delete data to/in the setting storage area (system memory) with the value set in SD384.

Regardless of whether it was successful or not, this relay turns off when the setting request is accepted.

U/S (Status change)

SM385*1 System operation setting error

Off: No error On: Error

This relay turns on when writing into the setting storage area (system area) fails.

S (Status change)

SM386*1 Program restoration information write status LED control setting mode

Off: LED flashing On: Without LED flashing

This relay indicates the LED control setting status of program restoration information.

S (Initial)

SM387*1 Program restoration information write status

Off: All written On: Not all written

This relay indicates the write status of program restoration information in the CPU module.

This relay turns off when all program restoration information is written.

This relay turns on if there is any program whose program restoration information is not in the CPU module.

S (Status change)

SM388*2 File batch online change operation setting status

Off: Program file only On: Program file/FB file/global

label setting file

This relay indicates the operating status of the file batch online change.

S (Status change)

No. Name Data stored Details Set by (setting timing)

APPX Appendix 4 List of Special Relay Areas 583

58

SFC information The following is a list of special relay areas relating to SFC information. (There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. Page 700 Added and Enhanced Functions)

For details on the SFC program, refer to the following. MELSEC iQ-R Programming Manual (Program Design)

No. Name Data stored Details Set by (setting timing)

SM320 Presence/absence of SFC program

Off: No SFC program On: SFC program

This relay switches to on if an SFC program has been registered, and switches to off if it has not.

S (Initial)

SM321 Start/stop SFC program Off: SFC program not executed (stop)

On: SFC program executed (start)

The same value as SM320 is set for the default value. (This relay automatically turns on if there is an SFC program.)

SFC program execution is stopped if this relay switches from on to off, and execution is restarted when it switches from off to on.

If this relay switches off before SFC program processing, execution of the SFC program is not started.

S (Initial)/U

SM322 SFC program start status

Off: Initial start On: Resumption

If the SFC program start mode in the parameters is off for initial start, off is set for the default, and if resumption, on is set.

S (Initial)/U

SM323 Presence/absence of continuous transition for entire block

Off: No continuous transition

On: Continuous transition

Sets whether there is a continuous transition for blocks for which no SFC information device continuous transition bit has been set.

No continuous transition when off. Continuous transition when on. There is no effect on operation for blocks for which the continuous

transition bit has been set.

U

SM324 Continuous transition prevention flag

Off: When transition executed

On: When there is no transition

This relay switches to off during operation in modes with continuous transition, or during continuous transition, and switches to on when it is not a continuous transition.

The relay is always on during operation in modes with no continuous transition.

S (Status change)

SM325 Output mode at block stop

Off: Off On: Hold

Selects whether to retain coil output for active steps during block stoppages.

The default value when the output mode for block stoppages in the parameters is coil output off is off, and on when coil output is retained.

All coil outputs are turned off when off. Coil outputs are retained when on.

S (Initial)/U

SM326 SFC device/label clear mode

Off: Device/label clear On: Device/label retain

Select the device status (all devices and labels (including latch labels) excluding step relay (S)) when the CPU module status changes from STOP program write RUN.

This relay is valid only when an SFC program exists after program writing.

This relay is valid not only when an SFC program is written, but also when the program file and the parameter file are written.

U

SM327 Output mode at execution of the end step

Off: Hold step output off On: Hold step output

retained

When this relay switches to off, coil output is turned off for steps (SC, SE, ST) for which transition is established and that are on hold reach the END step.

When this relay switches to on, coil output is retained (step becomes inactive) for steps (SC, SE, ST) for which transition is established and that are on hold reach the END step. However, coils are turned off following forced termination.

U

SM328 Clear processing mode when the sequence reaches the end step

Off: Clear processing performed

On: Clear processing not performed

Selects whether to perform clear processing if an active step other than those retained in the block exists when the END step is reached. When this relay switches to off, all active steps are forcibly terminated, and the block is terminated. When this relay switches to on, block execution is continued as is. When the END step is reached, if no active steps other than those retained exist, all retained steps are terminated, and the block is terminated.

U

SM329 Online change (SFC block) status flag

Off: Not being executed On: Being executed

This relay turns on while the online change (SFC block) is being executed.

S (Status change)

4 APPX Appendix 4 List of Special Relay Areas

A

System clock The following is the list of special relay areas relating to the system clock.

No. Name Data stored Details Set by (setting timing)

SM400 Always On Always On S (Power-on to RUN/STOP to RUN/every END*2)

SM401 Always Off Always Off S (Power-on to RUN/STOP to RUN/every END*2)

SM402 After RUN, ON for 1 scan only

This relay is on during only one scan after RUN mode starts. This relay is enabled only for the scan execution type program.

S (Status change/ every END*2)

SM403 After RUN, OFF for 1 scan only

This relay is off during only one scan after RUN mode starts. This relay is enabled only for the scan execution type program.

S (Status change/ every END*2)

SM409 0.01 second clock This relay repeats on/off at 5ms intervals. This relay does not turn on/off per scan, but turns on/off

whenever the specified time interval is reached. The initial state when the CPU module is powered on or reset is

off.

S (Status change)

SM410 0.1 second clock This relay repeats on/off at certain intervals. This relay does not turn on/off per scan, but turns on/off

whenever the specified time interval is reached. The initial state when the CPU module is powered on or reset is

off.

S (Status change)

SM411 0.2 second clock This relay repeats on/off at certain intervals. This relay does not turn on/off per scan, but turns on/off

whenever the specified time interval is reached. The initial state when the CPU module is powered on or reset is

off.

S (Status change)

SM412 1 second clock This relay repeats on/off at certain intervals. This relay does not turn on/off per scan, but turns on/off

whenever the specified time interval is reached. The initial state when the CPU module is powered on or reset is

off.

S (Status change)

SM413 2 second clock This relay repeats on/off at certain intervals. This relay does not turn on/off per scan, but turns on/off

whenever the specified time interval is reached. The initial state when the CPU module is powered on or reset is

off.

S (Status change)

SM414 2n second clock This relay repeats on/off at regular intervals specified in SD414 (in units of seconds). (When the value in SD414 is changed, the elapsed time count that has started when the ON/OFF state of SM414 last changed continues, and the ON/OFF state changes when the new specified time is elapsed.*1)

This relay does not turn on/off per scan, but turns on/off whenever the specified time interval is reached.

The initial state when the CPU module is powered on or reset is off.

S (Status change)

SM415 2n millisecond clock This relay repeats on/off at regular intervals specified in units of milliseconds on the SD415. (When the value in SD415 is changed, the elapsed time count that has started when the ON/ OFF state of SM415 last changed continues, and the ON/OFF state changes when the new specified time is elapsed.*1)

This relay does not turn on/off per scan, but turns on/off whenever the specified time interval is reached.

The initial state when the CPU module is powered on or reset is off.

S (Status change)

ON OFF

ON OFF

ON OFF

1 scan

ON OFF

1 scan

0.005s 0.005s

0.05s 0.05s

0.1s 0.1s

0.5s 0.5s

1s 1s

n s n s

n ms n ms

APPX Appendix 4 List of Special Relay Areas 585

58

SM420 User timing clock No.0 This relay repeats on/off at specified scan intervals. The initial state when the CPU module is powered on or reset is

off. The on/off scan interval is set using the DUTY instruction. (n1:

ON scan interval, n2: OFF scan interval)

S (Every END)

SM421 User timing clock No.1

SM422 User timing clock No.2

SM423 User timing clock No.3

SM424 User timing clock No.4

SM440 On only initial I44 execution after RUN

This relay is on during the first execution of the inter-module synchronous interrupt program (I44) after RUN mode starts and off during the second execution onwards.

Note that the relay status while the DI instruction is executed is as follows: On during the first execution of the inter-module synchronous interrupt program (I44) after the DI instruction is cleared and Off during the second execution onwards. (no change after the second DI clear).

This contact is enabled only for the inter-module synchronous interrupt program.

S (Status change)

SM441 On only initial I45 execution after RUN

This relay is on during the first execution of the multiple CPU synchronous interrupt program (I45) after RUN mode starts and off during the second execution onwards.

Note that the relay status while the DI instruction is executed is as follows: On during the first execution of the multiple CPU synchronous interrupt program (I45) after the DI instruction is cleared and Off during the second execution onwards. (no change after the second DI clear).

This contact is enabled only for the multiple CPU synchronous interrupt program.

S (Status change)

SM1184 *3

System clock (SM400 to SM403) every end update setting request

Off: Request accepted OffOn: Request submitted

This relay is turned off and on when a setting request of the value stored in SD1184 (System clock (SM400 to SM403) every end update setting) is submitted.

Regardless of whether the setting is successful or not, this relay turns off when the setting request is accepted.

The setting takes effect when the CPU module is powered off and on.

U (Status change)

SM1185 *3

System clock (SM400 to SM403) every end update setting error

Off: No error On: Error

This relay turns on when writing of the setting has failed. S (Status change)

SM1186 *3

System clock (SM400 to SM403) every end update setting status

Off: Disabled On: Enabled

This relay indicates the system clock (SM400 to SM403) every end update status.

S (Initial)

No. Name Data stored Details Set by (setting timing)

n1

n2

scan

scan

ON

OFF 1 scan

ON

OFF 1 scan

6 APPX Appendix 4 List of Special Relay Areas

A

*1 The following figures show operation examples of SM414/SM415 when a value in SD414/SD415 is changed.

Ex.

When a value in SD414 is changed from 3 to 10:

Ex.

When a value in SD414 is changed from 10 to 3:

*2 To enable the setting timing of "Every END" for these special relay areas, set both SM1184 and SD1184 (System clock (SM400 to SM403) every end update setting).

*3 The CPU module with the following firmware versions supports these special relay areas. R00CPU, R01CPU, R02CPU: "24" or later CPU modules other than R00CPU, R01CPU, and R02CPU: "57" or later

(1) The elapsed time after the ON/OFF state of SM414 changes remains. (2) Value change

(1) If the new interval in SD414 has already elapsed after the last change of the ON/OFF state of SM414, the ON/OFF state changes as soon as a value in SD414 is changed.

(2) Value change

SM414

SD414

ON OFF

103

10s10s3s3s

(1)

(2)

SM414

SD414

ON OFF

10 3

6s10s 3s 3s 3s

(1)

(2)

APPX Appendix 4 List of Special Relay Areas 587

58

Fixed scan function information The following is the list of special relay areas relating to the fixed scan function information.

*1 There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. ( Page 700 Added and Enhanced Functions)

No. Name Data stored Details Set by (setting timing)

SM480 Cycle error flag for inter-module synchronous interrupt program (I44)

Off: No error for the inter-module synchronization program (Normal)

On: Error state for the inter-module synchronization program

This relay switches to on when the inter-module synchronous interrupt program (I44) has not been completed within the specified inter-module synchronization cycle or the program cannot be executed due to various reasons, such as execution of a higher-priority interrupt program and interrupt disabling by the instruction execution.

The ON state is maintained even after the program is later completed within the specified inter-module synchronization cycle (Clear by turning power off and on or resetting).

S (Status change)

SM481*1 Cycle error flag for multiple CPU synchronization interrupt program (I45)

Off: No error for the multiple CPU synchronization program (Normal)

On: Error state for the multiple CPU synchronization program

This relay switches to on when the multiple CPU synchronization program (I45) has not been completed within the specified fixed scan communication cycle or the program cannot be executed due to various reasons, such as execution of a higher-priority interrupt program and interrupt disabling by the instruction execution.

The ON state is maintained even after the program is later completed within the specified fixed scan communication cycle (Clear by turning power off and on or resetting).

S (Status change)

SM484*1 Execution section excess error flag for multiple CPU synchronization interrupt program

Off: No execution section excess error for the multiple CPU synchronization interrupt program (Normal)

On: Execution section excess error state for the multiple CPU synchronization interrupt program

This relay switches to on when the program is executed exceeding the program execution section within the specified multiple CPU synchronization cycle.

The ON state is maintained even after the program is later completed within the multiple CPU synchronous interrupt program execution section (cleared by turning power off and on or resetting).

S (Status change)

SM488 Inter-module synchronization error (out of synchronization was detected on the CPU module)

Off: No error (Normal) On: Error

This relay switches to on when the inter-module synchronization signal cannot be identified within the inter-module synchronization cycle specified in the parameter or more than one signal has been identified within the same inter-module synchronization cycle.

The ON state is maintained even after the inter-module synchronization signal can be later identified within the specified inter-module synchronization cycle (cleared by turning power off and on or resetting).

S (Status change)

SM522*1 Scan time clear request Off: Do not clear the scan time. On: Clear the scan time.

This relay clears the maximum/minimum scan time. Turning off and on this relay clears the scan time. This relay automatically turns off when the scan time has

been cleared.

U/S (Status change)

8 APPX Appendix 4 List of Special Relay Areas

A

Drive information The following is the list of special relay areas relating to the drive information.

No. Name Data stored Details Set by (setting timing)

SM600*1 Memory card usable flags

Off: Disabled On: Enabled

This relay is on when an SD memory card is enabled (This relay switches to on when a valid SD memory card is inserted and prepared for use).

S (Status change)

SM601*1 Memory card protect flag

Off: Not protected On: Protected

This relay is on when the write protect switch of the SD memory card is set to on.

S (Status change)

SM603*1 Memory card (drive 2) flag

Off: No SD memory card inserted On: SD memory card inserted

This relay is on when an SD memory card is inserted. (This relay switches to on when an SD memory card is inserted regardless of its state (enabled/disabled) and type).

S (Status change)

SM604*1 Memory card in-use flag

Off: Not used On: In use

This relay is on when the SD memory card is being used. S (Status change)

SM605*1 Memory card remove/ insert prohibit flag

Off: Allowed to remove/insert On: Not allowed to remove/insert

Turn on this relay to prohibit the SD memory card from being removed/inserted. When this relay is on, if SM607 is set to on, the system switches it to off.

U/S

SM606*1 SD memory card forced disable instruction

Off: Cancel instruction On: Forced disable instruction

This relay can be switched to on to issue the instruction that forces the SD memory card to be disabled. However, whenever any function accesses the SD memory card, the disabling process does not start until the access is completed.

This relay can be switched to off to cancel the instruction that forces the SD memory card to be disabled.

U/S (Status change)

SM607*1 SD memory card forced disable status flag

Off: Not disabled On: Disabled

This relay switches to on when the SD memory card is disabled by switching SM606 to on.

This relay switches to off when the forcibly-disabled SD memory card is enabled by switching SM606 to off.

S (Status change)

SM624*3 Battery-less option cassette insertion flag

Off: Not inserted On: Inserted

This relay is on when the battery-less option cassette is inserted.

S (Status change)

SM625*3 Battery-less function execution flag

Off: Battery-less function not executed

On: Battery-less function executed

This relay is on while the battery-less function is being executed.

S (Status change)

SM626*2 Extended SRAM cassette insertion flag

Off: Not inserted On: Inserted

This relay is on when the extended SRAM cassette is inserted.

S (Status change)

SM628 Program memory write error

Off: No write operation/normal On: Write error

This relay switches to on when a write error is detected during write operation to the program memory. This relay switches to off when the write instruction is issued.

S (Writing)

SM629 Program memory write flag

Off: No write operation On: Executing write operation

This relay is on when the write process to the program memory is in progress. The relay is switched to off when the write process is completed.

S (Writing)

SM630 Program memory overwrite count error flag

Off: The number of rewrite operations is less than 100000

On: The number of rewrite operations reaches 100000

This relay switches to on when the number of program memory rewriting operations reaches 100000 (CPU module must be replaced).

S (Writing)

SM632 Data memory write error

Off: No write operation/normal On: Write error

This relay switches to on when a write error is detected during write operation to the data memory. This relay switches to off when the write instruction is issued.

S (Writing)

SM633 Data memory write flag Off: No write operation On: Executing write operation

This relay is on when the write process to the data memory is in progress. The relay is switched to off when the write process is completed.

S (Writing)

SM634 Number of rewriting operations error to data memory flag

Off: The number of rewrite operations is less than 100000

On: The number of rewrite operations reaches 100000

This relay switches to on when the number of data memory rewriting operations reaches 100000 (CPU module must be replaced).

S (Writing)

SM652*3 Function memory clear request

OffOn:Clear request exists OnOff:Function memory cleared

The function memory of the CPU module is initialized (cleared) when this relay is turned off and on while the operating status of the CPU module is in STOP.

The system turns off this relay when the initialization (clear) of the function memory is completed (regardless of whether it was successful or not).

S (Status change)/ U

APPX Appendix 4 List of Special Relay Areas 589

59

*1 The CPU module where the SD memory card can be used supports these special relay areas. *2 The CPU module where the extended SRAM cassette can be used supports these special relay areas. *3 There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. ( Page

700 Added and Enhanced Functions)

SM653*3 File transfer to data memory request

OffOn:Transfer executed OnOff:Transfer completed

Files saved in the function memory (SDRAM) are transferred to the data memory when this relay is changed from off to on.

The system turns off this relay when the file transfer is completed (regardless of whether it was successful or not).

Note that the files in the function memory are not deleted.

S (Status change)/ U

No. Name Data stored Details Set by (setting timing)

0 APPX Appendix 4 List of Special Relay Areas

A

Instruction related The following is the list of special relay areas relating to the instruction-related items.

No. Name Data stored Details Set by (setting timing)

SM699 Dedicated instruction skip flag

Off: Instruction being executed or completed

On: Instruction not executed

This relay indicates whether the built-in Ethernet function instruction (the SP.SOCOPEN/SP.SOCCLOSE/ SP.SOCRCV/S.SOCRCVS/SP.SOCSND/SP.ECPRTCL/ SP.SLMPSND/SP.FTPPUT/SP.FTPGET instruction), intelligent function module dedicated instruction, or multiple CPU dedicated instruction has been skipped. (Checking this flag immediately after the instruction issue allows to determine whether or not the dedicated instruction is non-processing (skipped) in the internal processing.)

This relay saves/returns while the interrupt program is being executed.

S (Status change)

SM700 Carry flag Off: Carry off On: Carry on

This relay is a carry flag used while the application instruction is executing.

This relay saves/returns when the interrupt program is being executed.

S (Instruction execution)

SM701 Number of output characters selection

Off: Outputs until reaching NULL code

On: Outputs 16 characters

ASCII codes are output until reaching NULL (00H) code, when SM701 is off.

16 characters of ASCII codes are output, when SM701 is on.

This relay saves/returns when the interrupt program is being executed.

U

SM702 Search method Off: Sequential search On: Dichotomizing search

The search method in the search instruction can be specified by using this relay.

To use the dichotomizing search, data must be sorted. This relay saves/returns while the interrupt program is

being executed.

U

SM703 Data sort instruction sort order

Off: Ascending On: Descending

This relay can be used to specify how to arrange data in the data sort instruction: ascending or descending.

This relay saves/returns while the interrupt program is being executed.

U

SM704 Block comparison Off: Mismatch is detected On: Completely match

This relay switches to on when all the data conditions are met in the block data comparison instruction.

This relay saves/returns while the interrupt program is being executed.

S (Instruction execution)

SM705*1 Number of conversion digits selection

Off: Fixed number of digits On: Desired number of digits

When SM705 is off, the conversion data is specified and output with the fixed number of digits.

When SM705 is on, the conversion data is specified and output with the desired number of digits.

This relay saves/returns while the interrupt program is being executed.

U

SM709 DT/TM instruction improper data detection flag

Off: No improper data On: Improper data is detected

This relay switches to on when the comparison target data is date data or cannot be recognized as clock data, or the comparison target device (three words) exceeds the specified device range in the DT/TM instruction.

This relay saves/returns while the interrupt program is being executed.

S (Instruction execution)/U

SM752 Dedicated instruction End bit control flag

Off: Automatically controlled On: Not automatically controlled

This relay can be used to set whether the system automatically controls the on/off operation of End bit being used for the dedicated instruction and other (control of End bit which is registered in the End processing of the instruction completion and turned on for only the next one scan (Off: turned on for only one scan after the instruction is completed as well as normal/error End bit, On: turned on when the instruction is completed and the On status is maintained after that)).

U

APPX Appendix 4 List of Special Relay Areas 591

59

SM753 File being accessed Off: Not in progress On: In progress

This relay is on during file access by the SP.DEVST instruction.

This relay is on while the SP.FTPPUT/SP.FTPGET instruction is being executed.

This relay is on while a database access instruction is being executed.*1*3

This relay is on during access to the SD memory card and data memory.

This relay is on while a file operation instruction is being executed.*3

S (Status change)

SM754 BIN/DBIN instruction error control flag

Off: Executes error detection On: No execute error detection

This relay can be switched to on when the error detection is not desirable in the BIN/DBIN instruction.

U

SM755 Scaling data check settings

Off: Performs data check On: Not perform data check

This relay can be used to enable/disable the check whether the scaling data is sorted in ascending order when the SCL/DSCL/SCL2/DSCL2 instruction is being executed.

U

SM756 Module access completion wait control flag

Off: Not wait the completion On: Waits the completion

This relay can be used to determine whether the system must wait until the access is completed before starting the next instruction when the write access instruction to the buffer memory of another module is being executed.

U

SM772*2 CCD/CRC instruction conversion mode (16- bit/8-bit) selection

Off: 16-bit conversion mode On: 8-bit conversion mode

This relay can be used to select 16-bit conversion mode or 8-bit conversion mode with the CCD/CRC instruction.

U

SM773*2 SMOV instruction BCD conversion prohibit flag

Off: BCD conversion enabled On: BCD conversion disabled

This relay switches to on when disabling conversion from BIN data to BCD data with the SMOV instruction.

U

SM774*3 Data table sort instruction sort order

Off: Ascending On: Descending

This relay can be used to specify how to arrange data in the data table sort instruction: ascending or descending.

U

SM775 Selection of refresh processing during the COM instruction execution

Off: Executes all the refresh processings

On: Executes the refresh processing specified in SD775

This relay can be used to select the refresh processing target when the COM instruction is executed from two options: all refresh processing or only refresh processing specified in SD775.

U

SM776 Local device setting at CALL

Off: Disables local devices On: Enables local devices

This relay can be used to determine whether the local devices on the subroutine program called when the CALL instruction is being executed are enabled or not.

U

SM777 Local device setting in interrupt programs

Off: Disables local devices On: Enables local devices

This relay can be used to determine whether the local devices are enabled or not when the interrupt program is being executed.

U

SM792 PID bumpless processing (for the complete differentiation PIDCONT instruction)

Off: Matching On: Not matching

This relay can be used to specify whether to match SV to PV in manual mode.

U

SM794 PID bumpless processing (for the inexact differential S.PIDCONT instruction)

Off: Matching On: Not matching

This relay can be used to specify whether to match SV to PV in manual mode.

U

SM796*2 Number of used blocks information for the multiple CPU dedicated instruction (for CPU No.1)

Off: The specified number of blocks is reserved

On: The number of blocks specified in SD796 is not reserved

This relay switches to on when the number of remaining blocks in the dedicated instruction transfer area to be used in the multiple CPU dedicated instruction (target machine: CPU No.1) drops below the number of blocks specified in SD796. This relay is also on when the instruction is being executed.

This relay switches to off when there exist free blocks during the END processing.

S (Instruction execution/During END)

SM797*2 Number of used blocks information for the multiple CPU dedicated instruction (for CPU No.2)

Off: The specified number of blocks is reserved

On: The number of blocks specified in SD797 is not reserved

This relay switches to on when the number of remaining blocks in the dedicated instruction transfer area to be used in the multiple CPU dedicated instruction (target machine: CPU No.2) drops below the number of blocks specified in SD797. This relay is also on when the instruction is being executed.

This relay switches to off when there exist free blocks during the END processing.

S (Instruction execution/During END)

No. Name Data stored Details Set by (setting timing)

2 APPX Appendix 4 List of Special Relay Areas

A

*1 The programmable controller CPU with firmware version "28" or later supports these special relay areas. However, there are no restrictions on the version of the R00CPU, R01CPU, and R02CPU.

*2 There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. ( Page 700 Added and Enhanced Functions)

*3 The CPU module where this function can be used supports this special relay area.

SM798*2 Number of used blocks information for the multiple CPU dedicated instruction (for CPU No.3)

Off: The specified number of blocks is reserved

On: The number of blocks specified in SD798 is not reserved

This relay switches to on when the number of remaining blocks in the dedicated instruction transfer area to be used in the multiple CPU dedicated instruction (target machine: CPU No.3) drops below the number of blocks specified in SD798. This relay is also on when the instruction is being executed.

This relay switches to off when there exist free blocks during the END processing.

S (Instruction execution/During END)

SM799*2 Number of used blocks information for the multiple CPU dedicated instruction (for CPU No.4)

Off: The specified number of blocks is reserved

On: The number of blocks specified in SD799 is not reserved

This relay switches to on when the number of remaining blocks in the dedicated instruction transfer area to be used in the multiple CPU dedicated instruction (target machine: CPU No.4) drops below the number of blocks specified in SD799. This relay is also on when the instruction is being executed.

This relay switches to off when there exist free blocks during the END processing.

S (Instruction execution/During END)

No. Name Data stored Details Set by (setting timing)

APPX Appendix 4 List of Special Relay Areas 593

59

Latch area The following is the list of special relay areas relating to the latch area. (The CPU module where each function can be used supports these special relay areas. Page 700 Added and Enhanced Functions)

No. Name Data stored Details Set by (setting timing)

SM922 Firmware update completion with/without an error

Off: Update completed without an error (including successful completion)

On: Update completed with an error

This relay switches to on when the firmware update function (firmware update using an SD memory card) is completed with an error. (switching to on when SD922 is 0100H to 0300H)

S (Initial)

SM940 Operation setting of the device test with execution conditions

Off: Registration disabled On: Registration not disabled

Set the operation when files relevant to the device test with execution conditions are changed.

U

SM953 CPU module data backup error check flag

Off: No error On: Error

This relay turns on if an error occurs at the execution of backup of the CPU module.

This relay turns off at the start of the CPU module data backup.

S (Status change)

SM959 CPU module data restoration error check flag

Off: No error On: Error

This relay turns on if an error occurs at the execution of restoration of the CPU module.

This relay turns off at the start of restoration of the CPU module.

S (Status change)

SM960 Upper limit setting flag for the number of CPU module backup data

Off: Backup continued On: Backup stopped

This relay specifies the operation of backup when the number of backup data of the CPU module reaches the upper limit. (This relay is valid only when bit 5 of SD944 is on.) Off: After deleting the oldest date stamp folder, the

backup is continued. On: The backup is not continued if the upper limit of the

number of backup data is exceeded. (In this case, the backup is completed with an error.)

U

SM961 Automatic backup retry failure flag

Off: Retry not executed/Retry being executed

On: Retry failed

This relay turns on when the retry of the automatic backup of the CPU module is failed even after the specified number of retries are attempted. This relay turns off at the start of the automatic backup. (This relay does not turn off when SM1351 is on.)

S (Status change)

4 APPX Appendix 4 List of Special Relay Areas

A

Data logging function The following is the list of special relay areas relating to the data logging function. (The R00CPU does not support the use of these functions.)

No. Name Data stored Details Set by (setting timing)

SM1200 Auto logging setting file and registration status

Off: Mismatch On: Matching

This relay is on when the auto logging setting executed (registered) matches with the content of the configuration file stored in the target memory. This relay is off when the setting does not match with the content.

S (Status change)

SM1201 SD memory card setting file in use flag

Off: Not used On: In use

This relay switches to on when the data logging configuration file stored in an SD memory card is being used. This relay switches to on when one or more data logging of the settings No.1 to 10 is registered.

The ON state is maintained even when the data logging later enters into suspend/waiting for start without collection/waiting for RUN without collection mode. However, the relay switches to off when all the data logging stops.

S (Status change)

SM1202 Data memory setting file in use flag

Off: Not used On: In use

This relay switches to on when the data logging configuration file stored in the data memory is being used. This relay switches to on when one or more data logging of the settings No.1 to 10 is registered.

The ON state is maintained even when the data logging later enters into suspend/waiting for start without collection/waiting for RUN without collection mode. However, the relay switches to off when all the data logging stops.

S (Status change)

SM1203 Data logging file transfer stop request

OffOn:Stop request exists OnOff:Transfer stopped

This relay stops the data logging file transfer according to the value specified in SD1203 when this relay is changed from off to on.

This relay turns off when the data logging file transfer is stopped.

U/S (Status change)

SM1210 Data logging setting No.1 Data logging preparation

Off: Not prepared On: Prepared

This relay switches to on when the data logging preparation is completed.

The ON state is maintained even when the data logging later enters into suspend/waiting for start without collection/waiting for RUN without collection mode. This relay switches to off when the data logging stops.

S (Initial)

SM1211 Data logging setting No.1 Data logging start

Off: Suspended/waiting for start On: Start

This relay switches to on when the data logging starts. The relay turns off when the data logging is in suspend/ waiting for start without collection mode. Associated special relay, such as Data logging collection, Data logging end, Data logging trigger, and After data logging trigger, switches to off simultaneously.

This relay also switches to off when the CPU module is moved from RUN to STOP mode and therefore the data collection is halted.

S (Status change)

SM1212 Data logging setting No.1 Data logging collection

Off: Not in progress On: In progress

This relay switches to on when the data logging starts data collection.

S (Status change)

SM1213 Data logging setting No.1 Data logging end

Off: Not completed On: Completed

This relay switches to on when the data logging is completed. For continuous logging, the corresponding bit switches to on when writing reaches the maximum number of storage files and data logging is completed (with "Stop" set for the operation at the time when the number of save files exceeds the limit). For trigger logging, the corresponding bit switches to on when data collection for the specified number of records has been completed followed by writing into the SD memory card after the trigger condition was satisfied. The bit also switches to on when an error is generated (except for data logging error caused by online program change) during the data logging execution.

S (Status change)

SM1214 Data logging setting No.1 Data logging trigger

OffOn:Triggered The system switches this relay to on when the specified trigger condition is satisfied.

S (Status change)

APPX Appendix 4 List of Special Relay Areas 595

59

SM1215 Data logging setting No.1 After data logging trigger

Off: Not post triggering On: Post triggering

This relay switches to on once data logging triggering occurs. The ON state is maintained even when the data logging is completed. However, this relay is off when the data logging is in suspend/waiting for start without collection/stop mode

This relay also switches to off when the CPU module is moved from RUN to STOP mode and therefore the data collection is halted.

S (Status change)

SM1216 Data logging setting No.1 Data logging error

Off: No error On: Error

This relay switches to on when a data logging function error is generated.

This relay switches to off when the setting is registered or by the stop command from CPU Module Logging Configuration Tool.

S (Status change)

SM1217 Data logging setting No.1 Data logging data saving in progress

Off: Not in progress On: In progress

This relay turns on when data in the internal buffer is being saved in the SD memory card or function memory with the data logging.

S (Status change)

SM1218 Data logging setting No.1 Logging data storage file switching in progress

Off: Not in progress On: In progress

This relay switches to on when storage file switching is in progress.

S (Status change)

SM1219 Data logging setting No.1 Data logging file transfer execution status flag

Off: Not executed On: Being executed

This relay turns on at the start of the data logging file transfer function or transferring of data logging files to the data memory.

This relay turns off at the completion of the data logging file transfer function or transferring of data logging transfer files to the data memory.

S (Status change)

SM1220 to SM1229

Data logging setting No.2 Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SM1210 to SM1219).

Same configuration as the setting No.1

SM1230 to SM1239

Data logging setting No.3 Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SM1210 to SM1219).

Same configuration as the setting No.1

SM1240 to SM1249

Data logging setting No.4 Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SM1210 to SM1219).

Same configuration as the setting No.1

SM1250 to SM1259

Data logging setting No.5 Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SM1210 to SM1219).

Same configuration as the setting No.1

SM1260 to SM1269

Data logging setting No.6 Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SM1210 to SM1219).

Same configuration as the setting No.1

SM1270 to SM1279

Data logging setting No.7 Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SM1210 to SM1219).

Same configuration as the setting No.1

SM1280 to SM1289

Data logging setting No.8 Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SM1210 to SM1219).

Same configuration as the setting No.1

SM1290 to SM1299

Data logging setting No.9 Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SM1210 to SM1219).

Same configuration as the setting No.1

SM1300 to SM1309

Data logging setting No.10

Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SM1210 to SM1219).

Same configuration as the setting No.1

SM1312 to SM1321

Data logging setting No.1 to 10 Data logging suspend/ resume flag

OffOn:Suspend OnOff:Resume

When this relay changes from off to on, the data logging function is suspended. In an off state of the data logging start SM, no processing is performed.

When this relay changes from on to off, the data logging function resumes. In an ON state of the data logging start SM, no processing is performed.

U

No. Name Data stored Details Set by (setting timing)

6 APPX Appendix 4 List of Special Relay Areas

A

CPU module data backup/restoration function The following is the list of special relay areas relating to the CPU module data backup/restoration function. (The R00CPU, R01CPU, and R02CPU do not support the use of these functions.)

iQ Sensor Solution data backup/restoration function The following is the list of special relay areas relating to the iQ Sensor Solution data backup/restoration function. (The R00CPU does not support the use of these functions.)

No. Name Data stored Details Set by (setting timing)

SM1350 CPU module data backup status flag

Off: Not being executed On: Being executed

This relay turns on during the backup of the CPU module. S (Status change)

SM1351 CPU module data backup execution request

OffOn:Backup requested OnOff:Backup completed

At the timing when this relay turns from off to on, the backup of the CPU module is executed.

This relay turns off at the completion of the backup of the CPU module.

S (Status change)/ U

SM1353 CPU module data restoration status flag

Off: Not being executed On: Being executed

This relay turns on during the restoration of the CPU module.

S (Status change)

SM1354 CPU module data restoration execution request

OffOn:Restoration requested OnOff:Restoration completed

At the timing when this relay turns from off to on during STOP, the restoration of the CPU module is executed.

This relay turns off at the completion of the restoration of the CPU module.

S (Status change)/ U

SM1356 Retry status flag for CPU module data automatic backup

Off: Not being executed On: Being executed

This relay turns on during the retry of the automatic backup of the CPU module.

S (Status change)

No. Name Data stored Details Set by (setting timing)

SM1360 Right-to-use request for iQ Sensor Solution data backup

OffOn: Right to use requested OnOff: Right to use acquired/

released

This relay requests acquiring or releasing the right to use of the data backup/restoration of iQ Sensor Solution.

At the timing when this relay turns from off to on, the relay requests the right to use with the value specified in SD1360.

This relay turns off when the right to use has been acquired or released.

S (Status change)/ U

SM1361 iQ Sensor Solution backup request

OffOn: Backup requested OnOff: Backup completed

This relay requests the data backup of iQ Sensor Solution. At the timing when this relay turns from off to on, the

backup of the set device(s) is executed. This relay turns off at the completion of the data backup of

iQ Sensor Solution. This relay turns from on to off when the right to use is

acquired.

S (Status change)/ U

SM1362 iQ Sensor Solution backup normal completion

Off: Other than normal completion

On: Completed normally

This relay turns on when the iQ Sensor Solution data backup is completed normally.

When the iQ Sensor Solution data backup is completed with an error, SM1363 turns on and this relay remains off.

This relay turns from on to off when the right to use is acquired or the backup is requested.

S (Status change)

SM1363 iQ Sensor Solution backup error completion

Off: Other than error completion

On: Completed with an error

This relay turns on when the iQ Sensor Solution data backup is competed with an error. The error code is stored into SD1376 or SD1377.

When the iQ Sensor Solution data backup is competed normally, SM1362 turns on and this relay remains off.

This relay turns from on to off when the right to use is acquired or the backup is requested.

S (Status change)

SM1364 iQ Sensor Solution restoration request

OffOn: Restoration requested OnOff: Restoration completed

This relay requests the iQ Sensor Solution data restoration.

At the timing when this relay turns from off to on, the restoration of the set device(s) is executed.

This relay turns off at the completion of the iQ Sensor Solution data restoration.

This relay turns from on to off when the right to use is acquired.

S (Status change)/ U

APPX Appendix 4 List of Special Relay Areas 597

59

File transfer function (FTP client) The following is the list of special relay areas relating to the file transfer function (FTP client). (The CPU module where this function can be used supports these special relay areas. MELSEC iQ-R Ethernet User's Manual (Application))

Global label assignment information The following is the list of special relay areas relating to global label assignment information. (The R00CPU, R01CPU, and R02CPU do not support the use of these functions.)

Memory dump function The following is the list of special relay areas relating to the memory dump function. (The R00CPU does not support the use of these functions.)

SM1365 iQ Sensor Solution restoration normal completion

Off: Other than normal completion

On: Completed normally

This relay turns on when the iQ Sensor Solution data restoration is completed normally.

When the iQ Sensor Solution data restoration is completed with an error, SM1366 turns on and this relay remains off.

This relay turns from on to off when the right to use is acquired or the restoration is requested.

S (Status change)

SM1366 iQ Sensor Solution restoration error completion

Off: Other than error completion

On: Completed with an error

This relay turns on when the iQ Sensor Solution data restoration is completed with an error. The error code is stored into SD1376 or SD1377.

When the iQ Sensor Solution data restoration is completed normally, SM1365 turns on and this relay remains off.

This relay turns from on to off when the right to use is acquired or the restoration is requested.

S (Status change)

SM1367 iQ Sensor Solution backup/restoration suspend request

OffOn: Suspension requested OnOff: Suspension

completed

This relay requests the suspension of the iQ Sensor Solution data backup/restoration.

At the timing when this relay turns from off to on, the iQ Sensor Solution data backup/restoration is suspended.

This relay turns off at the suspension completion of the iQ Sensor Solution data backup/restoration.

This relay turns from on to off when the right to use is acquired or the backup/restoration is requested.

S (Status change)/ U

No. Name Data stored Details Set by (setting timing)

SM1392 FTP client connection status

Off: Not connected (disconnected)

On: Connected

This relay turns on when the connection with the FTP server is established. This relay turns off when the connection with the FTP server is cut off.

S (Status change, END processing)

No. Name Data stored Details Set by (setting timing)

SM1398 Operation setting during global label assignment information update

Off: Response available during update

On: Response unavailable during update

This relay configures the operation setting while global label assignment information is being updated.

U

No. Name Data stored Details Set by (setting timing)

SM1472 Memory dump in progress Off: Memory dump not executed

On: Memory dump in progress

Turns on if memory dump is in progress, and turns off if memory dump is not executed.

S (Status change)

SM1473 Memory dump completed Off: Not completed On: Completed

Turns on at the time when collection of the data and save to the SD memory card are completed after the establishment of the trigger condition. Thereafter, the ON state remains even if memory dump is executed again. If the trigger condition is established again, On changes to Off.

S (Status change)

No. Name Data stored Details Set by (setting timing)

8 APPX Appendix 4 List of Special Relay Areas

A

Event history function The following is the list of special relay areas relating to the event history function. (The CPU module where this function can be used supports these special relay areas. Page 182 Event history logging restriction)

CPU module database access function The following is the list of special relay areas relating to the CPU module database access function. (The R00CPU, R01CPU, and R02CPU do not support the use of these functions.)

No. Name Data stored Details Set by (setting timing)

SM1464 Event history logging restriction status

Off: Not restricted On: Restricted

Turns on when the event history logging has been restricted. The relay remains on even after the restriction is lifted. Restricted modules can be identified in SD1464 to SD1467. SM1466 turns on when the event history logging of the CPU module is restricted and the event category is error (minor error), and SM1467 is turned on when the event history logging of the CPU module is restricted and the event category is information or warning.

S (Status change)

SM1466 Event history logging restriction status of CPU module (minor error)

Off: Not restricted On: Restricted

Turns on when CPU module event history logging whose event category is error (minor error) was restricted. The relay remains on even after the restriction is lifted.

S (Status change)

SM1467 Event history logging restriction status of CPU module (information, warning)

Off: Not restricted On: Restricted

Turns on when CPU module event history logging whose event category is information or warning was restricted. The relay remains on even after the restriction is lifted.

S (Status change)

No. Name Data stored Details Set by (setting timing)

SM1497 Memory card free space flag for CPU module database

Off: 20MB or more free space On: Less than 20MB free

space

Turns on when the free space of the SD memory card storing the CPU module database is 20MB or less.

S (Status change)

SM1498 CPU module database start-up flag

Off: Before start-up On: After start-up

Turns on only when the CPU module database access function is enabled by the module parameter setting and the database can be accessed.

S (Status change)

SM1499 CPU module database start-up failure

Off: Not failed On: Failed

Turns on only when the CPU module database access function is enabled by the module parameter setting but the database start-up is failed.

S (Status change)

APPX Appendix 4 List of Special Relay Areas 599

60

Ethernet function The following is the list of special relay areas relating to the Ethernet function.

*1 This is the memory used by the system when the CPU module is executing functions. *2 Ethernet function initial processing involves updating parameters set for data communication to Ethernet-equipped modules to enable

communication with external devices. Initial processing of Ethernet-equipped modules is performed by setting Ethernet parameters, writing them to the CPU module, and then powering off and on or resetting the CPU module. Note that if Ethernet parameters are not set, initial processing of Ethernet-equipped modules will be performed based on default parameters. (SM1524 (initial processing successful completion status) turns on the moment initial processing is complete, and communication with external devices becomes possible.)

*3 The CPU module where this function can be used supports this special register area. ( MELSEC iQ-R Ethernet User's Manual (Application))

No. Name Data stored Details Set by (setting timing)

SM1512 *3

FTP server function file path name switching setting Enable

Off: Disabled On: Enabled

When this relay is changed from off to on, the directory delimiter in a file path name of the CPU module is switched from "\" to "/". The drive number of the file path name can be omitted depending on the stored value in SD1512 when the relay is turned off and on. This setting is enabled while this relay is on.

When the directory delimiter is changed from "\" to "/", the CPU module can receive a command with "\" as the directory delimiter, however, the CPU module sends only a command with "/" as the directory delimiter.

This relay is on when the setting is enabled by executing the FTP command (quote path- delimiter).

Do not turn on and off/off and on this relay during operation. Doing so may cause malfunction.

S (Status change)/U

SM1513 *3

FTP server function file path name switching setting error

Off: No error On: Error

This relay is turned on when FTP server function file path name switching setting is failed to enable and the relay is turned off when the setting is enabled. The error cause is stored in SD1513.

This relay is turned off when SM1512 is changed from on to off, the setting is enabled by executing the FTP command (quote path-delimiter), or the setting is turned off (SM1512 is off).

S (Status change)

SM1520 IP address storage area write request

OffOn:Write request exists OnOff:Writing completed

When this relay is changed from off to on, IP address settings stored in SD1518 to SD1525 are written to the IP address storage area (system memory*1) of the CPU module.

Once write to the IP address storage area (system memory*1) is completed (regardless of whether it was successful or not), this relay is turned off.

S (Status change)/U

SM1521 IP address storage area write error

Off: No error On: Error

This relay is turned to on when write to the IP address storage area (system memory*1) failed, and off when it was successful.

S (Status change)

SM1522 IP address storage area clear request

OffOn:Clear request exists OnOff:Storage area

cleared

When this relay is changed from off to on, the IP address storage area (system memory*1) is cleared. Once clear of the IP address storage area (system memory*1) is completed (regardless of whether it was successful or not), this relay is turned off.

S (Status change)/U

SM1523 IP address storage area clear error

Off: No error On: Error

This relay is turned to on when clear of the IP address storage area (system memory*1) failed, and off when it was successful.

S (Status change)

SM1524 Initial processing successful completion state

Off: Completed with an error

On: Completed normally

This relay is turned on when the initial processing for the Ethernet function was completed successfully.*2 When the initial processing was completed with an error, SM1525 is turned on and SM1524 stays off.

S (Status change)

SM1525 Initial processing error completion state

Off: Completed normally On: Completed with an

error

This relay is turned on when the initial processing for the Ethernet function was completed with an error.*2 When the initial processing was completed successfully, SM1524 is turned on and SM1525 stays off.

S (Status change)

0 APPX Appendix 4 List of Special Relay Areas

A

CC-Link IE Field Network Basic function The following is the list of special relay areas relating to the CC-Link IE Field Network Basic function. (The CPU module where this function can be used supports these special relay areas. Page 700 Added and Enhanced Functions)

No. Name Data stored Details Set by (setting timing)

SM1536 Cyclic transmission status Off: Not performed On: Being performed

This relay turns on when the cyclic transmission starts.

This relay is turned off when the cyclic transmission stops.

S (Every END)

SM1540 Data link status Off: All stations normal On: One or more faulty

stations

This relay turns on when an error exists even in one slave station.

The status of each slave station can be checked in SD1540 to SD1543.

S (Every END)

APPX Appendix 4 List of Special Relay Areas 601

60

Appendix 5 List of Special Register Areas The following table lists items in the list.

Do not change the data set by the system in a program or by a device test. Doing so may result in system down or communication failure.

Item Description No. Special register number

Name Special register name

Data stored Data stored in the special register

Details Detailed description of the data stored

Set by (setting timing) Set side of data (system or user) and timing when data is set by the system S: System U: User (program, engineering tool, GOT, or other testing operations from external device) U/S: User and system

Every END: Data is set every time END processing is performed. Initial: Data is set when initial processing is performed (e.g. powering on the system, changing the operating status from

STOP to RUN). Status change: Data is set when the status is changed. Error: Data is set when an error occurs. Instruction execution: Data is set when an instruction is executed. Request: Data is set when requested by a user (using the special relay). Switch change: Data is set when the switch of the CPU module is changed. Card insertion/removal: Data is set when an SD memory card is inserted or removed. Writing: Data is set when a user performs a writing operation. During END: Data is set when END processing is performed.

2 APPX Appendix 5 List of Special Register Areas

A

Diagnostic information The following is the list of special register areas relating to the diagnostic information.

No. Name Data stored Details Set by (setting timing)

SD0 Latest self diagnostics error code

Latest self diagnostics error code

Error codes are stored in a hexadecimal value when the diagnostics detects an error.

S (Error)

SD1 Latest self-diagnostics error time

Latest self-diagnostics error time

The year value (four digits) of the date/time when SD0 data was updated is stored as a BIN code.

S (Error)

SD2 The month value of the date/time when SD0 data was updated is stored as a BIN code.

SD3 The day value of the date/time when SD0 data was updated is stored as a BIN code.

SD4 The hour value of the date/time when SD0 data was updated is stored as a BIN code.

SD5 The minute value of the date/time when SD0 data was updated is stored as a BIN code.

SD6 The second value of the date/time when SD0 data was updated is stored as a BIN code.

SD7 The day of the week value of the date/time when SD0 data was updated is stored as a BIN code. (0: Sun, 1: Mon, 2: Tue, 3: Wed, 4: Thu, 5: Fri, 6: Sat)

SD10 Self-diagnostic error number

Self-diagnostic error number 1 The maximum of 16 types of error codes are stored into SD10 onwards when the diagnostics detects an error (The same error code as one already stored in SD10 onwards is not stored). The 17th error code onwards are not stored. Also error codes are not stored when 16 types of error codes have already been stored into SD10 to SD25.

S (Error)

SD11 Self-diagnostic error number 2

SD12 Self-diagnostic error number 3

SD13 Self-diagnostic error number 4

SD14 Self-diagnostic error number 5

SD15 Self-diagnostic error number 6

SD16 Self-diagnostic error number 7

SD17 Self-diagnostic error number 8

SD18 Self-diagnostic error number 9

SD19 Self-diagnostic error number 10

SD20 Self-diagnostic error number 11

SD21 Self-diagnostic error number 12

SD22 Self-diagnostic error number 13

SD23 Self-diagnostic error number 14

SD24 Self-diagnostic error number 15

SD25 Self-diagnostic error number 16

SD49*1 Error detection invalidation setting

Error detection invalidation setting

Specify a function for which detection of continuation errors is invalidated. (On: Invalidate (do not detect an error), Off: Do not invalidate (detect an error))

b0: Built-in Ethernet port communication error

U

SD53 AC/DC DOWN The number of AC/DC DOWN detections

The value of this register increments by one and stored as a BIN code, each time input voltage drops to 85% (AC power)/65% (DC power) or less of the nominal value while the CPU module is carrying out an operation. A counting cycle from 0 to 65535 to 0 is repeated.

S (Error)

SD60 Number of module with blown fuse

Number of module with blown fuse

The lowest number of module in which a fuse blew is stored. The fuse blown state check is also done for output modules on the

remote I/O station.

S (Error)

SD61 I/O module verify error module number

I/O module verify error module number

The lowest I/O number of the module which has an error detected by the I/O module verification is stored.

I/O module verification is also done for modules on the remote I/O station.

S (Error)

SD62 Annunciator number Annunciator number The annunciator number which is detected first is stored. S (Instruction execution)

b0

APPX Appendix 5 List of Special Register Areas 603

60

SD63 Number of annunciators Number of annunciators The number of detected annunciator is stored. S (Instruction execution)

SD64 to SD79

Table of detected annunciator numbers

Detected annunciator number Numbers of activated annunciators are sequentially registered into SD64 to SD79, each time an annunciator (F) is turned on by the SET F instruction.

Number of the annunciator deactivated by the RST F instruction is removed from register areas SD64 to SD79, and the numbers of annunciators which were lined up behind the removed one move forward one by one. When the number of detected annunciators has already reached 16, the number of a newly detected annunciator is not stored into SD64 to SD79.

For details on the annunciator, refer to the annunciator (F) ( Page 417 Annunciator (F))

S (Instruction execution)

SD80 Detailed information 1 information category

Detailed information 1 information category code

Detailed information 1 information category code is stored.

b0 to b7: Information category code b8 to b15: Unused (fixed to 0) The following codes are stored into the information category code.

0: N/A 1: program position information 2: drive number and file name 4: Parameter information 5: System configuration information 6: number of times information 7: time information 24: Failure information 46: CPU module data backup/restoration folder information

S (Error)

SD81 to SD111

Detailed information 1 Detailed information 1 Detailed information 1 corresponding to the error code (SD0) is stored. The type of the detailed information 1 can be obtained using SD80

(The value of the "Detailed information 1 information category code" stored in SD80 corresponds to the following (1), (2), (4) to (7), and (24).)

(1) Error location information SD81: With or without specification

b0: Argument number b1: SFC block number b2: SFC step number b3: SFC transition number b4: Sequence step number b5: FB number b6: File name SD82: Argument number (stored in the range from 1) SD83: SFC block number SD84 to SD85: SFC step number SD86 to SD87: SFC transition number SD88 to SD89: Step number SD90: FB number SD91 to SD98: File name (first eight characters of Unicode string) (2) Drive number and file name SD81: With or without specification

b0: Drive number b1: File name SD82: Drive number SD83 to SD90: File name (first eight characters of Unicode string)

S (Error)

No. Name Data stored Details Set by (setting timing)

b15 b7b8 b0

b1b2b3b4b5b6 b0

b1 b0

4 APPX Appendix 5 List of Special Register Areas

A

SD81 to SD111

Detailed information 1 Detailed information 1 (4) Parameter information SD81: With or without specification

b0: Parameter type b1: Parameter storage location b2: I/O number b3: Parameter number b4: Network number b5: Station number b6: System information SD82

b0 to b7: Parameter type (stored in the following value) 1: System parameter 2: CPU parameter 3: Module parameter 4: Module extension parameter 5: Memory card parameter b8 to b15: Parameter storage location (2: SD memory card, 4: Data

memory) SD83: I/O number 0xFFFF is stored when no I/O number is assigned. SD84: Parameter number SD85: Network number SD86: Station number 0 to 120 (0 is stored for the master station.) SD87 to SD97: System information

S (Error)

No. Name Data stored Details Set by (setting timing)

b1b2b3b4b5b6 b0

b15 b7b8 b0

APPX Appendix 5 List of Special Register Areas 605

60

SD81 to SD111

Detailed information 1 Detailed information 1 (5) System configuration information SD81: With or without specification

b0: I/O number b1: Slot number b2: Base number b3: Power supply number b4: CPU number b5: Network number b6: Station number SD82: I/O number SD83

b0 to b7: Slot number (0 to 11) b8 to b15: Base number (0: Main base unit, 1 to 7: Extension base unit

level 1 to level 7, 8: Higher than level 7) SD84

b0 to b7: Power supply number (1 to 2: Power supply 1 to 2) b8 to b15: CPU number: (1 to 4: CPU 1 to 4)

SD85: Network number SD86: Station number 0 to 120 (0 is stored for the master station.) (6) Number of times information When there is no specification, 0 is set to each SD. SD81: With or without specification

b0: Number of times (set value) b1: Number of times (actual measurement value) SD82 to SD83: Number of times (set value) When the number of times (set value) is not specified, 0 is set to each SD. SD82: Lower word of the number of times (set value) SD83: Upper word of the number of times (set value)

SD84 to SD85: Number of times (actual measurement value) When the number of times (actual measurement value) is not specified, 0 is set to each SD. SD84: Lower word of the number of times (actual measurement value) SD85: Upper word of the number of times (actual measurement value)

(7) Time information When there is no specification, 0 is set to each SD. SD81: With or without specification

b0: Time (value set) (ms) b1: Time (value set) (s) b2: Time (actual measurement value) (ms) b3: Time (actual measurement value) (s) SD82: Time (value set) (ms) SD83: Time (value set) (s) SD84: Time (actual measurement value) (ms) SD85: Time (actual measurement value) (s) (24) Failure information Failure information is system information.

S (Error)

No. Name Data stored Details Set by (setting timing)

b1b2b3b4b5b6 b0

b15 b7b8 b0

b15 b7b8 b0

b1 b0

b1b0b2b3

6 APPX Appendix 5 List of Special Register Areas

A

SD81 to SD111

Detailed information 1 Detailed information 1 (46) CPU module data backup/restoration folder information SD81: With or without specification

b0: Folder specification b1: Date folder b2: Number folder SD82: Folder specification 0: Specification allowed 1: Specification not allowed SD83 to SD84: Date folder (yyyymmdd) Date of the folder is stored in BCD code. (yyyy: 0 to 9999, mm: 1 to 12, dd: 1 to 31) FFFFFFFFH is stored when a folder cannot be specified. SD83: Lower word of the date folder (yyyymmdd) SD84: Upper word of the date folder (yyyymmdd)

SD85: Number folder 0 to 32767 (FFFFH is stored when a folder cannot be specified.)

S (Error)

SD112 Detailed information 2 information category

Detailed information 2 information category code

Detailed information 2 information category code is stored.

b0 to b7: Information category code b8 to b15: Unused (fixed to 0)

The following codes are stored into the information category code. 0: N/A 2: Drive number and file name 3: Annunciator number 4: Parameter information 5: System configuration information

S (Error)

SD113 to SD143

Detailed information 2 Detailed information 2 Detailed information 2 corresponding to the error code (SD0) is stored. The type of information can be checked in SD112. (The value of the

"Detailed information 2 information category code" stored in SD112 corresponds to the following (2) to (5).)

(2) Drive number and file name SD113: With or without specification

b0: Drive number b1: File name SD114: Drive number SD115 to SD122: File name (first eight characters of Unicode string) (3) Annunciator number SD113: With or without specification

b0: Annunciator number SD114: Annunciator number (4) Parameter information SD113: With or without specification

b0: Parameter type b1: Parameter storage location b2: I/O number b3: Parameter number b4: Network number b5: Station number b6: System information

S (Error)

No. Name Data stored Details Set by (setting timing)

b1b2 b0

b15 b7b8 b0

b1 b0

b0

b1b2b3b4b5b6 b0

APPX Appendix 5 List of Special Register Areas 607

60

SD113 to SD143

Detailed information 2 Detailed information 2 SD114

b0 to b7: Parameter type (stored in the following value) 1: System parameter 2: CPU parameter 3: Module parameter 4: Module extension parameter 5: Memory card parameter b8 to b15: Parameter storage location (2: SD memory card, 4: Data

memory) SD115: I/O number FFFFH is stored when no I/O number is assigned. SD116: Parameter number SD117: Network number SD118: Station number 0 to 120 (0 is stored for the master station.) SD119 to SD129: System information (5) System configuration information SD113: With or without specification

b0: I/O number b1: Slot number b2: Base number b3: Power supply number b4: CPU number b5: Network number b6: Station number SD114: I/O number SD115

b0 to b7: Slot number (0 to 11) b8 to b15: Base number (0: Main base unit, 1 to 7: Extension base unit

level 1 to level 7, 8: Higher than level 7) SD116

b0 to b7: Power supply number (1 to 2: Power supply 1 to 2) b8 to b15: CPU number: (1 to 4: CPU 1 to 4)

SD117: Network number SD118: Station number 0 to 120 (0 is stored for the master station.)

S (Error)

SD150 *1

Power-off/power supply voltage drop detection status

Power-off/power supply voltage drop detection status (bit pattern) 0: Power-on/normal voltage 1: Power-off/voltage drop

detected/no power supply module

For the redundant power supply base unit, power supply module status (power is shut off, power supply voltage drop (not including a momentary power failure) is detected, or an empty slot for the power- supply module exists) is stored using the following bit pattern.

In a multiple CPU system, the status is stored only to the CPU module No.1.

(1) Powered-off/power supply voltage dropped (power supply module 1) b0:Main base unit b1 to b7: 1st to 7th level of the extension base unit (2) Powered-off/power supply voltage dropped (power supply module 2) b8: Main base unit b9 to b15: 1st to 7th level of the extension base unit

S (Status change)

No. Name Data stored Details Set by (setting timing)

b15 b8 b7 b0

b1b2b3b4b5b6 b0

b15 b8 b7 b0

b15 b8 b7 b0

b0b15

(2) (1)

b7 b1 b2 b8 b9

8 APPX Appendix 5 List of Special Register Areas

A

*1 There are restrictions on the firmware version of the supported CPU module. ( Page 700 Added and Enhanced Functions)

SD151 *1

Power supply failure detection status

Power supply failure detection status (bit pattern) 0: Not detected/power-off/no

power supply module 1: Detected

For the redundant power supply base unit, failure detection status of the power supply module is stored using the following bit pattern.

Bits corresponding to power-off or empty slots for the power supply module turn off.

In a multiple CPU system, the status is stored only to the CPU module No.1.

(1) Failure detection status of the power supply module 1 b0:Main base unit b1 to b7: 1st to 7th level of the extension base unit (2) Failure detection status of the power supply module 2 b8: Main base unit b9 to b15: 1st to 7th level of the extension base unit

S (Status change)

SD152 *1

Momentary power failure detection count (power supply module 1)

Momentary power failure detection count for power supply module 1

This register counts the number of momentary power failures. This register monitors the status of the power supply module mounted

on the main base unit and counts the number of momentary power failures.

When the CPU module starts up, the counters of the both power supplies are cleared to 0.

When one of the two power supply is powered off, the corresponding counter to the one powered off is cleared to 0.

The counter is incremented by one upon one momentary power failure on each power supply. A counting cycle from 0 to 65535 to 0 is repeated.

In a multiple CPU system, the status is stored only to the CPU module No.1.

S (Status change)

SD153 *1

Momentary power failure detection count (power supply module 2)

Momentary power failure detection count for power supply module 2

S (Status change)

SD154 *1

Details of the invalid power supply module

Details of the invalid power supply module (bit pattern) 0: Valid/power-off/no power

supply module 1: Invalid

For the redundant power supply base unit, when an invalid power supply module exists, the status is stored using the following bit pattern.

Bits corresponding to power-off or empty slots for the power supply module turn off.

In a multiple CPU system, the status is stored only to the CPU module No.1.

(1) Details of the invalid power supply module 1 b0:Main base unit b1 to b7: 1st to 7th level of the extension base unit (2) Details of the invalid power supply module 2 b8: Main base unit b9 to b15: 1st to 7th level of the extension base unit

S (Status change)

No. Name Data stored Details Set by (setting timing)

b0b15

(2) (1)

b7 b1 b2 b8 b9

b0b15

(2) (1)

b7 b1 b2 b8 b9

APPX Appendix 5 List of Special Register Areas 609

61

System information The following is the list of special register areas relating to the system information.

No. Name Data stored Details Set by (setting timing)

SD160*1 Firmware version Firmware version The firmware version is stored. S (Initial)

SD164 to SD171*3

Production information Production information This register stores the production information.

Example: The production information is 123456789ABCDEFG.

S (Initial)

SD200 Status of switch Status of CPU switch The switch status of the CPU module is stored as follows: 0: RUN, 1: STOP

S (Switch change)

SD201 LED status CPU-LED state This register stores the information that indicates LED status (0: off, 1: on, 2: flashing (fast/slow)) of the CPU module in the following bit patterns.

(1) READY (2) ERROR (3) PROGRAM RUN (4) USER (5) BATTERY (6) CARD READY (7) CARD ACCESS (8) FUNCTION For the R00CPU, (5), (6), and (7) are fixed to 0. For the R01CPU and R02CPU, (5) is fixed to 0.

S (Status change)

SD203 Operating status of CPU Operating status of CPU The operating status of the CPU module is stored as follows: 0: RUN, 2: STOP, 3: PAUSE

S (Every END)

SD210 Clock data Clock data (year) The year value (four digits) of the clock data is stored as a BIN code. S/U (Request)

SD211 Clock data (month) The month value of the clock data is stored as a BIN code. S/U (Request)

SD212 Clock data (day) The day value of the clock data is stored as a BIN code. S/U (Request)

SD213 Clock data (hour) The hour value of the clock data is stored as a BIN code. S/U (Request)

SD214 Clock data (minute) The minute value of the clock data is stored as a BIN code. S/U (Request)

SD215 Clock data (second) The second value of the clock data is stored as a BIN code. S/U (Request)

SD216 Clock data (day of the week) The day of the week value of the clock data is stored as a BIN code. (0: Sun, 1: Mon, 2: Tue, 3: Wed, 4: Thu, 5: Fri, 6: Sat)

S/U (Request)

SD218 Time zone setting value Time zone (in minutes) The time zone setting value specified in the parameter is stored in increments of minutes. Example: when the setting value of the time zone is "UTC+9," the result of the following equation is stored into SD218: 9 60 (minutes) = 540.

S (Initial)

SD164 SD165

SD171

b15 b8b7 b0

2nd digit from the left

1st digit from the left

4th digit from the left

3rd digit from the left

16th digit from the left

15th digit from the left

32H (2) 31H (1)

34H (4) 33H (3)

SD164

SD165

47H (G) 46H (F)SD171

b15 b8b7 b0

b15 b0b4 b3b7b11 b8b12

(4)(5)(6)(7)(8) (3) (2) (1)

0 APPX Appendix 5 List of Special Register Areas

A

SD228*2 Multiple CPU system information

Number of CPU modules The number of CPU modules which constitute a multiple CPU system is stored (one to four, including those reserved).

S (Initial)

SD229*2 CPU module number in multiple CPU system

The number of this CPU No. is stored when a multiple CPU system is configured.

S (Initial)

SD230*2 CPU No.1 operating status The operation information for each CPU No. is stored (the amount of stored information depending on the number of CPU modules indicated in SD228 is stored).

(1) The operating status is stored in b0 to b3. 0: RUN 2: STOP 3: PAUSE 4: INITIALIZE FH: RESET

(2) The classification is stored in b4 and b5. However, minor or moderate errors will be those set in the CPU parameter RAS settings, system parameter I/O assignment settings, and multiple CPU settings.

0: Normal 1: Minor error (error code: 1000H to 1FFFH) 2: Moderate error (error code: 2000H to 3BFFH) 3: Major error (error code: 3C00H to 3FFFH)

(3) The stop error flag is stored in b7. 0: No stop error 1: Stop error

(4) The CPU module mounting status is stored in b15. 0: Not mounted 1: Mounted

S (During END/ Error)SD231*2 CPU No.2 operating status

SD232*2 CPU No.3 operating status

SD233*2 CPU No.4 operating status

SD241 Extension stage number 0: base unit only 1 to 7: number of extension base units

The maximum number of implemented extension base units is stored.

S (Initial)

SD242 Identification for whether or not Q series module can be mounted

Identification of the base type 0: Cannot be mounted

(There is no base unit on which the Q series module can be mounted.)

1: Can be mounted (There is a base unit on which the Q series module can be mounted.)

Identify whether or not Q series module can be mounted. When no SD memory card is inserted, the value is fixed to 0.

b0: Main base unit (fixed to 0) b1: Extension base unit 1 (Q series modules can be mounted.) b2: Extension base unit 2 (Q series modules can be mounted.) b3 to b7: Extension base unit 3 to 7 (Q series modules can be

mounted.) b8 to b15: Fixed to 0

S (Initial)

SD243 Number of base slots Number of base slots The number of slots of the base unit, which is specified in the Base / power supply / extension cable setting of system parameters, is stored. When the number of slots of the base unit is not specified by the system parameter, that of the mounted base unit is stored.

0: Main 1 to 7: Extension 1 to 7

S (Initial)

SD244

SD250 Loaded maximum I/O Loaded maximum I/O number

The value obtained by dividing the last I/O number for an implemented unit plus one by 16 is stored. Example 1: Last I/O number 010FH SD250 = 0011H

Example 2: Last I/O number 0FFFH SD250 = 0100H

S (Initial)

No. Name Data stored Details Set by (setting timing)

b15 b14 b8 b7 b6 b5 b4 b3 b0 (2)(3)(4) (1)

b7 b2 b1 b0 to

b15

SD243

SD244

b12 b11 b8 b7 b4 b3 b0

3 2 1 0

7 6 5 4

APPX Appendix 5 List of Special Register Areas 611

61

SD260 Number of points assigned to bit devices

X (L) The number of points assigned to the X device is stored in 32 bits. S (Initial)

SD261 X (H)

SD262 Y (L) The number of points assigned to the Y device is stored in 32 bits. S (Initial)

SD263 Y (H)

SD264 M (L) The number of points assigned to the M device is stored in 32 bits. The number of points is stored even when the number of points

assigned to M is 32K or less.

S (Initial)

SD265 M (H)

SD266 B (L) The number of points assigned to the B device is stored in 32 bits. The number of points is stored even when the number of points

assigned to B is 32K or less.

S (Initial)

SD267 B (H)

SD268 SB (L) The number of points assigned to the SB device is stored in 32 bits.

The number of points is stored even when the number of points assigned to SB is 32K or less.

S (Initial)

SD269 SB (H)

SD270 F (L) The number of points assigned to the F device is stored in 32 bits. S (Initial)

SD271 F (H)

SD272 V (L) The number of points assigned to the V device is stored in 32 bits. S (Initial)

SD273 V (H)

SD274 L (L) The number of points assigned to the L device is stored in 32 bits. S (Initial)

SD275 L (H)

SD276*2 S (L) The number of points assigned to the S device is stored in 32 bits. S (Initial)

SD277*2 S (H)

SD280 Number of points assigned to word devices

D (L) The number of points assigned to the D device is stored in 32 bits. The number of points is stored even when the number of points

assigned to D is 32K or less.

S (Initial)

SD281 D (H)

SD282 W (L) The number of points assigned to the W device is stored in 32 bits. The number of points is stored even when the number of points

assigned to W is 32K or less.

S (Initial)

SD283 W (H)

SD284 SW (L) The number of points assigned to the SW device is stored in 32 bits.

The number of points is stored even when the number of points assigned to SW is 32K or less.

S (Initial)

SD285 SW (H)

SD288 Number of points assigned to timer/counter devices

T (L) The number of points assigned to the T device is stored in 32 bits. The number of points is stored even when the number of points

assigned to T is 32K or less.

S (Initial)

SD289 T (H)

SD290 ST (L) The number of points assigned to the ST device is stored in 32 bits.

The number of points is stored even when the number of points assigned to ST is 32K or less.

S (Initial)

SD291 ST (H)

SD292 C (L) The number of points assigned to the C device is stored in 32 bits. The number of points is stored even when the number of points

assigned to C is 32K or less.

S (Initial)

SD293 C (H)

SD294 LT (L) The number of points assigned to the LT device is stored in 32 bits.

The number of points is stored even when the number of points assigned to LT is 32K or less.

S (Initial)

SD295 LT (H)

SD296 LST (L) The number of points assigned to the LST device is stored in 32 bits.

The number of points is stored even when the number of points assigned to LST is 32K or less.

S (Initial)

SD297 LST (H)

SD298 LC (L) The number of points assigned to the LC device is stored in 32 bits.

The number of points is stored even when the number of points assigned to LC is 32K or less.

S (Initial)

SD299 LC (H)

SD300 Number of points assigned to the index register

Z The number of points assigned to the Z device is stored. S (Initial)

SD302 Number of points assigned to the long index register

LZ The number of points assigned to the LZ device is stored. S (Initial)

No. Name Data stored Details Set by (setting timing)

2 APPX Appendix 5 List of Special Register Areas

A

*1 The programmable controller CPU with firmware version "28" or later supports these special register areas. However, there are no

restrictions on the version of the R00CPU, R01CPU, and R02CPU. *2 There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. ( Page

700 Added and Enhanced Functions) *3 The CPU module with the following firmware versions supports these special register areas.

R00CPU, R01CPU, R02CPU: "24" or later CPU modules other than R00CPU, R01CPU, and R02CPU: "57" or later

SD306 Number of points assigned to the file register

ZR (L) The number of points assigned to the ZR device is stored in 32 bits.

The number of points is stored even when the number of points assigned to ZR is 32K or less.

S (Initial)

SD307 ZR (H)

SD308 Number of points assigned to refresh devices

RD (L) The number of points assigned to the RD device is stored in 32 bits.

The number of points is stored even when the number of points assigned to RD is 32K or less.

S (Initial)

SD309 RD (H)

SD312 File register block number File register block number The block number of the file register currently selected is stored. S (Status change)

SD384*2 System operation setting LED control setting for program restoration information write status

Target file setting for the file batch online change

Either of the following two setting can be used. This setting is written to the setting storage area (system area) by turning off and on SM384. LED control setting for program restoration information write status Set either of the following to specify whether or not the LED flashes when the program restoration information is not in the CPU module. AFA0H: LED flashing AFAFH: Without LED flashing

Target file setting for the file batch online change Set either of the following to specify the target file of the file batch online change For the R00CPU, R01CPU, and R02CPU, this setting is always "program file/FB file/global label setting file" regardless of the set value of this relay. AFB0H: Program file only AFBFH: Program file/FB file/global label setting file

U

SD385*2 System operation setting error cause

Error cause for the case when failing in writing into setting storage area

An error cause is stored when failing in writing into setting storage area (system memory). (Linked with SM385) 0H:No error 100H:A value stored in SD384 is out of the specified range. 200H:Write failure

S (Status change)

No. Name Data stored Details Set by (setting timing)

APPX Appendix 5 List of Special Register Areas 613

61

SFC information The following is the special register area relating to SFC information. (There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. Page 700 Added and Enhanced Functions)

System clock The following is the list of special register areas relating to the system clock.

*1 The CPU module with the following firmware versions supports these special register areas. R00CPU, R01CPU, R02CPU: "24" or later CPU modules other than R00CPU, R01CPU, and R02CPU: "57" or later

No. Name Data stored Details Set by (setting timing)

SD329 Online change (SFC block) target block number

SFC block number A target SFC block number is stored while the online change (SFC block) is being executed (SM329 = ON).

FFFFH is stored when the online change (SFC block) is not executed.

S (Status change)

No. Name Data stored Details Set by (setting timing)

SD412 One second counter The number of counts that is counted once per second.

The value in this register increments by one for each second after the CPU module enters in RUN mode.

A counting cycle from 0 to 65535 to 0 is repeated.

S (Status change)

SD414 2n second clock setting

Unit setting for 2n second clock The n value of the 2n second clock is stored (Default: 30). Configurable range is -32768 to 32767 (0 to FFFFH).

U

SD415 2n ms clock setting Unit setting for 2n ms clock The n value for the 2n ms clock is stored. (Default: 30). Configurable range is -32768 to 32767 (0 to FFFFH).

U

SD420 Scan counter The number of counts that is counted once for each scan.

The value in this register increments by one for each scan after the CPU module enters in RUN mode (however, the count is skipped for scans by the initial execution type program).

A counting cycle from 0 to 65535 to 0 is repeated.

S (Every END)

SD1184 *1

System clock (SM400 to SM403) every end update setting

System clock (SM400 to SM403) every end update setting

A value to enable or disable the system clock (SM400 to SM403) every end update is stored. Turning off and on SM1184 (System clock (SM400 to SM403) every end update setting request) submits a request to set either of the following two values. AA00H: Disabled AA55H: Enabled

U

SD1185 *1

System clock (SM400 to SM403) every end update setting error cause

Error cause for the case when failing in writing into setting storage area

This register stores an error cause when the setting value has failed to be written to the setting storage area. (This register operates together with SM1185 (System clock (SM400 to SM403) every end update setting error).) 0000H: No error 0100H: Value in SD1184 out of range 0200H: Setting value failed to be written

S (Status change)

4 APPX Appendix 5 List of Special Register Areas

A

Fixed scan function information The following is the list of special register areas relating to the fixed scan function information.

No. Name Data stored Details Set by (setting timing)

SD480 Number of cycle overrun events for inter-module synchronization cycle program (I44)

0: No cycle overrun event 1 to 65535:Accumulated number

of cycle overrun events

The number of events in which the inter-module synchronous interrupt program (I44) has not been completed within the inter-module synchronization cycle or the program cannot be executed due to various reasons, such as execution of a higher-priority interrupt program and interrupt disabling by the instruction execution is stored. When the count exceeds 65535, it returns to 0 and starts a new cycle. The number of cycle overrun events is counted regardless of the setting content for the error check setting of the RAS setting (execution check of the inter- module synchronous interrupt (I44)).

S (Status change)

SD481*1 Number of cycle overrun events for multiple CPU synchronization program (I45)

0: No cycle overrun event 1 to 65535:Accumulated number

of cycle overrun events

The number of events in which the multiple CPU synchronization program (I45) has not been completed within the fixed scan communication cycle or the program cannot be executed due to various reasons, such as execution of a higher-priority interrupt program and interrupt disabling by the instruction execution is stored. When the count exceeds 65535, it returns to 0 and starts a new cycle. The number of cycle overrun events is counted regardless of the setting content for the error check setting of the RAS setting (execution check of the multiple CPU synchronization program (I45)).

S (Status change)

SD484*1 Number of execution section excess errors for multiple CPU synchronization interrupt program

0: No error (Normal) 1 to 65535:Accumulated number

of errors

The number of events in which the program is executed exceeding the program execution section within the specified multiple CPU synchronization cycle is stored. When the count exceeds 65535, it returns to 0 and starts a new cycle. Note that the number of error occurrences is counted regardless of the CPU module operation setting for error detections within the RAS setting of the CPU parameter.

S (Status change)

SD500 Execution program number

Execution program number The program number which is currently executed is stored as a BIN value. S (Status change)

SD518 Initial scan time Initial scan time (unit: ms) The initial scan time is stored into SD518 and SD519 (The time is measured in microseconds (s).)

SD518: stores a value in the ms place (storage range: 0 to 65535) SD519: stores a value in the s place (storage range: 0 to 999) These areas are cleared to 0 when the operating status of the CPU

module is switched from STOP to RUN.

S (Every END)SD519 Initial scan time (unit: s)

SD520 Current scan time Current scan time (unit: ms) The current scan time is stored into SD520 and SD521 (it is measured in increments of s).

SD520: stores a value in the ms place (storage range: 0 to 65535) SD521: stores a value in the s place (storage range: 0 to 999) Example: If the current scan time is 23.6ms, the following values are stored: SD520 = 23 SD521 = 600 These areas are cleared to 0 when the operating status of the CPU

module is switched from STOP to RUN.

S (Every END)SD521 Current scan time (unit: s)

SD522 Minimum scan time Minimum scan time (unit: ms) The minimum value of the scan time other than one for the initial execution program is stored into SD522 and SD523 (it is measured in increments of s).

SD522: stores a value in the ms place (storage range: 0 to 65535) SD523: stores a value in the s place (storage range: 0 to 999) These areas are cleared to 0 when the operating status of the CPU

module is switched from STOP to RUN.

S (Every END)SD523 Minimum scan time (unit: s)

SD524 Maximum scan time Maximum scan time (unit: ms) The maximum value of the scan time other than one for the initial execution program is stored into SD524 and SD525 (it is measured in increments of s).

SD524: stores a value in the ms place (storage range: 0 to 65535) SD525: stores a value in the s place (storage range: 0 to 999) These areas are cleared to 0 when the operating status of the CPU

module is switched from STOP to RUN.

S (Every END)SD525 Maximum scan time (unit: s)

APPX Appendix 5 List of Special Register Areas 615

61

*1 There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. ( Page 700 Added and Enhanced Functions)

SD526 END processing time END processing time (unit: ms) The time period from completion of a scan program until start of the next scan is stored into SD526 to SD527 (it is measured in increments of s).

SD526: stores a value in the ms place (storage range: 0 to 65535) SD527: stores a value in the s place (storage range: 0 to 999) These areas are cleared to 0 when the operating status of the CPU

module is switched from STOP to RUN.

S (Every END)SD527 END processing time (unit: s)

SD528 Constant scan wait time

Constant scan wait time (unit: ms) The waiting time specified in the constant scan setting process is stored into SD528 and SD529 (it is measured in increments of s).

SD528: stores a value in the ms place (storage range: 0 to 65535) SD529: stores a value in the s place (storage range: 0 to 999) These areas are cleared to 0 when the operating status of the CPU

module is switched from STOP to RUN.

S (Every END)SD529 Constant scan wait time (unit: s)

SD530 Scan program execution time

Scan program execution time (unit: ms)

The execution time of the scan program for one scan is stored into SD530 and SD531 (it is measured in increments of s).

SD530: stores a value in the ms place (storage range: 0 to 65535) SD531: stores a value in the s place (storage range: 0 to 999) These areas are cleared to 0 when the operating status of the CPU

module is switched from STOP to RUN.

S (Every END)

SD531 Scan program execution time (unit: s)

No. Name Data stored Details Set by (setting timing)

6 APPX Appendix 5 List of Special Register Areas

A

Drive information The following is the list of special register areas relating to the drive information.

No. Name Data stored Details Set by (setting timing)

SD600*4 Memory card mounting status

SD memory card type This register indicates the type of mounted SD memory cards.

b0 to b3: Fixed to 0 b4 to b7

0: Does not exist 4: SD memory card b8 to b15: Fixed to 0

S (Initial, card insertion/ removal)

SD604*4 SD memory card (drive 2) usage status

SD memory card (drive 2) usage status

Usage status of the SD memory card is stored using the following bit pattern. (On indicates being used.) b0: Event history b1: Module extension parameter*1

b2: Label communication data b3 to b15: Not used

S (Status change)

SD606*4 SD memory card (drive 2) capacity

SD memory card (drive 2) capacity: the lower digits (unit: K bytes)

The capacity of the SD memory card is stored in increments of 1K byte (the amount of free space for a formatted memory card is stored).

S (Initial, card insertion/ removal)

SD607*4 SD memory card (drive 2) capacity: the higher digits (unit: K bytes)

The capacity of the SD memory card is stored in increments of 1K byte (the amount of free space for a formatted memory card is stored).

S (Initial, card insertion/ removal)

SD610*4 SD memory card (drive 2) free space

SD memory card (drive 2) free space: the lower digits (unit: K bytes)

The amount of free space of the SD memory card is stored in increments of 1K byte.

S (at change)

SD611*4 SD memory card (drive 2) free space: the higher digits (unit: K bytes)

The amount of free space of the SD memory card is stored in increments of 1K byte.

S (at change)

SD614 Device/label memory (drive 3) usage status

Device/label memory (drive 3) usage status

Usage status of the device/label memory is stored using the following bit pattern. (On indicates being used.) b0: File register b1 to b15: Not used

S (Status change)

SD616 Device/label memory (drive 3) capacity

Device/label memory (drive 3) capacity: the lower digits (unit: K bytes)

The capacity of the device/label memory is stored in increments of 1K byte (the amount of free space for a formatted memory card is stored).

S (Initial)

SD617 Device/label memory (drive 3) capacity: the higher digits (unit: K bytes)

The capacity of the device/label memory is stored in increments of 1K byte (the amount of free space for a formatted memory card is stored).

S (Initial)

SD618 Device/label memory (file storage area) capacity

Device/label memory (file storage area) (drive 3) capacity: the lower digits (unit: K bytes)

The capacity of the device/label memory (file storage area) is stored in increments of 1K byte (the amount of free space for a formatted memory card is stored).

S (Initial)

SD619 Device/label memory (file storage area) (drive 3) capacity: the higher digits (unit: K bytes)

The capacity of the device/label memory (file storage area) is stored in increments of 1K byte (the amount of free space for a formatted memory card is stored).

S (Initial)

SD620 Data memory (drive 4) usage status

Data memory (drive 4) usage status

Usage status of the data memory is stored using the following bit pattern. (On indicates being used.) b0: Event history b1: Module extension parameter*1

b2: Label communication data b3 to b15: Not used

S (Status change)

SD622 Data memory (drive 4) capacity

Data memory (drive 4) capacity: the lower digits (unit: K bytes)

The capacity of the data memory is stored in increments of 1K byte (the amount of free space for a formatted memory card is stored).

S (Initial)

SD623 Data memory (drive 4) capacity: the higher digits (unit: K bytes)

The capacity of the data memory is stored in increments of 1K byte (the amount of free space for a formatted memory card is stored).

S (Initial)

b15 b8 b7 b4 b3 b0

APPX Appendix 5 List of Special Register Areas 617

61

SD626*5 Extended SRAM cassette capacity identification information

Capacity identification information of the Extended SRAM cassette

Capacity identification information of the Extended SRAM cassette is stored. Unmounted: 0, 1M: 1, 2M: 2, 4M: 3, 8M: 4, 16M: 5

S (Initial)

SD629 Program memory write (transfer) status

Write (transfer) status display (percent)

This register displays write (transfer) status to the program memory in percentage (0 to 100%). The initial value is "0". Upon completion of writing, this register is set to "100". It is set to "0" at the time when the write command is issued.

S (Writing)

SD630 Program memory write count index

Index of the number of write operations up to now

This register indicates the index value for the number of write operations to the program memory up to now (stored as a 32-bit BIN value). However, the number of write operations is not equal to the index value.

When the index value exceeds 100000, an error is generated (the index value is continued to be counted even when it exceeds 100000). If the index value exceeds 100000, the CPU module must be replaced.

S (Writing)

SD631

SD633 Data memory write (transfer) status

Write (transfer) status display (percent)

This register displays write (transfer) status to the data memory in percentage. (0 to 100%). The initial value is "0". Upon completion of writing, this register is set to "100". It is set to "0" at the time when the write command is issued.*2

S (Writing)

SD634 Index for the number of data memory write operations

Index of the number of write operations up to now

This register indicates the index value for the number of write operations to the data memory up to now (stored as a 32-bit BIN value). However, the number of write operations is not equal to the index value.

When the index value exceeds 100000, an error is generated (the index value is continued to be counted even when it exceeds 100000). If the index value exceeds 100000, the CPU module must be replaced.

S (Writing)

SD635

SD640 Internal buffer empty area usage status

Internal buffer empty area usage status (usage status of the internal buffer for functions where the internal buffer capacity is not set in the internal buffer capacity setting of the CPU parameters)

This register stores the following in a bit pattern: usage status of the internal buffer for functions where the internal buffer capacity is not set in the internal buffer capacity setting of the CPU parameters. (On indicates being used.) b0: Used for realtime monitor b1 to b15: Not used

S (Status change)

SD642 Internal buffer capacity

Internal buffer capacity Low-order (in K bytes)

The capacity of the internal buffer is stored in K bytes. S (Initial)

SD643 Internal buffer capacity High-order (in K bytes)

The capacity of the internal buffer is stored in K bytes. S (Initial)

SD644 Internal buffer free area space

Internal buffer free area space Low-order (in K bytes)

This register stores the following in K bytes: internal buffer free space that is not set in the internal buffer capacity setting of the CPU parameters.

S (Status change)

SD645 Internal buffer free area space High-order (in K bytes)

This register stores the following in K bytes: internal buffer free space that is not set in the internal buffer capacity setting of the CPU parameters.

S (Status change)

SD648*6 Function memory capacity

Function memory capacity Low-order (in K bytes)

The capacity of the function memory is stored in K bytes. S (Initial)

SD649*6 Function memory capacity High-order (in K bytes)

The capacity of the function memory is stored in K bytes. S (Initial)

SD650*6 Function memory free space capacity

Function memory free space capacity Low-order (in K bytes)

The amount of free space of the function memory is stored in K bytes. S (Status change)

SD651*6 Function memory free space capacity High-order (in K bytes)

The amount of free space of the function memory is stored in K bytes. S (Status change)

SD652*6 Function memory clear error cause

Function memory clear error cause

An error cause detected at a request for clearing the function memory is stored. 0: No error Other than 0:For details on the values stored when an error occurs, refer

to the list of error codes. ( Page 502 List of Error Codes) The register is cleared to 0 at a request for clearing the function memory.

S (Status change)

No. Name Data stored Details Set by (setting timing)

8 APPX Appendix 5 List of Special Register Areas

A

*1 It is stored when used for the Ethernet function of CPU module. *2 When the save destination for the event history is the data memory: the event history will be stored at the timing of powering off and on

and resetting the CPU module. Accordingly, since the data will be written into the data memory, "100" is stored. (When the save destination for the event history is the SD memory, the initial value remains "0".)

*3 This is the memory used by the system when the CPU module is executing functions. *4 The CPU module where the SD memory card can be used supports these special register areas. *5 The CPU module where the extended SRAM cassette can be used supports these special register areas. *6 There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. ( Page

700 Added and Enhanced Functions)

SD653*6 File transfer to data memory error cause

File transfer to data memory error cause

The error cause that is detected at file transfer to the data memory is stored. 0: No error Other than 0:For details on the values stored when an error occurs, refer

to the list of error codes. ( Page 502 List of Error Codes) The register is cleared to 0 when SM653 (File transfer to data memory request) changes from off to on.

S (Status change)

No. Name Data stored Details Set by (setting timing)

APPX Appendix 5 List of Special Register Areas 619

62

Instruction related The following is the list of special register areas relating to the instruction-related items.

No. Name Data stored Details Set by (setting timing)

SD757 Current interrupt priority

Current interrupt priority The priority for the interrupt of the interrupt program currently executed is stored. 1 to 8:Priority for the interrupt pointer of the interrupt program currently being

executed 0: No interrupt operation (default)

S (Status change)

SD758 Interrupt disabling for each priority setting value

Interrupt disabling for each priority setting value

The interrupt priority of the interrupt program that the interrupt is disabled by using the DI instructions (Disabling interrupt programs/Disabling interrupt programs with specified priority or lower) and the EI instruction (Enabling interrupt programs) is stored in this register. 1: Interrupt programs with priority 1 or lower (all priority levels) disabled (default) 2: Interrupt programs with priority 2 or lower disabled 3: Interrupt programs with priority 3 or lower disabled 4: Interrupt programs with priority 4 or lower disabled 5: Interrupt programs with priority 5 or lower disabled 6: Interrupt programs with priority 6 or lower disabled 7: Interrupt programs with priority 7 or lower disabled 8: Interrupt programs with priority 8 or lower disabled 0: No interrupt program disabled (interrupt programs with any priority level

enabled)

S (Status change)

SD760 Unicode text file faulty area in the DBIMPORT instruction

Row number of the Unicode text file (lower)

If an error in the Unicode text file is detected when the DBIMPORT(P) instruction is executed, the row number of the Unicode text file is stored. The value is stored when the error completion signal of the DBIMPORT(P) instruction is turned on and is cleared to 0 when the DBIMPORT(P) instruction is executed.

S (Status change)

SD761 Row number of the Unicode text file (upper)

S (Status change)

SD771 Specification of the number of write instruction executions to data memory

Specification of the number of write instruction executions to data memory

In this register, the maximum number of the data memory writing instruction (SP.DEVST) executions per day is specified. When the number of data memory writing instruction executions exceeds the value specified in this register, an error is generated. Setting range is from 1 to 32767. If a value is set outside the range, an error is generated during the data memory writing instruction execution.

U

SD774*3 Execution status of data table sort instructions

Execution status of data table sort instructions

The execution statuses of SORTTBL/SORTTBL2/DSORTTBL2 instructions are stored. The bit indicating the finish of each instruction turns on when the instruction is finished. SORTTBL instruction

b0: Finish (0: Status except execution finished, 1: Execution finished) b2: Execution (0: Not executed, 1: Executed) SORTTBL2 instruction

b6: Finish (0: Status except execution finished, 1: Execution finished) b8: Execution (0: Not executed, 1: Executed) DSORTTBL2 instruction

b9: Finish (0: Status except execution finished, 1: Execution finished) b11: Execution (0: Not executed, 1: Executed)

S (Status change)

b2 b0

b8 b6

b11 b9

0 APPX Appendix 5 List of Special Register Areas

A

*1 When the value out of the range is specified, operation runs while its value is being regarded as max value of each range of multiple CPU system configuration.

*2 There are restrictions on the firmware version of the supported CPU module and software version of the engineering tool. ( Page 700 Added and Enhanced Functions)

*3 The CPU module where this function can be used supports these special register areas.

SD775 Selection of refresh processing during the COM instruction execution

Selection of refresh processing during the COM instruction execution

In this register, whether or not each processing is executed during the COM instruction execution is selected (Default: 0). The specification on the SD775 is effective when SM775 is turned on.

Refresh processing (0: Not executed, 1: Executed) b0: I/O refresh, I/O fetch from a group out of the multiple CPU system b1: Link refresh of the CC-Link module b2: Link refresh of the CC-Link IE Controller Network module and MELSECNET/H

network module b3: Intelligent function module refresh b4: Refresh using the CPU buffer memory of the multiple CPU system (END) b6: Link refresh of the CC-Link IE Field Network module b13: Link refresh of CC-Link IE Field Network Basic Device/label access service processing execution (0: Executed, 1: Not executed) b15: Device/label access service processing (communications with the engineering

tool, GOT, or other external devices)

U

SD792 and SD793

PID limit setting (for complete derivative)

0: Limit restriction applied 1: No limit restriction

The limit restriction for each PID loop is specified as follows: (for the PIDCONT instruction)

1 to 32: Loop 1 to 32

U

SD794 and SD795

PID limit setting (for incomplete derivative)

0: Limit restriction applied 1: No limit restriction

The limit restriction for each PID loop is specified as follows: (for the S.PIDCONT instruction)

1 to 32: Loop 1 to 32

U

SD796*2 Maximum number of blocks used for the multiple CPU dedicated instruction (for CPU No.1)

The maximum number of blocks to be used for the dedicated instruction Depending on the number of CPU modules which constitute a multiple CPU system, the range is as follows.*1

When constituting two modules: 2 to 599 When constituting three modules: 2 to 299 When constituting four modules: 2 to 199 (Default: 2).

The maximum number of blocks used for the multiple CPU dedicated instruction is specified (for CPU No.1).

When executing the multiple CPU dedicated instruction on CPU No. 1, if the number of free blocks in the dedicated instruction transfer area is less than the setting value on this register, SM796 is turned on.

This value is used as interlock signal for the continuous executions of the multiple CPU dedicated instruction.

U

SD797*2 Maximum number of blocks setting used for the multiple CPU dedicated instruction (for CPU No.2)

The maximum number of blocks used for the multiple CPU dedicated instruction is specified (for CPU No.2).

When executing the multiple CPU dedicated instruction on CPU No. 2, if the number of free blocks in the dedicated instruction transfer area is less than the setting value on this register, SM797 is turned on.

This value is used as interlock signal for the continuous executions of the multiple CPU dedicated instruction.

U

SD798*2 Maximum number of blocks setting used for the multiple CPU dedicated instruction (for CPU No.3)

The maximum number of blocks used for the multiple CPU dedicated instruction is specified (for CPU No.3).

When executing the multiple CPU dedicated instruction on CPU No. 3, if the number of free blocks in the dedicated instruction transfer area is less than the setting value on this register, SM798 is turned on.

This value is used as interlock signal for the continuous executions of the multiple CPU dedicated instruction.

U

SD799*2 Maximum number of blocks setting used for the multiple CPU dedicated instruction (for CPU No.4)

The maximum number of blocks used for the multiple CPU dedicated instruction is specified (for CPU No.4).

When executing the multiple CPU dedicated instruction on CPU No. 4, if the number of free blocks in the dedicated instruction transfer area is less than the setting value on this register, SM799 is turned on.

This value is used as interlock signal for the continuous executions of the multiple CPU dedicated instruction.

U

No. Name Data stored Details Set by (setting timing)

b15 b0b1b2b3b4b6b13

SD792 b15 b1 b0

SD793

16

32

2

18

1

17

to

to

SD794 b15 b1 b0

SD795 17 12

18 16 32

to to

APPX Appendix 5 List of Special Register Areas 621

62

Firmware update function The following is the list of special register areas relating to the firmware update function (firmware update using an SD memory card). (The CPU module where this function can be used supports these special register areas. Page 700 Added and Enhanced Functions)

No. Name Data stored Details Set by (setting timing)

SD904 Latest firmware update information (network)

History information

Version after the update (network)

The firmware version after the update execution is stored. When the update is completed with an error, 0 is stored.

S (Initial)

SD905 Version before the update (network)

The firmware version before the update execution is stored. S (Initial)

SD906 Previous firmware update information (network)

Version after the update (network)

The firmware version after the update execution is stored. When the update is completed with an error, 0 is stored.

S (Initial)

SD907 Version before the update (network)

The firmware version before the update execution is stored. S (Initial)

SD912 Latest firmware update information (CPU)*1

Execution time (year)

The year value (four digits) of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD913 Execution time (month)

The month value of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD914 Execution time (day)

The day value of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD915 Execution time (hour)

The hour value of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD916 Execution time (minute)

The minute value of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD917 Execution time (second)

The second value of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD918 Execution time (day of the week)

The day of the week value of the date/time when the firmware update was executed is stored as a BIN code. (0: Sun, 1: Mon, 2: Tue, 3: Wed, 4: Thu, 5: Fri, 6: Sat)

S (Initial)

SD919 Version after the update (CPU)

The firmware version after the update execution is stored. When the update is completed with an error, 0 is stored.

S (Initial)

SD920 Version before the update (CPU)

The firmware version before the update execution is stored. S (Initial)

SD921 Latest firmware update result

Target The start I/O number of the module where the firmware update was executed is stored. CPU module: 3FFH

S (Initial)

SD922 Execution result The execution result of the firmware update is stored. 0001H: Completed successfully 0100H: Flash ROM error 0200H: Model mismatched 0201H: File invalid 0202H: Combination invalid 0203H: Firmware update prohibited state 0300H: Firmware data error

S (Initial)

2 APPX Appendix 5 List of Special Register Areas

A

*1 For the RnENCPU, information of the CPU part is displayed.

SD923 Previous firmware update information (CPU)*1

History information

Execution time (year)

The year value (four digits) of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD924 Execution time (month)

The month value of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD925 Execution time (day)

The day value of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD926 Execution time (hour)

The hour value of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD927 Execution time (minute)

The minute value of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD928 Execution time (second)

The second value of the date/time when the firmware update was executed is stored as a BIN code.

S (Initial)

SD929 Execution time (day of the week)

The day of the week value of the date/time when the firmware update was executed is stored as a BIN code. (0: Sun, 1: Mon, 2: Tue, 3: Wed, 4: Thu, 5: Fri, 6: Sat)

S (Initial)

SD930 Version after the update (CPU)

The firmware version after the update execution is stored. When the update is completed with an error, 0 is stored.

S (Initial)

SD931 Version before the update (CPU)

The firmware version before the update execution is stored. S (Initial)

SD932 Previous firmware update result

Target The start I/O number of the module where the firmware update was executed is stored. CPU module: 3FFH

S (Initial)

SD933 Execution result The execution result of the firmware update is stored. 0001H: Completed successfully 0100H: Flash ROM error 0200H: Model mismatched 0201H: File invalid 0202H: Combination invalid 0203H: Firmware update prohibited state 0300H: Firmware data error

S (Initial)

No. Name Data stored Details Set by (setting timing)

APPX Appendix 5 List of Special Register Areas 623

62

Latch area The following is the list of special register areas relating to the latch area. (The CPU module where each function can be used supports these special register areas. Page 700 Added and Enhanced Functions)

No. Name Data stored Details Set by (setting timing)

SD940 Stop direction at file change on label specification

Stop direction at file change on label specification

Specify the operation for changing program files or the global label setting file. When the stop direction is given, an error occurs in the corresponding function (setting No.). (On: Stop the function, Off: Do not stop the function (The function continues to operate.))

b0: Data logging setting No.1 b1: Data logging setting No.2 b2: Data logging setting No.3 b3: Data logging setting No.4 b4: Data logging setting No.5 b5: Data logging setting No.6 b6: Data logging setting No.7 b7: Data logging setting No.8 b8: Data logging setting No.9 b9: Data logging setting No.10 b15: Real-time monitor

U

SD944 Backup function of the CPU module data backup/ restoration function

Backup function setting Set the backup function using the following bit pattern. (Off: Disabled, On: Enabled)

b0: Automatic backup setting by specification of day and time b1: Automatic backup setting by specification of time and day of the

week b5: Upper limit value status for the number of the CPU module backup

data b10: Retry execution for the automatic backup b15: Automatic backup setting at occurrence of the CPU stop error

U

SD947 Day and time setting for automatic backup (day)

Store the day when the automatic backup on the specified day and time is executed using the BIN code. Day (1 to 31)

U

SD948 Day and time setting for automatic backup (hour)

Store the hour when the automatic backup on the specified day and time is executed using the BIN code. Hour (0 to 23)

U

SD949 Day and time setting for automatic backup (minute)

Store the minute when the automatic backup on the specified day and time is executed using the BIN code. Minute (0 to 59)

U

SD950 Time and day of the week setting for automatic backup (hour)

Store the hour when the automatic backup on the specified day of the week and time is executed using the BIN code. Hour (0 to 23)

U

SD951 Time and day of the week setting for automatic backup (minute)

Store the minute when the automatic backup on the specified day of the week and time is executed using the BIN code. Minute (0 to 59)

U

SD952 Time and day of the week setting for automatic backup (day of the week)

Set the day of the week when the automatic backup is executed using the following bit pattern. (Off: Disabled, On: Enabled)

b0: Sunday, b1: Monday, b2: Tuesday, b3: Wednesday, b4: Thursday, b5: Friday, b6: Saturday

U

SD953 Backup error cause The cause of an error that occurred during the CPU module data backup is stored.

0H: No error Other than 0H:For details on the values stored when an error occurs,

refer to the list of error codes. ( Page 502 List of Error Codes) "0" is set at the start of the CPU module data backup.

S (Error)

b15 b1b2b3b4b5b6 b0b7b8b9

b15 b1b5b10 b0 0 0 0

b15 b1b2b3b4b5b6 b0 0

4 APPX Appendix 5 List of Special Register Areas

A

SD954 Restoration function of the CPU module data backup/ restoration function

Restoration target data setting

Set the target data to be restored with the CPU module data restoration function. 0: All the target data 1: Device/label data only 2: All the target data except for the device/label data

U

SD955 Restoration function setting

Set the CPU module data restoration function using the following bit pattern. (Off: Disabled, On: Enabled)

b0: Automatic restoration b1: Initialization at automatic restoration b13: Latest data b14: Special relay and special register b15: Continuous operation with the status at backup

U

SD956 Restoration target date folder setting

Store the target folder (date folder) of the CPU module data restoration using BCD code.

(1) Day (1 to 31) (2) Month (1 to 12) (3) Year (last two digits) (0 to 99) (4) Year (first two digits) (0 to 99) [Example] To specify the date folder of June 15 2015, store

"H20150615".

U

SD957 U

SD958 Restoration target number folder setting

Specify the target folder of the CPU module data restoration. 1 to 32767: Serial number of the backup folder (*****) in a date folder (00001 to 32767)

U

SD959 Restoration error cause The cause of an error that occurred during the CPU module data restoration is stored.

0H: No error Other than 0: For details on the values stored when an error occurs, refer to the list of error codes. ( Page 502 List of Error Codes) "0" is set at the start of the CPU module data backup.

S (Error)

SD960 Backup function of the CPU module data backup/ restoration function

Upper limit status for the number of CPU module backup data

This register indicates the set value of the upper limit for the number of backup data in accordance with bit 5 of SD944. Bit 5 of SD944 is off: 0 Bit 5 of SD944 is on: 1 to 100

S (Status change)

No. Name Data stored Details Set by (setting timing)

b1b13b14b15 b0 0

b2

SD957

b15 b8 b7 b0b31 b24 b23 b16 (1)(2)(3)(4)

SD956

APPX Appendix 5 List of Special Register Areas 625

62

Data logging function The following is the list of special register areas relating to the data logging function. (The R00CPU does not support the use of these functions.)

No. Name Data stored Details Set by (setting timing)

SD1200 Data logging Function memory use condition

Data logging Function memory use condition

The status of the data logging when the function memory is set for the storage location of data logging files are stored in the following bit patterns.

b0: Setting No.1 b1: Setting No.2

b9: Setting No.10 Each bit turns on when a relevant data logging starts and turns off

when the data logging stops.

S (Status change)

SD1203 Data logging file transfer stop information

Data logging file transfer stop information

To stop data transfer of each data logging setting number, set the relevant setting number with the following bit pattern. (Off: Disabled, On: Enabled)

b0: Setting No.1 b1: Setting No.2

b9: Setting No.10 This setting is activated when SM1203 is turned on.

U

SD1210 Data logging setting No.1 Latest storage file number

Latest storage file number The latest storage file number This register is cleared to 0 by the stop command from CPU Module

Logging Configuration Tool.

S (Status change)SD1211

SD1212 Data logging setting No.1 Oldest storage file number

Oldest storage file number The oldest storage file number This register is cleared to 0 by the stop command from CPU Module

Logging Configuration Tool.

S (Status change)SD1213

SD1214 Data logging setting No.1 Internal buffer free space

Free space size of the internal buffer (K bytes)

The amount of free space of the internal buffer is stored in K bytes. The smaller the value, the higher the generating ratio of processing overflow.

For the trigger logging, it refers to the total capacity of internal buffer until the data for the number of records is collected after a trigger occurred.

This register is cleared to 0 by the stop command from CPU Module Logging Configuration Tool.

S (Error)

SD1215 Data logging setting No.1 Number of processing overflow occurrences

Number of processing overflow occurrences

The number of data logging processing overflow occurrences When overflow occurs, data is lost. When the count exceeds 65535, it returns to 0 and starts a new cycle. With "Stop" set for the operation at the time when the number of save

files exceeds the limit, a processing overflow may occur until the stop operation is completed after the collection of data corresponding to the specified number of storage files was completed.

This register is cleared to 0 when the setting is registered or by the stop command from CPU Module Logging Configuration Tool.

S (Error)

SD1216 Data logging setting No.1 data logging error cause

Data logging error cause Cause of the error generated during data logging operations is stored. 0: No error Other than 0:For details on the values stored when an error occurs, refer

to the list of error codes. ( Page 502 List of Error Codes)

S (Error)

SD1217 Data logging setting No.1 Data logging file transfer error cause

Data logging file transfer error cause

An error cause that is detected last in the data logging file transfer function or a transferring of data logging files to the data memory is stored. 0: No error Other than 0:For details on the values stored when an error occurs, refer

to the list of error codes. ( Page 502 List of Error Codes) This register is cleared to 0 when data logging is started.

S (Error)

b1b2b3b4b5b6b7b8b9 b0

b1b2b3b4b5b6b7b8b9 b0

6 APPX Appendix 5 List of Special Register Areas

A

SD1220 to SD1227

Data logging setting No.2

Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SD1210 to SD1217). Same configuration as the setting No.1

SD1230 to SD1237

Data logging setting No.3

Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SD1210 to SD1217). Same configuration as the setting No.1

SD1240 to SD1247

Data logging setting No.4

Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SD1210 to SD1217). Same configuration as the setting No.1

SD1250 to SD1257

Data logging setting No.5

Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SD1210 to SD1217). Same configuration as the setting No.1

SD1260 to SD1267

Data logging setting No.6

Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SD1210 to SD1217). Same configuration as the setting No.1

SD1270 to SD1277

Data logging setting No.7

Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SD1210 to SD1217). Same configuration as the setting No.1

SD1280 to SD1287

Data logging setting No.8

Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SD1210 to SD1217). Same configuration as the setting No.1

SD1290 to SD1297

Data logging setting No.9

Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SD1210 to SD1217). Same configuration as the setting No.1

SD1300 to SD1307

Data logging setting No.10

Same configuration as the setting No.1

Data configuration is the same as the setting No.1 (SD1210 to SD1217). Same configuration as the setting No.1

No. Name Data stored Details Set by (setting timing)

APPX Appendix 5 List of Special Register Areas 627

62

CPU module data backup/restoration function The following is the list of special register areas relating to the CPU module data backup/restoration function. (The R00CPU, R01CPU, and R02CPU do not support the use of these functions.)

*1 When program files are restored, the progress in SD1351 stops while data is being written (transferred) to the program memory in the restoration processing because the data is transferred from the program cache memory to the program memory. The progress of data transfer to the program memory can be checked in SD629.

Data backup/restoration function of iQ Sensor Solution The following is the list of special register areas relating to the data backup/restoration function of iQ Sensor Solution. (The R00CPU does not support the use of these functions.)

No. Name Data stored Details Set by (setting timing)

SD1350 Number of uncompleted folders/ files of CPU module data backup/ restoration

Number of uncompleted folders/files of CPU module data backup/ restoration

This register indicates the number of folders/files where the backup/ restoration of the CPU module is not completed. When the backup/ restoration processing is started, the total number of folders and files to be backed up or restored is stored. The number is reduced one each time one folder/file is backed up or restored, and 0 is stored when all the data is backed up or restored.

S (Status change)

SD1351 Progression status of CPU module data backup/restoration

Progression status of CPU module data backup/ restoration

This register indicates the progression status of the backup or restoration in percentage.*1

Range of the value: 0 to 100 (%) "0" is set at the start of the CPU module data backup.

S (Status change)

SD1353 Upper limit value setting for the number of CPU module backup data

Setting of the upper limit value for the number of CPU module backup data

Set the upper limit value for the number of the backup data for the CPU module data backup. (1 to 100)

U

No. Name Data stored Details Set by (setting timing)

SD1360 Right-to-use request number for iQ Sensor Solution data backup/restoration

Right-to-use request number for data backup/ restoration

Set the request number (desired 4-digit number) to acquire/release the right to use. Use the request number as follows depending on the request source. 0000H: Right-to-use release request 1000H to 1FFFH: Request from the program D000H to DFFFH: Request from MELSOFT Navigator E000H to EFFFH: Request from GOT F000H to FFFFH: Request from GX Works3

U

SD1361 Right-to-use acquisition number for iQ Sensor Solution data backup/restoration

Right-to-use acquisition number for data backup/ restoration

This register stores the request number of when the right to use for the iQ Sensor Solution data backup/ restoration has been acquired. (0000H is stored when the right to use is not acquired or has been released)

S (Status change)

SD1362 Target module/ execution unit setting for iQ Sensor Solution data backup/restoration

Target module/execution unit setting for data backup/restoration

Set the target module and execution unit of the iQ Sensor Solution data backup/restoration. Lower 8 bits (target module)

1H: AnyWireASLINK 2H: CC-Link 3H: Ethernet 4H: CC-Link IE Field Network Upper 8 bits (execution unit)

1H: In module units 2H: In ID units 1H: In module units 2H: In station units 3H: In station sub ID units 1H: In module units 2H: In IP address units

U

8 APPX Appendix 5 List of Special Register Areas

A

SD1363 Target folder number setting for iQ Sensor Solution data backup/restoration

Target folder number setting for data backup/ restoration

Set a number of folder in which the backup data is to be stored or a folder in which the data to be restored is stored. 00 to 99: Target folder specification FFFEH: Automatic specification (Folder deletion supported) FFFFH (default): Automatic specification

U

SD1364 Target setting for iQ Sensor Solution data backup/restoration (target module)

Target setting for data backup/restoration (target module)

Set the target module of the iQ Sensor Solution data backup/restoration. I/O number.*1: Module 3FFH: Built-in Ethernet*2

U

SD1365 Target setting for iQ Sensor Solution data backup/restoration (target device 1)

Target setting for data backup/restoration (target device 1)

Set the target device of the iQ Sensor Solution data backup/restoration. ID number Station number IP address (lower 16 bits) Example: When the IP address is 192.168.3.40 (expressed in dotted decimal notation*3), 3 = 3H and 40 = 28H. Therefore, the value of the lower 16 bits (0328H) is 808.

U

SD1366 Target setting for iQ Sensor Solution data backup/restoration (target device 2)

Target setting for data backup/restoration (target device 2)

Set the target device of the iQ Sensor Solution data backup/restoration. 0 (Not used) Station sub-ID number IP address (upper 16 bits) Example: When the IP address is 192.168.3.40 (expressed in dotted decimal notation*3), 192 = C0H and 168 = A8H. Therefore, the value of the upper 16 bits (C0A8H) is 49320.

U

SD1367 Operation setting for iQ Sensor Solution data backup/ restoration

Operation setting for data backup/restoration

Set the operation of the iQ Sensor Solution data backup/restoration.

b0 to b7: Operation setting at error occurrence (0: Continue, 1: Stop) b8 to b15: Fixed to 0

U

SD1368 Communication timeout time of iQ Sensor Solution data backup/restoration

Communication timeout time of data backup/ restoration

Specify the communication timeout time of the iQ Sensor Solution data backup/restoration in increments of 100ms. 0: 600000ms (default) 1 to 65535 (100ms): 100 to 6553500ms

U

SD1371 Execution status of iQ Sensor Solution data backup/ restoration (total number of target devices)

Execution status of data backup/restoration (total number of target devices)

This register stores the total number of target devices of the data backup/restoration of iQ Sensor Solution for each execution unit.

This register is cleared to 0 when the right to use is acquired or the backup/restoration is requested.

S (Status change)

SD1372 Execution status of iQ Sensor Solution data backup/ restoration (normal completion count)

Execution status of data backup/restoration (normal completion count)

This register indicates the execution status (the number of devices where the processing has been completed normally) of the iQ Sensor Solution data backup/restoration.

Among the devices where the operation has been completed, the number of devices where the operation has been completed normally is stored.

This register is cleared to 0 when the right to use is acquired or the backup/restoration is requested.

S (Status change)

SD1373 Execution status of iQ Sensor Solution data backup/ restoration (error completion count)

Execution status of data backup/restoration (error completion count)

This register indicates the execution status (the number of devices where the processing has been completed with an error) of the iQ Sensor Solution data backup/restoration.

Among the devices where the operation has been completed, the number of devices where the operation has been completed with an error is stored.

This register is cleared to 0 when the right to use is acquired or the backup/restoration is requested.

S (Status change)

No. Name Data stored Details Set by (setting timing)

b15 b7b8 b0

APPX Appendix 5 List of Special Register Areas 629

63

SD1374 Execution status of iQ Sensor Solution data backup/ restoration (progress per device)

Execution status of data backup/restoration (progress per device)

This register indicates the progression status of the iQ Sensor Solution data backup/restoration of the device in progress in percentage (0 to 100%).

Range of the value: 0 to 100 (%) This register is cleared to 0 when the right to use is acquired or the

backup/restoration is requested.

S (Status change)

SD1375 Folder number of iQ Sensor Solution data backup

Backup target folder number

This register stores a number of the target folder where the backup data of the device supporting iQSS is stored.

0 to 99: Folder number FFFFH: Backup data not saved This register stores FFFFH when the right to use is acquired or the

backup/restoration is requested.

S (Status change)

SD1376 Module error cause of iQ Sensor Solution data backup/ restoration

Module error cause of data backup/restoration

This register stores the error cause that is detected in the module during the iQ Sensor Solution data backup/restoration. When errors are detected in multiple devices, the error detected first is stored. (For details on the error cause stored, refer to the manual for the CPU module used or the target device.)

This register is cleared to 0 when the right to use is acquired or the backup/restoration is requested.

S (Status change/Error)

SD1377 Target device error cause of iQ Sensor Solution data backup/restoration

Target device error cause of data backup/restoration

This register stores the error cause that is detected in the target device during the iQ Sensor Solution data backup/restoration. When errors are detected in multiple devices, the error detected first is stored. (For details on the error cause stored, refer to the manual for the target device.)

This register is cleared to 0 when the right to use is acquired or the backup/restoration is requested.

S (Status change/Error)

SD1378 Module information/ execution unit information of iQ Sensor Solution data backup/restoration error

Module information/ execution unit information of an error

At an occurrence of the iQ Sensor Solution data backup/restoration error, this register stores the information of the module where the error has been occurred and the execution unit information. When errors are detected in multiple devices, the information of a device where the error detected first is stored.

Lower 8 bits (target module) 1H: AnyWireASLINK 2H: CC-Link 3H: Ethernet 4H: CC-Link IE Field Network Upper 8 bits (execution unit)

1H: In module units 2H: In ID units 1H: In module units 2H: In station units 3H: In station sub ID units 1H: In module units 2H: In IP address units This register is cleared to 0 when the right to use is acquired or the

backup/restoration is requested.

S (Status change/Error)

SD1379 Folder number information of iQ Sensor Solution data backup/restoration error

Folder number information of an error

At an occurrence of the iQ Sensor Solution data backup/restoration error, this register stores the folder number (0 to 99) of the backup/ restoration target. If the folder number cannot be specified or a backup error is detected before creating a backup folder (I/O number_station number), FFFFH is stored.

This register is cleared to 0 when the right to use is acquired or the backup/restoration is requested.

S (Status change/Error)

SD1380 Details on iQ Sensor Solution data backup/restoration error (module)

Information of the module where an error has occurred

This register stores the information of a module where an error of the iQ Sensor Solution data backup/restoration has been occurred. When errors are detected in multiple modules, the information of a module where the error detected first is stored.

I/O number.*1: Module 3FFH: Built-in Ethernet*2

This register is cleared to 0 when the right to use is acquired or the backup/restoration is requested.

S (Status change/Error)

No. Name Data stored Details Set by (setting timing)

0 APPX Appendix 5 List of Special Register Areas

A

*1 The start I/O number (first three digits in four-digit hexadecimal representation) of each module *2 The built-in Ethernet port for the RnENCPU *3 A 32-bit IP address is expressed by converting it into decimal numbers in units of eight bits and separating each with a dot.

SD1381 Details on iQ Sensor Solution data backup/restoration error (device 1)

Information of the device (device 1) where an error has occurred

This register stores the information of a device (device 1) where an error of the iQ Sensor Solution data backup/restoration has been occurred. When errors are detected in multiple devices, the information of a device (device 1) where the error detected first is stored.

ID number Station number IP address (lower 16 bits) Example: When the IP address is 192.168.3.40 (expressed in dotted decimal notation*3), 3 = 3H and 40 = 28H. Therefore, the value of the lower 16 bits (0328H) is 808. This register is cleared to 0 when the right to use is acquired or the

backup/restoration is requested.

S (Status change/Error)

SD1382 Details on iQ Sensor Solution data backup/restoration error (device 2)

Information of the device (device 2) where an error has occurred

This register stores the information of a device (device 2) where an error of the iQ Sensor Solution data backup/restoration has been occurred. When errors are detected in multiple devices, the information of a device (device 2) where the error detected first is stored.

0 (Not used) Station sub-ID number IP address (upper 16 bits) Example: When the IP address is 192.168.3.40 (expressed in dotted decimal notation*3), 192 = C0H and 168 = A8H. Therefore, the value of the upper 16 bits (C0A8H) is 49320. This register is cleared to 0 when the right to use is acquired or the

backup/restoration is requested.

S (Status change/Error)

No. Name Data stored Details Set by (setting timing)

APPX Appendix 5 List of Special Register Areas 631

63

Interrupt pointer mask pattern The following is the list of special register areas relating to the mask pattern for interrupt pointers.

Event history function The following is the list of special relay areas relating to the event history function. (The CPU module where this function can be used supports these special register areas. Page 182 Event history logging restriction)

No. Name Data stored Details Set by (setting timing)

SD1400 to SD1463

Interrupt pointer mask pattern

Mask pattern The mask pattern for interrupt pointers is stored as shown in the following figure:

S (at execution)

No. Name Data stored Details Set by (setting timing)

SD1464 to SD1467

Module information on event history logging restriction

Module information on event history logging restriction

Modules on which event history logging is restricted are stored in the following bit patterns. (Off: No event history logging restricted, On: Event history logging restricted)

b0: Slot No.0 b1: Slot No.1

b15: Slot No.15

b0: Slot No.16 b1: Slot No.17

b15: Slot No.31

b0: Slot No.32 b1: Slot No.33

b15: Slot No.47

b0: Slot No.48 b1: Slot No.49

b15: Slot No.64 The bits corresponding to the slots in which the target modules are mounted turn on. The bits remain on even after the event history logging restriction is lifted.

S (Status change)

b15 b1 b0 SD1400 I15 I1 I0 SD1401 I31 I17 I16

SD1463 I1023 I1009 I1008

to to

to

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

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

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

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

2 APPX Appendix 5 List of Special Register Areas

A

Memory dump function The following is the special register area relating to the memory dump function. (The R00CPU does not support the use of these functions.)

Real-time monitor function The following is the special register area relating to the real-time monitor function. (The CPU module where each function can be used supports these special register areas. Page 700 Added and Enhanced Functions)

Debug function The following is the special register area relating to the debug function.

*1 The CPU module where this function can be used supports these special register areas. ( Page 700 Added and Enhanced Functions)

No. Name Data stored Details Set by (setting timing)

SD1472 Memory dump error cause

Memory dump error cause The cause of the error occurred during the memory dump function is stored. 0: No error Other than 0:For details on the values stored when an error occurs, refer

to the list of error codes. ( Page 502 List of Error Codes)

S (Error)

No. Name Data stored Details Set by (setting timing)

SD1484 Real-time monitor internal buffer free space

Free space size of the internal buffer (K bytes)

The amount of free space of the internal buffer is stored in K bytes. The smaller the value, the higher the generating ratio of processing overflow.

S (Status change)

No. Name Data stored Details Set by (setting timing)

SD1488 Debug function usage status

Debug function usage status

The usage status of the debug function is stored using the following bit pattern.

b0: External input/output forced on/off*1

Off: Not used On: In use

b1: Program restoration information write status*1

Off: All written On: Not all written When SM386 is on (without LED flashing), this bit does not turn on.

b2: Registration status of the device test with execution conditions*1

Off: Not registered On: Registered

b3 to b15: Empty (fixed to 0)

S (Status change)

b1b2 b0

APPX Appendix 5 List of Special Register Areas 633

63

CPU module database access function The following is the special register area relating to the CPU module database access function. (The R00CPU, R01CPU, and R02CPU do not support the use of these functions.)

No. Name Data stored Details Set by (setting timing)

SD1498 Start-up status of CPU module database

Start-up status of CPU module database

When the CPU module database access function is enabled with the module parameter, the CPU module database start-up status is stored. 0:No error FFFFH: Starting-up Other than above: Start-up error For the stored value at the start-up error, refer to the list of error codes that occur when a database access instruction is executed. ( MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks))

S (Status change)

4 APPX Appendix 5 List of Special Register Areas

A

Ethernet function The following is the list of special register areas relating to the Ethernet function.

No. Name Data stored Details Set by (setting timing)

SD1504 Open completion signal

In this register, open completion status is stored.

Open statuses of connection No.1 to 16 are stored. (0: Close/Open not completed, 1: Open completed).

b0: Connection 1 b1: Connection 2 b2 to b15: Connection 3 to 16 For details on the on/off timing, refer to the following. ( MELSEC iQ-R Ethernet User's Manual (Application))

S (Status change)

SD1505 Open request signal In this register, open request status is stored.

Open processing statuses of connection No.1 to 16 are stored. (0: No open request, 1: Open request exists).

b0: Connection 1 b1: Connection 2 b2 to b15: Connection 3 to 16 For details on the on/off timing, refer to the following. ( MELSEC iQ-R Ethernet User's Manual (Application))

S (Status change)

SD1506 Socket communications receive status signal

In this register, receive status is stored.

Receiving statuses of connections No.1 to 16 are stored. (0: No data received, 1: Data receiving completed)

b0: Connection 1 b1: Connection 2 b2 to b15: Connection 3 to 16 For details on the on/off timing, refer to the following. ( MELSEC iQ-R Ethernet User's Manual (Application))

S (Status change)

SD1512 *2

FTP server function file path name switching setting

The detailed of the file path name switching setting of the FTP server function is stored.

The setting details of the file path name switching settings in the FTP server function by executing SM1512 is stored according to the following bit pattern.

b0 (1): The directory delimiter of a file path name is set to "/". This delimiter is used for Linux computers. (0: Delimiter "/") b1 (2): The drive number in a file path name is omitted. (0: Not omitted, 1: Omitted) b2 to b3: Empty (fixed to 0) b4 to b7 (3): The target drive number is set when the drive number of the file path name is omitted. (2: SD memory card, 3: Device/label memory, 4: Data memory) When b1 sets to 1, settings in b4 to b7 are enabled. At omitted the drive number, when the CPU module receives a command which is specified the drive number to a file path name received from FTP client, the drive number specified by executing the command is prioritized. b8 to b15: Empty (fixed to 0)

U

SD1513 *2

FTP server function file path name switching setting error cause

An error cause of the file path name switching setting of the FTP server function is stored.

The error cause of the FTP server function file path name switching setting by executing SM1512 is stored. 0H: No error 100H: SD1512 (FTP server function file path name switching setting) is out of the specified range When the FTP command (quote path-delimiter) switching setting is enabled or the switching setting is off, the value is 0H.

S (Status change)

SD1504

b15 b12 b11 b8 b7 b4 b3 b0to to to to

SD1505

b15 b12 b11 b8 b7 b4 b3 b0to to to to

SD1506

b15 b12 b11 b8b7 b4 b3 b0to to to to

b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0 0 0 0 0 0 0 0 0 0 0 (2) (1)(3)

APPX Appendix 5 List of Special Register Areas 635

63

SD1514 *2

FTP server function file path name switching setting status

The current setting value of the file path name switching setting of the FTP server function is stored.

The current setting value in SD1512 (FTP server function file path name switching setting) is stored. (This value is also stored when the switching setting is set with the FTP command (quote path-delimiter)).

b0 (1): The directory delimiter of the file path name (0: quote path- delimiter) b1 (2): the drive number of the file path name is omitted. (0: Not omitted, 1: Omitted) b4 to b7 (3): The target drive number is set when the drive number of the file path name is omitted. (2: SD memory card, 3: Device/label memory, 4: Data memory) When SM1512 is turned on and off or the switching setting is off by executing the FTP command (quote path-delimiter off), the value is 0H.

S (Status change)

SD1518 *2

IP address setting Network number Set the network number to be stored in the IP address storage area (system memory*1).

Upon completion of writing or clearing the IP address to/from the IP address storage area (system memory*1), the value of the network number stored in the IP address storage area (system memory*1) is stored.

S (Status change)/U

SD1519 *2

Station number Set the station number to be stored in the IP address storage area (system memory*1).

Upon completion of writing or clearing the IP address to/from the IP address storage area (system memory*1), the value of the station number stored in the IP address storage area (system memory*1) is stored.

S (Status change)/U

SD1520 IP Address (lower) Specify the IP address to be stored into the IP address storage area (system memory*1). Range: 00000001H to DFFFFFFEH (0.0.0.1 to 223.255.255.254)

Upon completion of writing or clearing the IP address to/from the IP address storage area (system memory*1), the value of IP address stored in the IP address storage area (system memory*1) is stored.

1 to 4: First to fourth byte

S (Status change)/USD1521 IP Address (upper)

SD1522 Subnet mask pattern (lower)

Specify the Subnet mask pattern to be stored into the IP address storage area (system memory*1). Setting range: C0000000H to FFFFFFFCH (192.0.0.0 to 255.255.255.252), 00000000H (no setting)

Upon completion of writing or clearing the IP address to/from the IP address storage area (system memory*1), the value of subnet mask pattern stored in the IP address storage area (system memory*1) is stored.

1 to 4: First to fourth byte

S (Status change)/U

SD1523 Subnet mask pattern (upper)

SD1524 Default gateway IP address (lower)

Specify the default gateway IP address to be stored into the IP address storage area (system memory*1). Setting range: 00000001H to DFFFFFFEH (0.0.0.1 to 223.255.255.254), 00000000H (no setting)

Upon completion of writing or clearing the IP address to/from the IP address storage area (system memory*1), the value of default gateway IP address stored in the IP address storage area (system memory*1) is stored.

1 to 4: First to fourth byte

S (Status change)/U

SD1525 Default gateway IP address (upper)

No. Name Data stored Details Set by (setting timing)

b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0 0 0 0 0 0 0 0 0 0 0 (2) (1)(3)

SD1520 SD1521

3

1

4

2

b15 to b8 b7 to b0

SD1522 SD1523

3

1

4

2

b15 to b8 b7 to b0

SD1524 SD1525

3

1

4

2

b15 to b8 b7 to b0

6 APPX Appendix 5 List of Special Register Areas

A

*1 This is the memory used by the system when the CPU module is executing functions. *2 The CPU module where this function can be used supports these special register areas. ( MELSEC iQ-R Ethernet User's Manual

(Application))

SD1526 IP address storage area writing error cause

The error cause for the case when failing in writing into IP address storage area is stored.

The error cause generated when writing into IP address storage area (system memory*1) will be stored. (Linked with SM1521) 0H: No error 100H:SD1520 to SD1525 are out of the specified range. 200H:Write error 400H:Impossible to execute the write processing because clear

processing is in progress.

S (Status change)

SD1527 IP address storage area clearing error cause

The cause of the error for the case when failing in clearing IP address storage area is stored.

The cause of the error generated during writing into IP address storage area (system memory*1) is stored. (Linked with SM1523) 0H: No error 200H:Clear error 400H:Impossible to execute the clear processing because write

processing is in progress.

S (Status change)

No. Name Data stored Details Set by (setting timing)

APPX Appendix 5 List of Special Register Areas 637

63

CC-Link IE Field Network Basic function The following is the list of special register areas relating to the CC-Link IE Field Network Basic function. (The CPU module where this function can be used supports these special register areas. Page 700 Added and Enhanced Functions)

*1 This status includes the case where a slave station has not responded to the first request from the master station due to a power-off of the slave station. (The slave station is not judged as a faulty station because the data link status is not determined.)

No. Name Data stored Details Set by (setting timing)

SD1536 to SD1539

Cyclic transmission status of each station

Cyclic transmission status of each station

The cyclic transmission status of each station is stored using the following bit pattern. (Off: Not performed, On: Being performed)

The numbers in the figure indicate station numbers. (Condition) Only the bit of the start station number turns on. The status is not stored for the reserved stations and the station

numbers after the maximum station number. Use this register as an interlock for cyclic transmission. For details on the interlock program, refer to the following. CC-Link IE Field Network Basic Reference Manual

S (Every END)

SD1540 to SD1543

Data link status of each station

Data link status of each station

The data link status of each station is stored using the following bit pattern. (Off: Normally operating station*1, On: Faulty station)

The numbers in the figure indicate station numbers. (Condition) Only the bit of the start station number turns on. The status is not stored for the reserved stations and the station

numbers after the maximum station number. This register can be used to monitor errors in slave stations, connected cables, and a connected hub.

S (Every END)

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17

48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33

64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49

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

SD1537

SD1538

SD1539

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17

48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33

64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49

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

SD1541

SD1542

SD1543

8 APPX Appendix 5 List of Special Register Areas

A

System monitoring information The following is the list of special register areas relating to the system monitoring information. (There are restrictions on the firmware version of the supported CPU module. Page 700 Added and Enhanced Functions)

These special register areas can be written only by the system. The stored values, however, can be read by monitoring systems or SLMP-compatible devices. When reading a value using SLMP commands, use the following commands: 0401 (Read), 0403 (Read Random), and 0406 (Read Block). Do not use subcommands 008 (Read by device extension specification). Also, do not use the following to read the stored values (if used, "-1" is read): Programs, the circuit monitor function, or the watch function Index modification, indirect specification, or bit number specification

No. Name Data stored Details Set by (setting timing)

SD2000 Firmware version (monitor)

Firmware version This register reads the firmware version. S (Initial)

SD2001 to SD2008

Production information (monitor)

Production information This register reads the production information.

Example: The production information is 123456789ABCDEFG.

S (Initial)

SD2009 IP address (monitor) IP address (lower) This register reads the IP address of the built-in Ethernet port which is set with parameters or the IP address change function.

Example: The IP address is 192.168.3.40 (C0A80328H).

S (Initial)

SD2010 IP address (upper)

SD2011 Subnet mask pattern (monitor)

Subnet mask pattern (lower)

This register reads the subnet mask pattern of the built-in Ethernet port which is set with parameters or the IP address change function.

Example: The subnet mask pattern is 255.255.255.0 (FFFFFF00H).

S (Initial)

SD2012 Subnet mask pattern (upper)

SD2001 SD2002

SD2008

b15 b8b7 b0

2nd digit from the left

1st digit from the left

4th digit from the left

3rd digit from the left

16th digit from the left

15th digit from the left

32H (2) 31H (1)

34H (4) 33H (3)

47H (G) 46H (F)

b15 b8b7 b0

SD2001

SD2002

SD2008

SD2009 SD2010

b15 b8b7 b0

3rd byte 4th byte 1st byte 2nd byte

03H (3) 28H (40)

C0H (192) A8H (168)

b15 b8b7 b0

SD2009

SD2010

SD2011 SD2012

b15 b8b7 b0

3rd byte 4th byte 1st byte 2nd byte

FFH (255) 00H (0)

FFH (255) FFH (255)

b15 b8b7 b0

SD2011

SD2012

APPX Appendix 5 List of Special Register Areas 639

64

SD2013 Default gateway IP address (monitor)

Default gateway IP address (lower)

This register reads the default gateway IP address of the built-in Ethernet port which is set with parameters or the IP address change function.

Example: The default gateway IP address is 192.168.3.254 (C0A803FEH).

S (Initial)

SD2014 Default gateway IP address (upper)

SD2015 MAC address (monitor)

MAC address (5th octet and 6th octet)

This register reads the MAC address.

Example: The MAC address is 123456789ABC.

S (Initial)

SD2016 MAC address (3rd octet and 4th octet)

SD2017 MAC address (1st octet and 2nd octet)

SD2018 Network number (monitor)

Network number This register reads the network number of the built-in Ethernet port which is set with parameters or the IP address change function. 0: Not set 1 to 239: Network number

S (Initial)

SD2019 Station number (monitor)

Station number This register reads the station number of the built-in Ethernet port which is set with parameters or the IP address change function. 0: Not set 1 to 120: Station number

S (Initial)

SD2020 Firmware hash value (monitor)

Firmware hash value (3rd and 4th bytes)

This register reads the firmware hash value.

Example: The firmware hash value is 12345678H.

S (Status change)

SD2021 Firmware hash value (1st and 2nd bytes)

S (Status change)

SD2022 Parameter file(s) hash value (monitor)

Parameter file(s) hash value (3rd and 4th bytes)

This register reads the parameter file(s) hash value calculated from the following files: System parameter file CPU parameter file Module parameter file

Example: The parameter file(s) hash value is 12345678H.

S (Status change)

SD2023 Parameter file(s) hash value (1st and 2nd bytes)

S (Status change)

No. Name Data stored Details Set by (setting timing)

SD2013 SD2014

b15 b8b7 b0

3rd byte 4th byte 1st byte 2nd byte

03H (3) FEH (254)

C0H (192) A8H (168)

b15 b8b7 b0

SD2013

SD2014

SD2015 SD2016

b15 b8b7 b0

SD2017

5th octet 6th octet 3rd octet 4th octet

1st octet 2nd octet

SD2015 SD2016

b15 b8b7 b0

SD2017

9AH BCH 56H 78H

12H 34H

SD2020 SD2021

b15 b8b7 b0

3rd byte 4th byte 1st byte 2nd byte

56H 78H

12H 34H

b15 b8b7 b0

SD2020

SD2021

SD2022 SD2023

b15 b8b7 b0

3rd byte 4th byte 1st byte 2nd byte

56H 78H

12H 34H

b15 b8b7 b0

SD2022

SD2023

0 APPX Appendix 5 List of Special Register Areas

A

SD2024 Program file(s) and global label setting file hash value (monitor)

Program file(s) and global label setting file hash value (3rd and 4th bytes)

This register reads the parameter file(s) hash value calculated from the following files: Program files (All the files set in the program settings of the CPU

parameter) FB files (All the files set in the FB/FUN file settings of the CPU

parameter) Global label setting file

Example: The program file(s) and global label setting file hash value is 12345678.

S (Status change)

SD2025 Program file(s) and global label setting file hash value (1st and 2nd bytes)

S (Status change)

SD2026 CPU operating status (monitor)

Operating status of the CPU module

This register reads the operating status of the CPU module. 0: RUN 2: STOP 3: PAUSE

S (Status change)

SD2027 Initial scan time (monitor)

Initial scan time (unit: ms) This register reads the initial scan time. SD2027: The number of ms is read. (Range: 0 to 65535) SD2028: The number of s is read. (Range: 0 to 999)

These areas are cleared to 0 when the operating status of the CPU module is switched from STOP to RUN.

S (Status change)

SD2028 Initial scan time (unit: s) S (Status change)

SD2029 Current scan time (monitor)

Current scan time (unit: ms)

This register reads the current scan time. SD2029: The number of ms is read. (Range: 0 to 65535) SD2030: The number of s is read. (Range: 0 to 999)

Example: If the current scan time is 23.6ms, the following values are read: SD2029 = 23 SD2030 = 600

These areas are cleared to 0 when the operating status of the CPU module is switched from STOP to RUN.

S (Status change)

SD2030 Current scan time (unit: s)

S (Status change)

SD2031 Minimum scan time (monitor)

Minimum scan time (unit: ms)

The minimum value of the scan times except the scan time of the initial execution program is read.

SD2031: The number of ms is read. (Range: 0 to 65535) SD2032: The number of s is read. (Range: 0 to 999)

These areas are cleared to 0 when the operating status of the CPU module is switched from STOP to RUN.

S (Status change)

SD2032 Minimum scan time (unit: s)

S (Status change)

SD2033 Maximum scan time (monitor)

Maximum scan time (unit: ms)

The maximum value of the scan times except the scan time of the initial execution program is read.

SD2033: The number of ms is read. (Range: 0 to 65535) SD2034: The number of s is read. (Range: 0 to 999)

These areas are cleared to 0 when the operating status of the CPU module is switched from STOP to RUN.

S (Status change)

SD2034 Maximum scan time (unit: s)

S (Status change)

SD2035 Scan program execution time (monitor)

Scan program execution time (unit: ms)

The execution time of the scan program in a scan is read. SD2035: The number of ms is read. (Range: 0 to 65535) SD2036: The number of s is read. (Range: 0 to 999)

These areas are cleared to 0 when the operating status of the CPU module is switched from STOP to RUN.

S (Status change)

SD2036 Scan program execution time (unit: s)

S (Status change)

No. Name Data stored Details Set by (setting timing)

SD2024 SD2025

b15 b8b7 b0

3rd byte 4th byte 1st byte 2nd byte

56H 78H

12H 34H

b15 b8b7 b0

SD2024

SD2025

APPX Appendix 5 List of Special Register Areas 641

64

Appendix 6 Buffer Memory The buffer memory is memory used with the following applications.

The buffer memory content returns to its default status (initial value) when the CPU module is powered off or is reset.

List of buffer memory addresses

CPU module The following table lists the CPU module buffer memory addresses.

Ethernet function For a list of buffer memory addresses as well as details relating to the Ethernet function, refer to the following. ( MELSEC iQ-R Ethernet User's Manual (Application))

CC-Link IE Field Network Basic function The following table lists buffer memory addresses relating to the CC-Link IE Field Network Basic function. ( Page 643 Details on buffer memory addresses)

Module Application CPU module Stores values such as Ethernet function setting values.

Address Name Data stored Un\G1024 Total number of connected stations The total number of connected stations set in parameter is stored.

Un\G1025 Reserved station specification status The reserved station specification status of the slave station specified in parameter is stored.

Un\G1026 to Un\G1029

Reserved station specification status of each station

The reserved station specification status is stored.

Un\G1030 to Un\G1032, Un\G1034 to Un\G1036, Un\G1038 to Un\G1040, Un\G1042 to Un\G1044

Link scan information The link scan time during cyclic transmission is stored.

Un\G1050 Diagnostic information display request When a station number (1 to 16) to be diagnosed is specified in 'Diagnostic request information' (Un\G1051) and the bit 0 of 'Diagnostic information display request' (Un\G1050) is turned off and on, the diagnostic information of the specified slave station is stored in 'Diagnostic information 1' (Un\G1053 to Un\G1064) and 'Diagnostic information 2' (Un\G1068 to Un\G1077).

Un\G1051 Diagnostic request information

Un\G1052 Diagnostic information status flag

Un\G1053 to Un\G1064

Diagnostic information 1

Un\G1068 to Un\G1077

Diagnostic information 2

2 APPX Appendix 6 Buffer Memory

A

Details on buffer memory addresses The following table lists items in the list.

Do not change the data set by the system in a program or by a device test. Doing so may cause an unintended operation.

Item Description Address Buffer memory address of the CPU module

Name Buffer memory name of the CPU module

Data stored Data stored in the CPU module buffer memory and its meaning

Details Detailed description of the data stored

Set by (setting timing) Set side of data (system or user) and timing when data is set by the system S: System U: User (program, engineering tool, GOT, or other testing operations from external device) U/S: User and system

Every END: Data is set every time END processing is performed. Initial: Data is set when initial processing is performed (e.g. powering on the system, changing the operating status from

STOP to RUN). Status change: Data is set when the status is changed. Error: Data is set when an error occurs. Instruction execution: Data is set when an instruction is executed. Request: Data is set when requested by a user (using the special relay). Switch change: Data is set when the switch of the CPU module is changed. Card insertion/removal: Data is set when an SD memory card is inserted or removed. Writing: Data is set when a user performs a writing operation. During END: Data is set when END processing is performed.

APPX Appendix 6 Buffer Memory 643

64

CC-Link IE Field Network Basic function The following table lists buffer memory areas of the CPU module relating to the CC-Link IE Field Network Basic function.

Address Name Data stored Details Set by (setting timing)

Un\G1024 Total number of connected stations

Total number of connected stations

The total number of connected stations set in parameter is stored. Range: 1 to 16

S (Initial)

Un\G1025 Reserved station specification status

Reserved station specification status

The reserved station specification status of the slave station specified in parameter is stored. (0: Not specified, 1: Specified)

b0: Reserved station specification status b1 to b15: Empty (fixed to 0) The station number that is specified as a reserved station can be checked in 'Reserved station specification status of each station' (Un\G1026).

S (Initial)

Un\G1026 to Un\G1029

Reserved station specification status of each station

Reserved station specification status of each station

The reserved station specification status is stored using the following bit pattern. (Off: Other than the reserved station, On: Reserved station)

The numbers in the figure indicate station numbers. (Condition) Only the bit of the start station number turns on. The status is not stored for the station numbers after the maximum

station number.

S (Initial)

Un\G1030 Link scan information Group No.1 maximum link scan

The maximum link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1031 Group No.1 minimum link scan

The minimum link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1032 Group No.1 current link scan

The current link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1034 Group No.2 maximum link scan

The maximum link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1035 Group No.2 minimum link scan

The minimum link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1036 Group No.2 current link scan

The current link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1038 Group No.3 maximum link scan

The maximum link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1039 Group No.3 minimum link scan

The minimum link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1040 Group No.3 current link scan

The current link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1042 Group No.4 maximum link scan

The maximum link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1043 Group No.4 minimum link scan

The minimum link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1044 Group No.4 current link scan

The current link scan time value during cyclic transmission is stored. (Unit: ms)

S (Status change)

Un\G1050 Diagnostic information display request

Diagnostic information display request

After the END instruction of the scan where the bit 0 is turned off and on is executed, the diagnostic information of a slave station specified in 'Diagnostic request information' (Un\G1051) is read to Un\G1052 to Un\G1077. When reading of the diagnostic information has completed at END processing, 0 is stored.

b0: Diagnostic information display request b1 to b15: Empty (fixed to 0)

S (Status change)*1/U

b0

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17

48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33

64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49

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

Un\G1027

Un\G1028

Un\G1029

b0

4 APPX Appendix 6 Buffer Memory

A

Un\G1051 Diagnostic request information

Diagnostic request information

Specify a slave station number whose diagnostic information is to be displayed. Range: 1 to 64 For the programmable controller CPU with firmware version earlier

than "28", the range is from 1 to 16.

U

Un\G1052 Diagnostic information status flag

Diagnostic information status flag

After the END instruction of the scan where the bit 0 of 'Diagnostic information display request' (Un\G1050) is turned off and on is executed, the status (valid or invalid) of diagnostic information (Diagnostic information 1, Diagnostic information 2) of the slave station specified in 'Diagnostic request information' (Un\G1051) is stored. (Valid: 1, Invalid: 0)

b0 to b7: Diagnostic information 1 b8 to b15: Diagnostic information 2 If the station number of the slave station that is specified in

'Diagnostic request information' (Un\G1051) is the start station number of the occupied stations and the cyclic transmission is performed for the slave station, 1 is stored in b0 to b7 and b8 to b15. (If the specified slave station is a reserved station, 0 is stored in b8 to b15.)

If the station number of the slave station that is specified in 'Diagnostic request information' (Un\G1051) is other than the start station number of the occupied stations or the cyclic transmission is not performed for the slave station, 0 is stored in b0 to b7 and b8 to b15.

When b0 to b7 are valid, the number of occupied stations, group number, IP address, the accumulated number of timeouts, and the accumulated number of disconnection detection are stored in 'Diagnostic information 1' (Un\G1053 to Un\G1064). When invalid, 0 is stored in 'Diagnostic information 1' (Un\G1053 to Un\G1064).

When b8 to b15 are valid, the Manufacturer code, model code, device version, module information, error code, and detailed module information are stored in 'Diagnostic information 2' (Un\G1068 to Un\G1077). When invalid, 0 is stored in 'Diagnostic information 2' (Un\G1068 to Un\G1077).

S (Status change)

Address Name Data stored Details Set by (setting timing)

b15 b7b8 b0

APPX Appendix 6 Buffer Memory 645

64

*1 Data is stored at END processing where the value is changed. *2 When the count exceeds 65535, counting is continued from 1 again. *3 A slave station specified is being disconnected, the information immediately before the disconnection is stored.

Un\G1053 to Un\G1064

Diagnostic information 1*3 Diagnostic information 1 When 1 (valid) is stored in b0 to b7 of Un\G1052, the number of occupied stations, group number, IP address, the accumulated number of timeouts, and the accumulated number of disconnection detection are stored. When 0 (invalid) is stored in b0 to b7 of Un\G1052, 0 is stored. Un\G1053: Number of occupied stations Un\G1054: Group number Un\G1055: IP address (lower) Un\G1056: IP address (upper)

1 to 4: First octet to fourth octet When the IP address has not been set in the parameter, 0 is stored. Un\G1063: Accumulated number of timeouts After the END instruction of the scan where the bit 0 of 'Diagnostic information display request' (Un\G1050) is turned off and on is executed, the accumulated number of timeouts that occurred in a slave station specified in 'Diagnostic request information' (Un\G1051) is stored. 0: No timeouts 1 to 65535: Number of timeouts (accumulated number)*2

Un\G1064: Accumulated number of disconnection detection After the END instruction of the scan where the bit 0 of 'Diagnostic information display request' (Un\G1050) is turned off and on is executed, the accumulated number of disconnections that detected in a slave station specified in 'Diagnostic request information' (Un\G1051) is stored. 0: No disconnections 1 to 65535: Number of disconnection detection (accumulated

number)*2

S (Status change)

Un\G1068 to Un\G1077

Diagnostic information 2*3 Diagnostic information 2 When Diagnostic information 2 is valid (1 is stored in b8 to b15 of Un\G1052), the manufacturer code, model code, device version, module information, error code, and detailed module information are stored. When Diagnostic information 2 is invalid (0 is stored in b8 to b15 of Un\G1052), 0 is stored. Un\G1068: Manufacturer code Un\G1070: Model code (lower) Un\G1071: Model code (upper) Un\G1072: Device version Un\G1074: Module information Un\G1075: Error code Un\G1076: Detailed module information (lower) Un\G1077: Detailed module information (upper)

S (Status change)

Address Name Data stored Details Set by (setting timing)

3

1

4

2

b15 to b8 b7 to b0

Un\G1055 Un\G1056

6 APPX Appendix 6 Buffer Memory

A

Appendix 7 Processing Time The scan time of the CPU module is the sum of the instruction execution time, the program execution time, and the END processing time. Each of the processing time that constitutes the scan time is as follows.

For the availability of functions depending on the CPU module, refer to the description of each function.

Instruction execution time The instruction execution time is the total of each instruction processing time used for the program executed by the CPU module. For the processing time of each instruction, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

Program execution time The program execution time is the processing time when multiple programs are executed. When the interrupt program is executed, the overhead time during the interrupt program being executed is also included.

Processing time when multiple programs are executed (program switching time) When multiple programs are executed, the scan time becomes longer.

When multiple programs run The processing time [s] with multiple programs run is given by: the number of program files 1.2.

Overhead time at execution of interrupt/fixed scan execution type program This section describes each overhead time when each of the interrupt programs and fixed scan execution type programs is executed.

The processing time for the interrupt program and fixed scan execution type program is as shown below. Instruction processing time for each instruction + Overhead time + Each refresh processing time (when setting)

APPX Appendix 7 Processing Time 647

64

Overhead time when executing the interrupt program The overhead time when executing the interrupt program includes the one before executing the interrupt program and the other when the interrupt program finished. Overhead time before executing the interrupt program

Overhead time when finishing the interrupt program

Overhead time when executing the fixed scan execution type program The following table lists the overhead times when executing the fixed scan execution type program.

Interrupt factor Condition Overhead time Internal timer interrupt (I28 to I31) Saves/stores the file register (R) block number. 19.5s

Not save/store the file register (R) block number. 12.9s

Inter-module synchronous interrupt (I44) Saves/stores the file register (R) block number. 25.4s

Not save/store the file register (R) block number. 17.0s

Multiple CPU synchronous interrupt (I45) Saves/stores the file register (R) block number. 24.2s

Not save/store the file register (R) block number. 16.1s

High-speed internal timer interrupt 2 (I48), high-speed internal timer interrupt 1 (I49)

Saves/stores the file register (R) block number. 25.8s

Not save/store the file register (R) block number. 18.1s

Interrupt from module (I0 to I15, I50 to I1023) Saves/stores the file register (R) block number. 19.1s

Not save/store the file register (R) block number. 12.8s

Interrupt factor Condition Overhead time Internal timer interrupt (I28 to I31) Saves/stores the file register (R) block number. 16.0s

Not save/store the file register (R) block number. 8.5s

Inter-module synchronous interrupt (I44) Saves/stores the file register (R) block number. 19.0s

Not save/store the file register (R) block number. 11.4s

Multiple CPU synchronous interrupt (I45) Saves/stores the file register (R) block number. 18.7s

Not save/store the file register (R) block number. 10.5s

High-speed internal timer interrupt 2 (I48), high-speed internal timer interrupt 1 (I49)

Saves/stores the file register (R) block number. 19.4s

Not save/store the file register (R) block number. 10.3s

Interrupt from module (I0 to I15, I50 to I1023) Saves/stores the file register (R) block number. 15.7s

Not save/store the file register (R) block number. 8.5s

Condition Overhead time Saves/stores the file register (R) block number. 37.9s

Not save/store the file register (R) block number. 20.6s

8 APPX Appendix 7 Processing Time

A

END processing time The END processing time includes the following: Common processing time I/O refresh processing time Link refresh processing time for the network module Link refresh processing time for CC-Link IE Field Network Basic Intelligent function module refresh processing time Multiple CPU refresh processing time Prolonged time of END processing when executing each function Device/label access service processing time

Common processing time The common processing time by the system is 85s for one unit of CPU module (module is not mounted).

APPX Appendix 7 Processing Time 649

65

I/O refresh processing time The I/O refresh processing time for module mounted on main base unit and extension base unit can be calculated by the following formula. I/O refresh processing time [s] = ((Number of input refresh points*1 KM1) + (Number of unit having number of input points KM2) + KM3*3) + ((Number of output refresh points*2 KM4) + (Number of unit having number of output points KM5) + KM6*3) *1 The value indicates the numeric value that is obtained through dividing the number of input points by 16. *2 The value indicates the numeric value that is obtained through dividing the number of output points by 16. *3 When the number of I/O points is 0, this value is handled as 0.

Condition Constant value MELSEC iQ-R series module Main base unit Input KM1 0.04

KM2 0.56

KM3 11.2

Output KM4 0.02

KM5 0.94

KM6 6.30

Extension base unit Input KM1 0.04

KM2 0.56

KM3 11.2

Output KM4 0.02

KM5 0.94

KM6 6.30

Q series module RQ extension base unit Input KM1 1.15

KM2 1.33

KM3 24.0

Output KM4 0.03

KM5 1.20

KM6 6.21

Q series extension base unit Input KM1 1.85

KM2 1.98

KM3 39.4

Output KM4 0.02

KM5 1.29

KM6 6.01

0 APPX Appendix 7 Processing Time

A

Link refresh processing time for the network module This section describes the link refresh processing time for the network module.

Link refresh processing time for the CC-Link IE TSN master/local module The link refresh processing time between the CPU module and the CC-Link IE TSN master/local module on the main base unit or the extension base unit is calculated by the following formulas. T1, R1 [ms] = KM1 + KM2 ((RX + RY + SB) 16 + RWr + RWw + SW) + U T2, R2 [ms] = KM1 + KM2 (LB 16 + LW) U [ms] = KM3 (SBU 16 + SWU) T1: RX/RY/RWr/RWw/SB/SW link refresh time (sending side) T2: LB/LW link refresh time (sending side) R1: RX/RY/RWr/RWw/SB/SW link refresh time (receiving side) R2: LB/LW link refresh time (receiving side) U: Unit label (SB/SW) refresh time RX: Total number of points of remote input (RX) refreshed by the master station/local station*1

RY: Total number of points of remote output (RY) refreshed by the master station/local station*1

LB: Total number of points of link relay (LB) refreshed by the master station/local station station*1

RWw: Total number of points of remote register (RWw) refreshed by the master station/local station*1

RWr: Total number of points of remote register (RWr) refreshed by the master station/local station*1

LW: Total number of points of link register (LW) refreshed by the master station/local station station*1

SB: Number of points of link special relay (SB)*2

SW: Number of points of link special register (SW)*2

SBU: Number of points of link special relay (SB)*3

SWU: Number of points of link special register (SW)*3

*1 Total number of points here indicates the one of link devices that have been set in "Refresh Setting" and "Network Configuration Settings". The number of points that has been assigned in the reserved station is excluded in the link relay (LB) and the link register (LW).

*2 Number of points here indicates the one of when module label is not used. Calculation is executed while it is regarded as "0" when module label is used.

*3 Number of points here indicates the one of when module label is used. Calculation is executed while it is regarded as "0" when module label is not used.

*4 The base units here indicates the type of base unit where the network module targeted for refresh is mounted.

Condition Constant value KM1 (10-3) 40.00

KM2 (10-3) Main base unit*4 0.01

Extension base unit*4 0.12

KM3 (10-3) Main base unit*4 0.03

Extension base unit*4 0.15

APPX Appendix 7 Processing Time 651

65

Link refresh processing time for the CC-Link IE Controller Network module The link refresh processing time between the CPU module and the CC-Link IE Controller Network module on the main base unit or the extension base unit is calculated by the following formulas. T, R [ms] = KM1 + KM2 ((LB + LX + LY + SB) 16 + LW + SW) + U U [ms] = KM3 (SBU 16 + SWU) T: Link refresh time (sending side) R: Link refresh time (receiving side) U: Unit label (SB/SW) refresh time LB: Total number of points of link relay (LB) that is refreshed by the station*1

LW: Total number of points of link register (LW) that is refreshed by the station*1

LX: Total number of points of link input (LX) that is refreshed by the station*1

LY: Total number of points of link output (LY) that is refreshed by the station*1

SB: Number of points of link special relay (SB)*2

SW: Number of points of link special register (SW)*2

SBU: Number of points of link special relay (SB)*3

SWU: Number of points of link special register (SW)*3

*1 Total number of points here indicates the one of link devices that have been set in "Refresh Setting" and "Network Configuration Settings". Note that the number of points that has been assigned in the reserved station is excluded.

*2 Number of points here indicates the one of when module label is not used. Calculation is executed while it is regarded as "0" when module label is used.

*3 Number of points here indicates the one of when module label is used. Calculation is executed while it is regarded as "0" when module label is not used.

*4 The base units here indicates the type of base unit where the network module targeted for refresh is mounted.

Condition Constant value KM1 (10-3) 40.00

KM2 (10-3) Main base unit*4 0.01

Extension base unit*4 0.12

KM3 (10-3) Main base unit*4 0.03

Extension base unit*4 0.15

2 APPX Appendix 7 Processing Time

A

Link refresh processing time for the CC-Link IE Field Network module The link refresh processing time between the CPU module and the CC-Link IE Field Network module on the main base unit or the extension base unit is calculated by the following formulas. T, R [ms] = KM1 + KM2 ((RX + RY + SB) 16 + RWr + RWw + SW) + U U [ms] = KM3 (SBU 16 + SWU) T: Link refresh time (sending side) R: Link refresh time (receiving side) U: Unit label (SB/SW) refresh time RX: Total number of points of remote input (RX) refreshed by the master station/local station*1

RY: Total number of points of remote output (RY) refreshed by the master station/local station*1

RWw: Total number of points of remote register (RWw) refreshed by the master station/local station*1

RWr: Total number of points of remote register (RWr) refreshed by the master station/local station*1

SB: Number of points of link special relay (SB)*2

SW: Number of points of link special register (SW)*2

SBU: Number of points of link special relay (SB)*3

SWU: Number of points of link special register (SW)*3

*1 Total number of points here indicates the one of link devices that have been set in "Refresh Setting" and "Network Configuration Settings".

*2 Number of points here indicates the one of when module label is not used. Calculation is executed while it is regarded as "0" when module label is used.

*3 Number of points here indicates the one of when module label is used. Calculation is executed while it is regarded as "0" when module label is not used.

*4 The base units here indicates the type of base unit where the network module targeted for refresh is mounted.

Condition Constant value KM1 (10-3) 40.00

KM2 (10-3) Main base unit*4 0.01

Extension base unit*4 0.12

KM3 (10-3) Main base unit*4 0.03

Extension base unit*4 0.15

APPX Appendix 7 Processing Time 653

65

Link refresh processing time for the CC-Link module The link refresh processing time between the CPU module and the CC-Link module on the main base unit or the extension base unit is calculated by the following formulas. (Remote net Ver.1 mode, Remote net Ver.2 mode) T, R [ms] = KM1 + KM2 ((RX + RY + SB) 16 + RWr + RWw + SW) + U U [ms] = KM3 (SBU 16 + SWU) T: Link refresh time (sending side) R: Link refresh time (receiving side) U: Unit label (SB/SW) refresh time RX: Total number of points of remote input (RX) refreshed by the master station/local station*1

RY: Total number of points of remote output (RY) refreshed by the master station/local station*1

RWw: Total number of points of remote register (RWw) refreshed by the master station/local station*1

RWr: Total number of points of remote register (RWr) refreshed by the master station/local station*1

SB: Number of points of link special relay (SB)*2

SW: Number of points of link special register (SW)*2

SBU: Number of points of link special relay (SB)*3

SWU: Number of points of link special register (SW)*3

*1 Total number of points here indicates the one of link devices that have been set in "Refresh Setting" and "Network Configuration Settings".

*2 Number of points here indicates the one of when module label is not used. Calculation is executed while it is regarded as "0" when module label is used.

*3 Number of points here indicates the one of when module label is used. Calculation is executed while it is regarded as "0" when module label is not used.

*4 The base units here indicates the type of base unit where the network module targeted for refresh is mounted.

Condition Constant value KM1 (10-3) 40.00

KM2 (10-3) Main base unit*4 0.01

Extension base unit*4 0.12

KM3 (10-3) Main base unit*4 0.03

Extension base unit*4 0.15

4 APPX Appendix 7 Processing Time

A

Link refresh processing time for the MELSECNET/H network module The link refresh processing time between the CPU module and the MELSEC iQ-R series MELSECNET/H network module on the main base unit or the extension base unit is calculated by the following formulas. T, R [ms] = KM1 + KM2 ((LB + LX + LY + SB) 16 + LW + SW) + U U [ms] = KM3 (SBU 16 + SWU) T: Link refresh time (sending side) R: Link refresh time (receiving side) U: Unit label (SB/SW) refresh time LB: Total number of points of link relay (LB) that is refreshed by the station*1

LW: Total number of points of link register (LW) that is refreshed by the station*1

LX: Total number of points of link input (LX) that is refreshed by the station*1

LY: Total number of points of link output (LY) that is refreshed by the station*1

SB: Number of points of link special relay (SB)*2

SW: Number of points of link special register (SW)*2

SBU: Number of points of link special relay (SB)*3

SWU: Number of points of link special register (SW)*3

*1 Total number of points here indicates the one of link devices that have been set in "Refresh Setting" and "Network Configuration Settings". Note that the number of points that has been assigned in the reserved station is excluded.

*2 Number of points here indicates the one of when module label is not used. Calculation is executed while it is regarded as "0" when module label is used.

*3 Number of points here indicates the one of when module label is used. Calculation is executed while it is regarded as "0" when module label is not used.

*4 The base units here indicates the type of base unit where the network module targeted for refresh is mounted. The link refresh processing time between the CPU module and the MELSEC-Q series MELSECNET/H network module on the RQ extension base unit or the Q series extension base unit is calculated by the following formulas. T, R [ms] = KM1 + KM2 ((LB + LX + LY + SB) 16 + LW + SW) T: Link refresh time (sending side) R: Link refresh time (receiving side) LB: Total number of points of link relay (LB) that is refreshed by the station*5

LW: Total number of points of link register (LW) that is refreshed by the station*5

LX: Total number of points of link input (LX) that is refreshed by the station*5

LY: Total number of points of link output (LY) that is refreshed by the station*5

SB: Number of points of link special relay (SB) SW: Number of points of link special register (SW)

*5 Total number of points here indicates the one of link devices that have been set in "Refresh Setting" and "Network Configuration Settings". Note that the number of points that has been assigned in the reserved station is excluded.

*6 The base units here indicates the type of base unit where the network module targeted for refresh is mounted.

Condition Constant value KM1 (10-3) 40

KM2 (10-3) Main base unit*4 0.01

Extension base unit*4 0.12

KM3 (10-3) Main base unit*4 0.03

Extension base unit*4 0.15

Condition Constant value KM1 (10-3) 65

KM2 (10-3) RQ extension base unit (RQ6B)*6 0.41

Q series extension base unit (Q5B/Q6B)*6 0.92

APPX Appendix 7 Processing Time 655

65

Link refresh processing time for CC-Link IE Field Network Basic The link refresh processing time for CC-Link IE Field Network Basic (the increase in END processing time for the CPU module) can be calculated by the following formula. T [s] = KM1 + KM2 (((RX + RY) 16) + RWw + RWr) + E E [s] = KM3 + KM4 ((RX + RY) 16) + RWw + RWr) T: Link refresh time E: Link refresh time when the file register (R, ZR) is used*1

RX: Total number of points of remote input (RX) refreshed by the master station*2

RY: Total number of points of remote output (RY) refreshed by the master station*2

RWw: Total number of points of remote register (RWw) refreshed by the master station*2

RWr: Total number of points of remote register (RWr) refreshed by the master station*2

*1 This is added when file register (R, ZR) is used. *2 This value is determined according to the number of slave stations to be connected and the number of occupied stations.

Condition Constant value KM1 12.5

KM2 0.02

KM3 14.5

KM4 When the extended SRAM cassette or battery-less option cassette is not used

0.04

When the extended SRAM cassette or battery-less option cassette is used

0.11

6 APPX Appendix 7 Processing Time

A

Intelligent function module refresh processing time The following calculation formula shows the refresh processing time for the intelligent function module mounted on the main base unit and the extension base unit.

The refresh processing time described in this manual is for the case when the "Target" is set to "Device" in the refresh setting. For the refresh processing time of when the refreshing target is set to the module label or refresh data register (RD), refer to the manual for the module used.

Refresh processing time of one module [s] = Read refresh time*1 + Write refresh time*1

*1 When the number of settings of read refresh (Module CPU module) or write refresh (CPU module Module) is 0, each processing time is 0.

Read refresh time [s] Number of read refresh settings KM1 + Refresh time for the first item (A) + Refresh time for the second item (A) + + Refresh time for the nth item (A) + KM2

Write refresh time [s] Number of write refresh settings KM4 + Refresh time for the first item (B) + Refresh time for the second item (B) + + Refresh time for the nth item (B) + KM5 A: KM3 Number of refresh transfer (word) [s] B: KM6 Number of refresh transfer (word) [s] n: Number of blocks for refresh settings*1

KM1 to KM6: Constant value as shown below

*1 The number of blocks for refresh settings can be checked in "Auto Refresh Setting Total Counts" of "Module Parameter List" window. For details, refer to the manual for the module used.

Condition Constant value MELSEC iQ-R series module KM1 Module on the main base unit CPU module 0.98

Module on the extension base unit CPU module 0.98

KM2 Module on the main base unit CPU module 11.6

Module on the extension base unit CPU module 11.6

KM3 Module on the main base unit CPU module 0.05

Module on the extension base unit CPU module 0.05

KM4 CPU module Main base unit 0.58

CPU module Extension base unit 0.58

KM5 CPU module Main base unit 9.10

CPU module Extension base unit 9.10

KM6 CPU module Main base unit 0.01

CPU module Extension base unit 0.01

Q series module KM1 Module on the RQ extension base unit CPU module 1.47

Module on the Q series extension base unit CPU module 2.92

KM2 Module on the RQ extension base unit CPU module 21.2

Module on the Q series extension base unit CPU module 20.2

KM3 Module on the RQ extension base unit CPU module 0.38

Module on the Q series extension base unit CPU module 0.91

KM4 CPU module Module on the RQ extension base unit 0.83

CPU module Module on the Q series extension base unit 1.20

KM5 CPU module Module on the RQ extension base unit 15.8

CPU module Module on the Q series extension base unit 15.0

KM6 CPU module Module on the RQ extension base unit 0.43

CPU module Module on the Q series extension base unit 0.97

APPX Appendix 7 Processing Time 657

65

Multiple CPU refresh processing time This section describes the Multiple CPU refresh processing time. Refresh processing time [s] = Send refresh time + Receive refresh time Send refresh time [s] = KM1 + KM2 Number of points of send word Receive refresh time [s] = KM3 + KM4 Number of other CPU modules + KM5 Number of points of receive word

Refresh (when END) The following table lists the constant values when refresh is executed in END processing at CPU buffer memory area.

Refresh (when I45 is executed) The following table lists the constant values when refresh is executed in Multiple CPU synchronous interrupt (I45) at fixed scan communication area.

Constant Constant value KM1 6

KM2 0.01

KM3 5

KM4 14

KM5 0.011

Constant Constant value KM1 20

KM2 0.007

KM3 20

KM4 4

KM5 0.007

8 APPX Appendix 7 Processing Time

A

Prolonged time of END processing when executing each function This section describes the prolonged time of END processing when executing each function.

Latch processing time If the latch function is used and the range for the latch time setting is effective, the scan time becomes longer. Also when the time setting is configured for the latch time setting, the scan time may be prolonged in the next END processing after the specified time has passed. The increase in scan time when the latch range is set can be calculated by the following formula. Increase in scan time[s] = (KM1 Number of settings of latch range setting*1) + (KM2 (Number of points of bit device with latch specified 16 + Number of points of word device with latch specified + Number of points of double word device with latch specified 2)) + KM3 *1 The latch range (1) and the latch range (2) are counted as different device types.

Data logging function When the data logging function is executed, the scan time becomes longer. The increase in scan time can be calculated by the following formula. Increase in scan time [s] = KM1 + (KM2 Number of data logging settings) + (KM3 Number of device points of internal device*1) *1 This indicates the total number of points of data logging setting No.1 to No.10.

Data logging file transfer function In the data logging file transfer function, the scan time does not increase.

Processing time when file register is used When "Use File Register of Each Program" has been set through setting the file register, the scan time becomes longer. The increase in the scan time [ms] is given by: the number of program files 0.016.

When "Use Common File Register in All Programs" has been set, the scan time may not become longer.

Memory dump function The execution of the memory dump function results in an increase in the scan time. The increase in scan time can be calculated by the following formula. Increase in scan time [s] = (KM1 Number of points*1) + KM2

*1 This indicates the total number of points (total number of words) of devices that are set in the device area, file storage area, and refresh data register area. (unit: K words). When the total number of points exceeds the value specified in the internal buffer capacity setting, change the total number to that value (unit: K words).

Condition Constant value When set to "each scan" KM1 1.00

KM2 When the battery-less option cassette is not used 0.09

When the battery-less option cassette is used 0.1

KM3 1.20

When set to "hour" KM1 1.0

KM2 0.004

KM3 17.5

Condition Constant value When all the columns are outputted under the condition of file format of Unicode text file

KM1 34

KM2 34

KM3 0.08

Constant Constant value

R00CPU, R01CPU, R02CPU, R04CPU Other programmable controller CPUs KM1 102.00 61.00

KM2 10.00 25.00

APPX Appendix 7 Processing Time 659

66

Real-time monitor function The execution of the real-time monitor function results in an increase in the scan time. The increase in scan time can be calculated by the following formula. Increase in scan time [s] = KM1 + (KM2 Number of points of word device) + (KM3 Number of points of bit device) In monitoring global devices (X, Y, M, L, B, F, SB, V, T, ST, C, LT, LST, LC, D, W, SW, FX, FY, SM, FD, SD, BLn\S)/global

labels

In monitoring file registers (R, ZR)

In monitoring module access devices (Un\G, U3En\G, U3En\HG)/link direct devices (Jn\W, Jn\X, Jn\SW, Jn\Y, Jn\SB, Jn\B)

In monitoring local devices (M, V, T, ST, C, LT, LST, LC, D)/local labels

Sequence scan synchronization sampling function When the sequence scan synchronization sampling function is executed, the scan time becomes longer. The increase in scan time can be calculated by the following formula. Increase in scan time [s] = (KM1 Number of processing times*1) + (KM2 Total number of points of device that has been set*2) + (KM3 Number of settings*2) + (KM4 Number of modules*3) + KM5 *1 The number of processing times indicates the number of times to perform the processing for 64 points of the device that can be

processed at a time. The number of times is calculated by the total number of points of device that has been set n 64. (The decimal point is rounded up.)

*2 For the device types and number of settings that can be set, refer to the manual for the module used. *3 The number of modules indicates the total number of modules which has executed this function.

Constant Constant value KM1 149.00

KM2 3.20

KM3 0.80

Constant Constant value KM1 149.00

KM2 3.50

KM3 1.10

Constant Constant value

R00/R01/R02CPU Other CPU modules KM1 180.00 156.00

KM2 11.30 11.60

KM3 12.80 8.90

Constant Constant value

R00/R01/R02CPU Other CPU modules KM1 149.00 149.00

KM2 8.80 6.20

KM3 5.80 3.10

Constant Constant value KM1 8.00

KM2 0.42

KM3 0.20

KM4 24.00

KM5 85.00

0 APPX Appendix 7 Processing Time

A

File batch online change When the file batch online change is executed, the scan time becomes longer. The increase in scan time [ms] can be calculated by the following formula.

*1 For R00CPU, R01CPU, R02CPU, calculate with calculation formula for "when SM388 is on" in the above table. For R00CPU, R01CPU, R02CPU, the operation setting status is set to "program file/FB file/global label setting file" regardless of the SM388 setting.

*2 This indicates the number of program files that are written to the CPU module. *3 This indicates the number of steps in the largest program file among the program files to which the file batch online change is performed. *4 This indicates the number of program files to which the file batch online change is performed. *5 This indicates the total number of steps in the program files to which the file batch online change is performed.

The number of steps for each program file can be checked [Confirm Memory Size (Offline)] in [Tool] of the engineering tool.

Simple CPU communication function The processing time of the simple CPU communication function (the increase in END processing time for the CPU module) can be calculated by the following formula. Processing time of the simple CPU communication function [s] = KM1 + T1 + T2 + ... + Tn Tn [s] = KM2 + KM3 (number of bit points to be communicated 16 + number of word points to be communicated) + En

En [s] = KM4 + KM5 (number of bit points to be communicated 16 + number of word points to be communicated)

Condition*1 Calculation formula Constant value When SM388 is off (Program file only)

(KM1 Number of program files*2) + (KM2 Number of steps in the largest program*3) + KM3 KM1: 0.018 KM2: 0.06 10-3

KM3: 0.9

When SM388 is on (Program file/FB file/global label setting file)

(KM4 Number of program files to be written*4) + (KM5 Total number of steps in programs*5) KM4: 2.34 KM5: 0.06 10-3

Tn: Simple CPU communication processing time per setting En: Additional time when the file register (R, ZR) is used (It is added when the file register (R, ZR) is used.) n: Number of settings

Condition Constant value KM1 60.00

KM2 0.90

KM3 0.024

KM4 1.60

KM5 When the extended SRAM cassette or battery-less option cassette is not used 0.10

When the extended SRAM cassette or battery-less option cassette is used 0.13

APPX Appendix 7 Processing Time 661

66

Device/label access service processing time This section describes the device/label access service processing time when "Processing time = One time" in the device/label access service processing setting.

*1 When data are written to the program using a pointer (P) during RUN, the processing time is extended depending on the pointer number used. For example, when the data are written to the program using P8191 during RUN, the processing time is extended up to 3.0ms.

Condition Device/label access service processing time

Connected via USB Ladder block change during RUN (online program change)

100 steps are inserted into the head of program of 40K steps.

1.0ms maximum*1

Monitor data registration Data register (D) (Number of device points = 32 points) is registered to monitor.

0.07ms maximum

When connecting the Ethernet port (TCP)

Ladder block change during RUN (online program change)

100 steps are inserted into the head of program of 40K steps.

1.0ms maximum*1

Monitor data registration Data register (D) (Number of device points = 32 points) is registered to monitor.

0.07ms maximum

When connecting the Ethernet port (UDP)

Ladder block change during RUN (online program change)

100 steps are inserted into the head of program of 40K steps.

1.0ms maximum*1

Monitor data registration Data register (D) (Number of device points = 32 points) is registered to monitor.

0.07ms maximum

2 APPX Appendix 7 Processing Time

A

Data logging function processing time This section describes the processing time taken to store the data when executing the data logging function. (The values shown in the tables below are the minimum time values that allow the CPU module to collect data without missing any data while the continuous logging is executed.)

When the file format is Unicode text file When a global device or global label is specified The following table lists the collection intervals at which data can be collected under the following conditions. Scan time = 1.5ms (up to 3ms) Internal buffer capacity setting = 128K bytes per setting (default setting) Collection setting = Time specification (data collection at time interval) Data setting = Data register (D) (Data-type: word-signed (decimal number type)) Output setting = Day/time column (output format is default) and index column are outputted. Save setting = file switching timing: 1024K bytes (when the data storage destination memory is the function memory) or

10000 records (when the data storage destination memory is the SD memory card), operation when the number of saved files exceeded: overwriting

When the data storage destination memory is the SD memory card, functions that require access to files in the SD memory card except for the data logging function are not active.

The default setting value is used for the file transfer server setting of the CPU Module Logging Configuration Tool (however, the IP address, login user name, and password can be customized).

Parameters are used only for required settings that can be connected to the FTP server (IP address settings of the module parameter only) and default setting values are used for other settings.

Number of points File transfer Collection interval at which data can be collected

When the function memory is used

When the SD memory card is used

NZ1MEM-2GBSD NZ1MEM-4/8/16GBSD 8 points (8 points 1

setting) Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

16 points (16 points 1 setting)

Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

64 points (64 points 1 setting)

Not performed 1.0ms 2.0ms

Performed No file deletion specification at transfer completion

1.0ms 2.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 3.0ms

128 points (128 points 1 setting)

Not performed 1.0ms 4.0ms

Performed No file deletion specification at transfer completion

2.0ms 5.0ms

File deletion specification at transfer completion

1.0ms 2.0ms 6.0ms

256 points (128 points 2 setting)

Not performed 4.0ms 7.0ms (For the R04(EN)CPU: 5.0ms)

Performed No file deletion specification at transfer completion

4.0ms 8.0ms

File deletion specification at transfer completion

1.0ms 4.0ms 8.0ms

APPX Appendix 7 Processing Time 663

66

1280 points (128 points 10 setting)

Not performed 18.0ms 20.0ms

Performed No file deletion specification at transfer completion

19.0ms 23.0ms

File deletion specification at transfer completion

6.0ms 19.0ms 24.0ms (For the R04(EN)CPU: 23.0ms)

Number of points File transfer Collection interval at which data can be collected

When the function memory is used

When the SD memory card is used

NZ1MEM-2GBSD NZ1MEM-4/8/16GBSD

4 APPX Appendix 7 Processing Time

A

When a local device or local label is specified The following table lists the collection intervals at which data can be collected under the following conditions. Scan time = 1.5ms (up to 5ms) Internal buffer capacity setting = 128K bytes per setting (default setting) Collection setting = Time specification (data collection at time interval) Data setting = Data register (#D) (Data-type: word-signed (decimal number type)) Output setting = Day/time column (output format is default) and index column are outputted. Save setting = file switching timing: 1024K bytes (when the data storage destination memory is the function memory) or

10000 records (when the data storage destination memory is the SD memory card), operation when the number of saved files exceeded: overwriting

When the data storage destination memory is the SD memory card, functions that require access to files in the SD memory card except for the data logging function are not active.

The default setting value is used for the file transfer server setting of the CPU Module Logging Configuration Tool (however, the IP address, login user name, and password can be customized).

Parameters are used only for required settings that can be connected to the FTP server (IP address settings of the module parameter only) and default setting values are used for other settings.

Number of points File transfer Collection interval at which data can be collected

When the function memory is used

When the SD memory card is used

NZ1MEM-2GBSD NZ1MEM-4/8/16GBSD 8 points (8 points 1

setting) Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

16 points (16 points 1 setting)

Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

64 points (64 points 1 setting)

Not performed 1.0ms 2.0ms

Performed No file deletion specification at transfer completion

1.0ms 3.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 3.0ms

128 points (128 points 1 setting)

Not performed 3.0ms 5.0ms

Performed No file deletion specification at transfer completion

4.0ms 6.0ms

File deletion specification at transfer completion

1.0ms 4.0ms 6.0ms

256 points (128 points 2 setting)

Not performed 6.0ms 6.0ms

Performed No file deletion specification at transfer completion

7.0ms 7.0ms

File deletion specification at transfer completion

1.0ms 7.0ms 7.0ms

1280 points (128 points 10 setting)

Not performed 25.0ms 30.0ms

Performed No file deletion specification at transfer completion

30.0ms 35.0ms

File deletion specification at transfer completion

6.0ms 30.0ms 35.0ms

APPX Appendix 7 Processing Time 665

66

When the file format is CSV When a global device or global label is specified The following table lists the collection intervals at which data can be collected under the following conditions. Scan time = 1.5ms (up to 3ms) Internal buffer capacity setting = 128K bytes per setting (default setting) Collection setting = Time specification (data collection at time interval) Data setting = Data register (D) (Data-type: word-signed (decimal number type)) Output setting = Day/time column (output format is default) and index column are outputted. Save setting = file switching timing: 1024K bytes (when the data storage destination memory is the function memory) or

10000 records (when the data storage destination memory is the SD memory card), operation when the number of saved files exceeded: overwriting

When the data storage destination memory is the SD memory card, functions that require access to files in the SD memory card except for the data logging function are not active.

The default setting value is used for the file transfer server setting of the CPU Module Logging Configuration Tool (however, the IP address, login user name, and password can be customized).

Parameters are used only for required settings that can be connected to the FTP server (IP address settings of the module parameter only) and default setting values are used for other settings.

Number of points File transfer Collection interval at which data can be collected

When the function memory is used

When the SD memory card is used

NZ1MEM-2GBSD NZ1MEM-4/8/16GBSD 8 points (8 points 1

setting) Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

16 points (16 points 1 setting)

Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

64 points (64 points 1 setting)

Not performed 1.0ms 2.0ms

Performed No file deletion specification at transfer completion

1.0ms 2.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 3.0ms

128 points (128 points 1 setting)

Not performed 1.0ms 4.0ms

Performed No file deletion specification at transfer completion

2.0ms 5.0ms

File deletion specification at transfer completion

1.0ms 2.0ms 6.0ms

256 points (128 points 2 setting)

Not performed 4.0ms 7.0ms (For the R04(EN)CPU: 5.0ms)

Performed No file deletion specification at transfer completion

4.0ms 8.0ms

File deletion specification at transfer completion

1.0ms 4.0ms 8.0ms

1280 points (128 points 10 setting)

Not performed 18.0ms 20.0ms

Performed No file deletion specification at transfer completion

19.0ms 23.0ms

File deletion specification at transfer completion

6.0ms 19.0ms 24.0ms (For the R04(EN)CPU: 23.0ms)

6 APPX Appendix 7 Processing Time

A

When a local device or local label is specified The following table lists the collection intervals at which data can be collected under the following conditions. Scan time = 1.5ms (up to 5ms) Internal buffer capacity setting = 128K bytes per setting (default setting) Collection setting = Time specification (data collection at time interval) Data setting = Data register (#D) (Data-type: word-signed (decimal number type)) Output setting = Day/time column (output format is default) and index column are outputted. Save setting = file switching timing: 1024K bytes (when the data storage destination memory is the function memory) or

10000 records (when the data storage destination memory is the SD memory card), operation when the number of saved files exceeded: overwriting

When the data storage destination memory is the SD memory card, functions that require access to files in the SD memory card except for the data logging function are not active.

The default setting value is used for the file transfer server setting of the CPU Module Logging Configuration Tool (however, the IP address, login user name, and password can be customized).

Parameters are used only for required settings that can be connected to the FTP server (IP address settings of the module parameter only) and default setting values are used for other settings.

Number of points File transfer Collection interval at which data can be collected

When the function memory is used

When the SD memory card is used

NZ1MEM-2GBSD NZ1MEM-4/8/16GBSD 8 points (8 points 1

setting) Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

16 points (16 points 1 setting)

Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

64 points (64 points 1 setting)

Not performed 1.0ms 2.0ms

Performed No file deletion specification at transfer completion

1.0ms 3.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 3.0ms

128 points (128 points 1 setting)

Not performed 3.0ms 5.0ms

Performed No file deletion specification at transfer completion

4.0ms 6.0ms

File deletion specification at transfer completion

1.0ms 4.0ms 6.0ms

256 points (128 points 2 setting)

Not performed 6.0ms 6.0ms

Performed No file deletion specification at transfer completion

7.0ms 7.0ms

File deletion specification at transfer completion

1.0ms 7.0ms 7.0ms

1280 points (128 points 10 setting)

Not performed 25.0ms 30.0ms

Performed No file deletion specification at transfer completion

30.0ms 35.0ms

File deletion specification at transfer completion

6.0ms 30.0ms 35.0ms

APPX Appendix 7 Processing Time 667

66

When the file format is binary file When a global device or global label is specified The following table lists the collection intervals at which data can be collected under the following conditions. Scan time = 1.5ms (up to 3ms) Internal buffer capacity setting = 128K bytes per setting (default setting) Collection setting = Time specification (data collection at time interval) Data setting = Data register (D) (Data-type: word-signed (decimal number type)) Output setting = Day/time column (output format is default) and index column are outputted. Save setting = file switching timing: 1024K bytes (when the data storage destination memory is the function memory) or

10000 records (when the data storage destination memory is the SD memory card), operation when the number of saved files exceeded: overwriting

When the data storage destination memory is the SD memory card, functions that require access to files in the SD memory card except for the data logging function are not active.

The default setting value is used for the file transfer server setting of the CPU Module Logging Configuration Tool (however, the IP address, login user name, and password can be customized).

Parameters are used only for required settings that can be connected to the FTP server (IP address settings of the module parameter only) and default setting values are used for other settings.

Number of points File transfer Collection interval at which data can be collected

When the function memory is used

When the SD memory card is used

NZ1MEM-2GBSD NZ1MEM-4/8/16GBSD 8 points (8 points 1

setting) Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

16 points (16 points 1 setting)

Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

64 points (64 points 1 setting)

Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 2.0ms (For the R04(EN)CPU: 1.0ms)

128 points (128 points 1 setting)

Not performed 1.0ms 3.0ms

Performed No file deletion specification at transfer completion

2.0ms 4.0ms (For the R04(EN)CPU: 3.0ms)

File deletion specification at transfer completion

1.0ms 2.0ms 4.0ms (For the R04(EN)CPU: 3.0ms)

256 points (128 points 2 setting)

Not performed 4.0ms 5.0ms

Performed No file deletion specification at transfer completion

4.0ms 6.0ms

File deletion specification at transfer completion

1.0ms 4.0ms 7.0ms (For the R04(EN)CPU: 6.0ms)

1280 points (128 points 10 setting)

Not performed 13.0ms 18.0ms

Performed No file deletion specification at transfer completion

17.0ms 20.0ms (For the R04(EN)CPU: 18.0ms)

File deletion specification at transfer completion

5.0ms 17.0ms 21.0ms (For the R04(EN)CPU: 18.0ms)

8 APPX Appendix 7 Processing Time

A

When a local device or local label is specified The following table lists the collection intervals at which data can be collected under the following conditions. Scan time = 1.5ms (up to 5ms) Internal buffer capacity setting = 128K bytes per setting (default setting) Collection setting = Time specification (data collection at time interval) Data setting = Data register (#D) (Data-type: word-signed (decimal number type)) Output setting = Day/time column (output format is default) and index column are outputted. Save setting = file switching timing: 1024K bytes (when the data storage destination memory is the function memory) or

10000 records (when the data storage destination memory is the SD memory card), operation when the number of saved files exceeded: overwriting

When the data storage destination memory is the SD memory card, functions that require access to files in the SD memory card except for the data logging function are not active.

The default setting value is used for the file transfer server setting of the CPU Module Logging Configuration Tool (however, the IP address, login user name, and password can be customized).

Parameters are used only for required settings that can be connected to the FTP server (IP address settings of the module parameter only) and default setting values are used for other settings.

Number of points File transfer Collection interval at which data can be collected

When the function memory is used

When the SD memory card is used

NZ1MEM-2GBSD NZ1MEM-4/8/16GBSD 8 points (8 points 1

setting) Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

16 points (16 points 1 setting)

Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 1.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 1.0ms

64 points (64 points 1 setting)

Not performed 1.0ms 1.0ms

Performed No file deletion specification at transfer completion

1.0ms 2.0ms

File deletion specification at transfer completion

1.0ms 1.0ms 2.0ms

128 points (128 points 1 setting)

Not performed 2.0ms 5.0ms

Performed No file deletion specification at transfer completion

3.0ms 6.0ms

File deletion specification at transfer completion

1.0ms 3.0ms 6.0ms

256 points (128 points 2 setting)

Not performed 4.0ms 6.0ms

Performed No file deletion specification at transfer completion

5.0ms 7.0ms

File deletion specification at transfer completion

1.0ms 5.0ms 7.0ms

1280 points (128 points 10 setting)

Not performed 25.0ms 30.0ms

Performed No file deletion specification at transfer completion

25.0ms 35.0ms

File deletion specification at transfer completion

5.0ms 25.0ms 35.0ms

APPX Appendix 7 Processing Time 669

67

Memory dump function processing time This section describes the time (unit: seconds) taken to save all of the data when the memory dump function is in execution. The following table shows the time taken for data save under the following conditions: Scan time = 1.5ms (up to 3ms) Internal buffer capacity setting = 256K bytes (by default) SD memory card: NZ1MEM-2/4/8/16GBSD used

*1 This indicates the total number of points (total number of words) of devices that are set in the device area, file storage area, and refresh data register area.

*2 This indicates the number of device points (user device: 38.4K points (words), refresh data register: 512K points (words)) with the CPU parameters set to default values.

*3 Settings for this number of points (with no extended SRAM cassette inserted) are as follows. User device: 40K points (words), file register: 160K points (words), and refresh data register: 1024K points (words) "Use Common File Register in All Programs" is selected in the file register setting.

*4 Settings for this number of points (with an 8M extended SRAM cassette inserted) are as follows. Total number of points (total number of words) of user devices, local devices, and file registers: 4296K points (words), and refresh data register: 1024K points (words) "Use File Register of Each Program" is selected in the file register setting. The number of program files is 10.

*5 Settings for this number of points (with a 16M extended SRAM cassette inserted) are as follows. Total number of points (total number of words) of user devices, local devices, and file registers: 8392K points (words), and refresh data register: 1024K points (words) "Use File Register of Each Program" is selected in the file register setting. The number of program files is 10.

Real-time monitor function processing time This section shows the minimum value (unit: ms) of monitor interval that allows monitoring under the following conditions without data loss during execution of the real-time monitor function. Scan time = 1.5ms (up to 3ms)*1

Data = agrees with the "Number of points of word device" column in the table below (The value of monitor interval does not change when a local device or label is specified.)

Timing = Condition specification (step No. specification)*2

Internal buffer capacity = 32K bytes (default) Fixed scan interrupt timing = generating a fixed scan interrupt on the head step number of the program where step

numbers are specified Performance of the system of personal computer = CPU: Intel CoreTM i3-2100 CPU (3.10GHz), Memory: 2GB, OS:

Windows 7 Professional SP1 32 bits *1 The scan time during non-execution of the real-time monitor function shall be an average of 1.0ms. *2 Program name: Arbitrary, Step No.: Head step of the program, Execution condition: Set to Always

Number of points*1 Time taken for data save when the memory dump function is in execution

NZ1MEM-2GBSD NZ1MEM-4/8/16GBSD 550.4K points*2 17.00 seconds 25.00 seconds

1224K points*3 35.00 seconds 56.00 seconds

5320K points*4 145.00 seconds 240.00 seconds

9416K points*5 244.00 seconds 404.00 seconds

Condition Number of points of word device Value of monitor interval Connected via USB 1 point 0.15ms

8 points 0.25ms

16 points 0.45ms

When connecting the Ethernet port (TCP) 1 point 0.55ms

8 points 1.25ms

16 points 1.35ms

When connecting the Ethernet port (UDP) 1 point 0.15ms

8 points 0.30ms

16 points 0.50ms

0 APPX Appendix 7 Processing Time

A

Database function processing time

Database operation by database access instruction The table below lists the processing time under the following conditions:

This section shows the time taken for the completion signal of the completion device to turn on from the execution of each instruction of the database access instructions.

*1 After power-on, initial database access involves the diagnostics to check whether the database is corrupted, and thus it takes time to execute the DBOPEN instruction.

For the programmable controller CPU with firmware version earlier than "28" The table below lists the processing time under the following conditions:

This section shows the time taken for the completion signal of the completion device to turn on from the execution of each instruction of the database access instructions.

*1 After power-on, initial database access involves the diagnostics to check whether the database is corrupted, and thus it takes time to execute the DBOPEN instruction.

Condition 1 Condition 2 Number of records: 10000 Number of fields: 16

The data type of the field is WORD (6 fields), LREAL (6 fields), WSTRING (124 characters) (3 fields), and BOOL (1 field).

Main key: Provided Functions that require access to files in the SD memory card except for the

database function are not active.

Number of records: 10000 Number of fields: 64

The data type of the field is WORD (20 fields), LREAL (20 fields), WSTRING (124 characters) (6 fields), and BOOL (18 fields).

Main key: Provided Functions that require access to files in the SD memory card except for the

database function are not active.

Instruction Time taken to complete the execution of instruction

Condition 1 Condition 2 Database import DBIMPORT 155s 255s

Database export DBEXPORT 75s 195s

Database connection DBOPEN First time*1 150ms 150ms

Second time or later 105ms 105ms

Database disconnection DBCLOSE 30ms 30ms

Database record search DBSELECT 700ms 750ms

Database record addition DBINSERT 700ms 800ms

Database record update DBUPDATE 550ms 600ms

Database record deletion DBDELETE 700ms 1000ms

Condition Number of tables: 1 Number of records: 10000 Number of fields: 4

The data type of the field is specified as WORD, DWORD, WSTRING (16 characters), and WSTRING (32 characters). Index: specified Transaction: Provided (The DBINSERT/DBUPDATE/DBSELECT/DBDELETE instructions only are subject to this condition.) Functions that require access files in to the SD memory card except for the database access instruction are not active.

Instruction Time taken to complete the execution of instruction Database import DBIMPORT 320s

Database export DBEXPORT 220s

Database connection DBOPEN First time*1 590ms

Second time or later 140ms

Database disconnection DBCLOSE 3ms

Database record search DBSELECT 180ms

Database record addition DBINSERT 210ms

Database record update DBUPDATE 260ms

Database record deletion DBDELETE 300ms

APPX Appendix 7 Processing Time 671

67

Processing time of the CPU module database access (from external device) function The table below lists the processing time under the following conditions:

The following table lists the processing time until the database operation is completed with the CPU module database access function.

Condition 1 Condition 2 Number of records: 10000 Number of fields: 16

The data type of the field is specified as WORD (6 fields), DOUBLE PRECISION (6 fields), NLSCHAR(UNICODE) [124 characters] (3 fields), and BOOLEAN (1 field).

Main key: Provided Functions that require access to files in the SD memory card except for the

CPU module database access function are not active.

Number of records: 10000 Number of fields: 64

The data type of the field is specified as WORD (20 fields), DOUBLE PRECISION (20 fields), NLSCHAR(UNICODE) [124 characters] (6 fields), and BOOLEAN (18 fields).

Main key: Provided Functions that require access to files in the SD memory card except for the

CPU module database access function are not active.

Item Time until the operation is completed

Condition 1 Condition 2 Connect to the database of the CPU module from the application (Microsoft Access). 5s

Select a record in the database of the CPU module from the application (Excel). (SELECT) 3s 3s

Insert 1000 records in the database of the CPU module from the application (Microsoft Access). (INSERT) 230s 330s

Update a record in the database of the CPU module from the application (Microsoft Access). (UPDATE) 1s 1s

Delete a record in the database of the CPU module from the application (Microsoft Access). (DELETE) 1s 1s

2 APPX Appendix 7 Processing Time

A

SFC program processing time This section describes the time required for SFC program processing.

For details on the SFC program, refer to the following. MELSEC iQ-R Programming Manual (Program Design)

SFC program processing performance The SFC program execution time can be calculated with the following formula. SFC program execution time = (A) + (B) + (C)

*1 For the processing time for each instruction, refer to the following. MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

The following table lists the types of the SFC processing time (A). SFC processing time (A) = (a) + (b) + (c) + (d) + (e) + (f) + (g) + (h)

The following table lists the coefficient values for each processing time.

Item Description (A) SFC processing time This is the total time shown in the following table.

(B) Operation output processing time for all steps

This is the total processing time for each instruction used for operation output for all steps in the active status.

(C) Processing time for all transition conditions

This is the total processing time for each instruction used for transition conditions associated with each step in the active status.

Item Processing time calculation (unit: s) Description (a) Active block processing

time Active block processing time coefficient Number of active blocks

This is the system processing time required to execute active blocks.

(b) Inactive block processing time

Inactive block processing time coefficient Number of inactive blocks

This is the processing time required to execute inactive blocks.

(c) Nonexistent block processing time

Nonexistent block processing time coefficient Number of nonexistent blocks

This is the system processing time required to execute blocks that have not been created.

(d) Active step processing time Active step processing time coefficient Number of active steps

This is the time required to execute active steps.

(e) Active transition processing time

Active transition processing time coefficient Number of active transitions

This is the system processing time required to execute active transitions.

(f) Transition establishment step processing time

Transition establishment step processing time coefficient Number of transitions

This is the time required to turn off active steps when transitions are established.

(g) SFC END processing time SFC END processing time = SFC END processing time

This is the system processing time required for SFC END processing.

(h) Operation output processing time

Action processing time coefficient Number of actions

This is the system processing time required to process operation outputs.

Item Coefficient value

R00CPU, R01CPU, R02CPU Other CPU modules Active block processing time coefficient 3.35 4.4

Inactive block processing time coefficient 2.8 2.7

Nonexistent block processing time coefficient 0.25 0.23

Active step processing time coefficient 12.6 6.8

Active transition processing time coefficient 0.21 0.12

Transition establishment step processing time coefficient

Hold step 30.0 22.5

Normal step 45.0 31.0

SFC END processing time 45.0 56.5

Operation output processing time coefficient 2.5 0.94

APPX Appendix 7 Processing Time 673

67

SFC program switching This section describes the processing time required to switch the SFC program from the standby status to the scan execution type. Switching processing time [s] = (Number of blocks created Km) + (Number of steps created Kn) + (SFC program

capacity Kp) + Kq

*1 For the firmware version "30" or earlier, the values are as follows. R04CPU, R04ENCPU, R08CPU, R08ENCPU, R16CPU, R16ENCPU, R32CPU, R32ENCPU:Km = 3.97, Kn = 0.41, Kp = 0.39 R120CPU, R120ENCPU:Km = 3.97, Kn = 0.41, Kp = 0.32

When the SFC program capacity is the following models or conditions, the processing time required to switch the SFC program from the standby status to the scan execution type will be fixed.

When the SFC information device is set, the processing time required to switch the SFC program from the standby status to the scan execution type will become longer.

Constant Constant value

R00CPU, R01CPU, R02CPU Other CPU modules Km 7.90 7.90*1

Kn 1.85 1.55*1

Kp 0.21 0.21*1

Kq 2550 2500

Model Condition Processing time (constant value) The R04CPU, R04ENCPU, R08CPU, R08ENCPU, R16CPU, R16ENCPU, R32CPU, and R32ENCPU with firmware version "30" or earlier

28K steps or less 14ms

The R120CPU and R120ENCPU with firmware version "30" or earlier

48K steps or less 18ms

4 APPX Appendix 7 Processing Time

A

Processing time until the file operation is completed This section describes the processing time from the start of the file operation instruction until the completion of the file operation.

Changes in the processing time according to the number of files The processing time changes according to the number of files stored in folders. The table below lists the processing time under the following conditions: [Condition] Folder/file structure (drive 2: SD memory card) SD memory card: NZ1MEM-2/4/8/16GBSD used Size of each file to be operated: 1K byte The following table lists the instruction arguments of each file operation instruction.

File/folder structures except those shown below do not exist.

Overwriting setting: Not overwrite (SP.FCOPY, SP.FMOVE only) Target type setting: Folder specification Empty folder deletion setting: Delete folders even when they are not empty (SP.FDELETE only)

Processing time

Instruction name

First argument

Second argument

Third argument

Fourth argument

Fifth argument

Sixth argument

Seventh argument

SP.FDELETE U0 K2 D0 "D001" M0

SP.FCOPY U0 D0 K2 "D001" K2 "D002" M0

SP.FMOVE U0 D0 K2 "D001" K2 "D002" M0

SP.FRENAME U0 K2 D0 "D001" "D003" M0

SP.FSTATUS U0 K2 D0 "D001" D10 M0

Instruction name Number of operated files in the folder (D001)

1 10 100 1000 SP.FDELETE 38ms 173ms 1417ms 16768ms

SP.FCOPY 694ms 1169ms 6045ms 80977ms

SP.FMOVE 53ms 53ms 53ms 53ms

SP.FRENAME 32ms 32ms 32ms 32ms

SP.FSTATUS 9ms 9ms 9ms 9ms

Fxxxxx.txt

$MELPRJ$

D001

D002

APPX Appendix 7 Processing Time 675

67

Changes in the processing time according to the file size The processing time changes according to the size of the files stored in the folder. The table below lists the processing time under the following conditions: [Condition] Folder/file structure (drive 2: SD memory card) SD memory card: NZ1MEM-2/4/8/16GBSD used Number of files in the folder: 1 The following table lists the instruction argument of each file operation instruction.

File/folder structures except those shown below do not exist.

Overwriting setting: Not overwrite (SP.FCOPY, SP.FMOVE only) Target type setting: File specification

Processing time

Instruction name

First argument

Second argument

Third argument

Fourth argument Fifth argument

Sixth argument

Seventh argument

SP.FDELETE U0 K2 D0 "D001\F00001.txt" M0

SP.FCOPY U0 D0 K2 "D001\F00001.txt" K2 "D002" M0

SP.FMOVE U0 D0 K2 "D001\F00001.txt" K2 "D002" M0

SP.FRENAME U0 K2 D0 "D001\F00001.txt" "F00002.txt" M0

SP.FSTATUS U0 K2 D0 "D001\F00001.txt" D10 M0

Instruction name Size of operated files in the folder (D001)

1MB 16MB 64MB 256MB SP.FDELETE 40ms 40ms 130ms 270ms

SP.FCOPY 450ms 5450ms 21450ms 85400ms

SP.FMOVE 60ms 60ms 60ms 60ms

SP.FRENAME 50ms 50ms 50ms 50ms

SP.FSTATUS 10ms 10ms 10ms 10ms

F00001.txt

$MELPRJ$

D001

D002

6 APPX Appendix 7 Processing Time

A

Appendix 8 Parameter List This section lists parameters.

For the parameters that are not described in this chapter, refer to the manuals for each module used.

System parameters The following is the list of system parameters.

Item Parameter No. I/O Assignment Base/Power/Extension Cable Setting Slot 0201H

Base, Power Supply Module, Extension Cable 0203H

I/O Assignment Setting Points, Start XY, Module Status Setting 0200H

Control PLC Settings 0202H

Module Name 0203H

Points Occupied by Empty Slot Batch Setting 0100H

Multiple CPU Setting Communication Setting between CPUs

CPU Buffer Memory Setting (at refresh END) 0304H

CPU Buffer Memory Setting (at execution of refresh I45) 0308H

PLC Unit Data 0309H

Fixed Scan Communication Function

Fixed Scan Communication Area Setting 0307H

Fixed Scan Communication Setting Fixed Scan Interval Setting of Fixed Scan Communication 0306H

Fixed Scan Communication Function and Inter-module Synchronization Function

0306H

Operation Mode Setting Stop Setting 0302H

Synchronous Startup Setting 030AH

Other PLC Control Module Setting I/O Setting Outside Group 0305H

Inter-module Synchronization Setting

Use Inter-module Synchronization Function in System

Select Inter-module Synchronization Target Module 0101H

Fixed Scan Interval Setting of Inter-module Synchronization 0101H

Inter-module Synchronous Master Setting 0102H

APPX Appendix 8 Parameter List 677

67

CPU Parameters The following is the list of CPU parameters.

Item Parameter No. Name Setting Title Setting 3100H

Comment Setting 3101H

Operation Related Setting Timer Limit Setting 3200H

RUN-PAUSE Contact Setting 3201H

Remote Reset Setting 3202H

Output Mode Setting of STOP to RUN 3203H

Module Synchronous Setting 3207H

Clock Related Setting 3209H

Co-recording Setting 320DH

Interrupt Settings Fixed Scan Interval Setting 3A00H

Fixed Scan Execution Mode Setting 3A00H

Interrupt Enable Setting in Executing Instruction 3A00H

Block No. Save/Recovery Setting 3A00H

Interrupt Priority Setting from Module 3A01H

Service Processing Setting Device/Label Access Service Processing Setting 3B00H

File Setting File Register Setting 3300H

Initial Value Setting 3301H

Label Initial Value Reflection Setting 3302H

File Setting for Device Data Storage 3303H

Memory/Device Setting Cassette Setting Extended SRAM Cassette 3404H

Battery-less Option Cassette Setting 340CH

Device/Label Memory Area Setting Device/Label Memory Area Capacity Setting 3400H

Device Points 3401H

Local Device 3405H

Latch Range Setting 3407H

Latch Type Setting of Latch Type Label 3408H

Index Register Setting 3402H

Refresh Memory Setting 3403H

Device Latch Interval Setting 3406H

Pointer Setting 340BH

Internal Buffer Capacity Setting 340AH

Link Direct Device Setting 340DH

Buffer Area Setting for Data Sampling 340EH

Device write-protect setting 340FH

RAS Setting Scan Time Monitoring Time (WDT) Setting 3500H

Constant Scan Setting 3503H

Error Detections Setting 3501H

CPU Module Operation Setting at Error Detected 3501H

LED Display Setting 3502H

Event History Setting Save Destination 3507H*1

Set Save Volume of Per File 3507H*1

Save Device/Label Operations 3507H

8 APPX Appendix 8 Parameter List

A

*1 When the device/label operation save setting is set to "Do not save", the value is 3504H.

Module parameters The following are the lists of module parameters.

Ethernet function For the module parameters relating to the Ethernet function, refer to the following. MELSEC iQ-R Ethernet User's Manual (Application)

CC-Link IE Field Network Basic function The following is the list of module parameters relating to the CC-Link IE Field Network Basic function.

CPU module database access function The following is the list of the module parameter related to the CPU module database access function.

Memory card parameters The following is the list of memory card parameters.

Program Setting Program Setting Program Name 3700H

Execution Type 3700H

Type (Fixed Scan) 3700H

Type (Event) 3701H

Detail Setting Information

Refresh Group Setting 3700H

Device/File Use or not 3700H

FB/FUN File Setting 3702H

Refresh Setting between Multiple CPU

Refresh Setting (At the END) 3901H

Refresh Setting (At I45 Exe.) 3902H

Routing Setting Routing Setting 3800H

SFC Setting SFC Program Start Mode Setting 3C00H

Start Condition Setting 3C00H

Output Mode at Block Stop Setting 3C00H

Item Parameter No. CC-Link IEF Basic Setting Network Configuration Settings 7A00H

Refresh Settings 7420H

Item Parameter No. Application settings Built-in Database Access Setting A0E0H

Item Parameter No. Boot Setting Operation Setting at CPU Built-in Memory Boot 2000H

Boot File Setting

Setting of File/Data Use or Not in Memory Card Data for Label Communication 2010H

Module Extended Parameter

Slave Station Parameter

Item Parameter No.

APPX Appendix 8 Parameter List 679

68

Appendix 9 Target List and Operation Details of the Device/Label Access Service Processing Setting

Target list This section describes the targets of the device/label access service processing setting.

Communication functions via the SLMP/MC protocol Among communication functions using the SLMP/MC protocol, those to which the device/label access service processing setting can be applied are as follows.

*1 Only the file register file can support it. (Other file access is always executed asynchronously from the program.) *2 When registration/clear command is executed, it does not affect the scan time. However, since the serial communication module will

periodically access into the device memory of the CPU module when Function is enabled, it becomes the target for Device/Label access service processing setting.

Applicable function Description Functions to perform read/write to files accessed by programs When read/write is performed to the relevant files during execution of a

program, file inconsistency may occur. Therefore, such operation is performed during the END processing.

Functions to perform write to devices/labels When write is performed to devices/labels during execution of a program, the result of operation processing may become inconsistent. Therefore, such operation is performed during the END processing.

Function Command Device memory Multiple blocks batch read 0406 (000)

Multiple blocks batch write 1406 (000)

Batch read In units of bits 0401 (001)

In units of words 0401 (000)

Batch write In units of bits 1401 (001)

In units of words 1401 (000)

Random read 0403 (000)

Test (Random write) In units of bits 1402 (001)

In units of words 1402 (000)

Monitor 0802 (000)

Files New file creation*1 1820 (0000)

File copy*1 File password function incompatible 1824 (0000)

File password function compatible 1824 (0004)

File open*1 File password function incompatible 1827 (0000)

File password function compatible 1827 (0004)

File read*1 1828 (0000)

File write*1 1829 (0000)

File close*1 182A (0000)

Programmable controller CPU monitoring

Registration*2 0630 (0000)

Clear*2 0631 (0000)

0 APPX Appendix 9 Target List and Operation Details of the Device/Label Access Service Processing Setting

A

Communication function using an engineering tool Of the communication functions using an engineering tool, the functions targeted for the setting of the Device/Label access service processing are indicated.

*1 Only the file register file can support it. (Other file access is always executed asynchronously from the program.)

Function Writing data to the programmable controller File register file

Device data (Local device also included)

Global label and local label data

Reading data from the programmable controller File register file

Device data (Local device also included)

Global label and local label data

Device data storage file

Monitor function Circuit monitor

Device/buffer memory batch monitor

Label batch monitor (local label included)

Buffer memory monitor

Ethernet function File transfer (FTP server)*1

File transfer (FTP client)*1

APPX Appendix 9 Target List and Operation Details of the Device/Label Access Service Processing Setting 681

68

Operation details Operations enabled by setting details of the device/label access service processing setting are as follows.

Execute the process as scan time proceeds This setting is useful to execute the device/label access service processing in a way commensurate with the system size. It allows the system to be designed without considering the device/label access service processing time because it is determined as a function of the scan time.

Ex.

When "Scan time ratio = 10%" is set

For operations such as access to devices, which are synchronized with the program, adjust the time by this setting because they are processed during the END processing. If no request data for the device/label access service processing exists, the scan time is shortened by the specified ratio as the CPU module proceeds to the next scan without waiting for requests. However, when the device/label access service processing constant wait function*1 is enabled, until the ratio set for the device/label access service processing setting of the CPU parameters is reached, the CPU module waits for requests even if requests for service processing do not exist.

*1 For details on the compatible CPU modules, refer to the following. Page 700 Added and Enhanced Functions

(1) Synchronization with program is unnecessary. (2) Multiple requests are processed until the specified device/label access service processing ratio (10%) is exceeded. When the specified device/label access

service processing ratio is exceeded, the remaining requests are processed in the END processing of the next scan. Also, for scan which has the device/ label access service processing time shorter than 0.1ms, it is assumed as "The device/label access service processing time per scan = 0.1ms".

(3) Operations such as access to device, which are synchronized with the program, are processed in the END processing. (4) The maximum device/label access service processing time available varies because the scan time (program execution time) varies.

(1)

(3)

(2)

1ms

1.2ms

(4)

Control processing (At program execution)

Refresh processing

R eq

ue st

1

R eq

ue st

2

R eq

ue st

3

R eq

ue st

4

R eq

ue st

5

Program execution

END processing

Communication processing

Device/label access service processing request

Engineering tool

Communication processing

Refresh processing

Program execution

END processing

Refresh processing

Program execution

Request 2

Request 1

Request 3 Request 4

END processingS ec

on d

sc an

(1 0m

s) S

ec on

d sc

an (1

0m s)

Fi rs

t s ca

n (1

0m s)

Fi rs

t s ca

n (1

0m s)

Th ird

s ca

n (1

2m s)

Th ird

s ca

n (1

2m s)

2 APPX Appendix 9 Target List and Operation Details of the Device/Label Access Service Processing Setting

A

Set Processing Time This setting is useful to give priority to the device/label access service processing. It allows for stable communication because the CPU module can always process a constant amount of the device/label access service processing without affecting the scan time.

Ex.

When "Processing time = 1ms" is set

For operations such as access to devices, which are synchronized with the program, adjust the time by this setting because they are processed during the END processing. If no request data for the device/label access service processing exists, the scan time is shortened by the specified ratio as the CPU module proceeds to the next scan without waiting for requests.

(1) Synchronization with program is unnecessary. (2) Multiple requests are processed until the specified processing time (1ms) is exceeded. If the specified processing time is exceeded, the remaining requests

are processed in the END processing of the next scan. (3) Operations such as access to device, which are synchronized with the program, are processed in the END processing. (4) The maximum device/label access service processing time available is the same even when the scan time (program execution time) varies.

1ms

(4)

1ms

(2) (3)

(1)

Control processing (At program execution)

Refresh processing

Program execution

END processing

Refresh processing

Program execution

END processing

Refresh processing

Program execution

END processing

Request 2

Request 3 Request 4

Request 1 Communication processing

Communication processing

Device/label access service processing request

R eq

ue st

4

R eq

ue st

5

R eq

ue st

2

R eq

ue st

1

R eq

ue st

3

Engineering tool

S ec

on d

sc an

(1 0m

s) S

ec on

d sc

an (1

0m s)

Fi rs

t s ca

n (1

0m s)

Fi rs

t s ca

n (1

0m s)

Th ird

s ca

n (1

2m s)

Th ird

s ca

n (1

2m s)

APPX Appendix 9 Target List and Operation Details of the Device/Label Access Service Processing Setting 683

68

Set Processing Counts This setting is useful to stably execute the device/label access service processing in a system where requests come from multiple peripherals. It provides stable communication in a system where multiple peripherals exist because the CPU module can execute the device/label access service processing based on the number of request sources.

Ex.

When "Processing counts = 2" is set

For operations such as access to devices, which are synchronized with the program, adjust the number of executions by this setting because they are processed during the END processing. If no request data for the device/label access service processing exists, the CPU module proceeds to the next scan without waiting for requests.

(1) Synchronization with program is unnecessary. (2) Two requests are processed in one END processing independently of the requested processing time.

(1)

(2)

(2)

Fi rs

t s ca

n S

ec on

d sc

an Th

ird s

ca n

Control processing (At program execution) Communication processing

Refresh processing

Program execution

END processing

Refresh processing

Program execution

Request 2 Request 3

END processing

Refresh processing

Program execution

END processing Request 4 Request 5

Request 1 Communication processing

Re qu

es t 4

Re qu

es t 5

Re qu

es t 2

Re qu

es t 6

Re qu

es t 1

Re qu

es t 3

Device/label access service processing request

Engineering tool

4 APPX Appendix 9 Target List and Operation Details of the Device/Label Access Service Processing Setting

A

Execute END Processing between Programs This setting is useful to give priority to the device/label access service processing in a system with a large number of programs. Because operations such as access to devices are performed between program executions and during the END processing, requests as many as the number of programs can be processed during a single scan. As a result, it can reduce the response for the device/label access service processing.

Ex.

When "Execute END Processing between Programs" is enabled

(1) Synchronization with program is unnecessary. (2) Requests for operations such as access to devices are processed between program executions and during the END processing.

(1)

(2)

(2)

Control processing (At program execution) Communication processing

Refresh processing

Program 1) execution

Between programs

Program 2) execution

END processing

Request 2

Request 1

Request 3

1 sc

an

R eq

ue st

1

R eq

ue st

2

R eq

ue st

3

R eq

ue st

4

R eq

ue st

5

Engineering tool

Communication processing

Device/label access service processing request

APPX Appendix 9 Target List and Operation Details of the Device/Label Access Service Processing Setting 685

68

Appendix 10Program Restoration Information Write Selection

Program restoration information includes the information required to read a program from the programmable controller with the engineering tool. ( Page 125 Data allocation and procedure of read/write operations) Generally, use the CPU module with program restoration information written. However, the method that the program restoration information is not written during writing to the programmable controller and online change*1 can be selected. Disabling the writing of program restoration information can shorten the time required for writing. This setting is useful to change and write programs repeatedly in the short term such as system start-up and program debugging. *1 Even if the program restoration information writing is disabled, an empty file of the same size as the program restoration information is

created in the data memory. For the setting method and operating procedure, refer to the following. GX Works3 Operating Manual

To use the program restoration information write selection, check the versions of the CPU module and engineering tool used. ( Page 700 Added and Enhanced Functions)

When the program restoration information is not written, data cannot be read from the programmable controller or the detailed verification result window cannot be displayed for verifying data with the programmable controller. Therefore, always write program restoration information after the completion of work such as system start-up and program debugging.

Before writing the program restoration information to a CPU module with no program restoration information by using the online change, select "Write in Background" in the following option.

[Tool] [Options] "Convert" "Online Program Change" "Operational Setting" "Write Program Restore Information"

Checking the program restoration information write status The write status of the program restoration information can be checked in the following ways.

*1 Program restoration information of all programs is written. *2 There are one or more programs whose restoration information is not written.

The records of the program restoration information write status are not retained in the event history. Check the write status using the items described above.

Item Description Reference SM387 (Program restoration information write status)

Off: All written*1

On: Not all written*2 Page 582 System information

SD1488 (Debug function usage status) b1: Program restoration information write status Off: All written*1

On: Not all written*2

Page 633 Debug function

FUNCTION LED Off: All written*1

Flashing: Not all written*2

Monitor status of GX Works3 All written*1 (Data can be read from the programmable controller.)

GX Works3 Operating Manual

Not all written*2 (Data cannot be read from the programmable controller.)

6 APPX Appendix 10 Program Restoration Information Write Selection

A

FUNCTION LED The FUNCTION LED indication follows the priority order shown below.

When program restoration information is not written, the operating status of other functions cannot be checked with the FUNCTION LED indication only. However, the operating status of the above functions can be checked with the FUNCTION LED by changing the LED control setting for program restoration information write status.

Procedures for disabling the FUNCTION LED flashing The following describes the procedures for disabling the FUNCTION LED flashing when program restoration information is not written.

Priority Description Remarks High When program restoration information is not written, when the external input/output forced

on/off function is executed (in registration), when the device tests with execution conditions are registered

Same priority

Low Functions set in "Function to use FUNCTION LED" of "LED Display Setting" (such as the data logging function)

Page 172 LED display setting

1. Check that SM386 (Program restoration information write status LED control setting mode) is off (LED flashing).

2. Set "AFAFH" to SD384 (System operation setting).

3. Turn off and on SM384 (System operation setting request). SM384 is automatically turned off. If writing has failed, SM385 (System operation setting error) is turned on and an error is stored in SD385 (System operation setting error cause).

4. Check that SM385 is off, and turn off or reset the CPU module. 5. The FUNCTION LED turns off and SM386 turns on (without LED flashing). b1 of SD1488

(Debug function usage status) is turned off. When other functions relating to the FUNCTION LED indication are used, the LED indication follows the execution status.

APPX Appendix 10 Program Restoration Information Write Selection 687

68

Procedures for returning the FUNCTION LED to the flashing state The following describes the procedures for returning the FUNCTION LED to the flashing state when program restoration information is not written.

Precautions The following describes the precautions for the program restoration information write selection.

Precautions when using the boot operation When using the boot operation, always write program restoration information. When "No" is selected in "Program Restore

Information", the SD memory card cannot be specified for the write destination. If online change is executed during boot operation with "No" being selected in "Program Restore Information", the change

is not reflected in a program in the transfer source SD memory card.

Precautions when writing only program restoration information The initial global label value file and initial local label value file are also written at writing only program restoration information.

1. Check that SM386 (Program restoration information write status LED control setting mode) is turned on (without LED flashing).

2. Set "AFA0H" to SD384 (System operation setting).

3. Turn off and on SM384 (System operation setting request). SM384 is automatically turned off. If writing has failed, SM385 (System operation setting error) is turned on and an error is stored in SD385 (System operation setting error cause).

4. Check that SM385 is off, and turn off or reset the CPU module. 5. The FUNCTION LED flashes and SM386 turns off (LED flashing). b1 of SD1488 (Debug

function usage status) is turned on.

8 APPX Appendix 10 Program Restoration Information Write Selection

A

Appendix 11 List of Available SQL Commands for CPU Module Database Access Function

This section describes the available SQL commands for the CPU module database access function.

Data definition

CREATE TABLE This command creates a table in the database.

Option

Application example To create table1 (fld1 (integer type, primary key (key name: pk1)), fld2 (integer type), fld3 (character string type (120

characters, NOT NULL))) CREATE TABLE "table1" ("fld1" INT PRIMARY KEY "pk1", "fld2" INT, "fld3" NLSCHAR (120) NOT NULL); To create table2 (fld1 (integer type, foreign key (key name: fk1, reference: table1 fld1)), fld2 (BOOLEAN type), fld3 (single-

precision real number type)) CREATE TABLE "table2" ("fld1" INT FOREIGN KEY "fk1" REFERENCES "table1" ("fld1"), "fld2" BOOLEAN, "fld3" REAL);

Precautions To define the NLSCHAR field, check the data size of the field. Define the NLSCHAR type with the size specified in NLSCHAR = (n+1) 3*1 since it needs to be defined with the data

size. For example, the definition is 39 characters for "fld3" NLSCHAR (120) of table1 in the application example. *1 n indicates the number of characters.

DROP TABLE This command deletes the specified table in the database.

Application example To delete table 1 DROP TABLE "table1";

Syntax CREATE TABLE [table name] ([field name] [data type] [option], [field name] [data type] [option], , [field name] [data type] [option]);

Item Description Syntax Primary key constraint Maintains the uniqueness of a value stored in the field. (NULL is not available.)

Only one primary key constraint can be set per table. Key names must be up to 16 single-byte alphabetical characters and are case sensitive.

PRIMARY KEY [key name]

Foreign key constraint Refers to the value of a field of another table. Only the field with the name where the primary key constraint of another table is set can be set as the reference field. (Always set the same field name to the reference field and own field.) Key names must be up to 16 single-byte alphabetical characters and are case sensitive.

FOREIGN KEY [key name] REFERENCES [reference table name] ([reference field name])

NOT NULL constraint Disables storing NULL values. (Always store a value other than NULL.) NOT NULL

Syntax DROP TABLE [table name];

APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function 689

69

CREATE INDEX This command creates an index in the specified field of the specified table in the database. Index names must be up to 16 single-byte alphabetical characters and are case sensitive.

Application example To set the index "idx1" to fld2 of table1 CREATE INDEX "idx1" ON "table1" ("fld2");

DROP INDEX This command deletes the specified index in the database.

Application example To delete the "idx1" index in table1 DROP INDEX "idx1" ON "table1";

EMPTY TABLE This command deletes all records of the specified table in the database.

Application example To delete all records in table1 EMPTY "table1";

Syntax CREATE INDEX [index name] ON [table name] (field name);

Syntax DROP INDEX [index name] ON [table name];

Syntax EMPTY [table name];

0 APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function

A

Data operation

INSERT This command adds a record to the specified table in the database.

*1 Input null not to store the field value. *2 When the field value is a character string, enclose it in single quotation marks (').

Application example To add records to all fields INSERT INTO "table1" VALUES (11, null, 'abc'); To add records to the specified fields INSERT INTO "table1" ("fld1", "fld3") VALUES (12, 'efg');

SELECT This command outputs a value of the specified record from the specified table in the database.

Option 1

Option 2*1

*1 Multiple options can be used.

Application example To output all record values in table1 (all fields of table1) SELECT * FROM table1; To output all record values in table1 (fld1 and fld2 in table1) SELECT "fld1", "fld2" FROM table1; To output all records excluding the overlapped records in fld1 of table1 SELECT DISTINCT "fld1" FROM table1;

Syntax*1*2

To add records to all fields INSERT INTO [table name] VALUES (field 1 value, field 2 value, , field X value); To add records to the specified fields

INSERT INTO [table name] (field specification 1, field specification 2, , field specification X) VALUES (field 1 value, field 2 value, , field X value);

Syntax To output all values

SELECT [output target field or numeric expression] FROM [table name] [option]; To output a value excluding overlapped values

SELECT DISTINCT [output target field or numeric expression] FROM [table name] [option 1] [option 2];

Item Description Syntax INNER JOIN Performs inner join. (Records that exist in the specified both

tables are output.) SELECT [output target field or numeric expression] FROM [table name 1] INNER JOIN [table name 2] ON [combining condition];

LEFT JOIN Performs outer join. (All records that exist in [table name 1] are output.)

SELECT [output target field or numeric expression] FROM [table name 1] LEFT JOIN [table name 2] ON [combining condition];

RIGHT JOIN Performs outer join. (All records that exist in [table name 2] are output.)

SELECT [output target field or numeric expression] FROM [table name 1] RIGHT JOIN [table name 2] ON [combining condition];

FULL JOIN Performs outer join. (All records that exist in both of specified tables are output.)

SELECT [output target field or numeric expression] FROM [table name 1] FULL JOIN [table name 2] ON [combining condition];

Item Description WHERE Specifies the condition to obtain a specific record. ( Page 693 WHERE).

GROUP BY Specifies the grouping condition of the record to be obtained. ( Page 693 GROUP BY).

HAVING Specifies the condition to narrow down a search using the result of the aggregate function. ( Page 693 HAVING).

ORDER BY Specifies the sorting condition of the record to be obtained. ( Page 694 ORDER BY).

APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function 691

69

UPDATE This command updates the value of the specified record of the specified table in the database.

*1 When the field value is a character string, enclose it in single quotation marks (').

Option

Application example To store a value in "fld1" and "fld3" of the record of "fld2" field value = 935 of table1 (storing fld1 = 20, fld3 = abc) UPDATE table1 SET "fld1" = 20, "fld3" = 'abc' WHERE "fld2" = 935;

DELETE This command deletes a record of the specified table in the database.

*1 When the field value is a character string, enclose it in single quotation marks (').

Option

Application example To delete all records in table1 DELETE "table1"; To delete the record of the fld3 value = abc in table1 DELETE "table1" WHERE "fld3" = 'abc';

Syntax*1

UPDATE [table name] SET [field name = assigned value], [field name = assigned value], , [field name = assigned value] [option];

Item Description Syntax WHERE Specifies the condition to obtain (process) a specific record

( Page 693 WHERE). WHERE

Syntax*1

DELETE [table name] [option];

Item Description Syntax WHERE Specifies the condition to obtain (process) a specific record

( Page 693 WHERE). WHERE

2 APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function

A

Clause

WHERE This command conducts search with conditions.

Operators that can be used in [condition]

Application example To output a record with the fld1 value of 1 to 100 of table1 SELECT * FROM "table1" WHERE "fld1" BETWEEN 1 AND 100; To output fld1 and fld3 of the record with the fld3 value other than abc of table1 SELECT "fld1", "fld3" FROM "table1" WHERE NOT "fld3" = 'abc';

GROUP BY This command groups elements.

Application example To group Table1 according to the value of fld1 and aggregate the number of records SELECT COUNT(*) FROM "table1" GROUP BY "fld1";

HAVING This command narrows down a search using the result of the aggregate function.

Application example To output only the groups whose total value is 50 or less SELECT SUM ("fld2") FROM "table1" GROUP BY "fld1" HAVING SUM ("fld2") < 50;

Syntax To specify a condition

WHERE [condition] To specify an exception

WHERE NOT [condition]; To specify two conditions with AND

WHERE [condition 1] AND [condition 2]; To specify two conditions with OR

WHERE [condition 1] OR [condition 2];

Item Description Syntax = Equals [numeric expression 1] = [numeric expression 2]

!= Not equal to [numeric expression 1] != [numeric expression 2]

<> Not equal to [numeric expression 1] <> [numeric expression 2]

> Greater than [numeric expression 1] > [numeric expression 2]

>= Greater than or equal to [numeric expression 1] >= [numeric expression 2]

< Less than [numeric expression 1] < [numeric expression 2]

<= Less than or equal to [numeric expression 1] <= [numeric expression 2]

IN Brings the conditions to be set together. IN ([numeric expression 1], [numeric expression 2], , [numeric expression 3])

BETWEEN Specifies the range to be output. [numeric expression 1] BETWEEN [numeric expression 2] AND [numeric expression 3]

Syntax GROUP BY [numeric expression]

Syntax HAVING [numeric expression]

APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function 693

69

ORDER BY This command sorts output.

Application example To sort and output fld1 and fld2 of all records in ascending order of the fld1 value from table1 SELECT "fld1", "fld2" FROM "table1" ORDER BY "fld1" ASC;

Syntax Ascending

ORDER BY [numeric expression] ASC Descending

ORDER BY [numeric expression] DESC

4 APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function

A

Aggregate function

AVG This command obtains a mean value.

Application example To obtain the mean value of fld1 from table1 (including overlapped values) SELECT AVG ("fld1") FROM "table1"; To obtain the mean value of fld1 from table1 (excluding overlapped values) SELECT AVG (DISTINCT "fld1") FROM "table1";

COUNT This command aggregates the number of records.

Application example To obtain the number of records of fld1 from table1 (including overlapped values) SELECT COUNT ("fld1") FROM "table1"; To obtain the number of records of fld1 from table1 (excluding overlapped values) SELECT COUNT (DISTINCT "fld1") FROM "table1";

MAX This command obtains a maximum value.

Application example To obtain the maximum value of fld1 from table1 SELECT MAX ("fld1") FROM "table1";

MIN This command obtains a minimum value.

Application example To obtain the minimum value of fld1 from table1 SELECT MIN ("fld1") FROM "table1";

SUM This command obtains the total.

Application example To obtain the total of fld1 from table1 (including overlapped values) SELECT SUM ("fld1") FROM "table1"; To obtain the total of fld1 from table1 (excluding overlapped values) SELECT SUM (DISTINCT "fld1") FROM "table1";

Syntax AVG ([numeric expression])

Syntax COUNT [target]

Syntax MAX ([numeric expression])

Syntax MIN ([numeric expression])

Syntax SUM ([numeric expression])

APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function 695

69

Arithmetic function

ABS This command obtains an absolute value.

Application example To obtain the absolute value of fld1 from table1 SELECT ABS ("fld1") FROM "table1";

ACOS This command obtains an arc cosine.

Application example To obtain the arc cosine of fld1 from table1 SELECT ACOS ("fld1") FROM "table1";

ASIN This command obtains an arc sine.

Application example To obtain the arc sine of fld1 from table1 SELECT ASIN ("fld1") FROM "table1";

ATAN This command obtains an arc tangent.

Application example To obtain the arc tangent of fld1 from table1 SELECT ATAN ("fld1") FROM "table1";

ATAN2 This command obtains an arc tangent.

*1 This syntax is ATAN2 (y, x).

Application example To obtain an arc tangent of fld1/fld2 from table1 SELECT ATAN2 ("fld1", "fld2") FROM "table1";

Syntax ABS ([numeric expression])

Syntax ACOS ([numeric expression])

Syntax ASIN ([numeric expression])

Syntax ATAN ([numeric expression])

Syntax ATAN2 ([numeric expression 1], [numeric expression 2])*1

6 APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function

A

CEILING This command obtains the smallest integer greater than or equal to the specified numeric expression.

Application example To obtain the smallest integer greater than or equal to the fld1 value from table1 SELECT CEILING ("fld1") FROM "table1";

COS This command obtains a cosine.

Application example To obtain the cosine of fld1 from table1 SELECT COS ("fld1") FROM "table1";

COT This command obtains a cotangent.

Application example To obtain the cotangent of fld1 from table1 SELECT COT ("fld1") FROM "table1";

DEGREES This command obtains degrees from radians.

Application example To obtain degrees of fld1 from table1 SELECT DEGREES ("fld1") FROM "table1";

EXP This command obtains an exponent value. (It calculates e raised to the power of [numeric expression].)

Application example To obtain e raised to the power of fld1 from table1 SELECT EXP ("fld1") FROM "table1";

Syntax CEILING ([numeric expression])

Syntax COS ([numeric expression])

Syntax COT ([numeric expression])

Syntax DEGREES ([numeric expression])

Syntax EXP ([numeric expression])

APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function 697

69

FLOOR This command obtains the largest integer less than or equal to the specified numeric expression.

Application example To obtain the largest integer less than or equal to the fld1 value from table1 SELECT FLOOR ("fld1") FROM "table1";

LOG This command obtains a natural logarithm.

Application example To obtain the natural logarithm of fld1 from table1 SELECT LOG ("fld1") FROM "table1"; To obtain the decadic logarithm of fld1 from table1 SELECT LOG10 ("fld1") FROM "table1";

POW This command raises a value. (It raises [numeric expression 1] to the power of [numeric expression 2].)

Application example To obtain fld1 raised to the power of fld2 from table1 SELECT POW ("fld1", "fld2") FROM "table1";

RADIANS This command obtains radians from degrees.

Application example To obtain radians of fld1 from table1 SELECT RADIANS ("fld1") FROM "table1";

ROUND This command rounds a value. (The value of [numeric expression 1] is rounded off to the nth decimal place.)* 1

*1 Add one to the value specified in n = [numeric expression 2].

Application example To obtain the value of fld1 rounded off to the third decimal place from table1. SELECT ROUND ("fld1", 2) FROM "table1";

Syntax FLOOR ([numeric expression])

Syntax To obtain a natural logarithm

LOG ([numeric expression]) To obtain a decadic logarithm

LOG10 ([numeric expression])

Syntax POW ([numeric expression 1], [numeric expression 2]) When [numeric expression 1] = 0, [numeric expression 2] must be greater than 0. When [numeric expression 1] is less than 0, [numeric expression 2] must be an integer.

Syntax RADIANS ([numeric expression])

Syntax ROUND ([numeric expression 1], [numeric expression 2])

8 APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function

A

SIGN This command obtains a sign.

Application example To obtain the sign of fld1 from table1 SELECT SIGN ("fld1") FROM "table1";

SIN This command obtains a sine.

Application example To obtain the sine of fld1 from table1 SELECT SIN ("fld1") FROM "table1";

SQRT This command obtains a square root.

Application example To obtain the square root of fld1 from table1 SELECT SQRT ("fld1") FROM "table1";

TAN This command obtains a tangent.

Application example To obtain the tangent of fld1 from table1 SELECT TAN ("fld1") FROM "table1";

Syntax SIGN ([numeric expression])

Syntax SIN ([numeric expression])

Syntax SQRT ([numeric expression])

Syntax TAN ([numeric expression])

APPX Appendix 11 List of Available SQL Commands for CPU Module Database Access Function 699

70

Appendix 12Added and Enhanced Functions This section describes added and enhanced functions of the CPU module and the engineering tool, as well as the firmware versions of the CPU module and software versions of the engineering tool corresponding to the functions.

The firmware update function enables users to update the firmware versions of the CPU module. For the target CPU modules and how to update the firmware version, refer to the following. MELSEC iQ-R Module Configuration Manual

: Supported from the first released product, : Not supported, : Function usable regardless of the software version

Added or enhanced function F: Firmware version of the CPU module S: Software version of the engineering tool O: Version of the other tools

Reference

R00/R01/R02CPU Rn(EN)CPU LED specifications (enhanced use of the FUNCTION LED)

F: S: 1.040S

F: 06 S: 1.005F

Page 172 LED display setting

Memory dump function F: *1

S: 1.040S F: 06 S: 1.005F

Page 304 DEBUG FUNCTION

Real-time monitor function F: S: 1.040S

F: 06 S: O: 1.40S*2

Page 196 MONITOR FUNCTION GX LogViewer Version 1 Operating Manual

CC-Link IE Controller Network function of the RJ71EN71

F: S: 1.040S

F: 06 S: 1.005F

MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup)

MELSEC iQ-R CC-Link IE Controller Network User's Manual (Application)

Mounting of MELSEC iQ-R series modules occupying two slots

F: S: 1.040S

F: 08 S:

For the applicable modules, refer to the following. MELSEC iQ-R Module Configuration Manual

MELSEC-Q series MELSECNET/H network module

F: S: 1.040S

F: 10 S: 1.010L

For the applicable modules, refer to the following. MELSEC iQ-R Module Configuration Manual

SFC support F: S: 1.040S O: 1.49B*2*3*4

F: 12 S: 1.015R O: 1.49B*2*3*4

MELSEC iQ-R Programming Manual (Program Design)

Extended SRAM cassette (NZ2MC-16MBS) F: 12 S: 1.015R

Page 67 Extended SRAM Cassette Page 127 Device/label memory area setting

iQ Sensor Solution functions supporting Ethernet Automatic detection of connected device Communication setting reflection Sensor parameter read/write

F: S: 1.040S

F: 12 S: 1.015R

iQ Sensor Solution Reference Manual

iQ Sensor Solution functions supporting CC-Link IE Field Network Automatic detection of connected device Communication setting reflection Sensor parameter read/write

F: S: 1.040S

F: 12 S:

iQ Sensor Solution Reference Manual

Daylight saving time function F: S: 1.040S

F: 17 S: 1.020W

Page 151 Daylight Saving Time Function

Sequence scan synchronization sampling function F: S: 1.040S

F: 17 S: 1.020W

Page 405 SEQUENCE SCAN SYNCHRONIZATION SAMPLING FUNCTION

Duplication check for POU F: S: 1.040S

F: 19 S: 1.022Y

GX Works3 Operating Manual

Background processing of program transfer (writing the program restoration information) during changing a program online

F: S: 1.040S

F: 20 S: 1.022Y

GX Works3 Operating Manual

CPU module data backup/restoration function F: 22 S:

Page 346 CPU MODULE DATA BACKUP/ RESTORATION FUNCTION

iQ Sensor Solution functions supporting CC-Link IE Field Network Data backup/restoration (128 modules

maximum)*5

F: S: 1.040S

F: 22 S:

iQ Sensor Solution Reference Manual

iQ Sensor Solution functions supporting CC-Link IE Field Network Data backup/restoration (256 modules

maximum)*5

F: 14 S: 1.060N

F: 46 S: 1.060N

iQ Sensor Solution Reference Manual

0 APPX Appendix 12 Added and Enhanced Functions

A

iQ Sensor Solution functions supporting CC-Link- AnyWireASLINK Data backup/restoration*5

F: S: 1.040S

F: 22 S:

iQ Sensor Solution Reference Manual

Redundant power supply system F: S: 1.040S

F: 22 S: 1.025B

MELSEC iQ-R Module Configuration Manual

Firmware update function (Firmware update using the engineering tool)

F: 14 S: 1.060N

F: 46 S: 1.060N

MELSEC iQ-R Module Configuration Manual

Firmware update function (Firmware update using an SD memory card)

F: *1

S: For RnCPU F: 23 S: For RnENCPU F: 38 S:

MELSEC iQ-R Module Configuration Manual

External input/output forced on/off function F: S: 1.040S

F: 25 S: 1.030G

Page 204 External Input/Output Forced On/Off Function

iQ Sensor Solution functions supporting AnyWireASLINK Automatic detection of connected device Communication setting reflection Sensor parameter read/write

F: S: 1.040S

F: 25 S: 1.030G

iQ Sensor Solution Reference Manual

iQ Sensor Solution functions supporting Ethernet Data backup/restoration*5

F: S:

F: 25 S:

CC-Link IE Field Network Basic F: S: 1.040S

F: 25 S: 1.030G

CC-Link IE Field Network Basic Reference Manual

Multiple CPU system F: S: 1.040S

For RnCPU F: S: 1.000A For RnENCPU F: 25 S: 1.032J

MELSEC iQ-R Module Configuration Manual

CPU module database access function F: 28 S: 1.035M

Page 324 CPU Module Database Access (from External Device) Function

"Use MC/MCR to Control EN" of subroutine-type FB

F: S: 1.040S

F: 28 S: 1.035M

GX Works3 Operating Manual MELSEC iQ-R Programming Manual (Program

Design)

Program restoration information write selection F: S: 1.040S

F: 31 S: 1.040S

Page 686 Program Restoration Information Write Selection

File batch online change of FB files and the global label setting file

F: S: 1.040S

F: 31 S: 1.040S

Page 159 File batch online change

File batch online change when the program memory does not have enough free space

F: S: 1.040S

F: 31 S: 1.040S

Page 159 File batch online change

Storage of logging data in the function memory F: 31 S: O: 1.76E*4

Page 259 Numerical value range for each output type

Data logging file transfer function F: 06*1

S: O: 1.76E*4

F: 31 S: O: 1.76E*4

Page 273 Conditions under which missing data occurs

Error detection invalidation setting F: 05 S:

F: 35 S:

Page 173 Error detection invalidation setting

Local device and label specification for target data/ condition specification of the data logging function

F: 05*1

S: 1.045X O: 1.82L*4

F: 35 S: 1.045X O: 1.82L*4

Page 226 DATA LOGGING FUNCTION

'Communication load status' (Un\G100 to Un\G103)

F: 05 S:

F: 35 S:

MELSEC iQ-R Ethernet User's Manual (Application)

Battery-less option cassette F: 35 S: 1.045X

Page 480 Latch with Battery-less Option Cassette

iQ Sensor Solution functions for CC-Link Data backup/restoration*5

F: 05*1

S: F: 35 S:

iQ Sensor Solution Reference Manual

Online change (SFC block) F: 05*6

S: 1.045X*6 F: 35*7

S: 1.045X*7 MELSEC iQ-R Programming Manual (Program Design)

Added or enhanced function F: Firmware version of the CPU module S: Software version of the engineering tool O: Version of the other tools

Reference

R00/R01/R02CPU Rn(EN)CPU

APPX Appendix 12 Added and Enhanced Functions 701

70

Omission of writing files that are not changed F: 05*8

S: 1.045X*8 F: 35*9

S: 1.045X*9 GX Works3 Operating Manual

Device test with execution conditions F: 06 S: 1.047Z

F: 38 S: 1.047Z

Page 212 Device Test with Execution Conditions

SFC-activated step monitor F: 08 S: 1.050C

F: 40 S: 1.050C

GX Works3 Operating Manual

Event history logging restriction F: 08 S:

F: 40 S:

Page 182 Event history logging restriction

RJ71GN11-T2 F: 11 S: 1.055H

F: 43 S: 1.055H

Page 412 Device List Page 434 Link Direct Device MELSEC iQ-R CC-Link IE TSN User's Manual

(Application)

Motion module (RD78G4, RD78G8, RD78G16, RD78G32, RD78G64)

F: 12 S: 1.056J

F: 44 S: 1.056J

Page 434 Link Direct Device MELSEC iQ-R Motion Module User's Manual

(Application)

Motion module (RD78GHV, RD78GHW) F: 14 S: 1.060N

F: 46 S: 1.060N

Page 434 Link Direct Device MELSEC iQ-R Motion Module User's Manual

(Application)

Extension of points for CC-Link IE Controller Network

F: 11 S: 1.055H

F: 43 S: 1.055H

Page 412 Device List Page 434 Link Direct Device MELSEC iQ-R CC-Link IE Controller Network

User's Manual (Application)

Online Change F: S: 1.040S

F: S: 1.000A

Page 155 Online Change

Data communications between CPU modules F: S: 1.040S

F: S: 1.000A

Page 368 MULTIPLE CPU SYSTEM FUNCTION

Page 378 Data Communication Between CPU Modules

Multiple CPU synchronous interrupt (I45) F: S: 1.040S

F: S: 1.000A

Page 368 MULTIPLE CPU SYSTEM FUNCTION

Inter-module synchronous interrupt (I44) F: S: 1.040S

F: S: 1.000A

MELSEC iQ-R Inter-Module Synchronization Function Reference Manual

FB hierarchy information F: 14 S: 1.060N

F: 46 S: 1.060N

GX Works3 Operating Manual

MELSEC iQ-R series MELSECNET/H network module

F: 16 S: 1.063R

F: 48 S: 1.063R

MELSEC iQ-R Module Configuration Manual MELSEC iQ-R MELSECNET/H Network

Module User's Manual (Application)

CC-Link IE TSN network synchronous communication

F: 18 S: 1.065T

F: 50 S: 1.065T

MELSEC iQ-R CC-Link IE TSN User's Manual (Application)

Function memory capacity increased to 20480K bytes, file size unit (cluster size) increased to 8192 bytes.

F: 50*10

S: Page 62 Hardware specifications Page 134 File size unit based on memory area

Saving of device/label data write operation histories of the event history function

F: 50*10

S: 1.065T Page 183 Device/label data write operation saving

Simultaneous execution of up to 10 data loggings when the storage destination of data logging files is the function memory

F: 50*10

S: 1.065T Page 259 Numerical value range for each

output type CPU Module Logging Configuration Tool

Version 1 Operating Manual (MELSEC iQ-R Series)

MELSEC iQ-R series recorder module F: 50*10

S: 1.065T MELSEC iQ-R Module Configuration Manual MELSEC iQ-R System Recorder User's Manual

(Startup) MELSEC iQ-R System Recorder User's Manual

(Application)

Recording function F: 50*10

S: 1.065T MELSEC iQ-R System Recorder User's Manual

(Startup) MELSEC iQ-R System Recorder User's Manual

(Application)

Added or enhanced function F: Firmware version of the CPU module S: Software version of the engineering tool O: Version of the other tools

Reference

R00/R01/R02CPU Rn(EN)CPU

2 APPX Appendix 12 Added and Enhanced Functions

A

Data collection instruction (DATATRG) F: 50*10

S: 1.065T MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

CSV file format for the storage format of data logging files

F: 53 S: O: 1.112R*4

Page 242 Number of records CPU Module Logging Configuration Tool

Version 1 Operating Manual (MELSEC iQ-R Series)

"Condition specification" for the file switching timing for data logging setting

F: 53 S: O: 1.112R*4

Page 268 File switching condition CPU Module Logging Configuration Tool

Version 1 Operating Manual (MELSEC iQ-R Series)

Addition of device value to the data logging storage file name

F: 53 S: O: 1.112R*4

Page 269 Storage file CPU Module Logging Configuration Tool

Version 1 Operating Manual (MELSEC iQ-R Series)

MELSEC iQ-R series camera recorder module F: 55*10

S: 1.072A MELSEC iQ-R Module Configuration Manual MELSEC iQ-R System Recorder User's Manual

(Startup) MELSEC iQ-R System Recorder User's Manual

(Application)

Program start/stop F: 24 S: 1.075D

F: 57 S: 1.075D

GX Works3 Operating Manual

Specified program monitor F: 24 S: 1.075D

F: 57 S: 1.075D

Page 202 Specified Program Monitor GX Works3 Operating Manual

Phase processing instructions F: 24 S: 1.075D

F: 57 S: 1.075D

MELSEC iQ-R Programming Manual (CPU Module Instructions, Standard Functions/Function Blocks)

Label memory read/write F: 24 S: 1.075D

F: 57 S: 1.075D

GX Works3 Operating Manual

Copying/cutting across data logging settings for a data setting item

F: S: O: 1.118X*4

F: S: O: 1.118X*4

CPU Module Logging Configuration Tool Version 1 Operating Manual (MELSEC iQ-R Series)

System monitoring information (SD2000 to SD2036)

F: 24 S:

F: 57 S:

Page 639 System monitoring information

CC-Link TSN motion module inter-module synchronization function

F: 24 S: 1.075D

F: 57 S: 1.075D

MELSEC iQ-R Motion Module User's Manual (Network)

Scan time clear F: 26 S: 1.080J

F: 59 S: 1.080J

Page 588 Fixed scan function information GX Works3 Operating Manual

RJ71GN11-EIP F: 29 S: 1.082L

F: 62 S: 1.082L

Page 434 Link Direct Device MELSEC iQ-R CC-Link IE TSN Plus Master/

Local Module User's Manual

Scan time measurement F: 29 S: 1.082L

F: 62 S: 1.082L

Page 197 Scan Time Measurement GX Works3 Operating Manual

Write-protect function for device data (from outside the CPU module)

F: 30 S: 1.085P

F: 63 S: 1.085P

Page 401 Write-Protect Function for Device Data (from Outside the CPU Module)

Recording function (SFC device sampling) F: 65 S: 1.090U

MELSEC iQ-R System Recorder User's Manual (Startup)

MELSEC iQ-R System Recorder User's Manual (Application)

Co-recording function F: 32 S: 1.090U

F: 65 S: 1.090U

MELSEC iQ-R System Recorder Co-recording Function Reference Manual

Added or enhanced function F: Firmware version of the CPU module S: Software version of the engineering tool O: Version of the other tools

Reference

R00/R01/R02CPU Rn(EN)CPU

APPX Appendix 12 Added and Enhanced Functions 703

70

*1 The R00CPU is excluded. *2 This indicates the compatible software version of GX LogViewer. *3 Step relays (BLn\Sn) can be specified with CPU Module Logging Configuration Tool or GX LogViewer. *4 This indicates the compatible software version of CPU Module Logging Configuration Tool. *5 Data is backed up or restored by using programs (special relay and special register). *6 Online change (inactive SFC block) is supported in F: , S: 1.040S. *7 Online change (inactive SFC block) is supported in F: 28, S: 1.035M. *8 When writing to the SD memory card, it is supported in F: 11, S: 1.055H. *9 When writing to the SD memory card, it is supported in F: 43, S: 1.055H. *10 Supported when the 3rd and 4th digits from the left of CPU module production information are as follows.

CPU module 3rd and 4th digits from left of production information R04CPU "19" or later

R08CPU "20" or later

R16CPU "20" or later

R32CPU "17" or later

R120CPU "17" or later

R04ENCPU "32" or later

R08ENCPU "30" or later

R16ENCPU "27" or later

R32ENCPU "30" or later

R120ENCPU "22" or later

4 APPX Appendix 12 Added and Enhanced Functions

A

MEMO

APPX Appendix 12 Added and Enhanced Functions 705

70

INDEX

Symbols "$MELPRJ$" folder . . . . . . . . . . . . . . . . . . . . . 130

A Accuracy of constant scan . . . . . . . . . . . . . . . . . 74 Accuracy of timers . . . . . . . . . . . . . . . . . . . . . 424 Annunciator (F). . . . . . . . . . . . . . . . . . . . . . 65,417 ASCII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459

B Battery. . . . . . . . . . . . . . . . . . . . . . . . . . 31,33,40 BATTERY LED. . . . . . . . . . . . . . . . . . . . . . . 31,33 Battery-less option cassette . . . . . . . . . . . . . . . . 67 Behavior at the time of a transition to RUN . . . . 283 Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 Block number . . . . . . . . . . . . . . . . . . . . . . . . . 443 Block switching method . . . . . . . . . . . . . . . . . . 443 BOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 Boot operation . . . . . . . . . . . . . . . . . . . . . . . . 191 Buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . 23

C CARD ACCESS LED. . . . . . . . . . . . . . . . 29,31,33 CARD READY LED. . . . . . . . . . . . . . . . . 29,31,33 CC-Link IE Controller Network-equipped module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 CC-Link IE Field Network-equipped master/local module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 CC-Link IE TSN master/local module . . . . . . . . . 24 Character string constant . . . . . . . . . . . . . . . . . 488 Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461 Clearing file registers. . . . . . . . . . . . . . . . . . . . 444 Constant . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Constant scan . . . . . . . . . . . . . . . . . . . . . . . 64,73 Continuous logging . . . . . . . . . . . . . . . . . . . . . 237 Controlled module. . . . . . . . . . . . . . . . . . . . . . 369 COUNTER . . . . . . . . . . . . . . . . . . . . . . . . 459,460 Counter . . . . . . . . . . . . . . . . . . . . . . . . . . 459,460 Counter (C) . . . . . . . . . . . . . . . . . . . . . . . . 65,429 CPU buffer memory . . . . . . . . . . . . . . . . . . 62,131 CPU buffer memory access device . . . . . . . . 66,438 CPU module. . . . . . . . . . . . . . . . . . . . . . . . 62,571 CPU parameter. . . . . . . . . . . . . . . . . . . . . . . . . 53 CPU parameters . . . . . . . . . . . . . . . . . . . . . . . 678

D Data logging . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Data memory . . . . . . . . . . . . . . . . . . . . . . . 62,130 Data register (D) . . . . . . . . . . . . . . . . . . . . . 65,432 Data type . . . . . . . . . . . . . . . . . . . . . 459,460,461 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Database function . . . . . . . . . . . . . . . . . . . . . . 315 Debug function . . . . . . . . . . . . . . . . . . . . . . . . 304 Decimal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Decimal constant (K) . . . . . . . . . . . . . . . . . . . . 487 Device area . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Device assignment . . . . . . . . . . . . . . . . . . . . . 457

Device initial value . . . . . . . . . . . . . . . . . . . . . .483 Device supporting iQSS . . . . . . . . . . . . . . . . . . .24 Device/label access service processing . . . . . . . .75 Device/label memory. . . . . . . . . . . . . . . . . . 62,126 DINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 Double word [signed] . . . . . . . . . . . . . . . . . . . .459 Double word [unsigned]/bit string [32 bits] . . . . . .459 Double-precision real number . . . . . . . . . . 459,488 DWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459

E Edge relay (V) . . . . . . . . . . . . . . . . . . . . . . 65,420 END processing . . . . . . . . . . . . . . . . . . . . . . . . .71 Error clear . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 ERROR CODES. . . . . . . . . . . . . . . . . . . . . . . .500 ERROR LED . . . . . . . . . . . . . 27,29,31,33,54,493 Ethernet interface module with built-in CC-Link IE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Ethernet port . . . . . . . . . . . . . . . . .27,29,31,33,63 Ethernet-equipped module. . . . . . . . . . . . . . . . . .24 Event execution type program . . . . . . . . . . . . . . .91 Event history . . . . . . . . . . . . . . . . . . . . . . . . . .177 Event history file . . . . . . . . . . . . . . . . . . . . . . . .179 Extended SRAM cassette . . . . . . . . . . . . . . . 41,67 External dimensions . . . . . . . . . . . . . . . .63,67,571

F File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 File password. . . . . . . . . . . . . . . . . . . . . . . . . .399 File register (R/ZR) . . . . . . . . . . . . . . . . . . . 65,443 File register setting . . . . . . . . . . . . . . . . . . . . . .444 File registers common to all programs. . . . . . . . .444 File storage area . . . . . . . . . . . . . . . . . . . . . . . .62 Fixed scan execution mode . . . . . . . . . . . . . . . . .89 Fixed scan execution type program . . . . . . . . . . .86 Fixed scan interval . . . . . . . . . . . . . . . . . . . . . . .87 Function (FUN). . . . . . . . . . . . . . . . . . . . . . . . .458 Function block . . . . . . . . . . . . . . . . . . . . . . . . . .51 Function block (FB). . . . . . . . . . . . . . . . . . . . . .458 Function device . . . . . . . . . . . . . . . . . . . . . . . .433 Function input (FX) . . . . . . . . . . . . . . . . . . . 65,433 FUNCTION LED. . . . . . . . . . . . . . . . . 27,29,31,33 Function memory . . . . . . . . . . . . . . . . . . . . 62,130 Function output (FY) . . . . . . . . . . . . . . . . . . 65,433 Function register (FD) . . . . . . . . . . . . . . . . . 65,433

G Generic data type (ANY type) . . . . . . . . . . . . . .461 Global device . . . . . . . . . . . . . . . . . . . . . . . . . .451 Global label . . . . . . . . . . . . . . . . . . . .457,458,461 Global pointer. . . . . . . . . . . . . . . . . . . . . . . . . .447

H Hexadecimal . . . . . . . . . . . . . . . . . . . . . . . . . .487 Hexadecimal constant (H) . . . . . . . . . . . . . . . . .487 High-speed internal timer interrupt 1 (I49) . . . . . . .64 High-speed internal timer interrupt 2 (I48) . . . . . . .64 High-speed timer . . . . . . . . . . . . . . . . . . . . . . .422

6

I

High-speed timer (T/ST) . . . . . . . . . . . . . . . . . 422

I I/O No. specification device (U) . . . . . . . . . . . . 451 I/O refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Index modification . . . . . . . . . . . . . . . . . . . . . . 439 Index register (Z) . . . . . . . . . . . . . . . . . . . . . . . 65 Index register setting . . . . . . . . . . . . . . . . . . . . 440 Indirect specification . . . . . . . . . . . . . . . . . . . . 456 Initial execution type program. . . . . . . . . . . . . . . 85 Initial processing (when powered on) . . . . . . . . . 70 Initial processing (when switched to RUN) . . . . . . 70 Initial scan time. . . . . . . . . . . . . . . . . . . . . . . . . 72 Initial scan time monitoring time . . . . . . . . . . . . . 72 Initializing the CPU module . . . . . . . . . . . . . . . . 46 Input (X). . . . . . . . . . . . . . . . . . . . . . . . . . . 65,416 INT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 Inter-module synchronous interrupt (I44) . . . . . . . 64 Internal buffer . . . . . . . . . . . . . . . . . . . . . . . . . 265 Internal current consumption (5VDC) . . . . . . . . . 63 Internal relay (M). . . . . . . . . . . . . . . . . . . . . 65,417 Interrupt factor . . . . . . . . . . . . . . . . . . . . . . . . 450 Interrupt pointer (I) . . . . . . . . . . . . . . . . . . . 65,449 Interrupt pointer number . . . . . . . . . . . . . . . . . 450 Interrupt priority . . . . . . . . . . . . . . . . . . . . . . . 114 Interrupt using the internal timer (I28 to I31) . . . . . 64 IP filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

J Jump instructions . . . . . . . . . . . . . . . . . . . . . . 447

L Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Label area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Label initial value . . . . . . . . . . . . . . . . . . . . . . 483 Latch (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Latch (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Latch clear . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 Latch label area . . . . . . . . . . . . . . . . . . . . . . . . 62 Latch relay (L) . . . . . . . . . . . . . . . . . . . . . . 65,417 LCOUNTER . . . . . . . . . . . . . . . . . . . . . . . 459,460 Librarization of programs . . . . . . . . . . . . . . . . . . 95 Link direct device . . . . . . . . . . . . . . . . . . . . 65,434 Link refresh . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Link register (W) . . . . . . . . . . . . . . . . . . . . . 65,432 Link relay (B) . . . . . . . . . . . . . . . . . . . . . . . 65,417 Link special register (SW) . . . . . . . . . . . . . . 65,432 Link special relay (SB) . . . . . . . . . . . . . . . . . 65,419 Local label . . . . . . . . . . . . . . . . . . . . 457,458,461 Local pointer. . . . . . . . . . . . . . . . . . . . . . . . . . 448 LOGTRG instruction . . . . . . . . . . . . . . . . . . . . 240 LOGTRGR instruction . . . . . . . . . . . . . . . . . . . 296 Long counter . . . . . . . . . . . . . . . . . . . . . . 459,460 Long counter (LC) . . . . . . . . . . . . . . . . . . . . 65,429 Long index register (LZ). . . . . . . . . . . . . . . . . . . 65 Long retentive timer . . . . . . . . . . . . . . . . . 459,460 Long retentive timer (LST) . . . . . . . . . . . . . . 65,422 Long timer . . . . . . . . . . . . . . . . . . . . . . . . 459,460 Long timer (LT) . . . . . . . . . . . . . . . . . . . . . . 65,421 Low-speed timer . . . . . . . . . . . . . . . . . . . . . . . 422 Low-speed timer (T/ST) . . . . . . . . . . . . . . . . . . 422 LREAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 LRETENTIVETIMER . . . . . . . . . . . . . . . . . 459,460

LTIMER. . . . . . . . . . . . . . . . . . . . . . . . . . 459,460

M Master control instructions . . . . . . . . . . . . . . . . .446 Maximum counting speed for counters . . . . . . . .431 Memory capacity . . . . . . . . . . . . . . . . . . . . . . . .62 Memory card parameters. . . . . . . . . . . . . . . . . .679 Memory configuration . . . . . . . . . . . . . . . . . . . .124 Memory dump file . . . . . . . . . . . . . . . . . . . . . . .309 Memory dump status. . . . . . . . . . . . . . . . . . . . .310 Module access device . . . . . . . . . . . . . . . . . 65,437 Module extension parameter . . . . . . . . . . . . . . . .53 Module label . . . . . . . . . . . . . . . . . . . . . . . 44,457 Module label assignment area . . . . . . . . . . . . . .445 Module parameter . . . . . . . . . . . . . . . . . . . . . . .53 Momentary power failure . . . . . . . . . . . . . . . . . .123 Monitor function . . . . . . . . . . . . . . . . . . . . . . . .196 Multiple CPU synchronous interrupt . . . . . . . . . .397 Multiple CPU synchronous interrupt (I45) . . . . . . .64 Multiple CPU synchronous interrupt program. . . .397 Multiple CPU system. . . . . . . . . . . . . . . . . . . . .368 Multiple interrupt. . . . . . . . . . . . . . . . . . . . . . . .114 Multiple interrupt function. . . . . . . . . . . . . . . . . .114

N Nesting (N) . . . . . . . . . . . . . . . . . . . . . . . . 66,446 Nesting structure . . . . . . . . . . . . . . . . . . . . . . .446 Network No. specification device (J) . . . . . . . . . .451 Non-controlled module . . . . . . . . . . . . . . . . . . .369 Number of array elements . . . . . . . . . . . . . . . . .465 Number of FB files . . . . . . . . . . . . . . . . . . . . . . .64 Number of I/O points. . . . . . . . . . . . . . . . . . . . . .64 NZ2MC-16MBS . . . . . . . . . . . . . . . . . . . . . . . . .67 NZ2MC-1MBS . . . . . . . . . . . . . . . . . . . . . . . . . .67 NZ2MC-2MBS . . . . . . . . . . . . . . . . . . . . . . . . . .67 NZ2MC-4MBS . . . . . . . . . . . . . . . . . . . . . . . . . .67 NZ2MC-8MBS . . . . . . . . . . . . . . . . . . . . . . . . . .67

O Online change . . . . . . . . . . . . . . . . . . . . . . . . .155 Online change (ladder block) . . . . . . . . . . . . . . .155 Output (Y) . . . . . . . . . . . . . . . . . . . . . . . . . 65,416 Output mode at operating status change (STOP to RUN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122 Overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . .488

P Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Parameter No. . . . . . . . . . . . . . . . . . . . . . . . . .677 PAUSE state . . . . . . . . . . . . . . . . . . . . . . . . . .120 PID control. . . . . . . . . . . . . . . . . . . . . . . . . . . .344 POINTER . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 Pointer (P) . . . . . . . . . . . . . . . . . . . . . . . . . 65,447 Pointer setting . . . . . . . . . . . . . . . . . . . . . . . . .449 Priority for interrupt factors. . . . . . . . . . . . . . . . .450 Processing time . . . . . . . . . . . . . . . . . . . . . . . .647 Production information marking . . . . . . 27,29,31,33 Program arrangement change . . . . . . . . . . . . . . .95 Program block . . . . . . . . . . . . . . . . . . . . . . . . .458 Program cache memory . . . . . . . . . . . . . . . . . .125 Program capacity . . . . . . . . . . . . . . . . . . . . . . . .62

707

70

Program execution type . . . . . . . . . . . . . . . . . . . 85 Program file . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Program list monitor . . . . . . . . . . . . . . . . . . . . . 72 Program memory . . . . . . . . . . . . . . . . . . . . 62,125 PROGRAM RUN LED . . . . . . . . . . 27,29,31,33,55 Programmable controller CPU . . . . . . . . . . . . . . 24 Programming language . . . . . . . . . . . . . . . . . 44,64

Q Q6BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

R READY LED. . . . . . . . . . . . . . . . 27,29,31,33,493 REAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 Real constant (E) . . . . . . . . . . . . . . . . . . . . . . 488 Real number. . . . . . . . . . . . . . . . . . . . . . . . . . 488 Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 Refresh data register (RD) . . . . . . . . . . . . . . 66,445 Refresh memory . . . . . . . . . . . . . . . . . . . . . 62,131 Refresh memory setting. . . . . . . . . . . . . . . . . . 445 Remote head module . . . . . . . . . . . . . . . . . . . . 24 Remote operation . . . . . . . . . . . . . . . . . . . . . . 187 Remote password . . . . . . . . . . . . . . . . . . . . . . 399 Remote RESET . . . . . . . . . . . . . . . . . . . . . . . 190 Remote RUN . . . . . . . . . . . . . . . . . . . . . . . . . 187 Remote STOP . . . . . . . . . . . . . . . . . . . . . . . . 187 Reserved area for online change . . . . . . . . . . . 157 Resetting counters . . . . . . . . . . . . . . . . . . . . . 430 Resetting the CPU module. . . . . . . . . . . . . . . . . 54 Retentive timer . . . . . . . . . . . . . . . . . . . . . 459,460 Retentive timer (ST) . . . . . . . . . . . . . . . . . . 65,422 RETENTIVETIMER. . . . . . . . . . . . . . . . . . 459,460 RJ71GN11-EIP (CC-Link IE TSN part) . . . . . . . . 24 RJ71GN11-EIP (EtherNet/IP part). . . . . . . . . . . . 24 RnCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 RnENCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 RnENCPU (CPU part) . . . . . . . . . . . . . . . . . . . . 24 RnENCPU (network part). . . . . . . . . . . . . . . . . . 24 RUN state . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 RUN/STOP/RESET switch. . . . . 27,29,31,33,54,55 RUN-PAUSE contacts . . . . . . . . . . . . . . . . . . . 189

S Saving/restoring of the file register (R) block number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Saving/restoring of the index register (Z, LZ) . . . 112 Scan execution type program. . . . . . . . . . . . . . . 86 Scan monitoring function . . . . . . . . . . . . . . . . . 166 Scan time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Scan time monitoring time . . . . . . . . . . . . . . . . 166 Scan time monitoring time setting . . . . . . . . . . . 166 SD CARD OFF button . . . . . . . . . . . . . . . 29,31,33 SD memory card. . . . . . . . . . . . . . . . . . 42,62,132 SD/RD LED . . . . . . . . . . . . . . . . . . . . 27,29,31,33 Security function . . . . . . . . . . . . . . . . . . . . . . . 399 Security key authentication . . . . . . . . . . . . . . . 399 Serial number method . . . . . . . . . . . . . . . . . . . 443 Setting RUN-PAUSE contacts . . . . . . . . . . . . . 189 Setting time zone . . . . . . . . . . . . . . . . . . . . . . 150 SFC block device (BL) . . . . . . . . . . . . . . . . . 66,451 SFC transition device (TR) . . . . . . . . . . . . . . 66,451 Shift JIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 Signal flow memory. . . . . . . . . . . . . . . . . . . 62,131

Single-precision real number . . . . . . . . . . . 459,488 Special register (SD). . . . . . . . . . . . . . . . . . 65,434 Special relay (SM) . . . . . . . . . . . . . . . . . . . 65,434 SPEED LED. . . . . . . . . . . . . . . . . . . . 27,29,31,33 Stack file . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267 Standby type program. . . . . . . . . . . . . . . . . . . . .95 Station sub ID number. . . . . . . . . . . . . . . . . . . . .24 Step relay (S) . . . . . . . . . . . . . . . . . . . . . . . 65,420 STOP state . . . . . . . . . . . . . . . . . . . . . . . . . . .120 Storage file . . . . . . . . . . . . . . . . . . . . . . . . . . .269 STRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 String [Unicode] . . . . . . . . . . . . . . . . . . . . . . . .459 Structure . . . . . . . . . . . . . . . . . . . . . . . . . 460,466 Structure array . . . . . . . . . . . . . . . . . . . . . . . . .467 Subroutine call instruction . . . . . . . . . . . . . . . . . .98 System clock . . . . . . . . . . . . . . . . . . . . . . . . . .154 System device . . . . . . . . . . . . . . . . . . . . . . . . .433 System label . . . . . . . . . . . . . . . . . . . . . . . . . .457 System parameter . . . . . . . . . . . . . . . . . . . . . . .53 System parameters. . . . . . . . . . . . . . . . . . . . . .677 System switching . . . . . . . . . . . . . . . . . . . . . . .578

T TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 Time setting . . . . . . . . . . . . . . . . . . . . . . . . . . .148 Time zone . . . . . . . . . . . . . . . . . . . . . . . . . . . .150 TIMER. . . . . . . . . . . . . . . . . . . . . . . . . . . 459,460 Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . 459,460 Timer (T) . . . . . . . . . . . . . . . . . . . . . . . . . . 65,421 Timer current value. . . . . . . . . . . . . . . . . . . . . .423 Timer limit setting . . . . . . . . . . . . . . . . . . . . . . .423 Timer time limit value . . . . . . . . . . . . . . . . . . . .423 Tracking transfer . . . . . . . . . . . . . . . . . . . . . . .578 Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . .322 Trigger condition. . . . . . . . . . . . . . . . . . . . . . . .238 Trigger instruction. . . . . . . . . . . . . . . . . . . . . . .240 Trigger logging . . . . . . . . . . . . . . . . . . . . . . . . .237 Troubleshooting by symptom . . . . . . . . . . . . . . .496

U Underflow . . . . . . . . . . . . . . . . . . . . . . . . . . . .488 Unicode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 Unicode text file . . . . . . . . . . . . . . . . . . . . . . . .319 USB port . . . . . . . . . . . . . . . . . . . .27,29,31,33,63 User device . . . . . . . . . . . . . . . . . . . . . . . . . . .416 USER LED. . . . . . . . . . . . . . . . . . . . . 27,29,31,33

W Watchdog timer . . . . . . . . . . . . . . . . . . . . . . . .166 Weight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63,67 WORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 Word [signed]. . . . . . . . . . . . . . . . . . . . . . . . . .459 Word [unsigned]/bit string [16 bits] . . . . . . . . . . .459 WSTRING . . . . . . . . . . . . . . . . . . . . . . . . . . . .459

8

709

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

Japanese manual number: SH-082487-B

2022 MITSUBISHI ELECTRIC CORPORATION

Revision date *Manual number Description July 2022 SH(NA)-082488ENG-A First edition

October 2022 SH(NA)-082488ENG-B Added function Co-recording function Added or modified parts Chapter 9, 23, Section 34.1, 35.2, Appendix 3, 8, 12, COPYRIGHTS

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.

710

CONDITIONS OF USE FOR THE PRODUCT (1) MELSEC 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 ELECTRIC 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 ELECTRIC USER'S, 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 Electric 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 Electric 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 Electric representative in your region.

(3) Mitsubishi Electric shall have no responsibility or liability for any problems involving programmable controller trouble and system trouble caused by DoS attacks, unauthorized access, computer viruses, and other cyberattacks.

711

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 to: (1) Damages caused by any cause found not to be the responsibility of Mitsubishi. (2) Loss in opportunity, lost profits incurred to the user by Failures of Mitsubishi products. (3) Special damages and secondary damages whether foreseeable or not, compensation for accidents, and

compensation for damages to products other than Mitsubishi products. (4) 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.

712

TRADEMARKS Microsoft, Microsoft Access, Excel, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, Windows NT, Windows Server, Windows Vista, and Windows XP are trademarks of the Microsoft group of companies. The company names, system names and product names mentioned in this manual are either registered trademarks or trademarks of their respective companies. In some cases, trademark symbols such as '' or '' are not specified in this manual.

COPYRIGHTS The screens (screenshots) are used in accordance with the Microsoft Corporation guideline.

SH(NA)-082488ENG-B

SH(NA)-082488ENG-B(2210)MEE MODEL: RCPU-U-E MODEL CODE: 13JX6D

Specifications subject to change without notice.

When exported from Japan, this manual does not require application to the Ministry of Economy, Trade and Industry for service transaction permission.

HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN NAGOY

Manualsnet FAQs

If you want to find out how the R02CPU Mitsubishi works, you can view and download the Mitsubishi R02CPU Controller CPU User's Manual on the Manualsnet website.

Yes, we have the User's Manual for Mitsubishi R02CPU as well as other Mitsubishi manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The User's Manual should include all the details that are needed to use a Mitsubishi R02CPU. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Mitsubishi R02CPU Controller CPU User's Manual is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Mitsubishi R02CPU Controller CPU User's Manual consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Mitsubishi R02CPU Controller CPU User's Manual free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Mitsubishi R02CPU Controller CPU User's Manual, simply download the document to your computer. Once downloaded, open the PDF file and print the Mitsubishi R02CPU Controller CPU User's Manual as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.