Contents

SAFETY PRECAUTIONS
CONDITIONS OF USE FOR THE PRODUCT
INTRODUCTION
CONTENTS
MANUALS
MANUAL PAGE ORGANIZATION
TERMS
PROGRAMMING
- CHAPTER 1 BASIC PROCEDURE FOR PROGRAMMING
  - 1.1 System Configuration Example
  - 1.2 Creating a Project
  - 1.3 Creating a Program
    - 1.3.1 Prior knowledge for creating a program
    - 1.3.2 How to create a program
  - 1.4 Converting a Program
  - 1.5 Writing a Project to the CPU Module
    - 1.5.1 Formatting a memory
    - 1.5.2 Writing to the CPU module
  - 1.6 Checking an Operation of the CPU Module
  - 1.7 Saving a Project
- CHAPTER 2 APPLICATION OF PROGRAMMING
  - 2.1 Memory and Files
    - 2.1.1 Memory configuration and storable data
    - 2.1.2 Parameter-valid drive
    - 2.1.3 Files
  - 2.2 Base Unit Assignment
    - 2.2.1 Base mode
    - 2.2.2 Base unit assignment setting
  - 2.3 I/O Number Assignment
    - 2.3.1 Concept of I/O number assignment
    - 2.3.2 Setting I/O numbers
    - 2.3.3 I/O number setting example
    - 2.3.4 Checking I/O numbers
  - 2.4 Scan Time Structure
    - 2.4.1 Initial Processing
    - 2.4.2 I/O Refresh (Refresh Processing with Input/Output Modules)
    - 2.4.3 Program Operation
    - 2.4.4 END Processing
  - 2.5 Operation Processing in the RUN, STOP, or PAUSE Status
  - 2.6 Operation Processing during Momentary Power Failure
  - 2.7 Data Clear Processing
  - 2.8 I/O Processing and Response Delay
    - 2.8.1 Refresh mode
    - 2.8.2 Direct mode
  - 2.9 Interrupt Program
  - 2.10 Settings When Program is Divided
    - 2.10.1 Initial execution type program
    - 2.10.2 Scan execution type program
    - 2.10.3 Stand-by type program
    - 2.10.4 Fixed scan execution type program
    - 2.10.5 Changing the program execution type
  - 2.11 Boot Operation
  - 2.12 Programming Language
  - 2.13 Communications with Intelligent Function Modules
  - 2.14 Access to the AnS/A Series Special Function Modules
