Page 1 C Controller Module User's Manual (Hardware Design, Function Explanation) -Q12DCCPU-V(Basic mode) -Q06CCPU-V -Q06CCPU-V-B -SW3PVC-CCPU-E...
Page 3 SAFETY PRECAUTIONS (Read these precautions before using this product.) Before using this product, please read this manual and the relevant manuals carefully and pay full attention to safety to handle the product correctly. The precautions given in this manual are concerned with this product only. For the safety precautions of the programmable controller system, refer to the user's manual for the CPU module used.
Page 4 [Design Precautions] WARNING (3) Outputs may remain on or off due to a failure of an output module relay or transistor. Configure an external circuit for monitoring output signals that could cause a serious accident. In an output module, when a load current exceeding the rated current or an overcurrent caused by a load short-circuit flows for a long time, it may cause smoke and fire.
Page 5 [Design Precautions] CAUTION Do not install the control lines or communication cables together with the main circuit lines or power cables. Keep a distance of 100mm (3.94 inches) or more between them. Failure to do so may result in malfunction due to noise. When a device such as a lamp, heater, or solenoid valve is controlled through an output module, a large current (approximately ten times greater than normal) may flow when the output is turned from off to on.
Page 6 [Installation Precautions] CAUTION When using an extension cable, connect it to the connector of the base unit or module securely. Check the connection for looseness. Poor contact may cause incorrect input or output. When using a CompactFlash card, fully insert it into the CompactFlash card slot. Check that it is inserted completely.
Page 7 [Wiring Precautions] CAUTION Ground the FG and LG terminals to the protective ground conductor dedicated to the programmable controller. Failure to do so may result in electric shock or malfunction. Prevent foreign matter such as dust or wire chips from entering the module. Such foreign matter can cause a fire, failure, or malfunction.
Page 8 [Startup and Maintenance Precautions] WARNING Do not touch any terminal while power is on. Doing so will cause electric shock. Correctly connect the battery connector. Do not charge, disassemble, heat, short-circuit, solder, or throw the battery into the fire. Doing so will cause the battery to produce heat, explode, or ignite, resulting in injury and fire. Shut off the external power supply for the system in all phases before cleaning the module or retightening the terminal screws or module fixing screws.
Page 9 [Startup and Maintenance Precautions] CAUTION Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire. Before performing online operations (especially, program modification, forced output, and operation status change) for the running C Controller module from the peripheral connected, read relevant manuals carefully and ensure 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 countries, refer to Appendix 4.) [Transportation Precautions] CAUTION When transporting lithium batteries, follow the transportation regulations.
Page 11 CONDITIONS OF USE FOR THE PRODUCT (1) Mitsubishi C Controller system ("the PRODUCT") shall be used in conditions; i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident; and ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the case of any problem, fault or failure occurring in the PRODUCT.
Page 12 REVISIONS *The manual number is given on the bottom left of the back cover. Print date *Manual number Revision Jun., 2009 SH(NA)-080766ENG-A First edition Jan., 2010 SH(NA)-080766ENG-B Partial correction PRECAUTIONS Aug., 2010 SH(NA)-080766ENG-C Partial correction SAFETY PRECAUTIONS, ABOUT MANUALS, HOW TO USE THIS MANUAL, GENERIC TERMS AND ABBREVIATIONS, GLOSSARY, Section 1.1, 2.1.3, 2.1.4, 2.2.1, 2.2.2, 2.3, 2.4, 3.2, 3.4.2, 4.1, 4.4, 4.5, 4.13, 5.2 to 5.4, 6.2, 6.11.2, 8.1.1, 8.2.2, 10.1, 11.1.4, 11.3, 13.1, 13.2, 13.6, 14.1, 15.2.4, 16.3, 16.4.1,...
Page 13 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 14 OPERATING PRECAUTIONS This section provides the following precautions. Precautions for Refer to System configurations Page A-12 Standard RAM, standard ROM, and CompactFlash card Page A-13 Battery Page A-15 Clock setting Page A-16 Starting the C Controller module Page A-16 Network configurations Page A-17 Relation between system tasks and the system watchdog timer, user Page A-17...
Page 15 (2) Precautions for standard RAM, standard ROM, and CompactFlash card Table A.1 Memory availability Availability Memory Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Standard RAM Standard ROM CompactFlash card : Available, : N/A (a) Standard RAM formatting 1) When formatting the standard RAM Be sure to perform the method described in the following section.
Page 16 (d) Allowable number of writes to a CompactFlash card (service life) • For the live of the QD81MEM and GT05-MEM, refer to the following. Page 6-70, Section 6.8.5 • For the live of commercially available CompactFlash cards, refer to the specifications of each product.
Page 17 (3) Precautions for battery (a) For the Q12DCCPU-V 1) About file corruption The battery must be installed before operation. • If the C Controller system is operated without a battery and then is powered off or reset The data in the standard RAM and battery-backed-up RAM may be damaged, or a file system error may occur.
Page 18 Changing "Priority" to a larger value in the Option tab of C Controller setting utility increases the time after which the C Controller module can be connected. (b) Flashing "01" or "02" of the 7-segment LED (Q12DCCPU-V only) At start-up of the C Controller module, "01" or "02" flashes on the 7-segment LED in the following cases.
Page 19 (6) Precautions for network configurations (a) Precautions for using two Ethernet channels (Q12DCCPU-V only) When using two channels as Ethernet ports, two different network addresses must be set for CH1 and CH2 of the C Controller module. In the above case, a response to the message received through each channel is sent as follows: •...
Page 20 INTRODUCTION Thank you for purchasing the Mitsubishi C Controller module. Before using the product, please read this manual carefully to understand the features and performance of the C Controller module and use it correctly. CONTENTS SAFETY PRECAUTIONS············································································································ A - 1 CONDITIONS OF USE FOR THE PRODUCT ·················································································...
Page 21 Performance Specifications ···························································································3 - 2 RS-232 Connector Specifications····················································································3 - 4 3.3.1 RS-232 connector specifications for the Q12DCCPU-V ·················································3 - 4 3.3.2 RS-232 connector specifications for the Q06CCPU-V(-B)···············································3 - 5 Operation Processing ···································································································3 - 6 3.4.1 Initial processing····································································································3 - 6 3.4.2 I/O access timing ···································································································3 - 7...
Page 22 Fail-Safe Circuit ·········································································································· 6 - 4 Preparatory Procedure and Setting ················································································6 - 11 Part Names and Functions···························································································6 - 24 6.4.1 Part names and functions of the Q12DCCPU-V··························································6 - 24 6.4.2 Part names and functions of the Q06CCPU-V(-B) ·······················································6 - 31 Cable Connection ······································································································6 - 37 6.5.1...
Page 23 What is I/O Number? ·································································································· 7 - 13 I/O Number Assignment ······························································································ 7 - 14 7.5.1 I/O numbers of a base unit····················································································· 7 - 14 I/O Assignment by C Controller Setting Utility ·································································· 7 - 17 7.6.1 Purposes of I/O assignment by C Controller setting utility············································· 7 - 17 7.6.2 Details of I/O assignment by C Controller setting utility ················································...
Page 24 11.2.1 Applicable CPU modules ····················································································· 11 - 11 11.2.2 Precautions for using I/O modules and intelligent function modules ······························ 11 - 13 11.3 Precautions for System Configuration··········································································· 11 - 14 CHAPTER 12 CONCEPT OF MULTIPLE CPU SYSTEM 12 - 1 to 12 - 24 12.1 Mounting Positions of CPU Modules ··············································································12 - 1 12.2...
Page 25 Error codes and actions (for errors occurred in communication)··································· 16 - 73 16.5 Hardware Self-Diagnostic Function·············································································· 16 - 75 16.5.1 Hardware self-diagnostic test and initialization setting of the Q12DCCPU-V ··················· 16 - 75 16.5.2 Hardware self-diagnostic test and initialization setting of the Q06CCPU-V(-B) ················ 16 - 84 16.6 Diagnostics and Restoration of the Standard RAM, Standard ROM, and CompactFlash Card Drives ···················································································································...
Page 26 Appendix 2.3 Q06CCPU-V-B ····················································································· APPX - 9 Appendix 3 Transportation Precautions ·········································································· APPX - 10 Appendix 3.1 Regulated models ··············································································· APPX - 10 Appendix 3.2 Handling for transportation···································································· APPX - 10 Appendix 4 Handling of Batteries and Devices with Built-in Batteries in EU Member States ······ APPX - 11 Appendix 4.1 Disposal precautions ···········································································...
Page 27 Describes the system configuration, specifications, functions, handling methods, wiring, SH-081130ENG troubleshooting, and programming and function of C Controller module (Q24DHCCPU-V, (13JZ75) Q24DHCCPU-VG, Q24DHCCPU-LS, Q26DHCCPU-LS, and Q12DCCPU-V (Extended mode)). (Sold separately) Setting/Monitoring Tools for the C Controller Module Version 4 Operating Manual SH-081131ENG...
Page 28 ACCESS VIA NETWORK MODULES 5.4.4 Link device refresh setting Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Link device refresh setting is required when using the internal buffer access in user programs. To enable the link device refresh, set a link device refresh cycle and refresh parameters in CC IE Control utility.
Page 29 HOW TO USE THIS MANUAL This manual is intended to help you understand the system configurations, specifications, functions, preparatory procedures, and troubleshooting of the C Controller module. Utilize this manual, referring to the following. Item Description CHAPTER 1 Describes the features of the C Controller module. Describes system configurations that include the C Controller module, and CHAPTER 2 provides a list of the modules that are accessible from the C Controller...
Page 30 In principle, 'Q12DCCPU-V' indicates Q12DCCPU-V (Basic mode). Q12DCCPU-V When the classification is needed for such as comparison with other modules, 'Q12DCCPU-V (Basic mode)' and ‘Q12DCCPU-V (Extended mode)’ are mentioned. Q12DCCPU-V Status that Q12DCCPU-V is initialized with the basic mode (Basic mode)
Page 31 (2) CPU modules Generic term/abbreviation Description Generic term for the Q2ACPU, Q2ACPU-S1, Q2ASCPU, Q2ASCPU-S1, Q2ASHCPU, QnACPU Q2ASHCPU-S1, Q3ACPU, Q4ACPU, and Q4ARCPU Basic model QCPU Generic term for the Q00CPU and Q01CPU High Performance model QCPU Generic term for the Q02CPU, Q02HCPU, Q06HCPU, Q12HCPU, and Q25HCPU Process CPU Generic term for the Q02PHCPU, Q06PHCPU, Q12PHCPU, and Q25PHCPU Redundant CPU...
Page 32 (3) Network modules and PC boards Generic term/abbreviation Description CC-Link module Generic term for the QJ61BT11 and QJ61BT11N CC-Link/LT module Generic term for the QJ61CL12 Abbreviation for the Q81BD-J61BT11 or Q80BD-J61BT11N CC-Link system master/ CC-Link board local interface board, the A80BD-J61BT11 CC-Link system master/local interface board, and the A80BD-J61BT13 CC-Link interface board.
Page 33 (4) Power supply modules and base units Generic term/abbreviation Description Generic term for the Q33B, Q35B, Q38B, and Q312B main base units, to each of which a CPU module, Q series power supply module, Q series I/O modules, intelligent function Q3 B modules can be mounted.
Page 34 (5) Others Generic term/abbreviation Description Q series Abbreviation for the programmable controllers, MELSEC-Q series Abbreviation for the programmable controllers, MELSEC-AnS series, which are the AnS series downsized series of the MELSEC-A series Ethernet Generic term for the 100BASE-TX and 10BASE-T network systems Generic term for the QD81MEM-512MBC, QD81MEM-1GBC, QD81MEM-2GBC, QD81MEM QD81MEM-4GBC and QD81MEM-8GBC...
Page 35 GLOSSARY The following lists the terms used in C Controller module manuals and the meanings of the terms. Term Description FTP is an abbreviation for File Transfer Protocol, which is used to transfer data files. Telnet Network protocol, or virtual terminal software, that enables remote login in TCP/IP networks. CompactFlash card (CF Storage card stipulated in the "CF+ and CompactFlash Specification"...
Page 36 : Applicable, : Not applicable * 1 First five digits of serial number * 2 For Q12DCCPU-V earlier than "15102", the mode cannot be changed. Q12DCCPU-V earlier than "15102" is regarded as the basic mode in this manual. PACKING LIST One of the listed C Controller modules is included in the product package.
Page 37 OVERVIEW CHAPTER 1 OVERVIEW This manual describes the specifications, functions, preparatory procedures, and troubleshooting of the C Controller module. C Controller module CC-Link IE controller network module MELSECNET/H module CC-Link module Development environment (personal computer) Access by bus interface function! SW3PVC-CCPU, CC-Link Workbench, or Tornado...
Page 38 Details messages in respective utilities * 1 For Q24DHCCPU-V, Q24DHCCPU-VG, Q24DHCCPU-LS, Q26DHCCPU-LS, or Q12DCCPU-V (Extended mode), refer to the following manual. MELSEC-Q C Controller Module User's Manual * 2 For Q24DHCCPU-V, Q24DHCCPU-VG, Q24DHCCPU-LS, Q26DHCCPU-LS, or Q12DCCPU-V (Extended mode), refer to the following manual.
Page 39 OVERVIEW Remark This manual mainly describes the C Controller module itself. For the C Controller system information listed below, refer to the following. QCPU User's Manual (Hardware Design, Maintenance and Inspection) When reading the above manual, interpret the terms, "CPU module" and "programmable controller"...
Page 40 OVERVIEW Features The features of the C Controller module are described below. (1) Development environment can reduce the development period and engineering cost. By adopting a real-time operating system "VxWorks", a highly reliable and robust system can be constructed. User application (C or C language) Standard I/O library Dedicated library...
Page 41 (4) Takt time for the system can be reduced. (Q12DCCPU-V only) Without using any program, the Q12DCCPU-V can transfer a large volume of data (up to 14K words) at a high speed in cycles of 0.88ms, and can share the data with other CPU modules.
Page 42 OVERVIEW (5) Sophisticated and high-precision sequential and tracking controls (Q12DCCPU-V only) The C Controller module can execute an interrupt routine (interrupt program) when one of the following interrupts occurs. Interrupt routine (interrupt program) execution does not produce a delay that could be caused by user program execution or priority in multitasking.
Page 43 Interrupt routines (interrupt programs) cannot be executed for the following C Controller modules. • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier (c) Interrupts from other CPUs Interrupt routines (interrupt programs) can be executed for interrupts from other CPUs (programmable controller CPUs or C Controller modules).
Page 44 Ethernet communication programs can be created easily using the VxWorks communication library (socket functions). With two built-in Ethernet ports (two channels), the Q12DCCPU-V can perform real- time communication that will improve the machine operation rates and productivity. (a) Case 1: Real-time communication with MES and EES...
Page 45 Why? will visit you as soon as possible. Figure 1.9 7-segment LED display (8) Easy configuration and startup of positioning modules (Q12DCCPU-V only) By using GX Configurator-QP, which is a setting, monitoring and testing tool for positioning modules, the engineering cost can be reduced because parameter-setting programs are no more needed.
Page 46 OVERVIEW (9) More scalable and flexible system construction utilizing various MELSEC-Q series network products The following access methods are available through network modules. (a) Message communication Using a bus interface function or MELSEC data link function, a message can be transmitted via the following network module.
Page 47 The Q06CCPU-V-B cannot access another station's programmable controller CPU. The following C Controller modules cannot access another station's C Controller module. • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier • Q06CCPU-V(-B) Access via CC-Link IE controller network...
Page 48 OVERVIEW (10)Control of a wide variety of CC-Link products The C Controller module can control a wide variety of CC-Link products using user programs. Up to eight CC-Link modules can be mounted. C Controller module CC-Link module Remote I/O station Remote device station Local station Intelligent device station...
Page 49 OVERVIEW (12)Simple remote debugging of the C Controller module with the supported Telnet function By executing a Shell command from the Telnet tool of the development environment (personal computer), remote debugging of the C Controller module (task information display, memory dumping, etc.) can be performed with ease. Simple remote debugging without using Workbench or Tornado is available.
Page 50 OVERVIEW (14)User programs can be stored in the built-in standard RAM or ROM. The C Controller module has a built-in standard RAM or ROM. Therefore, user programs can be stored even if there is no external memory such as a CompactFlash card.
Page 51 Device functions cannot be used for the following C Controller modules. • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier • Q06CCPU-V(-B) (a) Communication with a GOT without using any program (connecting a GOT in a...
Page 52 Ethernet communications Figure 1.19 Connection with MX Component (19)Mode change expands the function (For Q12DCCPU-V with a serial number whose first five digits are "15102" or later) By switching the mode (from basic mode to extended mode) using the module initialization setting, the function of Q12DCCPU-V, such as the dedicated instructions, memory, and network, are added.
Page 53 SYSTEM CONFIGURATION CHAPTER 2 SYSTEM CONFIGURATION This chapter explains system configurations, applicable modules, and connectable devices when using the C Controller module. System Configuration This section introduces C Controller system configurations, including devices used for each base unit, connection with an environment development, and entire system overview.
Page 54 SYSTEM CONFIGURATION 2.1.1 Devices used for each base unit (1) When using the main base unit (Q3 CompactFlash card (sold 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 When a main base unit is used * 1 For the Q06CCPU-V-B, CompactFlash cards cannot be used.
Page 55 SYSTEM CONFIGURATION (2) When using the slim type main base unit (Q3 CompactFlash card (sold separately) C Controller module Battery Slim type main base unit Q series power supply, I/O, Intelligent function modules Figure 2.2 When a slim type main base unit is used * 1 For the Q06CCPU-V-B, CompactFlash cards cannot be used.
Page 56 SYSTEM CONFIGURATION (3) When using the multiple CPU high speed main base unit (Q3 CompactFlash card (sold 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 When a multiple CPU high speed main base unit is used * 1 For the Q06CCPU-V-B, CompactFlash cards cannot be used.
Page 57 SYSTEM CONFIGURATION 2.1.2 Connection with a development environment (1) For the Q12DCCPU-V C Controller module CompactFlash card (sold separately)* Development environment* (personal computer) Twisted pair cable (Straight cable or crossing cable) (sold separately) CompactFlash card Adaptor* (sold separately)* (sold separately)
Page 58 SYSTEM CONFIGURATION (2) For the Q06CCPU-V(-B) C Controller module CompactFlash card (sold separately)* Development environment* (personal computer) Twisted pair cable (Crossing cable) (sold separately) CompactFlash card Adaptor* (sold separately)* (sold separately) Tornado* SW3PVC-CCPU (sold separately) Figure 2.5 Connection with a development environment * 1 To write a user file to a CompactFlash card, a personal computer such as a laptop that has the PCMCIA interface, or a personal computer with a CompactFlash card reader/writer connected is required.
Page 59 SYSTEM CONFIGURATION 2.1.3 Connection with peripheral devices (1) For the Q12DCCPU-V C Controller module Hub (sold separately) Hub (sold separately) Twisted pair cable (Straight cable) (sold separately) Target devices (personal computer, C Controller module, GOT, etc) GOT, RS-232 cable (sold separately)
Page 60 SYSTEM CONFIGURATION (2) For the Q06CCPU-V(-B) C Controller module Hub (sold separately)*1 Twisted pair cable (Straight cable) Target devices (such as personal computer and C Controller (sold separately) module) GOT, RS-232 cable (sold separately) Figure 2.7 Connection with peripheral devices * 1 Q06CCPU-V does not support the IEEE802.3x flow control.
Page 61 SYSTEM CONFIGURATION 2.1.4 System configuration overview (1) When using the main base unit (Q3 Main base unit A 16-point module is mounted on each slot Q35B (exclusive 5 slots) Slot No. I/O No. Q series C Controller module power supply module Extension base unit A 16-point module is mounted on each slot...
Page 62 SYSTEM CONFIGURATION Table 2.1 Restrictions on the system configuration Maximum number of 7 units extension base units Maximum number of I/O 64 modules modules Main base unit model Q33B, Q35B, Q38B, Q312B No power supply module required Q52B, Q55B Extension base unit model Q series power supply module required Q63B, Q65B, Q68B, Q612B...
Page 63 SYSTEM CONFIGURATION (2) When using the slim type base unit (Q3 Slim type main base unit A 32-point module is mounted on each slot Q35SB (5 slots occupied) ..Slot number ..I/O number Slim type power supply C Controller module module Figure 2.9 Configuration example of a system using a slim type base unit Table 2.2 Restrictions on the system configuration...
Page 64 SYSTEM CONFIGURATION (3) When using the multiple CPU high speed main base unit (Q3 Multiple CPU high speed main base unit ...A 32-point module is mounted on each slot Q312DB (12 slots occupied) ..Slot number ..I/O number Q series power C Controller module supply module Extension base unit ...
Page 65 SYSTEM CONFIGURATION Table 2.3 Restrictions on the system configuration Maximum number of 7 units extension base units Maximum number of I/O 64 modules modules Applicable main base Q35DB, Q38DB, Q312DB unit model No power supply module required Q52B, Q55B Applicable extension base unit model Q series power supply module required Q63B, Q65B, Q68B, Q612B...
Page 66 GOT1000 Series Connection Manual (Mitsubishi Products) A GOT cannot be connected in a bus topology with the following C Controller modules. • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier • Q06CCPU-V(-B) (1) How the C Controller module recognizes the GOT If a GOT is connected in a bus topology, the C Controller module recognizes the GOT as an intelligent function module of 16 I/O points.
Page 67 SYSTEM CONFIGURATION • The following system alarm may occur in the GOT at start-up, depending on the system configuration and GOT settings. "402 A communication timeout occurred. Check the communication path or module." To avoid the occurrence of the above system alarm, set the GOT title display time to be sufficiently longer than the C Controller module start-up time.
Page 68 SYSTEM CONFIGURATION 2.1.6 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 main base units are not applicable.
Page 69 SYSTEM CONFIGURATION Applicable Modules This section introduces modules applicable to the C Controller module. Precautions for using I/O modules and intelligent function modules, refer to the following. Page 2-19, Section 2.2.2 2.2.1 Applicable I/O modules and intelligent function modules The following table indicates the MELSEC-Q series I/O modules and intelligent function modules that can be used with the C Controller module.
Page 70 For applicable GOT models, refer to the following. GOT1000 Series Connection Manual (Mitsubishi Products) * 1 This cannot be used with the Q12DCCPU-V with a serial number (first five digits) "12041" or earlier. * 2 This cannot be used with the Q06CCPU-V(-B) * 3 This cannot be used with the Q06CCPU-V with a serial number (first five digits) "10011"...
Page 71 * 1 When the interrupt event setting is specified in the following C Controller modules, up to 64 modules can be installed. •Q12DCCPU-V with a serial number whose first five digits are "12042" or later (2) Precautions for using a CC-Link module The following restrictions are applied to the CC-Link module controlled by the C Controller module.
Page 72 SYSTEM CONFIGURATION (3) Precautions for using a MELSECNET/H module The following restrictions are applied to the MELSECNET/H module controlled by the C Controller module. • The MELSECNET/H module cannot be used on a remote I/O network. Use of the module is allowed on a PLC-to-PLC network only. •...
Page 73 SYSTEM CONFIGURATION (4) Precautions for using a CC-Link IE controller network module The following restrictions are applied to the CC-Link IE controller network module controlled by the C Controller module. • The module cannot be used as a relay station for the data link transfer function or the routing function.
Page 74 SYSTEM CONFIGURATION (5) Precautions for using the CC-Link IE field network master/local module The following restrictions are applied to the CC-Link IE field network master/local module controlled by the C Controller module. (a) There are some unsupported functions. For the unsupported functions, refer to the following. MELSEC-Q CC-Link IE Field Network Master/Local Module User's Manual (b) There is no module configuration/monitoring tool for the CC-Link IE field network master/local module.
Page 75 SYSTEM CONFIGURATION (7) Precautions for using an FL-net module The following restrictions are applied to the FL-net module controlled by the C Controller module. • The word block read/write request messages using the message transmission function cannot be received. • The auto refresh function is not applicable. (8) Precautions on interrupt processing Interrupts are used for communications of the C Controller module.
Page 76 Motion CPU MX Component Version 3.14Q or later * 1 Can be connected when using Q12DCCPU-V with a serial number whose first five digits are "15102" or later with the extended mode. (2) For the Q06CCPU-V Table 2.7 Software package...
Page 77 Failure to do so may cause a problem such as data corruption in the CompactFlash card and system stop. Table 2.9 Applicable CompactFlash cards Applicable models Model name Description Q12DCCPU-V Q06CCPU-V GT05-MEM-128MC 128MB CompactFlash card GT05-MEM-256MC 256MB CompactFlash card QD81MEM-512MBC...
Page 78 SYSTEM CONFIGURATION (2) Twisted pair cable Use the twisted pair cables that meet IEEE802.3 10BASE-T/100BASE-TX standards. (a) At 100Mbps Use either of the following cables. • Unshielded twisted pair (UTP) cable Straight cable: Category 5 or higher Crossing cable: Category 5 or 5e •...
Page 79 When connecting a hub that does not have the auto negotiation function, set the hub to the half-duplex communication mode. (a) For the Q12DCCPU-V CH1 and CH2 of the C Controller module are assigned to different sub-networks. Do not connect CH1 and CH2 of the C Controller module to the same hub (excluding switching hubs).
Page 80 SYSTEM CONFIGURATION (5) USB cable (Q12DCCPU-V only) (a) The C Controller module is accessible from the following software packages by ® pre-installing a USB driver in Windows (For how to install the USB driver, refer to the manual for the software package to be used.)
Page 81 GOT1000 Series Connection Manual (Mitsubishi Products) * 2 The module cannot be connected to the following C Controller modules. • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier • Q06CCPU-V(-B) (7) Connection from GX Works2/GX Developer...
Page 82 SYSTEM CONFIGURATION 2) For the Q06CCPU-V(-B) GX Works2/GX Developer is not connectable to the C Controller module. C Controller module GX Works2/GX Developer Figure 2.14 Direct connection (not available) - 30 2.4 Applicable Devices...
Page 83 SYSTEM CONFIGURATION (b) Access to a programmable controller CPU via a network module controlled by a C Controller module GX Works2/GX Developer connected to a programmable controller CPU can access another programmable controller CPU on another station via a network module (CC-Link module, MELSECNET/H module, or CC-Link IE controller network module) controlled by a C Controller module.
Page 84 SYSTEM CONFIGURATION 2) Other station access via MELSECNET/H and CC-Link Transfer Setup in GX Works2/GX Developer Programmable controller CPU MELSECNET/H GX Works2/GX Developer Accessible via network module controlled by the C Controller module! CC-Link Programmable controller CPU Figure 2.16 Other station access via MELSECNET/H and CC-Link - 32 2.4 Applicable Devices...
Page 85 * 1 Connection via the 10BASE-T/100BASE-TX interface is not available with the following C Controller modules. • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier * 2 For connection via the 10BASE-T/100BASE-TX interface, it is necessary to configure the built-in Ethernet port open setting in the <<System Settings>>...
Page 86 SYSTEM CONFIGURATION (12)Connection to external devices (a) RS-232 device The following are precautions for connecting an RS-232 device to the RS-232 interface of the C Controller module. • A receive error may occur on the target device when the C Controller module or the target device connected to the C Controller module is powered on or off, or reset.
Page 87 System information screen of SW3PVC- CCPU. (1) Checking on the rating plate The rating plate is located on the side face of the module. (a) For the Q12DCCPU-V Serial number (first five digits) Function version Relevant regulation standards Figure 2.17 Rating plate...
Page 88 SYSTEM CONFIGURATION (2) Checking on the serial number display The serial number and function version is printed on the serial number display on the front (at the bottom) of the module. Function version 100911102450001-B Serial number Serial number display Figure 2.19 Front of the module Remark Serial No.
Page 89 Note that "-" is displayed for the module that does not support the product number display. * 1 The Product number fields are active only for the Q12DCCPU-V. (b) Version information screen To display the version information screen, select [Version information] from the System menu of C Controller setting utility.
Page 90 SYSTEM CONFIGURATION POINT The serial number displayed on the Version information screen of C Controller setting utility may differ from the ones printed on the rating plate and the front of the module. • The serial numbers on the rating plate and the front of the module indicate the management information.
Page 91 SPECIFICATIONS CHAPTER 3 SPECIFICATIONS Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B General Specifications Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following indicates the general specifications of the C Controller module. Table 3.1 General specifications Item Specifications Operating ambient temperature 0 to 55 Storage ambient temperature -25 to 75...
Page 92 SPECIFICATIONS Performance Specifications Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the performance specifications of the C Controller module. Table 3.2 Performance specifications Specifications Item Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Hardware specifications Endian format (Memory layout) Little endian Big endian Standard RAM 3M bytes...
Page 93 * 1 The number of bytes for the following C Controller modules is 128K bytes. •Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier * 2 For the development environment (personal computer), refer to the following manual.
Page 94 CI(RI) Ring Indicator (b) Connector shell for connection cable Use the following connector shell on the Q12DCCPU-CBL side. • DDK Ltd. Plug, shell: 17JE-23090-02(D8A)(-CG) • Connector fitting screw (M2.6) 3.3 RS-232 Connector Specifications 3.3.1 RS-232 connector specifications for the Q12DCCPU-V...
Page 95 SPECIFICATIONS 3.3.2 RS-232 connector specifications for the Q06CCPU-V(-B) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) RS-232 connector specifications Table 3.4 RS-232 connector specifications Signal direction Pin No. Mnemonic Signal name C Controller module RS-232 device CD(DCD) Data Carrier Detect RD(RXD) Received Data SD(TXD)
Page 96 SPECIFICATIONS Operation Processing Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B 3.4.1 Initial processing Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The initial processing is preprocessing executed upon startup 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.
Page 97 SPECIFICATIONS 3.4.2 I/O access timing Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the input (X) and output (Y) data transfer timings of the C Controller module. (1) Input (X) loading timing The C Controller module loads input (X) data at one of the following timings.
Page 98 SPECIFICATIONS 3.4.3 RUN, STOP and PAUSE status operation processing Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The C Controller module has three different operation states: RUN, STOP and PAUSE. This section explains the operation processing of the C Controller module in each operation status.
Page 99 SPECIFICATIONS 3.4.4 Operation processing during momentary power failure Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The C Controller module detects a momentary power failure when the input power voltage supplied to the power supply module falls below the specified range. On detection of a momentary power failure, the following operation is performed.
Page 100 FUNCTIONS CHAPTER 4 FUNCTIONS Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This chapter explains the C Controller module functions. Function List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following lists the C Controller module functions. Table 4.1 List of C Controller module functions Availability Reference Function Description...
Page 101 FUNCTIONS Table 4.1 List of C Controller module functions (continued) Availability Reference Function Description Q12DC Q06C Q06C section CPU-V CPU-V CPU-V-B Set whether to clear or hold the outputs to output modules, I/ Error time output mode Page 4-36, O combined modules, and intelligent function modules when setting Section 4.9 a stop error occurs in the C Controller module.
Page 102 Interrupt issue to interrupt to a Motion CPU. Page 13-44, Motion CPU For the Q172DCPU or Q173DCPU, use the Q12DCCPU-V C Section 13.6 Controller module. From the user program of the C Controller module, start a Motion CPU's SFC program or servo program or changes the...
Page 103 FUNCTIONS I/O Module and Intelligent Function Module Access Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) About this function This function controls the I/O modules and intelligent function modules that are controlled by the C Controller module. Create the user program of the C Controller module using the bus interface functions.
Page 104 FUNCTIONS Remote Operation Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The remote operation function controls the operation status of the C Controller module or a programmable controller CPU from the user program or C Controller setting utility of the development environment (personal computer).
Page 105 FUNCTIONS 4.3.1 Remote RUN/STOP Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B For the remote RUN/STOP operation from a programmable controller CPU, refer to the manual for the programmable controller CPU. (1) What is remote RUN/STOP? The remote RUN/STOP is a control from the user program or development environment (personal computer), by which the C Controller module can run or stop with its RUN/STOP/MODE switch set to RUN.
Page 106 FUNCTIONS (4) Methods for remote RUN/STOP The remote RUN/STOP can be executed by either of the following two methods: "Using user program" and "Using development environment (personal computer). (a) Using user program Execute a bus interface function (QBF_Control or QBF_ControlEx) from the user program to perform remote RUN/STOP.
Page 107 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 of the user program or C Controller setting utility. (b) Changing the remote STOP status to RUN again To change the C Controller module status from remote STOP to RUN again, execute remote RUN.
Page 108 FUNCTIONS 4.3.2 Remote PAUSE Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B For the remote PAUSE from a programmable controller CPU, refer to the manual for the programmable controller CPU. (1) What is remote PAUSE? The remote PAUSE is a control from the user program or development environment (personal computer), by which the C Controller module can be placed in the PAUSE status with its RUN/STOP/MODE switch set to RUN.
Page 109 FUNCTIONS (b) Using development environment (personal computer) In <<Online operation>> of C Controller setting utility, perform as described below. 1) Set "Remote operation" to "PAUSE" and select a C Controller module or programmable controller CPU. Execute 2) Click to execute remote PAUSE. 1) Set "PAUSE"...
Page 110 FUNCTIONS 4.3.3 Remote RESET Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) What is remote RESET? The remote RESET is a control from the user program or development environment (personal computer), by which the C Controller module or programmable controller CPU can be reset when it is in the STOP status.
Page 111 FUNCTIONS (4) Remote RESET timing The remote RESET is executable in the STOP status only. When the C Controller module or programmable controller CPU is in the RUN status, change the status to STOP by remote STOP. Even if the RUN/STOP/MODE, RUN/STOP, or RUN/STOP/RESET switch of the C Controller module or programmable controller CPU is set to RUN, it can be reset when it is stopped due to an error that can be detected by the self-diagnostic function.
Page 112 FUNCTIONS (b) When a programmable controller CPU is CPU No.1 in a multiple CPU system Check the following conditions 1) and 2) before executing remote RESET. Remote RESET is not available if either of 1) and 2) is not satisfied. 1) Setting required for remote RESET For CPU No.1, set "Allow"...
Page 113 FUNCTIONS (6) Methods for remote RESET The remote RESET can be executed by either of the following two methods: "Using user program" and "Using development environment (personal computer). (a) Using user program Execute a bus interface function (QBF_Reset) from the user program to perform remote RESET.
Page 114 FUNCTIONS (7) Precautions (a) Setting for remote RESET Check the conditions given in (5) in this section before performing remote RESET. If the conditions in (5) in this section are not satisfied, remote RESET is not allowed. (b) Before performing remote RESET Close the respective user programs in the C Controller module before performing remote RESET.
Page 115 FUNCTIONS 4.3.4 Relation between remote operation and RUN/STOP status Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the relation between the remote operations and the RUN/STOP/ MODE switch setting of the C Controller module. (1) Relation between remote operation and RUN/STOP status of C...
Page 116 FUNCTIONS POINT Remote operation from the C Controller module to CPU No.1 (programmable controller CPU) can be performed by the following methods. • Remote RESET from C Controller setting utility • Remote RESET from a bus interface function (QBF_Reset) • Remote RUN/STOP/PAUSE from a MELSEC data link function (mdControl) For the Q06CCPU-V-B, MELSEC data link functions are not available.
Page 117 Creates a device such as a programmable controller CPU in work RAM on the C Controller module. Device function cannot be used for the following C Controller modules. • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier (2) Device list The following shows devices that can be created.
Page 118 FUNCTIONS (4) Precautions (a) Number of device points Set only the required number of device points. Because a device is created in work RAM, the available range of work RAM, such as in a user program, decreases due to an extra setting. The consumption of work RAM is calculated by the following formulas.
Page 119 (a) Turning on or flashing the ERR. LED The ERR. LED on the front side of the C Controller module turns on or flashes. (b) Flashing the 7-segment LED (Q12DCCPU-V only) The 7-segment LED on the front of the C Controller module flashes, indicating "00", "01"...
Page 120 FUNCTIONS 3) Fuse blown error or module verify error For the above errors, whether to stop or continue the output (Y) from the user program and writing to the buffer memory can be selected. Set it in "Operation mode at the time of error" in <<System settings>> of C Controller setting utility.
Page 121 FUNCTIONS (4) Self-diagnostic function list Table 4.6 lists the self-diagnostic functions available during normal operation. The numbers under the "Error handling" column heading represent the following: Table 4.5 Numbers under "Error handling"and corresponding descriptions Description Error details can be confirmed in C Controller setting utility. C Controller Module User's Manual (Utility Operation, Programming) Output (ON/OFF) to an output module, I/O module, or intelligent function module from the user program is disabled.
Page 122 FUNCTIONS Table 4.6 Self-diagnostic function list C Controller LED status Error handling Item Description module Diagnostic timing ERR. status System watchdog timer A system watchdog timer error is Stop Flash Any time error detection detected. User watchdog timer A user watchdog timer error is Stop Flash Any time error detection...
Page 123 RAM (SRAM) is detected. SRAM error detection (The standard RAM ("/RAM") is Stop Flash At power-on included.) at reset (The Q12DCCPU-V only) An error of the built-in ROM ("/ Built-in ROM error At power-on, SYSTEMROM") is detected. Stop Flash at reset...
Page 124 A C Controller module can clear only continuation errors. The errors cannot be cleared with the following C Controller modules. • Q12DCCPU-V with a serial number whose first five digits are "12041" or higher • Q06CCPU-V(-B) (a) Error clear procedure To clear errors, complete the following procedure.
Page 125 FUNCTIONS Output (Y) Status Setting for Switching STOP to RUN Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Output (Y) status setting for changing the status from STOP to RUN When the C Controller module status is switched from RUN to STOP, the output data (Y) in the RUN status are saved in the C Controller module and actual outputs are all turned off.
Page 126 FUNCTIONS (3) Processing (a) Previous state (Default) The output status (Y) immediately before the change to STOP 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. For forcing the output (Y) to turn ON in the STOP status, refer to the following.
Page 127 FUNCTIONS (5) Precautions (a) When the output (Y) is forced to turn ON in the STOP status The table below shows the output operation when the output (Y) is forced to turn ON with the C Controller module set to STOP and then the STOP status is changed to RUN.
Page 128 FUNCTIONS Clock Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) What is the clock function? With the clock function, clock data in the C Controller module are read out by the user program to be used for time control. These clock data are mainly used for time control of the C Controller module system, such as storing time and date information in the event history.
Page 129 FUNCTIONS (4) Changing and reading clock data (a) Changing clock data Clock data can be changed by either of the following two methods: "Using C Controller setting utility" and "Using a user program". 1) Using C Controller setting utility Detail In <<Online operation>>...
Page 130 FUNCTIONS (5) Clock data accuracy (a) While the C Controller module is ON • The clock function accuracy is the same as that of the VxWorks POSIX Clock. A higher frequency of interrupt program execution may cause a longer clock delay, depending on the system configuration of the C Controller module.
Page 131 FUNCTIONS (d) Changing clock data by a user program When changing clock data by a user program, use the QBF_SetTime function. If any other clock data setting function is used, correct clock data will not be set in the C Controller module. (e) Reading clock data by a user program When reading clock data by the user program, functions other than QBF_GetTime can be used.
Page 132 FUNCTIONS 4.7.1 Multiple CPU Clock Synchronization Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) What is the multiple CPU clock synchronization function? The multiple CPU clock synchronization function allows clock data synchronization with CPU No.1 (programmable controller CPU or C Controller module) when the C Controller module is set as CPU No.2, No.3, or No.4 in a multiple CPU system.
Page 133 FUNCTIONS Input Response Time Selection (I/O Response Time) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) What is the input response time selection? The input response time can be changed for each Q series module. The following table shows the modules whose input response time can be changed and time options for them.
Page 134 FUNCTIONS (2) Input response time setting The input response time is set in "I/O assignment" in <<I/O assignment settings>> of C Controller setting utility. 1) Configure the I/O assignment settings. Detailed settings 2) Select 3) Set each input response time in the "I/O module, Intelligent function module detailed settings"...
Page 135 FUNCTIONS Error Time Output Mode Setting Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) What is the error time output mode setting? This setting determines whether to clear or hold the outputs to the following Q series modules when a stop error occurs in the C Controller module.
Page 136 FUNCTIONS 4.10 Hardware Error Time CPU Operation Mode Setting Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) What is the hardware error time CPU operation mode setting? This setting determines whether to stop or continue the output (Y) from the C Controller module and writing to the buffer memory if a hardware error occurs in an intelligent function module or interrupt module.
Page 137 FUNCTIONS 4.11 Switch Settings for I/O and Intelligent Function Modules Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) What is the switch settings for intelligent function modules and interrupt modules? The switches of the Q series intelligent function modules and interrupt modules can be set in C Controller setting utility.
Page 138 FUNCTIONS (3) Switch setting of intelligent function modules and interrupt modules The switches of intelligent function modules and interrupt modules are set in "I/O assignment" in << I/O assignment settings>> of C Controller setting utility. 1) Configure the I/O assignment settings. Switch settings 2) Select 3) Set the switches of each module.
Page 139 FUNCTIONS 4.12 Watchdog Timer (WDT) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) What is watchdog timer (WDT)? Watchdog timers are provided inside the C Controller module to detect failure of the hardware or user program. The C Controller module has the following two different watchdog timers.
Page 140 FUNCTIONS 2) User watchdog timer The user watchdog timer starts monitoring by the QBF_StartWDT function, and it is reset by the QBF_ResetWDT function. The user watchdog timer times out when the user program was not able to complete the processing within the time specified by the QBF_StartWDT function and could not execute the QBF_ResetWDT function.
Page 141 * 1 For the following C Controller modules, the routine cannot be executed as an interrupt routine (interrupt program). • Q12DCCPU-V with a serial number whose first five digits are "12041" or higher • Q06CCPU-V(-B) * 2 Interrupt routine (interrupt program) does not produce a delay caused by user program execution cycles or the priority in multitasking.
Page 142 FUNCTIONS 4) Intelli. module side "Start SI No." Set the intelligent function module interrupt pointer No. that was set at the intelligent function module. Setting range: 0 to 15 (b) Setting example The following is a setting example, showing that SI 0 to 3 of an intelligent function module mounted to the slot of start I/O No.20 are assigned to interrupt pointers 50 to 53.
Page 143 FUNCTIONS (3) Processing overview (a) Executing interrupt routines (interrupt programs) This section explains how to execute a routine registered in the QBF_EntryUnitInt function as an interrupt routine (interrupt program). 1) This function registers a routine that corresponds to an interrupt from the intelligent function module or interrupt module by the QBF_EntryUnitInt.
Page 144 FUNCTIONS (b) Restarting a user program This section explains how to restart a user program which is in the interrupt event waiting status by the QBF_WaitUnitEvent function. 1) In the user program, call the QBF_WaitUnitEvent function. 2) The user program is placed into the interrupt event waiting status by 1). 3) An interrupt from the intelligent function module or interrupt module is issued in the status of 2).
Page 145 FUNCTIONS (4) Function The following are functions used in interrupts from the intelligent function module or interrupt module. Table 4.10 Functions used for an interrupt from the intelligent function module or interrupt module Function name Function Registers a routine so that it can be called when an interrupt QBF_EntryUnitInt occurs from the intelligent function module or interrupt module.
Page 146 FUNCTIONS 4.14 Connection Between C Controller Module and GOT (Microcomputer Connection) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Connection between the C Controller module and GOT (Microcomputer connection) By connecting an RS-232 cable from a GOT to the C Controller module's RS-232 interface, the C Controller module can communicate with the GOT using virtual devices inside the GOT.
Page 147 FUNCTIONS 4.15 Telnet Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The Shell commands can be executed from the Telnet tool of the development environment (personal computer) without using Workbench or Tornado. This allows simple remote debugging (task information display, memory dumping, etc.) of the C Controller module.
Page 148 The timeout time for the C Controller module side Telnet (TCP) connection can be changed by setting the values in the calculation formula and using one of the setting methods introduced for each model. [Calculation for the Q12DCCPU-V] The timeout time is determined by the following calculation formula. Timeout time = net.inet.tcp.keepidle...
Page 149 FUNCTIONS [Setting methods for the Q12DCCPU-V] The following explains how to set the initial value of 30 seconds. • Setting it while the C Controller module is in operation 1) Connect the line to the C Controller module with the Telnet tool.
Page 150 FUNCTIONS [Calculation for the Q06CCPU-V(-B)] The timeout time is determined by the following calculation formula. Timeout time = tcp_keepidle + ( tcp_keepintvl tcp_keepcnt ) [s] Initial value: 15000 (4 hours and 10 minutes) tcp_keepidle: Time elapsed from line disconnection to the first retry (s) Initial value: 14400 tcp_keepintvl: Retry interval (in 0.5s units) Initial value: 150...
Page 151 The Shell commands entered by the Telnet tool of the development environment (personal computer) operate on the tasks of the following priorities C Controller module Priority Q12DCCPU-V Q06CCPU-V(-B) When using a Shell command, pay attention to the following. • Only alphanumeric characters and special characters can be used.
Page 152 Ethernet port on the C Controller module with an Ethernet cable. Functions for communicating with a peripheral device through an Ethernet port cannot be used with the following C Controller modules. • Q12DCCPU-V with a serial number whose first five digits are "12041" or higher C Controller module Ethernet GX Developer Figure 4.24 Example of the connection with a peripheral device through an Ethernet port...
Page 153 FUNCTIONS (2) Peripheral devices that cannot be connected The following peripheral devices cannot be connected to the Ethernet port of the C Controller module. • GX Configurator-QP • MT Developer (3) Settings for communication with peripheral devices through an Ethernet port For communicating with a peripheral device through an Ethernet port, it is necessary to set the built-in Ethernet port open settings in the <<System settings>>...
Page 154 FUNCTIONS (c) Resend processing for TCP connections When there is no ACK response of the TCP protocols from the external device for sending in TCP connection, resend processing is performed at the following numbers of resends and resend intervals. Table 4.12 Resend interval Interval until resend When connection is being After connection is...
Page 155 ACCESS VIA NETWORK MODULES CHAPTER 5 ACCESS VIA NETWORK MODULES Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Network Module Access Function List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following table lists the network module access functions of the C Controller module. Table 5.1 List of the network module access functions of the C Controller module...
Page 156 ACCESS VIA NETWORK MODULES CC-Link Module Access Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) The CC-Link module access function This function allows access to each station, programmable controller CPU on another station, or C Controller module that is connected to CC-Link via CC-Link modules.
Page 157 ACCESS VIA NETWORK MODULES 5.2.1 Block data assurance per station Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The block data assurance per station is a function with which integrity of cyclic data is ensured for each station. Depending on the read/write timing, a block of cyclic data may be split into new and old data in double-word (32-bit) units.
Page 158 ACCESS VIA NETWORK MODULES (3) How to read out cyclic data (from the buffer memory) Cyclic data can be read out from the buffer memory using the block data assurance per station, by one of the methods described below. If any other method is used, integrity of cyclic data for each slave station is not guaranteed.
Page 159 ACCESS VIA NETWORK MODULES (b) Manual cyclic data refresh 1) Use the QBF_RefreshLinkDevice function to issue a refresh request. 2) The user program is continued. 3) Data are refreshed by the request in 1). 4) Execute the QBF_FromBuf function with "manual" specified for "CC-Link refresh method"...
Page 160 ACCESS VIA NETWORK MODULES POINT When any of the following operations is performed for the CC-Link module for which the block data assurance per station is enabled, cyclic data are automatically refreshed even if the QBF_RefleshLinkDevice function is not executed. •...
Page 161 ACCESS VIA NETWORK MODULES (a) Automatic cyclic data refresh 1) Execute the QBF_ToBuf function with "automatic" specified for "CC-Link refresh method" of the third argument (ulOffset). 2) In the timing of the next link scan, data are refreshed. C Controller module CC-Link module User program Link scan...
Page 162 ACCESS VIA NETWORK MODULES (b) Manual cyclic data refresh 1) Execute the QBF_ToBuf function with "manual" specified for "CC-Link refresh method" of the third argument (ulOffset). 2) Use the QBF_RefreshLinkDevice function to issue a refresh request. 3) In the timing of the next link scan, refresh is performed. C Controller module CC-Link module User program...
Page 163 ACCESS VIA NETWORK MODULES • If data writing is attempted before completion of the refresh after execution of the QBF_RefreshLinkDevice function, the data will be not written until completion of the previous refresh. C Controller module CC-Link module User program Link scan Buffer memory QBF_ToBuf function (Manual) 1)
Page 164 ACCESS VIA NETWORK MODULES MELSECNET/H Module Access Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The MELSECNET/H module access function allows access to each station, programmable controller CPU on another station, or C Controller module connected to MELSECNET/H via MELSECNET/H modules. In a multiple CPU system configuration, access cannot be made via a MELSECNET/H module controlled by another CPU.
Page 165 ACCESS VIA NETWORK MODULES 5.3.1 Message communication Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The C Controller module can transfer messages (message transmission/reception) by user programs. Messages can be transferred among the following modules via a MELSECNET/H module. In a multiple CPU system configuration, any access via a MELSECNET/H module controlled by another CPU is not allowed.
Page 166 ACCESS VIA NETWORK MODULES (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 receive buffer has the areas for four MELSECNET/H modules, and up to 128 received data can be stored in each area.
Page 167 ACCESS VIA NETWORK MODULES Remark For the bus interface functions and MELSEC data link functions, refer to the following manual. C Controller Module User's Manual (Utility Operation, Programming) (3) Message communication example The following a message communication example. 1) The C Controller module sends a message using a message sending function in the user program.
Page 168 ACCESS VIA NETWORK MODULES POINT Pay attention to the following when sending a message to a MELSECNET/H module controlled by a programmable controller CPU. When sending data twice to the same channel of the receiving station with ACK set, execute the second transmission after the receiving station has read out the first data by the RECV instruction.
Page 169 ACCESS VIA NETWORK MODULES 5.3.2 Link device access Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Link device data of a MELSECNET/H module controlled by a C Controller module can be read or written from a 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 170 ACCESS VIA NETWORK MODULES 2) Accessible devices The following devices are available for internal link device buffer access. Table 5.5 List of accessible devices Accessible device No. of points Address range LX buffer 8192 0000 to 1FFF LY buffer 8192 0000 to 1FFF LB buffer...
Page 171 ACCESS VIA NETWORK MODULES (c) Link device refresh Data are refreshed between the link devices and internal link device buffers in the specified link device refresh cycles and with refresh parameters set in MELSECNET/H utility. Page 5-21, Section 5.3.4) This refresh is performed in the areas that are set by refresh parameters and also set in Network range assignment in the <<Parameter settings>>...
Page 172 ACCESS VIA NETWORK MODULES (2) Direct access (a) What is direct access? The direct access is a method of directly accessing a link device of a MELSEC/H module from a user program on the C Controller module, independently of the link device refresh.
Page 173 ACCESS VIA NETWORK MODULES (c) Selection of internal buffer access or direct access Select a suitable access method referring to the following. 1) Data suitable for internal buffer access If a link device is used frequently or the block data assurance per station is needed for a link device, the data of the link device are suitable for internal buffer access.
Page 174 ACCESS VIA NETWORK MODULES 5.3.3 Parameter settings Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Set parameters in the <<Parameter settings>> tab of MELSECNET/H utility. C Controller Module User's Manual (Utility Operation, Programming)) Figure 5.17 Parameter settings tab - 20 5.3 MELSECNET/H Module Access Function...
Page 175 ACCESS VIA NETWORK MODULES 5.3.4 Link device refresh setting Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Link device refresh setting is required when using the internal buffer access in user programs. To enable the link device refresh, set a link device refresh cycle and refresh parameters in MELSECNET/H utility.
Page 176 ACCESS VIA NETWORK MODULES 3) Variation in total link device refresh time The total link device refresh time varies depending on the operating conditions of the C Controller system. It may take a longer time if the interrupt processing or high-priority task processing, such as the following, is activated during link device refresh.
Page 177 ACCESS VIA NETWORK MODULES (b) How to determine the link device refresh cycle Take the steps according to the following flowchart. Calculating total link device refresh time (This section (1)) (Page 5-24) Setting a temporary link device refresh cycle (This section (2)) (Page 5-24) (Page 5-24) Test run of C Controller system (This section (3))
Page 178 ACCESS VIA NETWORK MODULES 1) Calculating the total link device refresh time Calculate the total link device refresh time. Page 5-32, Section 5.3.5 (2)) 2) Setting a temporary link device refresh cycle The link device refresh cycle value and the total link device refresh time value obtained in 1) must satisfy the following relational expression.
Page 179 ACCESS VIA NETWORK MODULES [Check 2: Check if the C Controller system operation meets the system specifications or not.] Check if the C Controller system operation meets the system specifications or not. Even if the error stated in Check 1 is not detected, normal operation of the C Controller system must be confirmed.
Page 180 ACCESS VIA NETWORK MODULES 5) Actions for C Controller system malfunction For a C Controller system malfunction or faulty user program processing performance, take actions 1 to 3 if necessary to correct the system operation. [Action 1: Increase the link device refresh cycle setting value.] Check the total link device refresh time (Max.) measured during C Controller system operation, in "Link device refresh time (Max.)"...
Page 181 ACCESS VIA NETWORK MODULES [Action 2: Decrease the refresh points.] Check the refresh parameters and decrease the number of refresh points to reduce the total link device refresh time. ( Page 5-35, Section 5.3.5 (3)) Link device refresh cycle C Controller module processing <Before taking action>...
Page 182 ACCESS VIA NETWORK MODULES (2) Refresh parameters The refresh parameters are parameters by which data are transferred from the link devices (LX, LY, LB, and LW) of a MELSECNET/H module to the internal link device buffers (LX, LY, LB and LW buffers) of the C Controller module for use in the user program.
Page 183 ACCESS VIA NETWORK MODULES (3) Refresh parameter setting example The following is a refresh parameter setting example. (a) System configuration Control station Normal station Power MELSECNET MELSECNET C Controller module /H module /H module supply Station Station No.1 No.2 Network No.1 Network No.2 Station Station...
Page 184 ACCESS VIA NETWORK MODULES (c) MELSECNET/H utility: Refresh parameter settings screen Figure 5.29 MELSECNET/H module (1st module) setting Figure 5.30 MELSECNET/H module (2nd module) setting Remark For the MELSECNET/H utility, refer to the following. C Controller Module User's Manual (Utility Operation, Programming) - 30 5.3 MELSECNET/H Module Access Function 5.3.4 Link device refresh setting...
Page 185 ACCESS VIA NETWORK MODULES 5.3.5 Link data transfer processing time specifications Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains how to calculate the link data transfer time and transmission delay time in the MELSECNET/H network system. (1) Link data transfer processing (a) Processing outline Cyclic transmission uses LB/LW/LX/LY of a MELSECNET/H module.
Page 186 ACCESS VIA NETWORK MODULES (b) Link scan and link device refresh Link scans are NOT synchronized with link device refreshes of the C Controller module. Link device refreshes are performed in the link device refresh cycles set for the C Controller module.
Page 187 ACCESS VIA NETWORK MODULES * 1 Total time for the number of mounted MELSECNET/H modules. * 2 For details, refer to the Q Corresponding MELSECNET/H Network System Reference Manual (PLC to PLC network). The above calculation formulas are effective under the following conditions: •...
Page 188 ACCESS VIA NETWORK MODULES (b) Transmission delay time calculation example In a single system configuration, a delay time in cyclic transmission is calculated as described below. Table 5.8 System configuration and conditions Item Description CPU on receiving station C Controller module Total number of stations per network 2 (Control station : 1, Normal station : 1) LB/LW...
Page 189 ACCESS VIA NETWORK MODULES (3) Reducing the link device refresh time The link device refresh time can be reduced by decreasing the number of refresh points for the C Controller module. To decrease the refresh points, modify the refresh and network range assignment parameter settings and use the direct access method for accessing link devices.
Page 190 ACCESS VIA NETWORK MODULES (b) How to decrease the refresh points 1) Modifying refresh parameters Up to 64 refresh ranges can be set for the C Controller module. For refresh parameters, set only the ranges that need to be refreshed. C Controller module MELSECNET/H module Internal link device...
Page 191 ACCESS VIA NETWORK MODULES 2) Using direct access By using direct access for link devices that are infrequently used on its own station and excluding these from the link device refresh ranges, the link device refresh time can be reduced. C Controller C Controller MELSECNET/H module...
Page 192 ACCESS VIA NETWORK MODULES CC-Link IE Controller Network Module Access Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The CC-Link IE controller network module access function allows access to each station, programmable controller CPU on another station, or a C Controller module connected to the CC-Link IE controller network via a CC-Link IE controller network module.
Page 193 ACCESS VIA NETWORK MODULES 5.4.1 Message communication Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The C Controller module can transfer messages (message transmission/reception) by a user program. Messages can be transferred among the following modules via a CC-Link IE controller network module. In a multiple CPU system configuration, any access via a CC-Link IE controller network module controlled by another CPU is not allowed.
Page 194 ACCESS VIA NETWORK MODULES (a) Internal buffer for message reception 1) The internal buffer for message reception stores the data received from the CC-Link IE controller network module controlled by the C Controller module. 2) The internal receive buffer has areas for four CC-Link IE controller network modules, and up to 128 received data can be stored in each area.
Page 195 ACCESS VIA NETWORK MODULES Remark For the bus interface functions and MELSEC data link functions, refer to the following manual. C Controller Module User's Manual (Utility Operation, Programming) (3) Message communication example The following a message communication example. 1) The C Controller module sends a message using a message sending function in the user program.
Page 196 ACCESS VIA NETWORK MODULES 5.4.2 Link device access Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The link devices of a CC-Link IE controller network module controlled by the C Controller module can be accessed for data reading or writing from the user program on the C Controller module.
Page 197 ACCESS VIA NETWORK MODULES 2) Accessible devices The following devices are available for internal link device buffer access. Table 5.9 List of accessible devices Accessible device No. of points Address range LX buffer 8192 0000 to 1FFF LY buffer 8192 0000 to 1FFF LB buffer...
Page 198 ACCESS VIA NETWORK MODULES (c) Link device refresh Data are refreshed between the link devices and internal link device buffers in the specified link device refresh cycles and with refresh parameters set in CC IE Control utility. Page 5-48, Section 5.4.4) This refresh is performed in the area ranges that are set by refresh parameters and also set in Network range assignment in the <<Parameter settings>>...
Page 199 ACCESS VIA NETWORK MODULES (2) Direct access (a) What is direct access? The direct access is a method of directly accessing a link device of a CC-Link IE controller network module from a user program on the C Controller module, independently of the link device refresh.
Page 200 ACCESS VIA NETWORK MODULES (c) Selection of internal buffer access or direct access Select a suitable access method referring to the following. 1) Data suitable for internal buffer access If a link device is used frequently or the block data assurance per station is needed for a link device, the data of the link device are suitable for internal buffer access.
Page 201 ACCESS VIA NETWORK MODULES 5.4.3 Parameter settings Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Set parameters in the <<Parameter settings>> tab of CC IE Control utility. C Controller Module User's Manual (Utility Operation, Programming)) Figure 5.44 Parameter settings tab 5.4 CC-Link IE Controller Network Module Access Function - 47 5.4.3 Parameter settings...
Page 202 ACCESS VIA NETWORK MODULES 5.4.4 Link device refresh setting Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Link device refresh setting is required when using the internal buffer access in user programs. To enable the link device refresh, set a link device refresh cycle and refresh parameters in CC IE Control utility.
Page 203 ACCESS VIA NETWORK MODULES 3) Variation in total link device refresh time The total link device refresh time varies depending on the operating conditions of the C Controller system. It may take longer time if the interrupt processing or high-priority task processing, such as the following, is activated during link device refresh.
Page 204 ACCESS VIA NETWORK MODULES (b) How to determine the link device refresh cycle Take the steps according to the following flowchart. (Page 5-51) Calculating total link device refresh time (This section (1)) Setting a temporary link device refresh cycle (Page 5-51) (This section (2)) (Page 5-51) Test run of C Controller system (This section (3))
Page 205 ACCESS VIA NETWORK MODULES 1) Calculating the total link device refresh time Calculate the total link device refresh time. Page 5-59, Section 5.4.5 (1) (b)) 2) Setting a temporary link device refresh cycle The link device refresh cycle value and the total link device refresh time value obtained in 1) must satisfy the following relational expression.
Page 206 ACCESS VIA NETWORK MODULES 4) Checking the C Controller system operation In the test run of the C Controller system using the temporary link device refresh cycle setting, check the following 1 and 2. [Check 1: Check for an error in the C Controller module.] Check if any error has occurred in the C Controller module.
Page 207 ACCESS VIA NETWORK MODULES 5) When the C Controller system is malfunctioning In the case of C Controller system malfunction or faulty user program processing performance, take actions 1 to 3 if necessary to correct the system operation. [Action 1: Increase the link device refresh cycle setting value.] Check the total link device refresh time (Max.) measured during C Controller system operation, in "Link device refresh time (Max.)"...
Page 208 ACCESS VIA NETWORK MODULES [Action 3: Modify the user program.] Modify the task configuration, priority, processing details of the user program so that the C Controller system specifications and user program processing performance can be satisfied. (c) Link device refresh cycle setting Set a link device refresh cycle in "Link device refresh cycle"...
Page 209 ACCESS VIA NETWORK MODULES (2) Refresh parameters The refresh parameters are parameters by which data are transferred from the link devices (LX, LY, LB, and LW) of a CC-Link IE controller network module to the internal link device buffers (LX, LY, LB and LW buffers) of the C Controller module for use in the user program.
Page 210 ACCESS VIA NETWORK MODULES (3) Refresh parameter setting example The following is a refresh parameter setting example. (a) System configuration Control station Normal station Power CC-Link IE CC-Link IE C Controller module controller controller supply network network module module Station Station No.1 No.2...
Page 211 ACCESS VIA NETWORK MODULES (c) CC IE Control utility: Refresh parameter settings screen Figure 5.56 CC-Link IE controller network module (1st module) setting Figure 5.57 CC-Link IE controller network module (2nd module) setting Remark For the CC IE Control utility, refer to the following manual. C Controller Module User's Manual (Utility Operation, Programming) 5.4 CC-Link IE Controller Network Module Access Function - 57...
Page 212 ACCESS VIA NETWORK MODULES 5.4.5 Link data transfer processing time specifications Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section describes 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 CC-Link IE controller network modules.
Page 213 ACCESS VIA NETWORK MODULES (b) Total link device refresh time ( The total link device refresh time can be calculated by the following formula, with the points assigned to link devices. [Total link device refresh time] LB LX LY = KM1 + KM2 [ms] : Total link device refresh time (sending side) : Total link device refresh time (receiving side)
Page 214 ACCESS VIA NETWORK MODULES (2) How to calculate the 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 Table 5.12 Calculation formulas for transmission delay time >...
Page 215 ACCESS VIA NETWORK MODULES (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) Table 5.13 System configuration and conditions Item Description CPU on receiving station C Controller module Total number of stations per network 2 (Control station: 1, Normal station: 1)
Page 216 ACCESS VIA NETWORK MODULES (3) Reducing the link device refresh time The link device refresh time can be reduced by decreasing the number of refresh points for the C Controller module. To decrease the refresh points, modify the refresh and network range assignment parameter settings and use the direct access method for accessing link devices.
Page 217 ACCESS VIA NETWORK MODULES (b) How to decrease the refresh points 1) Modifying refresh parameters Up to 64 refresh ranges can be set for the C Controller module. For refresh parameters, set only the ranges that need to be refreshed. C Controller module CC-Link IE controller network module Internal link device...
Page 218 ACCESS VIA NETWORK MODULES 2) Using direct access By using direct access for link devices that are infrequently used on its own station and excluding these from the link device refresh ranges, the link device refresh time can be reduced. CC-Link IE controller C Controller C Controller...
Page 219 PREPARATORY PROCEDURES AND SETTING CHAPTER 6 PREPARATORY PROCEDURES AND SETTING Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This chapter explains the preparatory procedures and setting methods for operating the C Controller module in the system. POINT Before handling the C Controller module, read the safety precautions provided in...
Page 220 PREPARATORY PROCEDURES AND SETTING Handling Precautions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the handling precautions for the C Controller module. CAUTION Use the C Controller module in an environment that meets the general specifications shown in this manual. Failure to do so may result in an electric shock, fire, malfunction, or damage to or deterioration of the product.
Page 221 PREPARATORY PROCEDURES AND SETTING POINT Referring to the following manual, observe the proper mounting procedures. QCPU User's Manual (Hardware Design, Maintenance and Inspection) • The case of the C Controller module is made of resin. Do not drop or apply strong shock to it. •...
Page 222 PREPARATORY PROCEDURES AND SETTING Fail-Safe Circuit Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B WARNING Configure safety circuits external to the C Controller module to ensure that the entire system operates safely even when a fault occurs in the external power supply or the C Controller module.
Page 223 PREPARATORY PROCEDURES AND SETTING WARNING For the following controls, configure an interlock circuit in the user program to ensure that the entire system will always operate safely. (1) Changing data of a running C Controller module from the development environment (personal computer) connected (2) Changing the operating status (3) Operation from the development environment (personal computer)
Page 224 PREPARATORY PROCEDURES AND SETTING (1) Circuit example for system design (when not using the ERR. contact of the power supply module) Power supply FOR AC FOR AC/DC Power supply Trans- Trans- former former Transformer Fuse Fuse Fuse C Controller module RUN/STOP circuit C Controller module power...
Page 225 PREPARATORY PROCEDURES AND SETTING * 1 Program the system so that the following operation will be performed at start-up of the C Controller module. 1) When a battery voltage drop is detected, Ym is turned on. In the program, Ym must be turned on by the QBF_Y_Out_BitEx function when "Built-in battery error status"...
Page 226 PREPARATORY PROCEDURES AND SETTING (2) Circuit example for system design (When using the ERR. contact of the power supply module) Power supply FOR AC/DC Transformer Transformer Fuse Fuse C Controller module power (-) (+) Fuse User program RUN/STOP circuit Started when RA1 START (control start output of RA1 RA3...
Page 227 PREPARATORY PROCEDURES AND SETTING * 1 Program the system so that the following operation will be performed at start-up of the C Controller module. 1) When a battery voltage drop is detected, Ym is turned on. In the program, Ym must be turned on by the QBF_Y_Out_BitEx function when "Built-in battery error status"...
Page 228 PREPARATORY PROCEDURES AND SETTING (3) Fail-safe measures against C Controller system failure The C Controller module can detect its own failure by the self-diagnostic function. However, it may not be able to detect a failure that occurred in an I/O control part. In such a case, all of inputs and outputs may turn on or off depending on the failure, and normal operation of the control target and safety may not be ensured.
Page 229 PREPARATORY PROCEDURES AND SETTING Preparatory Procedure and Setting Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B POINT When using Q12DCCPU-V (Extended mode), refer to the following manual. MELSEC-Q C Controller Module User's Manual (1) Starting up the single CPU system Ethernet cable Development environment C Controller module...
Page 230 Is the power supply correctly wired? Page 3-1, Section 3.1 Is the power supply voltage correct? Initialization of C Controller module (Q12DCCPU-V only) (1) (a) in this section, If "01" or "02" flashes on the 7-segment LED at the start of Page 6-72, Section 6.10.1...
Page 231 PREPARATORY PROCEDURES AND SETTING Page 6-37, Section 6.5, Parameter setting C Controller Module User's Manual 1) Connect the C Controller module and development environment (personal computer) with an Ethernet cable. (Utility Operation, Programming), 2) After power-on or completion of the reset status, the C Page 4-29, Section 4.7 Controller module is ready to connect to each utility at the following timing.
Page 232 C Controller module and development environment (personal computer). Page 6-39, Section 6.6) (a) Precautions 1) Flashing "01" or "02" of the 7-segment LED (Q12DCCPU-V only) At start-up of the C Controller module, "01" or "02" flashes on the 7-segment LED when the C Controller module is: •...
Page 233 PREPARATORY PROCEDURES AND SETTING (2) Starting up the CC-Link C Controller module Development environment (personal computer) CC-Link Ethernet Figure 6.9 Configuration at CC-Link startup Preparatory procedure MELSEC-Q CC-Link System Master/ Consideration of network parameters Local Module User's Manual Consider the network (CC-Link) parameters. C Controller Module User's Manual Network parameter setting (Utility Operation, Programming)
Page 234 2) Debug the user program. 3) Register the user program to the C Controller module. 4) Back up the standard RAM data not to lose them due to expiry of battery life. (Q12DCCPU-V only) Page 8-2, Section 8.1 1)) Operation Figure 6.10 Flowchart for CC-Link startup (continued)
Page 235 PREPARATORY PROCEDURES AND SETTING (3) Starting up the MELSECNET/H C Controller module Development environment (personal computer) MELSECNET/H Ethernet Figure 6.11 Configuration at MELSECNET/H startup Preparatory procedure Q Corresponding MELSECNET/H Consideration of network parameters Network System Reference Manual Consider the network (MELSECNET/H) parameters. (PLC to PLC network) C Controller Module User's Manual Network parameter setting...
Page 236 2) Debug the user program. 3) Register the user program to the C Controller module. 4) Back up the standard RAM data not to lose them due to expiry of battery life. (Q12DCCPU-V only) Page 8-2, Section 8.1 1)) Operation Figure 6.12 Flowchart for MELSECNET/H startup (continued)
Page 237 PREPARATORY PROCEDURES AND SETTING (b) GX Works2/GX Developer and SW3PVC-CCPU In troubleshooting according to the MELSECNET/H module manual, actions to be taken with GX Works2/GX Developer are as follows. Table 6.3 GX Works2/GX Developer and SW3PVC-CCPU GX Works2/GX Developer SW3PVC-CCPU Use the System information screen of C Controller setting PLC diagnostics utility.
Page 238 PREPARATORY PROCEDURES AND SETTING (4) Starting up the CC-Link IE controller network C Controller module Development environment (personal computer) CC-Link IE controller network Ethernet Figure 6.13 Configuration at CC-Link IE controller network startup Preparatory procedure Consideration of network parameters MELSEC-Q CC-Link IE Controller Consider the network (CC-Link IE controller network) Network Reference Manual parameters.
Page 239 2) Debug the user program. 3) Register the user program to the C Controller module. 4) Back up the standard RAM data not to lose them due to expiry of battery life. (Q12DCCPU-V only) Page 8-2, Section 8.1 1)) Operation Figure 6.14 Flowchart for CC-Link IE controller network startup (continued)
Page 240 PREPARATORY PROCEDURES AND SETTING (b) GX Works2/GX Developer and SW3PVC-CCPU When performing troubleshooting according to the CC-Link IE controller network module manual, actions to be taken with GX Works2/GX Developer are as follows. Table 6.4 GX Works2/GX Developer and SW3PVC-CCPU GX Works2/GX Developer SW3PVC-CCPU Use the CC-Link IE Controller Network diagnostics result...
Page 241 3) Register the user program to the C Controller module. 4) Back up the standard RAM data not to lose them due to expiry of battery life. (Q12DCCPU-V only) Page 8-2, Section 8.1 1)) Operation Figure 6.16 Flowchart for connecting GOT by microcomputer connection...
Page 242 Q06CCPU-V-B 6.4.1 Part names and functions of the Q12DCCPU-V Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The part names of the Q12DCCPU-V are shown by numbers given in the external views. MODE STOP RES. SEL. Hook a finger here to open the front cover.
Page 243 * 1 Keep the dummy CompactFlash card in a safe place after replacing it so that it can be used again. * 2 Operate the RUN/STOP/MODE and RESET/SELECT switches by hand. Using a tool such as a screwdriver can cause a failure. 6.4 Part Names and Functions - 25 6.4.1 Part names and functions of the Q12DCCPU-V...
Page 244 * 1 All of the LEDs turn off while the module is reset. * 2 When a system watchdog timer error occurs, the RUN and MODE LEDs turn off and the ERR. LED flashes. - 26 6.4 Part Names and Functions 6.4.1 Part names and functions of the Q12DCCPU-V...
Page 245 The error location can be identified by a value displayed on the 7- Flashing segment LED. Page 16-81, Section 16.5.1 (5)) Remark For the hardware self-diagnostic function, refer to the following. Page 16-75, Section 16.5.1 6.4 Part Names and Functions - 27 6.4.1 Part names and functions of the Q12DCCPU-V...
Page 246 * 2 The LED is flashing when a standard RAM data error detected. * 3 The LED is flashing when a battery-backed-up RAM data error detected. - 28 6.4 Part Names and Functions 6.4.1 Part names and functions of the Q12DCCPU-V...
Page 247 In normal operation mode unmounted. Page 6-67, Section 6.8.3) SEL. In hardware self- Used for the hardware self-diagnostic function. ( Page 16-75, Section diagnostic operation 16.5.1) mode 6.4 Part Names and Functions - 29 6.4.1 Part names and functions of the Q12DCCPU-V...
Page 248 * 4 When the SELECT position is held in either of the following conditions, the CompactFlash card is not unmounted. (The CF CARD LED does not flash.) • No CompactFlash card is installed. • The CompactFlash card has already been unmounted. - 30 6.4 Part Names and Functions 6.4.1 Part names and functions of the Q12DCCPU-V...
Page 249 PREPARATORY PROCEDURES AND SETTING 6.4.2 Part names and functions of the Q06CCPU-V(-B) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The part names of the Q06CCPU-V and Q06CCPU-V-B are shown by numbers given in external views of the Q06CCPU-V. The external views of the Q06CCPU-V-B are the same as those of the Q06CCPU-V except: •...
Page 250 PREPARATORY PROCEDURES AND SETTING Table 6.11 Part names Name Description For the indicator LEDs, refer to the following. Indicator LEDs (1) in this section Used to connect a 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 251 PREPARATORY PROCEDURES AND SETTING (1) Indicator LED specifications Q06CCPU-V Q06CCPU-V-B Q06CCPU-V Q06CCPU-V-B MODE MODE ERR. ERR. CF CARD CH2 SD/RD USER CH2 SD/RD USER CH1 10BASE-T/ 100BASE-TX Figure 6.28 Indicator LEDs (a) In normal operation mode (when the MODE LED is on (green)) The operation mode is changed by switches.
Page 252 PREPARATORY PROCEDURES AND SETTING (b) In hardware self-diagnostic operation mode (when the MODE LED is on (orange)) The operation mode is changed by switches. ( (2), (3) in this section) Table 6.13 Indicator LEDs and their states in hardware self-diagnostic operation mode Indicator LED Name LED status...
Page 253 PREPARATORY PROCEDURES AND SETTING (2) RUN/STOP/MODE switch operation STOP MODE Figure 6.29 The RUN/STOP/MODE switch Table 6.14 RUN/STOP/MODE switch operation Position Operation The C Controller module is operating. In normal operation mode (Output (Y) from a user program and writing to the buffer memory are enabled.) In hardware self- For the hardware self-diagnostic function, refer to the following.
Page 254 PREPARATORY PROCEDURES AND SETTING (3) RESET/SELECT switch operation RESET SEL. Figure 6.30 The RESET/SELECT switch Table 6.15 RESET/SELECT switch operation Position Operation When the RESET *2 *3 All LEDs turn off and the hardware is reset. position is held The module exits the reset status. •...
Page 255 PREPARATORY PROCEDURES AND SETTING Cable Connection Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains how to connect cables to the C Controller module. To fully utilize the C Controller module functionality and achieve a reliable system, wiring resistant to noise is required.
Page 256 (b) RS-232 cable For the RS-232 cable running outside from the control panel, always ground the shield section of the shielded cable. (c) USB cable (Q12DCCPU-V only) Use a USB cable of 3m (9.84 feet) or less. Remark For the EMC Directive, refer to the following manual.
Page 257 When connecting a development environment (personal computer) to a C Controller module, connect them on one-to-one (1:1) basis by using an Ethernet cable. * 1 For the Q12DCCPU-V, use an Ethernet cable (straight cable or crossing cable). For the Q06CCPU-V(-B), use an Ethernet cable (crossing cable).
Page 258 PREPARATORY PROCEDURES AND SETTING (b) How to configure network settings for the development environment (personal computer) The settings can be configured on the "Internet Protocol (TCP/IP) Properties" screen. ® ® (Example) On Microsoft Windows XP Professional Operating System 1) Select [Start]-[Control Panel], and click "Network and Internet Connections". 2) Click "Network Connections"...
Page 259 PREPARATORY PROCEDURES AND SETTING (3) Accessing the C Controller module from the development environment (personal computer) (a) Confirmation of power-on Check that the C Controller module has been started up (powered on). (b) The C Controller module is ready to connect to C Controller setting utility at the following timing.
Page 260 Communications with the C Controller module are available from C Controller utility after the connection is complete. In the tabs such as <<Module information >>, <<Event history>>, and <<Module monitoring>>, check that relevant information can be monitored. Figure 6.37 Module information tab (Q12DCCPU-V) - 42 6.6 Network Settings for 1:1 Connection...
Page 261 To change the default IP address of the C Controller module, perform the operations described below. • Default IP address of CH1: 192.168.3.3 • Default IP address of CH2: No setting (Q12DCCPU-V only) (a) Displaying the relevant tab Detail In the <<Online operation>> tab of C Controller setting utility, click the button and select the <<IP address>>...
Page 262 PREPARATORY PROCEDURES AND SETTING (c) Network settings for the development environment (personal computer) Change the network settings (IP address) of the development environment (personal computer) as needed, and shutdown the personal computer. (d) Connection to LAN Disconnect the Ethernet cable from the C Controller module and development environment (personal computer).
Page 263 PREPARATORY PROCEDURES AND SETTING (6) Precautions (a) Precautions for using two Ethernet channels (ports) (Q12DCCPU-V only) When using two channels as Ethernet ports, two different network addresses must be set for CH1 and CH2 of the C Controller module. In the above case, a response to the message received through each channel is sent as follows.
Page 264 (b) Flashing "01" or "02" of the 7-segment LED (Q12DCCPU-V only) At start-up of the C Controller module, "01" or "02" flashes on the 7-segment LED when the C Controller module is: •...
Page 265 PREPARATORY PROCEDURES AND SETTING Specifications, Installation, and Replacement of the Battery Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains specifications, installation, and replacement of the battery. 6.7.1 Battery specifications Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following table indicates the specifications of the batteries for the C Controller module.
Page 266 IMPORTANT A battery must be installed for operation. When the Q12DCCPU-V is operated without installing a battery and then the C Controller system is powered off or reset, the standard RAM or battery-backed-up RAM data may be damaged, or a file system error may occur.
Page 267 PREPARATORY PROCEDURES AND SETTING 6.7.3 Battery replacement Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the replacement of the C Controller module battery. The C Controller module battery is used for the following purposes. • Backup of the standard RAM files • Protection of the standard ROM files •...
Page 268 PREPARATORY PROCEDURES AND SETTING (b) When a battery error occurs 1) The ERR. LED turns on indicating a battery error (error code: 1600, BATTERY ERROR). The error code can be checked in the <<Module information>> tab of C Controller setting utility. 2) The date and time of the error, event No.
Page 269 25 days 5 years 5 years 25 days 25,800 hours 43,800 hours 600 hours 43,800 hours 43,800 hours 600 hours Q12DCCPU-V 2.96 years 5 years 25 days 5 years 5 years 25 days 40,000 hours 43,800 hours 600 hours 43,800 hours...
Page 270 PREPARATORY PROCEDURES AND SETTING POINT 1. Use the battery within the time shown by the guaranteed value of the battery life. 2. If the battery may be used exceeding the time shown by the guaranteed battery life value, perform the following. •...
Page 271 PREPARATORY PROCEDURES AND SETTING (4) Battery replacement procedure Before the C Controller module battery reaches the limit of its life, replace it by the following procedure. Before removing the battery, turn on the C Controller system power for 10 minutes or more.
Page 272 PREPARATORY PROCEDURES AND SETTING 6.7.4 When the module has been operated without battery Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section provides the precautions for having operated the module without battery. IMPORTANT A battery must be installed for operation. If the system has been operated with no battery installed, perform the shutdown operation before powering off or resetting the C Controller system.
Page 273 PREPARATORY PROCEDURES AND SETTING POINT Use the QBF_SetTime function when setting clock data from the user program. Calling a clock data setting function of ANSI-C or VxWorks does not set clock data correctly. (2) Shutdown operation required for powering off or resetting the C Controller system without a battery installed Perform the shutdown operation ( Page 6-58, Section 6.7.5 (1)) when powering...
Page 274 PREPARATORY PROCEDURES AND SETTING (3) Disabling battery error detection A battery error occurs if a battery is not installed in the C Controller module. To disable the battery error detection, perform the procedure (a) below. * 1 Occurrence of a battery error does not change the CPU operating status.(If it was in the RUN status, it remains in the RUN status.) (a) Disabling battery error detection 1) In the <<System settings>>...
Page 275 PREPARATORY PROCEDURES AND SETTING 6.7.5 Removing a battery before storage Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B To store the C Controller module with a battery removed, perform the shutdown operation, power off the C Controller system, and then remove the battery. IMPORTANT Data in the standard RAM, standard ROM being accessed, or battery-backed-up RAM may be corrupted or a file system error may occur if the procedure given below is not followed.
Page 276 PREPARATORY PROCEDURES AND SETTING (1) Shutdown operation (a) For the Q12DCCPU-V Determine a shutdown request signal (Xm) in advance. Create a program to perform the following operations by using the QBF_X_In_BitEx function or various file access (close) functions. 1) Turn the shutdown request signal (Xm: arbitrary) from off to on by using an external input.
Page 277 PREPARATORY PROCEDURES AND SETTING (b) For the Q06CCPU-V(-B) Determine a shutdown request signal (Xm) in advance. Create a program to perform the following operations by using the QBF_X_In_BitEx function, QBF_ShutdownRom function, and various file access (close) functions. (Use "Standard ROM shutdown status" of the QBF_ReadStatusEx function as necessary.) 1) Turn the shutdown request signal (Xm: arbitrary) from off to on by using an external input.
Page 278 PREPARATORY PROCEDURES AND SETTING Inserting/Removing a CompactFlash Card and Access Stop Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains how to insert and remove a CompactFlash card and how to stop access to the CompactFlash card. IMPORTANT Before handling a CompactFlash card, touch a grounded metal object to discharge the static electricity from the human body.
Page 279 PREPARATORY PROCEDURES AND SETTING Insert or remove a CompactFlash card according to the following procedure. Especially, when removing or replacing the CompactFlash card, stop accessing to the CompactFlash card. Removal or replacement of Insert a CompactFlash card CompactFlash card Has the C Controller system been powered off? File writing to the CompactFlash card is stopped?
Page 280 CompactFlash card slot Dummy CompactFlash card Figure 6.48 Removing the dummy CompactFlash card (for the Q12DCCPU-V) 1) Put your finger on the bottom of the C Controller module front cover, and open the front cover. 2) Press the EJECT button to remove the dummy CompactFlash card.
Page 281 EJECT button. CompactFlash card slot CompactFlash card Figure 6.50 Removing the CompactFlash card (for the Q12DCCPU-V) 1) Put your finger on the bottom of the C Controller module front cover, and open the front cover. 2) Press the EJECT button to remove the CompactFlash card.
Page 282 PREPARATORY PROCEDURES AND SETTING 6.8.2 Stopping access to the CompactFlash card Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B To replace the CompactFlash card while the C Controller system power is on, access to the CompactFlash card must be stopped. This section describes how to stop access to the CompactFlash card.
Page 283 PREPARATORY PROCEDURES AND SETTING 1) Turn the file access stop request signal (Xn: arbitrary) from off to on by using an external input. 2) Stop the file access to the CompactFlash card, and close the opened files. (Use the QBF_X_In_BitExXm function and the close or fclose function in programming so that this operation will be performed when Xn turns on.) 3) Unmount the CompactFlash card by using the QBF_UnmountCfCard function.
Page 284 PREPARATORY PROCEDURES AND SETTING (b) When inserting a CompactFlash card while power is on IMPORTANT Before the following operation, touch a grounded metal object to discharge the static electricity from the human body. Failure to do so may cause failure of the module or malfunction. Insert a CompactFlash card according to the above procedure.
Page 285 PREPARATORY PROCEDURES AND SETTING 6.8.3 Unmounting the CompactFlash card by the RESET/SELECT switch Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The CompactFlash card can be unmounted by the RESET/SELECT switch. Use this unmounting method only when file writing to the CompactFlash card is not in execution.
Page 286 PREPARATORY PROCEDURES AND SETTING 6.8.4 Measures against static electricity for commercially available CompactFlash cards in compliance with the EMC directives Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The C Controller system may be affected by static electricity discharged to a commercially available CompactFlash card.
Page 287 PREPARATORY PROCEDURES AND SETTING (2) Insulation sheet example Single-sided adhesive sheet for electric insulation • Base material: 50 m-PET film (UL compliant) • Adhesive: Acrylic pressure sensitive adhesive (3) Precautions The insulation sheet must be as large as the CompactFlash card. Make sure that it is not oversized and does not cover the groove (connector guide) on the side of the CompactFlash card.
Page 288 PREPARATORY PROCEDURES AND SETTING 6.8.5 Life of CompactFlash card Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B A life of CompactFlash card is limited (a limited number of writing). The life calculation method is shown below. The actual life varies depending on operating conditions. Use this as a guide to estimate the time for replacement.
Page 289 PREPARATORY PROCEDURES AND SETTING Checking the Number of Erasures on the Standard ROM Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The standard ROM built in the C Controller module is used to save various parameters and user programs. Since a flash ROM is used as the standard ROM, the number of writes (life) is limited.
Page 290 • The module initialization setting procedure of the C Controller module Page 6-77, Section 6.10.1 (6)) (2) Changing mode of Q12DCCPU-V (Basic mode/Extended mode) The mode switching of the modules can be performed by the initialization setting. For operation of switching to the extended mode, refer to the following manual.
Page 291 Is the C Controller module operating normally? Please consult your local Mitsubishi service center or representative, explaining a detailed description of the problem. Figure 6.54 Operating procedure 6.10 Initializing/Changing Mode of C Controller Module - 73 6.10.1 Initializing/Changing mode of Q12DCCPU-V...
Page 292 The "STARTUP.CMD" saved in the standard RAM before execution of the default IP setting mode is renamed to "STARTUP.BAK" and saved to the standard RAM. (If "STARTUP.BAK" already exists, it is overwritten.) - 74 6.10 Initializing/Changing Mode of C Controller Module 6.10.1 Initializing/Changing mode of Q12DCCPU-V...
Page 293 Before writing parameters, open the <<Online operation>> tab and select "Clear all parameter before writing" in the "Write parameters" area. Resetting or restarting the C Controller module sets the module into the initialized status. 6.10 Initializing/Changing Mode of C Controller Module - 75 6.10.1 Initializing/Changing mode of Q12DCCPU-V...
Page 294 2. If the C Controller module does not operate normally even after execution of the "Default IP setting" mode, perform the module initialization setting procedure. Page 6-77, Section 6.10.1 (6)) - 76 6.10 Initializing/Changing Mode of C Controller Module 6.10.1 Initializing/Changing mode of Q12DCCPU-V...
Page 295 ( Page 8-7, Section 8.2.1) POINT When using Q12DCCPU-V with a serial number whose first five digits are "15102" or later • When performing the initialization, select Mode '11' module initialization setting (Basic mode). When Mode '12' module initialization setting (Extended mode) is selected, the module cannot be connected to SW3PVC-CCPU.
Page 296 Do not power off or reset the C Controller module while the standard RAM is being formatted. Doing so will cause the standard RAM to be formatted again when the C Controller module is started at the next time. - 78 6.10 Initializing/Changing Mode of C Controller Module 6.10.1 Initializing/Changing mode of Q12DCCPU-V...
Page 297 2.Do not power off or reset the C Controller module while the standard RAM is being formatted. Doing so will cause the standard RAM to be formatted again when the C Controller module is started at the next time. 6.10 Initializing/Changing Mode of C Controller Module - 79 6.10.1 Initializing/Changing mode of Q12DCCPU-V...
Page 298 PREPARATORY PROCEDURES AND SETTING Remark For script files and sample programs, refer to the following. C Controller Module User's Manual (Utility Operation, Programming) - 80 6.10 Initializing/Changing Mode of C Controller Module 6.10.1 Initializing/Changing mode of Q12DCCPU-V...
Page 299 PREPARATORY PROCEDURES AND SETTING 6.10.2 Setting the Q06CCPU-V(-B) back to the factory-set status Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Data such as parameter files saved in the C Controller module can be initialized to the factory-set status by performing the following operations. • Executing the "Default IP setting" mode of the C Controller module Page 6-84, Section 6.10.2 (3))
Page 300 PREPARATORY PROCEDURES AND SETTING (1) Applications The C Controller module can be restored by setting it to the initialized status if it does not operate normally by the following reasons. • Execution of a user program registered to a script file •...
Page 301 PREPARATORY PROCEDURES AND SETTING (2) Settings and file conditions after the operations The following table indicates the settings and file conditions after executing the "Default IP setting" mode or formatting the standard ROM. Table 6.22 File conditions Settings and file conditions File type Standard ROM Default IP setting...
Page 302 PREPARATORY PROCEDURES AND SETTING (3) Default IP setting mode To set the IP address back to default, start the C Controller module in the hardware self-diagnostic mode ( Page 16-84, Section 16.5.2), and then execute the "Default IP setting" mode. 1) Start up the C Controller module in the hardware self-diagnostic mode (with the RUN/STOP/MODE switch set to MODE).
Page 303 PREPARATORY PROCEDURES AND SETTING (4) Formatting the standard ROM The following describes how to format the standard ROM and operations after formatting. Each file in the standard ROM will be deleted after formatting the standard ROM. Before operating the procedure provided below, back up necessary data, user programs, and parameter files.
Page 304 PREPARATORY PROCEDURES AND SETTING 2) By creating a script file in the CompactFlash card • Write the following script file "STARTUP.CMD" to the CompactFlash card, insert it into the C Controller module, and then start the C Controller module. (The RUN LED flashes during processing the script file "STARTUP.CMD".) <Sample script file for standard ROM formatting >...
Page 305 PREPARATORY PROCEDURES AND SETTING Remark For script files and sample programs, refer to the following. C Controller Module User's Manual (Utility Operation, Programming) 6.10 Initializing/Changing Mode of C Controller Module - 87 6.10.2 Setting the Q06CCPU-V(-B) back to the factory-set status...
Page 306 Incorporate measures other than this function if the C Controller system's safety must be maintained against illegal access from an external device. Mitsubishi Electric Corporation cannot be held responsible for any system problems that may occur from illegal access.
Page 307 PREPARATORY PROCEDURES AND SETTING 6.11.2 Setting a login user Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section describes how to set a login user and precautions. (1) Default login user and setting method (a) Default login user The default login user of the C Controller module is as follows.
Page 308 PREPARATORY PROCEDURES AND SETTING (b) Setting a login user To add a login user account other than the default, or to delete or change any existing account, use the functions offered by the loginLib library in a script file or user program.
Page 309 PREPARATORY PROCEDURES AND SETTING (2) Precautions (a) Application of the login user setting of the C Controller module The login user setting of the C Controller module restricts users and module setting operations. This setting does not completely prevent unauthorized access form outside. (b) Ensuring safety from illegal access from outside To ensure the C Controller system safety against unauthorized access from outside, take appropriate measures.
Page 310 PREPARATORY PROCEDURES AND SETTING 6.12 Maintenance and Inspection Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B WARNING Do not touch any terminal while power is on. Doing so will cause electric shock. Correctly connect the battery connector. Do not charge, disassemble, heat, short-circuit, solder, or throw the battery into the fire.
Page 311 PREPARATORY PROCEDURES AND SETTING CAUTION Before performing online operations (especially program modification, forced output, and operation status change), read relevant manuals carefully and ensure the safety. Improper operation may damage machines or cause accidents. Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire.
Page 312 Mitsubishi service center or 7-segment LED Check for on/off of the LED. representative, explaining the Page 16-83, Section (Q12DCCPU-V only) details of the problem. 16.5.1 (5) (c) Lit when the input is on. Input module Off when the input is off.
Page 313 PREPARATORY PROCEDURES AND SETTING 6.12.2 Periodical inspection Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the items to be inspected once or twice every six months or every year. Note that these inspections are required when the system is moved or modified including re-wiring.
Page 314 I/O NUMBER ASSIGNMENT CHAPTER 7 I/O NUMBER ASSIGNMENT Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This chapter explains the I/O number assignment that is required for data communications between the C Controller module and I/O modules and intelligent function modules. Number of Base Units and Number of Slots...
Page 315 I/O NUMBER ASSIGNMENT (2) Precautions on the number of mounted modules The number of mounted modules must be within the range of available slots. Even if the total number of slots on the main 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 the modules are mounted in the allowed number of slots.
Page 316 I/O NUMBER ASSIGNMENT Connecting Extension Base Units and Setting the Number of Stages Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The extension base unit models, Q5 B and Q6 B, are connectable. The Q6 RB and QA1S6 B cannot be used. (1) Extension stage number setting and setting order For each extension base unit, set the extension stage number with the stage number setting connector on the unit.
Page 317 I/O NUMBER ASSIGNMENT (2) Precautions for extension stage number setting (a) Extension stage number setting order The extension stage numbers must be set consecutively. Even if any extension stage number is skipped when the Auto mode is active for base unit assignment ( Page 7-7, Section 7.3 (1)), 0 slot is assigned to the skipped stage and the number of available slots does not increase.
Page 318 I/O NUMBER ASSIGNMENT (b) Duplicated extension stage number setting The same extension stage number cannot be assigned to more than one extension base unit. Main base unit Q312B Slot number Power supply C Controller module module Extension base unit Q68B Extension 1 The same extension stage number cannot be set!
Page 319 I/O NUMBER ASSIGNMENT (c) Attaching two or more connectors to different positions or attaching no connector The system is not operable when two or more extension stage setting connectors are attached to different positions or no connector is attached. Main base unit Q312B Slot number Power supply...
Page 320 I/O NUMBER ASSIGNMENT Base Unit Assignment (Base Mode) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The Auto and Detail modes are available for the C Controller module to assign the modules to the main base unit, slim type main base unit, and extension base units.
Page 321 I/O NUMBER ASSIGNMENT (b) For a 5-slot base unit: Five slots are occupied. Main base unit Q35B Power supply C Controller module module Extension base unit Q65B Figure 7.7 5-slot base units (c) For a 8-slot base unit: Eight slots are occupied. Main base unit Q38B Slot number...
Page 322 I/O NUMBER ASSIGNMENT (d) For a 12-slot base unit: Twelve slots are occupied. Main base unit Q312B Slot number Power supply C Controller module module Extension base unit Q612B Figure 7.9 12-slot base units 7.3 Base Unit Assignment (Base Mode)
Page 323 I/O NUMBER ASSIGNMENT (2) Detail mode In Detail mode, the number of modules can be set for each base unit in the <<I/O assignment settings>> tab of C Controller setting utility. (a) Application Since an empty slot occupies one slot if 0 point is assigned to it, this mode is used to make unused slots unassigned.
Page 324 I/O NUMBER ASSIGNMENT 2) When the set number of slots is less than the number of slots used on the base unit The slots after the set quantity are disabled. For example, if the number of slots to be used is set to eight on a 12-slot base unit, the right four slots are disabled.
Page 325 I/O NUMBER ASSIGNMENT (3) Base mode setting in C Controller setting utility Figure 7.12 I/O assignment settings (a) Base model Enter the base unit model name within 16 characters. The C Controller module does not recognize this setting. (Use this setting as a note.) (b) Power model Enter the power supply module name within 16 characters.
Page 326 I/O NUMBER ASSIGNMENT What is I/O Number? Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B I/O numbers represent addresses that are used in user programs to perform the following: • Inputting ON/OFF data into the C Controller module • Outputting ON/OFF data from the C Controller module to the outside (1) Inputting and outputting ON/OFF data Input (X) is used to input ON/OFF data to the C Controller module.
Page 327 I/O NUMBER ASSIGNMENT I/O Number Assignment Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B 7.5.1 I/O numbers of a base unit Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The C Controller module assigns I/O numbers when it is powered on or reset. Figure 7.14 shows an example of I/O assignment when a base unit is set in Auto mode and no I/O assignment is manually performed.
Page 328 I/O NUMBER ASSIGNMENT POINT The C Controller module can control the system even if I/O numbers are not assigned in C Controller setting utility. Assign I/O numbers according to the following. (1) Number of slots of base units The number of slots of each base unit is set in the base mode. ( Page 7-7, Section 7.3) (a) In Auto mode...
Page 329 I/O NUMBER ASSIGNMENT (5) I/O numbers of empty slots To an empty slot on a base unit, where no I/O module or intelligent function module is mounted, the number of points set in the <<System settings>> tab of C Controller setting utility is assigned.
Page 330 I/O NUMBER ASSIGNMENT I/O Assignment by C Controller Setting Utility Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section describes I/O assignment using C Controller setting utility. 7.6.1 Purposes of I/O assignment by C Controller setting utility Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Use C Controller setting utility for I/O assignment in the following cases.
Page 331 I/O NUMBER ASSIGNMENT (8) Setting C Controller module operation for an intelligent function module hardware error The operation status (continue/stop) of the C Controller module can be set for the time when a hardware error occurs in an intelligent function module. ( Page 4-37, Section 4.10) POINT...
Page 332 I/O NUMBER ASSIGNMENT 7.6.2 Details of I/O assignment by C Controller setting utility Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The "Type" (module type), "Points" (I/O points), and "Start X/Y" (start I/O number) can be assigned for each slot of base units. For example, to change the I/O points of a specific slot, only the respective point value can be changed.
Page 333 I/O NUMBER ASSIGNMENT (b) Type (C Controller module uses this setting.) Select the type of each module from the following. • Empty (Empty slot) • Input (Input module) • Hi Input (High-speed input module) • Output (Output module) • I/O Mix (I/O combined module) •...
Page 334 I/O NUMBER ASSIGNMENT (2) Precautions for I/O assignment (a) I/O-assigned slot status When I/O assignment is set for a slot, the setting has priority over the actual module-mounting status. 1) When the set number of points is less than the points of the actual I/O module The I/O points for the actual module are decreased.
Page 335 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 exceeds FFF , an intelligent function module assignment error (error code: 2124, SP.UNIT LAY ERR.) will occur. 7.6 I/O Assignment by C Controller Setting Utility - 22 7.6.2 Details of I/O assignment by C Controller setting utility...
Page 336 I/O NUMBER ASSIGNMENT (b) Precautions on automatic assignment of start X/Y When a start X/Y has not been entered, the C Controller module automatically assigns it. Because of this, the start X/Y setting of a slot may overlap with the one assigned by the C Controller module in the case of 1) or 2) below.
Page 337 I/O NUMBER ASSIGNMENT I/O Assignment Example Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section provides an example of I/O number assignment by using C Controller setting utility. (1) Changing the points assigned to an empty slot from 16 to 32 To an empty slot (Slot No.3), 32 points are assigned so that I/O numbers for Slot No.4 or higher will not change when a 32-point input module is mounted in the slot in the future.
Page 338 I/O NUMBER ASSIGNMENT (b) I/O assignment setting in C Controller setting utility In the <<I/O assignment settings>> tab of C Controller setting utility, set Slot No.3 to "32 points". Select 32 points. (When the type is not selected, the type of the installed module will be selected.) Figure 7.20 I/O assignment setting (when changing the points for empty slot No.3) (c) I/O number assignment after change...
Page 339 I/O NUMBER ASSIGNMENT (2) Changing the I/O numbers of a slot I/O numbers of Slot No.3 are changed to X200 to X21F so that I/O numbers for Slot No.4 or higher will not change when a 32-point input module is mounted in the slot in the future.
Page 340 I/O NUMBER ASSIGNMENT (b) I/O assignment setting in C Controller setting utility In the <<I/O assignment settings>> tab of C Controller setting utility, set "200" for Slot No.3 and "70" for Slot No.4. Set "200" for the start I/O number. Set "70"...
Page 341 I/O NUMBER ASSIGNMENT Checking I/O Numbers Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The modules mounted with the C Controller module and respective I/O numbers can be checked in "System information" in the <<Module monitoring>> tab of C Controller setting utility. For C Controller setting utility, refer to the following.
Page 342 MEMORIES AND FILES CHAPTER 8 MEMORIES AND FILES Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This chapter explains the memories and file operations of the C Controller module and the precautions for them. Memories of the C Controller Module Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the user memories and system memory used for the C Controller module.
Page 343 MEMORIES AND FILES 1) Standard RAM The standard RAM stores C Controller module parameters and writes, reads and saves data such as a user program file. Backup the data stored in the standard RAM since the data in the standard RAM may be lost if the battery life is expired.
Page 344 RAM or CompactFlash card. • Q12DCCPU-V with a serial number whose first five digits are "12042" or later. If parameters are stored in different drives, the parameters in the drive where the C Controller setting parameters are stored are valid.
Page 345 These drive names are also used for specifying the target when reading and writing a file to and from the development environment (personal computer) using FTP. Table 8.3 Memories and drive names Drive name Memory name Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Standard RAM /RAM...
Page 346 Page 6-81, Section 6.10.2) * 3 128K bytes for the following C Controller modules. • Q12DCCPU-V with a serial number whose first five digits are "12041" or higher * 4 For CompactFlash card formatting, refer to the manual for the CompactFlash card used.
Page 347 MEMORIES AND FILES 8.1.2 System memory Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The system memory is a memory used to store data of the operating system, system software, VxWorks image files, etc. of the C Controller module. The system memory is controlled by the following drive name.
Page 348 MEMORIES AND FILES File Operation and Handling Precautions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B 8.2.1 File operation Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Files stored in the standard RAM, standard ROM, or a CompactFlash card can be read, written, and verified with the following. 1) C Controller setting utility...
Page 349 * 3 To restore a parameter file from a CompactFlash card or another memory, copy all the previously backed-up data (*2 above) to the "/RAM" or "/ROM" drive after the following operation. Q12DCCPU-V: "/RAM" drive formatting ( Page 6-77, Section 6.10.1 (6)) Q06CCPU-V(-B): "/ROM"...
Page 350 MEMORIES AND FILES 8.2.2 Precautions for handling files Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains precautions for handling files of the C Controller module. (1) When writing a file The following are precautions for writing a user file using FTP or copy registration from a CompactFlash card to the standard RAM or standard ROM.
Page 351 Table 8.8 Parameter storage location directories Directory Remarks /RAM/Melco/ Q12DCCPU-V only /RAM/Mqbf/ /ROM/Melco/ Q06CCPU-V(-B) only /ROM/Mqbf/ /CF/Melco/ Only when CompactFlash card is inserted...
Page 352 U3En\G10000 to 24335 * 1 These devices cannot be used with the following C Controller modules. • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier • Q06CCPU-V(-B) * 2 The setting range can be changed from the <<Device settings>> tab of the C Controller setting utility.
Page 353 DEVICE DESCRIPTION I/O Device This section explains devices that can be used to suit the user application. 9.2.1 Input (X) Input is used for giving commands and data to the C Controller module from an external device such as a push-button switch, a selector switch, a limit switch, or a digital switch. POINT (1) Writing to the input (X) is ignored.
Page 354 DEVICE DESCRIPTION Internal User Device This section explains devices which are created on the work RAM of the C Controller module. This is a device that can be used to suit the user application. An internal user device is created with device functions. For the device functions, refer to the following.
Page 355 DEVICE DESCRIPTION Link Direct Device This device directly accesses a link device in the CC-Link IE controller network module or in the MELSECNET/H module. Link devices in the CC-Link IE controller network module or MELSECNET/H module can be read or written by user programs, independently of the link device refresh of the C Controller module.
Page 356 DEVICE DESCRIPTION Module Access Device 9.6.1 Intelligent function module device This device is for directly accessing the buffer memory of an intelligent function module installed in the base unit from the C Controller module. 9.6.2 Multiple CPU area device This device accesses the CPU shared memory in each CPU module of the multiple CPU system.
Page 357 Redundant CPUs cannot be used in multiple CPU systems. For applicable module versions, refer to the following. Page 11-11, Section 11.2 Table 10.1 Applicable CPU modules Model CPU module Q06CCPU-V, Q06CCPU-V-B, Q12DCCPU-V (Basic mode), C Controller module Q12DCCPU-V (Extended mode), Q24DHCCPU-V, Q24DHCCPU-LS Q00CPU, Q01CPU Basic model QCPU...
Page 358 MULTIPLE CPU SYSTEM OVERVIEW (2) Controlling I/O modules and intelligent function modules In a multiple CPU system, it is necessary to specify which CPU module controls which I/O module or intelligent function module (control CPU setting). Slot number Control CPU setting Control with CPU module 1.
Page 359 MULTIPLE CPU SYSTEM OVERVIEW (3) Application example of a multiple CPU system The optimum load distribution system can be configured when programmable controller CPUs process time-critical cyclic tasks and the C Controller module performs processing of C language information. By adding a Motion CPU to the multiple CPU system, motion control, sequence control, and information processing (data processing and communication) can be integrated into an advanced system.
Page 360 No.1, refer to the following. QCPU User's Manual (Multiple CPU System) For the system configuration where a Q24DHCCPU-V/-VG/-LS, Q26DHCCPU-LS, or Q12DCCPU-V (Extended mode) C Controller module is set as CPU No.1, refer to the following. MELSEC-Q C Controller Module User's Manual...
Page 361 B type extension base unit B type extension base unit * 1 The Q12DCCPU-V and a Motion CPU cannot be installed on the same base unit. * 2 To a Motion CPU, a CompactFlash card and a battery cannot be installed.
Page 362 MULTIPLE CPU SYSTEM CONFIGURATION (2) When using the slim type main base unit (Q3 CompactFlash card (sold separately) Battery C Controller module *1*2 Slim type main base unit Slim type power supply module, I/O module, intelligent function module * 1 Use a slim type power supply module. The current consumption must be the rated output current or less.
Page 363 B extension base unit B extension base unit * 1 The Q12DCCPU-V and a Motion CPU (except the Q172DCPU and Q173DCPU) cannot be installed on the same base unit. * 2 To a Motion CPU, a CompactFlash card and a battery cannot be installed.
Page 364 MULTIPLE CPU SYSTEM CONFIGURATION 11.1.2 Connection with a development environment Configurations of a development environment in a single CPU system can be applied to multiple CPU systems. ( Page 2-5, Section 2.1.2) 11.1.3 Connection with peripheral devices Configurations of peripheral devices in a single CPU system can be applied to multiple CPU systems.
Page 365 MULTIPLE CPU SYSTEM CONFIGURATION 11.1.4 System configuration overview (when CPU No.1 is a C Controller module) (1) When using the main base unit (Q3 Main base unit..A 32-point module is mounted on each slot Q312B (12 slots occupied) ..Slot number ..
Page 366 <<Multiple CPU settings>> tab of C Controller setting utility. • For details of the Motion CPU, refer to the manual for the Motion CPU. • When the Q12DCCPU-V is CPU No.1, no Motion CPU can be installed. When the Q06CCPU-V(-B) is CPU No.1, the Q172DCPU and Q173DCPU cannot be installed.
Page 367 MULTIPLE CPU SYSTEM CONFIGURATION (2) When using the slim type base unit (Q3 Slim type main base unit ..A 32-point module is mounted on each slot Q35SB (5 slots occupied) ..Slot number ..I/O number Slim type power supply module CPU module 2 CPU module 1 Figure 11.5 Configuration example of a system using a slim type base unit...
Page 368 MULTIPLE CPU SYSTEM CONFIGURATION (3) When using the multiple CPU high speed main base unit (Q3 Multiple CPU high speed main base unit ... A 32-point module is mounted on each slot Q312DB (12 slots occupied) ..Slot number ..I/O number Q series power CPU module 4 CPU module 3...
Page 369 <<Multiple CPU settings>> tab of C Controller setting utility. • For details of the Motion CPU, refer to the manual for the Motion CPU. • When the Q12DCCPU-V is CPU No.1, only the Q172DCPU and Q173DCPU can be installed.
Page 370 Q173HCPU-T : No restrictions * 1 The Q12DCCPU-V and a Motion CPU cannot be installed on the same base unit. * 2 The versions can be applied to multiple CPU systems when the QBF_MotionDDWR or QBF_MotionDDRD function is used in the user program.
Page 371 MULTIPLE CPU SYSTEM CONFIGURATION Remark For CPU modules that can be used when a programmable controller CPU is CPU No.1, refer to the following. QCPU User's Manual (Multiple CPU System) 11.2 Applicable Modules - 12 11.2.1 Applicable CPU modules...
Page 372 MULTIPLE CPU SYSTEM CONFIGURATION 11.2.2 Precautions for using I/O modules and intelligent function modules (1) Applicable I/O modules All I/O modules (QX and QY ) can be used in the multiple CPU system. Any of CPU No.1 to CPU No.4 can be set as a control CPU for each of them. (2) Applicable intelligent function modules (a) When using an intelligent function module in a multiple CPU system The function version of the intelligent function module must be B or later.
Page 373 * 1 When the interrupt event setting is specified in the following C Controller, up to 64 modules can be inserted. • Q12DCCPU-V with a serial number whose first five digits are "12042" or later. * 2 The module is available only when the interrupt module is selected by setting the function selector switch (SW2) to OFF.
Page 374 MULTIPLE CPU SYSTEM CONFIGURATION (2) Combinations of power supply modules and base units Some restrictions are applied to the combinations of power supply modules and base units. Page 11-2, Section 11.1.1) (3) Precautions for GOT connection The GOTs that can be used for the C Controller module are the same as those usable in a single CPU system.
Page 375 Q06CCPU -V/-LS CPU No.1) Universal Q172HCPU-T -V-B Model QCPU Q173HCPU Q173HCPU-T (1) in this Q12DCCPU-V 0 to 3 0 to 3 0 to 1 section Q06CCPU-V (2) in this 0 to 3 0 to 3 0 to 3 0 to 1...
Page 376 Q06CCPU-V-B section : N/A (1) When CPU No.1 is the Q12DCCPU-V The positions of respective CPU modules are shown in Table 12.4. (a) Mounting position of a C Controller module Up to four C Controller modules can be mounted on the CPU slot (the slot on the right of the power supply module) and Slot 0 to Slot 2 of the main base unit.
Page 377 CONCEPT OF MULTIPLE CPU SYSTEM POINT When a C Controller module is used, "CPU (Empty)" cannot be set for a slot located between CPU modules. Since no priority in the mounting order is provided for C Controller modules and Motion CPUs, any one of them can be installed to an empty slot without shifting the rightmost CPU module to the right.
Page 378 CONCEPT OF MULTIPLE CPU SYSTEM Table 12.4 CPU module positions (excluding Q24DHCCPU-V/-LS) : Slot number CPU module position No. of CPUs * 1 No. of CPUs indicates the value set in "Number of CPUs" in the <<Multiple CPU settings>> tab of C Controller setting utility.
Page 379 CONCEPT OF MULTIPLE CPU SYSTEM Table 12.5 CPU module positions (including Q24DHCCPU-V/-LS) : Slot number CPU module position No. of CPUs * 1 No. of CPUs indicates the value set in "Number of CPUs" in the <<Multiple CPU settings>> tab of C Controller setting utility.
Page 380 CONCEPT OF MULTIPLE CPU SYSTEM (2) When CPU No.1 is the Q06CCPU-V(-B) The positions of respective CPU modules are shown in Table 12.6. (a) Mounting position of a C Controller module Up to four C Controller modules can be mounted on the CPU slot (the slot on the right of the power supply module) and Slot 0 to Slot 2 of the main base unit.
Page 381 CONCEPT OF MULTIPLE CPU SYSTEM Table 12.6 CPU module positions (excluding Q24DHCCPU-V/-LS) : Slot number CPU module position No. of CPUs * 1 No. of CPUs indicates the value set in "Number of CPUs" in the <<Multiple CPU settings>> tab of C Controller setting utility.
Page 382 CONCEPT OF MULTIPLE CPU SYSTEM Table 12.7 CPU module positions (including Q24DHCCPU-V/-LS) : Slot number CPU module position No. of CPUs * 1 No. of CPUs indicates the value set in "Number of CPUs" in the <<Multiple CPU settings>> tab of C Controller setting utility.
Page 383 CONCEPT OF MULTIPLE CPU SYSTEM 12.2 CPU No. of CPU Module (1) CPU No. assignment CPU numbers are used to identify each CPU module configured in a multiple CPU system. CPU No.1 is assigned to the CPU slot, and CPU No.2, No.3, and No.4 are assigned to the slots starting from the right of the CPU slot.
Page 384 CONCEPT OF MULTIPLE CPU SYSTEM The following are CPU No. application examples. • Diagnosing the communication from the <<Communication diagnostics>> tab of C Controller setting utility Slot number CPU number Ethernet Communicates with CPU No.2. Select No.2. Development environment (personal computer) Figure 12.4 Target setting in C Controller setting utility •...
Page 385 CONCEPT OF MULTIPLE CPU SYSTEM 12.3 I/O Number Assignment In the multiple CPU system, I/O numbers are used for communication between each CPU module and I/O modules or intelligent function modules, and for communication between different CPU modules. 12.3.1 I/O number assignment for the module The position (slot) of the I/O number 00 in the multiple CPU system is different from that in the single CPU system.
Page 386 CONCEPT OF MULTIPLE CPU SYSTEM 12.3.2 I/O number of each CPU module In a multiple CPU system configuration, a specific I/O number is assigned to each CPU module for identification. Each of these I/O number is fixed to the corresponding slot and cannot be changed in the <<I/O assignment settings>>...
Page 387 CONCEPT OF MULTIPLE CPU SYSTEM 12.4 Access Ranges Between a CPU Module and Other Modules 12.4.1 Access to controlled modules A CPU module can read and write buffer memory data of the I/O modules and intelligent function modules that are controlled by the CPU module. ( Page 4-4, Section 4.2) 12.4.2 Access to non-controlled modules...
Page 388 CONCEPT OF MULTIPLE CPU SYSTEM (1) Input (X) loading Whether to load inputs from input modules and intelligent function modules controlled by other CPUs is determined by the "I/O sharing when using Multiple CPUs" parameter in the <<Multiple CPU settings>> tab of C Controller setting utility. I/O sharing when using Multiple CPUs All CPUs can read all inputs: "All CPUs can read all inputs"...
Page 389 CONCEPT OF MULTIPLE CPU SYSTEM 2) Input (X) data are loaded from the modules indicated in Table 12.10, which are mounted on a main base unit or extension base units. Table 12.10 Modules from which inputs can be loaded Type setting in the <<I/O assignment settings>>...
Page 390 CONCEPT OF MULTIPLE CPU SYSTEM (2) Output (Y) loading Whether to load outputs from output modules and intelligent function modules controlled by other CPUs is determined by the "I/O sharing when using Multiple CPUs" parameter in the <<Multiple CPU settings>> tab of C Controller setting utility. I/O sharing when using Multiple CPUs All CPUs can read all outputs: "All CPUs can read all outputs"...
Page 391 CONCEPT OF MULTIPLE CPU SYSTEM 2) Output (Y) data are loaded from the modules indicated in Table 12.11, which are mounted on a main base unit and extension base units. Table 12.11 Modules from which outputs are loaded Type setting in the <<I/O assignment settings>>...
Page 392 CONCEPT OF MULTIPLE CPU SYSTEM (3) Output to output modules and intelligent function modules On/off data cannot be output to non-controlled modules. Even if turning on or off the output of an output module or intelligent function module controlled by another CPU is attempted from a C Controller module, no output is made to the output module or intelligent function module.
Page 393 CONCEPT OF MULTIPLE CPU SYSTEM (b) Writing to the buffer memory Data cannot be written to the buffer memory of any intelligent function module controlled by another CPU. If writing to an intelligent function module controlled by another CPU is attempted, a non-controlled module write error (return value: -28654) occurs.
Page 394 CONCEPT OF MULTIPLE CPU SYSTEM 12.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 are controlled by another CPU is not accessible by a user program.
Page 395 CONCEPT OF MULTIPLE CPU SYSTEM 12.6 Resetting CPU Modules The entire multiple CPU system can be reset by resetting CPU No.1. CPU modules other than CPU No.1, I/O modules, and intelligent function modules on the system will be all reset when CPU No.1 is reset. When a stop error has occurred on any of the CPU modules on the multiple CPU system, reset CPU No.1 or restart the multiple CPU system (power on on).
Page 396 CONCEPT OF MULTIPLE CPU SYSTEM 12.7 When a CPU Module Stop Error Occurs The behavior of a multiple CPU system depends on whether a stop error occurs in CPU No.1 or in any of CPU No.2 to No.4. (1) When a stop error occurs in CPU No.1 If a stop error occurs in CPU No.1, the multi CPU error (error code: 7000, MULTI CPU DOWN) occurs in all of the other CPU modules, and the multiple CPU system stops.
Page 397 CONCEPT OF MULTIPLE CPU SYSTEM POINT When a stop error is detected in a CPU, a multi CPU error (error code: 7000, MULTI CPU DOWN) occurs in the CPU. Depending on the timing of error detection, "MULTI CPU DOWN" may be detected from a CPU that was placed in the "MULTI CPU DOWN"...
Page 398 CONCEPT OF MULTIPLE CPU SYSTEM (3) Restoring the system When a C Controller is CPU No.1, restore the system in the following procedure. 1) Check the No. of the faulty CPU and the error cause on the System information screen opened from the <<Module monitoring>> tab of C Controller setting utility.
Page 399 COMMUNICATIONS BETWEEN CPU MODULES CHAPTER 13 COMMUNICATIONS BETWEEN CPU MODULES Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This chapter explains how the C Controller module can intercommunicate with a programmable controller CPU or Motion CPU in a multiple CPU system. Table 13.1 List of the functions available between C Controller module and programmable controller CPU...
Page 400 COMMUNICATIONS BETWEEN CPU MODULES 13.1 Data Communications by MELSEC Data Link Functions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Data communications by MELSEC data link functions From the C Controller module, access can be made to device data in a programmable controller CPU or C Controller module.
Page 401 QBF_WaitEvent function. * 1 The following C Controller modules cannot execute it as an interrupt routine (interrupt program). • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier • Q06CCPU-V(-B) * 2 Interrupt routine (interrupt program) execution does not produce a delay that could be caused by user program execution or priority in multitasking.
Page 402 COMMUNICATIONS BETWEEN CPU MODULES (2) Processing outline (a) How to execute interrupt routines (interrupt programs) This section explains how to execute a routine registered by the QBF_EntryCpuInt function as an interrupt routine (interrupt program). 1) With the QBF_EntryCpuInt function, register a routine that corresponds to an interrupt from another CPU (programmable controller CPU or C Controller module).
Page 403 COMMUNICATIONS BETWEEN CPU MODULES (b) How to resume the user program This section explains how to resume the user program that is waiting for an interrupt event by the QBF_WaitEvent function. 1) In the user program, call the QBF_WaitEvent function. 2) By 1), the user program is placed into the interrupt event waiting status.
Page 404 COMMUNICATIONS BETWEEN CPU MODULES (c) Operation timing QBF_GINT function executed C Controller module (another CPU) user program Executing an interrupt Interrupt issued routine (interrupt program) C Controller module interrupt routine (interrupt program) Interrupt routine (interrupt Interrupt routine (interrupt program) in waiting status program) in waiting status Interrupt event notified QBF_WaitEvent function executed...
Page 405 COMMUNICATIONS BETWEEN CPU MODULES (4) Dedicated instructions The following shows programmable controller CPU dedicated instructions used for interrupt from a programmable controller CPU (another CPU). Table 13.3 Devices available for S(P).GINT and D(P).GINT instructions Available devices Link direct device Intelligent Setting Internal device File register...
Page 406 QBF_WaitEvent function. * 1 The following C Controller modules cannot execute it as an interrupt routine (interrupt program). • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier • Q06CCPU-V(-B) 1) When transmission of the instruction command to the C Controller module is completed The SM391 (S(P).GINT or D(P).GINT execution completed) flag of the...
Page 407 COMMUNICATIONS BETWEEN CPU MODULES (d) Operation timing Sequence program S(P).GINT instruction executed S(P). GINT instruction Interrupt issued Interrupt routine (interrupt program) executed C Controller module interrupt routine (interrupt program) Interrupt routine (interrupt program) Interrupt routine (interrupt program) in waiting status in waiting status QBF_Wait Event function Interrupt event notified...
Page 408 COMMUNICATIONS BETWEEN CPU MODULES (f) Program example In the sequence program below, an interrupt is issued to the C Controller module that is set as CPU No.2. S.GINT H3E1 SM391 Program for normal completion SM391 Program that will cause interrupt again Figure 13.8 Example of a program using S(P).GINT instruction (5) Precautions (a) When an interrupt event has already been notified at execution of the...
Page 409 COMMUNICATIONS BETWEEN CPU MODULES 13.2.1 Multiple CPU synchronous interrupt function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Multiple CPU synchronous interrupt function By registering a routine capable of the multiple CPU synchronous interrupt with the QBF_EntryMultiCPUSyncInt function, a program that is executed synchronously with a Motion CPU (Q172DCPU or Q173DCPU) can be created.
Page 410 COMMUNICATIONS BETWEEN CPU MODULES 13.3 Data Communications Using CPU Shared Memory Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Data communications using CPU shared memory The C Controller module can exchange data with CPU modules using the CPU shared memory. Use the bus interface functions when creating user programs of the C Controller module.
Page 411 COMMUNICATIONS BETWEEN CPU MODULES POINT The CPU shared memory is accessible only when the number of CPUs is set to 2 or more in <<Multiple CPU settings>> of C Controller setting utility. If the CPU shared memory is accessed without setting two or more CPU modules, CPU No.
Page 412 COMMUNICATIONS BETWEEN CPU MODULES 13.3.1 CPU shared memory structure Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following shows 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...
Page 413 COMMUNICATIONS BETWEEN CPU MODULES Table 13.9 CPU shared memory structure Area name Description Error details or operation status of the host CPU (C Controller module) Host CPU operation information area are stored in this area. Table 13.10) System area This area is used by the system. This area data are automatically refreshed into devices of the QCPU standard programmable controller CPU or Motion CPU, based on the auto refresh...
Page 414 1): RUN 5): Not used 1: Reserved 2): ERR. 6): Not used 2: STOP 3): USER 7): USER LED color (Q12DCCPU-V only) 3: PAUSE 8): MODE 4): CF CARD (other than Q06CCPU-V-B), STS (Q06CCPU-V-B) 2): STOP/PAUSE factor 0: RUN/STOP/MODE switch *1 Valid only when USER LED is on.
Page 415 COMMUNICATIONS BETWEEN CPU MODULES 13.3.2 Data communications using auto refresh Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the processing and setting for communicating data with a programmable controller CPU or Motion CPU, using the CPU shared memory and auto refresh. (1) Data communications using auto refresh The following shows the processing of data communication when using auto refresh.
Page 416 2. Auto refresh cannot be used for communication between a C Controller module and the Q172DCPU or Q173DCPU. For communication between the Q12DCCPU-V and the Q172DCPU or Q173DCPU, utilize the multiple CPU high speed transmission area for auto refresh. ( Page 13-24, Section 13.3.3)
Page 417 COMMUNICATIONS BETWEEN CPU MODULES (2) Auto refresh area setting Data communications with a programmable controller CPU or Motion CPU using auto refresh require the auto refresh area setting. Configure the auto refresh area settings in "Communication area setting (refresh setting)" in <<Multiple CPU settings>> of C Controller setting utility. The "Communication area setting (refresh setting)"...
Page 418 COMMUNICATIONS BETWEEN CPU MODULES Remark For the auto refresh area setting for a programmable controller CPU or Motion CPU, refer to the manual for each CPU module. (b) Setting example The following is an example of the auto refresh area setting. In this example, a High Performance model QCPU is used as CPU No.1, and CPU No.4 does not use auto refresh.
Page 419 COMMUNICATIONS BETWEEN CPU MODULES (3) Precautions for data communications using auto refresh Depending on the timing of writing data to the host CPU's auto refresh area or reading data from another CPU, old and new data may be mixed in the area for each CPU. Therefore, configure an interlock program for auto refresh so that data of another CPU will not be used when old and new data are mixed.
Page 420 COMMUNICATIONS BETWEEN CPU MODULES Sending side program for CPU No.1 Receiving side program for CPU No.2 (C Controller module) (programmable controller CPU) Write command unsigned short usBuf; /* Data storage destination */ M100 unsigned short pusData[128]; /* Data storage destination */ Set send data in D0 to D9.
Page 421 COMMUNICATIONS BETWEEN CPU MODULES 1) CPU No.1 stores send data in D0 to D9. 2) CPU No.1 turns on the data set completion bit (M0). • In the END processing of CPU No.1, the above data are written to the auto refresh area in its CPU No.1 send area.
Page 422 1) A multiple CPU high speed main base unit (Q3 DB) is used. 2) A Universal model QCPU (except the Q00UCPU, Q01UCPU, and Q02UCPU) or the Q12DCCPU-V is used as CPU No.1. 3) Two or more Universal model QCPU(s) (except the Q00UCPU, Q01UCPU, and Q02UCPU), Motion CPU(s) (Q172DCPU or Q173DCPU), Q12DCCPU- V(s) or the Q24DHCCPU-V/-LS are used.
Page 423 COMMUNICATIONS BETWEEN CPU MODULES (2) Communication using auto refresh (a) Outline of auto refresh Auto refresh is a communication method using the auto refresh area in the multiple CPU high speed transmission area of the CPU shared memory. Data written to the auto refresh area in the multiple CPU high speed transmission area are sent to another auto refresh area of another CPU at regular intervals (multiple CPU high speed transmission cycle).
Page 424 COMMUNICATIONS BETWEEN CPU MODULES Universal model QCPU (CPU No.1) C Controller module (CPU No.2) CPU shared memory CPU shared memory CPU No.1 multiple CPU high speed CPU No.1 multiple CPU high speed 2) Send to CPU No.2 transmission area transmission area Auto refresh area Auto refresh area CPU No.2 multiple CPU high speed...
Page 425 COMMUNICATIONS BETWEEN CPU MODULES (c) Memory structure of the multiple CPU high speed transmission area The following explains memory structure of the multiple CPU high speed transmission area in the CPU shared memory.( Page 13-14, Section 13.3.1) 2) CPU No.1 send area 3) User setting area 1) Multiple CPU high speed...
Page 426 COMMUNICATIONS BETWEEN CPU MODULES (e) Setting example When two auto refresh setting ranges are configured for a system comprising of a Universal model QCPU (CPU No.1) and a C Controller module (CPU No.2), the send and receive areas in each auto refresh area are as illustrated below. If auto refresh settings in Figure 13.19 are configured for each CPU, the auto refresh areas of the Universal model QCPU (CPU No.1) and C Controller module are allocated as shown in Figure 13.20.
Page 427 COMMUNICATIONS BETWEEN CPU MODULES (3) Precautions (a) Transmission delay time A transmission delay caused by auto refresh will be within the following range. 0.09 ms to (1.80 + (Sending-side write time + Receiving-side reading cycle 2)) ms * 1 For the write time of the QBF_ToBuf function, refer to the following. Appendix 1 * 2 When the receiving side is a C Controller module, there is no reading cycle (0ms).
Page 428 COMMUNICATIONS BETWEEN CPU MODULES Sending side program for CPU No.1 Receiving side program for CPU No.2 (C Controller module) (programmable controller CPU) Write command unsigned short usBuf; /* Data storage destination */ M100 unsigned short pusData[128]; /* Data storage destination */ Set send data in D0 to D9.
Page 429 COMMUNICATIONS BETWEEN CPU MODULES 1) CPU No.1 stores send data in D0 to D9. 2) CPU No.1 turns on the data set completion bit (M0). • In the END processing of CPU No.1, the above data are written to the auto refresh area in its CPU No.1 send area.
Page 430 COMMUNICATIONS BETWEEN CPU MODULES 13.3.4 Data communications without using auto refresh Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains processing outline of data communications in the CPU shared memory without using auto refresh of the programmable controller CPU. (1) Data communications without using auto refresh When auto refresh is not used, data are communicated as described below.
Page 431 COMMUNICATIONS BETWEEN CPU MODULES <Interlock program example> Depending on the following timing, old and new data for each CPU may be mixed (data separation). • Writing data to the user setting area in another CPU and reading another CPU's user setting area data from the host CPU •...
Page 432 COMMUNICATIONS BETWEEN CPU MODULES 1) CPU No.1 writes send data to the user setting area. 2) CPU No.1 writes the data set completion bit ON to the user setting area. The multiple CPU high speed transmission area data of CPU No.1 are sent to CPU No.2.
Page 433 COMMUNICATIONS BETWEEN CPU MODULES (b) Between C Controller modules C Controller module 1) C Controller module 2) CPU shared memory CPU shared memory Host CPU operation information area Host CPU operation information area System area System area Auto refresh area Auto refresh area Data written by QBF_ToBuf function Data written by QBF_ToBuf function...
Page 434 COMMUNICATIONS BETWEEN CPU MODULES <Interlock program example> Depending on the following timing, old and new data for each CPU may be mixed (data separation). • Writing data to the user setting area in another CPU and reading another CPU's user setting area data from the host CPU •...
Page 435 COMMUNICATIONS BETWEEN CPU MODULES Receiving side program for CPU No.2 (C Controller module) unsigned short usBuf; /* Data storage destination */ unsigned short pusData[128]; /* Data storage destination */ /****************************************************************/ /* The ON status of CPU No.1 data set completion bit is detected.*/ /****************************************************************/ while(1){ sRet = QBF_FromBuf(lPath, 0x3E0, 10010, 1, &usBuf, 1);...
Page 436 COMMUNICATIONS BETWEEN CPU MODULES 1) CPU No.1 writes send data to the user setting area. 2) CPU No.1 writes the data set completion bit ON to the user setting area. The multiple CPU high speed transmission area data of CPU No.1 are sent to CPU No.2.
Page 437 Motion CPU onto the user program. Figure 13.26 Communication without using auto refresh Remark 1. For communications between the Q12DCCPU-V and the Q172DCPU or Q173DCPU, use the auto refresh area in the multiple CPU high speed transmission area. ( Page 13-24, Section 13.3.3)
Page 438 1) The user setting area in the multiple CPU high speed transmission area is available for the following CPU modules only. • Universal model QCPU (except for the Q00UCPU, Q01UCPU, and Q02UCPU) • Motion CPU (Q172DCPU, Q173DCPU) • Q12DCCPU-V • Q24DHCCPU-V/-LS Host CPU operation information area System area Auto refresh area Can be used by a CPU module.
Page 439 COMMUNICATIONS BETWEEN CPU MODULES (b) Addresses of the multiple CPU high speed transmission area Figure 13.28 shows the addresses in the multiple CPU high speed transmission area. The last address of each CPU's send area shown in Figure 13.28 varies depending on the points set in "CPU specific send range"...
Page 440 COMMUNICATIONS BETWEEN CPU MODULES 13.4 Programmable Controller Remote Control Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Programmable controller remote controller function This function allows the C Controller module to control the execution status of a programmable controller CPU. Use a MELSEC data link function when creating a user program of the C Controller module.
Page 441 COMMUNICATIONS BETWEEN CPU MODULES 13.5 Sequence Program Control Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Sequence program control function This function allows the C Controller module to control (change) the sequence program execution type of a programmable controller CPU. Use a bus interface function when creating a user program for the C Controller module.
Page 442 CPU from the C Controller module. Figure 13.31 Interrupt to the Motion CPU POINT To apply this function to the Q172DCPU or Q173DCPU, the C Controller module must be the Q12DCCPU-V. - 44 13.6 Issuing an Interrupt to Another CPU...
Page 443 • Resumes the user program that is waiting for an interrupt event by the QBF_WaitEvent function. * 1 The following C Controller modules cannot execute it as an interrupt routine (interrupt program). • Q12DCCPU-V with a serial number whose first five digits are "12041" or earlier • Q06CCPU-V(-B) C Controller module (another CPU)
Page 444 Figure 13.34 Motion CPU control instruction POINT To apply this function to the Q172DCPU or Q173DCPU, the C Controller module must be the Q12DCCPU-V. Remark For the bus interface functions, refer to the following. C Controller Module User's Manual (Utility Operation, Programming) - 46 13.7 Motion CPU Control Instruction...
Page 445 Figure 13.35 Motion CPU device access POINT To apply this function to the Q172DCPU or Q173DCPU, the C Controller module must be the Q12DCCPU-V. Remark For the bus interface functions, refer to the following. C Controller Module User's Manual (Utility Operation, Programming) 13.8 Motion CPU Device Access...
Page 446 • Universal model QCPU (except the Q00UCPU, Q01UCPU, and Q02UCPU) • Motion CPU (the Q172DCPU and Q173DCPU) • Q12DCCPU-V • Q24DHCCPU-V/-LS (1) Multiple CPU synchronized boot-up setting In the Multiple CPU settings tab of C Controller setting utility, check the boxes for any target CPUs (CPU 1 to CPU 4).
Page 447 CPU 2 and CPU 4. • Universal model QCPU (except the Q00UCPU, Q01UCPU, and Q02UCPU) • Motion CPU (the Q172DCPU and Q173DCPU) • Q12DCCPU-V • Q24DHCCPU-V/-LS Clear the check boxes when CPU modules other than the listed above are used.
Page 448 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEMS CHAPTER 14 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEMS Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B 14.1 Parameter List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Parameters used for multiple CPU systems The following parameter settings have been added to C Controller setting utility to support not only single CPU systems but also multiple CPU systems.
Page 449 All CPUs can read all inputs Page 14-6, Section 14.1.4 All CPUs can read all outputs Multiple CPU Multiple CPU high speed transmission area setting (Q12DCCPU-V only) settings Use multiple CPU high speed transmission CPU specific send range Page 14-7, Section 14.1.8...
Page 450 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEMS If a multiple CPU setting parameter is changed, change the corresponding setting for each of all CPUs in the multiple CPU system accordingly. After that, reset CPU No.1 or restart the multiple CPU system (power it on, off, and on again).
Page 451 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEMS 14.1.1 Setting the number of CPUs (required) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Number of CPUs In the <<Multiple CPU settings>> tab of C Controller setting utility, select the number of CPU modules to be used in the multiple CPU system.
Page 452 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEMS POINT The following (1) or (2) may cause an error in the actually mounted CPU module No.1. (1) CPU modules exceeding the specified 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, PARAMETER ERROR) occurs.
Page 453 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEMS 14.1.2 Operation mode setting (optional) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B When a stop error occurs in a CPU module other than CPU No.1, this setting allows operations of the other CPUs to continue. The operation mode of CPU No.1 cannot be changed. All CPUs will stop if a stop error occurs in CPU No.1.
Page 454 PARAMETERS ADDED FOR MULTIPLE CPU SYSTEMS 14.1.6 Control CPU settings (required) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Specify a control CPU for each of I/O modules and intelligent function modules that are mounted on a base unit in the multiple CPU system. CPU No.1 is set for all by default.
Page 455 STARTING A MULTIPLE CPU SYSTEM CHAPTER 15 STARTING A MULTIPLE CPU SYSTEM Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This chapter explains the standard startup procedure of a multiple CPU system. 15.1 Flowchart for Starting a Multiple CPU System Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B For the parameter setting and programming of programmable controller CPUs and Motion CPUs, refer to the manuals for respective modules.
Page 456 C Controller Module User's Manual respective CPU modules, No.2 and higher. (Utility Operation, Programming) Set the switches of all CPUs from STOP Q12DCCPU-V: Page 6-29, Section 6.4.1 (3) Section 5.4 (2)*2 to RUN. Q06CCPU-V(-B): Page 6-35, Section 6.4.2 (2) Reset CPU No.1. (Written parameters take effect by resetting.)
Page 457 (Utility Operation, Programming) the C Controller module. 2) Back up the standard RAM data not to lose them due to expiry of battery life. (Q12DCCPU-V only) Page 8-2, Section 8.1 1)) Operation Figure 15.1 Procedure for starting up a multiple CPU system * 1 Reference section and manual are for the C Controller module.
Page 458 STARTING A MULTIPLE CPU SYSTEM 15.2 Setting Parameters Added for Multiple CPU Systems Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section provides the procedure for setting parameters for the multiple CPU system in C Controller setting utility. 15.2.1 System configuration Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The procedure for setting multiple CPU system parameters is explained by using the system shown in Figure 15.2 as an example.
Page 459 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 unless otherwise noted. Page 14-1, Section 14.1) (1) For the Q12DCCPU-V Number of CPUs Multiple CPU settings...
Page 460 STARTING A MULTIPLE CPU SYSTEM (2) For the Q06CCPU-V(-B) Number of CPUs Multiple CPU settings Operation mode I/O sharing when using Multiple CPUs Change screens Communication area setting (refresh setting) Send range for each CPU I/O assignment I/O assignment settings Detailed settings: Control CPU Slots...
Page 461 STARTING A MULTIPLE CPU SYSTEM 15.2.3 When creating a new system Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) For the Q12DCCPU-V Start Start C Controller setting utility Connect to the C Controller module. "Points occupied by empty slot" in the <<System settings>> tab (optional) Set the points to be occupied by one empty slot.
Page 462 STARTING A MULTIPLE CPU SYSTEM (From the previous page) "Operation mode" in the <<Multiple CPU settings>> tab (optional) 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. 2, 3 and 4 (Checked) For example, when "All CPUs stopped due to an error in CPU2"...
Page 463 STARTING A MULTIPLE CPU SYSTEM (From the previous page) "CPU specific send range" in the <<Multiple CPU settings>> tab (setting required) Set the points of data to be sent and received between CPUs. The setting range is shown below. Number of CPUs Setting range 0 to 14K points 0 to 13K points...
Page 464 STARTING A MULTIPLE CPU SYSTEM (From the previous page) "Communication area setting (refresh setting)" in the <<Multiple CPU settings>> tab (optional) Set the points of the auto refresh area for the data to be sent and received by auto refresh between CPUs. In the Type column in the <<I/O assignment settings>>...
Page 465 STARTING A MULTIPLE CPU SYSTEM (2) For the Q06CCPU-V(-B) Start Start C Controller setting utility. Connect to the C Controller module. "Points occupied by empty slot" in the <<System settings>> tab (optional) Set the points to be occupied by one empty slot. Default: 16 points "Number of CPUs"...
Page 466 STARTING A MULTIPLE CPU SYSTEM (From the previous page) "Operation mode" in the <<Multiple CPU settings>> tab (optional) 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 467 STARTING A MULTIPLE CPU SYSTEM (From the previous page) In the Type column in the <<I/O assignment>> tab, select "CPU (Empty)" for a slot where no module is mounted. Click the Detailed settings button to open the Detailed settings screen. Control CPU (setting required) Select a control CPU (No.1 to No.4) for each slot.
Page 468 STARTING A MULTIPLE CPU SYSTEM 15.2.4 Importing existing multiple CPU parameters Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Remark To use multiple CPU parameters set by GX Works2, save projects in GX Developer format in advance. Start Start C Controller setting utility. Connect to the C Controller module.
Page 469 STARTING A MULTIPLE CPU SYSTEM (From the previous page) Clicking Yes will load the following data from the specified GX Developer project or parameter setting file in C Controller setting utility, and will overwrite the current settings. Number of empty slot points I/O assignment settings Multiple CPU settings Verify the multiple CPU settings in the <<Multiple CPU...
Page 470 STARTING A MULTIPLE CPU SYSTEM (From previous page) Check the "Points occupied by empty slot" setting on the <<System settings>> tab. Set parameters other than these multiple CPU system parameters. Save the set parameters into a file. Figure 15.7 Parameter setting procedure for importing multiple CPU system parameters Remark For C Controller setting utility, refer to the following.
Page 471 STARTING A MULTIPLE CPU SYSTEM Memo 15.2 Setting Parameters Added for Multiple CPU Systems - 17 15.2.4 Importing existing multiple CPU parameters...
Page 472 TROUBLESHOOTING CHAPTER 16 TROUBLESHOOTING Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This chapter provides error information, return values (error codes) of bus interface functions and MELSEC data link functions, and corrective actions for various problems. For the Q06CCPU-V-B, MELSEC data link functions cannot be used.
Page 473 TROUBLESHOOTING 16.1 Troubleshooting Basics Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B First, perform the following three steps. (1) Visual check Check the following: 1) The operating states of the external devices 2) The operating state of the external power supply 3) Whether the cables are connected normally...
Page 474 TROUBLESHOOTING 16.2 Troubleshooting Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B If a problem has occurred in the C Controller module, first conduct a hardware self- diagnostics to check the C Controller module itself for a hardware failure. ( Page 16- 75, Section 16.5) See the following table and refer to the relevant troubleshooting flowchart.
Page 475 TROUBLESHOOTING 16.2.1 When the POWER LED on the power supply module turned off Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedures to be taken when the POWER LED of the power supply module turns off at the time of power-on or during operation of the C Controller module.
Page 476 TROUBLESHOOTING 16.2.2 When the MODE LED is not lit Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedures to be taken when the MODE LED on the C Controller module does not light up when the C Controller system is powered on.
Page 477 Check the result of hardware self- Please consult your local Mitsubishi diagnostic, and please consult your local Electric System & Service Co., Ltd. or Mitsubishi Electric System & Service representative, explaining a detailed Co., Ltd. or representative, explaining a description of the problem.
Page 478 TROUBLESHOOTING 16.2.3 When the ERR. LED is on or flashing Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedures to be taken when the ERR. LED on the C Controller module turns on or flashes at the time of power-on or operation start or during operation of the C Controller system.
Page 479 TROUBLESHOOTING 16.2.4 When the RUN LED remains flashing Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B When the RUN LED on the C Controller module remains flashing, it means the script file (command) remains in execution. Perform the following. • Correct the script file and user program.
Page 480 TROUBLESHOOTING 16.2.5 When UNIT VERIFY ERR. occurred Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedures to be taken when a module verify error (error code: 2000, UNIT VERIFY ERR.) occurred when the C Controller system is powered on or during operation.
Page 481 TROUBLESHOOTING 16.2.6 When CONTROL-BUS.ERR. occurred Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedures to be taken when a control bus error (error code: 1412 to 1416, CONTROL-BUS.ERR.) occurred when the C Controller system is powered on or during operation.
Page 482 TROUBLESHOOTING CONTROL-BUS.ERR. occurred Check the error information in <<Module information>> or <<Event history>> of C Controller setting utility. Reset the C Controller module and RUN it again. Was the error removed? Is the module in Mount the module and connect the relevant slot mounted the extension cable properly.
Page 483 Controller system operation. POINT When using Q12DCCPU-V with a serial number whose first five digits are “15102” or later, check if the connected module is set to the basic mode. If not, switch the setting to the basic mode with the initialization setting.
Page 484 TROUBLESHOOTING Is there a C Controller module channel for which the network address of the development environment (personal computer) set? (For Q06CCPU-V(-B), go to No.) Connect the Ethernet cable to the channel for which the network address of the development environment (personal computer) is set.
Page 485 TROUBLESHOOTING (2) When the C Controller module is not accessible from the development environment (personal computer) by FTP Check the following: • Steps 1) to 4) of the flowchart in (1) in this section • Priority of the task in the user program (3) When Workbench or Tornado on the development environment (personal computer) cannot be connected to the C Controller module Check the following:...
Page 486 TROUBLESHOOTING 16.2.8 When a file (program) cannot be written Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedures to be taken when a file such as a user program file cannot be written to the C Controller module. Unable to write a file such as a user program file.
Page 487 TROUBLESHOOTING 16.2.9 When an error occurs during user program execution Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedures to be taken when an error occurred during execution of a user program in the C Controller system. Error occurred Does the endian...
Page 488 TROUBLESHOOTING Is combination of According to the method for creating and the C Controller module and compiling a new project of user program Workbench or Tornado, and precautions for program debugging by which the executed user program create a user program. was created, correct? Is the stack size of the task sufficient?
Page 489 TROUBLESHOOTING 16.2.10 When a file system error occurred Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedures to be taken when a file system error occurred when the standard RAM, standard ROM, or CompactFlash card is accessed. POINT Data cannot be written to the standard ROM when the standard ROM has been shut down.
Page 490 TROUBLESHOOTING Has a file system error occurred? Format the drive Restore (copy) the necessary data and Page 6-72, Section 5.11 ). Page 6-72, Section 6.10 program files. Page 15-15, Section 18.6 ) Page 16-91, Section 16.6 Restore (copy) the necessary data and program files.
Page 491 TROUBLESHOOTING 16.2.11 When no LED on an output module turn on Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedures to be taken when no LED on an output module turn on during C Controller system operation. POINT Before using the following flowchart, check if the RUN LED on the C Controller module is on.
Page 492 TROUBLESHOOTING 16.2.12 When an output load device of an output module does not turn on Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedures to be taken when an output load device of an output module does not turn on during C Controller system operation.
Page 493 CompactFlash card. in the standard RAM or standard ROM Figure 16.12 Disabling script file execution (for the Q12DCCPU-V and Q06CCPU-V) * 1 For restrictions on the functions, refer to the following. C Controller Module User's Manual (Utility Operation, Programming) 16.2 Troubleshooting...
Page 494 Consult your local Mitsubishi service center or representative, explaining the details of the problem. Figure 16.12 Disabling script file execution (for the Q12DCCPU-V and Q06CCPU-V) (continued) - 23 16.2 Troubleshooting 16.2.13 When operation is not normal due to script file execution...
Page 495 TROUBLESHOOTING (2) For the Q06CCPU-V-B Error occurred Does the endian format of the execution file match the specification of the C Controller module? Compile the user program and regenerate an execution file according to the C Controller module specifications. When the user program was started from a script file in the standard ROM, perform the following.
Page 496 (1) Error messages indicating the endian format mismatch between the user program and the C Controller module (a) For the Q12DCCPU-V 1) When downloading a user program to a C Controller module Failed to load "..xxx/SH7750gnu/Demo1.out on "yyyyyyyy@zzzzz:SH-4A" Figure 16.14 Error message 2) When executing a user program with the ld command ld(1,0,"/CF/Demo1.out")
Page 497 TROUBLESHOOTING (b) For the Q06CCPU-V(-B) 1) When downloading a user program to a C Controller module Error: This is not an elf module for the SH architecture. Error: Object module load failed for C:/xxx/Demo1.out Removed Demo1.out from target..done WTX Error 0x1002e (LOADER_UNKNOWN_OBJ_MODULE_FORMAT) Figure 16.16 Error message 2) When executing a user program with the ld command ld(1,0,"/ROM/Demo1.out")
Page 498 TROUBLESHOOTING 16.2.15 When unable to read from or write to the specified device Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The following flowchart shows the procedure to be taken when reading from or writing to the specified device cannot be performed with a MELSEC data link function.
Page 499 Check if the target C Controller module is operating. Check for Ethernet cable connection. Check if the Ethernet cable is connected to the correct interface (CH1 or CH2). (For Q12DCCPU-V only) Communicating normally? Check that Windows Firewall is disabled. Issue a PING command from the...
Page 500 TROUBLESHOOTING If the Microsoft Windows FTP tool is used, access the Microsoft Support Online website and troubleshoot the problem. Was the problem solved? Use another type of FTP tool to check. Communicating normally? Consult your local Mitsubishi service center or representative, explaining the details of the problem.
Page 501 Check for Ethernet cable connection. Check if the Ethernet cable is connected to the correct interface (CH1 or CH2). (For Q12DCCPU-V only) Connected? Check that Windows Firewall is disabled. Issue a PING command from the development environment (personal computer) to the C Controller module to confirm the presence.
Page 502 TROUBLESHOOTING Make a Telnet connection from the command prompt and check if the following error message will appear. "Sorry, session limit reached." or "Connection to host lost." Error occurred? Use Workbench or Tornado in the current or another computer to check if Telnet connection is already made.
Page 503 Check for Ethernet cable connection. Check if the Ethernet cable is connected to the correct interface (CH1 or CH2). (For Q12DCCPU-V only) Connected? Check that Windows Firewall is disabled. Issue a PING command from the development environment (personal computer) to the C Controller module to confirm the presence.
Page 504 TROUBLESHOOTING Check if more than 10 connections are made concurrently from the FTP tool. If so, reduce the number of connections to 10 or less by disconnecting some of them. Connected? Refer to the Precautions for program registration via FTP and check them. Connected? Consult your local Mitsubishi service center or representative, explaining the...
Page 505 TROUBLESHOOTING 16.3 Actions to be Taken When the ERR. LED is On or Flashing Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B If a stop or continuation error occurs in the C Controller module, the color of the corresponding error box changes from (white) to (red) in "Error information"...
Page 506 TROUBLESHOOTING POINT 1. Monitoring stops when the active tab is switched from to another during monitoring, and resumes when the <<Module information>> is opened again. Start monitoring 2. If a communication error occurs during access, click the button or specify the connection target again. 3.
Page 507 TROUBLESHOOTING (c) Error details and corrective actions Identify the relevant error code in Table 16.2, and refer to the following. (3) Detailed error information and corrective actions by error code in this section Table 16.2 Self-diagnostics and error codes Error Error item Self-diagnostic item Description...
Page 508 TROUBLESHOOTING Table 16.2 Self-diagnostics and error codes (continued) Error Error item Self-diagnostic item Description code 2100 2103 2106 2107 2108 Intelligent function Intelli. module An error occurred during diagnosis of the intelligent 2120 module assignment error assignment err. function module I/O assignment. 2121 detection 2122...
Page 509 TROUBLESHOOTING Table 16.2 Self-diagnostics and error codes (continued) Error Error item Self-diagnostic item Description code 1510 A stop or continuation error other than the above was 1520 Others Another error detection detected. 2502 5012 Remark For the self-diagnostic item details, refer to the following. Page 4-20, Section 4.5 16.3 Actions to be Taken When the ERR.
Page 510 TROUBLESHOOTING (3) Detailed error information and corrective actions by error code The error codes and respective detailed information and corrective actions are shown below. If an error code not found in the error code list is detected, please consult your local Mitsubishi service center or representative, explaining the details of the problem.
Page 511 TROUBLESHOOTING Error code Error details and cause Corrective action • Take a preventive measure against noise. • Reset the CPU module and restart it. CPU module drives recklessly or it breaks down. If the same error is displayed again, a hardware failure may have 1000 •...
Page 512 TROUBLESHOOTING Table 16.3 Error codes (continued) LED status Error code Error message Error information CPU operation status ERR. 1401 SP.UNIT DOWN Off/On Flashing/On Module No. Stop/Continue 1403 SP.UNIT DOWN Off/On Flashing/On Module No. Stop/Continue 1412 CONTROL-BUS.ERR. Flashing Stop Module No. 1413 CONTROL-BUS.ERR.
Page 513 TROUBLESHOOTING Error code Error details and cause Corrective action When unsupported module is mounted, remove the module. • In the initial processing, no response returns from an intelligent If the module is supported, a hardware failure may have occurred in function module.
Page 514 TROUBLESHOOTING Table 16.3 Error codes (continued) LED status Error code Error message Error information CPU operation status ERR. 1432 MULTI-C.BUS.ERR. Flashing Stop Module No. 1433 MULTI-C.BUS.ERR. Flashing Stop Module No. 1434 MULTI-C.BUS.ERR. Flashing Stop Module No. 1435 MULTI-C.BUS.ERR. Flashing Stop Module No.
Page 515 TROUBLESHOOTING Error code Error details and cause Corrective action Reset the CPU module and set it to RUN again. If the same error is Communication timeout with other CPU was detected at the multiple displayed again, a hardware failure may have occurred in the CPU 1432 CPU high speed transmission.
Page 516 TROUBLESHOOTING (b) Error code list (2000 to 2999) Table 16.4 Error codes LED status Error code Error message Error information CPU operation status ERR. Off/ 2000 UNIT VERIFY ERR. Flashing/On Module No. Stop/Continue 2100 SP.UNIT LAY ERR. Flashing Stop Module No. 2103 SP.UNIT LAY ERR.
Page 517 TROUBLESHOOTING Error code Error details and cause Corrective action In the multiple CPU system, a CPU module incompatible with the Replace the incompatible CPU module with a compatible one. multiple CPU system is mounted. • Read the error information in C Controller setting utility, check the The setting is different from the I/O module information input at power- module corresponding to the value (module No.), and replace the 2000...
Page 518 TROUBLESHOOTING Table 16.4 Error codes (continued) LED status Error code Error message Error information CPU operation status ERR. 2124 SP.UNIT LAY ERR. Flashing Stop 2125 SP.UNIT LAY ERR. Flashing Stop Module No. 2126 SP.UNIT LAY ERR. Flashing Stop Module No. 2150 SP.UNIT VER.ERR.
Page 519 TROUBLESHOOTING Error code Error details and cause Corrective action • A module is installed in the position of slot 65 or higher. • Remove the module in slot 65 or higher. • A module is installed in the position of the slot number that exceeds •...
Page 520 TROUBLESHOOTING (c) Error code list (3000 to 3999) Table 16.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 521 TROUBLESHOOTING Error code Error details and cause Corrective action • In the interrupt event setting of Parameter, specify the start I/O No. of In the multiple CPU system, an intelligent function module controlled the intelligent function module controlled by the host CPU. by another CPU is specified in the interrupt event setting of Parameter.
Page 522 TROUBLESHOOTING Table 16.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 the parameter setting location for each parameter number, refer to the following. Appendix 8 16.3 Actions to be Taken When the ERR.
Page 523 TROUBLESHOOTING Error code Error details and cause Corrective action • Delete the network parameters for the CC-Link IE controller network In the multiple CPU system, a CC-Link IE controller network module module controlled by another CPU. controlled by another CPU is assigned to the start I/O No. in the CC- •...
Page 524 TROUBLESHOOTING Table 16.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...
Page 525 TROUBLESHOOTING Error code Error details and cause Corrective action • When the station No. of a MELSECNET/H module is 0, parameters for the PLC-to-PLC network are set. Correct the type or station No. of the MELSECNET/H module. • When the station No. of a MELSECNET/H module is other than 0, parameters for a remote master are set.
Page 526 TROUBLESHOOTING (d) Error code list (5000 to 5999) Table 16.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 527 5012 • The C Controller module was restarted while online connection with • Restart the C Controller module with Workbench connection Tornado or Workbench (Q12DCCPU-V only). disconnected. For precautions for program debugging, refer to the following. • Check the command executed from Shell.
Page 528 TROUBLESHOOTING (e) Error code list (7000 to 10000) Table 16.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...
Page 529 TROUBLESHOOTING Error code Error details and cause Corrective action • In the operating mode of the multiple CPU system, a CPU error occurred in the CPU for which "All station stop by stop error of CPU" is selected. • Identify the error of the CPU module and eliminate the error cause. •...
Page 530 TROUBLESHOOTING 16.4 Error Code List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains error codes that are returned upon error occurrence. 16.4.1 Error codes and actions (for errors occurred in function execution) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The error codes returned in bus interface or MELSEC data link function execution are returned as a return value.
Page 531 TROUBLESHOOTING Table 16.8 Common error codes returned by bus interface and MELSEC data link functions (continued) Return value Error description Corrective action (HEX) Network channel No. error (When a SEND/RECV request is issued.) Check the specified channel No. when a (0x55) Channel No.
Page 532 TROUBLESHOOTING Table 16.8 Common error codes returned by bus interface and MELSEC data link functions (continued) Return value Error description Corrective action (HEX) 16386 An unprocessable request was received. Change the request destination. (0x4002) 16400 Reset the C Controller module when it is in the Not executable during running (0x4010) STOP status.
Page 533 TROUBLESHOOTING Table 16.8 Common error codes returned by bus interface and MELSEC data link functions (continued) Return value Error description Corrective action (HEX) The instruction cannot be executed on the specified target CPU module. 17233 Check and revise the program to a proper user (1) The instruction name is wrong.
Page 534 TROUBLESHOOTING Table 16.8 Common error codes returned by bus interface and MELSEC data link functions (continued) Return value Error description Corrective action (HEX) CPU No. of the requesting CPU is incorrect. (the error code returned 19465 Check the user program on C Controller by the Motion CPU) (0x4C09) module.
Page 535 TROUBLESHOOTING Table 16.8 Common error codes returned by bus interface and MELSEC data link functions (continued) Return value Error description Corrective action (HEX) Restart the data link. Device access error during data link stop -28150 Note: Writing/reading data will be performed RX/RY/RWw/RWr was accessed when the own station was not (0x920A) even when this error occurs.
Page 536 TROUBLESHOOTING Table 16.8 Common error codes returned by bus interface and MELSEC data link functions (continued) Return value Error description Corrective action (HEX) -28622 Target module busy error Add a program to wait until the processing is (0x9032) Target module is busy. completed or to retry.
Page 537 TROUBLESHOOTING Table 16.8 Common error codes returned by bus interface and MELSEC data link functions (continued) Return value Error description Corrective action (HEX) Buffer access range error Check the offset. -28631 The specified offset is out of range. Check the buffer size. (0x9029) The specified offset plus size is out of range.
Page 538 TROUBLESHOOTING Table 16.8 Common error codes returned by bus interface and MELSEC data link functions (continued) Return value Error description Corrective action (HEX) -28664 Data transmission area occupied. Retry. (0x9008) -28665 No registration data error Reboot the operating system. (0x9007) -28666 Data length error Reboot the operating system.
Page 539 TROUBLESHOOTING (2) Error codes returned by bus interface functions The following provides the error descriptions and corrective actions corresponding to individual error code returned in execution of bus interface functions. For the common error codes returned by bus interface functions and MELSEC data link functions, refer to the following.
Page 540 TROUBLESHOOTING Table 16.9 Error codes returned by bus interface functions (continued) Return value Error description Corrective action (HEX) -223 Memory allocation error Check available memory. (0xFF21) Sufficient memory could not be allocated. -224 LED set value error Check the LED set value. (0xFF20) The specified LED control value is out of range.
Page 541 Check if the standard ROM is being accessed. Check if all user files are closed. -244 Standard ROM shut down error In the case of Q12DCCPU-V, standard ROM is (0xFF0C) Standard ROM shut down has failed. not supported. Correct the user program so that this function is not called.
Page 542 TROUBLESHOOTING (3) Error codes returned by MELSEC data link functions The following provides the error descriptions and corrective actions corresponding to individual error code returned in execution of MELSEC data link functions. For the common error codes returned by bus interface functions and MELSEC data link functions, refer to the following.
Page 543 TROUBLESHOOTING Table 16.10 Error codes returned by MELSEC data link functions (continued) Return value Error description Corrective action (HEX) SEND/RECV channel No. error Specify the channel No. within the range (1 to The channel No. specified in the SEND/RECV function is out of (0xFFED) range.
Page 544 TROUBLESHOOTING 16.4.2 Error codes and actions (for errors occurred in communication) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The C Controller module returns an error code to a request source if an error occurs at the time of a communication request from the following.
Page 545 TROUBLESHOOTING Table 16.11 Error codes that may be detected during communication (continued) Error code (hexadecimal) Error Action • Set the C Controller module into the remote- request-executable state and then make the 408B The remote request cannot be executed. request again. •...
Page 546 Page 16-80, Section 16.5.1 (3) (c) * 2 The following C Controller module performs sum check instead of error detection. • The Q12DCCPU-V with serial number (first five digits) "12041" or earlier - 75 16.5 Hardware Self-Diagnostic Function...
Page 547 Page 16-80, Section 16.5.1 (3) (c) * 2 Can be selected for Q12DHCCPU-V with a serial number whose first five digits are "15102" or later. 16.5 Hardware Self-Diagnostic Function - 76 16.5.1 Hardware self-diagnostic test and initialization setting of the Q12DCCPU-V...
Page 548 Use the QBF_ReadSRAM function for programming. Alternatively, store the data by clicking the Save data button on the SRAM monitoring tab of C Controller setting utility. - 77 16.5 Hardware Self-Diagnostic Function 16.5.1 Hardware self-diagnostic test and initialization setting of the Q12DCCPU-V...
Page 549 6) When executing Mode 7 Visually check the status of 7-segment LED indication. (5) (c) in this section) 7) When executing Mode 0 Perform 1) to 5). 16.5 Hardware Self-Diagnostic Function - 78 16.5.1 Hardware self-diagnostic test and initialization setting of the Q12DCCPU-V...
Page 550 MODE STOP MODE STOP MODE CF CARD ERR. RES. RES. CH3 SD/RD USER SEL. SEL. Figure 16.25 Switch operation for the hardware self-diagnostics mode - 79 16.5 Hardware Self-Diagnostic Function 16.5.1 Hardware self-diagnostic test and initialization setting of the Q12DCCPU-V...
Page 551 Module initialization setting (Extended mode) * 1 Can be selected for Q12DHCCPU-V with a serial number whose first five digits are "15102" or later. 16.5 Hardware Self-Diagnostic Function - 80 16.5.1 Hardware self-diagnostic test and initialization setting of the Q12DCCPU-V...
Page 552 • For mode 1, the indication alternates between 01 and the progress level (%). * 1 The LED of the following C Controller module indicates 01 without showing the progress level (%). • The Q12DCCPU-V with serial number (first five digits) "12041" or earlier (5) Confirming the hardware self-diagnostic test and initialization setting...
Page 553 If failure is detected again, the hardware of the C Controller module may be faulty. Please consult your local Mitsubishi representative, explaining the details of the problem. 16.5 Hardware Self-Diagnostic Function - 82 16.5.1 Hardware self-diagnostic test and initialization setting of the Q12DCCPU-V...
Page 554 If any of them does not lit, hardware fault of the C Controller module may be the cause. Please consult your local Mitsubishi representative, explaining the details of the problem. - 83 16.5 Hardware Self-Diagnostic Function 16.5.1 Hardware self-diagnostic test and initialization setting of the Q12DCCPU-V...
Page 555 TROUBLESHOOTING 16.5.2 Hardware self-diagnostic test and initialization setting of the Q06CCPU-V(-B) Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Hardware self-diagnostic test and initialization setting Starting the C Controller module in the hardware self-diagnostic mode allows the module to perform the following hardware self-diagnostic tests and initialization setting.
Page 556 TROUBLESHOOTING (2) Before executing the hardware self-diagnostic test and initialization setting (a) Removing modules and distribution cables Remove all the distribution cables and modules except for the power supply module and C Controller module from the C Controller system. Note that distribution cables must be connected for executing Mode 3 (RS-232 diagnostic test).
Page 557 TROUBLESHOOTING (3) Selecting a mode in the hardware self-diagnostic mode (a) Before switching the mode to the hardware self-diagnostic mode Be sure to perform operations described in Page 16-85, Section 16.5.2 (2). (b) Switching to the hardware self-diagnostic mode 1) Move the RESET/SELECT switch to the RESET position, and hold the RUN/ STOP/MODE switch at the MODE position.
Page 558 TROUBLESHOOTING (c) Switching the mode Set the RUN/STOP/MODE switch to "STOP", and select the mode by moving the RESET/SELECT switch to the "SELECT" position. • Mode 1 : Move the RESET/SELECT switch to the SELECT position once. The RUN LED turns on. •...
Page 559 TROUBLESHOOTING (4) Executing the hardware self-diagnostic test and initialization setting POINT Do not power off the C Controller system or reset the C Controller module during the self-diagnostics and setting. Doing so may cause the C Controller module not to start normally. Shift the RUN/STOP/MODE switch from STOP to RUN to execute the diagnostics and setting.
Page 560 TROUBLESHOOTING (5) Confirming the hardware self-diagnostic test and initialization setting result (a) Normal completion 1) The flashing LED turns off during the diagnostics and setting. MODE CF CARD ERR. CH2 SD/RD USER Figure 16.29 LED indication for normal completion (for the Q06CCPU-V) 2) Turn the power off to finish the hardware self-diagnostic mode.
Page 561 TROUBLESHOOTING (b) Abnormal end The ERR. LED starts flashing upon error detection during the diagnostics and setting, and the LEDs turn on corresponding to the diagnostics or setting of the error. Upon detection of the failure, the diagnostics and setting will be terminated. Table 16.20 LED indication for error completion (error detection) (for the Q06CCPU-V) Error detection LED indication...
Page 562 TROUBLESHOOTING 16.6 Diagnostics and Restoration of the Standard RAM, Standard ROM, and CompactFlash Card Drives Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B An error may occur in the file system if any of the following drives is incorrectly used. • Standard RAM drive • Standard ROM drive •...
Page 563 TROUBLESHOOTING (2) How to restore the FAT file system of the drive If an error is detected in the file system, the FAT format can be restored by either of the following methods. • Use the restore function of the chkdsk command ( (3) in this section) •...
Page 564 TROUBLESHOOTING (c) Execution example of the chkdsk command The following explains how to diagnose the standard RAM of the Q12DCCPU-V by using the chkdsk command from the Telnet tool. This operation procedure can be applied to diagnostics and restoration of the standard ROM or a CompactFlash card.
Page 565 APPENDICES APPENDICES Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Appendix 1 Function Processing Time Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This chapter explains the time required for processing functions when one user program created using bus interface functions and/or MELSEC data link functions is executed with the task priority set to 100.
Page 566 (a) I/O access time 1) When accessing an input module QX42 (Start input number: X0) in a single CPU system Table APPX.1 Access time Communication Access time Function size Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B High-speed 1 bit QBF_X_In_BitEx access Normal access 1 bit...
Page 567 1) When accessing the QJ61BT11N (Start I/O number: 0) in a single CPU system, where the block data assurance per station function is disabled by CC- Link utility Table APPX.3 Access time Communication Access time Function size Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B 1 word 15 s 16 s 16 s QBF_FromBuf...
Page 568 APPENDICES 3) When accessing an intelligent function module other than the QJ61BT11N in a single CPU system Table APPX.6 Access time Communication Access time Function size Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B 1 word 14 s 16 s 16 s QBF_FromBuf 64 words...
Page 569 CPU in a multiple CPU system (CPU No.1: Q26UDHCPU, CPU No.2: C Controller module) Table APPX.9 Access time Communication Access time Function size Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B 1 word QBF_FromBuf 64 words 18 s 512 words...
Page 570 APPENDICES Appendix 2 External Dimensions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Appendix 2.1 Q12DCCPU-V (1) Q12DCCPU-V 23(0.91) 27.4(1.08) 115(4.53) (Unit: mm (inches)) Figure APPX.1 External dimensions APPX Appendix 2 External Dimensions Appendix 2.1 Q12DCCPU-V...
Page 571 RS-232 cable is used. For the Q12DCCPU-CBL, "cable's outside diameter 4" is 22 mm (0.87 inches). (2) Q12DCCPU-CBL 530 20 (20.87 0.79) 14.6 (0.57) (0.59) (Unit: mm (inches)) Figure APPX.2 External dimensions APPX Appendix 2 External Dimensions Appendix 2.1 Q12DCCPU-V...
Page 572 APPENDICES Appendix 2.2 Q06CCPU-V 23 (0.91) 89.3 (3.52) 27.4 (1.08) (0.21) Cable's outside diameter 4+10 (Unit: mm (inches)) Figure APPX.3 External dimensions * 1 The bend radius (R1: reference value) near the connector must be "cable's outside diameter 4" or more when a twisted pair cable is used. * 2 The bend radius (R2: reference value) near the connector must be "cable's outside diameter 4"...
Page 573 APPENDICES Appendix 2.3 Q06CCPU-V-B 23(0.91) 27.4(1.08) 89.3(3.52) (0.21) Cable's outside diameter 4 10 (Unit: mm (inches)) Figure APPX.4 External dimensions * 1 The bend radius (R1: reference value) near the connector must be "cable's outside diameter 4" or more when a twisted pair cable is used. * 2 The bend radius (R2: reference value) near the connector must be "cable's outside diameter 4"...
Page 574 APPENDICES Appendix 3 Transportation Precautions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B When transporting lithium batteries, follow the transportation regulations. Appendix 3.1 Regulated models Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Lithium batteries for the C Controller module are classified as shown in the table below. Table APPX.11 Regulated models...
Page 575 APPENDICES Appendix 4 Handling of Batteries and Devices with Built-in Batteries in EU Member States Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section describes the precautions for disposing of waste batteries in EU member status and exporting batteries and/or devices with built-in batteries to EU member states.
Page 576 APPENDICES Appendix 4.2 Exportation precautions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The new EU Battery Directive (2006/66/EC) requires the following when marketing or exporting batteries and/or devices with built-in batteries to EU member states. • To print the symbol on batteries, devices, or their packaging •...
Page 577 APPENDICES Appendix 5 Characters Applicable to User Names and Passwords Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the characters applicable to user names and passwords set on each utility. (1) Characters applicable to user names Alphanumeric characters can be used, and a space, "(quotation mark), and :(colon) are not applicable.
Page 578 APPENDICES (2) Characters applicable to passwords Alphanumeric characters can be used, and a space, "(quotation mark), and @(at mark) are not applicable. The following ASCII code table shows applicable characters. Table APPX.13 Characters applicable to passwords Higher 4 bits Applicable Not applicable APPX - 14...
Page 579 APPENDICES Appendix 6 List of Special Relays Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The special relay (SM) is an internal relay whose application is fixed in a C Controller module. For this reason, the special relay cannot be used in the same way as other internal relays are used in user programs.
Page 580 APPENDICES Appendix 7 List of Special Registers Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The special register (SD) is an internal register whose application is fixed in a C Controller module. For this reason, the special relay cannot be used in the same way as other internal relays are used in user programs.
Page 581 APPENDICES (1) Diagnostic information Table APPX.17 Special registers Setting side Number Name Description Detailed description (setting time) Diagnostic error • The error code occurred in diagnosis in diagnosis is stored as a binary code. Diagnostic error code • The information is the same as the latest error code. (Error) •...
Page 582 APPENDICES Table APPX.17 Special registers (continued) Setting side Number Name Description Detailed description (setting time) • Common information corresponding to the error code (SD0) is stored. • The following three types of information are stored. • Common error information type can be determined by "Common information category code"...
Page 583 APPENDICES Table APPX.17 Special registers (continued) Setting side Number Name Description Detailed description (setting time) Base No./power supply No. Item Base No. Power supply No. SD10 (Empty) SD11 SD12 SD13 Common error Common error SD14 SD15 information information (Error) SD15 1: Error occurring in power supply 1 2: Error occurring in power supply 2 "Power supply 1"...
Page 584 APPENDICES (2) System information Table APPX.18 Special registers Setting side Number Name Description Detailed description (setting time) C Controller • The switch status of the C Controller module is stored. SD200 Switch status module switch 0: RUN, 1: STOP (System) status •...
Page 585 APPENDICES (4) Fuse blown module Table APPX.20 Special registers Setting side Number Name Description Detailed description (setting time) • The output module numbers (units of 16 points), which are in the fuse blown status, are entered in the bit pattern. (If parameters are used, the set numbers are entered.) b15 b14 b13 b12 b11b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0 SD1300...
Page 586 APPENDICES Appendix 8 Parameter Number List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B A parameter number is displayed on the Detailed event information screen of C Controller setting utility when an error occurs in parameter setting. ( Page 16-34, Section 16.3) This section provides the tables indicating parameter numbers and where each parameter is to be set.
Page 587 APPENDICES (2) Parameter No. list The following table shows the parameter numbers and where each of them is to be set. Table APPX.25 Parameter No. list Parameter No. Item Utility Type Model name 0400 I/O assignment C Controller setting utility Points Start X/Y (Start I/O No.) Base model...
Page 588 APPENDICES Table APPX.25 Parameter No. list (continued) Parameter No. Item Utility 3000 WDT(Watchdog timer) setting C Controller setting utility Battery check 3001 Error check Fuse blown check C Controller setting utility Module verification Operation mode at the time of Fuse blown 3002 C Controller setting utility Module verify error...
Page 589 APPENDICES Appendix 9 Connection with GX Works2/GX Developer Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the setting method of when connecting GX Works2/GX Developer to a C Controller module. This section does not cover precautions and tips on the use of GX Works2/GX Developer.
Page 590 APPENDICES 2) Set "PC side I/F" to "Serial USB". Set the detailed setting dialog box as follows. • Select "USB". RS-232C cannot be used. 3) Set "PLC side I/F" to "PLC module". Set the detailed setting dialog box as follows. •...
Page 591 APPENDICES • To use the GOT (Ethernet) transparent function, set the following GOT (Ethernet) transparent setting dialog box as follows. • For "PLC type", select "QnUDE(H)". • For "IP address", set the IP address of the connecting C Controller module. For details on the GOT transparent, refer to the following.
Page 592 APPENDICES (b) Ethernet connection To access another CPU module of a multiple CPU system from the C Controller module via Ethernet, follow the procedure below. POINT • To connect GX Works2 to the C Controller module via Ethernet, built-in Ethernet port open settings need to be configured on the <<System settings>>...
Page 593 APPENDICES 2) Set "PC side I/F" to "Ethernet board". Set the detailed setting dialog box as follows. • "Network No." and "Station No."do not need to be changed because they are not used. • For "Protocol", select either in "TCP" or "UDP". 3) Set "PLC side I/F"...
Page 594 APPENDICES (2) GX Developer (a) USB connection To access another CPU module of a multiple CPU system from the C Controller module via USB, follow the procedure below. 1) [Online] Select [Transfer setup]. 2) Set "PC side I/F" to "Serial USB". Set the detailed setting dialog box as follows.
Page 595 APPENDICES 3) Set "PLC side I/F" to "PLC module". Set the detailed setting dialog box as follows. • For "PLC mode", select "QCPU (Q mode)". • The GOT (direct) transparent function cannot be used. Do not check the box. • To use the GOT (Ethernet) transparent function, set the GOT (Ethernet) transparent setting dialog box as follows.
Page 596 APPENDICES (b) Ethernet connection To access another CPU module of a multiple CPU system from the C Controller module via Ethernet, follow the procedure below. POINT • To connect GX Developer to the C Controller module via Ethernet, built-in Ethernet port open settings need to be configured on the <<System settings>>...
Page 597 APPENDICES 2) Set "PC side I/F" to "Ethernet board". Set the detailed setting dialog box as follows. • "Network No." and "Station No."do not need to be changed because they are not used. • For "Protocol", select either in "TCP" or "UDP". 3) Set "PLC side I/F"...
Page 598 APPENDICES Appendix 9.2 Accessing other stations Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B To access other stations from the C Controller module via USB or Ethernet, follow the procedure below. (1) GX Works2 1) INavigation window Select [Connection Destination]. 2) Set "PC side I/F" and "PLC side I/F" in the same way as for accessing another CPU in a multiple CPU system.
Page 599 APPENDICES 4) When "Other station (Single network)" is specified for "Other station", specify accessed network type for "Network route". When "Other station (Co-existence network)" is specified for "Other station", for "Network route" specify the accessed network type to which the C Controller module is connected.
Page 600 APPENDICES POINT Ethernet is assumed to be the same type of network as CC-Link IE controller network, MELSECNET/H, or MELSECNET/10. For this reason, when a combined system of Ethernet, CC-Link IE controller network, MELSECNET/H, or MELSECNET/10 is used, specify "Other station (single network)".
Page 601 APPENDICES Appendix 10 Connection with MX Component Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains the setting method of when connecting MX Component to a C Controller module. This section does not cover precautions and tips on the use of MX Component.
Page 602 APPENDICES Next > 3) Set the personal computer side interface as follows, and click the button. • Select "USB" for "PC side I/F". 4) Set the programmable controller side interface as follows, and click the Next > button. • Select "CPU module" for "PLC side I/F". •...
Page 603 APPENDICES 6) Input a comment, and click the Finish button. POINT When the access destination is the C Controller module, device function settings need to be configured on the <<Device settings>> tab of the C Controller setting utility. For details, refer to the following. C Controller Module User's Manual (Utility Operation, Programming) APPX Appendix 10 Connection with MX Component...
Page 604 APPENDICES (2) Ethernet connection To access the host station from the C Controller module via Ethernet, follow the procedure below. 1) Start the communication setting wizard from the communication setting utility. 2) Select a value for logical station number, and click the Next >...
Page 605 APPENDICES 4) Set the programmable controller side interface as follows, and click the Next > button. • Select "CPU module" for "PLC side I/F". • When setting a host name for "Host (IP Address)", input the name of the hosts file in no more than 64 characters. When setting an IP address, input the IP address of the C Controller module to be connected.
Page 606 APPENDICES Finish 6) Input a comment, and click the button. POINT • When the access destination is the C Controller module, device function settings need to be configured on the <<Device settings>> tab of the C Controller setting utility. For details, refer to the following. C Controller Module User's Manual (Utility Operation, Programming) •...
Page 607 APPENDICES Appendix 10.2 Accessing other stations To access other stations from the C Controller module via USB or Ethernet, follow the procedure below. 1) Start the communication setting wizard from the communication setting utility. 2) Select a value for logical station number, and click the Next >...
Page 608 APPENDICES Next > 5) Configure the other station setting as follows, and click the button. • Select the CPU type of the other station for "CPU type". • Input the network number of the other station for "Network No". • Input the station number of the other station for "Station No". •...
Page 609 1)Q12DCCPU-V 2)Q06CCPU-V 3)Q06CCPU-V-B First 5 digits of serial number Software version of Function SW3PVC-CCPU Partial change on C Controller modules • Supporting the Q12DCCPU-V Version3.03D or later • Not supporting the Q06CCPU-V-H01 12042 or Supporting more than one QI60 (interrupt module)
Page 610 Addition of high speed mode to argument "sFlg" of a function (QBF_WriteSRAM 13032 or Version3.06G or later function) used to write data into Battery-backed-up RAM (user area) later 15102 or Supporting Q12DCCPU-V (Extended mode) Version3.09K or later later 15102 or ® Version3.09K or later...
Page 611 APPENDICES (2) SW3PVC-CCPU Table APPX.27 Functions added to SW PVC-CCPU 1)Q12DCCPU-V 2)Q06CCPU-V 3)Q06CCPU-V-B First 5 digits of serial number Software version of Function SW3PVC-CCPU Partial change on the operating environment for SW3PVC-CCPU ® ® • Not compatible with Microsoft WindowsNT Workstation Operating System Version4.0...
Page 612 APPENDICES Memo APPX - 48 Appendix 11 Functions Added by Version Upgrade...
Page 613 I/O number of CPU module ·························· 12-12 Data register (D) ············································9-3 I/O sharing when using multiple CPUs ··············14-6 Default IP setting mode ································· 6-75 Q06CCPU-V(-B) ······································· 6-84 Q12DCCPU-V ·········································· 6-75 Detail mode ················································ 7-10 Life of CompactFlash card ·····························6-70 Device list·····················································9-1 Link data transfer processing time CC-Link IE controller network·······················5-58...
Page 614 MELSECNET/H ········································5-31 RUN status ·················································· 3-8 Link device access CC-Link IE controller network ······················5-42 MELSECNET/H ········································5-15 Self-diagnostic function································· 4-20 Link device refresh Sequence program control function ················13-43 CC-Link IE controller network ······················5-48 Setting the number of CPUs ·························· 14-4 MELSECNET/H ········································5-21 Software version ·········································...
Page 615 WARRANTY Please confirm the following product warranty details before using this product. 1. Gratis Warranty Term and Gratis Warranty Range If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product within the gratis warranty term, the product shall be repaired at no cost via the sales representative or Mitsubishi Service Company.
Page 616 CompactFlash is either a registered trademark or a trademark of SanDisk Corporation. Ethernet is a registered trademark of Fuji Xerox Corporation in Japan. Microsoft, Windows, Windows Vista, and Windows XP are either registered trademarks or trademarks of Microsoft Corpora- tion in the United States and/or other countries. Tornado, VxSim, VxWorks, and Wind River are either registered trademarks or trademarks of Wind River Systems, Inc.
Page 618 SH(NA)-080766ENG-O(1710)KWIX MODEL: Q12DCCPU-V-U-HK-E MODEL CODE: 13JZ17 HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN NAGOYA WORKS : 1-14 , YADA-MINAMI 5-CHOME , HIGASHI-KU, NAGOYA , JAPAN When exported from Japan, this manual does not require application to the Ministry of Economy, Trade and Industry for service transaction permission.

This manual is also suitable for:

Sw3pvc-ccpu-e Q06ccpu-v Q06ccpu-v-b

Mitsubishi Electric Q12DCCPU-V User Manual

Quick Links

Related Manuals for Mitsubishi Electric Q12DCCPU-V

Summary of Contents for Mitsubishi Electric Q12DCCPU-V

This manual is also suitable for:

Table of Contents