Page 3: Safety Precautions
SAFETY PRECAUTIONS (Always read these instructions before using this product.) Before using this product, please read this manual and the relevant manuals introduced in this manual carefully and pay full attention to safety to handle the product correctly. The instructions given in this manual are concerned with this product. For the safety instructions of the programmable controller system, please read the CPU module user's manual.
Page 4 [Design Precautions] DANGER If load current more than the rating or overcurrent due to a short circuit in the load has flowed in the output module for a long time, it may cause a fire and smoke. Provide an external safety device such as a fuse.
Page 5 [Installation Precautions] CAUTION Use the C Controller module in an environment that meets the general specifications shown in this manual. Using this C Controller module in an environment outside the range of the general specifications could result in an electric shock, fire, erroneous operation, and damage to or deterioration of the product.
Page 6 [Wiring Precautions] DANGER Completely turn off the externally supplied power used in the system when wiring. Failure to do so could result in an electric shock or damage to the product. Before energizing or operating the system after wiring, be sure attach the terminal cover supplied with the product.
Page 7 [Wiring Precautions] CAUTION Be sure to ground the FG and LG terminals to the protective ground conductor. Not doing so could result in an electric shock or erroneous operation. Prevent foreign matter such as dust or wiring debris from entering the module. Failure to do so could cause fires, damage, or erroneous operation.
Page 8 [Startup and Maintenance Precautions] DANGER Do not touch the terminals while power is on. Doing so may cause an electric shock. Correctly connect the battery. Also, do not charge, disassemble, heat, place in fire, short circuit, or solder the battery. Mishandling of the battery can cause overheating or cracks which could result in injury and/or fires.
Page 9 [Startup and Maintenance Precautions] CAUTION Do not disassemble or modify the modules. Doing so could cause malfunction, erroneous operation, injury, or fire. Perform online operations connecting peripheral devices to the running C Controller module (especially program modification, forced output, and operation status change) after reading the manual carefully and fully ensuring the safety.
Page 10 [Disposal Precautions] CAUTION When disposing of this product, treat it as industrial waste. When disposing of batteries, separate them from other wastes according to the local regulations. (For details of the battery directive in EU member states, refer to Appendix 4.) [Transportation Precautions] CAUTION When transporting lithium batteries, make sure to treat them based on the transport regulations.
Page 11: Revisions
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.
Page 12: Operating Precautions
OPERATING PRECAUTIONS This section explains precautions in the following order. 1) Precautions for system configuration 2) Precautions for standard ROM and CompactFlash card 3) Precautions for battery 4) Precautions for clock setting 5) Precautions for installation and uninstallation 6) Precautions for each utility 7) Precautions for programming 8) Precautions for program debugging 9) Precautions for use of FTP...
Page 13 Precautions for standard ROM and CompactFlash card (1) Formatting of standard ROM (a) When formatting the standard ROM Be sure to use the method described in Section 5.10 (4)(a). Do not format it using a command from Shell of Tornado. (b) While standard ROM is being formatted Do not power off or reset the C Controller module.
Page 14 Precautions for battery (1) File corruption (a) When battery is not replaced after battery error occurrence The standard ROM/battery-backed-up RAM data during access or the clock data may be corrupted, or a file system error may occur. (b) When shutdown operation is not performed after running without battery The standard ROM/battery-backed-up RAM data during access or the clock data may be corrupted, or a file system error may occur.
Page 15 Precautions for installation and uninstallation (1) Installation When overwriting the SW PVC-CCPU, install the new one into the folder where the old one has already been stored. Installing into any other folder is not allowed. PVC-CCPU of another version cannot be overwritten. In this case, perform installation after uninstalling already installed SW PVC-CCPU.
Page 16 Precautions for programming (1) Restrictions on bus interface functions and MELSEC data link functions (a) Endian format (Memory layout) C Controller module is divided into two types: One using the memory layout of little endian and the other using the memory layout of big endian. Create a user program in little endian or big endian according to the type used.
Page 17 (g) Relations between Tornado, system watchdog timer and user watchdog timer When using Browser's Spy Chart function or Wind Power tool (e.g. WindView) in Tornado environment, set a sufficiently long time to the system watchdog timer and user watchdog timer. Since using Browser's Spy Chart function or Wind Power tool (e.g.
Page 18 (5) Power off (including reset) during file operation If the C Controller system is powered off or reset (remote RESET included) while a user file within the standard ROM or CompactFlash card is being written, data corruption or a file system error may occur. (CompactFlash card is available for the Q06CCPU-V only.) In this case, execute the following before powering off or resetting the system.
Page 19 Precautions for program debugging (1) VxWorks image file When debugging the user program with connecting Tornado of the development environment (personal computer) to the C Controller module, be sure to specify the Vxworks image file whose function version matches the first 5 digits of serial No. of the C Controller module to be connected.
Page 20 (c) Execution of VxWorks reboot command Do not reboot VxWorks by executing the reboot function or pressing the CTRL + X keys. If VxWorks is rebooted, the C Controller module does not start up properly. Reset it on the C Controller module. ( Section 4.5.3, 13.6) (d) Command execution without argument specified If a command having an argument was executed with no argument specified, it...
Page 21: Table Of Contents
INTRODUCTION Thank you for choosing the Mitsubishi MELSEC-Q Series of General Purpose Programmable Controllers. Before using the equipment, please read this manual carefully to develop full familiarity with the functions and performance of the Q series programmable controller you have purchased, so as to ensure correct use.
Page 22 3.4.2 I/O access timing ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••3 - 6 3.4.3 RUN,STOP and PAUSE status operation processing •••••••••••••••••••••••••••••••••••••••••••••••••3 - 7 3.4.4 Operation processing during momentary power failure ••••••••••••••••••••••••••••••••••••••••••••••••3 - 8 CHAPTER4 FUNCTIONS 4 - 1 to 4 - 106 Function List •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••4 - 1 I/O Module and Intelligent Function Module Access Function •••••••••••••••••••••••••••••••••••••••••••••4 - 4 CC-Link Module Access Function •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••4 - 6 4.3.1...
Page 23 Cable Connection ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 25 Network Settings for 1:1 Connection •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 26 Battery Specifications, Installation and Replacement•••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 32 5.7.1 Battery specifications ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 32 5.7.2 Installing battery ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 33 5.7.3 Replacing battery•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 5 - 34 5.7.4 When module has been operated without battery ••••••••••••••••••••••••••••••••••••••••••••••••••••...
Page 24 CHAPTER8 INSTALLING AND UNINSTALLING SW[]PVC-CCPU 8 - 1 to 8 - 8 Development Environment ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 1 Installation ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 2 Icons to be Registered •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 6 Uninstallation ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••8 - 7 CHAPTER9 UTILITY OPERATION 9 - 1 to 9 - 196 Common Utility Operations •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••9 - 2 9.1.1 Starting utility•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••9 - 2...
Page 25 9.5.1 CC IE Control utility function list •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••9 - 137 9.5.2 Operating Module information screen ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••9 - 138 9.5.3 Operating Diagnostics result screen••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••9 - 141 9.5.4 Operating Online operation screen •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••9 - 158 9.5.5 Operating Parameter settings screen ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••9 - 161 9.5.6 Operating Target settings screen •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••9 - 174 9.5.7...
Page 26 CHAPTER11 OVERVIEW OF MULTIPLE CPU SYSTEM 11 - 1 to 11 - 4 11.1 What is Multiple CPU System ? •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 11 - 1 CHAPTER12 MULTIPLE CPU SYSTEM CONFIGURATION 12 - 1 to 12 - 38 12.1 System Configuration •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 12 - 1 12.1.1 Devices to be used •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••...
Page 27 14.8 Motion CPU Device Access••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••14 - 25 CHAPTER15 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEM 15 - 1 to 15 - 6 15.1 Parameter List ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 15 - 1 15.1.1 Setting Number of CPUs (Setup required) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 15 - 4 15.1.2 Operation mode setting (optional) •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••...
Page 28 18.5 Hardware Self-diagnostic Function •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••18 - 88 18.6 Diagnostics and Restoration of Standard ROM and CompactFlash Card Drives •••••••••••••••••••18 - 95 APPENDICES App- 1 to App - 29 Appendix 1 Function Processing Time••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• App- 1 Appendix 2 External Dimensions ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• App- 6 Appendix 2.1 Q06CCPU-V •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••...
Page 29: About Manuals
ABOUT MANUALS The following manuals are also related to this product. If necessary, please place an order referring to the table below. Related Manuals Manual Number Manual Name (Model Code) QCPU User's Manual (Hardware Design, Maintenance and Inspection) SH-080483ENG This manual provides the specifications of the CPU modules, power supply modules, base units, (13JR73) extension cables, memory cards and others.
Page 30: How This Manual Is Organized
HOW THIS MANUAL IS ORGANIZED CPU modules having precautions Reference Chapter heading The CPU modules having precautions are A reference section or The index on the right side of the page shown as icons. reference manual is marked shows the chapter of the open page at a "Note "...
Page 31: How To Use This Manual
HOW TO USE THIS MANUAL This manual describes the procedures and operations for using the C Controller module in a system and provides the information that may be needed in various stages. Use this manual, referring to the following description. (1) Features ( Chapter 1) Chapter 1 describes the features of the C Controller module.
Page 32: Generic Terms And Abbreviations Used In This Manual
Generic term for the 100BASE-TX and 10BASE-T network systems Abbreviation for the Mitsubishi graphic operation terminal Q series Abbreviation for the Mitsubishi programmable controllers, MELSEC-Q series AnS series Abbreviation for the Mitsubishi programmable controllers, compact MELSEC-A series Product name of the SW D5C-GPPW-E GPP function software package for Q series...
Page 33 Generic term/abbreviation Description Generic term for the Q33B, Q35B, Q38B, and Q312B main base units to which the CPU modules, Q series power supply modules, Q series I/O modules, and intelligent function Q3 B modules can be mounted Generic term for the Q32SB, Q33SB, and Q35SB slim type main base units to which the C Controller module, Basic model QCPU, High Performance model QCPU, Universal Q3 SB model QCPU, slim type power supply modules, Q series I/O modules, and intelligent...
Page 34 Abbreviation for Tornado 2.1.0 for Hitachi Super H Cumulative patch 1 manufactured by Wind River Systems, Inc. Tornado For the specifications and inquiries of Tornado, visit the Wind River Systems, Inc. website: http://www.windriver.com/ Abbreviation for the MELSEC-Q series PC CPU module manufactured by CONTEC CO. PC CPU module LTD. - 32...
Page 35: Glossary
GLOSSARY The following indicates the meanings of the terms used in the C Controller module manual. Term Description FTP stands for File Transfer Protocol. This protocol is used to transfer files. Protocol or virtual terminal software designed to perform operations by logging in to a computer Telnet from a remote location in a TCP/IP network.
Page 36: Chapter1 Overview
OVERVIEW CHAPTER1 OVERVIEW This manual explains the specifications, functions, and operating procedures of the MELSEC-Q series C Controller module, the utilities offered by the setting/monitoring tool for C Controller module (SW PVC-CCPU), the specifications of functions, and troubleshooting. C Controller module...
Page 37 Shield section Clamp fitting Masked Shield cable Recommended clamp fitting: Mitsubishi AD75CK Figure 1.3 Part to be exposed Figure 1.4 Shield grounding (Correct example) Note) The method of earthing by soldering a wire onto the shield section of the shielded cable as shown below is not recommended. The high frequency impedance will increase and the shield will be ineffective.
Page 38: Features
OVERVIEW 1.1 Features The following are the features of the C Controller module. (1) VxWorks enables system configuration of high real-time performance. The VxWorks, a real-time OS is built in the C Controller module. Creating a user program with the C language and executing the program on VxWorks enables system configuration of high real-time performance.
Page 39 OVERVIEW (5) Optimum multiple CPU system is configurable. The C Controller module can be used with programmable controller CPU module(s) and Motion CPU(s) to configure a multiple CPU system. In the multiple CPU system, individual CPU utilizes its own advantage and shares the processing task so that the optimum system can be configured.
Page 40 OVERVIEW (7) Accessible from C Controller module to other station via CC-Link Access can be made to the other station programmable controller CPU via CC-Link from the user program created using the MELSEC data link functions. (MELSEC data link functions are available for the Q06CCPU-V only) Access via CC-Link C Controller module...
Page 41 OVERVIEW (b) Accessible to other station programmable controller via MELSECNET/H module (Q06CCPU-V only) From the user program created using the MELSEC data link functions, access to the other station programmable controller CPU can be made via the MELSECNET/H network. Access via MELSECNET/H Q06CCPU-V MELSECNET/H Figure 1.11 Access to other station programmable controller via MELSECNET/H module...
Page 42 OVERVIEW (b) Access to programmable controller CPUs on other stations via CC-Link IE controller network module From the user program created with MELSEC data link functions, access to another station's programmable controller CPU is available via a CC-Link IE controller network. Access via CC-Link IE controller network Q06CCPU-V CC-Link IE controller network...
Page 43 OVERVIEW (11)A variety of CC-Link products can be controlled The C Controller module can control a variety of CC-Link products by user programs. Up to eight CC-Link modules can be installed. C Controller module CC-Link module Remote I/O station Remote device station Local station Intelligent device station Partner manufacturer's...
Page 44 OVERVIEW (13)Easy creation of serial communication program The C Controller module has the RS-232 port. Using the VxWorks communication library, serial communication programs can be created. Microcomputer connection to a GOT is also available. ( Section 4.16) C Controller module Serial communications Figure 1.17 Serial communications using RS-232 port (14)Efficient development of user programs by integrated development...
Page 45 OVERVIEW (15)Supporting Telnet function The C Controller module has Telnet program preinstalled. Instead of using Tornado, the Telnet function allows simple remote debugging (task information display, memory dump, etc.) of the C Controller module to be done by executing the Shell command from the Telnet tool of the development environment (personal computer).
Page 46 OVERVIEW (18)Login user access restrictions The C Controller module allows the login user to be set (added/deleted). This enables restrictions on the Telnet function and the operation for writing parameters from FTP or each utility. Figure 1.20 Login user access restrictions (19)RAM disk function The C Controller module can create a RAM disk on the work RAM by the user program.
Page 47: Chapter2 System Configuration
SYSTEM CONFIGURATION CHAPTER2 SYSTEM CONFIGURATION This chapter explains the system configuration, compatible modules, and connectable devices of the C Controller module. 2.1 System Configuration This section explains the device configuration, connection with an environment development, and system configuration overview of a C Controller system. For the multiple CPU system configuration, refer to Chapter 11 and 12.
Page 48: Devices To Be Used
SYSTEM CONFIGURATION 2.1.1 Devices to be used (1) When the main base unit (Q3 B) is used Commercially available CompactFlash card (to be purchased separately) C Controller module Battery Main base unit Extension cable Q series power supply, I/O, Intelligent function modules Extension base unit Figure 2.1 System configurations when main base unit is used * 1 The CompactFlash card cannot be installed to the Q06CCPU-V-B.
Page 49 SYSTEM CONFIGURATION (2) When the slim type main base unit (Q3 SB) is used Commercially available CompactFlash card (to be purchased separately) C Controller module Battery Slim type main base unit Q series power supply, I/O, Intelligent function modules Figure 2.2 System configuration when slim type main base unit is used * 1 The CompactFlash card cannot be installed to the Q06CCPU-V-B.
Page 50 SYSTEM CONFIGURATION (3) When the multiple CPU high speed main base unit (Q3 DB) is used Commercially available CompactFlash card (to be purchased separately) C Controller module Battery DB multiple CPU high speed main base unit Extension cable Q series power supply, I/O, Intelligent function modules Extension base unit Figure 2.3 System configuration when Q3 DB is used * 1 The CompactFlash card cannot be installed to the Q06CCPU-V-B.
Page 51: Connection With Development Environment
SYSTEM CONFIGURATION 2.1.2 Connection with development environment C Controller module Commercially available CompactFlash card (to be purchased separately)* Development environment* (personal computer) Twisted pair cable (Crossing cable) (to be purchased separately) Adaptor* Commercially available (to be purchased CompactFlash card (to be separately) purchased separately)* Tornado*...
Page 52: Connection With Peripheral Devices
SYSTEM CONFIGURATION 2.1.3 Connection with peripheral devices C Controller module Hub (to be purchased separately) Twisted pair cable (Straight cable) Personal computer (target device) (to be purchased separately) GOT, RS-232 cable (to be purchased separately) Figure 2.5 Connection with peripheral devices 2.1 System Configuration 2.1.3 Connection with peripheral devices...
Page 53: Overview Of System Configuration
SYSTEM CONFIGURATION 2.1.4 Overview of system configuration (1) When the main base unit (Q3 B) is used Main base unit When 32-point modules are loaded to slots. Q312B (12 slots occupied) ..Slot number ..I/O number Q series C Controller module power supply module Extension base unit...
Page 54 SYSTEM CONFIGURATION Table2.1 Restrictions on the system configuration, and available base units, extension cables and power supply modules Maximum number of extension stages of 7 extension stages extension base units Maximum number of 64 modules mounted I/O modules Available main base unit Q33B, Q35B, Q38B, Q312B model Module types requiring no power supply module...
Page 55 SYSTEM CONFIGURATION (2) When the slim type main base unit (Q3 SB) is used Slim type main base unit When 32-point modules are loaded to slots. Q35SB (5 slots occupied) ..Slot number ..I/O number Slim type power supply C Controller module module Figure 2.7 System configuration example when slim type main base unit is used...
Page 56 SYSTEM CONFIGURATION (3) When the multiple CPU high speed main base unit (Q3 DB) is used Multiple CPU high speed main base unit ... When 32-point modules are load to slots. Q312DB (12 slots occupied) ..Slot number ..I/O number Q series power C Controller module supply module...
Page 57 SYSTEM CONFIGURATION Table2.3 Restrictions on the system configuration, and available base units, extension cables and power supply modules Maximum number of extension stages of 7 extension stages extension base units Maximum number of 64 modules mounted I/O modules Available main base unit Q38DB, Q312DB model Module types requiring no power supply module...
Page 58: Precautions For System Configuration
SYSTEM CONFIGURATION 2.1.5 Precautions for system configuration This section explains the precautions for system configuration. (1) Main base unit not applicable to the C Controller module The following main base unit is not applicable. • Redundant power main base unit (Q3 RB) (2) Extension base units not applicable to the C Controller module The following extension base units are not applicable.
Page 59: Applicable Modules
2.2.1 Applicable I/O modules and intelligent function modules The following indicates the MELSEC-Q series I/O modules and intelligent function modules applicable to the C Controller module. The MELSEC-AnS/Q2AS series I/O modules and special function modules are not applicable.
Page 60 SYSTEM CONFIGURATION Table2.4 Applicable modules (Continued) Classification Model name *2*3 QJ71GP21-SX, QJ71GP21S-SX CC-Link IE controller network module QJ71LP21-25 QJ71LP21S-25 QJ71LP21G QJ71LP21GE *1*2 MELSECNET/H module QJ71BR11 ID interface module QD35ID1 QD35ID2 QJ71DN91 DeviceNet module * 1 Use the product of function version B or later. * 2 There are restrictions on some functions.
Page 61: Precautions When Using I/O Modules Or Intelligent Function Modules
SYSTEM CONFIGURATION 2.2.2 Precautions when using I/O modules or intelligent function modules This section explains the precautions when using the I/O modules, intelligent function modules, and GX Configurator. (1) Precautions when using I/O modules or intelligent function modules Pay attention to the following when using the I/O modules or intelligent function modules.
Page 62 SYSTEM CONFIGURATION (c) Precautions for using CC-Link module Note that there are restrictions on the following functions of the CC-Link module controlled by the C Controller module. • The CC-Link dedicated instructions are not executable. • Interrupt sequence program start is not applicable. •...
Page 63 SYSTEM CONFIGURATION (d) Precautions for using MELSECNET/H module Note that there are restrictions on the following functions of the MELSECNET/H module controlled by the C Controller module. • Not applicable to the remote I/O network. Applicable to only the PLC-to-PLC network. •...
Page 64 SYSTEM CONFIGURATION (f) Precautions for using serial communication module The serial communication module controlled by the C Controller module supports only communication based on the nonprocedural protocol. 1) Note that the following functions are not applicable: • The MC protocol and bidirectional protocol. •...
Page 65 SYSTEM CONFIGURATION (2) Precautions for using GX Configurator Take the following precautions when utilizing the intelligent function module parameters set by GX Configurator for the C Controller setting utility. (a) Incompatible GX Configurator The following are GX Configurators whose intelligent function module parameters cannot be utilized for the C Controller setting utility.
Page 66: Applicable Software Package
SYSTEM CONFIGURATION 2.3 Applicable Software Package The following shows the C Controller module and applicable SW PVC-CCPU. Table2.7 Applicable software package C Controller module Software version Q06CCPU-V Version 3.00A or later Q06CCPU-V-B Version 3.01B or later 2.4 Applicable Devices This section provides the devices that can be connected to the C Controller module. (1) CompactFlash card (Q06CCPU-V only) The CompactFlash card applicable to the C Controller module is the TYPE I storage card that complies with the CompactFlash...
Page 67 SYSTEM CONFIGURATION (2) Twisted pair cable Use the twisted pair cable that meets IEEE802.3 10BASE-T/100BASE-TX standards. (a) For 100Mbps Use either of the following cables. • Unshielded twisted pair cable (UTP cable), Category 5 • Shielded twisted pair cable (STP cable), Category 5 (b) For 10Mbps Use either of the following cables.
Page 68 SYSTEM CONFIGURATION (3) Hub The C Controller module discriminates between 10BASE-T and 100BASE-TX and between full-duplex and half-duplex communication modes according to the hub. When connecting to the hub that does not have the auto negotiation function, set the hub to operate in the half-duplex communication mode. (4) RS-232 cable Use the RS-232-compliant cable which length is 15m or less.
Page 69 SYSTEM CONFIGURATION (b) Access to programmable controller CPU via network module controlled by C Controller module GX Developer connected to a programmable controller CPU can access another station’s programmable controller CPU via a network module (CC-Link module, MELSECNET/H module, CC-Link IE controller network module) controlled by the C Controller module.
Page 70 SYSTEM CONFIGURATION 2) Other station access via MELSECNET/H to CC-Link Connection target specification on GX Developer Programmable controller CPU MELSECNET/H GX Developer Accessible via network module controlled by the C Controller module! CC-Link Programmable controller CPU Figure 2.11 Other station access via MELSECNET/H to CC-Link - 24 2.4 Applicable Devices...
Page 71 SYSTEM CONFIGURATION (7) Connection with external devices (a) RS-232 device Take the following precautions when connecting an RS-232 device to the RS-232 interface of the C Controller module. • When the C Controller module or the target device connected to the C Controller module is powered on or off, a receive error may occur on the target device side.
Page 72: Confirming Function Version And Software Version
SYSTEM CONFIGURATION 2.5 Confirming Function Version and Software Version Confirm the function version of the C Controller module and the software version of SW PVC-CCPU by the following method. (1) Confirming the function version of the C Controller module (a) Checking "rating plate" on the module side face The serial No.
Page 73: Chapter3 Specifications
SPECIFICATIONS CHAPTER3 SPECIFICATIONS 3.1 General Specifications The following indicates the general specifications of the C Controller module. Table3.1 General specifications Item Specifications Operating ambient 0 to 55 temperature Storage ambient -25 to 75 temperature Operating ambient 5 to 95%RH , non-condensing humidity Storage ambient 5 to 95%RH...
Page 74: Performance Specifications
SPECIFICATIONS 3.2 Performance Specifications This section explains the performance specifications of the C Controller module. Table3.2 Performance specifications Specifications Item Q06CCPU-V Q06CCPU-V-B Hardware specifications ---- Endian format (Memory layout) Little endian Big endian Standard ROM 6M bytes User file capacity Depends on the CompactFlash (For user file storage) CompactFlash card...
Page 75 SPECIFICATIONS Table3.2 Performance specifications (Continued) Specifications Item Q06CCPU-V Q06CCPU-V-B CompactFlash card ---- ---- Supply power voltage 3.3V 5% ---- Supply power capacity Max. 150mA ---- TYPE I card ---- Card size Number of loadable cards ---- Number of I/O points (number of points accessible to actual I/O 4096 points (X/Y0 to FFF) modules) Year, month, day, hour, minute, second, day of week (automatic leap year...
Page 76: Connector Specifications
SPECIFICATIONS 3.3 RS-232 Connector Specifications The RS-232 connector specifications are shown below. (1) RS-232 connector specifications Table3.3 RS-232 connector specifications Signal direction Signal Pin No. Signal name C Controller abbreviation Modem module CD(DCD) Data Carrier Detect RD(RXD) Received Data SD(TXD) Transmitted Data ER(DTR) Data Terminal Ready...
Page 77: Operation Processing
SPECIFICATIONS 3.4 Operation Processing 3.4.1 Initial processing The initial processing is pre-processing executed at the start of the C Controller module. When the initial processing is completed, the C Controller module is placed in the status preset by the RUN/STOP/MODE switch. The following indicates the initial processing details performed when the power is switched on or when the C Controller module is reset.
Page 78: I/O Access Timing
SPECIFICATIONS 3.4.2 I/O access timing This section explains the input (X) loading and output (Y) writing timings of the C Controller module. (1) Input (X) loading timing The C Controller module executes input (X) loading when the bus interface function (such as the QBF_X_In_BitEx function) is executed in the user program.
Page 79: Run,Stop And Pause Status Operation Processing
SPECIFICATIONS 3.4.3 RUN,STOP and PAUSE status operation processing The C Controller module has three different operation statuses: RUN, STOP and PAUSE. This section explains the operation processing of the C Controller module in each operation status. (1) Operation processing in RUN status In the RUN status, output (Y) to each module and writing to buffer memory are enabled from the user program in the C Controller module.
Page 80: Operation Processing During Momentary Power Failure
SPECIFICATIONS 3.4.4 Operation processing during momentary power failure The C Controller module detects a momentary stop when the input power supply voltage supplied to the power supply module falls below the specified range. On detection of a momentary stop, the C Controller module performs the following operation processing.
Page 81: Chapter4 Functions
FUNCTIONS CHAPTER4 FUNCTIONS This chapter explains the functions of the C Controller module. 4.1 Function List The following lists the C Controller module functions. Table4.1 C Controller module function list Applicability Reference Function Description Q06CCP Q06CCP section U-V-B I/O module access function Controls I/O modules and intelligent function modules from the user program of the C Controller Intelligent function module...
Page 82 FUNCTIONS Table4.1 C Controller module function list (Continued) Applicability Reference Q06CCP Q06CCP Function Description section U-V-B Sets whether to clear or hold the outputs to output modules, I/O composite modules and intelligent Error time output mode setting 4.11 function modules when a stop error occurs in the C Controller module.
Page 83 FUNCTIONS Table4.1 C Controller module function list (Continued) Applicability Reference Function Description Q06CCP Q06CCP section U-V-B Starts the SFC program or servo program of the Motion CPU Motion CPU or changes the set value/present value control 14.7 Multiple CPU of the servo from the user program of the C instruction system Controller module.
Page 84: I/O Module And Intelligent Function Module Access Function
FUNCTIONS 4.2 I/O Module and Intelligent Function Module Access Function (1) I/O module, intelligent function module access function This function controls the I/O modules and intelligent function modules controlled by the C Controller module. Create the user program of the C Controller module using the bus interface functions. <Example>...
Page 85 FUNCTIONS (2) Functions The following functions are used to access the I/O modules and intelligent function modules. Table4.2 Function list Function name Function QBF_Open Opens the bus. QBF_Close Closes the bus. QBF_X_In_BitEx Reads one input signal (X). QBF_X_In_WordEx Reads input signals (X) in word units. QBF_Y_Out_BitEx Outputs one output signal (Y).
Page 86: Cc-Link Module Access Function
PW L RUN L ERR X0 1 2 3 Y8 9 A B STATION NO. B RATE 40 20 10 8 4 2 1 4 2 1 controller CPU to the C Controller module via the CC- MITSUBISHI J65SBTB32-8DT2 +24V DC24V (FG)
Page 87: Data Consistency Verification Per Station Function
FUNCTIONS 4.3.1 Data consistency verification per station function The data consistency verification per station function is a function to assure cyclic data per slave station. Depending on the read/write timing, a block of cyclic data might be split into new and old data in double-word (32-bit) units.
Page 88 FUNCTIONS (3) How to read out cyclic data (buffer memory) Cyclic data can be read out from the buffer memory, using the data consistency verification per station function as described below. If any other method is used, cyclic data per station are not be guaranteed. 1) Set to use the data consistency verification per station function in the CC-Link utility.( Section 9.3.5)
Page 89 FUNCTIONS (b) Manually refreshing cyclic data 1) Issue a refresh request with the QBF_RefreshLinkDevice function. 2) The user program is continued. 3) Data are refreshed by the request of 1). 4) Execute the QBF_FromBuf function with "manual" specified for "The link refreshing method of the CC-Link link"...
Page 90 FUNCTIONS POINT When one of the following operations is performed to the CC-Link module where the data consistency verification per station function is set, the cyclic data are automatically refreshed even if the QBF_RefreshLinkDevice function is not executed. • Monitoring on the Module monitoring screen of the C Controller setting utility •...
Page 91 FUNCTIONS (4) How to write cyclic data (buffer memory) Cyclic data can be written to the buffer memory with the data consistency verification per station function as described below. If any other method is used, cyclic data per station are not be guaranteed. 1) Set to use the data consistency verification per station function in CC- Link utility.
Page 92 FUNCTIONS • If execution of the QBF_ToBuf function is attempted before completion of the previous refresh, data writing will not start until completion of the refresh. C Controller module CC-Link module User program Link scan Buffer memory QBF_ToBuf function Refresh request 1) (Automatic) Writing data 1) Link scan Refresh...
Page 93 FUNCTIONS • If a value is written to the same address area before execution of the QBF_RefreshLinkDevice function, the area is overwritten with the value written later. By writing the value to another address area, both of the data can be written.
Page 94 FUNCTIONS POINT When one of the following operations is performed to the CC-Link module where the data consistency verification per station function is set, the cyclic data are automatically refreshed even if the QBF_RefreshLinkDevice function is not executed. • Forced writing to the buffer memory on the Module monitoring screen of the C Controller setting utility •...
Page 95: Melsecnet/H Module Access Function
FUNCTIONS 4.4 MELSECNET/H Module Access Function The MELSECNET/H module access function allows access to C Controller modules and programmable controller CPUs of other stations connected to the MELSECNET/H via a MELSECNET/H module controlled by the C Controller module. Create the user programs of the C Controller module using the MELSEC data link functions or bus interface functions.
Page 96: Message Communication
FUNCTIONS 4.4.1 Message communication The C Controller module can make message communication (message transmission/ reception) by a user program. Messages can be transferred among the following modules via a MELSECNET/H module controlled by the C Controller module. • C Controller module on other station •...
Page 97 FUNCTIONS (a) Internal buffer for message reception 1) The internal buffer for message reception stores the data received from the MELSECNET/H module controlled by the C Controller module. 2) The internal buffer for message reception has areas for four MELSECNET/H modules, and in each of the areas, up to 128 received data can be stored.
Page 98 FUNCTIONS (3) Message communication functions The following functions are available for message communication. Table4.6 Message communication function list Function Function Description name QBF_SEND Message Sends a message to the other station via a MELSECNET/H transmission module. (Equivalent to the SEND instruction) mdSend QBF_RECV Message...
Page 99 FUNCTIONS POINT The following precaution must be taken when a message is sent to the MELSECNET/H module controlled by the programmable controller CPU. When sending data to the same channel of the receiving station with ACK set, execute the transmission after the receiving station has read out the previously received data with the RECV instruction.
Page 100: Link Device Access
FUNCTIONS 4.4.2 Link device access The link devices of the MELSECNET/H module controlled by the C Controller module can be accessed for data reading/writing from the user program on the C Controller module. To access from the user program to the link devices, two different methods are available: the internal buffer access and the direct access.
Page 101 FUNCTIONS 2) Devices accessible from internal link device buffers The following devices are accessible from internal link device buffers. Table4.7 List of devices accessible from internal link device buffers Accessible device No. of points Address range LX buffer 8192 0000 to 1FFF LY buffer 8192...
Page 102 FUNCTIONS (c) Link device refresh Data are refreshed between the link devices and internal link device buffers are refreshed by the link device refresh cycle and refresh parameters set in the MELSECNET/H utility. Section 4.4.4) The ranges that are set by the refresh parameters from the <<Parameter settings>>...
Page 103 FUNCTIONS (2) Direct access (a) Definition of direct access The direct access is a method for directly accessing the link devices of MELSECNET/H modules by the user program on the C Controller module, independently of the link device refresh. Since the internal link device buffers are not accessed in the case of the direct access method, no link device refresh cycle and refresh parameters need to be set in the MELSECNET/H utility.
Page 104 FUNCTIONS (c) Selection of internal buffer access or direct access Select a suitable access method as follows: 1) Data suitable for internal buffer access Data of the link devices that are used frequently or that must be secured in units of stations are suitable for internal buffer access. For these data, set refresh parameters to utilize them for internal buffer access.
Page 105 FUNCTIONS (3) Link device access functions The following functions are available for link device access. Table4.9 Link device access function list Function Function name Description QBF_WriteLinkDevice mdSend mdRandW mdDevSet Writing data to link Writes data to link devices of the mdDevRst device MELSECNET/H module.
Page 106: Parameter Settings
FUNCTIONS 4.4.3 Parameter settings Set the parameters on the <<Parameter settings>> tab screen of the MELSECNET/H utility. Section 9.4.6) Figure 4.18 Parameter settings screen - 26 4.4 MELSECNET/H Module Access Function 4.4.3 Parameter settings...
Page 107: Link Device Refresh Setting
FUNCTIONS 4.4.4 Link device refresh setting Link device refresh setting is required to use the internal buffer access in the user program. To enable the link device refresh, set the link device refresh cycle and refresh parameters on the MELSECNET/H utility. (1) Link device refresh cycle The link device refresh cycle is an interval of time during which the internal link device buffers of the C Controller module and link devices of the MELSECNET/H modules...
Page 108 FUNCTIONS 4) Confirmation of total link devices refresh time The total link devices refresh time during the C Controller system operation can be confirmed in "Link device refresh time (Max./Min./Current)" on the <<Module information>> tab screen of the MELSECNET/H utility. Section 9.4.2) Total link devices refresh time during the C Controller system operation...
Page 109 FUNCTIONS (b) How to determine link device refresh cycle Determine the link device refresh cycle by the following flowchart. Calculation of total link devices refresh time (This section 1)) (This section (1)) Temporary setting of link device refresh cycle (This section 2)) (This section (2)) (This section 3)) Test run of C Controller system (This section (3))
Page 110 FUNCTIONS 1) Calculation of total link devices refresh time Calculate the total link devices refresh time. Section 4.4.5 (2)) 2) Temporary setting of link device refresh cycle The link device refresh cycle and the total link devices refresh time obtained in 1) must satisfy the following relational expression.
Page 111 FUNCTIONS When the system specifications are not satisfied, take corrective actions according to This section 5). Link device Link device Link device Link device refresh cycle refresh cycle refresh cycle refresh cycle High-priority task High-priority task High-priority task processing processing processing Interrupt processing...
Page 112 FUNCTIONS [Action 2: Decrease the refresh points.] Reexamine the refresh parameters and decrease the number of refresh points to reduce the total link devices refresh time. ( Section 4.4.5 (3)) Link device refresh cycle C Controller module processing <Before taking action>...
Page 113 FUNCTIONS (2) Refresh parameters The refresh parameters are designed to transfer the data of the MELSECNET/H module link devices (LX, LY, LB, LW) to the internal link device buffers (LX buffer, LY buffer, LB buffer, LW buffer) of the C Controller module for use in the user program. (a) Link refreshable devices The C Controller module allows 64 transfer settings (LX, LY, LB, LW) for each MELSECNET/H module.
Page 114 FUNCTIONS (3) Refresh parameter setting example The following provides a refresh parameter setting example. (a) System configuration Control station Normal station C Controller MELSECNET MELSECNET Power module /H module /H module supply Station Station No.1 No.2 Network No.1 Network No.2 Station Station Station...
Page 115 FUNCTIONS (c) MELSECNET/H utility: Refresh parameter settings screen Figure 4.30 MELSECNET/H module (1st module) setting Figure 4.31 MELSECNET/H module (2nd module) setting 4.4 MELSECNET/H Module Access Function - 35 4.4.4 Link device refresh setting...
Page 116: Link Data Send/Receive Processing Time Specifications
FUNCTIONS 4.4.5 Link data send/receive processing time specifications This section explains how to calculate the link data send/receive time and transmission delay time in the MELSECNET/H network system. (1) Link data send/receive processing (a) Outline of send/receive processing Cyclic transmission uses LB/LW/LX/LY of the MELSECNET/H module to make communications.
Page 117 FUNCTIONS (b) Link scan and link device refresh Link scan is performed "asynchronously" with the link device refresh of the C Controller module. The link device refresh is executed in the link device refresh cycles set for the C Controller module. Link device refresh cycle Link device...
Page 118 FUNCTIONS * 1 A total time for the number of mounted MELSECNET/H modules and CC-Link IE controller network modules. * 2 For details, refer to the Q Corresponding MELSECNET/H Network System Reference Manual (PLC to PLC network). The mentioned calculation expressions are effective under the following conditions: •...
Page 119 FUNCTIONS (b) Transmission delay time calculation example The transmission delay time is calculated in the following system configuration and conditions. (System configuration, conditions) • Transmission method: Cyclic transmission (transient transmission not used) • Total no. of stations: 2 (1 control station, 1 normal station) •...
Page 120 FUNCTIONS (3) Reduction of link device refresh time The link device refresh time can be shortened by reducing the number of refresh points to the C Controller module, setting proper refresh parameters/network range assignment parameters and making direct access to the link devices. (a) Concept of refresh range (points) Within the range set in the refresh parameters, the range of all stations set in the network range assignment parameters (Stations 1 to 3) covering "first address to...
Page 121 FUNCTIONS (b) How to decrease the refresh points 1) Method using refresh parameters Up to 64 refresh ranges can be set for the C Controller module. For the refresh parameters, set only the ranges that need to be refreshed. C Controller module MELSECNET/H module Internal link device Network range...
Page 122 FUNCTIONS (4) Reduced link scan time The link device refresh data and link scan data (LB/LW) in normal cyclic transmission can be reduced by assigning the data that do not require high speed transmission to the extended area (2000 to 3FFF ) for making low-speed cyclic transmission.
Page 123: Cc-Link Ie Controller Network Module Access Function
FUNCTIONS 4.5 CC-Link IE Controller Network Module Access Function The CC-Link IE controller network module access function is a function that allows access to stations on the CC-Link IE controller network and access to C Controller modules and programmable controller CPUs on other stations, via a CC-Link IE controller network module controlled by a C Controller module.
Page 124: Message Communication
FUNCTIONS 4.5.1 Message communication The C Controller module can send or receive messages using a user program. Messages can be exchanged with the following modules, passing through CC-Link IE controller network module(s) controlled by the C Controller module. • C Controller module on another station •...
Page 125 FUNCTIONS (a) Internal buffer for message reception 1) The internal buffer for message reception stores receive data of the CC-Link IE controller network module that is controlled by the C Controller module. 2) This internal buffer have areas for four CC-Link IE controller network modules, and can store up to 128 receive data blocks for each module area.
Page 126 FUNCTIONS (3) Message communication functions Functions used for message communication are listed below. Table4.12 Message communication function list Function Function Description name Message QBF_SEND Sends messages to another station via CC-Link IE controller transmission mdSend network module. (Equivallent to SEND instruction) Message QBF_RECV Receives messages from another station via CC-Link IE...
Page 127 FUNCTIONS POINT When sending a message to a CC-Link IE controller network module that is controlled by a programmable controller CPU, pay attention to the following: When sequentially sending data with arrival confirmation to the same channel of a station, send the next one after a receiving station retrieved previously received data with the RECV instruction.
Page 128: Link Device Access
FUNCTIONS 4.5.2 Link device access From a user program on a C Controller module, data can be read from or written to the link devices of a CC-Link IE controller network module, which is controlled by the C Controller module. There are two kinds of methods for accessing link devices from a user program: internal buffer access and direct access.
Page 129 FUNCTIONS 2) Devices accessible from internal link device buffers The following devices are accessible from internal link device buffers. Table4.13 List of devices accessible from internal link device buffers Accessible device No. of points Address range LX buffer 8192 0000 to 1FFF LY buffer 8192...
Page 130 FUNCTIONS (c) Link device refresh Data are refreshed between the link devices and internal link device buffers by the link device refresh cycle and refresh parameters set in the CC IE Control utility. Section 4.5.4) The ranges that are set by the refresh parameters from the <<Parameter settings>>...
Page 131 FUNCTIONS (2) Direct access (a) Definition of direct access The direct access is a method for directly accessing the link devices of MELSECNET/H modules by the user program on the C Controller module, independently of the link device refresh. Since the internal link device buffers are not accessed in the case of the direct access method, no refresh parameters need to be set in the CC IE Control utility.
Page 132 FUNCTIONS (c) Selection of internal buffer access or direct access Select a suitable access method as follows: 1) Data suitable for internal buffer access Data of the link devices that are used frequently or that must be secured in units of stations are suitable for internal buffer access. For these data, set refresh parameters to utilize them for internal buffer access.
Page 133 FUNCTIONS (3) Link device access functions The following functions are available for link device access. Table4.15 Link device access function list Function Function name Description QBF_WriteLinkDevice mdSend mdRandW mdDevSet Writing data to link Writes data to link devices of CC-Link IE mdDevRst device controller network module.
Page 134: Parameter Settings
FUNCTIONS 4.5.3 Parameter settings Set the parameters on the <<Parameter settings>> tab screen of the CC IE Control utility. Section 9.4.5) Figure 4.45 Parameter settings screen - 54 4.5 CC-Link IE Controller Network Module Access Function 4.5.3 Parameter settings...
Page 135: Link Device Refresh Setting
FUNCTIONS 4.5.4 Link device refresh setting Link device refresh setting is required to use the internal buffer access in the user program. To enable the link device refresh, set the link device refresh cycle and refresh parameters in the CC IE Control utility. (1) Link device refresh cycle The link device refresh cycle is an interval of time during which the internal link device buffers of the C Controller module and link devices of the CC-Link IE controller...
Page 136 FUNCTIONS 4) Confirmation of total link devices refresh time The total link devices refresh time during the C Controller system operation can be confirmed in "Link device refresh time (Max./Min./Current)" on the <<Module information>> tab screen of the CC IE Control utility. Section 9.4.2) Total link devices refresh time during the C Controller system operation...
Page 137 FUNCTIONS (b) How to determine link device refresh cycle Determine the link device refresh cycle by the following flowchart. Calculation of total link devices refresh time (This section 1)) (This section (1)) Temporary setting of link device refresh cycle (This section 2)) (This section (2)) (This section 3)) Test run of C Controller system (This section (3))
Page 138 FUNCTIONS 3) Test run of C Controller system Perform the test run of the C Controller system to check whether the C Controller system operates properly with the link device refresh cycle that is temporarily set in 2). 4) C Controller system operation check Check the following 1) and 2) when the C Controller system is test-run with a temporary link device refresh cycle.
Page 139 FUNCTIONS 5) Corrective actions for C Controller system malfunction In the case of C Controller system malfunction or faulty user program processing performance, take actions 1) to 3) as necessary to correct the system operation. [Action 1: Increase the link device refresh cycle setting value.] Check the total link devices refresh time value (Max.) measured during C Controller system operation at "Link device refresh time (Max.)"...
Page 140 FUNCTIONS [Action 3: Reexamine the user program.] Reexamine the task configuration, priority, processing details, etc. of the user program in the C Controller module and make sure that the C Controller system specifications and user program processing performance are satisfied. (c) Link device refresh cycle setting Set the link device refresh cycle in "Link device refresh cycle"...
Page 141 FUNCTIONS (2) Refresh parameters The refresh parameters are designed to transfer the data of CC-Link IE controller network module’s link devices (LX, LY, LB and LW) to the internal link device buffers (LX, LY, LB and LW buffers) of a C Controller module for use in the user program. (a) Link refreshable devices The C Controller module allows 64 transfer settings (LX, LY, LB and LW) for each CC-Link IE controller network module.
Page 142 FUNCTIONS (3) Refresh parameter setting example The following provides a refresh parameter setting example. (a) System configuration Control station Normal station C Controller CC-Link IE CC-Link IE Power module controller controller supply network network module module Station Station No.1 No.2 Network No.1 Network No.2 Station...
Page 143 FUNCTIONS (c) CC IE Control utility: Refresh parameter settings screen Figure 4.57 CC-Link IE congroller network module (1st module) setting Figure 4.58 CC-Link IE congroller network module (2nd module) setting 4.5 CC-Link IE Controller Network Module Access Function - 63 4.5.4 Link device refresh setting...
Page 144: Link Data Send/Receive Processing Time Specifications
FUNCTIONS 4.5.5 Link data send/receive processing time specifications This section explains the cyclic transmission and processing time of CC-Link IE controller network modules. (1) Cyclic transmission function This function allows periodic data communication between stations on the same network, using link devices (LB/LW/LX/LY) of a CC-Link IE controller network module. (a) Send/receive processing in cyclic transmission In the following example, data of the C Controller module side link relay (B) are sent to the link relay (B) of another station’s C Controller module.
Page 145 FUNCTIONS (b) Total link devices refresh time ( The total link devices refresh time is calculated by the following expression according to the points assigned to link devices. [Total link devices refresh time] LB + LX + LY + (LW = KM1 + KM2 [ms] : Total link devices refresh time (sending side)
Page 146 FUNCTIONS (2) How to calculate transmission delay time (a) Delay time in cyclic transmission Calculation formulas for cyclic transmission delay time (time required for data to be delivered) are shown below. 1) For a single network system Table4.18 Calculation formulas for transmission delay time Transmission delay when L >LS[ms] Calculated value...
Page 147 FUNCTIONS (b) Transmission delay time calculation example The following shows a calculation example for cyclic transmission delay time in a single network system. (System configuration and conditions) Table4.19 System configuration and conditions Item Description CPU module on receiving station C Controller module Total number of stations per network 2 (Control station: 1, Normal station: 1) LB/LW...
Page 148 FUNCTIONS 3) Cyclic transmission delay Table4.20 Example of transmission delay time calculation Transmission delay when L >LS[ms] Calculated value Block data assurance per station enabled ) x 1.5 + LS x 0.5 + (L ) x 0.5 Normal value (100 + 1.41) x 1.5 + 1.25 x 0.5 + (100 + 1.41) x 0.5 = 203.445[ms] ) x 2 + LS x 1 + L Max.
Page 149 FUNCTIONS (3) Reduction of link device refresh time The link device refresh time can be shortened by reducing the number of refresh points to the C Controller module, setting proper refresh parameters/network range assignment parameters and making direct access to the link devices. (a) Concept of refresh range (points) The ranges set with the refresh parameters from the <<Parameter settings>>...
Page 150 FUNCTIONS (b) How to decrease the refresh points 1) Method using refresh parameters Up to 64 refresh ranges can be set for the C Controller module. For the refresh parameters, set only the ranges that need to be refreshed. C Controller module CC-Link IE controller network module Internal link device Network range assignment parameter...
Page 151 FUNCTIONS 2) Method using direct access By using direct access for link devices that are less frequently used on its own station and excluding those link devices from the link device refresh range, the link device refresh time can be reduced. CC-Link IE controller C Controller C Controller...
Page 152: Remote Operation Function
FUNCTIONS 4.6 Remote Operation Function The remote operation function is provided to control the operation of a C Controller module or programmable controller CPU from the user program or the C Controller setting utility of the development environment (personal computer). Use the bus interface functions to create the user program of the C Controller module.
Page 153 FUNCTIONS (4) Remote RUN/STOP methods Remote RUN/STOP can be executed by either of two methods: "Using user program" or "Using development environment (personal computer)". (a) Using user program Execute a bus interface function (QBF_Control or QBF_ControlEx function) from the user program to perform remote RUN/STOP. The functions used for remote RUN/STOP are as follows: Table4.21 Functions used for remote RUN/STOP Function name...
Page 154 FUNCTIONS (5) Precautions Pay attention to the following since the C Controller module gives priority to STOP. (a) STOP timing The C Controller module is stopped when remote STOP is executed from either the user program or C Controller setting utility. (b) Changing the module status to RUN again after remote STOP To bring the C Controller module status back to RUN again after having stopped it by remote STOP, use remote RUN.
Page 155: Remote Pause
FUNCTIONS 4.6.2 Remote PAUSE For the remote PAUSE operation from a programmable controller CPU, refer to the manual for the programmable controller CPU. (1) Definition of remote PAUSE Remote PAUSE is the operation performed to place the C Controller module in a PAUSE status from the user program or development environment (personal computer), with the RUN/STOP/MODE switch on the C Controller module set to RUN.
Page 156 FUNCTIONS (b) Using development environment (personal computer) On the <<Online operation>> tab of the C Controller setting utility, perform as described below. 1) Set "Remote operation" to "PAUSE" and select a target C Controller module or programmable controller CPU. 2) Click the button for remote PAUSE.
Page 157: Remote Reset
FUNCTIONS 4.6.3 Remote RESET (1) Definition of remote RESET Remote RESET is the operation performed to reset the C Controller module or programmable controller CPU from the user program or development environment (personal computer) when the C Controller module or programmable controller CPU is in the STOP status.
Page 158 FUNCTIONS (5) Confirmation before remote RESET (a) When the C Controller module is used in a single CPU system, or used as CPU No.1 in a multiple CPU system Before executing remote RESET, check the following conditions 1) to 2). Remote RESET is not allowed if any of the conditions 1) to 2) are not satisfied.
Page 159 FUNCTIONS POINT Remote RESET is not executable from the C Controller module when remote STOP is performed from the other peripheral devices (such as GX Developer). Cancel remote STOP of the peripheral device where remote STOP is being performed. For the remote operations of the programmable controller CPU, refer to the following manual.
Page 160 FUNCTIONS (6) Remote RESET methods Remote RESET can be executed by either of the following two methods: "Using user program" or "Using development environment (personal computer)". (a) Using user program Execute the bus interface function (QBF_Reset function) from the user program to perform remote RESET.
Page 161 FUNCTIONS (7) Precautions (a) Setting for remote RESET Before performing remote RESET, check the conditions described in (4) of this section. Remote RESET is not allowed if the conditions in (4) are not satisfied. (b) Before performing remote RESET Before performing remote RESET, close all user programs in the C Controller module.
Page 162: Relation Between Remote Operation And Run/Stop Status
FUNCTIONS 4.6.4 Relation between remote operation and RUN/STOP status This section explains the operations resulting from the combinations of the remote operation and the RUN/STOP/MODE switch setting of the C Controller module. (1) Relation between remote operation and RUN/STOP status of C Controller module The following table indicates the operations resulting from the combinations of the remote operation and the RUN/STOP status of the C Controller module.
Page 163 FUNCTIONS POINT Remote operation from the C Controller module toward the CPU No.1 (programmable controller module) can be performed by the following methods. • Remote RESET from C Controller setting utility • Remote RESET from bus interface function (QBF_Reset function) •...
Page 164: Self-Diagnostic Function
FUNCTIONS 4.7 Self-diagnostic Function (1) What is self-diagnostic function? The self-diagnostic function allows the C Controller module to check itself for errors during normal operation in order to prevent C Controller module malfunction and to provide preventive maintenance. (2) Processing after error detection The C Controller module operates as described below if it is started in the normal operation mode and an error is detected by the self-diagnostics.
Page 165 FUNCTIONS 4) When error occurred in any of CPU No.2 to 4 of multiple CPU system When a stop error has occurred in any of CPU No.2 to 4 of the multiple CPU system, whether to stop the whole multiple CPU system or not can be selected.
Page 166 FUNCTIONS Table4.26 Numbers indicated under "Error handling" and descriptions (Continued) Description Registration to event history file. Only when an error is detected without the same error being detected, the error is registered to the event history file. Table4.27 Self-diagnostic function list LED status Error handling C Controller...
Page 167 FUNCTIONS Table4.27 Self-diagnostic function list (Continued) LED status Error handling C Controller Diagnostic Item Description module status timing ERR. The system setting, multiple CPU Parameter error At power-on, setting and other parameters are Stop Flash detection at reset diagnosed. Intelligent function Intelligent function module At power-on, module parameter error...
Page 168: Output (Y) Status Setting For Switching Stop To Run
FUNCTIONS 4.8 Output (Y) Status Setting for Switching STOP to RUN (1) Output (Y) status setting for the case where STOP status is changed to RUN status When the C Controller module status is switched from RUN to STOP, the RUN-state output data (Y) are stored into the C Controller module and actual outputs are all turned off.
Page 169 FUNCTIONS (3) Processing (a) Previous state (Default) The outputs status (Y) immediately before the module is changed into the STOP status is output. Then, output from the user program is enabled. (b) Reset output (Y) The outputs turn to OFF. Then, output from the user program is enabled.
Page 170 FUNCTIONS (4) Setting of output (Y) status when switching STOP to RUN status On the <<System settings>> tab of the C Controller setting utility, set the output status before STOP when the STOP status has been changed to RUN. Output mode setting when switching from STOP to RUN...
Page 171: Clock Function
FUNCTIONS 4.9 Clock Function (1) What is clock function? The clock function allows reading of the clock data in the C Controller module by a user program to use them for time control. The clock data are mainly used for the time control of the functions performed by the C Controller module system, such as date and time data saving into the event history.
Page 172 FUNCTIONS (4) Changing and reading clock data (a) Changing clock data The clock data may be changed by either of the two methods: "Using C Controller setting utility" and "Using user program". 1) Using C Controller setting utility When using the C Controller setting utility, click the button on the Detail <<Online operation>>...
Page 173 FUNCTIONS (c) Clock data correction 1) Even if some of clock data is to be corrected, all clock data must be written to the C Controller module again. 2) When the year exceeds 2100 after setting the clock, the C Controller module can be used with the clock data of 2100 or later until it is restarted.
Page 174: Input Response Time Selection (I/O Response Time)
FUNCTIONS 4.10 Input Response Time Selection (I/O Response Time) (1) What is input response time selection? This function allows the input response time to be changed for each Q series module. The following table indicates the modules whose input response time can be set and their time options.
Page 175 FUNCTIONS (3) Precautions (a) When input response time is reduced Reducing the input response time value for high-speed response makes the module noise-sensitive. Take into account the operating environment when setting the input response time. (b) Timing when the setting becomes effective The input response time setting becomes effective when: •...
Page 176: Error Time Output Mode Setting
FUNCTIONS 4.11 Error Time Output Mode Setting (1) What is error time output mode setting? The error time output mode setting is a setting by which, when the C Controller module stops by a stop error, whether to clear or hold the data to be output to the Q series modules (the output, I/O composite, intelligent function, and interrupt modules) is specified.
Page 177: Hardware Error Time Cpu Operation Mode Setting
FUNCTIONS 4.12 Hardware Error Time CPU Operation Mode Setting (1) What is H/W error time CPU operation mode setting? The H/W error time CPU operation mode setting is a setting by which, when a hardware error occurs in the intelligent function module or interrupt module, whether to stop or continue the output (Y) from the C Controller module and writing to buffer memory is specified.
Page 178: Intelligent Function Module And Interrupt Module Switch Settings
FUNCTIONS 4.13 Intelligent Function Module and Interrupt Module Switch Settings (1) Intelligent function module and interrupt module switch settings The switch statuses of the Q series intelligent function modules and interrupt modules can be set on the C Controller setting utility. (2) Timing when the switch setting is written The switch setting is written from the C Controller module to each intelligent function module and/or interrupt module when the C Controller system is powered on or the C...
Page 179 FUNCTIONS (3) Intelligent function module and interrupt module switch settings Make this switch setting in "I/O assignment" on the <<I/O assignment settings>> tab of the C Controller setting utility. 1) Make the I/O assignment settings. 2) Select the button. Switch settings 3) Set the module switch data.
Page 180: Watchdog Timers (Wdt)
FUNCTIONS 4.14 Watchdog Timers (WDT) (1) Definition of watchdog timers (WDT) The watchdog timers are internal timers of the C Controller module that are used to detect hardware and user program errors of the C Controller module. The C Controller module has the following two different watchdog timers. (a) System watchdog timer The system watchdog timer monitors the C Controller module system and is used to detect hardware and system software errors.
Page 181 FUNCTIONS 2) User watchdog timer The user watchdog timer starts monitoring by the QBF_StartWDT function, and resets itself by the QBF_Reset WDT function. The user watchdog timer runs out if the user program was not able to execute the QBF_ResetWDT function due to incompletion of its processing within the time specified by the QBF_StartWDT function.
Page 182: Interrupt From Intelligent Function Module
FUNCTIONS 4.15 Interrupt from Intelligent Function Module (1) Interrupt from intelligent function module The C Controller module can receive the interrupt event from the interrupt module and the intelligent function module. In the user program, create a program to receive an interrupt event and execute the relevant processing using the QBF_WaitUnitEvent function.
Page 183 FUNCTIONS (b) Setting example The following is a setting example, showing SI 0 to 3 of the intelligent function module mounted to the slot whose start I/O No. is 20 are assigned to the interrupt pointers 50 to 53. Figure 4.79 Interrupt event setting example Remark This section explains the C Controller module side setting.
Page 184: Connection Between C Controller Module And Got (Microcomputer Connection)
FUNCTIONS 4.16 Connection between C Controller Module and GOT (Microcomputer Connection) (1) Connection between C Controller module and GOT (Microcomputer connection) By connecting a GOT to the C Controller module’s RS-232 interface by an RS-232 cable, the C Controller module can communicates with the GOT using virtual devices inside the GOT.
Page 185: Telnet Function
FUNCTIONS 4.17 Telnet Function Tin the C Controller module, the Shell command can be executed from the Telnet tool of the development environment (personal computer) without using Tornado. This allows simple remote debugging (task information display, memory dump, etc.) of the C Controller module.
Page 186 FUNCTIONS (3) Precautions for Telnet function (a) Connection of Telnet tool and C Controller module Connect the Telnet tool to the C Controller module on a one-to-one basis. Connection from multiple Telnet tools to the same C Controller module is not allowed.
Page 187: Chapter5 Settings And Procedures Before Operation
SETTINGS AND PROCEDURES BEFORE OPERATION CHAPTER5 SETTINGS AND PROCEDURES BEFORE OPERATION This chapter explains the preparatory procedures and setting methods for operating the C Controller module in a system. POINT Before handling the C Controller module, please read the Safety Precautions described in the beginning of this manual.
Page 188 SETTINGS AND PROCEDURES BEFORE OPERATION • The casing of the C Controller module is made of resin. Do not drop it or not apply strong shock to it. • Do not remove the printed boards of the module from the casing. Doing so may cause a failure.
Page 189 SETTINGS AND PROCEDURES BEFORE OPERATION 5.2 Fail-safe Circuit DANGER Provide a safety circuit outside the C Controller module to ensure that the entire system will operate safely even if an external power failure or C Controller module failure occurs. Failure to do so could result in accidents due to erroneous output or operation.
Page 190 SETTINGS AND PROCEDURES BEFORE OPERATION For each station's operating status in the event of a each DANGER station error, refer to the corresponding each station manual. Not doing so could result in erroneous output or operation. When controlling a running C Controller module (data modification) by connecting a personal computer to the C Controller module, create an interlock circuit on user programs so that the whole system functions safely all the time.
Page 191 SETTINGS AND PROCEDURES BEFORE OPERATION When the C Controller system is powered ON-OFF, the control output may not be supplied normally for a little while because of the delay time and rise time difference between the C Controller system power supply and the external power supply for the control target (especially in DC).
Page 192 SETTINGS AND PROCEDURES BEFORE OPERATION (1) System design circuit example (when not using ERR contact of power supply module) Power supply For AC For AC/DC Power supply Transformer Transformer Transformer Fuse Fuse Fuse C Controller C Controller RUN/STOP circuit module module power Started when RA1...
Page 193 SETTINGS AND PROCEDURES BEFORE OPERATION The power-ON procedure is as follows: For AC For AC/DC 1) Turn ON the power. 1) Turn ON the power. 2) Set the C Controller module to "RUN". 2) Set the C Controller module to "RUN". 3) Turn ON the start switch.
Page 194 SETTINGS AND PROCEDURES BEFORE OPERATION (2) System design circuit example (when using ERR contact of power supply module) Power supply For AC/DC Transfor- Transfor- Fuse Fuse C Controller RUN/STOP circuit DC power module Started when RA1 (control start output of C Controller (-) (+) module) turns ON.
Page 195 SETTINGS AND PROCEDURES BEFORE OPERATION * 1 Perform programming to execute the following operation at start of the C Controller module. 1) Turning ON Ym when battery voltage drop is detected. Create a program so that Ym is turned ON by the QBF_Y_Out_BitEx function when the "Built- in battery error status"...
Page 196 In such a case, all the I/O may turn ON or OFF depending on the failure, and normal operation and safety of the control target may not be ensured. Though Mitsubishi products are manufactured under strict quality control, the C Controller system may fail for unspecific reasons. To prevent mechanical damage and/or accidents in that case, please configure a fail-safe circuit outside the C Controller module.
Page 197 SETTINGS AND PROCEDURES BEFORE OPERATION 5.3 Settings and Procedures before Operation (1) Starting up the C Controller module Ethernet (Crossing cable) Development C Controller module environment (PC) Install Module setting/monitoring Factory-set values tool for C Controller module IP address [192.168.3. ] IP address [192.168.3.3] PVC-CCPU)
Page 198 SETTINGS AND PROCEDURES BEFORE OPERATION (2) When configuring a single CPU system C Controller module Development environment (PC) Ethernet Figure 5.9 Single CPU system configuration Procedures for operation This section (1) Start up the C Controller module. On the C Controller setting utility, make system setting Section 9.2.7 necessary to use the C Controller module.
Page 199 SETTINGS AND PROCEDURES BEFORE OPERATION (3) When configuring a CC-Link system C Controller module Development environment (PC) CC-Link Ethernet Figure 5.11 CC-Link system configuration Procedures for operation This section (1) Start up the C Controller module. This section (2) or Section 17.1 Set parameters, referring to (2) for a single CPU system, This section (2) or Section 16.1 or the flowchart in Section 17.1 for a multiple CPU system.
Page 200 SETTINGS AND PROCEDURES BEFORE OPERATION Move the RUN/STOP/MODE switch of the C Controller Section 5.4 (2) module from STOP to RUN, and check that the C Controller module is in the RUN status (the RUN LED is lit). Check the operation status (e.g. errors) in the system information of the C Controller setting utility.
Page 201 SETTINGS AND PROCEDURES BEFORE OPERATION (4) When configuring a MELSECNET/H system C Controller module Development environment (PC) MELSECNET/H Ethernet Figure 5.13 MELSECNET/H system configuration Procedures for operation This section (1) Start up the C Controller module. Set parameters, referring to (2) for a single CPU system, This section (2) or This section (2) or or the flowchart in Section 17.1 for a multiple CPU system.
Page 202 SETTINGS AND PROCEDURES BEFORE OPERATION Move the RUN/STOP/MODE switch of the C Controller Section 5.4 (2) module from STOP to RUN, and check that the C Controller module is in the RUN status (the RUN LED is lit). Check the operation status (e.g. errors) in the system information of the C Controller setting utility.
Page 203 SETTINGS AND PROCEDURES BEFORE OPERATION (5) When configuring a CC-Link IE controller network C Controller module Development environment (PC) CC-Link IE controller network Ethernet Figure 5.15 CC-Link IE controller network configuration Procedures for operation This section (1) Start up the C Controller module. Set parameters, referring to (2) for a single CPU system, This section (2) or This section (2) or...
Page 204 SETTINGS AND PROCEDURES BEFORE OPERATION Move the RUN/STOP/MODE switch of the C Controller Section 5.4 (2) module from STOP to RUN, and check that the C Controller module is in the RUN status (the RUN LED is lit). Check the operation status (e.g. errors) in the system information of the C Controller setting utility.
Page 205 SETTINGS AND PROCEDURES BEFORE OPERATION (6) When making microcomputer connection with GOT C Controller module Development environment (PC) RS-232 Ethernet Figure 5.17 Configuration of microcomputer connection with GOT Procedures for operation This section (1) Start up the C Controller module. Set parameters, referring to (2) for a single CPU This section (2) or system, or the flowchart in Section 17.1 for a multiple...
Page 206: Parts Names And Functions
SETTINGS AND PROCEDURES BEFORE OPERATION 5.4 Parts Names and Functions The part names of the C Controller module are shown in the external view of the Q06CCPU-V. The external view of the Q06CCPU-V-B is the same as that of the Q06CCPU-V, except for the following.
Page 207 SETTINGS AND PROCEDURES BEFORE OPERATION Table5.2 Part names Name Description Indicator LEDs Refer to this section (1) for the indicator LEDs. Connector used to connect the C Controller module to 10BASE-T/100BASE-TX. 10BASE-T/100BASE-TX interface (The C Controller module determines 10BASE-T or 100BASE-TX depending on connector (RJ45) the target device.) RS-232 interface connector...
Page 208 SETTINGS AND PROCEDURES BEFORE OPERATION (1) LED indicator specifications Q06CCPU-V Q06CCPU-V-B Q06CCPU-V Q06CCPU-V-B MODE MODE CF CARD ERR. ERR. CH2 SD/RD USER CH2 SD/RD USER CH1 10BASE-T/ 100BASE-TX Figure 5.22 LED indicators (a) In normal operation mode (When the MODE LED is lit "green") Change the operation mode by the switch.( This section (2), (3)) Table5.3 LED indicators and statuses in normal operation mode...
Page 209 SETTINGS AND PROCEDURES BEFORE OPERATION (b) In hardware self-diagnostic operation mode (When the MODE LED is lit "orange") Change the operation mode by the switch.( This section (2), (3)) Table5.4 LED indicators and statuses in hardware self-diagnostic operation mode LED indicator Name LED status Description...
Page 210 SETTINGS AND PROCEDURES BEFORE OPERATION (2) RUN/STOP/MODE switch operation STOP MODE Figure 5.23 RUN/STOP/MODE switch Table5.5 RUN/STOP/MODE switch Position Operation The C Controller module is operating. In normal operation mode (Output (Y) from user program and writing to buffer memory are enabled) In hardware self- diagnostic operation Refer to Section 18.5 for the hardware self-diagnostics function.
Page 211: Cable Connection
SETTINGS AND PROCEDURES BEFORE OPERATION 5.5 Cable Connection This section explains how to connect cables to the C Controller module. To realize a reliable system and fully utilize the C Controller module functions, wiring resistant to external noise is required. •...
Page 212: Network Settings For 1:1 Connection
SETTINGS AND PROCEDURES BEFORE OPERATION 5.6 Network Settings for 1:1 Connection Connect the development environment (personal computer) to the C Controller module on a one-to-one (1:1) basis by a crossing cable. After that, set the C Controller module using the C Controller setting utility on the development environment (personal computer).
Page 213 SETTINGS AND PROCEDURES BEFORE OPERATION (b) How to make network settings of development environment (personal computer) Make this setting on the "Internet Protocol (TCP/IP) Properties" screen. (Example) In the case of Microsoft Windows XP Professional Operating System Choose [Start] - [Control Panel], click "Network and Internet Connections" and then "Network Connections", and double-click the "Local Area Connection"...
Page 214 SETTINGS AND PROCEDURES BEFORE OPERATION (3) Accessing the C Controller module from the development environment (personal computer) (a) Confirmation of power-on Make sure that the C Controller module has been started up (powered on). (b) Setting on C Controller setting utility Start the C Controller setting utility on the development environment (personal computer), and select "192.168.3.3 (Default)"...
Page 215 SETTINGS AND PROCEDURES BEFORE OPERATION (c) Access to C Controller module Check the "Write authority" box, enter the login user information (User name, Password Section 5.11.2), and then click the button to access the Connect C Controller module in "Status with parameter write authority". Figure 5.30 Connection settings screen POINT When access to the C Controller module is not available, issue the PING...
Page 216 SETTINGS AND PROCEDURES BEFORE OPERATION (5) Changing the IP address of the C Controller module Perform the following to change the IP address of the C Controller module from the default IP (192.168.3.3). (a) Displaying the relevant screen From the <<Online operation>> tab of the C Controller setting utility, click the button and select the <<IP address>>...
Page 217 SETTINGS AND PROCEDURES BEFORE OPERATION (c) Network settings of development environment (personal computer) Change the network settings (IP address) of the development environment (personal computer) if necessary, and shut down the personal computer. (d) Connection to LAN Disconnect the crossing cable from the C Controller module and development environment (personal computer), and connect them to a LAN by different straight cables separately.
Page 218: Battery Specifications, Installation And Replacement
SETTINGS AND PROCEDURES BEFORE OPERATION 5.7 Battery Specifications, Installation and Replacement This section explains the battery specifications and installation. 5.7.1 Battery specifications The following are the specifications of the C Controller module battery. Table5.7 Battery specifications Type Item Q6BAT Classification Manganese dioxide lithium primary battery Initial voltage 3.0V...
Page 219: Installing Battery
SETTINGS AND PROCEDURES BEFORE OPERATION 5.7.2 Installing battery The battery for the C Controller module is shipped with its connector disconnected. Connect the connector before use. Open the C Controller module's bottom cover. Connector Confirm that the battery is loaded correctly.
Page 220: Replacing Battery
SETTINGS AND PROCEDURES BEFORE OPERATION 5.7.3 Replacing battery This section explains the replacement of the C Controller module battery. The battery of the C Controller module is used for standard ROM file protection and backup of the battery-backed-up RAM data and clock data. The battery must be replaced when the voltage of the C Controller module battery becomes low.
Page 221 SETTINGS AND PROCEDURES BEFORE OPERATION (b) When a battery error has occurred 1) The ERR. LED turns on, indicating that a battery error (error code: 1600, BATERY ERROR) has occurred. The error code can be checked on the <<Module information>> tab of the C Controller setting utility.
Page 222 SETTINGS AND PROCEDURES BEFORE OPERATION (2) Life of C Controller module battery (Q6BAT) The following indicates the life of the C Controller module battery. Table5.8 Battery life Battery life Actual service value Power-on Guaranteed value Guaranteed time after battery error (Reference value) time ratio occurrence...
Page 223 SETTINGS AND PROCEDURES BEFORE OPERATION POINT 1. Use the battery within the period not exceeding the guaranteed battery life value. 2. When it is expected that the guaranteed battery value will be exceeded, perform the following actions. • Perform shutdown procedures when powering off the C Controller module.( Section 5.7.4 (2)) •...
Page 224 SETTINGS AND PROCEDURES BEFORE OPERATION (4) C Controller module battery replacement procedure When the C Controller module battery has reached its end of life, replace it by the following procedure. Before removing the battery, keep the C Controller system ON for 10 minutes or more. Even if the battery is removed, the memory is backed up by the capacitor for some time.
Page 225: When Module Has Been Operated Without Battery
SETTINGS AND PROCEDURES BEFORE OPERATION 5.7.4 When module has been operated without battery This section provides the precautions to be taken when the module has been operated without a battery installed. IMPORTANT Always install a battery before starting operation. If operation has been started without a battery installed, be sure to perform shutdown procedures, and then power off the C Controller system.
Page 226 SETTINGS AND PROCEDURES BEFORE OPERATION (1) Clock data setting when C Controller system is powered on without battery installed (Clock data not guaranteed) If the C Controller system is powered up without a battery installed, it starts up with unreliable clock data. Since the program in which the event history file and/or clock data will not run properly, be sure to set clock data by either of the following methods.
Page 227 SETTINGS AND PROCEDURES BEFORE OPERATION (2) Shutdown procedures needed when powering off C Controller system without battery installed Be sure to perform shutdown procedures when powering off the C Controller system without a battery installed in the C Controller module. If the power is turned off without a battery installed, the saved data, such as the standard ROM parameter file, event history file, data being processed, user program, data file, and battery-backed-up RAM data, will be lost.
Page 228 SETTINGS AND PROCEDURES BEFORE OPERATION (4) Disabling battery error detection A battery error is detected when a battery is not installed in the C Controller module. Perform the operation described in (a) below to disable the battery error detection. * 1 Occurrence of a battery error will not change the CPU operation status. (If the CPU was in the RUN status, the module remains in the RUN status.) (a) Setting for disabling battery error detection 1) Uncheck the "Battery check"...
Page 229: Operation For Storing C Controller Without Battery
SETTINGS AND PROCEDURES BEFORE OPERATION 5.7.5 Operation for storing C Controller without battery When storing the C Controller module with the battery removed, be sure to perform shutdown procedures before powering off the C Controller system and removing the battery. IMPORTANT Failure to follow the procedures given below may corrupt the data in the standard ROM/ battery-backed-up RAM being accessed, or may generate a file system error.
Page 230: Installing/Removing Compactflash Card And Access Stop
SETTINGS AND PROCEDURES BEFORE OPERATION 5.8 Installing/Removing CompactFlash Card and Access Stop This section explains how to install and remove a CompactFlash card and how to stop access to the CompactFlash card. For the Q06CCPU-V-B, the CompactFlash card is not available. IMPORTANT While a file is being written to the CompactFlash card, do not switch the power off or remove the CompactFlash card.
Page 231 SETTINGS AND PROCEDURES BEFORE OPERATION [Removing or replacing CompactFlash card] Before removing or replacing the CompactFlash card, be sure to stop access to the CompactFlash card according to the following procedures. Removal or replacement of CompactFlash card Has the C Controller system been powered off? Is any file being written to the CompactFlash card?
Page 232 SETTINGS AND PROCEDURES BEFORE OPERATION (1) Installing the CompactFlash card (a) Removing the dummy CompactFlash card Open the front cover of the C Controller module, and remove the dummy CompactFlash card. Front cover EJECT button 1) Open the front cover. 2) Press the EJECT button.
Page 233 SETTINGS AND PROCEDURES BEFORE OPERATION (b) Installing a CompactFlash card When installing a CompactFlash card into the C Controller module, pay attention to its orientation. Push the CompactFlash card into the slot until the CompactFlash card edge is flush with the EJECT button. EJECT button STOP MODE...
Page 234 SETTINGS AND PROCEDURES BEFORE OPERATION (2) CompactFlash card removal (a) Removing the CompactFlash card Open the front cover of the C Controller module, and remove the CompactFlash card. Front cover EJECT button 1) Open the front cover. 2) Press the EJECT button.
Page 235: Stopping Access To Compactflash Card
SETTINGS AND PROCEDURES BEFORE OPERATION 5.8.2 Stopping access to CompactFlash card TO replace the CompactFlash card while the C Controller system power is on, it is necessary to stop access to the CompactFlash card. This section explains how to stopping access to the CompactFlash card and gives a sample program for that.
Page 236 SETTINGS AND PROCEDURES BEFORE OPERATION [When installing the CompactFlash card while the power is on] 1) Install the CompactFlash card. 2) Make sure that the CompactFlash card is mounted (the CF CARD LED is on). When the CF CARD LED turns on, access to files on the CompactFlash card is available.
Page 237: Unmounting Compactflash Card By Reset/Select Switch
SETTINGS AND PROCEDURES BEFORE OPERATION 5.8.3 Unmounting CompactFlash card by RESET/SELECT switch Unmount the CompactFlash card by operating the RESET/SELECT switch. Perform this operation only when a file is not being written to the CompactFlash card. (1) Unmounting procedures by the RESET/SELECT switch 1) Hold the RESET/SELECT switch in the SELECT position.
Page 238: Checking Number Of Erasures On Standard Rom
SETTINGS AND PROCEDURES BEFORE OPERATION 5.9 Checking Number of Erasures on Standard ROM The standard ROM built in the C Controller module is used to store various parameters and user programs. Since a flash ROM is used as the standard ROM, it has a limit on the number of writes (life).
Page 239: Setting C Controller Module Back To Factory-Set State
Is C Controller module operating normally? Format the standard ROM. This section (4) Is C Controller module operating normally? Please consult your local Mitsubishi Completed service center or representative, explaining a detailed description of the problem. Figure 5.45 Operating procedure 5.10 Setting C Controller Module Back to Factory-set State...
Page 240 SETTINGS AND PROCEDURES BEFORE OPERATION (2) Settings and file conditions after execution of each operation The following table indicates the settings and file conditions after "Default setting" mode execution and standard ROM formatting. Table5.10 File conditions Settings and file conditions CC-Link IE MELSEC- C Controller...
Page 241 SETTINGS AND PROCEDURES BEFORE OPERATION (3) Default setting mode operation To set the C Controller module back to the factory-set status, start up the C Controller module in the hardware self-diagnostics mode ( Section 18.5) and execute the "Default setting mode". 1) Start up the C Controller module in the hardware self-diagnostics mode (with the RUN/STOP/MODE switch set to "MODE").
Page 242 SETTINGS AND PROCEDURES BEFORE OPERATION (4) Standard ROM formatting method The following describes the standard ROM formatting method and the operation to be performed after standard ROM formatting. If the standard ROM is formatted, each file in the standard ROM is cleared. Back up the essential data, user program and parameter file before performing the following operations.
Page 243 SETTINGS AND PROCEDURES BEFORE OPERATION 1) Formatting by creating a script file on a CompactFlash card • Write the following script file "STARTUP.CMD" to the CompactFlash card, install the CompactFlash card into the C Controller module, and start up the C Controller module. (The RUN LED flashes during processing of the script file "STARTUP.CMD".) <Sample script file for standard ROM formatting...
Page 244: Login User Setting And Restrictions
SETTINGS AND PROCEDURES BEFORE OPERATION 5.11 Login User Setting and Restrictions By setting the user name and password to the C Controller module and starting it as a login user, FTP file access and operations performed from each utility are restricted. 5.11.1 Functions to which access can be restricted by login user setting The C Controller module can restrict the access of the following functions.
Page 245: Login User Setting
<Program example> When registering "qcpu" as a user name and "mitsubishi" as a password: 1) Encrypt the password with the loginDefaultEncrypt function or the vxencrypt command When using the vxencrypt command, start it from the command prompt of the development environment (personal computer).
Page 246 SETTINGS AND PROCEDURES BEFORE OPERATION (2) Precautions (a) Application of login user setting of C Controller module Although the login user setting of the C Controller module restricts user access for the C Controller setting operations, it does not completely prevent illegal access from outside.
Page 247: Maintenance And Inspection
SETTINGS AND PROCEDURES BEFORE OPERATION 5.12 Maintenance and Inspection DANGER Do not touch the terminals while power is on. Doing so could cause a malfunction. Correctly connect the battery. Also, do not charge, disassemble, heat, place in fire, short circuit, or solder the battery. Mishandling of the battery can cause overheating or cracks which could result in injury and/or fires.
Page 248 SETTINGS AND PROCEDURES BEFORE OPERATION CAUTION Do not disassemble or modify the modules. Doing so could cause malfunction, erroneous operation, injury, or fire. Perform the online operations during system operation (especially, program modification, forced output or operation status change), shall be conducted after reading the manual carefully and ensuring the safety.
Page 249: Daily Inspection
SETTINGS AND PROCEDURES BEFORE OPERATION 5.12.1 Daily inspection The following indicates the items to be inspected daily. Table5.14 Daily inspection Item Inspection Item Inspection Judgment Criteria Remedy Check that fixing screws are The screws and cover must Installation of base unit not loose and the cover is not Retighten the screws.
Page 250: Periodical Inspection
SETTINGS AND PROCEDURES BEFORE OPERATION 5.12.2 Periodical inspection This section explains the items to be inspected once or twice every six months or every year. Note that these inspections must be implemented when the system is moved or modified or when the wiring is changed, for example. Table5.15 Periodic inspection Item Inspection Item...
Page 251: Chapter6 I/O Number Assignment
I/O NUMBER ASSIGNMENT CHAPTER6 I/O NUMBER ASSIGNMENT This chapter explains the I/O number assignment required for the C Controller module to communicate data with I/O modules and/or intelligent function modules. 6.1 Relation between No. of Base Units and No. of Slots The C Controller module can construct a system in the following configurations.
Page 252 I/O NUMBER ASSIGNMENT (2) Precautions for the number of mounted modules Mount modules within the range of the allowed number of slots. Even if the total number of slots for a main base unit and extension base units is greater than the number of available slots (for example, six 12-slot base units are used), no error will occur as long as modules are mounted in slots whose number is within a valid range.
Page 253: Connecting Extension Base Units And Setting No. Of Stages
I/O NUMBER ASSIGNMENT 6.2 Connecting Extension Base Units and Setting No. of Stages The model, Q5 B or Q6 B is available as the extension base unit. The Q6 RB and QA1S6 B are not to be used. (1) Extension stage number setting and setting order When using extension base units for extension, set the extension stage numbers with the stage number setting connectors on the extension base units.
Page 254 I/O NUMBER ASSIGNMENT (2) Precautions for extension stage number setting (a) Extension stage number setting order Set the extension stage numbers consecutively. If any extension stage number is skipped in the auto mode ( Section 6.3 (1)) of base unit assignment, 0 slot is set to the skipped stage and the number of empty slots does not increase.
Page 255 I/O NUMBER ASSIGNMENT (b) When the same extension stage number is set The same extension stage number cannot be set to multiple extension base units. Main base unit Q312B Slot number Power supply C Controller module module Extension base unit Q68B Extension 1 The same extension stage...
Page 256 I/O NUMBER ASSIGNMENT (c) When connector pins are inserted into two or more positions or no connector pin is inserted Extension base units cannot be used with connector pins inserted in two or more positions. Also, they cannot be used without connector pins being inserted. Main base unit Q312B Slot number...
Page 257: Base Unit Assignment (Base Mode)
I/O NUMBER ASSIGNMENT 6.3 Base Unit Assignment (Base Mode) The C Controller module has the Auto mode and Detail mode, in which the number of modules mounted on the main base unit, slim type main base unit,and/or extension base unit can be assigned. The base mode can be set on the <<I/O assignment settings>>...
Page 258 I/O NUMBER ASSIGNMENT (b) For 5-slot base unit: 5 slots are occupied Main base unit Q35B Power supply C Controller module module Extension base unit Q65B Figure 6.7 5 For 5-slot base units (c) For 8-slot base unit: 8 slots are occupied Main base unit Q38B Slot number...
Page 259 I/O NUMBER ASSIGNMENT (d) For 12-slot base unit: 12 slots are occupied Main base unit Q312B Slot number Power supply C Controller module module Extension base unit Q612B Figure 6.9 For 12-slot base units 6.3 Base Unit Assignment (Base Mode)
Page 260 I/O NUMBER ASSIGNMENT (2) Detail mode In Detail mode, set the number of mountable modules to each base unit on the <<I/O assignment settings>> tab of the C Controller setting utility. (a) Applications Since an empty slot set as 0 point in the I/O assignment occupies 1 slot, this mode is used to make the unused slots unrecognized.
Page 261 I/O NUMBER ASSIGNMENT 2) When the preset number of slots is less than the number of actually used slots The slots other than those designated are disabled. For example, when 8 slots are designated for a 12-slot base unit, the 4 slots on the right of the base unit are disabled.
Page 262 I/O NUMBER ASSIGNMENT (3) Base mode setting screen and settings on C Controller setting utility Figure 6.12 I/O assignment settings (a) Base model Set the mounted base unit model name within 16 characters. The C Controller module does not use the preset model name. (It is used as a user's memo) (b) Power model Set the mounted power supply module model name within 16 characters.
Page 263: What Is I/O Number
I/O NUMBER ASSIGNMENT 6.4 What is I/O Number? I/O numbers indicate the addresses used in a user program to input or output ON/OFF data between the C Controller module and other modules. (1) Input and output of ON/OFF data Input (X) is used to input ON/OFF data to the C Controller module, and output (Y) is used to output ON/OFF data from the C Controller module.
Page 264: I/O Number Assignment
I/O NUMBER ASSIGNMENT 6.5 I/O Number Assignment 6.5.1 I/O number of base unit The C Controller module assigns I/O numbers at power-on or reset. Figure 6.14 shows an example of the I/O number assignment when the base unit is set in Auto mode without I/O assignment.
Page 265 I/O NUMBER ASSIGNMENT To assign I/O numbers, follow the items below: (1) Number of slots of base units The number of slots of base units is set in Base mode.( Section 6.3) (a) In Auto mode The number of slots is determined as the available number of modules mounted to each base unit.
Page 266 I/O NUMBER ASSIGNMENT (5) I/O numbers of empty slots For empty slots on the base unit to which no I/O modules or intelligent function modules are mounted, points can be set on the <<System settings>> tab of the C Controller setting utility. (Default is 16 points.) POINT In Auto mode, if an extension stage is skipped in the setting using the stage number setting connectors of the base units, the skipped extension stage is not...
Page 267: I/O Assignment By C Controller Setting Utility
I/O NUMBER ASSIGNMENT 6.6 I/O Assignment by C Controller Setting Utility This section describes the I/O assignment using C Controller setting utility. 6.6.1 Purpose of I/O assignment by C Controller setting utility Perform I/O assignment settings by C Controller setting utility in the following cases. (1) Reserving points when changing to module other than 16-point module You can reserve the number of points in advance so that you do not have to change the I/O numbers when the current module will be replaced with the one of a different...
Page 268 I/O NUMBER ASSIGNMENT POINT 1. The I/O assignment settings become effective when either of the following operations is performed after writing parameters on the C Controller setting utility. • Reapply power to the C Controller system (ON, OFF and ON). •...
Page 269: Details Of I/O Assignment By C Controller Setting Utility
I/O NUMBER ASSIGNMENT 6.6.2 Details of I/O assignment by C Controller setting utility In I/O assignment, the "Type (module type)", "Points (I/O points)" and "Start X/Y" (starting I/O number) can be set for each slot of the base units. For example, to change the number of occupied I/O points of a designated slot, only the number of occupied I/O points can be designated.
Page 270 I/O NUMBER ASSIGNMENT (b) Type (For C Controller module) Select the type of the modules being mounted from the following: • Empty (Empty slot) • Input (Input module) • Hi Input (Q Series high speed module) • Output (Output module) •...
Page 271 I/O NUMBER ASSIGNMENT (2) Precautions for I/O assignment (a) Slot status after I/O assignment When I/O assignment settings have been made to a slot, that settings have precedence over the mounted module. 1) When the preset number of points is less than the number of I/O points of modules actually mounted The I/O points for actually mounted modules are decreased.
Page 272 I/O NUMBER ASSIGNMENT 5) Last I/O number In the I/O assignment settings, the last I/O number must be FFF or lower. If it has exceeded FFF , an Intelli. module assignment err. (error code: 2124, SP.UNIT LAY ERR.) will occur. - 22 6.6 I/O Assignment by C Controller Setting Utility 6.6.2 Details of I/O assignment by C Controller setting utility...
Page 273 I/O NUMBER ASSIGNMENT (b) Precautions for automatic start X/Y assignment by C Controller module When the start X/Y has not yet entered, the C Controller module automatically assigns it. In the case of 1) or 2) below, therefore, the start X/Y setting of each slot may overlap the one assigned by the C Controller module.
Page 274: I/O Number Assignment Examples
I/O NUMBER ASSIGNMENT 6.7 I/O Number Assignment Examples The following example shows I/O number assignment performed using C Controller set- ting utility. (1) When changing the number of points of an empty slot from 16 to 32: Reserve 32 points so that the I/O numbers of Slot No. 4 and later will not change when a 32-point input module is mounted in the currently empty slot position (Slot No.
Page 275 I/O NUMBER ASSIGNMENT (b) I/O assignment with C Controller setting utility Set "32 points" to Slot No.3 on <<I/O assignment settings>> tab of the C Controller setting utility. Select 32 points. (When the type is not selected, the type of the installed module will be selected.) Figure 6.20 I/O assignment (When changing points of empty Slot 3) (c) I/O number assignment after change with C Controller setting utility...
Page 276 I/O NUMBER ASSIGNMENT (2) Changing the I/O number of the slot Change the I/O number of an empty slot (slot No. 3) to X200 through X21F so that the I/O numbers of slot No. 4 and later slots will not change when a 32-point input module is mounted to the empty slot (slot No.
Page 277 I/O NUMBER ASSIGNMENT (b) I/O assignment with C Controller setting utility Set "200" to Slot No.3 and "70" to Slot No.4 on <<I/O assignment settings>> tab of the C Controller setting utility. "200" is specified as the start I/O number. "70"...
Page 278: Checking I/O Numbers
I/O NUMBER ASSIGNMENT 6.8 Checking I/O Numbers The mounted modules used with the C Controller module and their I/O numbers can be confirmed in "System information" on the <<Module monitoring>> tab of the C Controller setting utility. ( Section 9.2.5 (3)) - 28 6.8 Checking I/O Numbers...
Page 279: Chapter7 Memories And Files Handled By Ccontroller Module
MEMORIES AND FILES HANDLED BY C CONTROLLER MODULE CHAPTER7 MEMORIES AND FILES HANDLED BY C CONTROLLER MODULE This chapter explains the memories and file operations of the C Controller module and the precautions for them. 7.1 Memory of C Controller Module This section explains the user memories and system memory applicable to the C Controller module.
Page 280 MEMORIES AND FILES HANDLED BY C CONTROLLER MODULE (2) Data that can be stored into user memories of C Controller module The following data can be stored into the work RAM, battery-backed-up RAM, standard ROM, and CompactFlash card of the C Controller module. Table7.1 Data that can be stored into user memories Built in C Controller module Standard...
Page 281: System Memory
MEMORIES AND FILES HANDLED BY C CONTROLLER MODULE (4) Memory capacities and necessity of formatting The following shows capacities of memories used for the C Controller module and whether formatting is necessary or not. Table7.3 Memory capacities and necessity of formatting Memory name Memory capacity Formatting...
Page 282: File Operation And Handling Precautions
MEMORIES AND FILES HANDLED BY C CONTROLLER MODULE 7.2 File Operation and Handling Precautions 7.2.1 File operation The files stored in the standard ROM or CompactFlash card (Q06CCPU-V only) can be read, written, and verified through the following: 1) C Controller setting utility 2) CC-Link utility 3) MELSECNET/H utility 4) CC IE Control utility (Q06CCPU-V only)
Page 283: Precautions For Handling Files
MEMORIES AND FILES HANDLED BY C CONTROLLER MODULE 7.2.2 Precautions for handling files The following are the precautions for handling the files of the C Controller module. (1) Precautions for file writing When writing a file to the standard ROM or CompactFlash card, set the C Controller module to the STOP status.
Page 284: Chapter8 Installing And Uninstalling Sw[]Pvc-Ccpu
INSTALLING AND UNINSTALLING SW PVC-CCPU CHAPTER8 INSTALLING AND UNINSTALLING SW[]PVC- CCPU This chapter explains how to install or uninstall the SW PVC-CCPU. 8.1 Development Environment The following are the product requirements of SW PVC-CCPU. Table8.1 Product requirements of SW PVC-CCPU Item Description Personal computer with Pentium /Celeron...
Page 285: Installation
INSTALLING AND UNINSTALLING SW PVC-CCPU 8.2 Installation This section explains the installation of SW PVC-CCPU. (1) Installation procedures Start Install Tornado into the development Tornado's Manual environment (personal computer). Install SW PVC-CCPU into the This section (2) development environment (personal computer).
Page 286 INSTALLING AND UNINSTALLING SW PVC-CCPU 1) Turn on the development environment (personal computer) to start Windows . 2) Click [Start] [Control Panel]. REMARKS When using the following OS, click [Start] [Setting] [Control Panel]. • Windows NT Workstation 4.0 • Windows 2000 Professional 3) Open "Add or Remove Programs"...
Page 287 INSTALLING AND UNINSTALLING SW PVC-CCPU (From previous page) 5) The screen on the left shows that "Setup.exe" was detected. Click the button to start installation. Finish If "Setup.exe" was not found, click the button Browse... and change it to the location where "Setup.exe" exists. 6) When the left message has appeared, SW PVC-CCPU has already been installed.
Page 288 INSTALLING AND UNINSTALLING SW PVC-CCPU (From previous page) 10)When the left screen has appeared, specify the folder of installation destination. (When was clicked in Step 9 above), this screen does not appear.) Clicking starts installation into the "Destination Next> Folder". To install it into other than the "Destination Folder"...
Page 289: Icons To Be Registered
INSTALLING AND UNINSTALLING SW PVC-CCPU 8.3 Icons to be Registered Once SW PVC-CCPU is installed, the following icons are registered to the location displayed by [Start] [All Programs] [MELSEC] [C Controller]. Table8.2 Icons registered to Start menu Icon Name Description Bus interface function HELP Starts the bus interface function HELP.
Page 290: Uninstallation
INSTALLING AND UNINSTALLING SW PVC-CCPU 8.4 Uninstallation This section explains the uninstallation of SW PVC-CCPU. The screens used in this section are those of Microsoft Windows XP Professional. When uninstalling SW PVC-CCPU into either of the following OS, refer to REMARKS •...
Page 291 INSTALLING AND UNINSTALLING SW PVC-CCPU (From previous page) 2) Open "Add or Remove Programs" and select "Change or Remove Programs". When the left screen has appeared, select "SW PVC- CCPU" and click the button. Change/Remove REMARKS • When using Windows 2000 Professional, open "Add/ Remove Programs"...
Page 292: Chapter9 Utility Operation
UTILITY OPERATION CHAPTER9 UTILITY OPERATION The following lists the utilities included in SW PVC-CCPU. Table9.1 Utility list of SW PVC-CCPU Applicability Reference Q06CCPU- Q06CCPU- Utility name Description section The C Controller setting utility has the following functions. • Displaying the module information (LED status, switch status, error information, etc.) of the C Controller module.
Page 293: Common Utility Operations
UTILITY OPERATION 9.1 Common Utility Operations This section explains the operation common to the utilities. 9.1.1 Starting utility To start a utility, choose [Start] [All Programs] [MELSEC] [C Controller], and click a desired item in the following menu. Starts the Bus Interface Function HELP. Starts the C Controller setting utility.
Page 294: Exiting Utility
UTILITY OPERATION 9.1.2 Exiting utility This section explains how to exit the utilities. (1) To exit a utility other than the Device monitoring utility, click the button at bottom Exit right of the utility screen. Click. Figure 9.2 Exiting the C Controller setting utility (2) To exit the Device monitoring utility, click [Menu] [Exit] on the menu bar.
Page 295: Setting Connection Target
UTILITY OPERATION 9.1.3 Setting connection target This section explains Connection settings to connect the development environment (personal computer) to the C Controller module. (1) Connection status (a) Online A status, in which each utility and the C Controller module are connected, is defined as online.
Page 296 UTILITY OPERATION (3) Operating Connection settings screen Starting each utility displays the following screen. To set the connection target, enter the IP address or host name of the execution target (C Controller module) into the "Connection settings" box, and click the Connect button.
Page 297 UTILITY OPERATION Table9.2 Explanation of Connection settings screen (Continued) Item Description Detailed settings Opens the Detailed settings screen. ( this section (3)(a)) button Performs the following processing and closes the "Connection settings" screen. • As the connection target, sets the IP address and host name specified button Connect in "Connection settings".
Page 298 UTILITY OPERATION (a) Detailed settings screen For Ethernet communication between the development environment (personal computer) and C Controller module, set values for Communication check time and Retry count. Figure 9.7 Detailed settings screen Table9.3 Explanation of Detailed settings screen Item Description Set a communication check time for Ethernet communication Communication...
Page 299: Displaying Help Screen
UTILITY OPERATION 9.1.4 Displaying Help screen This section explains how to display the Help screen of the utility. (1) Utilities other than the Device monitoring utility To display the Help screen of the utilities other than the Device monitoring utility, click button at bottom right of the utility screen.
Page 300: Checking Version
UTILITY OPERATION 9.1.5 Checking version This section explains how to check the utility version. (1) Utilities other than the Device monitoring utility To check the version of the utilities other than the Device monitoring utility, select [Version information] in the system menu. C Controller setting utility..
Page 301: Parameter Setting File
UTILITY OPERATION 9.1.6 Parameter setting file This section explains the parameter setting files of the utilities other than the Device monitoring utility. (1) Loading/saving the parameter setting file The following indicates a parameter setting file loading/saving procedure. 1) Click the button to load the parameter setting file.
Page 302 UTILITY OPERATION Remark 1. The name of the currently used parameter setting file is displayed on the status bar of the utilities other than the Device monitoring utility. C Controller setting utility, CC-Link utility, or MELSECNET/H utility. 2. The following indicates the extensions for parameter setting files. Table9.6 Extensions of parameter setting files Utility name Parameter setting file extension...
Page 303: Displays On Title And Status Bars
UTILITY OPERATION 9.1.7 Displays on title and status bars This section explains the title bar and status bar of each utility. (1) Title bar (a) Connection target display 1) Online When the utility is online, the IP address or host name of the connection target module is displayed on the title bar.
Page 304: C Controller Setting Utility
UTILITY OPERATION 9.2 C Controller Setting Utility This section explains the operation of the C Controller setting utility. The following are the precautions for use of the C Controller setting utility. (1) Maximum number of concurrently applicabe C Controller setting utilities Up to 8 C Controller setting utilities can be activated used at the same time.
Page 305: Function List Of C Controller Setting Utility
UTILITY OPERATION 9.2.1 Function list of C Controller setting utility This section explains the functions of the C Controller setting utility. Table9.7 Function list of C Controller setting utility Applicability Reference Q06CCPU- Q06CCPU- Name Description section Sets the C Controller module to which this utility will be Connection settings 9.1.3 connected.
Page 306: Operating Module Information Screen
UTILITY OPERATION 9.2.2 Operating Module information screen The Module information screen displays the LED and switch statuses, error information, and drive information of the C Controller module. POINT 1. Monitoring is stopped when the <<Module information>> tab is switched to another tab during monitor.
Page 307 UTILITY OPERATION Table9.8 Explanation of Module information screen Module information Event history SRAM monitoring Module monitoring Online operation Reference Item Description section Module information Displays the information of the C Controller module. Displays the LED status of the C Controller module. LED information 5.4 (1) Note that the CH2 SD/RD indication is invalid.
Page 308: Operating Event History Screen
UTILITY OPERATION 9.2.3 Operating Event history screen (1) Precautions for Event history screen (a) Event history update timing Event history data are acquired from the C Controller module and updated when connection is made to the C Controller module by Connection settings or when button is clicked.
Page 309 UTILITY OPERATION (2) Event history screen This screen displays/saves the history of events that occurred in the C Controller module. Figure 9.20 Event history screen Table9.9 Explanation of Event history screen Event history Module information SRAM monitoring Module monitoring Online operation Reference Item Description...
Page 310 UTILITY OPERATION Table9.9 Explanation of Event history screen (Continued) Event history Module information SRAM monitoring Module monitoring Online operation Reference Item Description section Displays the history of up to 512 events that occurred in the C Controller module. If 513 or more events have occurred, the oldest data is deleted and a new This section Event history event is recorded.
Page 311 UTILITY OPERATION (3) Detailed event information screen Double-clicking an event as stated (2) in this section displays the detail information of the event on a single screen. Figure 9.21 Detailed event information screen Table9.10 Explanation of Detailed event information screen Reference Item Description...
Page 312 UTILITY OPERATION (4) Details of event types The following indicates the details of the event types. Table9.11 Details of event types Display Description System (Err.) The event is a C Controller system error. System (Warning) The event is a C Controller system warning. System (Info.) The event is C Controller system information.
Page 313 UTILITY OPERATION (b) CSV file saved on previous page (a) Event history,192.168.3.3(Default)[CR][LF] 4[CR][LF] Date,Time,Source flag,Source,Event No.,Event information[CR][LF] 2008/02/14,16:40:01,0001,MQbfDrv ,C000020B,An error occurred ror information: -][CR][LF] 2008/02/14,16:40:01,0001,MQbfDrv ,C0000201,AC/DC DOWN occ me of occurrence: 2004/01/24 08:19:05][CR][LF] 2008/02/14,16:33:45,0001,MQbfDrv ,C000020B,An error occurred ror information: -][CR][LF] 2008/02/14,16:33:45,0001,MQbfDrv ,C0000201,AC/DC DOWN occ me of occurrence: 2004/01/24 08:18:52][CR][LF] [EOF]...
Page 314: Operating Sram Monitoring Screen
UTILITY OPERATION 9.2.4 Operating SRAM monitoring screen Danger When performing the control (data change) of an operating C Controller module connected to a development environment (personal computer), configure an interlock circuit in the user program so that the whole system will always operate safely. When performing the other control (operating status change (status control)) of the operating C Controller module or when operating the development environment (personal computer), configure an...
Page 315 UTILITY OPERATION Table9.12 Explanation of SRAM monitoring screen SRAM monitoring Module information Event history Module monitoring Online operation Reference Item Description section Monitors battery-backed-up RAM data. Double-clicking one of the data, or selecting it and pressing the [ENTER] SRAM monitoring key during monitoring enables data entry.
Page 316 UTILITY OPERATION SRAM monitoring screen display Memory status Address Address +00 +01 +02 +03 Display data Display data 56 34 12 34 56 78 12 34 56 78 For the For the Q06CCPU-V Q06CCPU-V-B Figure 9.25 Display example at "DWORD" setting (3) Data settings dialog box Data are entered into the battery-backed-up RAM.
Page 317 UTILITY OPERATION (a) Display on SRAM monitoring screen (when "BYTE" is set as "Monitoring type") Figure 9.28 SRAM monitoring screen (b) CSV file saved on above screen (a) Battery backup RAM data,192.168.3.3(Default)[CR][LF] Offset,[+00],[+01],[+02],[+03], ,[+0D],[+0E],[+0F][CR][LF] 0x00000000,12,34,56,78, ,00,00,00[CR][LF] 0x00000010,00,00,00,00, ,00,00,00[CR][LF] 0x00000020,00,00,00,00, ,00,00,00[CR][LF] 0x0001FFE0,00,00,00,00, ,00,00,00[CR][LF] 0x0001FFF0,00,00,00,00,...
Page 318 UTILITY OPERATION (d) Specifications of binary format • The extension is "bin". • When saved in binary format, the battery-backed-up RAM data are saved as they are. Remark The standard directory for the battery-backed-up RAM data is "C:\MELSEC\CCPU\Param". (When SW PVC-CCPU is installed in "C:\MELSEC") - 27 9.2 C Controller Setting Utility...
Page 319: Operating Module Monitoring Screen
UTILITY OPERATION 9.2.5 Operating Module monitoring screen Danger When performing the control (data change) of an operating C Controller module connected to a development environment (personal computer), configure an interlock circuit in the user program so that the whole system will always operate safely. When performing the other control (operating status change (status control)) of the operating C Controller module or when operating the development environment (personal computer), configure an...
Page 320 UTILITY OPERATION (d) Monitor and test Module monitor and test (forced output of output (Y), forced write to buffer memory and CPU shared memory) performed on this screen are executed for the module installed to "Slot No." set on this screen. They do not depend on the data in the "Type"...
Page 321 UTILITY OPERATION (2) Module monitoring screen The input (X), output (Y) and buffer memory statuses of the module installed to the selected slot are monitored on this tab. Also the forced output of the output (Y) and forced write to the buffer memory can be executed.
Page 322 UTILITY OPERATION Table9.13 Explanation of Module monitoring screen (Continued) Module monitoring Module information Event history SRAM monitoring Online operation Reference Item Description section Displays the number of I/O points and type of the module if the slot where any other than CPU modules is installed is specified in "Slot No." The value within parentheses is the "points"...
Page 323 UTILITY OPERATION Table9.13 Explanation of Module monitoring screen (Continued) Module monitoring Module information Event history SRAM monitoring Online operation Reference Item Description section Specify the buffer memory offset address of the intelligent function module to be monitored. This address can only be set for the intelligent function module. Buffer memory Offset This area display is switched to "CPU shared memory address"...
Page 324 UTILITY OPERATION (3) System information screen Displays the information of the C Controller system. System configuration Figure 9.31 System information screen Table9.15 Explanation of System information screen Reference Item Description section Displays the status of the CPU module(s) that comprises the C Controller system.
Page 325 UTILITY OPERATION Table9.14 Explanation of System information screen (Continued) Reference Item Description section CPU status Selecting the C Controller module (host CPU) and clicking button will start Help of the C Controller setting utility and Error code help display the help information on the current error. This button can be used button Error code help only when the C Controller module (host CPU) is selected.
Page 326 UTILITY OPERATION (a) Error details screen Figure 9.32 Error details screen Table9.16 Explanation of Error details screen Reference Item Description section Common error information Displays common information corresponding to the error code. Individual error information Displays individual information corresponding to the error code. * 1 For errors of C Controller modules, refer to Section 18.3.
Page 327 UTILITY OPERATION (b) CSV file saved on screen of previous page (a) System information,192.168.3.3(Default)[CR][LF] CPU status[CR][LF] CPU module,Status,Switch,Error code,Present error,Date,Time[CR][LF] No. 1,RUN,RUN,0,No error[CR][LF] [CR][LF] [CR][LF] [CR][LF] [CR][LF] Slot,Type,Series,Model name,Points,Start I/O No.,Control CPU,Serial No.,Ver.[CR][LF] CPU,CPU,Q,Q06CCPU-V,-,3E00,-,100120000000000,B[CR][LF] 0(0-0),Intelli.,Q,QJ61BT11N,32 points,0000,No. 1,080320000000000,B[CR][LF] 1(0-1),Intelli.,Q,QJ71LP21-25,32 points,0020,No. 1,060820000000000,D[CR][LF] 2(0-2),Input,Q,QX41,16 points,0040,No.
Page 328: Operating Online Operation Screen
UTILITY OPERATION 9.2.6 Operating Online operation screen POINT 1. If a communication error has occurred during connection, set Connection settings again. 2. Communication are not available during reset of the C Controller module. Start communication after terminating the reset process. (1) Online operation screen This screen allows parameter read/write/verification, remote operation, clock setting, and IP address setting for the C Controller module.
Page 329 UTILITY OPERATION Table9.15 Explanation of Online operation screen (Continued) Online operation Module information Event history SRAM monitoring Module monitoring Reference Item Description section Writes parameters, which were set on the C Controller setting utility, to the C Controller module. The written parameters become valid when the C Controller module is powered off and then on or is reset.
Page 330 UTILITY OPERATION (2) Detailed settings screen Set the IP address, Clock, MD function (Q06CCPU-V only), and Option settings of the C Controller module. Figure 9.36 Detailed settings screen Table9.18 Explanation of Detailed settings screen IP address(*) Clock(*) MD function Option Reference Item Description...
Page 331 UTILITY OPERATION (a) IP address settings screen Set the IP address to be used by the C Controller module. Figure 9.37 IP address screen Table9.19 Explanation of IP address screen IP address(*) Clock(*) MD function Option Reference Item Description section *1, *2 Displays and sets the IP address used by the C Controller module.
Page 332 UTILITY OPERATION (b) Clock setting screen Set the clock of the C Controller module. Figure 9.38 Clock setting screen Table9.21 Explanation of Clock setting screen Clock(*) IP address(*) MD function Option Reference Item Description section Displays and sets the date used in the C Controller module. Date (Setting range: 2000/1/1 to 2099/12/31) Displays and sets the time used in the C Controller module.
Page 333 UTILITY OPERATION (c) MD function screen Set the timeout period of communication made by the MELSEC data link function. This is not available for the Q06CCPU-V-B. Figure 9.39 MD function screen Table9.22 Explanation of MD function screen MD function IP address(*) Clock(*) Option Reference...
Page 334 UTILITY OPERATION (d) Option screen Set the processing priority for communication with the C Controller module. Figure 9.40 Option screen Table9.23 Explanation of Option screen Option IP address(*) Clock(*) MD function Reference Item Description section Utility communication task Set the processing priority for communication with the C Controller module.
Page 335: Operating System Settings Screen
UTILITY OPERATION 9.2.7 Operating System settings screen Set Parameter settings (System settings) of the C Controller module. Set the system-related parameters. POINT 1. In a multiple CPU system configuration, utilize the multiple CPU parameters set to the programmable controller CPU(s) or C Controller module(s). Utilizing the existing multiple CPU parameters prevents setting mismatches between the C Controller module and other CPUs.
Page 336 UTILITY OPERATION Table9.22 Explanation of System settings screen (Continued) System settings I/O assignment settings Multiple CPU settings Communication diagnostics Reference Item Description section Select the operation status for the output (Y) in the case where the C Controller module is switched from STOP to RUN, from "Previous state" Output mode at STOP to RUN or "Reset output (Y)".
Page 337 UTILITY OPERATION (2) Intelligent function module interrupt event settings screen Set the data for the interrupt events of the intelligent function module. Figure 9.42 Intelligent function module interrupt event settings screen Table9.25 Explanation of Intelligent function module interrupt event settings screen Reference Item Description...
Page 338 UTILITY OPERATION Table9.24 List of interrupt event No. and interrupt factors (Continued) Interrupt event No. Interrupt factor 11th point 12th point 13th point Interrupt by QI60 14th point 15th point 16th point 16 to 49 Not used Intelligent function module Using parameters, set which 50 to 255 interrupt...
Page 339: Operating I/O Assignment Settings Screen
UTILITY OPERATION 9.2.8 Operating I/O assignment settings screen Set Parameter settings (I/O assignment settings) of the C Controller module. Perform the I/O assignment for the slots and set the parameters related to the base unit where modules are installed. POINT 1.
Page 340 UTILITY OPERATION (1) I/O assignment settings screen Figure 9.43 I/O assignment settings screen Table9.27 Explanation of I/O assignment settings screen I/O assignment settings System settings Multiple CPU settings Communication diagnostics Reference Item Description section Displays the "Slot No." of the mounted module, the stage No. of the base Slot unit mounted with the module, and the installation position on the base 6.6.2...
Page 341 UTILITY OPERATION Table9.25 Explanation of I/O assignment settings screen (Continued) I/O assignment settings System settings Multiple CPU settings Communication diagnostics Reference Item Description section Power model Set the model name of the power supply module installed. Extension cable Set the model name of the extension cable. Specify the number of the slots of the base unit.
Page 342 UTILITY OPERATION (3) Intelligent function module detailed settings screen Make the detailed settings of the I/O modules and intelligent function modules. Figure 9.45 Intelligent function module detailed settings screen Table9.29 Explanation of Intelligent function module detailed settings screen Reference Item Description section Displays the "Slot", "Type", and "Model name"...
Page 343: Operating Multiple Cpu Settings Screen
UTILITY OPERATION 9.2.9 Operating Multiple CPU settings screen Set Parameter settings (Multiple CPU settings) of the C Controller module. Set the parameters related to the multiple CPUs. POINT 1. In a multiple CPU system configuration, utilize the multiple CPU parameters set to the programmable controller CPU(s) or C Controller module(s).
Page 344 UTILITY OPERATION Table9.30 Explanation of Multiple CPU settings screen Multiple CPU settings System settings I/O assignment settings Communication diagnostics Reference Item Description section Set the total number of programmable controller CPUs, C Controller Modules and Motion CPUs that comprise the multiple CPU system. 15.1.1 Number of CPUs (Initial value: 1, Setting range: 1 to 4)
Page 345: Operating Communication Diagnostics Screen
UTILITY OPERATION 9.2.10 Operating Communication diagnostics screen When the C Controller module is in a multiple CPU configuration, whether it can communicate with another CPU or not is diagnosed on this screen. This is not available for the Q06CCPU-V-B. POINT 1.
Page 346 UTILITY OPERATION Table9.31 Explanation of Communication diagnostics screen Communication diagnostics System settings I/O assignment settings Multiple CPU settings Reference Item Description section Select the CPU to be diagnosed. Target CPU (Initial value: "No. 1", Setting range: "No. 1" to "No. 4") Specify the number of times communication diagnostics will be Repeat count performed.
Page 347: Operating System Menu
UTILITY OPERATION 9.2.11 Operating system menu (1) System menu Open and use the system menu of the C Controller setting utility by any of the following three methods. • Right-click on the title bar. • Click the icon ( ) on the title bar. •...
Page 348 UTILITY OPERATION (2) Version information screen Displays the version information of the C Controller setting utility. Figure 9.51 Version information screen (Example: Version 3.01B) Table9.33 Explanation of Version information screen Reference Item Description section Software package Displays the version of SW PVC-CCPU. SW PVC-CCPU-E Version C Controller setting utility Displays the update date of the C Controller setting utility.
Page 349: Reading Initial Setting File And Importing Multiple Cpu Parameters
UTILITY OPERATION 9.2.12 Reading initial setting file and importing multiple CPU parameters (1) How to display the screen Perform any of the following operations to open the "Open project" screen. • Click the button of the <<System settings>> tab. Load initial setting file •...
Page 350: Cc-Link Utility
UTILITY OPERATION 9.3 CC-Link Utility This section explains the operation of the CC-Link utility. The following are the precautions for use of the CC-Link utility. (1) Parameter details Refer to the following manual for parameter details. CC-Link System Master/Local Module User's Manual (2) Maximum number of concurrently applicable CC-Link utilities Up to 8 CC-Link utilities can be activated and used at the same time.
Page 351: Cc-Link Utility Function List
UTILITY OPERATION 9.3.1 CC-Link utility function list This section explains the functions of the CC-Link utility. Table9.36 Function list of CC-Link utility Applicability Reference Q06CCPU- Q06CCPU- Name Description section Sets the C Controller module to which the CC-Link Connection settings 9.1.3 utility will be connected.
Page 352: Operating Module Information Screen
UTILITY OPERATION 9.3.2 Operating Module information screen The Module information screen displays various types of information of the CC-Link module (own station) that is controlled by the connected C Controller module. POINT 1. If a communication error has occurred during connection, click the button or set Connection settings again.
Page 353 UTILITY OPERATION Table9.37 Explanation of Module information screen Module information Other station monitoring Online operation Parameter settings Target settings Test Item Description Select the CC-Link module whose module information will be displayed. Target module (Initial value: "1-4 slot", Setting range: "1-4 slot", "5-8 slot") Slot n Displays various types of the CC-Link module information.
Page 354 UTILITY OPERATION (b) Details of data link status The following indicates the details of the Data link status. Table9.39 Details of Data link status Display Description In data link Data link is being executed. Suspended data link Data link is suspended. Initial status In initial status (before parameter update).
Page 355 UTILITY OPERATION (c) Details of error status The following indicates the details of the error status. Table9.40 Details of error status Display Description Normal Normal status. Transport error Transmission channel error was detected. Parameter error Parameter error was detected. CRC error CRC error was detected.
Page 356 UTILITY OPERATION Remark The information of the "Detailed module information" screen is based on the time when the "Detailed module information" screen is opened. To update the information, close and reopen the "Detailed module information" screen. - 65 9.3 CC-Link Utility 9.3.2 Operating Module information screen...
Page 357 UTILITY OPERATION (a) Details of Mode switch status The following indicates the details of the Mode switch status. Table9.42 Details of Mode switch status Transmission Display Mode speed 0: 156kbps (Online) 156kbps 1: 625kbps (Online) 625kbps 2: 2.5Mbps (Online) 2.5Mbps Online 3: 5Mbps (Online) 5Mbps...
Page 358 UTILITY OPERATION (3) Specifications of SB/SW save file An example of a SB/SW save file is given below. (a) Link special relays (SB) and link special registers (SW) data saved in CSV file SB/SW,192.168.3.3(Default)[CR][LF] QJ61BT11N ,071010000000000-B[CR][LF] Start I/O No.,Station No.,Station type[CR][LF] 0000,0,Master station[CR][LF] [CR][LF] SB/SW information[CR][LF]...
Page 359: Operating Other Station Monitoring Screen
UTILITY OPERATION 9.3.3 Operating Other station monitoring screen This screen displays the line status of the other stations (CC-Link network stations). POINT 1. When the CC-Link utility is started, monitoring is in a stop status. Click the button to start monitoring. Start monitoring 2.
Page 360 UTILITY OPERATION Table9.43 Explanation of Other station monitoring screen (Continued) Other station monitoring Module information Online operation Parameter settings Target settings Test Item Description Target module Station type Displays the station type. ( This section (1)(a)) Displays the number of occupied stations. (Display range: "Exclusive station 1" to Occupied number "Exclusive station 4") Status...
Page 361 UTILITY OPERATION (b) Status details The following indicates the details of the statuses. Table9.45 Status details Display Description Normal Normal Temporary error invalidity status Temporary error is treated as invalid. Data link error Link status is in error. WDT error Watchdog timer error occurred.
Page 362 UTILITY OPERATION (2) View all stations screen Displays the states of other stations. Figure 9.57 View all stations screen Table9.49 View all stations screen Item Description Displays the communication status of each station. ( This section (2)(a)) Status of each station Closes the "View all stations"...
Page 363: Operating Online Operation Screen
UTILITY OPERATION 9.3.4 Operating Online operation screen The CC-Link parameters can be read, written or verified from this screen. POINT 1. If a communication error has occurred during connection, set Communication settings again. 2. Communication are not available during reset of the C Controller module. Start communication after terminating the reset process.
Page 364 UTILITY OPERATION Table9.51 Explanation of Online operation screen Online operation Other station monitoring Module information Parameter settings Target settings Test Item Description Read parameters Reads the CC-Link parameters from the C Controller module. button Read Writes the set CC-Link parameters to the C Controller module. The written parameters become effective when the C Controller module is powered off and then on or is reset.
Page 365: Operating Parameter Settings Screen
UTILITY OPERATION 9.3.5 Operating Parameter settings screen This screen allows the parameter settings of the CC-Link module. POINT 1. If any entered parameter is erroneous when attempting to switch the screen to another, a warning message appears and the screen will not be switched. Switch the tab after correcting the erroneous parameter.
Page 366 UTILITY OPERATION Table9.52 Explanation of Parameter settings screen Parameter settings Module information Other station monitoring Online operation Target settings Test Item Description Set the number of CC-Link modules to be controlled by the C Controller module. Number of modules Selecting " (Blank)" is recognized as no setting (Setting clear). (Initial value: "...
Page 367 UTILITY OPERATION Table9.52 Explanation of Parameter settings screen (Continued) Parameter settings Other station monitoring Online operation Module information Target settings Test Item Description Operation settings Make the operational setting of the CC-Link module. Set the type of the CC-Link module. Type (Initial value: "Master station", Setting range: "Master station", "Local station") Set the mode of the CC-Link module.
Page 368 UTILITY OPERATION Table9.52 Explanation of Parameter settings screen (Continued) Parameter settings Other station monitoring Online operation Module information Target settings Test Item Description Station information settings Intelligent buffer select This setting is available only when "Intelligent device station", "Ver. 1 Intelligent device (word) station", or "Ver.2 Intelligent device station"...
Page 369 UTILITY OPERATION 3) Target module numbers are corrected when the tab is switched or when the parameter setting file is saved Target module Start I/O No. 00 20 Figure 9.62 Target module numbers are corrected (b) Initial value and setting range for each station type The initial value and setting range for each station type changes depending on the "Mode"...
Page 370 UTILITY OPERATION (2) Other settings screen Figure 9.63 Other settings screen Table9.54 Explanation of Other settings screen Item Description Set the number of retries in the case of a communication error (transient transmission error occurrence). Retry count (Initial value: 3, Setting range: 1 to 7) Set the number of modules that can be automatically reconnected in one link scan.
Page 371: Operating Target Settings Screen
UTILITY OPERATION 9.3.6 Operating Target settings screen Set the logical station No. for making access to any CPU module in a multiple CPU system where the CC-Link module is installed. For the Q06CCPU-V-B, the logical station No. is not available. POINT 1.
Page 372 UTILITY OPERATION Table9.55 Explanation of Target settings screen Target settings Parameter settings Other station monitoring Online operation Module information Test Item Description Select the module to be set. Target module (Initial value: "Slot 1", Setting range: "Slot 1" to "Slot 8") Specify the logical station No.
Page 373 UTILITY OPERATION (2) Access example Using the logical station No."65", access can be made from a CC-Link module controlled by the Q06CCPU-V to CPU No. 4 via another CC-Link module (controlled by CPU No. 2). From the Device monitoring utility or user program (MELSEC data link function), access can be made to CPU No.
Page 374 UTILITY OPERATION (3) Access that does not require the logical station No. setting For accessing to the following, use the station No. of the other station CC-Link module. There is no need to set the logical staiton No. Other station CC-Link module Control CPU of other station CC-Link module Figure 9.67 Access that does not require the logical staiton No.
Page 375: Operating Test Screen
UTILITY OPERATION 9.3.7 Operating Test screen The network test and line test of the installed CC-Link module can be conducted. POINT 1. Execute the network test and line test when the installed CC-Link module is online. When it is offline, the network test and line test are not executable. 2.
Page 376 UTILITY OPERATION Table9.56 Explanation of Test screen Test Module information Other station monitoring Online operation Parameter settings Target settings Item Description Select the module to be tested. Target module (Initial value: "1 Slot", Setting range: "1 Slot" to "8 Slot") Start I/O No.
Page 377 UTILITY OPERATION (2) Test operation procedures (a) Line test procedure The line test can be executed only when the data link status ( Section 9.3.2) of the CC-Link module is "In data link" or "Performing auto-return". 1) Setting Select the target station of the line test and click the button to start the line test.
Page 378 UTILITY OPERATION (b) Network test operation procedure The network test can be executed only when the data link status ( Section 9.3.2) of the CC-Link module is "In data link" or "Performing auto-return". 1) Setting Select whether to start or stop data link and click the button to start the network test.
Page 379: Operating System Menu
UTILITY OPERATION 9.3.8 Operating system menu (1) System menu Open and use the system menu of the CC-Link utility by any of the following three methods. • Right-click on the title bar. • Click the icon ( ) on the title bar. •...
Page 380: Melsecnet/H Utility
UTILITY OPERATION 9.4 MELSECNET/H Utility This section explains the operation of the MELSECNET/H utility. The following are the precautions for use of the MELSECNET/H utility. (1) Parameter details Refer to the following manual for parameter details. Q Corresponding MELSECNET/H Network System Reference Manual (PLC to PLC network) (2) Maximum number of concurrently applicable MELSECNET/H utilities Up to 8 MELSECNET/H utilities can be activated and used at the same time.
Page 381: Melsecnet/H Utility Function List
UTILITY OPERATION 9.4.1 MELSECNET/H utility function list This section explains the functions of the MELSECNET/H utility. Table9.59 Function list of MELSECNET/H utility Applicability Reference Q06CCPU- Q06CCPU- Name Description section Sets the C Controller module to which the Connection settings 9.1.3 MELSECNET/H utility will be connected.
Page 382: Operating Module Information Screen
UTILITY OPERATION 9.4.2 Operating Module information screen The Module information screen displays various types of information of the MELSECNET/ H module (own station) that is controlled by the connected C Controller module. POINT 1. If a communication error has occurred during connection, click the button or set Connection settings again.
Page 383 UTILITY OPERATION Table9.60 Explanation of Module information screen (Continued) Module information Error history monitoring Other station monitoring Correspon- Correspon- Item Description ding SB ding SW Displays various types of the MELSECNET/H module 1-4 Slot information in order of start I/O No. Start I/O No.
Page 384 UTILITY OPERATION (a) Communication status details The following indicates the communication status details. Table9.61 Communication status details Display Description In data link Data link is being performed. Cyclic transmission was stopped from the other Suspended data link (Other) station. Cyclic transmission was stopped by the own Suspended data link (Self) station.
Page 385 UTILITY OPERATION (2) Detailed module information screen This screen displays the detailed information of the MELSECNET/H module. Figure 9.77 Detailed module information screen Table9.62 Explanation of Detailed module information screen Correspon- Correspon- Item Description ding SB ding SW Model name Displays the model name of the MELSECNET/H module.
Page 386 UTILITY OPERATION Table9.62 Explanation of Detailed module information screen (Continued) Correspon- Correspon- Item Description ding SB ding SW Displays the own station information of the MELSECNET/H Own station information module. Displays the start I/O No. of the own station. Start I/O No. (Display range: 0000 to 0FE0) Displays the network No.
Page 387 UTILITY OPERATION Table9.62 Explanation of Detailed module information screen (Continued) Correspon- Correspon- Item Description ding SB ding SW Displays the control station information of the MELSECNET/H Control station information network system. Displays the specified control station in the MELSECNET/H Assign control station network system.
Page 388 UTILITY OPERATION Table9.62 Explanation of Detailed module information screen (Continued) Correspon- Correspon- Item Description ding SB ding SW Data link information Displays the data link status of MELSECNET/H. Total number of link Displays the total number of linked stations on MELSECNET/ SW0059 stations Station of maximum...
Page 389 UTILITY OPERATION (a) Details of Reason for transmission interruption The following lists the Reason for transmission interruption. Table9.63 Details of Reason for transmission interruption Display Description/Action Normal Communicating normally Offline Offline Offline test Offline test being conducted. Initial status Error occurred. (Error code: F101, F102, F105) Shift control station Error occurred.
Page 390 UTILITY OPERATION (3) SB/SW save file specifications An example of a SB/SW save file is given below. (a) Link special relays (SB) and link special registers (SW) data saved in CSV file SB/SW,192.168.3.33 (Default)[CR][LF] QJ71LP21-25 ,060120000000000-D [CR][LF] Start I/O No., Network No., Group No., Station No., Network, Type [CR][LF] 0000,1,0,1,MELSECNET/H Extended(Loop),Net control station, PLC-PLC [CR][LF] [CR][LF] SB/SW information [CR][LF]...
Page 391: Operating Error History Monitoring Screen
UTILITY OPERATION 9.4.3 Operating Error history monitoring screen This screen displays the historical data of loop errors, communication errors, and transient transmission errors. POINT 1. Up to 16 loop switching or transient transmission errors are stored as historical data. If the number of errors exceeds 16, the older ones are deleted in order. (No.1 (Oldest) to No.16 (Newest)) 2.
Page 392 UTILITY OPERATION Table9.65 Explanation of Error history monitoring screen (Continued) Error history monitoring Module information Other station monitoring Correspon- Correspon- Item Description ding SB ding SW Starts monitoring of the MELSECNET/H module. During monitoring, this button changes to , and Stop monitoring button Start monitoring...
Page 393 UTILITY OPERATION Table9.65 Explanation of Error history monitoring screen (Continued) Error history monitoring Module information Other station monitoring Correspon- Correspon- Item Description ding SB ding SW Displays the number of error occurrences. Refer to the following for details of each error factor and Number of error occurrences corrective actions.
Page 394 UTILITY OPERATION (2) Clear error history screen Clear the number of errors to 0. Figure 9.80 Clear error history screen Table9.66 Explanation of Clear error history screen Correspon- Correspon- Item Description ding SB ding SW Clear type Select the item whose number of errors is to be cleared to 0. Clears the number of retries (link special register SW00C8, Clear retry counter SW00C9) to 0.
Page 395 UTILITY OPERATION (3) Error factors and corrective actions The following indicates factors and corrective actions for each error. They can also be confirmed from the following link special registers (SW), as well as on the Error history monitoring screen. Refer to the following manual for details of the link special registers (SW). Q Corresponding MELSECNET/H Network System Reference Manual (PLC to PLC network) Table9.67 Error factors and corrective actions...
Page 396: Operating Other Station Monitoring Screen
UTILITY OPERATION 9.4.4 Operating Other station monitoring screen This screen displays the line status of the other stations (MELSECNET/H network stations). POINT 1. When the MELSECNET/H utility is started, monitoring is in a stop status. Click button to start monitoring. Start monitoring 2.
Page 397 UTILITY OPERATION Table9.68 Explanation of Other station monitoring screen (Continued) Other station monitoring Module information Error history monitoring Correspon- Correspon- Item Description ding SB ding SW Stops monitoring of the MELSECNET/H module. When monitoring is stopped, this button changes to button Stop monitoring Start monitoring...
Page 398 UTILITY OPERATION (2) Details screens Each of them displays the detailed information of the item selected on the "Other station monitoring" screen. Open any of the following details screens by making selection on the "Other station monitoring" screen. Table9.69 Selection on "Other station monitoring" and corresponding details screen "Other station monitoring"...
Page 399 UTILITY OPERATION (a) Communication status of each station screen Displays the baton pass status (availability of transient transmission). The number of displayed stations is equal to the "Total stations" set on the "Parameter settings" screen. Figure 9.82 Communication status of each station screen Table9.70 Explanation of Communication status of each station screen Correspon- Correspon-...
Page 400 UTILITY OPERATION (b) Data link status of each station screen Displays the cyclic transmission status. The number of displayed stations is equal to the "Total stations" set on the "Parameter settings" screen. Figure 9.83 Data link status of each station screen Table9.71 Explanation of Data link status of each station screen Correspon- Correspon-...
Page 401 UTILITY OPERATION (c) Parameter status of each station screen Displays the parameter communication status and error status of each station. The number of displayed stations is equal to the "Total stations" set on the "Parameter settings" screen. Figure 9.84 Parameter status of each station screen Table9.72 Explanation of Parameter status of each station screen Correspon- Correspon-...
Page 402 UTILITY OPERATION (d) CPU operation status of each station screen Displays the CPU operation status. The number of displayed stations is equal to the "Total stations" set on the "Parameter settings" screen. Figure 9.85 CPU operation status of each station screen Table9.73 Explanation of CPU operation status of each station screen Correspon- Correspon-...
Page 403 UTILITY OPERATION (e) CPU RUN status of each station screen Displays the RUN/STOP states of the CPUs. The number of displayed stations is equal to the "Total stations" set on the "Parameter settings" screen. Figure 9.86 CPU RUN status of each station screen Table9.74 Explanation of CPU RUN status of each station screen Correspon- Correspon-...
Page 404 UTILITY OPERATION (f) Loop status of each station screen Displays the forward and reverse loop statuses in the case of the optical loop system. The number of displayed stations is equal to the "Total stations" set on the "Parameter settings" screen. Figure 9.87 Loop status of each station screen Table9.75 Explanation of Loop status of each station screen Correspon-...
Page 405 UTILITY OPERATION (g) Reserved station designation of each station screen Displays the reserved station setting status. The number of displayed stations is equal to the "Total stations" set on the "Parameter settings" screen. Figure 9.88 Reserved station designation of each station screen Table9.76 Explanation of Reserved station designation of each station screen Correspon- Correspon-...
Page 406 UTILITY OPERATION (h) PSU operation status of each station extension screen Displays the 24VDC external power supply status of the MELSECNET/H module. The number of displayed stations is equal to the "Total stations" set on the "Parameter settings" screen. Figure 9.89 PSU operation status of each station extension screen Table9.77 Explanation of PSU operation status of each station extension screen Correspon- Correspon-...
Page 407 UTILITY OPERATION (i) Each station network type status screen Displays whether or not the network type set for the control station is identical with that for the normal stations. The number of displayed stations is equal to the "Total stations" set on the "Parameter settings"...
Page 408: Operating Online Operation Screen
UTILITY OPERATION 9.4.5 Operating Online operation screen The MELSECNET/H parameters can be read, written or verified from this screen. POINT 1. If a communication error has occurred during connection, set Connection settings again. 2. Communications are not available during reset of the C Controller module. Start communications after terminating the reset process.
Page 409 UTILITY OPERATION Table9.79 Explanation of Online operation screen (Continued) Online operation Parameter settings Target settings Item Description Compares the MELSECNET/H parameters of the C Controller module with those of the Verify parameters MELSECNET/H utility. button Verify The result is displayed in the message box. Remark 1.
Page 410: Operating Parameter Settings Screen
UTILITY OPERATION 9.4.6 Operating Parameter settings screen This screen allows the parameter settings of the MELSECNET/H module. POINT 1. If any entered parameter is erroneous when attempting to switch the screen to another, a warning message appears and the screen will not be switched. Switch the tab after correcting the erroneous parameter.
Page 411 UTILITY OPERATION Table9.80 Explanation of Parameter settings screen Parameter settings Online operation Target settings Item Description Set the number of MELSECNET/H modules to be controlled by the C Controller module. Number of modules Selecting "(Blank)" is recognized as no setting (Setting clear). (Initial value: "(Blank)", Setting range: 1 to 4, "(Blank)") Set the refresh cycle of the link device.
Page 412 UTILITY OPERATION Table9.80 Explanation of Parameter settings screen (Continued) Parameter settings Online operation Target settings Item Description Operation settings Make the return setting of the control station. This setting is available when "MNET/H mode (Control station)", "MNET/10 mode (Control station)", or "MNET/H Ext. mode (Control station)" is selected for "Network Return type".
Page 413 UTILITY OPERATION (a) Network range assignment setting ranges The following indicates the setting ranges of network range assignment. Table9.81 Setting ranges of network range assignment Device name Points/Start/End Setting range Points 16 to 8192 Start 0000 to 1FF0 000F to 1FFF Points 16 to 8192 Start...
Page 414 UTILITY OPERATION (2) Routing parameter settings screen Set the transfer destination, relay network No., and relay station No. POINT 1. The MELSECNET module controlled by the C Controller module cannot be an intermediate station servicing as bridge. As an intermediate station, use the MELSECNET/H module controlled by a programmable controller CPU with which multiple network systems can be configured.
Page 415 Cancel * 1 Select 960 words only when the intermediate and target stations of transient transmission via another network (No.) are the MELSEC-Q series network modules. Select 480 words when the intermediate and target stations of transient transmission are other than the MELSEC-Q series network modules.
Page 416 UTILITY OPERATION (3) Refresh parameter settings screen Set the refresh parameters. Figure 9.95 Refresh parameter settings screen Table9.83 Explanation of Refresh parameter settings screen Item Description The device range input method can be switched between Points/Start and Start/End. Assignment method (Initial value: "Start/End") Set the refresh parameters of the target module selected on the "Parameter settings"...
Page 417 UTILITY OPERATION (a) Initial values of "Device name", "Points", "Start", and "End" The following indicates the initial values of "Device name", "Points", "Start", and "End". Table9.84 Initial values of "Device name", "Points", "Start", and "End" Setting item Device name Points Start Trans.1 8192...
Page 418 UTILITY OPERATION (4) Equal assignment screen The link device points of all stations can be equally assigned on this screen. The start and end station values show the number of the equal assignment stations and the setting must be within (Total link stations - (Start station No. - 1)). (a) When "LB/LW settings"...
Page 419 UTILITY OPERATION (b) When "LX/LY settings (1)" or "LX/LY settings (2)" is set for "Switch screens" on "Parameter settings" screen Figure 9.97 Equal assignment screen (for LX/LY settings (1)) Table9.88 Explanation of Equal assignment screen (for LX/LY settings (1)/(2)) Item Description Equally assigns the input points to the link devices of each station.
Page 420 UTILITY OPERATION (5) Supplementary settings screen The Supplementary settings is utilized for more detailed applications. Generally, use the initial setting. Figure 9.98 Supplementary settings screen Table9.89 Explanation of Supplementary settings screen Item Description Constant scan is a feature to keep the fixed link scan time. Constant scan Set a value when variation in the link scan time is not desired.
Page 421 UTILITY OPERATION Table9.89 Explanation of Supplementary settings screen (Continued) Item Description Transient settings Set the execution conditions for transient transmission. Set the number of transient transmissions (total on a whole network) that can be Max. number of transients executed by one network during 1 link scan. per scan (Initial value: 2, Setting range: 1 to 255) Set the number of transient transmissions that can be executed by one station during 1...
Page 422: Operating Target Settings Screen
UTILITY OPERATION 9.4.7 Operating Target settings screen The logical station No. for access to a multiple CPU system can be set on this screen. For the Q06CCPU-V-B, the logical station No. is not available. POINT 1. To update the settings into the C Controller module, write the parameters on the <<Online operation>>...
Page 423 UTILITY OPERATION Table9.91 Explanation of Target settings screen (Continued) Target settings Online operation Parameter settings Item Description Specify the logical station No. of the module selected in "Target module". Logical Sta. No. (Initial value: 65, Setting range: 65 to 239) Set the network No.
Page 424 UTILITY OPERATION (1) Access example Using the logical station No."65", access can be made from a MELSECNET/H module controlled by the Q06CCPU-V to CPU No.4 via another MELSECNET/H module (controlled by CPU No.2, network No.1). From the Device monitoring utility or user program (MELSEC data link function), access can be made to CPU No.4 by opening Channel No.51 and specifying station No.65.
Page 425 UTILITY OPERATION (2) Access that does not require the logical station No. setting For accessing to the following, use the station No. of the other station MELSECNET/H module. There is no need to set the logical staiton No. Control CPU of other station Other station MELSECNET/H module MELSECNET/H module Figure 9.102 Access that does not require the logical staiton No.
Page 426: Operating System Menu
UTILITY OPERATION 9.4.8 Operating system menu (1) System menu Open and use the system menu of the MELSECNET/H utility by any of the following three methods. • Right-click on the title bar. • Click the icon ( ) on the title bar. •...
Page 427: Cc Ie Control Utility
UTILITY OPERATION 9.5 CC IE Control utility This section explains the operation of the CC IE Control utility. For the Q06CCPU-V-B, the CC IE Control utility is not available. The following are the precautions for use of the CC IE Control utility. (1) Parameter details Refer to the following manual for parameter details.
Page 428: Cc Ie Control Utility Function List
UTILITY OPERATION 9.5.1 CC IE Control utility function list This section explains the functions of the CC IE Control utility. Table9.94 Function list of CC IE Control utility Reference Name Description section Sets the C Controller module to which the CC IE Control utility will be Connection settings 9.1.3 connected.
Page 429: Operating Module Information Screen
UTILITY OPERATION 9.5.2 Operating Module information screen The Module information screen displays various types of information of the CC-Link IE controller network module (own station) that is controlled by the connected C Controller module. POINT 1. If a communication error has occurred during connection, click the button or set Connection settings again.
Page 430 UTILITY OPERATION Table9.95 Explanation of Module information screen (Continued) Module information Target settings Online operation Parameter settings Correspon- Correspon- Item Description ding SB ding SW Displays various types of the CC-Link IE controller network 1-4 Slot module information in order of start I/O No. Displays the start I/O No.
Page 431 UTILITY OPERATION (2) SB/SW save file specifications An example of a SB/SW save file is given below. (a) Link special relays (SB) and link special registers (SW) data saved in CSV file SB/SW,192.168.3.3(Default)[CR][LF] QJ71GP21-SX ,090420000000000-B[CR][LF] Start I/O No., Network No., Group No., Station No., Network, Type[CR][LF] 0000, 1, 0, 1, CC-Link IE Controller Network, Control station[CR][LF] [CR][LF] SB/SW information[CR][LF]...
Page 432: Operating Diagnostics Result Screen
UTILITY OPERATION 9.5.3 Operating Diagnostics result screen A click on the button on the <<Module information>> tab screen will display Diagnostics this screen. Figure 9.107 CC IE Control Network diagnostics result screen POINT When there are two or more CC-Link IE controller network modules that are controlled by the C Controller module, the "Select diagnostics destination"...
Page 433 UTILITY OPERATION Table9.96 Explanation of Diagnostics result screen Item Description Displays the "Select diagnostics destination" screen when there are two or more CC- Link IE controller network modules that are controlled by the C Controller module. button Change module Change the network to the one that is to be diagnosed. Entering a station No.
Page 434 UTILITY OPERATION (1) Network information The link status and station status of the network are displayed. Figure 9.109 Network information screen Table9.97 Explanation of Network information screen Item Description Displays the module on the network, which is being diagnosed. Module The number corresponds to one of Slots 1 to 4 on the "Module information"...
Page 435 UTILITY OPERATION (a) Icon The icons represent each station status and inter-station status. Figure 9.110 Station status and inter station status representation 1) Station No. A station No. of a CC-Link IE controller network module is displayed. 2) Connected This is displayed for the station connected to the CC IE Control utility. 3) Icon The meanings of the icons are listed below.
Page 436 UTILITY OPERATION (b) Display position of disconnected station 1) When normal connection information has been obtained The disconnected station is displayed in the position where it was connected when operated normally. Figure 9.111 When normal connection information has been obtained Conditions and timing for normal connection information acquisition When all of the following conditions are met, the normal connection information is stored in the CC-Link IE controller network module.
Page 437 UTILITY OPERATION 2) When normal connection information has not been obtained The disconnected station is displayed on the IN side of the CC IE Control utility connected station. Figure 9.112 When normal connection information has not been obtained 9.5 CC IE Control utility - 146 9.5.3 Operating Diagnostics result screen...
Page 438 UTILITY OPERATION (2) Network device status of selected station Displays the detailed information on the selected station. Figure 9.113 Network device status of selected station Table9.99 Explanation of Network device status of selected station Item Display Description Displays the group No. of the selected station. Group No.
Page 439 UTILITY OPERATION (a) Select station network device status LED display Displays the operating status of the selected station. Figure 9.114 Select station network device status LED display Table9.100 Explanation of Select station network device status LED display Name LED status Description ON,green Operating normally...
Page 440 UTILITY OPERATION (b) Error details button Clicking this button will display the "Error details" screen. It shows the detailed information, error factor, and troubleshooting tips. Figure 9.115 Error details screen - 149 9.5 CC IE Control utility 9.5.3 Operating Diagnostics result screen...
Page 441 UTILITY OPERATION (3) Communication Test screen The route from the own station to the specified destination is shown, and whether transient transmissions can be performed correctly or not is checked. Upon completion of the test, the test result is displayed. If an error occurs, take actions according to the error message.
Page 442 UTILITY OPERATION Table9.101 Explanation of Communication Test screen (Continued) Item Description Own station Displays the information on the own (connected) station. Displays the network No. of the own (connected) station. Network No. (Display range: 1 to 239) Displays the station No. of the own (connected) station. Station No.
Page 443 UTILITY OPERATION (4) Link start/stop screen From this screen, data link of the specified station can be started or stopped. Figure 9.118 Link start/stop screen Table9.102 Explanation of Link start/stop screen Item Description Network information Displays the information of the selected network (own station). Displays the name of the selected network (own station).
Page 444 UTILITY OPERATION Table9.102 Explanation of Link start/stop screen (Continued) Item Description Displays the information of the stations connected to the selected network (own station). Status of all stations Displayed the status as the link start/stop setting target. Selected/non-selected (Display range: "Selected", "Non-selected") Displays the station No.
Page 445 UTILITY OPERATION (5) Logging screen Transmission path switch and transient transmission error logs of the connected station can be monitored. Also, error information can be cleared. <<Monitoring details>> tab <<Clear error>> tab Figure 9.119 Logging screen Table9.103 Explanation of Logging screen Item Description Connected station...
Page 446 UTILITY OPERATION Table9.103 Explanation of Logging screen (Continued) Item Description <<Monitoring details>> tab Displays logs in Transmission path switch and Transient transmission error. Displays transmission path switch logs. Transmission path switch Displays the information on the transmission paths on the entire network. Loop status (Display item: "Normal", "Loopback", "Error in all stations") Displays the station No.
Page 447 UTILITY OPERATION Table9.103 Explanation of Logging screen (Continued) Item Description <<Clear error>> tab Clears the errors. Clear communication error Select whether or not to clear the communication error counter. counter (Initial value: Checked, Setting range: "Check", "Uncheck") Clear IN side transmission error Select whether or not to clear the IN-side transmission error counter.
Page 448 UTILITY OPERATION (6) Error log file A click on the button on the <<Monitoring details>> tab on the Save error log "Logging" screen will output a CSV file under the folder specified as shown below.( This section (5)) (a) For Transmission path switch An error log file for Transmission path switch saves the following data: •...
Page 449: Operating Online Operation Screen
UTILITY OPERATION 9.5.4 Operating Online operation screen The CC-Link IE controller network parameters can be read, written or verified from this screen. POINT 1. If a communication error has occurred during connection, set Connection settings again. 2. Communications are not available during reset of the C Controller module. Start communications after terminating the reset process.
Page 450 UTILITY OPERATION Table9.104 Explanation of Online operation screen (Continued) Online operation Parameter settings Target settings Module information Item Description Compares the CC-Link IE controller network parameters of the C Controller module with those of the CC IE Control utility. Verify parameters The verification results are shown in a message box.
Page 451 UTILITY OPERATION (2) Verification results file saving If a mismatch is found, a message appears and prompts the user to save the results to a file. To save a verification results file, click the button and save it on the following screen.
Page 452: Operating Parameter Settings Screen
UTILITY OPERATION 9.5.5 Operating Parameter settings screen This screen allows the parameter settings of the CC-Link IE controller network module. POINT 1. If any entered parameter is erroneous when attempting to switch the screen to another, a warning message appears and the screen will not be switched. Switch the tab after correcting the erroneous parameter.
Page 453 UTILITY OPERATION Table9.105 Explanation of Parameter settings screen Parameter settings Module information Online operation Target settings Item Description Set the number of CC-Link IE controller network modules to be controlled by the C Controller module. Number of modules Selecting "(Blank)" is recognized as no setting (Setting clear). (Initial value: "(Blank)", Setting range: 1 to 4, "(Blank)") Set the refresh cycle of the link device.
Page 454 UTILITY OPERATION Table9.105 Explanation of Parameter settings screen (Continued) Parameter settings Module information Online operation Target settings Item Description Operation settings Specify the CC-Link IE controller network module operation. Set the type of the CC-Link IE controller network module. Network type (Initial value: "CC IE Control (Control station)", Setting range: "CC IE Control (Control station)", "CC IE Control (Normal station)") Set the mode of the CC-Link IE controller network module.
Page 455 UTILITY OPERATION (2) Routing parameter settings screen Set the transfer destination, relay network No., and relay station No. POINT 1. The MELSECNET module controlled by the C Controller module cannot be an intermediate station servicing as bridge. As an intermediate station, use the CC-Link IE controller network module controlled by a programmable controller CPU with which multiple network systems can be configured.
Page 456 Cancel * 1 Select 960 words only when the intermediate and target stations of transient transmission via another network (No.) are the MELSEC-Q series network modules. Select 480 words when the intermediate and target stations of transient transmission are other than the MELSEC-Q series network modules.
Page 457 UTILITY OPERATION (3) Refresh parameter settings screen Set the refresh parameters. Figure 9.125 Refresh parameter settings screen Table9.107 Explanation of Refresh parameter settings screen Item Description The device range input method can be switched between Points/Start and Start/End. Assignment method (Initial value: "Start/End") Set the refresh parameters of the target module selected on the "Parameter settings"...
Page 458 UTILITY OPERATION (a) Initial values of "Device name", "Points", "Start", and "End" The following indicates the initial values of "Device name", "Points", "Start", and "End". Table9.108 Initial values of "Device name", "Points", "Start", and "End" Setting item Device name Points Start Trans.1 32768...
Page 459 UTILITY OPERATION (4) Network range assignment screen For each station, set cyclic transmission ranges of LB, LW, LX and LY. Figure 9.126 Network range assignment screen Table9.111 Explanation of Network range assignment screen Item Description Set the total stations (including the control station) on the target network. Total stations (Initial value: 2, Setting range: 2 to 120) The device range input method can be switched between Points/Start and Start/End.
Page 460 UTILITY OPERATION Table9.111 Explanation of Network range assignment screen (Continued) Item Description button Displays the “Equal assignment” screen.( This section (5)) Equal assignment button Displays the “Supplementary settings” screen.( This section (6)) Supplementary settings Erases the "Points", "Start", and "End" settings and sets the initial values to "Total button Clear stations"...
Page 461 UTILITY OPERATION (5) Equal assignment screen The link device points of all stations can be equally assigned on this screen. The start and end station values show the number of the equal assignment stations and the setting must be within (Total link stations - (Start station No. - 1)). (a) When "LB/LW settings (1)"...
Page 462 UTILITY OPERATION (b) When "LX/LY settings (1)" or "LX/LY settings (2)" is set for "Switch screens" on "Network range assignment" screen Figure 9.128 Equal assignment screen (for LX/LY settings (1)) Table9.114 Explanation of Equal assignment screen (for LX/LY settings (1)/(2)) Item Description Equally assigns the input points to the link devices of each station.
Page 463 UTILITY OPERATION (6) Supplementary settings screen The Supplementary settings is utilized for more detailed applications. Generally, use the initial setting. Figure 9.129 Supplementary settings screen Table9.115 Explanation of Supplementary settings screen Item Description Constant scan is a feature to keep the fixed link scan time. Constant scan Set a value when variation in the link scan time is not desired.
Page 464 UTILITY OPERATION (a) Link scan operation by Constant scan time assurance setting Table9.116 Link scan operation by Constant scan time assurance setting Constant scan time assurance Link scan operation • Link scan time is kept constant. • Longer link scan time compared with the case of "disabled" setting. Enabled •...
Page 465: Operating Target Settings Screen
UTILITY OPERATION 9.5.6 Operating Target settings screen The logical station No. for access to a multiple CPU system can be set on this screen. POINT 1. To update the settings into the C Controller module, write the parameters on the <<Online operation>> tab and turn on and then off or reset the C Controller system.
Page 466 UTILITY OPERATION Table9.117 Explanation of Target settings screen (Continued) Target settings Module information Online operation Parameter settings Item Description Displays a list of the Logical station No. set to the module selected in "Target module" Target list and the corresponding network No., station No. and target CPUs. Displays the data in the row (Logical station No.) selected in the Target list in the Logical station No.
Page 467 UTILITY OPERATION (1) Access example Using the logical station No."65", access can be made from a CC-Link IE controller network module controlled by the C Controller module to CPU No.4 via another CC- Link IE controller network module (controlled by CPU No.2, network No.1). From the Device monitoring utility or user program (MELSEC data link function), access can be made to CPU No.4 by opening Channel No.151 and specifying station No.65.
Page 468 UTILITY OPERATION (2) Access that does not require the logical station No. setting For accessing to the following, use the station No. of the other station CC-Link IE controller network module. There is no need to set the logical staiton No. Control CPU of other station Other station CC-Link IE controller network module CC-Link IE controller network module...
Page 469: Operating System Menu
UTILITY OPERATION 9.5.7 Operating system menu (1) System menu Open and use the system menu of the CC IE Control utility by any of the following three methods. • Right-click on the title bar. • Click the icon ( ) on the title bar. •...
Page 470: Device Monitoring Utility
UTILITY OPERATION 9.6 Device Monitoring Utility This section explains the operations of the Device monitoring utility. For the Q06CCPU-V-B, the Device monitoring utility is not available. The following are the precautions for use of the Device monitoring utility. (1) While script file processing is being executed (the RUN LED is flashing), access may not be made from each utility to the C Controller module.
Page 471: Setting Batch Monitoring
UTILITY OPERATION 9.6.2 Setting batch monitoring Only one specified device can be monitored. POINT (1) If a communication error has occurred during connection, set Device settings, Connection settings or Network settings again. (2) When monitoring is performed to the CC-Link module (specified as own station) where data consistency verification per station function is set to be enabled, the cyclic data are automatically refreshed.
Page 472 UTILITY OPERATION (1) Menu item to be selected Select [Menu] [Batch monitoring] from the menu bar. (Selectable only when 16-point register monitoring is active. Batch monitoring is displayed immediately after startup of the Device monitoring utility.) After choosing [Setting] [Device settings] from the menu bar, set the device to be monitored.
Page 473: Setting 16-Point Register Monitoring
UTILITY OPERATION 9.6.3 Setting 16-point register monitoring Up to five bit devices and one word device can be monitored at the same time. POINT (1) If a communication error has occurred during connection, set Device settings, Connection settings or Network settings again. (2) When monitoring is performed to the CC-Link module (specified as own station) where data consistency verification per station function is set to be enabled, the cyclic data are automatically refreshed.
Page 474 UTILITY OPERATION (1) Menu item to be selected Select [Menu] [16-point register monitoring] from the menu bar. (Selectable only when batch monitoring is active.) After choosing [Setting] [Device settings] from the menu bar, set the device to be monitored. ( Section 9.6.5) (2) Display screen Figure 9.137 16-point register monitoring...
Page 475: Setting Monitoring Target
UTILITY OPERATION 9.6.4 Setting monitoring target Set the network for which the Device monitoring utility is used. Make the settings at startup of the Device monitoring utility. POINT When the own station is selected in the Network Settings, network No."0" and station No."255"...
Page 476: Setting Device To Be Monitored
UTILITY OPERATION 9.6.5 Setting device to be monitored Set the device to be monitored. POINT The devices that can be monitored by 16-point register monitoring are only randomly accessible devices. If the specified device does not allow random access, a device type error (-3) will occur.
Page 477: Changing Word Device Values
UTILITY OPERATION 9.6.6 Changing word device values The specified word device data can be changed. Danger When controlling (data change) a running C Controller module connected to a development environment (personal computer), configure an interlock circuit in the user program so that the whole system will function safely all the time.
Page 478 UTILITY OPERATION (1) Menu item to be selected Select [Write device] [Data change] from the menu bar. (2) Dialog box Figure 9.140 Data change dialog box Table9.125 Explanation of Data change dialog box Item Description Set the type, block No., and network No. of the device whose data will Device type be changed.
Page 479: Changing Word Device Values Continuously
UTILITY OPERATION 9.6.7 Changing word device values continuously The specified word device data for the set points can be changed to the specified data. Danger When controlling (data change) a running C Controller module connected to a development environment (personal computer), configure an interlock circuit in the user program so that the whole system will function safely all the time.
Page 480 UTILITY OPERATION (1) Menu item to be selected Select [Write device] [Continuous data change] from the menu bar. (2) Dialog box Figure 9.141 Continuous data change dialog box Table9.126 Explanation of Continuous data change dialog box Item Description Set the type, block No., and network No. of the device whose data will Device type be changed.
Page 481: Turning On/Off Bit Device
UTILITY OPERATION 9.6.8 Turning on/off bit device The specified bit device can be turned ON/OFF. Danger When controlling (data change) a running C Controller module connected to a development environment (personal computer), configure an interlock circuit in the user program so that the whole system will function safely all the time.
Page 482 UTILITY OPERATION (1) Menu item to be selected Select [Write device] [Set (Reset) bit device] from the menu bar. (2) Dialog box Figure 9.142 Set bit device dialog box Table9.127 Explanation of Set bit device dialog box Item Description Set the type, block No., and network No. of the device to be turned Device type ON/OFF.
Page 483: Switching The Display Format
UTILITY OPERATION 9.6.9 Switching the display format The data format preset for the device monitoring can be changed to the selected format. The menu options are different between Batch monitoring and 16-point register monitoring. (1) Menu item to be selected Select [Data Format] [Word (Bit) device] from the menu bar.
Page 484: Operating Start/Stop Of Monitoring
UTILITY OPERATION 9.6.10 Operating start/stop of monitoring Operate the button of Device monitoring utility. Start monitoring Stop monitoring button can be operated after completing the Device Start monitoring Stop monitoring settings. (1) Operation Start or stop monitoring with the button in the monitoring display. Stop monitoring (2) Display screen Figure 9.144 Start/stop monitoring operation screen...
Page 485: Numerical Pad
UTILITY OPERATION 9.6.11 Numerical pad By selecting [Option] [Numerical pad] from the menu bar, the numerical pad can be used to set values such as device values. 1) Click the space for numerical entry. 2) As the Numerical pad appears, enter a numerical value using the buttons.
Page 486: Other Operations
UTILITY OPERATION 9.6.12 Other operations By double-clicking the device No. on the screen during monitoring, word device data can be changed or bit devices can be turned ON/OFF. (1) Word device The following explains how to change a word device. (Only in 16-bit display format) Danger When controlling (data change) a running C Controller module...
Page 487 UTILITY OPERATION (2) Bit device The following explains how to turn a bit device ON/OFF. Note that this operation can be performed only when the display format is "Vertical". Danger When controlling (data change) a running C Controller module connected to a development environment (personal computer), configure an interlock circuit in the user program so that the whole system will function safely all the time.
Page 488: Chapter10 Functions And Programming
FUNCTIONS AND PROGRAMMING CHAPTER10 FUNCTIONS AND PROGRAMMING This chapter explains the bus interface functions and MELSEC data link functions supplied by SW PVC-CCPU. The Q06CCPU-V-B does not support the MELSEC data link functions. When utilizing the program examples introduced in this chapter for an actual system, be sure to verify that no problem will arise in the target system control.
Page 489 FUNCTIONS AND PROGRAMMING The system illustration below represents the descriptions on the previous page. Intelligent function module CC-Link module CC-Link IE controller network module or I/O module MELSECNET/H module C Controller module Programmable Motion CPU controller CPU 2 Programmable Programmable controller CPU controller CPU 1 6) to 12)
Page 490 FUNCTIONS AND PROGRAMMING Table10.1 Access targets of bus interface functions by applications Access from C Application Setting of Device Arrow Access target Controller setting Remarks given above monitoring utility utility Input (X) : Monitoring enabled Input module/output module Accessible Not available Output (Y) : Monitoring and forced output enabled...
Page 491 FUNCTIONS AND PROGRAMMING (2) The following indicates the applications of the MELSEC data link functions. 1) Access to a programmable controller CPU within the same system to which the C Controller module belongs. 2) Access to another station programmable controller CPU via a CC-Link module controlled by the C Controller module.
Page 492 FUNCTIONS AND PROGRAMMING Table10.2 Access targets of MELSEC data link functions by applications Setting of Access from Communication Device monitoring utility Arrow Access target Application C Controller Remarks path setting utility Channel name Station Programmable 12: Q series bus Other Q series bus Not accessible controller CPU...
Page 493: Programming Using Bus Interface Functions
FUNCTIONS AND PROGRAMMING 10.2 Programming Using Bus Interface Functions This section explains the bus interface functions included with SW PVC-CCPU. 10.2.1 Bus interface function list The following lists the bus interface functions. Table10.3 Bus interface function list Category Function name Function Opens a bus.
Page 494 FUNCTIONS AND PROGRAMMING Table10.3 Bus interface function list (Continued) Category Function name Function Resets the bus master CPU (CPU No.1). QBF_Reset CPU operating status QBF_Control Controls remote operations (RUN/STOP/PAUSE) for C Controller module. control Remotely controls RUN/STOP/PAUSE of the specified C Controller module or QBF_ControlEx programmable controller CPU.
Page 495: Programming Procedures
FUNCTIONS AND PROGRAMMING 10.2.2 Programming procedures This section provides programming procedures using the bus interface functions and MELSEC data link functions. Start Set the C Controller module. Chapter 5 Install Tornado into the development environment Tornado manual (personal computer). Make sure that the VxWorks image files in the system memories of the development environment (personal Section 10.2.6 (1) computer) and C Controller module match.
Page 496: Creating And Compiling New Project Of User Program
FUNCTIONS AND PROGRAMMING 10.2.3 Creating and compiling new project of user program This section explains: • How to create a new project ( This section (1)) • Compiling method ( This section (2)) • How to check the endian format (memory layout) of the execution file ( This section (3)) (1) How to create a new project...
Page 497 FUNCTIONS AND PROGRAMMING (From previous page) 4) Select "A toolchain", choose either of the following from the pull-down menu, and click the button. Next> Q06CCPU-V: SH7750gnule (Little endian) Q06CCPU-V-B: SH7750gnu (Big endian) REFERENCE This setting determines the endian format. If a different endian setting is selected, the program does not run.
Page 498 FUNCTIONS AND PROGRAMMING (From previous page) 7) Double-click the icon ( ) to display the lower item. 8) Right-click "SH7750gnule" and select [Properties] from the menu. REFERENCE For the Q06CCPU-V-B, right-click "SH7750gnu" and select [Properties] from the menu. (To next page) - 11 10.2 Programming Using Bus Interface Functions 10.2.3 Creating and compiling new project of user program...
Page 499 FUNCTIONS AND PROGRAMMING (From previous page) 9) Open the <<C/C++compiler>> tab. To the text area at screen center, add the directory setting to which the bus interface function and MELSEC communication function header files have been installed, and click the button.
Page 500 FUNCTIONS AND PROGRAMMING (2) Compiling method Compile the source file by the following method. POINT When compiling, be sure to perform the following operation. 1) On the <<Files>> tab of the "Workspace" window, right-click on the source file name to be complied, and select [Dependencies] from the menu.
Page 501 FUNCTIONS AND PROGRAMMING (From previous page) 4) A compiling process appears on the screen as shown on the left. 5) When the compile is finished, the execution file (user program) to be used by the C Controller module is generated. The user program is not generated if an error has occurred during compile.
Page 502: Programming Using Bus Interface Functions
FUNCTIONS AND PROGRAMMING 10.2.4 Programming using bus interface functions Using the bus interface functions, perform programming in the following procedure. (1) Programming outline The procedure for creating a user program using the bus interface functions is shown below. Task start Open the bus.
Page 503 FUNCTIONS AND PROGRAMMING (2) Precautions for using the bus interface functions (a) Programming precautions 1) Open/close processing Perform the bus open/close (QBF_Open function/QBF_Close function) processing only once at the beginning and end of the program. Communication performance will decrease if open/close is repeated at each communication.
Page 504 FUNCTIONS AND PROGRAMMING (c) Precautions for host station device access via MELSECNET/H module When making access via a MELSECNET/H module, provide interlocks in the user program to enable writing to or reading from the host station devices. Data becomes valid only when the following conditions are satisfied. •...
Page 505: Restrictions On Functions
FUNCTIONS AND PROGRAMMING 10.2.5 Restrictions on functions There are the following restrictions on the bus interface functions and MELSEC data link functions. (1) Endian format (Memory layout) There are C Controller module models for two different endian formats (memory layout): little endian model and big endian model. Create your user program using either little or big endian format that is appropriate to the model being used.
Page 506 FUNCTIONS AND PROGRAMMING (7) Clock setting If the year exceeds 2100 after the clock setting of the C Controller module, the C Controller module can be used with the clock data of 2100 or later until it is restarted. When the C Controller module is restarted, the year will be re-set to 2000 - 2099. (8) When operation status is changed from RUN to STOP/PAUSE When the operation status of the C Controller module changes from RUN to STOP/ PAUSE, the user program task does not stop.
Page 507 FUNCTIONS AND PROGRAMMING (14)Power off/reset operation during user file writing If the C Controller system is powered off or reset (remote RESET included) during write to the user file in the standard ROM or CompactFlash card, data corruption or file system error may occur. While data are being written to the user file in the standard ROM or CompactFlash card, execute the following operation and then power off or reset the system.
Page 508: Precautions For Program Debugging
FUNCTIONS AND PROGRAMMING 10.2.6 Precautions for program debugging (1) VxWorks image file specification To debug the user program, the same image file as that of VxWorks installed in the C Controller module must be specified for Tornado. (a) Specifying method 1) Make sure that the VxWorks image file in the system memory of the development environment (personal computer) is matched with that of C Controller module.
Page 509 FUNCTIONS AND PROGRAMMING (b) VxWorks image file 1) VxWorks image file storage location When SW PVC-CCPU has been installed, the VxWorks image file corresponding to one of the following models is stored. Table10.5 VxWorks image file storage location Model File Q06CCPU-V C:\Melsec\CCPU\Vx\Tools\Q06CCPU-V_XXXXX-Y Q06CCPU-V-B...
Page 510 FUNCTIONS AND PROGRAMMING (2) IP address setting of C Controller module The IP address of the C Controller module must be specified for Tornado to debug the user program by connecting the development environment (personal computer) and C Controller module via Ethernet. 1) Start Tornado.
Page 511 FUNCTIONS AND PROGRAMMING (3) Symbol information synchronization setting To debug the user program, the symbol information of the C Controller module and that of the development environment (personal computer) must be synchronized. 1) Start Tornado. 2) Choose [Tools] [Target Server] [Configure] from the menu bar to open the "Configure Target Severs"...
Page 512 FUNCTIONS AND PROGRAMMING (4) Shell display setting The following setting must be made to display output information (such as printf) from each task of the C Controller module on Shell. When the following setting is not made, only the output information on the Shell task is displayed.
Page 513 FUNCTIONS AND PROGRAMMING (5) Precautions for executing Shell command from Tornado Shell or Telnet tool 1) TWhen executing Shell command from Tornado Shell When executing the Shell command from Tornado Shell, the entered Shell command operates on the task of Priority 1 in the C Controller module. Care should be taken since a system error/stop (such as a system watchdog timer error) may occur in the C Controller module depending on the entered command (example: command that occupies CPU processing).
Page 514: Program Registration
FUNCTIONS AND PROGRAMMING 10.2.7 Program registration Each file is registered to a C Controller module by writing the file to the standard ROM of the C Controller module or a CompactFlash card. Table10.6 How to write to each drive Program storage location CompactFlash Writing method Standard...
Page 515 FUNCTIONS AND PROGRAMMING (c) Precautions for program registration via FTP 1) Login user setting The C Controller module supports the basic authentication (account setting) by use of the user name and password, but it restricts users and C Controller module setting operation and does not completely prevent illegal access from the outside.
Page 516 FUNCTIONS AND PROGRAMMING (d) Registration procedure via FTP The following indicates the registration procedure via FTP. 1) Start Internet Explorer, and enter the C Controller module address into the Address bar in the following format. ftp://<User name>:<Password>@<IP address of C Controller module><Drive name>...
Page 517 FUNCTIONS AND PROGRAMMING (2) Copy registration from CompactFlash card to standard ROM (for the Q06CCPU-V only) The following explains copy registration of the files in the CompactFlash card to the standard ROM of the C Controller module. This operation ensures easy registration of the same user program to multiple C Controller modules.
Page 518: Creating Script File "Startup.cmd
FUNCTIONS AND PROGRAMMING 10.2.8 Creating script file "STARTUP.CMD" (1) Definition of script file The script file "STARTUP.CMD" is the one used to describe the loading location, startup order, parameter setting values, etc. of the user program that will start when the C Controller module is booted up.
Page 519 FUNCTIONS AND PROGRAMMING Remark 1. Depending on the description of the script file, the following operation can be performed from the CompactFlash card to the standard ROM. • Copy registration of program to standard ROM ( Section 10.2.7) • Standard ROM formatting ( Section 5.10) 2.
Page 520 FUNCTIONS AND PROGRAMMING (4) Example of script file description The following provides an example of describing the script file to start user programs. (a) When loading user programs from script file in standard ROM The following gives an example of loading user programs ("fileA.out", "fileB.out") in the standard ROM from the script file in the standard ROM.
Page 521 FUNCTIONS AND PROGRAMMING (b) When loading user programs from script file on CompactFlash card (for the Q06CCPU-V only) The following gives an example of loading user programs ("fileA.out", "fileB.out") in the standard ROM and CompactFlash card from the script file in the CompactFlash card.
Page 522: Device Types For Bus Interface Functions
FUNCTIONS AND PROGRAMMING 10.2.9 Device types for bus interface functions The device types used for the bus interface functions may be either the code numbers or device names indicated in this section. (1) Motion CPU dedicated device types The motion CPU dedicated device types can be specified in the argument sDevType of the QBF_MotionDDWR or QBF_MotionDDRD function.
Page 523 FUNCTIONS AND PROGRAMMING (2) Device types for accessing CC-Link IE controller network modules or MELSECNET/H modules Specify the device type for accessing a CC Link IE controller network module or MELSECNET/H module with the argument, sDevType of the QBF_WriteLinkDevice or QBF_ReadLinkDevice function.
Page 524 FUNCTIONS AND PROGRAMMING POINT 1. Use the internal link device buffers (LX buffer, LY buffer, LB buffer, LW buffer) by setting the following items and making them refresh with link devices (LX, LY, LB, LW). Table10.13 Setting link device refresh cycle and ranges Network Item Reference section...
Page 525: Programming Using Melsec Data Link Functions
FUNCTIONS AND PROGRAMMING 10.3 Programming Using MELSEC Data Link Functions This section explains the MELSEC data link functions contained in SW PVC-CCPU. The Q06CCPU-V-B does not support the MELSEC data link functions. 10.3.1 MELSEC data link function list The following lists the MELSEC data link functions. Table10.14 MELSEC data link function list Category Function name...
Page 526: Programming Using Melsec Data Link Functions
FUNCTIONS AND PROGRAMMING 10.3.4 Programming using MELSEC data link functions This section shows a programming procedure using the MELSEC data link functions. (1) Programming procedure The following shows the outline of user program creation using the MELSEC data link functions. Task start Opens a communication line.
Page 527 FUNCTIONS AND PROGRAMMING (2) Precautions for using MELSEC data link functions (a) Precautions for programming 1) Opening/closing communication lines Open and close a communication line (mdOpen and mdClose functions) only once at the start (task start) and end (task end) of each user program task. Communication performance will be affected if open/close is repeated at each communication.
Page 528 FUNCTIONS AND PROGRAMMING (b) Precautions for access to CC-Link module's own station devices and other station programmable controller devices When making access via a CC-Link module, provide interlocks depending on the link status of the own station and other station. 1) Access to own station device Create a user program that will provide interlocks to validate data writing to or data reading from the own station device.
Page 529 FUNCTIONS AND PROGRAMMING (d) Precautions for access to CC-Link IE controller network module's own station devices and other station programmable controller devices When making access via a CC-Link IE controller network module, provide interlocks depending on the link status of the own station. 1) Access to own station devices Create a user program that has interlocks for enabling data writing to or data reading from the own station devices.
Page 530: Restrictions On Melsec Data Link Functions
FUNCTIONS AND PROGRAMMING 10.3.5 Restrictions on MELSEC data link functions Refer to Section 10.2.5 for details of the restrictions on the MELSEC data link functions. 10.3.6 Precautions for program debugging Refer to Section 10.2.6 for details of the program debugging precautions. 10.3.7 Program registration Refer to Section 10.2.7 for details of program registration.
Page 531: Station No. Setting For Melsec Data Link Functions
FUNCTIONS AND PROGRAMMING 10.3.10 Station No. setting for MELSEC data link functions The following describes how to specify network No. and station No. for a MELSEC data link function. (1) Functions other than extended functions Table10.16 Station numbers specified for MELSEC data link functions Communication Station No.
Page 532 FUNCTIONS AND PROGRAMMING (2) Extended functions Table10.17 Extended functions Communication Network No. specification Station No. specification Own station:255(FF Q series bus interface ) fixed Other station:1(CPU No.1), 2(CPU No.2), 3(CPU No.3), 4(CPU No.4) Own station:255(FF CC-Link IE controller network Own station, logical station No.: Other station:1(1 ) to 120(78 or MELSECNET/H...
Page 533: Device Types For Melsec Data Link Functions
FUNCTIONS AND PROGRAMMING 10.3.11 Device types for MELSEC data link functions Device types used for the MELSEC data link functions may be either code numbers or device names. (1) Common device types Table10.18 Common device types of MELSEC data link functions Device type Device Code...
Page 534 FUNCTIONS AND PROGRAMMING Table10.18 Common device types of MELSEC data link functions(Continued) Device type Device Code Device name DEC. HEX. DevSTN Retentive timer (current value) DevWw Own station link register (for sending) DevWr Own station link register (for receiving) DevSPB Own station buffer memory DevMAIL Q/QnA SEND function (with arrival confirmation) and RECV function...
Page 535 FUNCTIONS AND PROGRAMMING (3) CC-Link dedicated device types Table10.20 CC-Link dedicated device types Device type Code Device Device name DEC. HEX. DevX Own station RX DevY Own station RY DevSM Own station SB (link special relay for CC-Link) DevSD Own station SW (link special register for CC-Link) DevQSB Own station SB (link special relay for CC-Link) DevQSW...
Page 536 FUNCTIONS AND PROGRAMMING (4) Device types for accessing CC-Link IE controller modules or MELSECNET/H modules In the user program, either of the following two link device access methods can be selected by specifying a device. (a) Internal buffer access Table10.21 Device types for internal buffer access Device type Code Device...
Page 537 FUNCTIONS AND PROGRAMMING (c) Message reception Table10.23 Device types for message reception Device type Code Device Device name DEC. HEX. DevMAIL Q/QnA SEND function (with arrival confirmation) and RECV function DevMAILNC Q/QnA SEND function (no arrival confirmation) * 1 The device name specification (macro) is defined in this function's include file "MdFunc.h". Section 10.2.3 (1) ) POINT 1.
Page 538: Accessible Ranges And Devices Of Melsec Data Link Functions
FUNCTIONS AND PROGRAMMING 10.3.12 Accessible ranges and devices of MELSEC data link functions This section explains the accessible range and devices for use of the MELSEC data link functions. (1) Multiple CPU system access The following explains the accessible range and devices at the time of multiple CPU system access.
Page 539 FUNCTIONS AND PROGRAMMING 1) Accessing own station When accessing the own station, the following devices are accessible. Table10.25 Accessible devices at the time of own station access Access target Device type Own station Device (Device name specification) (Q06CCPU-V) DevSPB1 (for CPU No.1), Batch DevSPB2 (for CPU No.2), CPU shared memory...
Page 540 FUNCTIONS AND PROGRAMMING Table10.26 Accessible devices at the time of other station access(Continued) Device type Access target Device Programmable controller CPU (Device name specification) SD (special register), SW (link special Batch register for MELSECNET/H, CC-Link IE DevSD Random controller network and CC-Link) Batch T (main setting) DevTM...
Page 541 FUNCTIONS AND PROGRAMMING Table10.26 Accessible devices at the time of other station access(Continued) Device type Access target Device (Device name specification) Programmable controller CPU Batch Own station random access buffer DevMRB Random Batch Retentive timer (current value) DevSTN Random Own station link register Batch DevWw Random...
Page 542 FUNCTIONS AND PROGRAMMING (2) Access via CC-Link module The following explains the accessible range and devices when access is made via a CC-Link module. (a) Accessible range When access is made via a CC-Link module, the access is limited to programmable controller CPUs on the master or local stations where the CC-Link module is connected, the C Controller module, PC CPU module, intelligent device station, and personal computer with the CC-Link board installed.
Page 543 FUNCTIONS AND PROGRAMMING 1) Accessing own station The following indicates the accessible devices when accessing a CC-Link module controlled by the C Controller module. Table10.27 Accessible devices at the time of own station access Device type Device Accessibility (Device name specification) Batch Own station RX DevX...
Page 544 FUNCTIONS AND PROGRAMMING Table10.29 Accessible devices at the time of other station access Device type Access target Device (Device name specification) Batch DevX Random Batch DevY Random Batch DevL Random Batch DevM Random SM (special relay),SB (link special relay Batch for MELSECNET/H, CC-Link IE controller DevSM Random...
Page 545 FUNCTIONS AND PROGRAMMING Table10.29 Accessible devices at the time of other station access(Continued) Device type Access target Device (Device name specification) Batch C (main setting) DevCM Random Batch C (sub setting 1) DevCS Random Batch C (sub setting 2) DevCS2 Random Batch C (sub setting 3)
Page 546 FUNCTIONS AND PROGRAMMING Table10.29 Accessible devices at the time of other station access(Continued) Device type Access target Device (Device name specification) Own station link register Batch DevWw Random (for sending) Own station link register Batch DevWr (for receiving) Random Batch Own station buffer memory DevSPB Random...
Page 547 FUNCTIONS AND PROGRAMMING (3) Access via MELSECNET/H module The following explains the accessible range and devices when access is made via a MELSECNET/H module. (a) Accessible range This section provides a system configuration for access via a MELSECNET/H module and a table showing accessibility of each CPU type. 1) System configuration C Controller module Connected network...
Page 548 FUNCTIONS AND PROGRAMMING Table10.31 Accessibility table (continued) 4.Target CPU 1.Connected 2.Connected 3.Relayed network QCPU network station CPU CC-Link IE controller *4*5 network MELSECNET/H MELSECNET/10 QCPU (Q mode) MELSECNET(II) Ethernet Computer link CC-Link CC-Link IE controller network MELSECNET/H MELSECNET/10 MELSECNET/10 QnACPU MELSECNET(II) Ethernet Computer link...
Page 549 FUNCTIONS AND PROGRAMMING (b) Accessible devices The following explains the accessible devices when access is made via a MELSECNET/H module. POINT 1. The words, Batch and Random in the table indicate the following. Batch : Batch write (mdSend and mdSendEx functions) and batch read (mdReceive and mdReceiveEx functions) Random : Random write (mdRandW and mdRandWEx functions), random read (mdRandR and mdRandREx functions), bit set (mdDevSet...
Page 550 FUNCTIONS AND PROGRAMMING 2) Accessing other station Descriptions in 1) to 7) below are used to explain the access target. Table10.33 Access targets at the time of other station access Access target A1NCPU A0J2HCPU, A1SCPU(-S1), A1SHCPU, A1SJ(H)CPU, A2NCPU(-S1), A2SCPU(-S1), A2SHCPU(-S1) A2ACPU(-S1), A2UCPU(-S1), A2USCPU(-S1), A2ASCPU(-S1/-S30), A2USHCPU-S1, Q02(H)CPU-A, Q06HCPU-A A3NCPU, A3ACPU, A3UCPU...
Page 551 FUNCTIONS AND PROGRAMMING Table10.34 Accessible devices at the time of other station access(Continued) Device type Access target Device (Device name specification) Batch C (coil) DevCC Random Batch T (current value) DevTN Random Batch C (current value) DevCN Random Batch DevD Random SD (special register),SW (link special Batch...
Page 552 FUNCTIONS AND PROGRAMMING Table10.34 Accessible devices at the time of other station access(Continued) Device type Access target Device (Device name specification) Q/QnA link special relay Batch DevQSB Random (within Q/QnACPU) Batch Retentive timer (contact) DevSTT Random Batch Retentive timer (coil) DevSTC Random Q/QnA link special register...
Page 553 FUNCTIONS AND PROGRAMMING Table10.34 Accessible devices at the time of other station access(Continued) Device type Access target Device (Device name specification) Batch DevSPG(0) to Special direct buffer register Random DevSPG(255) Batch Other station buffer memory DevRBM Random Batch Other station random access buffer DevRAB Random Batch...
Page 554 FUNCTIONS AND PROGRAMMING 2) Accessibility table The following table indicates whether access can be made or not for each case. The own station and connected station CPUs are all accessible. Table10.35 CPU type CPU type QCPU (Q mode) QCPU (A mode) QnACPU ACPU C Controller module, PC CPU module...
Page 555 FUNCTIONS AND PROGRAMMING (b) Accessible devices The following explains the accessible devices when access is made via a CC-Link IE controller network module. POINT 1. The words, Batch and Random in the table indicate the following. Batch : Batch write (mdSend and mdSendEx functions) and batch read (mdReceive and mdReceiveEx functions) Random : Random write (mdRandW and mdRandWEx functions), random read (mdRandR and mdRandREx functions), bit set (mdDevSet...
Page 556 FUNCTIONS AND PROGRAMMING 2) Accessing other station Descriptions in 1) to 7) below are used to explain the access target. Table10.38 Access targets at the time of other station access Access target A1NCPU A0J2HCPU, A1SCPU(-S1), A1SHCPU, A1SJ(H)CPU, A2NCPU(-S1), A2SCPU(-S1), A2SHCPU(-S1) A2ACPU(-S1), A2UCPU(-S1), A2USCPU(-S1), A2ASCPU(-S1/-S30), A2USHCPU-S1, Q02(H)CPU-A, Q06HCPU-A A3NCPU, A3ACPU, A3UCPU...
Page 557 FUNCTIONS AND PROGRAMMING Table10.39 Accessible devices at the time of other station access (Continued) Device type Access target Device (Device name specification) Batch DevD Random SD (special register),SW (link special Batch register for MELSECNET/H, CC-Link IE DevSD Random controller network and CC-Link) Batch T (main setting) DevTM...
Page 558 FUNCTIONS AND PROGRAMMING Table10.39 Accessible devices at the time of other station access (Continued) Device type Access target Device (Device name specification) Batch Retentive timer (coil) DevSTC Random Q/QnA link special register Batch DevQSW Random (within Q/QnACPU) Q/QnA link edge relay Batch DevQV Random...
Page 559 FUNCTIONS AND PROGRAMMING Table10.39 Accessible devices at the time of other station access (Continued) Device type Access target Device (Device name specification) Batch Other station RX DevRX Random Batch Other station RY DevRY Random Batch Other station link register DevRW Random Other station SB Batch...
Page 560: Programming With Vxworks Api Functions
FUNCTIONS AND PROGRAMMING 10.4 Programming with VxWorks API Functions C Controller modules implement components that are shown in Appendix 7. For each component functionality and VxWorks API functions, refer to the following manual. VxWorks manual (1) Sample program using VxWorks API functions Installing SW PVC-CCPU registers a sample program that includes the following.
Page 561: Sample Programs
FUNCTIONS AND PROGRAMMING 10.5 Sample Programs When SW PVC-CCPU is installed into the development environment (personal computer), sample programs are registered to <User-specified folder> - <CCPU> - <CCPUTooL> - <Sample>. The sample programs are provided for user program creation as reference. Please use the sample programs at your own discretion.
Page 562 FUNCTIONS AND PROGRAMMING Remark Each of sample programs that are not available for the Q06CCPU-V-B contains the following description. /**************************************************************************/ Sample program When X0 is ON, unmount the CF card. Note) This sample program cannot be used because Q06CCPU-V-B does not support CF card interface. If the following functions are executed, unsupported communications path error (19203 [0x4B03]) will be returned.
Page 563: Chapter11 Overview Of Multiple Cpu System
OVERVIEW OF MULTIPLE CPU SYSTEM CHAPTER11 OVERVIEW OF MULTIPLE CPU SYSTEM 11.1 What is Multiple CPU System ? (1) Configuration of multiple CPU system The multiple CPU system is a system where more than one CPU module are mounted on the main base unit and each of them controls I/O modules and/or intelligent function modules individually.
Page 564 OVERVIEW OF MULTIPLE CPU SYSTEM Taking into account a system scale and applications, select the most suitable CPU modules to configure a desired system. Refer to Section 13.1 for combinations of applicable CPU modules. 11.1 What is Multiple CPU System ?
Page 565 OVERVIEW OF MULTIPLE CPU SYSTEM (2) Method for controlling I/O module and intelligent function module It is necessary to set which CPU module is to control which I/O modules and/or intelligent function modules in the multiple CPU system (control CPU setup). Slot number Control CPU setting Control with CPU module 1.
Page 566 OVERVIEW OF MULTIPLE CPU SYSTEM (3) Application example of multiple CPU system If programmable controller CPUs handle control tasks requiring high speed and fixed- cycle operations while the C Controller modules process data written by the C language, the optimum load distribution system can be created. Further, adding a Motion CPU to the multiple CPU system realizes a more sophisticated system that performs motion control, sequence control and information system processing (data processing/communications).
Page 567: Chapter12 Multiple Cpu System Configuration
MULTIPLE CPU SYSTEM CONFIGURATION CHAPTER12 MULTIPLE CPU SYSTEM CONFIGURATION This chapter explains the system configuration of a multiple CPU system and the operating precautions for configuring the multiple CPU system. 12.1 System Configuration This section explains the device configuration of the multiple CPU system, connection with the development environment, and the outline of the system configuration.
Page 568: Devices To Be Used
MULTIPLE CPU SYSTEM CONFIGURATION 12.1.1 Devices to be used (1) When using the main base unit (Q3 B) Commercially available CompactFlash card (to be purchased separately) C Controller Basic model High Performance Motion QCPU model QCPU module Battery Process CPU Universal model QCPU B type main base unit * Extension cable...
Page 569 MULTIPLE CPU SYSTEM CONFIGURATION POINT 1. For combinations of configurable CPU modules, refer to Section 13.1. 2. When a multiple CPU system is configured using a C Controller module, redundant power supply base units are not applicable. 12.1 System Configuration 12.1.1 Devices to be used...
Page 570 MULTIPLE CPU SYSTEM CONFIGURATION When using the slim type main base unit (Q3 SB) Commercially available CompactFlash card (to be purchased separately) High Performance C Controller module Basic model Battery model QCPU QCPU Slim type main base unit * Slim type power supply/input/output/ intelligent function module * 1 The programmable controller CPU does not accept the CompactFlash card.
Page 571 MULTIPLE CPU SYSTEM CONFIGURATION (3) When using the multiple CPU high speed main base unit (Q3 DB) Commercially available CompactFlash card (to be purchased separately) C Controller module Basic model High Performance Motion QCPU model QCPU Battery Process CPU Universal model QCPU DB multiple CPU high speed main base unit Extension cable...
Page 572: Connection With Development Environment
MULTIPLE CPU SYSTEM CONFIGURATION 12.1.2 Connection with development environment The connection with development environment for a multiple CPU system configuration is the same as that for a single CPU system configuration. ( Section 2.1.2) 12.1.3 Connection with peripheral devices The connection with peripheral devices for a multiple CPU system configuration is the same as that for a single CPU system configuration.
Page 573: System Configuration (When Cpu No. 1 Is C Controller Module)
MULTIPLE CPU SYSTEM CONFIGURATION 12.1.4 System configuration (When CPU No. 1 is C Controller module) (1) When using the main base unit (Q3 B) Main base unit..32-point modules are mounted to each slot. Q312B (12 slots occupied) ..Slot number ..
Page 574 MULTIPLE CPU SYSTEM CONFIGURATION Table12.1 Restrictions on system configuration, applicable base units, extension cables, power supply modules CPU number CPU module 1: CPU No.1, CPU module 2: CPU No.2, CPU module 3: CPU No.3, CPU module 4: CPU No.4 Maximum number of 7 extension stages extension stages Maximum number of...
Page 575 MULTIPLE CPU SYSTEM CONFIGURATION (2) When using the slim type main base unit (Q3 SB) Slim type main base unit ..32-point modules are mounted to each slot. Q35SB (5 slots occupied) ..Slot number ..I/O number Slim type power supply module CPU module 2 CPU module 1...
Page 576 MULTIPLE CPU SYSTEM CONFIGURATION (3) When using the multiple CPU high speed main base unit (Q3 DB) Multiple CPU high speed main base unit ... 32-point modules are mounted to each slots. Q312DB (12 slots occupied) ..Slot number ..I/O number Q series power CPU module 4 CPU module 3...
Page 577 MULTIPLE CPU SYSTEM CONFIGURATION Table12.3 Restrictions on system configuration, applicable base units, extension cables, power supply modules CPU number CPU module 1: CPU No.1, CPU module 2: CPU No.2, CPU module 3: CPU No.3, CPU module 4: CPU No.4 Maximum number of 7 extension stages extension stages Maximum number of...
Page 578: System Configuration (When Cpu No. 1 Is Basic Model Qcpu)
MULTIPLE CPU SYSTEM CONFIGURATION 12.1.5 System configuration (When CPU No. 1 is Basic model QCPU) (1) When using the main base unit (Q3 B) Main base unit..32-point modules are mounted to each slot. Q38B (8 slots occupied) ..Slot number ..
Page 579 MULTIPLE CPU SYSTEM CONFIGURATION Table12.4 Restrictions on System Configuration, Applicable Base Units, Extension Cables, Power Supply Modules CPU module 1: CPU No. 1 (Basic model QCPU), CPU number CPU module 2: CPU No. 2 (Motion CPU (except for Q172DCPU and Q173DCPU)), CPU module 3: CPU No.
Page 580 MULTIPLE CPU SYSTEM CONFIGURATION (2) When using the slim type main base unit (Q3 SB) Slim type main base unit ..32-point modules are mounted to each slot. Q35SB (5 slots occupied) ..Slot number ..I/O number Slim type power supply module CPU module 2 CPU module 1...
Page 581 MULTIPLE CPU SYSTEM CONFIGURATION (3) When using the multiple CPU high speed main base unit (Q3 DB) Multiple CPU high speed main base unit ... 32-point modules are mounted to each slots. Q38DB (8 slots occupied) ..Slot number ..I/O number Q series power supply module CPU module 2...
Page 582 MULTIPLE CPU SYSTEM CONFIGURATION Table12.6 Restrictions on system configuration, applicable base units, extension cables, power supply modules CPU module 1: CPU No.1 (Basic model QCPU) CPU number CPU module 2: CPU No.2 (C Controller module) Maximum number of 4 extension stages extension stages Maximum number of 25 - (Number of CPUs configured)
Page 583: System Configuration
MULTIPLE CPU SYSTEM CONFIGURATION 12.1.6 System configuration (When CPU No.1 is High Performance model QCPU or Process CPU) (1) When using the main base unit (Q3 B) Main base unit..32-point modules are mounted to each slot. Q312B (12 slots occupied) ..
Page 584 MULTIPLE CPU SYSTEM CONFIGURATION Table12.7 Restrictions on system configuration, applicable base units, extension cables, power supply modules CPU number CPU module 1: CPU No.1, CPU module 2: CPU No.2, CPU module 3: CPU No.3, CPU module 4: CPU No.4 Maximum number of 7 extension stages extension stages Maximum number of...
Page 585 MULTIPLE CPU SYSTEM CONFIGURATION (2) When using the slim type main base unit (Q3 SB) Slim type main base unit ..32-point modules are mounted to each slot. Q35SB (5 slots occupied) ..Slot number ..I/O number Slim type power supply module CPU module 2 CPU module 1...
Page 586 MULTIPLE CPU SYSTEM CONFIGURATION (3) When using the multiple CPU high speed main base unit (Q3 DB) Multiple CPU high speed main base unit ... 32-point modules are mounted to each slots. Q312DB (12 slots occupied) ..Slot number ..I/O number Q series power CPU module 4 CPU module 3...
Page 587 MULTIPLE CPU SYSTEM CONFIGURATION Table12.9 Restrictions on system configuration, applicable base units, extension cables, power supply modules CPU number CPU module 1: CPU No.1, CPU module 2: CPU No.2, CPU module 3: CPU No.3, CPU module 4: CPU No.4 Maximum number of 7 extension stages extension stages Maximum number of...
Page 588: System Configuration (When Cpu No.1 Is Universal Model Qcpu)
MULTIPLE CPU SYSTEM CONFIGURATION 12.1.7 System configuration (When CPU No.1 is Universal model QCPU) (1) When using the multiple CPU high speed main base unit (Q3 DB) Multiple CPU high speed main base unit ... 32-point modules are mounted to each slots. Q312DB (12 slots occupied) ..
Page 589 MULTIPLE CPU SYSTEM CONFIGURATION Table12.10 Restrictions on system configuration, applicable base units, extension cables, power supply modules CPU number CPU module 1: CPU No.1, CPU module 2: CPU No.2, CPU module 3: CPU No.3, CPU module 4: CPU No.4 Maximum number of 7 extension stages (When using Q02UCPU: 4) extension stages Maximum number of...
Page 590 MULTIPLE CPU SYSTEM CONFIGURATION (2) When using the main base unit (Q3 B) Main base unit ... 32-point modules are mounted to each slots. Q312B (12 slots occupied) ..Slot number ..I/O number CPU module 4* Q series power CPU module 3 supply module CPU module 2...
Page 591 MULTIPLE CPU SYSTEM CONFIGURATION Table12.11 Restrictions on system configuration, applicable base units, extension cables, power supply modules CPU number CPU module1: CPU No.1, CPU module 2: CPU No.2, CPU module 3: CPU No.3, CPU module 4: CPU No.4 Maximum number of 7 extension stages (When using Q02UCPU: 4) extension stages Maximum number of...
Page 592 MULTIPLE CPU SYSTEM CONFIGURATION (3) When using the slim type main base unit (Q3 SB) Slim type main base unit ... 32-point modules are mounted to each slots. Q35SB (5 slots occupied) ..Slot number ..I/O number Slim type power supply module CPU module 2 CPU module 1...
Page 593: Applicable Modules
MULTIPLE CPU SYSTEM CONFIGURATION 12.2 Applicable Modules 12.2.1 Applicable CPU modules Table12.13 lists the CPU modules that can configure a multiple CPU system with the C Controller module. Refer to the manual of each CPU module for how to confirm the version of each CPU module.
Page 594 MULTIPLE CPU SYSTEM CONFIGURATION * 2 Indicates the multiple CPU system compatible version when the QBF_MotionDDWR function or QBF_MotionDDRD function is used in the user program. When the above instruction is not used, there are no restrictions on the multiple CPU system compatible version.
Page 595: Precautions When Using I/O Modules Or Intelligent Function Modules
MULTIPLE CPU SYSTEM CONFIGURATION 12.2.2 Precautions when using I/O modules or intelligent function modules (1) Compatible I/O modules All I/O modules (QX , QY ) are compatible with the multiple CPU system. Any of CPU No.1 to No.4 can be set as a control CPU for them. (2) Compatible intelligent function modules (a) When using intelligent function modules in multiple CPU system The intelligent function modules compatible with the multiple CPU system are...
Page 596: Precautions For System Configuration
MULTIPLE CPU SYSTEM CONFIGURATION 12.3 Precautions for System Configuration This section explains the restrictions on configuration of a multiple CPU system where the C Controller module is used. (1) Restrictions on the number of mounted modules The following indicates the modules having restrictions on the number of mounted modules in a multiple CPU system.
Page 597 MULTIPLE CPU SYSTEM CONFIGURATION (b) When CPU No. 1 is Basic model QCPU Table12.15 Modules having restrictions on the number of mounted modules Limit on number of mounted Limit on number of mounted Product Model name modules per system modules per CPU •...
Page 598 MULTIPLE CPU SYSTEM CONFIGURATION (c) When CPU No. 1 is High Performance model QCPU or Process CPU Table12.16 Modules having restrictions on the number of mounted modules Limit on number of mounted modules Limit on number of mounted Product Model name per system modules per CPU Q series CC-Link IE controller...
Page 599 MULTIPLE CPU SYSTEM CONFIGURATION (d) When CPU No.1 is Universal model QCPU Table12.17 Modules having restrictions on the number of mounted modules Limit on number of mounted Limit on number of mounted Product Model name modules per system modules per CPU Q series CC-Link IE controller •...
Page 600 MULTIPLE CPU SYSTEM CONFIGURATION (2) When programmable controller CPU version incompatible with C Controller module is used When a multiple CPU system including the C Controller module is configured by using a programmable controller CPU version incompatible with C Controller module, the following error occurs and the multiple CPU system does not start up.
Page 601 MULTIPLE CPU SYSTEM CONFIGURATION (b) When CPU No. 1 is High Performance model QCPU GX Developer Figure 12.17 Multiple CPU system configuration example 1) Error check method If an error has occurred, check the error details in the PLC diagnostics of GX Developer Version 6 or later.
Page 602 MULTIPLE CPU SYSTEM CONFIGURATION (3) Combination of power supply module, base unit and programmable controller CPU There are restrictions on the combination of the power supply module, base unit and programmable controller CPU. Section 12.1.1) (4) Precautions for GOT connection The display devices applicable to the C Controller module are the same as the ones in a single CPU system.
Page 603 MULTIPLE CPU SYSTEM CONFIGURATION (6) Access from GX Developer to programmable controller CPU via C Controller module The C Controller module cannot connect to GX Developer. However, the following CPU can be accessed from GX Developer via the C Controller module.
Page 604 MULTIPLE CPU SYSTEM CONFIGURATION Station No. 2 (Normal station) Station No. 3 (Normal station) Control CPU setting MELSECNET/H PLC-to-PLC network Station No. 1 (Control station) Control CPU setting GX-Developer Figure 12.18 Access via MELSECNET/H PLC-to-PLC network - 38 12.3 Precautions for System Configuration...
Page 605: Chapter13 Multiple Cpu System Concept
MULTIPLE CPU SYSTEM CONCEPT CHAPTER13 MULTIPLE CPU SYSTEM CONCEPT 13.1 Mounting Position of CPU Module When a multiple CPU system is configured, combinations of CPU modules shown in Table13.1 to Table13.3 are available. Table13.1 When using the main base unit (Q3 B) Number of CPU modules mountable as CPU No.2 and higher number Motion CPU Q172CPUN...
Page 606 MULTIPLE CPU SYSTEM CONCEPT Table13.3 When using the multiple CPU high speed main base unit (Q3 DB) Number of CPU modules mountable as CPU No.2 and higher number Motion CPU Q172CPUN Max. no. of High Q172CPUN-T mounted Performance Q173CPUN CPU No.1 modules Reference model QCPU/...
Page 607 MULTIPLE CPU SYSTEM CONCEPT (c) "CPU (Empty)" setting An empty slot can be reserved for future addition of a CPU module. Set the number of CPU modules, including the one on the empty slot, in "Number of CPUs" on the <<Multiple CPU settings>> tab of the C Controller setting utility. After that, set the type "CPU (Empty)"...
Page 608 MULTIPLE CPU SYSTEM CONCEPT Table13.4 CPU module mounting position : Slot number CPU module mounting position No. of CPUs* * 1 The No. of CPUs indicates the value set in "Number of CPUs" on the <<Multiple CPU settings>> tab of the C Controller setting utility. Refer to the manuals of the corresponding CPU modules for programmable controller CPUs and Motion CPUs.
Page 609 MULTIPLE CPU SYSTEM CONCEPT (2) When CPU No. 1 is Basic model QCPU The mounting position of each CPU module is shown in Table13.5. (a) Mounting position of Basic model QCPU Only one Basic model QCPU can be mounted on the CPU slot (slot on the right- hand side of the power supply module) of the main base unit.
Page 610 MULTIPLE CPU SYSTEM CONCEPT 2) When adding a C Controller module in the future • When mounting a Motion CPU Set slot 1 as "CPU (Empty)." Slot number Slot number Added C Controller module Figure 13.5 "CPU (Empty)" setting for addition of C Controller module •...
Page 611 MULTIPLE CPU SYSTEM CONCEPT Table13.5 Mounting position of CPU module : Slot num Mounting position of CPU module No. of CPUs* * 1 The No. of CPUs indicates the value set in "Number of CPUs" on the <<Multiple CPU settings>> tab of the C Controller setting utility.
Page 612 MULTIPLE CPU SYSTEM CONCEPT (3) When CPU No. 1 is High Performance model QCPU or Process CPU The mounting position of each CPU module is shown in Table13.6. (a) Mounting position of High Performance model QCPU or Process CPU Up to four High Performance model QCPUs or Process CPUs can be mounted to the slots of a main base unit, from CPU slot (the slot on the immediate right of power supply module) through slot 2.
Page 613 MULTIPLE CPU SYSTEM CONCEPT (e) "CPU (Empty)" setting An empty slot can be reserved for future addition of a CPU module. Set the number of CPU modules, including the one on the empty slot, in "Number of CPUs" on the <<Multiple CPU settings>> tab of the C Controller setting utility. After that, set the type "CPU (Empty)"...
Page 614 MULTIPLE CPU SYSTEM CONCEPT Table13.6 CPU module mounting position : Slot number CPU module mounting position No. of CPUs* * 1 The No. of CPUs indicates the value set in "Number of CPUs" on the <<Multiple CPU settings>> tab of the C Controller setting utility. Refer to the manuals of the corresponding CPU modules for programmable controller CPUs and Motion CPUs.
Page 615 MULTIPLE CPU SYSTEM CONCEPT (4) When CPU No.1 is Universal model QCPU The mounting position of each CPU module is shown in Table 13.7 and Table 13.8. (a) Mounting position of Universal model QCPU Only one Q02UCPU can be mounted on the CPU slot (the slot on the immediate right of power supply module).
Page 616 MULTIPLE CPU SYSTEM CONCEPT (e) "CPU (Empty)" setting An empty slot can be reserved for future addition of a CPU module. Set the number of CPU modules, including the one on the empty slot, in "Number of CPUs" on the <<Multiple CPU settings>> tab of the C Controller setting utility. After that, on the <<I/O assignment settings>>...
Page 617 MULTIPLE CPU SYSTEM CONCEPT Table13.8 Mounting position of CPU module (When mounting other than Q02UCPU as CPU No.1) : Slot number Mounting position of CPU module No. of CPUs * 1 The No. of CPUs indicates the value set in "Number of CPUs" on the <<Multiple CPU settings>> tab of the C Controller setting utility.
Page 618 MULTIPLE CPU SYSTEM CONCEPT Table13.8 Mounting position of CPU module (When mounting other than Q02UCPU as CPU No.1) (Continued) : Slot number Mounting position of CPU module No. of CPUs * 1 The No. of CPUs indicates the value set in "Number of CPUs" on the <<Multiple CPU settings>> tab of the C Controller setting utility.
Page 619: Cpu No. Of Cpu Module
MULTIPLE CPU SYSTEM CONCEPT 13.2 CPU No. of CPU Module (1) CPU No. allocation CPU numbers are allocated for identifying the CPU modules mounted on the main base unit in the multiple CPU system. CPU No.1 is allocated to the CPU slot, and Universal Basic CPU No.2, No.3 and No.4 are allocated to the right of the CPU No.1 in this...
Page 620 MULTIPLE CPU SYSTEM CONCEPT The CPU No. is used for the following applications. • Communication diagnostics on the <<Communication diagnostics>> tab of the C Controller setting utility. ( Section 9.2.10) Slot number CPU number Ethernet Communicate with CPU No. 2. Specify CPU No.
Page 621 MULTIPLE CPU SYSTEM CONCEPT • Setting the control CPU on the <<I/O assignment settings>> tab of the C Controller setting utility. ( Section 15.1.6) Control CPU setting Figure 13.15 Control CPU setting Remark Refer to the manual of the corresponding CPU module for confirmation of the host CPU No.
Page 622: I/O Number Assignment
MULTIPLE CPU SYSTEM CONCEPT 13.3 I/O Number Assignment In the multiple CPU system, I/O numbers are used for interactive transmission between a CPU module and the I/O modules and intelligent function modules, or between CPU modules. 13.3.1 I/O number assignment of each module The multiple CPU system is different from the single CPU system in the position (slot) of I/ O number 00 However, the order of allocating I/O numbers, I/O numbers for each slot and empty slots is...
Page 623: I/O Number Of Each Cpu Module
MULTIPLE CPU SYSTEM CONCEPT 13.3.2 I/O number of each CPU module In the multiple CPU system, I/O numbers are assigned to specify each of mounted CPU modules. The I/O number for each CPU module is fixed to the mounted slot and cannot be changed by <<I/O assignment settings>>...
Page 624: Access Ranges Between Cpu Modules And Other Modules
MULTIPLE CPU SYSTEM CONCEPT 13.4 Access Ranges between CPU Modules and Other Modules 13.4.1 Access to controlled modules As in a single CPU system, the CPU module can read/write data to/from the buffer memories of the controlled I/O modules and intelligent function modules. Section 4.2) - 20 13.4 Access Ranges between CPU Modules and Other Modules...
Page 625: Access To Non-Controlled Modules
MULTIPLE CPU SYSTEM CONCEPT 13.4.2 Access to non-controlled modules A CPU module can load the input (X) ON/OFF data of non-controlled modules and the output (Y) ON/OFF data of other CPUs by the parameters of the Multiple CPU settings. Therefore, ON/OFF data of input modules, I/O composite modules or intelligent function modules controlled by other CPUs can be used as interlocks for the host CPU, and the output status to external equipment being controlled by another CPU can be confirmed.
Page 626 MULTIPLE CPU SYSTEM CONCEPT (1) Input (X) loading Whether inputs can be loaded or not from the input modules and intelligent function modules controlled by another CPU is determined by "I/O sharing when using Multiple CPUs" on the <<Multiple CPU settings>> tab of the C Controller setting utility. I/O sharing when using Multiple CPUs All CPUs can read all inputs: "All CPUs can read all inputs"...
Page 627 MULTIPLE CPU SYSTEM CONCEPT 2) Input (X) data are loaded from the modules indicated in Table13.11 that are mounted on the main base unit and extension base unit. Table13.11 Modules trom which inputs can be loaded Type setting on <<I/O assignment settings>> tab Mounted module of C Controller setting utility Input module...
Page 628 MULTIPLE CPU SYSTEM CONCEPT (2) Output (Y) loading Whether outputs can be loaded or not from the output modules and intelligent function modules controlled by another CPU is determined by "I/O sharing when using Multiple CPUs" on the <<Multiple CPU settings>> tab of the C Controller setting utility. I/O sharing when using Multiple CPUs All CPUs can read all outputs: "All CPUs can read all outputs"...
Page 629 MULTIPLE CPU SYSTEM CONCEPT 2) Output (Y) data are loaded from the modules indicated in Table13.12 that are mounted on the main base unit and extension base unit. Table13.12 Modules trom which outputs can be loaded Type setting on <<I/O assignment settings>> tab Mounted module of C Controller setting utility Output module...
Page 630 MULTIPLE CPU SYSTEM CONCEPT (3) Outputs to output modules and intelligent function modules ON/OFF data cannot be output to non-controlled modules. When the outputs of the output modules and intelligent function modules controlled by another CPU are turned ON/OFF from the C Controller module, they are not output to the output modules and intelligent function modules.
Page 631 MULTIPLE CPU SYSTEM CONCEPT (b) Write to buffer memory Data cannot be written to the buffer memory of the intelligent function module controlled by another CPU. If this happens, a non-controlled module write error (return value: -28654) occurs. Intelligent function modules Slot number Control CPU setting Write by bus interface function...
Page 632: Access To Link Devices
MULTIPLE CPU SYSTEM CONCEPT 13.5 Access to Link Devices Only the control CPU can access link devices of CC-Link IE controller network modules or MELSECNET/H modules by user programs. A CC-Link IE controller network module or MELSECNET/H module that is controlled by another CPU is not accessible by a user program.
Page 633: Resetting Cpu Module
MULTIPLE CPU SYSTEM CONCEPT 13.6 Resetting CPU Module The entire multiple CPU system can be reset by resetting CPU No.1. The CPU modules of No.2 to No.4, I/O modules and intelligent function modules will be reset when CPU No.1 is reset. If a stop error has occurred in any of the CPUs on the multiple CPU system, either reset CPU No.1 or restart the multiple CPU system (power supply ON ON) for...
Page 634: Operation At Cpu Module Stop Error
MULTIPLE CPU SYSTEM CONCEPT 13.7 Operation at CPU Module Stop Error The entire system behaves differently depending on whether a stop error occurs in CPU No.1 or any of CPU No.2 to No.4 in the multiple CPU system. (1) When a stop error occurs in CPU No.1 When a stop error occurs in the CPU module No.
Page 635 MULTIPLE CPU SYSTEM CONCEPT POINT When a stop error occurs, a multi CPU error (error code: 7000, MULTI CPU DOWN), occurs in the CPU on which the error was detected. Depending on the timing of error detection, a "MULTI CPU DOWN" error may be detected in a CPU of "MULTI CPU DOWN"...
Page 636 MULTIPLE CPU SYSTEM CONCEPT (3) Restoring the system Restore the system in the following procedure. (a) When C Controller module is set as CPU No. 1 1) Check the faulty CPU No. and error factor in "System information" on the <<Module monitoring>>...
Page 637: Chapter14 Communications Between Cpu Modules
COMMUNICATIONS BETWEEN CPU MODULES CHAPTER14 COMMUNICATIONS BETWEEN CPU MODULES This chapter explains the functions utilized between the C Controller module and programmable controller CPU/Motion CPU in a multiple CPU system. Table14.1 List of functions utilized between C Controller module and programmable controller CPU/Motion CPU Reference Function...
Page 638: Data Communications By Melsec Data Link Functions
COMMUNICATIONS BETWEEN CPU MODULES 14.1 Data Communications by MELSEC Data Link Functions (1) Data communications by MELSEC data link functions (the Q06CCPU-V only) Access can be made from the C Controller module to programmable controller CPU device data. Use the MELSEC data link functions to create the user program of the C Controller module.
Page 639 COMMUNICATIONS BETWEEN CPU MODULES (2) Functions The following MELSEC data link functions are used for data communications. Table14.2 Functions used for Data communications by MELSEC data link functions Function name Function mdOpen Opens a communication line. mdClose Closes a communication line. mdSend Batch writes devices.
Page 640: Event Notification
COMMUNICATIONS BETWEEN CPU MODULES 14.2 Event Notification (1) Event notification This function issues an interrupt event notification to a user program waiting for an interrupt event in the C Controller module to resume the user program. An interrupt event is issued by either of the following. •...
Page 641 COMMUNICATIONS BETWEEN CPU MODULES (3) Functions The following indicates the functions used for event notification. Table14.3 Functions used for event notification Function name Function Waits for an interrupt event notification from the user program (QBF_GINT function) of the C Controller module or from the QBF_WaitEvent sequence program (S(P).GINT instruction) of the programmable controller CPU.
Page 642 COMMUNICATIONS BETWEEN CPU MODULES (4) Sequence program instruction (S(P).GINT) used for event notification The following indicates the programmable controller CPU-dedicated instruction used for event notification. Table14.4 Devices applicable to S(P).GINT instruction Applicable devices Link direct device Setting Internal device Intelligent File Index register Constant...
Page 643 COMMUNICATIONS BETWEEN CPU MODULES [Control details] On the leading edge (OFF to ON) of the S(P).GINT instruction execution command in the sequence program, an interrupt is generated for the C Controller module. When the interrupt is generated from the programmable controller CPU, the C Controller module executes the processing of the bus interface function (QBF_WaitEvent function) programmed in the user program.
Page 644 COMMUNICATIONS BETWEEN CPU MODULES [Error details] In any of the following cases, an operation error occurs, the error flag (SM0) of the programmable controller CPU turns ON, and the error code is stored into SD0. Table14.7 Error codes related to S(P).GINT instruction Corrective Error factor Error code...
Page 645: Data Communications Using Cpu Shared Memory
COMMUNICATIONS BETWEEN CPU MODULES 14.3 Data Communications Using CPU Shared Memory (1) Data communications using CPU shared memory This function enables data communications between the C Controller module and CPU module using the CPU shared memory. Use the bus interface functions to create the user program of the C Controller module. The following describes the data communication methods using the CPU shared memory and its selection.
Page 646 COMMUNICATIONS BETWEEN CPU MODULES POINT 1) Access can be made to the CPU shared memory only when the No. of CPUs is set to 2 or more on the <<Multiple CPU settings>> tab of the C Controller setting utility. CPU No. error (return value: -28662) will occur if access is made to the CPU shared memory without the No.
Page 647: Cpu Shared Memory Structure
COMMUNICATIONS BETWEEN CPU MODULES 14.3.1 CPU shared memory structure The following indicates the CPU shared memory structure and accessibility of the C Controller module. Programmable Programmable C Controller module controller CPU controller CPU (host CPU) Motion CPU C Controller module (another CPU) User program Power supply...
Page 648 COMMUNICATIONS BETWEEN CPU MODULES Table14.10 CPU shared memory structure Area name Description Host CPU operation The error details and operation status of the host CPU (C Controller module) are stored. information area System area Area used by the system. This area is automatically refreshed to the programmable controller Auto refresh area CPU and Motion CPU devices according to the auto refresh setting.
Page 649 COMMUNICATIONS BETWEEN CPU MODULES Table14.11 List of host CPU operation information areas CPU shared memory Name Description Details address The area for checking if information is stored in the host CPU's Information presence Information flag operation information area (1 to 1F ,) or not.
Page 650: Data Communications Using Auto Refresh
COMMUNICATIONS BETWEEN CPU MODULES 14.3.2 Data communications using auto refresh This section explains the processing and setting for data communications using CPU shared memory and the auto refresh of the programmable controller CPU and Motion CPU. (1) Processing of data communications using auto refresh The following shows the processing of data communications made using auto refresh.
Page 651 COMMUNICATIONS BETWEEN CPU MODULES POINT 1) Auto refresh in 4. of Figure 14.10 is performed in the END processing of the programmable controller CPU (Motion CPU) after execution of the QBF_ToBuf function in 2. of Figure 14.10. 2) Auto refresh cannot be used for communication between a C Controller module and the Q172DCPU or Q173DCPU.
Page 652 COMMUNICATIONS BETWEEN CPU MODULES (2) Auto refresh area setting The auto refresh area must be set to make data communications using the auto refresh of the programmable controller CPU or Motion CPU. To set the auto refresh area, make "Refresh settings" on the <<Multiple CPU settings>>...
Page 653 COMMUNICATIONS BETWEEN CPU MODULES 3) "Start", "End" When "Points" are set, the first address and last address of the auto refresh area are automatically displayed in "Start" and "End" as hexadecimal offset values. Remark Refer to the manual of the corresponding CPU module for the auto refresh area setting of the programmable controller CPU or Motion CPU.
Page 654: Data Communications Without Using Auto Refresh
COMMUNICATIONS BETWEEN CPU MODULES (3) Precautions for data communications using auto refresh Depending on the timing of write to the auto refresh area of the host CPU and read from another CPU, old data and new data may exist together in the data of each CPU. For auto refresh, create an interlock program so that the data of another CPU is not used when both old and new data exist.
Page 655 COMMUNICATIONS BETWEEN CPU MODULES Remark Figure 14.13 shows an operation example using the S.TO and FROM instructions on the High Performance model QCPU. Refer to the manual of the corresponding CPU module for the operation of the programmable controller CPU when auto refresh is not used. (b) Between C Controller modules C Controller module 1) C Controller module 2)
Page 656 COMMUNICATIONS BETWEEN CPU MODULES (c) Between Motion CPU (Q172DCPU, Q173DCPU) and C Controller module C Controller module Motion CPU (Q172DCPU, Q173DCPU) CPU shared memory CPU shared memory Host CPU operation information area Host CPU operation information area System area System area Auto refresh area 3.
Page 657: Programmable Controller Remote Control Function
COMMUNICATIONS BETWEEN CPU MODULES 14.4 Programmable Controller Remote Control Function (1) Programmable controller remote control function (the Q06CCPU-V only) With this function, the C Controller module can control the execution status of a programmable controller CPU. Use the MELSEC data link functions to create the user program of the C Controller module.
Page 658: Sequence Program Control Function
COMMUNICATIONS BETWEEN CPU MODULES 14.5 Sequence Program Control Functioníç1 Basic Note14.1 (1) Sequence program control Function This function controls (changes) the sequence program execution type of the programmable controller CPU from the C Controller module. Use the bus interface function to create the user program of the C Controller module. Programmable controller CPU C Controller module Sequence program...
Page 659: Interrupt Issue To Motion Cpu
COMMUNICATIONS BETWEEN CPU MODULES 14.6 Interrupt Issue to Motion CPU (1) Interrupt issue to Motion CPU This function issues an interrupt from the user program of the C Controller module to the Motion CPU. Use the bus interface function to create the user program of the C Controller module. Motion CPU C Controller module /* Issues an interrupt */...
Page 660: Motion Cpu Control Instruction
COMMUNICATIONS BETWEEN CPU MODULES 14.7 Motion CPU Control Instruction (1) Motion CPU control instruction This function gives a control instruction to the Motion CPU from the user program of the C Controller module. Use the bus interface function to create the user program of the C Controller module. C Controller module Motion CPU /* Motion SFC program start request */...
Page 661: Motion Cpu Device Access
COMMUNICATIONS BETWEEN CPU MODULES 14.8 Motion CPU Device Access (1) Motion CPU device access This function allows data writing/reading from the user program of the C Controller module to the Motion CPU devices. Use the bus interface functions to create the user program of the C Controller module. C Controller module Motion CPU /* Write to Motion CPU device */...
Page 662: Chapter15 Parameters Added For Multiple Cpu System
PARAMETERS ADDED FOR MULTIPLE CPU SYSTEM CHAPTER15 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEM 15.1 Parameter List (1) Parameters for multiple CPU system Compared with the single CPU system, the multiple CPU system has additional settings of "Number of CPUs", "Control CPU", "Refresh settings (automatic refresh settings)"...
Page 663: Parameter List
PARAMETERS ADDED FOR MULTIPLE CPU SYSTEM (2) C Controller setting utility setting items needed for multiple CPU system operation Table15.1 indicates the C Controller setting utility items required for using a multiple CPU system. Table15.1 Setting list for the multiple CPU system and I/O assignment (control CPU) Necessity Same C Controller setting utility item...
Page 664 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEM If some of the Multiple CPU setting parameters have been changed, adjust the all CPU settings in the multiple CPU system to the same values, and then reset CPU No.1, or reboot the multiple CPU system (power ON, OFF, and ON again). The C Controller setting utility has a feature that allows you to utilize multiple CPU parameters previously set in the C Controller setting utility or GX Developer.
Page 665: Setting Number Of Cpus (Setup Required)
PARAMETERS ADDED FOR MULTIPLE CPU SYSTEM 15.1.1 Setting Number of CPUs (Setup required) (1) Number of CPUs On the <<Multiple CPU settings>> tab of the C Controller setting utility, select the number of CPU modules to be used in the multiple CPU system. Number of CPUs Figure 15.1 Number of CPUs setting screen (2) Reserving empty slots...
Page 666 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEM POINT In the actually mounted CPU No.1, an error may occur due to either of the following error factors (1) or (2). (1) When CPU modules exceeding the preset number of CPUs are mounted (a) When CPU No.1 is a C Controller module An intelligent function module assignment error (error code: 2126, SP.UNIT LAY ERROR.) or a parameter error (error code: 3010,...
Page 667: Operation Mode Setting (Optional)
PARAMETERS ADDED FOR MULTIPLE CPU SYSTEM 15.1.2 Operation mode setting (optional) When a stop error occurs in a CPU module other than CPU No.1, this setting allows operations of other CPUs to continue. The operation mode for CPU No.1 cannot be changed. All CPUs will stop due to a stop error of CPU No.1.
Page 668: Chapter16 Precautions For Use Of Ans Series Module
PRECAUTIONS FOR USE OF AnS SERIES MODULE CHAPTER16 PRECAUTIONS FOR USE OF A S SERIES MODULE 16.1 Precautions for Use of AnS Series Module (1) Applicable I/O modules and special function modules Only when a multiple CPU system is configured with a High Performance model QCPU set as CPU No.1, the AnS series (compact type) I/O modules and special function modules can be used.
Page 669 PRECAUTIONS FOR USE OF AnS SERIES MODULE (2) Control CPU setting The AnS series I/O modules or special function modules can be controlled by only one of High Performance model QCPUs No.1 to No.4 when configuring a multiple CPU system. The C Controller module or Motion CPU cannot be set to a control CPU.
Page 670: Chapter17 Starting Multiple Cpu System
STARTING MULTIPLE CPU SYSTEM CHAPTER17 STARTING MULTIPLE CPU SYSTEM This chapter explains the standard startup procedure of a multiple CPU system. 17.1 Flowchart for Starting Multiple CPU System For the parameter setting and programming of a programmable controller CPU or Motion CPU, refer to each CPU module manual.
Page 671 STARTING MULTIPLE CPU SYSTEM (From previous page) Setting of CPU No.2 and higher Utilize the CPU No.1 setting Section 9.1.6, 17.2.4 Section 9.1.6, 17.2.4*2 to set the same multiple CPU system parameters to all CPU modules.*3 Section 9.2.7*2 Section 9.2.7 Make the system setting necessary to use each CPU module.
Page 672 STARTING MULTIPLE CPU SYSTEM (To Page 17-1 1)) (From previous page) On the System information screen of Section 9.2.5 (3) Section 9.2.5 (3) the C Controller setting utility, check the operating status (e.g. errors) of the multiple CPU system. Section 13.7 Has any error occurred? Section 13.7 Section 5.3 (3), (4), (5)
Page 673: Setting Parameters Added For Multiple Cpu System
STARTING MULTIPLE CPU SYSTEM 17.2 Setting Parameters Added for Multiple CPU System This section provides a procedure for setting the multiple CPU system parameters on the C Controller setting utility. 17.2.1 System configuration The multiple CPU system parameter setting procedure is explained using the system shown in Figure 17.2 as an example.
Page 674: Parameters Required For Multiple Cpu System
STARTING MULTIPLE CPU SYSTEM 17.2.2 Parameters required for multiple CPU system The following parameters must be set for the multiple CPU system. The same parameters must be set to the items marked as "Same setting to all CPU modules" for all CPU modules in the multiple CPU system. ( Section 15.1) Number of CPUs Multiple CPU settings...
Page 675 STARTING MULTIPLE CPU SYSTEM 17.2.3 When creating new systemíç1 Start Start the C Controller setting utility. Connect to the C Controller module. "Points occupied by empty slot" (optional) on <<System settings>> tab Set the points to be occupied by one empty slot. Default: 16 points "Number of CPUs"...
Page 676: When Creating New System
STARTING MULTIPLE CPU SYSTEM (From previous page) "Operation mode" (optional) on <<Multiple CPU settings>> tab Select whether to stop or continue the operations of all CPUs in the event of a stop error. Default: All CPUs stop by a stop error in any of CPU No.
Page 677 STARTING MULTIPLE CPU SYSTEM (From previous page) "Refresh settings" (optional) on <<Multiple CPU settings>> tab Set the points of the auto refresh area where data communications between CPU modules will be performed by auto refresh. "Refresh settings" (optional) on <<Multiple CPU settings>>...
Page 678 STARTING MULTIPLE CPU SYSTEM (From previous page) In Type of the <<I/O assignment settings>> tab, select "CPU (Empty)" for the slot to which no CPU module is mounted. Click the Detailed settings button to open the "Detailed settings" screen. Control CPU (setup required) Select a control CPU (CPU No.1 to 4) for Universal Basic...
Page 679: Reusing Preset Multiple Cpu Parameters
STARTING MULTIPLE CPU SYSTEM 17.2.4 Reusing preset multiple CPU parameters Start Start the C Controller setting utility. Connect to the C Controller module. Click the Import multiple CPU parameters button on the <<Multiple CPU settings>> or <<I/O assignment settings>> tab. Setting of the project to be imported Select a project in GX Developer or a parameter setting file in C Controller setting...
Page 680 STARTING MULTIPLE CPU SYSTEM (From previous page) Verify the multiple CPU setting data on the <<Multiple CPU settings>> tab. Check the I/O assignment setting and base setting data on the <<I/O assignment settings>> tab. Click the Detailed settings button to display the "Detailed settings"...
Page 681 STARTING MULTIPLE CPU SYSTEM (From previous page) Confirm the settings of "Control CPU". Check the "Points occupied by empty slot" setting on the <<System settings>> tab. Make parameter settings other than those for the multiple CPU system. Save the set parameters into a file. Figure 17.5 Parameter setting procedure for importing multiple CPU parameters 17.2 Setting Parameters Added for Multiple CPU System - 12...
Page 682: Chapter18 Troubleshooting
TROUBLESHOOTING CHAPTER18 TROUBLESHOOTING This chapter explains various types of error information, the return values (error codes) of the bus interface functions and MELSEC data link functions (for the Q06CCPU-V only), and the corrective actions for the cases of problem occurrence. 18.1 Troubleshooting Basics First check the following three points for troubleshooting.
Page 683 TROUBLESHOOTING 18.2 Troubleshooting If a fault has occurred in the C Controller module, first conduct a hardware self-diagnostics to check the C Controller module for a hardware failure. ( Section 18.5) If a problem arises, see the following table and refer to the relevant troubleshooting flow to identify the cause.
Page 684: When Power Led Of Power Supply Module Turns Off
Turn it inactive? on after several minutes. Did the POWER LED turn on? Please consult your local Mitsubishi service center or representative, explaining the details of the problem. Figure 18.1 When POWER LED turns off on power supply module 18.2 Troubleshooting...
Page 685: When Mode Led Is Not Lit Green
Is the MODE LED lit orange? Carry out the hardware self-diagnostics of the C Controller module. Check the result of the hardware self- Consult your local Mitsubishi service diagnostics, and consult your local center or representative, explaining Mitsubishi service center or the details of the problem.
Page 686 Compile the user program and regenerate an execution file according to the C Controller module specifications. Completed Consult your local Mitsubishi service center or representative, explaining the details of the problem. Figure 18.3 When ERR. LED is on or flashing * 1 Specify the correct script file and user program with special care.
Page 687: When Run Led Keeps Flashing
TROUBLESHOOTING 18.2.4 When RUN LED keeps flashing When the RUN LED of the C Controller module keeps flashing, it means the script file (command) remains in execution. Perform the following: • Correct the script file and user program. ( Section 10.2.8) •...
Page 688: When Unit Verify Err. Occurs
Has any error occurred? Replace the base unit. Has any error occurred? It is a hardware fault of the module. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. Figure 18.4 When UNIT VERIFY ERR. has occurred 18.2 Troubleshooting...
Page 689: When Control-Bus.err. Occurs
Has any error occurred? Replace the base unit. Has any error occurred? It is a hardware fault of the module. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. Figure 18.5 When CONTROL-BUS. ERR. has occurred 18.2 Troubleshooting...
Page 690: When Communication Is Not Available Between Development Environment (Pc) And C Controller
Reinstall the software package. Does it normally communicate? Completed Consult your local Mitsubishi service center or representative, explaining the details of the problem. Figure 18.6 When communications are not available 18.2 Troubleshooting 18.2.7 When communication is not available between development environment (PC) and C Controller...
Page 691 TROUBLESHOOTING (2) When connection to C Controller module is not available from development environment (personal computer) via FTP Check the following when connection from the development environment (personal computer) to the C Controller module is not available via FTP. • Steps 1), 2) and 3) in the flowchart given in this section (1). •...
Page 692: When Program Cannot Be Written
(shutdown completed), module lit green? reapply power to the C Controller system to turn on the MODE LED. Consult your local Mitsubishi service center or representative, explaining the details of the problem. Figure 18.7 When program cannot be written * 1 The Q06CCPU-V-B does not accept CompactFlash cards.
Page 693: When Error Occurs At Function Execution
Correct the pointer value. details of the problem. Reserve the memory area. Has any error occurred? Consult your local Mitsubishi service center Completed or representative, explaining the details of the problem. Figure 18.8 When error occurs at function execution 18.2 Troubleshooting...
Page 694: When File System Error Occurs
TROUBLESHOOTING 18.2.10 When file system error occurs The following flowchart shows the procedures to be taken when a file system error has occurred during access to the standard ROM or CompactFlash card (the Q06CCPU-V only). POINT Data cannot be written to the standard ROM when the standard ROM has been shut down.
Page 695 Section 18.6 program files. ( Section 18.6 ). Has a file system error occurred? Consult your local Mitsubishi service Complete center or representative, explaining the details of the problem. Figure 18.9 When file system error has occurred (continued) 18.2 Troubleshooting - 14 18.2.10 When file system error occurs...
Page 696: When Output Module Led Does Not Turn On
Consult your local Mitsubishi service then forcibly turned center or representative, explaining the details of the problem. It is a hardware fault of the output module.
Page 697: When Output Load Device Of Output Module Does Not Turn On
TROUBLESHOOTING 18.2.12 When output load device of output module does not turn on The following flowchart shows procedures to be taken when the output load device of the output module does not turn on during operation of the C Controller system. The output load does not turn on.
Page 698 TROUBLESHOOTING (1) For the Q06CCPU-V Error occurred Does the endian format of the execution file match the specification of your C Controller module? Section 10.2.3 (3) Section 10.2.3(3) ) Compile the user program and regenerate an execution file according to the C Controller module specifications.
Page 699 Correct the script file in the standard ROM, or correct the user program started from the script file in the standard ROM. Consult your local Mitsubishi service center or representative, explaining the details of the problem. Complete Figure 18.12 Flowchart for disabling script file execution (for the Q06CCPU-V) (continued)
Page 700: When Error Occurred While Downloading User Program Or Executing It With Id Command
TROUBLESHOOTING 18.2.14 When error occurred while downloading user program or executing it with Id command An error occurs if the endian format (memory layout) of the user program is different from that of the C Controller module while: • Downloading the user program to the C Controller module •...
Page 701: When Unable To Read From Or Write To The Specified Device
(8000 ) bytes or more been specified as a size? Is any extended function used? Consult your local Mitsubishi service center Modify the user program so that or representative, explaining the details of the extended functions will be used. problem.
Page 702 TROUBLESHOOTING Memo - 21 18.2 Troubleshooting 18.2.15 When unable to read from or write to the specified device...
Page 703: Actions For Lit/Flashing Err. Led
TROUBLESHOOTING 18.3 Actions for Lit/Flashing ERR. LED If a stop/continue error occurs in the C Controller module, the box for the error item changes from (White) to (Red) in "Error information" on the <<Module information>> tab of the C Controller module setting utility, and an error code is displayed. The following describes how to handle the error when any error item box changes from (White) to (Red) .
Page 704 TROUBLESHOOTING (2) Corrective action and error code obtained by error information check The following describes how to handle an error when the error occurs and the corresponding error item box changed from (White) to (Red) . (a) When multiple kinds of errors occurred Check the information of the first stop/continue error (the error code, present error, date and time) in "System information"...
Page 705 TROUBLESHOOTING Table18.2 Self-diagnostics and error codes (Continued) Error Error item Self-diagnostic item Description code 1310 Intelligent function Intelligent function An intelligent function module error was detected. 1401 module error module error detection 1403 2100 2103 2106 2107 2108 Intelligent function Intelligent function An error occurred during diagnosis of the intelligent 2120...
Page 706 For an error code not referred to the error code table, please consult your local Mitsubishi service center or representative, explaining the details of the problem. (a) Error code list (1000 to 1999). Table18.3 Error codes...
Page 707 CPU module, or base 1412 with the intelligent function module. unit is faulty. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. • Remove the CPU module incompatible with the multiple CPU system from the main base unit, or replace the CPU module with a CPU module compatible with the multiple CPU system.
Page 708 TROUBLESHOOTING Table18.3 Error codes (Continued) LED status Error code Error message Error information CPU operation status ERR. 1414 CONTROL-BUS.ERR. Flashing Stop Module No. 1415 CONTROL-BUS.ERR. Base No. Flashing Stop 1416 CONTROL-BUS.ERR. Flashing Stop Module No. 1500 AC/DC DOWN Continue 1510 SINGLE PS.DOWN Base No./Power supply No.
Page 709 1415 Fault of the main or extension base unit was detected. unit is faulty. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. Reset the CPU module and RUN it again. If the same error is...
Page 710 TROUBLESHOOTING (b) Error Code list (2000 to 2999) Table18.4 Error Codes LED status Error code Error message Error information CPU operation status ERR. 2000 UNIT VERIFY ERR. Off/On Flashing/On Module No. Stop/Continue 2100 SP.UNIT LAY ERR. Flashing Stop Module No. 2103 SP.UNIT LAY ERR.
Page 711 TROUBLESHOOTING Error code Error description and cause Corrective action In a multiple CPU system, a CPU module incompatible with the Replace the CPU module incompatible with the multiple CPU system multiple CPU system is mounted. with a CPU module compatible with the multiple CPU system. •...
Page 712 TROUBLESHOOTING Table18.4 Error codes (Continued) LED status Error code Error message Error information CPU operation status ERR. 2106 SP.UNIT LAY ERR. Flashing Stop Module No. 2107 SP.UNIT LAY ERR. Flashing Stop Module No. 2108 SP.UNIT LAY ERR. Flashing Stop Module No. 2120 SP.UNIT LAY ERR.
Page 713 • The intelligent function module is faulty. Please consult your local 2125 • There was no response form the intelligent function module. Mitsubishi service center or representative, explaining the details of the problem. Take the following actions. In a multiple CPU system, the CPU module configuration is as Refer to Section 13.1 for the CPU module's mounting position in a...
Page 714 TROUBLESHOOTING Table18.4 Error codes (Continued) LED status Error code Error message Error information CPU operation status ERR. 2200 MISSING PARA. Flashing Stop 2502 CAN'T EXE.PRG. Flashing Stop * 1 The error information (module No.) stored in "Event information" on the <<Event history>> tab of the C Controller setting utility is displayed as given below.
Page 715 TROUBLESHOOTING Error code Error description and cause Corrective action 2200 No parameter file has been set. Set the parameter file. On the C Controller setting utility, check the event information of the event No. 0x0000111 that occurred at "MMain", correct/delete the 2502 One command (one line) in the script file has 129 or more characters.
Page 716 TROUBLESHOOTING (c) Error Code list (3000 to 3999) Table18.5 Error codes LED status Error code Error message Error information CPU operation status ERR. 3000 PARAMETER ERROR Flashing Stop Parameter No. 3001 PARAMETER ERROR Flashing Stop Parameter No. 3010 PARAMETER ERROR Flashing Stop Parameter No.
Page 717 • If the same error occurs again, it is thought to be a hardware failure. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. • Read the error information from the C Controller setting utility, check the parameter item corresponding to the numerical value (parameter No.), and correct it if necessary.
Page 718 TROUBLESHOOTING Table18.5 Error codes (Continued) LED status Error code Error message Error information CPU operation status ERR. 3100 LINK PARA.ERROR Flashing Stop Parameter No. * 1 For parameter setting locations indicated by parameter No., refer to the following. Appendix 5 18.3 Actions for Lit/Flashing ERR.
Page 719 I/O No. indicates a hardware fault. Replace the faulty module, or, consult your local Mitsubishi service center or representative, explaining the • Although a CC-Link IE controller network module has been details of the problem.
Page 720 TROUBLESHOOTING Table18.5 Error codes (Continued) LED status Error code Error message Error information CPU operation status ERR. 3101 LINK PARA.ERROR Flashing Stop Parameter No. 3102 LINK PARA.ERROR Flashing Stop Parameter No. 3103 LINK PARA.ERROR Flashing Stop Parameter No. 3104 LINK PARA.ERROR Flashing Stop Parameter No.
Page 721 Please replace the faulty module, or consult your local Mitsubishi service center or representative, explaining the details of the problem. A network parameter error for the CC-Link IE controller network was •...
Page 722 TROUBLESHOOTING (d) Error Code list (5000 to 5999) Table18.6 Error codes LED status Error code Error message Error information CPU operation status ERR. 5000 SYSTEM WDT ERROR Time (set value: ms) Flashing Stop 5001 USER WDT ERROR Time (set value: ms) Flashing Stop Link device refresh cycle...
Page 723 • A task of high CPU utilization rate is running. • Reexamine the user program. • A program that will cause an error in the memory, stack, etc. was • Consult your local Mitsubishi service center or representative, executed. explaining the details of the problem.
Page 724 TROUBLESHOOTING (e) Error Code list (7000 to 10000) Table18.7 Error codes LED status Error code Error message Error information CPU operation status ERR. 7000 MULTI CPU DOWN Flashing Stop Module No. 7002 MULTI CPU DOWN Flashing Stop Module No. 7010 MULTI EXE.ERROR Flashing Stop...
Page 725 • Reset the CPU module and RUN it again. If the same error is displayed again, any of the CPU modules is faulty. Please consult • There is no response from the target CPU module in a multiple CPU your local Mitsubishi service center or representative, explaining the system during initial communication. 7002 details of the problem.
Page 726: Error Code And Error Message Lists
TROUBLESHOOTING 18.4 Error Code and Error Message Lists This section explains the error codes and messages returned at occurrence of errors. 18.4.1 Actions by error codes generated at function execution The error code returned when the bus interface function or MELSEC data link function is executed is returned unchanged as a return value.
Page 727 TROUBLESHOOTING Table18.8 Common error codes returned by bus interface functions and MELSEC data link functions (Continued) Return value Error description Corrective action (HEX) Retry. Check if the operating system is running Transmission error normally. (0x66) Transmitting data has failed. Reboot the operating system. Retry.
Page 728 TROUBLESHOOTING Table18.8 Common error codes returned by bus interface functions and MELSEC data link functions (Continued) Return value Error description Corrective action (HEX) Check the communications path/target that Unsupported communications path error 19203 supports the request. The request cannot be executed via the specified (0x4B03) Do not issue a request that generated an error to communications path/target.
Page 729 TROUBLESHOOTING Table18.8 Common error codes returned by bus interface functions and MELSEC data link functions (Continued) Return value Error description Corrective action (HEX) Target station No. error Check the target station No. -2174 The station No. specified for processing the request is the own When sending a request to the own station, (0xF782) station No.
Page 730 TROUBLESHOOTING Table18.8 Common error codes returned by bus interface functions and MELSEC data link functions (Continued) Return value Error description Corrective action (HEX) Check the version to see if the target module Function unsupported error supports the block data assurance per station Processing was executed for the module that does not support the function.
Page 731 TROUBLESHOOTING Table18.8 Common error codes returned by bus interface functions and MELSEC data link functions (Continued) Return value Error description Corrective action (HEX) -28638 Multiple CPU unsupported operation error Reset CPU 1. (0x9022) STOP/PAUSE error Output data was written to output module when the CPU operating -28640 status is STOP/PAUSE.
Page 732 TROUBLESHOOTING (2) Error codes returned by bus interface functions The following provides the error descriptions and corrective actions corresponding to individual error codes returned when the bus interface functions are executed. Refer to this section (1) for the common error codes returned by bus interface functions and MELSEC data link functions.
Page 733 TROUBLESHOOTING Table18.9 Error codes returned by bus interface functions (Continued) Return value Error description Corrective action (HEX) Allow “Remote reset” in the system settings for the bus master CPU (CPU 1). -222 Bus master CPU reset error Change the status of the bus master CPU (0xFF22) Remote reset for the bus master CPU (CPU 1) has failed.
Page 734 TROUBLESHOOTING Table18.9 Error codes returned by bus interface functions (Continued) Return value Error description Corrective action (HEX) -242 Synchronization type error Check the specified synchronization type. (0xFF0E) The specified synchronization type is out of range. -243 SRAM size error Check the specified size. (0xFF0D) The specified offset plus size is out of range.
Page 735 TROUBLESHOOTING (3) Error codes returned by MELSEC data link functions The following provides the error descriptions and corrective actions corresponding to individual error codes returned when the MELSEC data link functions are executed. Refer to this section (1) for the common error codes returned by bus interface functions and MELSEC data link functions.
Page 736 TROUBLESHOOTING Table18.10 Error codes returned by MELSEC data link functions (Continued) Return value Error description Corrective action (HEX) Retry. There may be a possibility of insufficient memory. Another task/thread is occupying the resource and the resource is Terminate other task(s) currently (0xFFE0) not released within 30 seconds.
Page 737: Actions By Event No
TROUBLESHOOTING 18.4.2 Actions by Event No. Figure 18.18 Event history The data in the following table are stored into the "Source" on the <<Event history>> tab of the C Controller utility. Table18.11 Data stored into event history Occurrence Reference Source Data type flag section...
Page 738 TROUBLESHOOTING When the event type is "System", a 2-word value defined as shown below is stored into the "Event No." on the <<Event history>> tab of the C Controller setting utility. Bit 31 16 15 Bit 0 Upper word Lower word Event No.
Page 739 TROUBLESHOOTING (1) Corrective actions for "MQbfDrv" events by event Nos. Corrective actions for events that may occur in "MQbfDrv" are listed below by event Nos. The fixed value, 49152 (0xC000) is stored into the upper word part of the event No. Table18.12 Corrective actions for "MQbfDrv"...
Page 740 Check 0xC0000001 An exceptional error occurred. Tornado operation method as well. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. (3) Corrective actions for "MUtllfQbf" events by event Nos.
Page 741 Check the utility and C Controller module 0xC0000001 An instruction error occurred. versions. Restart the C Controller module. Please consult your local Mitsubishi service 0xC0000002 A socket generation error occurred. center or representative, explaining the details of the problem. A port acquisition error occurred.
Page 742 Check the utility and C Controller module 0xC0000001 An instruction error occurred. versions. Restart the C Controller module. Please consult your local Mitsubishi service 0xC0000002 A socket generation error occurred. center or representative, explaining the details of the problem. Check the port No. used.
Page 743 A system error in the C Controller module is probable. 0xC0000401 Usage of the buttery backup RAM exceeded the capacity. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. Write the file again if it was not written normally.
Page 744 A system error in the C Controller module is probable. 0xC0000200 An initialization parameter error occurred. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. A system error in the C Controller module is probable.
Page 745: Actions By Error Messages
TROUBLESHOOTING 18.4.3 Actions by error messages If an error has occurred on each utility, the corresponding error message is displayed. This section explains the corrective actions by error messages. Refer to Section 18.4.1 for the errors whose error codes are displayed. (1) Error messages on C Controller setting utility The following indicates the error messages displayed on the C Controller setting utility and their corrective actions.
Page 746 TROUBLESHOOTING Table18.21 Error messages on C Controller setting utility (Continued) Index Error message Corrective action Failed to allocate memory. Check if there is sufficient free space in the memory. • Check if the target C Controller module is operating. Failed to change IP address settings of C Controller module. •...
Page 747 TROUBLESHOOTING Table18.21 Error messages on C Controller setting utility (Continued) Index Error message Corrective action Failed to save the event log file. Check the free space of the destination to save. • Check the free space of the destination to save. Failed to save the parameter file.
Page 748 TROUBLESHOOTING Table18.21 Error messages on C Controller setting utility (Continued) Index Error message Corrective action Press the Update button to read the event history. No event history data to be saved. In the absence of data, the event history cannot be saved. Number of interrupt events has not been set.
Page 749 TROUBLESHOOTING Table18.21 Error messages on C Controller setting utility (Continued) Index Error message Corrective action The default gateway address setting is out of range. Make the default gateway setting within the allowable range. Check the address range and set it again. The MD function timeout value is out of range.
Page 750 TROUBLESHOOTING Table18.21 Error messages on C Controller setting utility (Continued) Index Error message Corrective action Check if the target C Controller module is used in a multiple CPU The target CPU does not exist. configuration, and change the target CPU of communication CPU numbers may exceed the set number of the multiple CPUs.
Page 751 TROUBLESHOOTING (2) Error messages on CC-Link utility The following indicates the error messages displayed on the CC-Link utility and their corrective actions. Table18.22 Error messages on CC-Link utility Index Error message Corrective action Check the error details, referring to the following manuals. A communication error occurred with C Controller module.
Page 752 TROUBLESHOOTING Table18.22 Error messages on CC-Link utility (Continued) Index Error message Corrective action Failed to read parameters. The probable causes are: Set the CC-Link parameters, and write them to the C Controller • CC-Link parameters have not been set. module. •...
Page 753 TROUBLESHOOTING Table18.22 Error messages on CC-Link utility (Continued) Index Error message Corrective action Number of occupied stations has not been set for all of the Set the occupied station count for the number of connected connected modules. modules set in the Station information settings. Set the number of occupied stations for each of the modules.
Page 754 TROUBLESHOOTING Table18.22 Error messages on CC-Link utility (Continued) Index Error message Corrective action Conduct a communication test after checking the following. • Check if the target C Controller module is operating. • Check if the Ethernet cable is connected. The specified connection target was not found in the •...
Page 755 TROUBLESHOOTING (3) Error messages on MELSECNET/H utility The following indicates the error messages displayed on the MELSECNET/H utility and their corrective actions. Table18.23 Error messages on MELSECNET/H utility Index Error message Corrective action Take corrective actions according to the error code. ( Error A communication error occurred with C Controller module.
Page 756 TROUBLESHOOTING Table18.23 Error messages on MELSECNET/H utility (Continued) Index Error message Corrective action Check the free space of the destination to save. Failed to save the parameter file. Check the media of the destination to save. Confirm save location. Set the total of the saving location and file names using 128 characters or less.
Page 757 TROUBLESHOOTING Table18.23 Error messages on MELSECNET/H utility (Continued) Index Error message Corrective action M station to L station setting in the LX/LY setting 1 is Correct the setting so that data of the L station to M station overlapping. settings in LX/LY setting 1 are not duplicated. Correct these settings.
Page 758 TROUBLESHOOTING Table18.23 Error messages on MELSECNET/H utility (Continued) Index Error message Corrective action Relay network No. is out of range. Set the relay network No. within the range of 1 to 239. Set it within the range of 1 to 239. Relay station No.
Page 759 TROUBLESHOOTING Table18.23 Error messages on MELSECNET/H utility (Continued) Index Error message Corrective action Transfer target network No. is out of range. Set the transfer destination network No. within the range of 1 to Set it within the range of 1 to 239. 239.
Page 760 TROUBLESHOOTING (4) Error messages on CC IE Control utility The following indicates the error messages displayed on the CC IE Control utility and their corrective actions. Table18.24 Error messages on CC IE Control utility Index Error message Corrective action \ is continuously used in the directory. Do not use \ continuously. Do not use \ continuously. A communication error occurred with C Controller module.
Page 761 TROUBLESHOOTING Table18.24 Error messages on CC IE Control utility (Continued) Index Error message Corrective action Constant link scan setting is out of range. Set a constant link scan value within the range of 1 to 500, or Set it within the range of 1 to 500. leave it blank.
Page 762 TROUBLESHOOTING Table18.24 Error messages on CC IE Control utility (Continued) Index Error message Corrective action Correct the network parameters. Restart the CC IE Control utility. Failed to obtain the station type of the connected station. Since installation of SW PVC-CCPU may have failed, reinstall Since installation of SW PVC-CCPU may have failed, reinstall Failed to open Help file.
Page 763 TROUBLESHOOTING Table18.24 Error messages on CC IE Control utility (Continued) Index Error message Corrective action L station to M station setting in the LX/LY setting 1 is Eliminate overlap in "M station to L station" settings in LX/LY overlapping. setting 1. Correct these settings.
Page 764 TROUBLESHOOTING Table18.24 Error messages on CC IE Control utility (Continued) Index Error message Corrective action Number of assigned points in the equal assignment settings is out of range. Set points for the equal assignment within the range of XX to YY. Set it within the range of XX to YY.
Page 765 TROUBLESHOOTING Table18.24 Error messages on CC IE Control utility (Continued) Index Error message Corrective action The number of LB points per station exceeds 16384. At least one station has LB points that exceeds 16384. Change Set it within 16384 points. the set value to 16384 or less.
Page 766 TROUBLESHOOTING Table18.24 Error messages on CC IE Control utility (Continued) Index Error message Corrective action Verify the user name and password, and reconnect. Unable to obtain the write authority. Section 5.11.2) Verify the user name and password. Connect without the write authority. Check the specified file.
Page 767 TROUBLESHOOTING (5) Error messages on Device monitoring utility The following indicates the error messages displayed on the Device monitoring utility and their corrective actions. Table18.25 Error messages on Device monitoring utility Index Error message Corrective action Retry (e.g. Start monitoring, Connection settings) after checking the following.
Page 768 TROUBLESHOOTING Table18.25 Error messages on Device monitoring utility (Continued) Index Error message Corrective action OCT input range error. Enter an octal number of 0 to 7. Enter 0 to 7. Points data have not been entered. Enter the number of points. Setting data have not been entered.
Page 769: Hardware Self-Diagnostic Function
TROUBLESHOOTING 18.5 Hardware Self-diagnostic Function (1) Hardware self-diagnostics function The hardware self-diagnostics function allows the hardware check of the C Controller module. When the C Controller module is started up in the hardware self-diagnostic mode, the following hardware self-diagnostic tests can be executed. ( This section (3)) Table18.26 Hardware self-diagnostics function Mode...
Page 770 TROUBLESHOOTING (c) Preparations necessary for each mode Make the following preparations. 1) When executing Mode 1 Disconnect the cable, if any, from CH1. 2) When executing Mode 2 For the Q06CCPU-V, install a CompactFlash card into the CompactFlash card slot. ( Section 5.8.1 (1)) For the Q06CCPU-V-B, nothing needs to be done.
Page 771 TROUBLESHOOTING (c) Switching the mode Set the RUN/STOP/MODE switch to "STOP", and move the RESET/SELECT switch to "SELECT" to select a desired mode. • Mode 1 : Move the RESET/SELECT switch to "SELECT" once. The "RUN LED" turns on. • Mode 2 : Move the RESET/SELECT switch to "SELECT"...
Page 772 TROUBLESHOOTING (4) Execution of hardware self-diagnostic tests POINT During a hardware self-diagnostic test, do not power off the C Controller system or reset the C Controller module. Doing so may disable normal startup of the C Controller module. Set the RUN/STOP/MODE switch from "STOP" to "RUN" to execute a hardware self- diagnostic test.
Page 773 TROUBLESHOOTING (5) Confirming hardware self-diagnostic test result (a) Normal completion 1) The LED that was flashing during the self-diagnostic test turns off. MODE CF CARD ERR. CH2 SD/RD USER Figure 18.22 LED status after normal completion (for the Q06CCPU-V) 2) Switch the power off to terminate the hardware self-diagnostics mode. Remark When the standard ROM format setting is made, the standard ROM is formatted during the next startup of the C Controller module.
Page 774 TROUBLESHOOTING (b) Abnormal termination Upon error detection during the self-diagnostic test, the "ERR. LED" flashes, and the LED corresponding to the self-diagnostic test turns on. Upon abnormal termination, the self-diagnostic test ends with no more test being conducted. Table18.29 LED status at abnormal termination (error detection) (for the Q06CCPU-V) Error detection LED indication MODE...
Page 775 In the case of abnormal termination, perform the hardware self-diagnostic test again. If the error recurs, a possible cause is a hardware fault of the C Controller module. Please consult your local Mitsubishi representative, explaining the details of the problem. 18.5 Hardware Self-diagnostic Function - 94...
Page 776: Diagnostics And Restoration Of Standard Rom And Compactflash Card Drives
Section 5.10 (4)) If the file system is not restored or if the standard ROM drive cannot be formatted by either of the above methods, please consult your local Mitsubishi service center or representative, explaining the details of the problem.
Page 777 TROUBLESHOOTING (3) chkdsk command The following describes the "chkdsk" command of VxWorks. (a) Format of chkdsk command chkdsk, "Device name", Flag Table18.30 Input values and settings of chkdsk command Argument Input value Setting /ROM Standard ROM Device name CompactFlash card (the Q06CCPU-V only) Diagnostics Flag...
Page 778 TROUBLESHOOTING 2) The following screen appears if it is terminated normally. Figure 18.24 Execution result of chkdsk command (Normal termination) Remark Refer to the VxWorks Manual for details. - 97 18.6 Diagnostics and Restoration of Standard ROM and CompactFlash Card Drives...
Page 779: Appendices
APPENDICES APPENDICES Appendix 1 Function Processing Time This chapter describes the time required for processing functions when a single user program using the bus interface functions or MELSEC data link functions (Q06CCPU-V only) is executed with setting 100 as the task priority. POINT The processing times of the bus interface functions and MELSEC data link functions (Q06CCPU-V only) vary in some degree depending on the operation...
Page 780 APPENDICES (b) Buffer memory access time 1) In case of accessing the QJ61BT11N (Start I/O No: 0) where the data consistency verification per station function is set to be disabled in the CC-Link utility in a single CPU system configuration Table App.3 Access time Communication size Function name...
Page 781 APPENDICES 4) When accessing the CPU shared memory of the host CPU in a multiple CPU system (CPU No.1: Q25HCPU, CPU No.2: Q06CCPU-V) Table App.7 Access time Communication size Function name 1 word 64 words 512 words QBF_FromBuf 13 s 20 s 73 s QBF_ToBuf...
Page 782 APPENDICES (b) Buffer memory access time 1) In case of accessing the QJ61BT11N (Start I/O No: 0) where the data consistency verification per station function is set to be disabled in the CC-Link utility in a single CPU system configuration Table App.11 Access time Communication size Function name...
Page 783 APPENDICES 4) When accessing the CPU shared memory of the host CPU in a multiple CPU system (CPU No.1: Q25HCPU, CPU No.2: Q06CCPU-V-B) Table App.15 Access time Communication size Function name 1 word 64 words 512 words QBF_FromBuf 13 s 26 s 125 s QBF_ToBuf...
Page 784: Appendix 2 External Dimensions
APPENDICES Appendix 2 External Dimensions Appendix 2.1 Q06CCPU-V 27.4 (1.08) 89.3 (3.52) (0.21) STOP MODE RESET SEL. Cable's outside diameter 4+10 (Unit: mm (in.)) Figure App.1 External dimensions * 1 The bending radius near the connectors (reference value: R1) should be four times as long as the cable's outside diameter or more when connecting the twisted pair cable.
Page 785: Appendix 2.2 Q06Ccpu-V-B
APPENDICES Appendix 2.2 Q06CCPU-V-B 27.4(1.08) 89.3(3.52) (0.21) STOP MODE RESET SEL. Cable's outside diameter 4 10 (Unit: mm (in.)) Figure App.2 External dimensions * 1 The bending radius near the connectors (reference value: R1) should be four times as long as the cable's outside diameter or more when connecting the twisted pair cable.
Page 786: Appendix 3 Transportation Precautions
APPENDICES Appendix 3 Transportation Precautions When transporting lithium batteries, be sure to treat them based on the transportation regulations. Appendix 3.1 Applicable model The lithium battery used for the C Controller module is classified as shown in the table below. Table App.17 Model subject to transportation regulations Model Product name...
Page 787: Appendix 4 Handling Of Batteries And Devices With Built-In Batteries In Eu Member States
The symbol shown in Figure App.3 is printed on the batteries and packaging of batteries and devices with built-in batteries used for Mitsubishi programmable controllers. Figure App.3 Symbol Note: This symbol is for EU member states only.
Page 788: Appendix 4.2 Exportation Precautions
September 26, 2008 or later, provide the latest manuals that include the explanation of the symbol. If no Mitsubishi manuals or any old manuals without the explanation of the symbol are provided, separately attach an explanatory note regarding the symbol to each manual of the devices.
Page 789: Appendix 5 Characters Usable For User Name And Password
APPENDICES Appendix 5 Characters Usable for User Name and Password This section explains the characters applicable to user names and passwords set on each utility. (1) Characters applicable to user names Alphanumeric characters are usable. However, a space, ", and : are not applicable. The following ASCII code table shows applicable characters.
Page 790 APPENDICES (2) Characters applicable to passwords Alphanumeric characters are usable. However, a space, ", and @ are not applicable. The following ASCII code table shows applicable characters. Table App.19 Characters applicable to passwords Higher 4 bits Applicable Not applicable - 12 Appendix 5 Characters Usable for User Name and Password...
Page 791: Appendix 6 Parameter No. List
APPENDICES Appendix 6 Parameter No. List Parameter No. is displayed in Detailed event information screen of C Controller setting utility when an error ( Section 18.3) occurs in parameter settings. This appendix describes the correspondence of a parameter No. to a parameter setting locations.
Page 792 APPENDICES (2) Parameter No. List The following table shows the correspondence of a parameter No. to a parameter setting locations. Table App.23 Parameter No. List Parameter No. Item Utility name 0000 Label 0001 Comment Type Model name 0400 I/O assignment C Controller setting utility Points StartX/Y(Start I/O No.)
Page 793 APPENDICES Table App.23 Parameter No. List (Continued) Parameter No. Item Utility name Low speed 1000 Timer limit setting High speed 1001 RUN-PAUSE contacts PAUSE 1002 Remote reset C Controller setting utility 1003 Output mode at STOP to RUN C Controller setting utility 1004 Floating point arithmetic processing 1005...
Page 794 APPENDICES Table App.23 Parameter No. List (Continued) Parameter No. Item Utility name System WDT setting C Controller setting utility 3000 WDT (Watchdog timer) setting Initial execution monitoring time Low speed execution monitoring time Battery check 3001 Error check Fuse blown check C Controller setting utility Module verification Computation error...
Page 795 APPENDICES Table App.23 Parameter No. List (Continued) Parameter No. Item Utility name Program Clear program memory 7000 Boot option Auto Download all Data from Memory card to Standard ROM Boot file setting 8002 SFC program start mode 8003 Start conditions 8006 Output mode when the block is stopped 9000...
Page 796 APPENDICES Table App.23 Parameter No. List (Continued) Parameter No. Item Utility name C000 Number of modules CC-Link utility Remote input (RX) Remote output (RY) Remote register (RWr) Remote register (RWw) Ver.2 Remote input (RX) CNM1 Ver.2 Remote output (RY) Ver.2 Remote register (RWr) Ver.2 Remote register (RWw) Special relay (SB) Special register (SW)
Page 797 APPENDICES Appendix 7 VxWorks Component List This section describes the components that the C Controller module has and the method for checking the information of components. (1) VxWorks component list The C Controller module has the following components. Table App.24 VxWorks component list Component Macro ANSI assert...
Page 798 APPENDICES Table App.24 VxWorks component list (Continued) Component Macro DOS File System Volume Formatter INCLUDE_DOSFS_FMT DOSFS2 File System Primary Module INCLUDE_DOSFS_MAIN doubly linked lists INCLUDE_DLL enable caches INCLUDE_CACHE_ENABLE END attach interface INCLUDE_END_BOOT END interface support INCLUDE_END environment variables INCLUDE_ENV_VARS exception handling INCLUDE_EXC_HANDLING exception task INCLUDE_EXC_TASK...
Page 799 APPENDICES Table App.24 VxWorks component list (Continued) Component Macro POSIX ftruncate INCLUDE_POSIX_FTRUNC POSIX message queues INCLUDE_POSIX_MQ POSIX mman INCLUDE_POSIX_MEM POSIX scheduler INCLUDE_POSIX_SCHED POSIX semaphores INCLUDE_POSIX_SEM POSIX signals INCLUDE_POSIX_SIGNALS POSIX timers INCLUDE_POSIX_TIMERS RAM disk driver INCLUDE_RAMDRV rBuff library INCLUDE_RBUFF read the bootline INCLUDE_BOOT_LINE_INIT Remote Procedure Call system INCLUDE_RPC...
Page 800 APPENDICES Table App.24 VxWorks component list (Continued) Component Macro WDB exception notification INCLUDE_WDB_EXC_NOTIFY WDB gopher INCLUDE_WDB_GOPHER WDB hardware fpp support INCLUDE_WDB_HW_FP WDB memory access INCLUDE_WDB_MEM WDB register access INCLUDE_WDB_REG WDB system agent hardware fpp support INCLUDE_WDB_SYS_HW_FP WDB system debugging INCLUDE_WDB_SYS WDB target server file system INCLUDE_WDB_TSFS WDB task breakpoints...
Page 801 APPENDICES (2) Method for checking VxWorks component information The information of VxWorks components can be checked by the following procedures. The following shows the procedures for checking the information of VxWorks components. VxWorks image cannot be created (changed). 1) Select [File] [New Project] from menu bar.
Page 802: Appendix 7 Vxworks Component List
APPENDICES (From previous page) 5) Check that "Workspace", "Project", and "Basis BSP" are correct, and click the button. Finish 6) Open the <<VxWorks>> tab of "Workspace" window. (To next page) - 24 Appendix 7 VxWorks Component List...
Page 803 APPENDICES (From previous page) 7) Click the icon ( ) to display the items in the low order. 8) Right click on "ANSI assert" and select [Properties] from the menu. (To next page) Appendix 7 VxWorks Component List - 25...
Page 804 APPENDICES (From previous page) 9) Check the information of VxWorks components with the Properties screen displayed. (Completed) Remark The components of VxWorks can be searched by the following procedures. 1) Right click to select [Find Object] from the menu. 2) Click the Find button. - 26 Appendix 7 VxWorks Component List...
Page 805: Appendix 8 Difference Between C Controller Module And Q06Ccpu-V-H01
APPENDICES Appendix 8 Difference between C Controller Module and Q06CCPU- V-H01 This section describes the difference between the C Controller module and the Q06CCPU-V-H01. Appendix 8.1 Performance specifications The following describes the comparison of the specifications between the Q06CCPU-V and the Q06CCPU-V-H01. The performance specifications of the Q06CCPU-V is the same as that of the Q06CCPU- V-H01, except for the following.
Page 806: Appendix 8.3 Precautions For Replacing Systems
APPENDICES Appendix 8.3 Precautions for replacing systems The following describes the precautions for replacing the Q06CCPU-V-H01 with the Q06CCPU-V. (1) Connection equipment The Q06CCPU-V can use the connection equipment such as a CompactFlash card which was used in the Q06CCPU-V-H01. ( Section 2.4) (2) Combination of software package and C Controller module Table App.28 Combination of software package and C Controller module...
Page 807: Appendix 9 Comparison
APPENDICES Appendix 9 Comparison The C Controller module and SW PVC-CCPU have been upgraded, offering new additional functions and specification change. This section shows their functional comparisons between versions. Table App.29 Functional upgrade of C Controller module and SW PVC-CCPU Software version of First 5 digits of serial No.
Page 808 INDEX Operating Target settings screen ..9-80 Operating Test screen....9-84 Accessible ranges and devices of MELSEC data link Channels.
Page 809 File operation......7-4 Operating Parameter settings screen ..9-119 Formatting the standard ROM .
Page 810 Setting Number of CPUs ....15-4 Settings and procedures before operation ..5-11 Shell display setting ..... 10-25 Software version .
Page 811 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 dealer or Mitsubishi Service Company.
Page 812 Microsoft, Windows, Windows NT are registered trademarks of Microsoft Corporation in the United States and other countries. Pentium and Celeron are trademarks of Intel Corporation in the United States and other countries. Ethernet is a trademark of Xerox Corporation. CompactFlash is a trademark of SanDisk Corporation. VxWorks, Tornado, WindPower, WindSh and WindView are registered trademarks of Wind River Systems, Inc.