FUNCTIONS
- CHAPTER 3 FUNCTIONS
  - 3.1 Function List
  - 3.2 Constant Scan
  - 3.3 Latch Function
  - 3.4 Output Mode at Operating Status Change (STOP to RUN)
  - 3.5 Clock Function
  - 3.6 Remote Operation
    - 3.6.1 Remote RUN/STOP
    - 3.6.2 Remote PAUSE
    - 3.6.3 Remote RESET
    - 3.6.4 Remote latch clear
    - 3.6.5 Relationship between remote operation and RUN/STOP status of the CPU module
  - 3.7 Q Series-compatible Module Input Response Time Selection (I/O Response Time)
  - 3.8 Error Time Output Mode Setting
  - 3.9 H/W Error Time PLC Operation Mode Setting
  - 3.10 Intelligent Function Module Switch Setting
  - 3.11 Monitor Function
    - 3.11.1 Monitor condition setting
    - 3.11.2 Local device monitor/test
    - 3.11.3 External input/output forced on/off
    - 3.11.4 Executional conditioned device test
  - 3.12 Writing Programs While CPU Module is in RUN Status
    - 3.12.1 Online change (ladder mode)
    - 3.12.2 Online change (files)
    - 3.12.3 Precautions for online change
  - 3.13 Execution Time Measurement
    - 3.13.1 Program monitor list
    - 3.13.2 Interrupt program monitor list
    - 3.13.3 Scan time measurement
  - 3.14 Sampling Trace Function
  - 3.15 Debug from Multiple Programming Tools
    - 3.15.1 Simultaneous monitoring from multiple programming tools
    - 3.15.2 Online change from multiple programming tools
  - 3.16 Watchdog Timer (WDT)
  - 3.17 Self-diagnostic Function
    - 3.17.1 LEDs indicating errors
    - 3.17.2 Clearing errors
  - 3.18 Error History
  - 3.19 Security Function
    - 3.19.1 Password registration
    - 3.19.2 File password 32
    - 3.19.3 File access control by security key
    - 3.19.4 Remote password
  - 3.20 LED Indication
    - 3.20.1 Methods for turning off the LEDs
    - 3.20.2 LED indication priority
  - 3.21 High-Speed Interrupt Function
    - 3.21.1 High-speed interrupt program execution function
    - 3.21.2 High-speed I/O refresh function and high-speed buffer transfer function
    - 3.21.3 Precautions
  - 3.22 Interrupt from Intelligent Function Module
  - 3.23 Serial Communication Function
  - 3.24 Service Processing
    - 3.24.1 Service processing setting
  - 3.25 Initial Device Value
  - 3.26 Battery Life-prolonging Function
  - 3.27 Memory Check Function
  - 3.28 Program Cache Memory Auto Recovery Function
  - 3.29 Latch Data Backup to Standard ROM
  - 3.30 Writing/Reading Device Data to/from Standard ROM
  - 3.31 CPU Module Change Function with Memory Card
    - 3.31.1 Data backup for the CPU module change function
    - 3.31.2 Restoration for the CPU module change function
  - 3.32 CPU Module Data Backup/restoration Function
    - 3.32.1 Backup function
    - 3.32.2 Restoration function
  - 3.33 Module Model Name Read
  - 3.34 Module Error Collection
  - 3.35 Local Device Batch Read Function
  - 3.36 Send Points Extension Function (CC-Link IE Controller Network Module)
  - 3.37 Write-Protect Function for Device Data (from Outside the CPU Module)
    - 3.37.1 Setting method
    - 3.37.2 Target devices
    - 3.37.3 Operations and functions that cannot be executed for devices in write-protected range
    - 3.37.4 Precautions
  - 3.38 Operation History Function
    - 3.38.1 Operation history save function
    - 3.38.2 Operation history display
    - 3.38.3 Operation history clear function
    - 3.38.4 Precautions
    - 3.38.5 List of operation codes
  - 3.39 iQ Sensor Solution Function
DEVICES, CONSTANTS
- CHAPTER 4 DEVICES
  - 4.1 Device List
  - 4.2 Internal User Devices
    - 4.2.1 Input (X)
    - 4.2.2 Output (Y)
    - 4.2.3 Internal relay (M)
    - 4.2.4 Latch relay (L)
    - 4.2.5 Annunciator (F)
    - 4.2.6 Edge relay (V)
    - 4.2.7 Link relay (B)
    - 4.2.8 Link special relay (SB)
    - 4.2.9 Step relay (S)
    - 4.2.10 Timer (T)
    - 4.2.11 Counter (C)
    - 4.2.12 Data register (D)
    - 4.2.13 Link register (W)
    - 4.2.14 Link special register (SW)
  - 4.3 Internal System Devices
    - 4.3.1 Function devices (FX, FY, FD)
    - 4.3.2 Special relay (SM)
    - 4.3.3 Special register (SD)
  - 4.4 Link Direct Device
  - 4.5 Module Access Devices
    - 4.5.1 Intelligent function module device
    - 4.5.2 Cyclic transmission area device
  - 4.6 Index Register (Z)/Standard Device Resister (Z)
    - 4.6.1 Index register (Z)
    - 4.6.2 Standard device register (Z)
    - 4.6.3 Switching from the scan execution type to the interrupt/fixed scan execution type program
  - 4.7 File Register (R)
    - 4.7.1 Storage location
    - 4.7.2 File register size
    - 4.7.3 Differences in available accesses by storage memory
    - 4.7.4 Registration procedure for the file register
    - 4.7.5 Specification methods of the file register
    - 4.7.6 Precautions for using the file register
  - 4.8 Extended Data Register (D) and Extended Link Register (W)
  - 4.9 Nesting (N)
  - 4.10 Pointer (P)
    - 4.10.1 Local pointer
    - 4.10.2 Common pointer
  - 4.11 Interrupt Pointer(I)
    - 4.11.1 List of interrupt pointer numbers and interrupt factors
  - 4.12 Other Devices
    - 4.12.1 SFC block device (BL)
    - 4.12.2 Network No. specification device (J)
    - 4.12.3 I/O No. specification device (U)
    - 4.12.4 Macro instruction argument device (VD)
