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

This manual is also suitable for:

Q06ccpu-v-h01

Mitsubishi MELSEC-Q Series User Manual

Chapter1 Overview

Chapter2 System Configuration

Chapter3 Specifications

Chapter4 Functions

Chapter5 Settings And Procedures before Operation

Chapter6 I/O Number Assignment

Chapter7 Memories And Files Handled by Ccontroller Module

Chapter8 Installing And Uninstalling Sw[]Pvc-Ccpu

Chapter9 Utility Operation

Chapter10 Functions And Programming

Chapter11 Overview Of Multiple Cpu System

Chapter12 Multiple Cpu System Configuration

Chapter13 Multiple Cpu System Concept

Chapter14 Communications Between Cpu Modules

Chapter15 Parameters Added for Multiple Cpu System

CHAPTER16 PRECAUTIONS FOR USE of Ans SERIES MODULE

Chapter17 Starting Multiple Cpu System

Chapter18 Troubleshooting

Appendices

Appendix 1 Function Processing Time

Appendix 2 External Dimensions

Appendix 3 Transportation Precautions

Appendix 3.1 Applicable Model

Appendix 3.2 Transportation Guidelines

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

Appendix 4.1 Disposal Precautions

Appendix 4.2 Exportation Precautions

Appendix 5 Characters Usable for User Name and Password

Appendix 6 Parameter No. List

Appendix 7 Comparison

Quick Links

Troubleshooting

Related Manuals for Mitsubishi MELSEC-Q Series

Summary of Contents for Mitsubishi MELSEC-Q Series