This manual is also suitable for:

Melsec q06ccpu-v Melsec q06ccpu-v-b Melsec sw3pvc-ccpu-e

Mitsubishi MELSEC-Q Series User Manual

Chapter1 Overview

Chapter2 System Configuration

Chapter3 Specifications

Chapter4 Functions

Chapter5 Settings And Procedures before Operation

Chapter6 I/O Number Assignment

Chapter7 Memories And Files Handled by Ccontroller Module

Chapter8 Installing And Uninstalling Sw[]Pvc-Ccpu

Chapter9 Utility Operation

Chapter10 Functions And Programming

Chapter11 Overview Of Multiple Cpu System

Chapter12 Multiple Cpu System Configuration

Chapter13 Multiple Cpu System Concept

Chapter14 Communications Between Cpu Modules

Chapter15 Parameters Added for Multiple Cpu System

CHAPTER16 PRECAUTIONS FOR USE of Ans SERIES MODULE

Chapter17 Starting Multiple Cpu System

Chapter18 Troubleshooting

Appendix 1 Function Processing Time

Appendix 2 External Dimensions

Appendix 2.1 Q06CCPU-V

Appendix 2.2 Q06CCPU-V-B

Appendix 3 Transportation Precautions

Appendix 3.1 Applicable Model

Appendix 3.2 Transportation Guidelines

Appendix 4 Handling of Batteries and Devices with Built-In Batteries in EU Member States

Appendix 4.1 Disposal Precautions

Appendix 4.2 Exportation Precautions

Appendix 5 Characters Usable for User Name and Password

Appendix 6 Parameter No. List

Appendix 7 Vxworks Component List

Quick Links

Related Manuals for Mitsubishi MELSEC-Q Series

Summary of Contents for Mitsubishi MELSEC-Q Series