- CHAPTER 5 CONSTANTS
  - 5.1 Decimal Constant (K)
  - 5.2 Hexadecimal Constant (H)
  - 5.3 Real Number (E)
  - 5.4 Character String (" ")
- CHAPTER 6 CONVENIENT USAGE OF DEVICES
  - 6.1 Global Device
  - 6.2 Local Device
APPENDICES
- Appendix 1 Parameters
  - Appendix 1.1 List of parameter numbers
  - Appendix 1.2 PLC parameters
    - Appendix 1.2.1 PLC name
    - Appendix 1.2.2 PLC system
    - Appendix 1.2.3 PLC file
    - Appendix 1.2.4 PLC RAS
    - Appendix 1.2.5 Boot file
    - Appendix 1.2.6 Program
    - Appendix 1.2.7 SFC
    - Appendix 1.2.8 Device
    - Appendix 1.2.9 I/O assignment
    - Appendix 1.2.10 Multiple CPU setting
    - Appendix 1.2.11 Built-in Ethernet port setting
    - Appendix 1.2.12 Serial communication
    - Appendix 1.2.13 Acknowledge XY assignment
  - Appendix 1.3 Network Parameters
    - Appendix 1.3.1 CC-Link IE Controller Network setting
    - Appendix 1.3.2 CC-Link IE Field Network setting
    - Appendix 1.3.3 MELSECNET/H setting
    - Appendix 1.3.4 Ethernet setting
    - Appendix 1.3.5 CC-Link setting
  - Appendix 1.4 Remote Password
- Appendix 2 Functions Added or Changed by Version Upgrade
- Appendix 3 CPU Module Processing Time
  - Appendix 3.1 Scan time structure
  - Appendix 3.2 Time required for each processing included in scan time
  - Appendix 3.3 Factors that increase the scan time
- Appendix 4 Data Used in Sequence Programs
  - Appendix 4.1 BIN (Binary Code)
  - Appendix 4.2 HEX (Hexadecimal)
  - Appendix 4.3 BCD (Binary-coded Decimal)
  - Appendix 4.4 Real number (Floating-point data)
  - Appendix 4.5 Character string data
- Appendix 5 Replacing Basic Model QCPU or Qn(H)CPU with QnUCPU
  - Appendix 5.1 Replacement precautions
    - Appendix 5.1.1 Replacing Basic model QCPU with Universal model QCPU
    - Appendix 5.1.2 Replacing High Performance model QCPU with Universal model QCPU
  - Appendix 5.2 Applicable devices and software
  - Appendix 5.3 Instructions
    - Appendix 5.3.1 Instructions not supported in the Universal model QCPU and replacing methods
    - Appendix 5.3.2 Replacing programs using multiple CPU transmission dedicated instructions
    - Appendix 5.3.3 Program replacement examples
  - Appendix 5.4 Functions
    - Appendix 5.4.1 Floating-point operation instructions
    - Appendix 5.4.2 Error check processing for floating-point data comparison instructions (excluding High-speed Universal model QCPU)
    - Appendix 5.4.3 Range check processing for index-modified devices
    - Appendix 5.4.4 Device latch function
    - Appendix 5.4.5 File usability setting
    - Appendix 5.4.6 Parameter-valid drive and boot file setting
    - Appendix 5.4.7 External input/output forced on/off function
  - Appendix 5.5 Special Relay and Special Register
    - Appendix 5.5.1 Special relay list
    - Appendix 5.5.2 Special register list
- Appendix 6 Precautions for Replacing QnUD(E)(H)CPU with QnUDVCPU/QnUDPVCPU
  - Appendix 6.1 Precautions
- Appendix 7 Precautions for Replacing QnPHCPU with QnUDPVCPU
- Appendix 8 Precautions for Using GX Works2 and Differences with GX Developer
- Appendix 9 Ways to Use Different Types of the Backup/restoration Function
- Appendix 10 Device Point Assignment Sheet
INDEX
REVISIONS
WARRANTY

Mitsubishi Electric MELSEC Q QnUCPU User's Manual

Mitsubishi Electric MELSEC Q QnUCPU manual cover

Pages 588

Year 0

Language(s)

of 588

Mitsubishi Electric MELSEC Q QnUCPU Specification

The Mitsubishi Electric MELSEC Q series QnUCPU is a high-performance programmable logic controller (PLC) designed to provide enhanced processing power and connectivity for industrial automation applications. This series offers advanced CPU modules that deliver superior speed and precision, making it ideal for complex control tasks and large-scale system integration. The QnUCPU features a scalable architecture, allowing users to configure the system to meet specific requirements, from simple to highly sophisticated control tasks. It supports a wide range of I/O modules, network communication options, and intelligent function modules, ensuring flexibility and adaptability in diverse industrial environments.

The QnUCPU series incorporates a high-speed processor, capable of executing instructions at remarkable speeds, significantly reducing cycle times and increasing throughput. With its robust memory capacity, it supports extensive program and data storage, enabling complex and large-scale process automation. The series also includes built-in Ethernet ports, enhancing connectivity options for seamless communication within industrial networks and with higher-level enterprise systems.

Furthermore, the QnUCPU provides comprehensive diagnostic and maintenance features, including error detection, logging, and system monitoring, which enhance reliability and ease of maintenance. The programming environment for the QnUCPU is user-friendly, supporting various programming languages such as ladder logic, structured text, and function block diagram, facilitating integration with existing systems and legacy equipment. Overall, the Mitsubishi Electric MELSEC Q QnUCPU series represents a versatile and powerful solution for achieving high efficiency, precision, and reliability in industrial automation applications.

Mitsubishi Electric MELSEC Q QnUCPU F.A.Q.

How do I connect the MELSEC Q QnUCPU to a PC for programming?

To connect the MELSEC Q QnUCPU to a PC, use a USB or Ethernet cable depending on the model. Install the necessary drivers and use the GX Developer or GX Works2 software for programming.

What should I do if the QnUCPU does not start up correctly?

Check the power supply and ensure all modules are securely connected. Verify that there are no error codes displayed on the CPU module and consult the manual for troubleshooting specific error codes.

How can I update the firmware of my MELSEC QnUCPU?

First, download the latest firmware from Mitsubishi Electric's official website. Connect to the QnUCPU via USB or Ethernet and use the firmware update tool provided by Mitsubishi to upload the new firmware.

What is the procedure for backing up the program on a MELSEC QnUCPU?

Use GX Developer or GX Works2 software to connect to the CPU, then navigate to the 'Project' menu and select 'Save As' to create a backup of the current program on your PC.

Can I use third-party modules with MELSEC Q series PLCs?

While Mitsubishi recommends using official modules for compatibility and support, some third-party modules may be compatible. Always check the specifications and test the setup in a controlled environment before deployment.

How do I perform a factory reset on the MELSEC QnUCPU?

To perform a factory reset, power off the PLC, set the initial setting switch to "ON", then power it back on. After a reset, remember to reconfigure the necessary settings and restore any backups.

What are the common causes of communication failure between the QnUCPU and a network device?

Common causes include incorrect IP settings, faulty cables, network congestion, and incompatible network configurations. Verify all settings and connections, and consult the network administrator if needed.

How can I monitor the status of the MELSEC QnUCPU remotely?

Use the MX Component or MC Works64 software to set up remote monitoring. Ensure that the QnUCPU is connected to a network and that remote access settings are configured correctly.

What maintenance practices should be followed for MELSEC QnUCPU?

Regularly check for firmware updates, ensure proper ventilation to prevent overheating, inspect connections for wear or damage, and perform routine backups of the program data.

How do I troubleshoot a program error on the MELSEC QnUCPU?

Check the error code displayed on the CPU and refer to the manual for specific troubleshooting steps. Use the GX Developer or GX Works2 software to debug the program and identify the source of the error.