Download  Print this page

Mitsubishi Electric Q12DCCPU-V User Manual

Melsec-q series c controller module.
Hide thumbs

Advertisement

C Controller Module User's Manual
(Utility Operation, Programming)
-Q12DCCPU-V (Basic mode)
-Q06CCPU-V
-Q06CCPU-V-B
-SW3PVC-CCPU-E

Advertisement

Table of Contents

   Also See for Mitsubishi Electric Q12DCCPU-V

   Related Manuals for Mitsubishi Electric Q12DCCPU-V

   Summary of Contents for Mitsubishi Electric Q12DCCPU-V

  • Page 1 C Controller Module User's Manual (Utility Operation, Programming) -Q12DCCPU-V (Basic mode) -Q06CCPU-V -Q06CCPU-V-B -SW3PVC-CCPU-E...
  • Page 3: Safety Precautions

    SAFETY PRECAUTIONS (Read these precautions before using this product.) Before using this product, please read this manual and the relevant manuals carefully and pay full attention to safety to handle the product correctly. The instructions given in this manual are concerned with this product only. For the safety instructions of the programmable controller system, please read the CPU module user's manual.
  • Page 4 [Setup and Maintenance Precautions] WARNING Configure safety circuits external to the C Controller module to ensure that the entire system operates safely even when a fault occurs in the external power supply or the C Controller module. For the following controls, configure an interlock circuit in the user program to ensure that the entire system will always operate safely.
  • Page 5: Conditions Of Use For The Product

    CONDITIONS OF USE FOR THE PRODUCT (1) Mitsubishi C Controller system ("the PRODUCT") shall be used in conditions; i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident; and ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the case of any problem, fault or failure occurring in the PRODUCT.
  • Page 6: Revisions

    REVISIONS *The manual number is given on the bottom left of the back cover. Print date Revision Manual number Jun., 2009 SH(NA)-080767ENG-A First edition Jan., 2010 SH(NA)-080767ENG-B Partial correction SAFETY PRECAUTIONS, Chapter 11 Aug., 2010 SH(NA)-080767ENG-C Partial correction GENERIC TERMS AND ABBREVIATIONS, GLOSSARY, Section 2.1, 2.2, 3.5, 3.6, 4.1,4.2, 4.4, 4.6, 4.7, 4.13, 5.1, 5.4, 6.1, 6.5, 7.1, 7.4, 8.9, 9.2, 9.6, 9.8, 9.10, 10.13.1 to 10.13.4, Chapter 12, Chapter 13, Appendix 1 Addition...
  • Page 7 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 8: Precautions

    PRECAUTIONS The following precautions are given in this section. Precautions Reference page For installation, uninstallation Page A-6 For each utility Page A-6 For programming Page A-7 For debugging a program Page A-11 For using FTP Page A-16 For the Wind River Systems product Page A-16 (1) Precautions for installation and uninstallation (a) Installation by overwriting...
  • Page 9 (d) Parameters Parameters written from utility other than Device monitoring utility to a C Controller module will take effect when the C Controller module is powered off and then on or is reset. Written parameters will not take effect by changing the C Controller module status from STOP to RUN by remote operation or by a switch.
  • Page 10 [For the Q12DCCPU-V] Use the Telnet tool. [For the Q06CCPU-V(-B)] Execute from the Tornado Shell. Example) When using the Telnet tool on the Q12DCCPU-V Command execution Port numbers being used in a C Controller module. Figure A.1 When using Telnet tool on the Q12DCCPU-V 5) When writing a file from a user program in the Q06CCPU-V(-B) Do not write a file to the standard ROM.
  • Page 11: Precautions ··············································································································4

    7) Relation between system tasks and the system watchdog timer, user watchdog timer, and link device refresh cycles When using any of the following functions, set a sufficiently long time for each of the system watchdog timer, user watchdog timer, and link device refresh cycles.
  • Page 12 (d) Login user 1) Default account To prevent illegal access, delete the default account (User name and password) using the loginUserDelete function. 2) Retaining login user setting The login user settings are cleared and return to default when the C Controller module is powered off or is reset.
  • Page 13: Precautions ··············································································································6

    C Controller module to Workbench or to Tornado. The serial No. and function version of the file to be specified must be identical with those of the C Controller module. (Example for Q12DCCPU-V: Q12DCCPU- V_10121-B) ( Page 9-31, Section 9.7)
  • Page 14 The timeout time for the C Controller module side Telnet (TCP) connection can be changed by setting the values in the calculation formula by the following setting methods. [Calculation formula for the Q12DCCPU-V] The timeout time is determined by the following calculation formula. Timeout time = net.inet.tcp.keepidle...
  • Page 15 [Calculation for the Q06CCPU-V(-B)] The timeout time is determined by the following calculation formula. Timeout time = tcp_keepidle + (tcp_keepintvl tcp_keepcnt) [s] Initial value: 15000 (4 hours and 10 minutes) tcp_keepidle: Time from line disconnection to the first retry (s) Initial value: 14400 tcp_keepintvl: Retry interval (in 0.5s units) Initial value: 150...
  • Page 16 (c) Precautions for executing the Shell command from Workbench Shell or Tornado Shell, or the Telnet tool 1) When executing the Shell command from Workbench Shell or Tornado Shell Pay attention to the following since the entered Shell commands operate on the task of priority 1 in the C Controller module.
  • Page 17 (personal computer) operate on the task of the following priorities in the C Controller module. C Controller module Priority Q12DCCPU-V Q06CCPU-V(-B) When using Shell commands, pay attention to the following: • Only alphanumeric characters and special characters can be used.
  • Page 18 (5) Precautions for use of FTP (a) When reading out files from the C Controller module A 426 (Data connection error) occurs if many files are read (downloaded) by using FTP. In that case, take following actions and read files again. •...
  • Page 19: Table Of Contents

    INTRODUCTION Thank you for purchasing the C Controller module. Before using this product, please read this manual carefully and develop familiarity with the functions and performance of the C Controller module to handle the product correctly. CONTENTS SAFETY PRECAUTIONS ··········································································································· A - 1 CONDITIONS OF USE FOR THE PRODUCT ·················································································...
  • Page 20 CHAPTER 4 C CONTROLLER SETTING UTILITY 4 - 1 to 4 - 50 C Controller Setting Utility Function List ··········································································· 4 - 1 Module Information Tab································································································ 4 - 2 Event History Tab ······································································································· 4 - 4 SRAM Monitoring Tab·································································································· 4 - 8 Module Monitoring Tab································································································4 - 13 Online Operation Tab··································································································4 - 21 System Settings Tab···································································································4 - 30...
  • Page 21 Programming Procedure ·······························································································9 - 8 Creating and Compiling a New Project of User Program ······················································9 - 9 9.4.1 For the Q12DCCPU-V ····························································································9 - 9 9.4.2 For the Q06CCPU-V(-B) ······················································································· 9 - 17 Programming Flow for Bus Interface Functions ································································ 9 - 23 Precautions for Functions ····························································································...
  • Page 22 9.10 Device Types for Bus Interface Functions ·······································································9 - 56 CHAPTER 10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 10 - 1 to 10 - 45 10.1 Outline of MELSEC Data Link Functions ·········································································10 - 1 10.2 MELSEC Data Link Function List···················································································10 - 4 10.3 Programming Procedure······························································································10 - 4 10.4...
  • Page 23: About Manuals

    C Controller Module User's Manual (Hardware Design, Function Explanation) Describes the system configuration, specifications, functions, handling instructions, wiring, and SH-080766ENG troubleshooting of the C Controller module (Q12DCCPU-V (Basic mode), Q06CCPU-V, Q06CCPU-V- (13JZ17) (Sold separately) MELSEC-Q C Controller Module User's Manual...
  • Page 24 CC-LINK UTILITY Target Settings Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B A logical station No. is set from the Target settings tab. The logical station No. is used, when a target station is a multiple CPU system, to access a programmable controller CPU other than the control CPU of the target station.
  • Page 25: How To Use This Manual

    HOW TO USE THIS MANUAL This manual is used to develop familiarity with parameter settings, monitoring, and programming required for using the C Controller module. Refer to the following list when using this manual. Chapter Description CHAPTER 1 Features of SW3PVC-CCPU CHAPTER 2 Operating environment, installing, uninstalling of SW3PVC-CCPU CHAPTER 3 to...
  • Page 26: Generic Terms And Abbreviations

    In principle, 'Q12DCCPU-V' indicates Q12DCCPU-V (Basic mode). Q12DCCPU-V When the classification is needed for such as comparison with other modes, 'Q12DCCPU-V (Basic mode)' and ‘Q12DCCPU-V (Extended mode)’ are mentioned. Q12DCCPU-V Status that Q12DCCPU-V is initialized with the basic mode (Basic mode)
  • Page 27 (2) CPU modules Generic term/abbreviation Description Generic term for the A1NCPU, A0J2HCPU, A1SCPU, A1SHCPU, A1SJCPU, A1SJHCPU, A2CCPU, A2CJCPU, A2NCPU, A2NCPU-S1, A2SCPU, A2SHCPU, ACPU A2ACPU, A2ACPU-S1, A2UCPU, A2UCPU-S1, A2USCPU, A2USCPU-S1, A2USHCPU-S1, A3NCPU, A3ACPU, A3UCPU, and A4UCPU Generic term for the Q2ACPU, Q2ACPU-S1, Q2ASCPU, Q2ASCPU-S1, Q2ASHCPU, QnACPU Q2ASHCPU-S1, Q3ACPU, Q4ACPU, and Q4ARCPU QCPU (A mode)
  • Page 28 (3) Network modules and PC boards Generic term/abbreviation Description CC-Link module Generic term for the QJ61BT11 and QJ61BT11N CC-Link/LT module Generic term for the QJ61CL12 Generic term for the Q81BD-J61BT11 and Q80BD-J61BT11N CC-Link system master/ CC-Link board local interface boards, A80BD-J61BT11 CC-Link system master/local interface board, and A80BD-J61BT13 CC-Link interface board CC-Link IE Controller Network Generic term for the QJ71GP21-SX and QJ71GP21S-SX...
  • Page 29 (4) Power supply modules and base units Generic term/abbreviation Description Generic term for the Q33B, Q35B, Q38B, and Q312B main base units on which the CPU modules, Q series power supply module, 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 on which the C Controller module, Basic model QCPU, High Performance model QCPU,...
  • Page 30 (5) Others Generic term/abbreviation Description Q series Abbreviation for the programmable controllers, MELSEC-Q series AnS series Abbreviation for the programmable controllers, compact MELSEC-A series Ethernet Generic term for the 100BASE-TX and 10BASE-T network systems MELSECNET/H Generic term for the Q series MELSECNET/H network system Abbreviation for the Mitsubishi Graphic Operation Terminal GX Works2 Product name of the software package for the MELSEC programmable controllers...
  • Page 31: Glossary

    GLOSSARY Definitions of the terms used in this manual are explained below. Term Description FTP is an abbreviation for File Transfer Protocol, which is used to transfer data files. Telnet Network protocol, or virtual terminal software, that enables remote login in TCP/IP networks. CompactFlash card A storage card regulated by the 'CF+ and CompactFlash Specification' issued by the (CF card)
  • Page 32: Product Organization

    : Available, : Not available * 1 First five digits of serial number * 2 For Q12DCCPU-V earlier than "15102", the mode cannot be changed. Q12DCCPU-V earlier than "15102" is regarded as the basic mode in this manual. PACKING LIST The following is the product line of the C Controller module.
  • Page 33 Memo - 31...
  • Page 34: Chapter 1 Overview

    Configuring a multiple CPU system (Start-up procedure and I/O No. Details Outline assignment) (To the next page) * 1 For Q24DHCCPU-V, Q24DHCCPU-VG, Q24DHCCPU-LS, Q26DHCCPU-LS, or Q12DCCPU-V (Extended mode), refer to the following manual. MELSEC-Q C Controller Module User's Manual...
  • Page 35 Details codes Checking Event No. Details * 1 For Q24DHCCPU-V, Q24DHCCPU-VG, Q24DHCCPU-LS, Q26DHCCPU-LS, or Q12DCCPU-V (Extended mode), refer to the following manual. MELSEC-Q C Controller Module User's Manual * 2 For Q24DHCCPU-V, Q24DHCCPU-VG, Q24DHCCPU-LS, Q26DHCCPU-LS, or Q12DCCPU-V (Extended mode), refer to the following manual.
  • Page 36: Features

    OVERVIEW Features (1) Easy setting with utilities Various settings, such as parameter setting for the C Controller module and multiple CPU setting, can be easily configured by using C Controller setting utility. Also, parameters for the following modules can be set, and device monitoring of an access target can be configured and executed.
  • Page 37 OVERVIEW (2) Efficient development of user programs with integrated development environment (a) For the Q12DCCPU-V Workbench (CW Workbench or Wind River Workbench), an integrated development environment, provides efficient development of user programs with C or C++ language. Providing a development group that covers all the developing processes from "software development", "system diagnostics", "testing", to "manufacturing",...
  • Page 38: Chapter 2 Installation And Uninstallation Of Software Package

    •Windows 2000 (Professional SP4 or later) Development tool CW Workbench For product requirements for CW Workbench, refer to the CW Workbench Operating Manual. Q12DCCPU-V Wind River Workbench 2.6.1 Update For product requirements for Wind River Workbench, refer to the manual of Wind River Workbench. Q06CCPU-V, Tornado 2.1.0 for Hitachi SuperH Cumulative patch 1...
  • Page 39 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE Table 2.2 Requirements for operating system and personal computer Personal computer Operating system Memory Windows 10 (Home, Pro, Enterprise, Education) ® Intel Core 2 Duo Windows 8.1, Windows 8.1 (Pro, Enterprise) 1GB or more 1GHz or more Windows 8, Windows 8 (Pro, Enterprise) Windows 7 (Starter, Home Premium, Professional, Ultimate, Enterprise)
  • Page 40 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE POINT 1. When installing or uninstalling SW3PVC-CCPU and when operating utility, logon as a user with Administrator attribute. 2. When using Windows 2000 Professional, large fonts (detailed setting in the screen properties) cannot be used. If used, this product may not operate properly.
  • Page 41: Installation

    INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE Installation (1) Preparation for installation Before installation, perform the following. 1) Logon as a user with Administrator attribute. ® 2) Remove all the applications in the start up, restart Windows , and logon again as a user with Administrator attribute.
  • Page 42 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE (2) Installation procedure 1) Insert a CD-ROM, this product, to the CD-ROM drive. 2) Double-click "Setup.exe" in the CD-ROM folder to start the installer of SW3PVC-CCPU. 3) Proceed the installation following the instructions provided by the installer. For the setting selection, refer to the following instruction.
  • Page 43 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE Selecting installation destination Specify the folder of installation destination. Next> •When installation destination is "C:\MELSEC", click the button. Browse •When installation destination is other than "C:\MELSEC", click the button and specify the folder of installation destination. ®...
  • Page 44 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE (3) Operation after installation ® ® (a) For Windows XP or Windows Vista ® If the Windows Firewall was not turned on during the installation, turn it on, referring to the following. ® Open the Control Panel of Windows , click the following ®...
  • Page 45 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE (From the previous page) If no utility is displayed or any one is missing, click the Add Program button. Select a utility of SW3PVC-CCPU, and click the button. Repeat this operation until all utilities of SW3PVC-CCPU are added.
  • Page 46 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE ® (b) For Windows 7 or later ® If the Windows Firewall was not turned on during the installation, turn it on, referring to the following. ® Open the Control Panel of Windows , and click "System and Security".
  • Page 47 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE (From the previous page) If no utility is displayed or any one is missing, click the Allow another program button to display the left dialog box. Select a utility of SW3PVC-CCPU, and click the button.
  • Page 48 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE (From the previous page) Click "Turn Windows Firewall on or off". If the left dialog box appears, click the button. Check that the "Block all incoming connections, including those in the list of allowed programs" checkbox is not selected, and click the button.
  • Page 49: Uninstallation

    INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE Uninstallation Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Preparation for uninstallation Perform the following before uninstallation. 1) Logon as a user with Administrator attribute. 2) Terminate all the running utilities. POINT 1. If uninstallation cannot be performed, check if the following file names are displayed as image names in the process of task manager.
  • Page 50 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE (2) Uninstallation procedure ® 1) Open the Control Panel of Windows 2) Open the screen for uninstallation on applicable operating system. Table 2.5 Screen for uninstallation Operating system Screen ® Add/Remove Programs Windows 2000 Professional ®...
  • Page 51: Chapter 3 Common Utility Operations

    COMMON UTILITY OPERATIONS CHAPTER 3 COMMON UTILITY OPERATIONS Utility List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Table 3.1 Utilities in SW3PVC-CCPU Availability Reference Utility Description Q12DCCPU Q06CCPU Q06CCPU page -V-B Functions of C Controller setting utility are as follows. •Displays the module information (LED status, switch status,...
  • Page 52: Activating Utility

    COMMON UTILITY OPERATIONS Activating Utility Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B To activate a utility, select the menu in [MELSEC] [C Controller] from "Start" of ®*1. Windows * 1 [Start screen] [All apps] or [Start] [All Programs] Activates Bus Interface Function HELP Activates C Controller setting utility...
  • Page 53: Exiting Utility

    COMMON UTILITY OPERATIONS Exiting Utility Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Utility other than Device monitoring utility Exit To exit utility other than Device monitoring utility, click the button at the bottom right of the screen. Click. Figure 3.2 Exiting C Controller setting utility (2) Device monitoring utility To exit Device monitoring utility, select [Menu] [Exit] on the menu bar.
  • Page 54: Specifying Cpu Type

    Description Specifies a C Controller module to which parameters are set or to be monitored. CPU type (Default: "Q12DCCPU-V") The specified CPU type is fixed and this screen will not be displayed on and after next utility operation. CPU type fixed To set back to the default (CPU type not fixed), select [Specify CPU type] in the system menu to open this screen and deselect the check box.
  • Page 55: Setting Connection Target

    COMMON UTILITY OPERATIONS Setting Connection Target Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Connect an development environment (personal computer) and the C Controller module. (1) Operating procedure Select "192.168.3.3 (Default)" in "Target module". When the IP address of the C Controller module has been changed, enter the IP address or host name currently set.
  • Page 56 Table 3.3 Drives used for reading parameters Model Drive The drive in which parameters of the operating C Q12DCCPU-V with serial No. (first 5 digits) Controller module are stored "12042" or later (Standard RAM or CompactFlash card) Q12DCCPU-V with serial No. (first 5 digits) Standard RAM "12041"...
  • Page 57 COMMON UTILITY OPERATIONS (2) Connection settings screen Figure 3.5 Connection settings screen Table 3.4 Description of the Connection settings screen Item Description Enter the IP address or host name of the C Controller module to be connected. Click to allow selection from the following. •Connection target history (Up to 8 data, common to all utilities) Target module •"192.168.3.3 (Default)"...
  • Page 58 COMMON UTILITY OPERATIONS (a) Detailed settings screen Enter values in "Communication check time" and "Retry count" used in Ethernet communication between a development environment (personal computer) and the C Controller module. Figure 3.6 Detailed settings screen Table 3.5 Description of the Detailed settings screen Item Description Set a communication check time in Ethernet communication between...
  • Page 59 COMMON UTILITY OPERATIONS Remark 1. Offline operation Parameters can be written to each utility offline. When writing parameters, a connection must be established with the C Controller module. 2. Changing connection target To connect with other target, open the "Connection settings" screen with the following operations and change the IP address or host name.
  • Page 60: Displaying The Help Screen

    COMMON UTILITY OPERATIONS Displaying the Help Screen Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Utilities other than Device monitoring utility To display the Help screen of utilities other than Device monitoring utility, click the Help button at the bottom right of the screen.
  • Page 61 COMMON UTILITY OPERATIONS ® ® (3) Windows Vista or Windows 7 or later ® ® When using Windows Vista or Windows 7 or later, the screen below may appear instead of the Help screen. Install the required software following the corrective action ®...
  • Page 62 COMMON UTILITY OPERATIONS Remark 1. The Help screens in SW3PVC-CCPU cannot be displayed simultaneously. Display one screen at a time. If another Help screen is started while a Help screen is being displayed, the first one is closed to display the one last opened. 2.
  • Page 63: Checking Version

    COMMON UTILITY OPERATIONS Checking Version Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Utilities other than Device monitoring utility To check the version of utilities other than Device monitoring utility, select [Version information] in the system menu. C Controller setting utility ..Page 4-46, Section 4.12 CC-Link utility ......
  • Page 64: Parameter Setting File

    COMMON UTILITY OPERATIONS Parameter Setting File Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Loading and saving parameter setting file The following indicates the procedure of reading/saving a parameter setting file. Load File 1) Click the button to load a parameter setting file. Save File Click the button to save a parameter setting file.
  • Page 65 COMMON UTILITY OPERATIONS Remark 1. The name of the parameter setting file currently used is displayed on the status bar in utilities other than Device monitoring utility. 2. The following table lists the extensions for parameter setting files. Table 3.8 Extensions for parameter setting file Utility Extension for parameter setting file C Controller setting utility...
  • Page 66: Displays On The Title Bar And Status Bar

    COMMON UTILITY OPERATIONS Displays on the Title Bar and Status Bar Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Figure 3.14 Title bar and status bar Table 3.10 Display on the title bar and status bar Display Utility name IP address or host address of the connection target C Controller module "Offiline"...
  • Page 67: Chapter 4 C Controller Setting Utility

    C CONTROLLER SETTING UTILITY CHAPTER 4 C CONTROLLER SETTING UTILITY C Controller Setting Utility Function List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Table 4.1 C Controller setting utility function list Availability Reference Name Description Q12DCCPU Q06CCPU Q06CCPU page -V-B Specifies a C Controller module to which parameters are set...
  • Page 68: Module Information Tab

    Displays the LED states of the C Controller module. LED information Note that the CH3 SD/RD indication for the Q12DCCPU-V and the CH2 SD/RD indication for the Q06CCPU-V(-B) are disabled. * 1 For part names and functions of the C Controller module, refer to the C Controller Module User's...
  • Page 69 This button cannot be clicked when: Error clear button •A stop error has occurred. •The Q12DCCPU-V with serial number (first 5 digits) "12041" or earlier is used. •The Q06CCPU-V(-B) is used. Drive information Displays drive information of the C Controller module.
  • Page 70: Event History Tab

    C CONTROLLER SETTING UTILITY Event History Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Precautions for the Event history tab (a) Event history update timing Event history is updated by acquiring the data from the C Controller module when a connection is established to the C Controller module in Connection settings or...
  • Page 71 C CONTROLLER SETTING UTILITY (2) Event history tab The events occurred in the C Controller module are displayed or saved in this tab. Figure 4.2 Event history tab Table 4.3 Description of the Event history tab Event history Module information SRAM monitoring Module monitoring Online operation...
  • Page 72 C CONTROLLER SETTING UTILITY (3) Detailed event information screen The detailed information of the event that is double-clicked on the Event history tab is displayed. ( Page 4-5). Figure 4.3 Detailed information screen Table 4.4 Description of the Detailed information screen Reference Item Description...
  • Page 73 C CONTROLLER SETTING UTILITY (4) Specifications of the Event history file A file format can be selected in "Files of type" on the following screen. Figure 4.4 Save As screen To use the text data of the Event history file in a user program etc., select "EventLog File(*.csv)"...
  • Page 74: Sram Monitoring Tab

    C CONTROLLER SETTING UTILITY SRAM Monitoring Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B WARNING For the following controls, configure an interlock circuit in the user program to ensure that the entire system will always operate safely. (1) Changing data of the running C Controller module by connecting...
  • Page 75 +00 +01 +02 +03 Address Display data Display data 56 34 12 34 56 78 12 34 56 78 For the For the Q12DCCPU-V Q06CCPU-V-B and Q06CCPU-V Figure 4.7 Display example when "32 bits" is selected 4.4 SRAM Monitoring Tab...
  • Page 76 C CONTROLLER SETTING UTILITY (3) Data settings screen Data can be entered into the battery-backed-up RAM from this screen. Target address Input data Figure 4.8 Data settings screen Table 4.7 Description of the Data settings screen Reference Item Description page Select a format of the value to be entered in "Input data".
  • Page 77 C CONTROLLER SETTING UTILITY (4) Restoration of battery-backed-up RAM data Binary battery-backed-up RAM data, which were saved in the personal computer, are restored to the C Controller module. Figure 4.9 Restore data dialog box (a) Restorable file specification Table 4.8 Restorable file specification Item Description Extension...
  • Page 78 C CONTROLLER SETTING UTILITY (5) Specifications of the battery-backed-up RAM data save file Battery-backed-up RAM data can be saved either in the CSV or binary format. A file format can be selected in "Files of type" on the following screen. Figure 4.10 Save As screen (a) Specifications of the CSV format To use the text data of the Battery-backed-up RAM data save file in a user...
  • Page 79: Module Monitoring Tab

    C CONTROLLER SETTING UTILITY Module Monitoring Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B WARNING For the following controls, configure an interlock circuit in the user program to ensure that the entire system will always operate safely. (1) Changing data of the running C Controller module by connecting...
  • Page 80 C CONTROLLER SETTING UTILITY (d) Monitored or tested module The monitoring from this screen and the following tests are performed for the module selected by "Slot No.". • Forced output of Output (Y) • Forced write to buffer memory • Forced write to CPU shared memory The setting in the "Type"...
  • Page 81 C CONTROLLER SETTING UTILITY (2) Module monitoring tab The status of input (X), output (Y), and buffer memory of the module installed to the selected slot are monitored on this tab. The forced output of the output (Y) and forced write to the buffer memory are allowed. Figure 4.12 Module monitoring tab Table 4.9 Description of the Module monitoring tab Module monitoring...
  • Page 82 C CONTROLLER SETTING UTILITY Table 4.9 Description of the Module monitoring tab (continued) Module monitoring Module information Event history SRAM monitoring Online operation System settings Reference Item Description page Starts or stops monitoring the C Controller module. Start monitoring "*" flashes in the upper right of the button during monitoring. Stop monitoring button These buttons are disabled in the offline status.
  • Page 83 C CONTROLLER SETTING UTILITY (3) System information screen Information of the C Controller system can be displayed on this screen. System configuration Figure 4.13 System information screen Table 4.10 Description of the System information screen Reference Item Description manual Displays the status of CPU modules that configure the C Controller system. Double-clicking the C Controller module or programmable controller CPU with an CPU status error opens the Error details screen.
  • Page 84 C CONTROLLER SETTING UTILITY Table 4.10 Description of the System information screen (continued) Reference Item Description page CPU status Error code help Selecting a C Controller module (own station) and clicking the button starts Help of C Controller setting utility, which displays help information of a current error.
  • Page 85 C CONTROLLER SETTING UTILITY (a) Error details screen Figure 4.14 Error details screen Table 4.11 Description of the Error details screen Item Description Reference Common error information Displays common information corresponding to the error code. Individual error information Displays individual information corresponding to the error code. * 1 For errors of the C Controller module, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
  • Page 86 C CONTROLLER SETTING UTILITY (4) Specifications of the system information save file A file format can be selected in "Files of type" on the following screen. Figure 4.15 Save As screen To use the text data of the system information save file in a user program, select "System Info File(*.csv)"...
  • Page 87: Online Operation Tab

    When writing parameters from each of the utilities to the following C Controller module, write them to the same drive. • Q12DCCPU-V whose serial number (first five digits) is "12042" or later If the parameters are written to different drives, those of the drive, which include C Controller setting parameters, will take effect.
  • Page 88 If the button is clicked with this checkbox selected, all parameters prior to writing." checkbox (for the (including the following) of all drives will be cleared before parameter writing. Q12DCCPU-V) •CC-Link module parameters "Clear all parameters before •MELSECNET/H module parameters writing."...
  • Page 89 C CONTROLLER SETTING UTILITY (3) Detailed settings screen The IP address, clock, MD function and Option for the C Controller module can be set on this screen. For the Q06CCPU-V-B, the MD function setting is not available. Figure 4.18 Detailed settings screen Table 4.13 Description of the Detailed settings screen IP address Clock...
  • Page 90 C CONTROLLER SETTING UTILITY (a) IP address tab The IP address for the C Controller module can be set in this tab. Figure 4.19 IP address tab Table 4.14 Description of the IP address tab IP address Clock MD function Option Reference Item...
  • Page 91 C CONTROLLER SETTING UTILITY 1) IP address setting • IP address setting range The following table indicates the IP addresses settable to the C Controller module. For the IP address setting, consult your network administrator (network planner or person in charge of IP addresses) Table 4.15 IP address setting range Class High-order bits of IP address...
  • Page 92 C CONTROLLER SETTING UTILITY • To enable the settings The entered IP address takes effect when the C Controller module is powered off and then on or is reset. When the IP address is changed, set the connection target with the new IP address in Connection setting.
  • Page 93 C CONTROLLER SETTING UTILITY (b) Clock tab Clock data of the C Controller can be set in this tab. Figure 4.20 Clock tab Table 4.18 Description of the Clock tab Clock IP address MD function Option Reference Item Description page Set the clock of the C Controller module and displays it.
  • Page 94 C CONTROLLER SETTING UTILITY (c) MD function tab The timeout value used in the MELSEC data link function can be set in this tab. For the Q06CCPU-V-B, this setting is not available. Figure 4.21 MD function tab Table 4.19 Description of the MD function tab MD function IP address Clock...
  • Page 95 C CONTROLLER SETTING UTILITY (d) Option tab The priority of processing for communications with the C Controller module can be set in this tab. Figure 4.22 Option tab Table 4.20 Description of the Option tab Option IP address Clock MD function Reference Item Description...
  • Page 96: System Settings Tab

    C CONTROLLER SETTING UTILITY System Settings Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Parameters (system settings) of the C Controller module and system-related parameters can be set in this tab. (1) Precautions for the System settings tab (a) Multiple CPU system configuration Set the multiple CPU parameters on the CPU No. 1.
  • Page 97 Set this for communication with peripheral devices through Ethernet. This setting is not available for the following: Built-in Ethernet port open settings •Q12DCCPU-V whose serial No. (first five digits) is "12041" or earlier •Q06CCPU-V(-B) Set whether to enable connection with a peripheral such as GX Developer.
  • Page 98 Set whether to register the event history data. This setting is not available for the following: Event history registration settings •Q12DCCPU-V whose serial No. (first five digits) is "12041" or earlier •Q06CCPU-V(-B) Set whether to register System (Info.) events to the event history or not.
  • Page 99 C CONTROLLER SETTING UTILITY (3) Intelligent function module interrupt event settings screen Interrupt event data of an intelligent function module can be set on this screen. The interrupt event is an event for interrupt notification that occurs in response to an interrupt from an intelligent function module.
  • Page 100 C CONTROLLER SETTING UTILITY (a) List for No. and factors of interrupt event Table 4.23 List for Event No. and factor of event Interrupt event No. Interrupt factor 1st point 2nd point 3rd point 4th point 5th point 6th point 7th point 8th point Interrupt by interrupt module...
  • Page 101: Device Settings Tab

    For the device function, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation). The devices set on this screen cannot be used for the following C Controller module. • Q12DCCPU-V whose serial No. (first five digits) is "12041" or earlier (1) Device settings tab Figure 4.25 Device settings tab Table 4.24 Description of the Device settings tab...
  • Page 102 C CONTROLLER SETTING UTILITY Remark Special relays (SM) and special registers (SD) can be used regardless of the above setting. - 36 4.8 Device Settings Tab...
  • Page 103: I/o Assignment Settings Tab

    C CONTROLLER SETTING UTILITY I/O Assignment Settings Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Parameters (I/O assignment) of the C Controller module can be set in this tab. Assign I/O to slots and set parameters related to the base units where modules are installed.
  • Page 104 C CONTROLLER SETTING UTILITY Table 4.25 Description of the I/O assignment settings tab (continued) I/O assignment settings Device settings Multiple CPU settings Communication diagnostics Reference Item Description page I/O assignment Select the type of the mounted module. In a multiple CPU system, no error will be displayed when "CPU (Empty)" is set to Type the position where the C Controller module does not support.
  • Page 105 C CONTROLLER SETTING UTILITY (3) Switch settings for I/O and intelligent function module screen Switch settings for I/O and intelligent function module can be set on this screen. For the switch settings, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
  • Page 106 C CONTROLLER SETTING UTILITY (4) Intelligent function module detailed settings screen Detailed settings for I/O modules and intelligent function modules can be set on this screen. For setting items on this screen, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
  • Page 107: Multiple Cpu Settings Tab

    C CONTROLLER SETTING UTILITY 4.10 Multiple CPU Settings Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Parameters of the C Controller module (multiple CPU setting) for configuring a multiple CPU system can be set in this tab. Set parameters regarding the multiple CPU system.
  • Page 108 C CONTROLLER SETTING UTILITY Table 4.28 Description of the Multiple CPU settings tab (continued) Multiple CPU settings Device settings I/O assignment settings Communication diagnostics Reference Item Description page Set the operation mode for a CPU stop error on each programmable controller CPU.
  • Page 109 C CONTROLLER SETTING UTILITY Table 4.28 Description of the Multiple CPU settings tab (continued) Multiple CPU settings Device settings I/O assignment settings Communication diagnostics Reference Item Description page Communication area setting (refresh Set the auto refresh area within CPU modules setting) Select any of registered refresh setting.
  • Page 110 C CONTROLLER SETTING UTILITY (3) Auto refresh settings screen Points of the Multiple CPU high speed transmission area to which each CPU module performs auto refresh can be set on this screen. Figure 4.32 Auto refresh settings screen Table 4.29 Description of the Auto refresh settings screen Item Description Select the CPU module to be configured.
  • Page 111: Communication Diagnostics Tab

    C CONTROLLER SETTING UTILITY 4.11 Communication Diagnostics Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Whether access from the C Controller module in a multiple CPU system to another CPU is available or not can be checked in this tab. (1) Precautions for the Communication diagnostics tab...
  • Page 112: System Menu

    C CONTROLLER SETTING UTILITY 4.12 System Menu Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) System menu System menu in C Controller setting utility can be accessed either in the following three way. • Right-click on the title bar. • Click the ( ) icon on the title bar.
  • Page 113 C CONTROLLER SETTING UTILITY (2) Version information screen Version information of C Controller setting utility can be checked on this screen. Figure 4.35 Version information screen (Example: Version 3.03D) Table 4.32 Description of the version information screen Reference Item Description page Software package SW3PVC-CCPU-E...
  • Page 114: 4.13 Reading Initial Setting File And Importing Multiple Cpu Parameters

    C CONTROLLER SETTING UTILITY 4.13 Reading Initial Setting File and Importing Multiple CPU Parameters Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Displaying the screen Display the Open project screen in either of the following ways. Load initial setting file • Click the button in the System settings tab.
  • Page 115 GX Configurator-TI GX Configurator-FL GX Configurator-PT GX Configurator-AS •For the Q12DCCPU-V To write parameters to a positioning module, connect a development environment (personal computer) and the C Controller module with a USB, and use GX Configurator-QP Version 2.30G or later.
  • Page 116: Precautions

    C CONTROLLER SETTING UTILITY 4.14 Precautions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Simultaneous use of utility Up to eight C Controller setting utilities can be simultaneously activated. (2) Written parameters Parameters written to the C Controller module take effect when the C Controller module is powered off and then on or is reset.
  • Page 117: Chapter 5 Cc-link Utility

    CC-LINK UTILITY CHAPTER 5 CC-LINK UTILITY CC-Link Utility Function List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Table 5.1 CC-Link utility function list Availability Reference Name Description Q12DCCPU Q06CCPU Q06CCPU page -V-B Specifies a C Controller module to which parameters are set Specify CPU type Page 3-4 or to be monitored.
  • Page 118: Module Information Tab

    CC-LINK UTILITY Module Information Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The Module information tab displays information of the CC-Link module (own station) controlled by the connected C Controller module. (1) Precautions for the Module information tab (a) When a utility communication error has occurred...
  • Page 119 CC-LINK UTILITY Table 5.2 Description of Module information tab (continued) Module information Other station monitoring Online operation Parameter settings Target settings Test Item Description Slot n Displays the station No., Station type, and Operation mode. (Display example: "0: Master station (Ver.2 mode)", "1: Local station") Sta.
  • Page 120 CC-LINK UTILITY (c) Error status The following indicates details of the Error status. Table 5.5 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. Timeout error Timeout error was detected.
  • Page 121 CC-LINK UTILITY (a) Mode switch status The following indicates details of the Mode switch states. Table 5.7 Details of Mode switch states Transmission Display Mode speed 0: 156kbps (Online) 156Kbps 1: 625kbps (Online) 625Kbps 2: 2.5Mbps (Online) 2.5Mbps Online 3: 5Mbps (Online) 5Mbps 4: 10Mbps (Online) 10Mbps...
  • Page 122: Other Station Monitoring Tab

    CC-LINK UTILITY Other Station Monitoring Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This tab displays the line states of other stations (CC-Link network stations). (1) Precautions for the Other station monitoring tab (a) Monitoring status Monitoring is stopped while CC-Link utility is being started.
  • Page 123 CC-LINK UTILITY Table 5.8 Description of the Other station monitoring tab (continued) Other station monitoring Module information Online operation Parameter settings Target settings Test Item Description Target module Sta. No. Displays the station No. Reserved station information Displays the reserved station. Error invalid station information Displays the error invalid station.
  • Page 124 CC-LINK UTILITY (3) View all stations screen The following indicates communication states of other stations. Figure 5.6 View all stations screen Table 5.10 Description of View all stations screen Item Description Communication status of each station is coded in color as follows. White: Normal communication Red: Error station Green: Error invalid station...
  • Page 125: Online Operation Tab

    When writing parameters from each of the utilities to the following C Controller module, write them to the same drive. • Q12DCCPU-V whose serial No. (first five digits) is "12042" or later If the parameters are written to different drives, those of the drive, which include C Controller setting parameters, will take effect.
  • Page 126 CC-LINK UTILITY Table 5.11 Description of Online operation tab (continued) Online operation Module information Other station monitoring Parameter settings Target settings Test Item Description Writes the CC-Link parameter to the C Controller module. The written parameters take effect when the C Controller module is powered off and then on or is Write parameters reset.
  • Page 127: Parameter Settings Tab

    CC-LINK UTILITY Parameter Settings Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Set the CC-Link module parameter in the Parameter settings tab. (1) Parameter settings tab Figure 5.8 Parameter settings tab Table 5.12 Description of Parameter settings tab Parameter settings Other station monitoring Online operation...
  • Page 128 CC-LINK UTILITY Table 5.12 Description of Parameter settings tab (continued) Parameter settings Other station monitoring Online operation Module information Target settings Test Item Description Operation settings Set the operation mode of the CC-Link module. Select a type of the CC-Link module. Type (Default: "Master station") Select a mode of the CC-Link module.
  • Page 129 CC-LINK UTILITY Table 5.12 Description of Parameter settings tab (continued) Parameter settings Other station monitoring Online operation Module information Target settings Test Item Description Station information settings Set the CC-Link module as a reserved or invalid station. Reserve/invalid station select (Default: "No setting") This setting is available when any of the following is set in "Type".
  • Page 130 CC-LINK UTILITY (2) Other settings screen Figure 5.9 Other settings screen Table 5.13 Description of Other settings screen Item Description Set the number of retries in the case of a communication error (transient transmission error occurrence) Retry count (Default: 3, Setting range: 1 to 7) Set the number of modules that can be automatically reconnected in one link scan.
  • Page 131: Target Settings Tab

    CC-LINK UTILITY Target Settings Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B A logical station No. is set from the Target settings tab. The logical station No. is used, when a target station is a multiple CPU system, to access a programmable controller CPU other than the control CPU of the target station.
  • Page 132 CC-LINK UTILITY Table 5.14 Description of Target settings tab (continued) Target settings Parameter settings Other station monitoring Online operation Module information Test Item Description Displays the logical No. set to the module selected in "Target module", corresponding station No., Target list and target CPU in a list.
  • Page 133 CC-LINK UTILITY (4) Access that does not require a logical station No. setting In the following access, use the station No. of a CC-Link module on other station. The logical station No. setting is not required. Control CPU of other station Other station CC-Link module CC-Link module C Controller...
  • Page 134: Test Tab

    CC-LINK UTILITY Test Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B A network test and line test for the mounted CC-Link module can be executed from this tab. (1) Precautions for the Test tab (a) Connection status for testing The network and line test can be executed while the CC-Link module is online.
  • Page 135 CC-LINK UTILITY Table 5.15 Description of the Test tab (continued) Test Module information Other station monitoring Online operation Parameter settings Target settings Item Description Target module Displays a station No., type of the station, and operation mode. For details of the operation mode, refer to the following. Own station information Page 5-3, Section 5.2 (2) (a) Select the test to conduct.
  • Page 136 CC-LINK UTILITY (b) Network test The network test can be conducted only when the data link status of the CC-Link module is "In data link" or "Perform auto-return". ( Page 5-2, Section 5.2) 1) Setting Select whether to start or stop a data link and then click the button to start the test.
  • Page 137: System Menu

    CC-LINK UTILITY System Menu Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) System menu System menu in CC-Link utility can be accessed either in the following three way for operation. • Right-click on the title bar. • Click the ( ) icon on the title bar.
  • Page 138 CC-LINK UTILITY (2) Version information screen Version information of CC-Link utility can be checked on this screen. Figure 5.20 Version information screen (Example: Version 3.01B) Table 5.17 Description of Version information screen Item Description Software package SW3PVC-CCPU-E Displays the version of SW3PVC-CCPU. CC-Link utility Displays the update date of CC-Link utility.
  • Page 139: Precautions

    CC-LINK UTILITY Precautions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Parameter details For details of respective parameters, refer to CC-Link System Master/Local Module User's Manual. (2) Simultaneous use of utilities Up to eight CC-Link setting utilities can be used simultaneously. (3) Written parameters Parameters written to the C Controller module take effect when the C Controller is powered off and then on or is reset.
  • Page 140: Chapter 6 Melsecnet/h Utility

    MELSECNET/H UTILITY CHAPTER 6 MELSECNET/H UTILITY MELSECNET/H Utility Function List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Table 6.1 MELSECNET/H Utility function list Availability Reference Item Description Q12DCCPU Q06CCPU Q06CCPU page -V-B Specifies a C Controller module to which parameters are set Specify CPU type Page 3-4 or to be monitored.
  • Page 141: Module Information Tab

    MELSECNET/H UTILITY Module Information Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The Module information tab displays information of the MELSECNET/H module (host station) controlled by the connected C Controller module. (1) Precautions for the Module information tab (a) When a utility communication error has occurred...
  • Page 142 MELSECNET/H UTILITY Table 6.2 Description of the Module information tab (continued) Module information Error history monitoring Other station monitoring Corresponding Corresponding Item Description Link device refresh time Displays current total link device refresh time. Current "-" appears when Link device refresh cycle ( Page 6-27, Section 6.6) is 0ms.
  • Page 143 MELSECNET/H UTILITY (3) Detailed module information screen. Detailed information of the MELSECNET/H module are displayed on this screen. Figure 6.2 Detailed module information screen Table 6.4 Description of the Detailed module information screen Corresponding Corresponding Item Description Model name Displays the model name of the MELSECNET/H module. Displays the product information (serial No.
  • Page 144 MELSECNET/H UTILITY Table 6.4 Description of the Detailed module information screen (continued) Corresponding Corresponding Item Description Own station information Displays operation setting status of the own station. Displays the parameter setting status of the host station with any of the following.
  • Page 145 MELSECNET/H UTILITY Table 6.4 Description of the Detailed module information screen (continued) Corresponding Corresponding Item Description Link information Displays the network status Displays the operation mode of the own station. Mode SW0043 (Display: "Online", "Offline", "Loop test") Displays the forward loop status. SB0091, F loop status "-"...
  • Page 146 MELSECNET/H UTILITY (a) Reason for transmission interruption The following lists the display in Reason for transmission interruption. Table 6.5 Details of Reason for transmission interruption Display Description/Action Normal Communicating normally Offline Offline Offline test Offline test being conducted. Initial status Error occurred.
  • Page 147 MELSECNET/H UTILITY (4) Specifications of the SB/SW save file A file format can be selected in "Save as" on the following screen. Figure 6.3 Save As screen To use the text data of the SB/SW save file in a user program, select "SBSWSave File(*.csv)"...
  • Page 148: Error History Monitoring Tab

    MELSECNET/H UTILITY Error History Monitoring Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The Error history monitoring tab displays the historical data of loop errors, communication errors, and transient transmission errors. (1) Precautions for the Error history monitoring tab (a) Number of historical data Up to 16 loop switching or transient transmission errors are stored.
  • Page 149 MELSECNET/H UTILITY Table 6.7 Description of the Error history monitoring tab (continued) Error history monitoring Module information Other station monitoring Corresponding Corresponding Item Description Displays the own station information of the MELSECNET/H Own station information module. Start I/O No. Displays the start I/O No. of the own station. Network No.
  • Page 150 MELSECNET/H UTILITY Table 6.7 Description of the Error history monitoring tab Error history monitoring Module information Other station monitoring Corresponding Corresponding Item Description Displays the number of error occurrences. For details of factors and corrective actions, refer to the Number of error occurrences following.
  • Page 151 MELSECNET/H UTILITY (3) Clear error history screen Clear the number of errors to 0. Figure 6.6 Clear error history screen Table 6.8 Description of the Clear error history screen Corresponding Corresponding Item Description Clear type Select the item(s) for clearing the number of error occurrences. Select to clear the number of retries (link special register Clear retry counter SW00C8, SE00C9) to 0.
  • Page 152 MELSECNET/H UTILITY (4) Factors and actions The following table shows factors and corrective actions for each error. The information can also be checked from the following link special registers (SW) as well as on the Error history monitoring tab. For details of special registers (SW), refer to the Q Corresponding MELSECNET/H Network System Reference Manual (PLC to PLC network).
  • Page 153: Other Station Monitoring Tab

    MELSECNET/H UTILITY Other Station Monitoring Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The Other station monitoring tab displays the status of the other stations (MELSECNET/H network stations). (1) Precautions for the Other station monitoring tab (a) Monitoring status When MELSECNET/H utility is started, monitoring is in stop status.
  • Page 154 MELSECNET/H UTILITY Table 6.10 Description of the Other station monitoring tab (continued) Other station monitoring Module information Error history monitoring Corresponding Corresponding Item Description Own station information Displays the own station information of the MELSECNET/H module. Start I/O No. Displays the start I/O No. of the own station. Network No.
  • Page 155 MELSECNET/H UTILITY (a) Communication status of each status screen Displays the baton pass status. (Availability of transient transmission) Displayed number of the stations is based on the "Total stations" set on the Parameter settings tab. Figure 6.8 Communication status of each status screen Table 6.12 Description of the Communication status of each status screen Corresponding Corresponding...
  • Page 156 MELSECNET/H UTILITY (b) Data link status of each station screen Displays the cyclic transmission status. The number of displayed stations is based on the "Total stations" set in the Parameter settings tab. Figure 6.9 Data link status of each station screen Table 6.13 Description of the Data link status of each station screen Corresponding Corresponding...
  • Page 157 MELSECNET/H UTILITY (c) Parameter status of each station screen Displays the parameter communication status and parameter error status of each station. The number of displayed stations is based on the "Total stations" set in the Parameter settings tab. Figure 6.10 Communication status of each station screen Table 6.14 Description of the Communication status of each station screen Corresponding Corresponding...
  • Page 158 MELSECNET/H UTILITY (d) CPU operation status of each station screen Displays the CPU operation status. The number of displayed stations is based on the "Total stations" set in the Parameter settings tab. Figure 6.11 CPU operation status of each station screen Table 6.15 Description of the CPU operation status of each station screen Corresponding Corresponding...
  • Page 159 MELSECNET/H UTILITY (e) CPU RUN status of each station screen Displays the RUN/STOP states of the CPUs. The number of displayed stations is based on the "Total stations" set in the Parameter settings tab. Figure 6.12 CPU RUN status of each station screen Table 6.16 CPU RUN status of each station screen Corresponding Corresponding...
  • Page 160 MELSECNET/H UTILITY (f) Loop status of each station screen In the case of the optical loop system, this screen displays the forward and reverse loop states. The number of displayed stations is based on the "Total stations" set in the Parameter settings tab.
  • Page 161 MELSECNET/H UTILITY (g) Reserved station designation of each station screen Displays the setting status of the reserved status. The number of displayed stations is based on the "Total stations" set in the Parameter settings tab. Figure 6.14 Reserved station designation of each station screen Table 6.18 Description of the Reserved station designation of each station screen Corresponding Corresponding...
  • Page 162 MELSECNET/H UTILITY (h) PSU operation status of each station extension screen Displays the status of 24VDC external power supply for MELSECNET/H module. The number of displayed stations is based on the "Total stations" set in the Parameter settings tab. Figure 6.15 PSU operation status of each station extension Table 6.19 Description of the PSU operation status of each station extension Corresponding Corresponding...
  • Page 163 MELSECNET/H UTILITY (i) Each station network type status screen Displays consistency of the network types that are set in the control station and in the normal station. The number of displayed stations is based on the "Total stations" set in the Parameter settings tab.
  • Page 164: Online Operation Tab

    When writing parameters from each of the utilities to the following C Controller module, write them to the same drive. • Q12DCCPU-V whose serial No. (first five digits) is "12042" or later If the parameters are written to different drives, those of the drive, which include C Controller setting parameters, will take effect.
  • Page 165 MELSECNET/H UTILITY Table 6.21 Description of the Online operation tab (continued) Online operation Parameter settings Target settings Item Description Writes MELSECNET/H parameters to the C Controller module. The written parameters take effect when the C Controller module is powered off and then on or is reset. Write parameters Parameters can be written only when "Write authority"...
  • Page 166: Parameter Settings Tab

    MELSECNET/H UTILITY Parameter Settings Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Parameters of the MELSECNET/H module can be set in this tab. (1) Precautions for the Parameter settings tab (a) Link device refresh cycle and Routing parameter "Link device refresh cycle" and "Routing parameter" are parameters common to CC-Link IE Controller Networks.
  • Page 167 MELSECNET/H UTILITY Table 6.22 Description of the Parameter setting tab (continued) Parameter settings Online operation Target settings Item Description Set the refresh cycle of the link device. (In increments of ms) When using both the CC-Link IE Controller Network and MELSECNET/H, set the same value as the value set in CC IE Control utility.
  • Page 168 MELSECNET/H UTILITY Table 6.22 Description of the Parameter setting tab (continued) Parameter settings Online operation Target settings Item Description Assign network ranges. •MNET/H mode (Control station) Network range assignment •MNET/10 mode (Control station) •MNET/H Ext. mode (Control station) Set a total number of stations (including the control station) to the target network. Total stations (Default: 2) Switches the device range input method between Points/Start and Start/End.
  • Page 169 MELSECNET/H UTILITY (a) Network range assignment The following table indicates the setting ranges of network assignment. Table 6.23 Setting ranges of network range assignment Device Points/Start/End Setting range Points 16 to 8192 Start 0000 to 1FF0 000F to 1FFF Points 16 to 8192 Start 0000 to 1FF0...
  • Page 170 MELSECNET/H UTILITY (3) Routing parameter settings screen Transfer destination, relay network No., and relay station No. are set on this screen. POINT 1. The MELSECNET/H module controlled by the C Controller module cannot be used a relay station which operates as a bridge. For a relay station, use the MELSECNET/H module that is controlled by a programmable controller CPU which is capable of configuring multiple network systems.
  • Page 171 MELSECNET/H UTILITY Table 6.24 Description of the Routing parameter settings screen (continued) Item Description Max. size of transient transmission via For each channel No., set the maximum transmission size of data sent by transient transmission other network No. from a user program via another network (No.). For each channel No., set the maximum transmission size for the case where data are sent by transient transmission to another network (No.) via a MELSECNET/H module.
  • Page 172 MELSECNET/H UTILITY (4) Refresh parameter settings screen Set refresh parameters. Figure 6.21 Refresh parameter settings screen Table 6.25 Description of the Refresh parameter settings screen Item Description The device range input method can be switched between Points/Start and Start/End. Assignment method (Default: "Start/End") Set the refresh parameters of the target module selected on the Parameter settings tab.
  • Page 173 MELSECNET/H UTILITY (a) Default The following indicates the default for "Device name", "Points", "Start", and "End". Table 6.26 Default for "Device name", "Points", "Start", and "End" Setting item Device name Points Start Trans.1 8192 0000 1FFF Trans.2 8192 0000 1FFF Trans.3 to "(Blank)"...
  • Page 174 MELSECNET/H UTILITY (5) Equal assignment screen The link device points of all stations can be equally assigned on this screen. For the start and end stations, set values within the number of the stations for equal assignment target, which can be calculated in the following expression: (Total link stations (Start station No.
  • Page 175 MELSECNET/H UTILITY (b) When "LX/LY settings (1)" or "LX/LY settings (2)" is set for "Switch screens" in the Parameter settings tab. Figure 6.23 Equal assignment screen (for LX/LY settings (1)) Table 6.30 Description of the Equal assignment screen (for LX/LY settings (1) and (2)) Item Description Equally assigns entered points to the link devices of each station.
  • Page 176 MELSECNET/H UTILITY (6) Supplementary settings screen The supplementary settings is used for advanced settings. Default values can be applied for normal usage. Figure 6.24 Supplementary settings screen Table 6.31 Description of the Supplementary settings screen Item Description Constant scan is used to maintain the link scan time at a constant time. Constant scan Set a value to prevent fluctuation of the link scan time.
  • Page 177 MELSECNET/H UTILITY Table 6.31 Description of the Supplementary settings screen (continued) Item Description Transient settings Determine the conditions for transient transmission. Enter the number of transient transmissions (total of entire network) that can be performed by one Max. number of transients per network during one scan.
  • Page 178: Target Settings Tab

    MELSECNET/H UTILITY Target Settings Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Logical station numbers are set on this tab. Logical station numbers are used when the target station is a multiple CPU system to access the programmable controller other than control CPU in the target station.
  • Page 179 MELSECNET/H UTILITY Table 6.33 Description of the Target settings tab (continued) Target settings Online operation Parameter settings Item Description Displays a list of the Logical Sta. No. set to the module selected in "Target module" and the Target list corresponding network No., station No., and target CPUs Displays the data of the selected row (Logical sta.
  • Page 180 MELSECNET/H UTILITY (4) Access that does not require a logical station No. setting In the following access, use the station No. of a MELSECNET/H module on other station. The logical station number setting is not required. Control CPU of other station Other station MELSECNET/H module MELSECNET/H module C Controller...
  • Page 181: System Menu

    MELSECNET/H UTILITY System menu Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) System menu Open the system menu of MELSECNET/H utility in any of the following three methods. • Right-click on the title bar. • Click the ( ) icon on the title bar.
  • Page 182 MELSECNET/H UTILITY (2) Version information screen Displays the version information of MELSECNET/H utility. Figure 6.30 Version information screen (Example: Version 3.01B) Table 6.35 Description of the Version information screen Item Description Software package SW3PVC-CCPU-E Displays the version of SW3PVC-CCPU. MELSECNET/H utility Displays the update date of MELSECNET/H utility.
  • Page 183: Precautions

    MELSECNET/H UTILITY Precautions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Parameter details For details of each parameter, refer to Q Corresponding MELSECNET/H Network System Reference Manual (PLC to PLC network). (2) Simultaneous use of utility Up to eight MELSECNET/H utilities can be simultaneously activated.
  • Page 184: Chapter 7 Cc Ie Control Utility

    CC IE CONTROL UTILITY CHAPTER 7 CC IE CONTROL UTILITY CC IE Control Utility Function List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Table 7.1 CC IE Control utility function list Applicability Reference Name Description Q12DCCPU Q06CCPU page Specify CPU type Specifies a C Controller module for parameter setting and monitoring.
  • Page 185: Module Information Tab

    CC IE CONTROL UTILITY Module Information Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The Module information tab displays information of the CC-Link IE Controller Network module (own station) that is controlled by the connected C Controller module. (1) Precautions for the Module information tab...
  • Page 186 CC IE CONTROL UTILITY Table 7.2 Description of Module information tab (continued) Module information Target settings Online operation Parameter settings Corresponding Corresponding Item Description Link device refresh time Displays the current total link device refresh time. Current When Link device refresh cycle ( Page 7-23, Section 7.5) is 0ms, "-"...
  • Page 187 CC IE CONTROL UTILITY (3) Specifications of the SB/SW save file A file format can be selected in "Save as type" on the following screen. Figure 7.2 SaveAs screen To use the text data of the SB/SW save file in a user program etc, select "SBSWSave File(*.csv)"...
  • Page 188: Diagnostics Result Screen

    CC IE CONTROL UTILITY Diagnostics Result Screen Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Diagnostics Clicking the button in the <<Module information>> tab displays this screen. Figure 7.4 CC IE Control Network diagnostics result screen POINT When there are two or more CC-Link IE Controller Network modules that are controlled by the C Controller module, the following "Select diagnostics...
  • Page 189 CC IE CONTROL UTILITY Table 7.3 Description of Select diagnostics destination Item Description Displays the Select diagnostics destination" screen when there are two or more CC-Link IE Controller Change module Network modules that are controlled by the C Controller module. button Change the network to one that is to be diagnosed.
  • Page 190 CC IE CONTROL UTILITY (1) Network information The link status and station status of the network are displayed. Figure 7.6 Network information display Table 7.4 Description of Network information display Item Description Displays the module on the network, which is being diagnosed. Module The number corresponds to one of Slots 1 to 4 on the "Module information"...
  • Page 191 CC IE CONTROL UTILITY (a) Icons Each icon represents its station status or inter-station status. Figure 7.7 Displaying each station status and inter-station status 1) Station No. Station No. of each CC-Link IE Controller Network module is displayed. 2) Connected This word is shown for the station connected to the CC IE Control utility (own station).
  • Page 192 CC IE CONTROL UTILITY (b) Position of a disconnected station 1) If the station has obtained normal connection information The disconnected station is displayed in the position where it was connected when it was normal. Figure 7.8 When the disconnected station has obtained normal connection information Conditions and timing for normal connection information acquisition When all of the following conditions are met, normal connection information is stored in a CC-Link IE Controller Network module.
  • Page 193 CC IE CONTROL UTILITY (2) Network device status of selected station The detailed information of a selected station is displayed. Figure 7.10 Network device status of selected station Table 7.6 Description of Network device status of selected station Item Display Description Displays the group No.
  • Page 194 CC IE CONTROL UTILITY (a) LEDs of the selected station network device The operating status of the selected station is displayed. Figure 7.11 LEDs of the selected station network device Table 7.7 Description of LEDs of the selected station network device LED status Description On, green...
  • Page 195 CC IE CONTROL UTILITY (b) Error details button Clicking the button displays the "Error details" screen. The detailed information, error factor, and troubleshooting tips are displayed. Figure 7.12 Error details screen 7.3 Diagnostics Result Screen - 12...
  • Page 196 CC IE CONTROL UTILITY (3) Communication Test screen The route from the own station to the specified destination is displayed on this screen, and whether transient transmissions can be performed correctly or not is checked. Upon completion of the communication test, the test result is displayed. If an error occurs, take actions according to the error message.
  • Page 197 CC IE CONTROL UTILITY Table 7.8 Description of Communication Test screen (continued) Item Description Own station Displays the information on the own (connected) station. Network No. Displays the network No. of the own (connected) station. Station No. Displays the station No. of the own (connected9 station. Communication information Displays the communication information.
  • Page 198 CC IE CONTROL UTILITY (4) Link start/stop screen From this screen, data link of the specified station can be started or stopped. Figure 7.15 Link start/stop screen Table 7.9 Description of Link start/stop screen Item Description Network information Displays the information on the selected network (own station). Displays the name of the selected network (own station).
  • Page 199 CC IE CONTROL UTILITY (5) Logging screen Transmission pass switching and transient transmission error logs can be monitored, and error information can be cleared. <<Monitoring details>> tab <<Clear error>> tab Figure 7.16 Logging screen Table 7.10 Description of Logging screen Item Description Connected station...
  • Page 200 CC IE CONTROL UTILITY Table 7.10 Description of Logging screen (continued) Item Description <<Monitoring details>> tab Displays logs in the Transmission path switch and Transient transmission error areas. Up to 100 transmission path switch logs can be displayed. Transmission path switch If more than 100 logs have occurred, the oldest log will be deleted to record the latest log.
  • Page 201 CC IE CONTROL UTILITY Table 7.10 Description of Logging screen (continued) Item Description <<Clear error>> tab Clears the errors. The communication error counter can be cleared to zeros. Clear communication error counter (Default: Checked (Clears to 0)) The areas for detected IN-side line errors (SW0068, SW0069, SB006E, SB0140, SW0074, and Clear IN side transmission error SW0140 to SW0147) can be cleared to zeros.
  • Page 202 CC IE CONTROL UTILITY (6) Specifications of the error log file A file format can be selected in "Files of type" on the following screen. Open To save the file, go back to the error log save screen by clicking the button after selecting the format.
  • Page 203: Online Operation Tab

    When writing parameters from each of the utilities to the following C Controller module, write them to the same drive. • Q12DCCPU-V whose serial No. (first five digits) is "12042" or later If the parameters are written to different drives, those of the drive, which include C Controller setting parameters, will take effect.
  • Page 204 CC IE CONTROL UTILITY Table 7.11 Description of Online operation tab (continued) Online operation Parameter settings Target settings Module information Item Description Read parameters Reads CC-Link IE Controller Network parameters from the C Controller module. Read button Writes CC-Link IE Controller Network parameters to the C Controller module. The written parameters take effect when the C Controller module is powered off and then on or is Write parameters reset.
  • Page 205 CC IE CONTROL UTILITY (3) Verification results file If a mismatch is found, a message appears and prompts the user to save the results to a file. To save a verification results file, click the button and enter appropriate data on the following screen.
  • Page 206: Parameter Settings Tab

    CC IE CONTROL UTILITY Parameter Settings Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Parameters of the CC-Link IE Controller Network module can be set in this tab. (1) Precautions for the Parameter settings tab (a) Link device refresh cycle and Routing parameter "Link device refresh cycle" and "Routing parameter" are parameters common to MELSECNET/H.
  • Page 207 CC IE CONTROL UTILITY Table 7.12 Description of Parameter settings tab (continued) Parameter settings Module information Online operation Target settings Item Description Set a refresh cycle for link devices. (In increments of ms) When using both the CC-Link IE Controller Network and MELSECNET/H network, set the same value as the value set in MELSECNET/H utility.
  • Page 208 CC IE CONTROL UTILITY (3) Routing parameter settings screen The transfer target network, relay network, and relay station can be specified on this screen. POINT 1. The CC-Link IE Controller Network module controlled by a C Controller module cannot be a relay station that is supposed to act as a bridge. As a relay station, use a CC-Link IE Controller Network module controlled by a programmable controller CPU with which multiple network systems can be constructed.
  • Page 209 CC IE CONTROL UTILITY Table 7.13 Description of Routing parameter settings screen (continued) Item Description Max. size of transient transmission via For each channel No, set the maximum size of transient transmission data sent from a user other network No. program via another network (No.) For each channel, set the maximum size of transient transmission data sent to another network (No.) via a CC-Link IE Controller Network module.
  • Page 210 CC IE CONTROL UTILITY (4) Refresh parameter settings screen Refresh parameters are set on this screen. Figure 7.25 Refresh parameter settings screen Table 7.14 Description of Refresh parameter settings screen Item Description How to enter the device range data can be switched between Points/Start and Start/End styles. Assignment method (Default: "Start/End") Set refresh parameters of the module selected on the "Parameter settings"...
  • Page 211 CC IE CONTROL UTILITY (a) Default values for "Device name", "Points", "Start", and "End" The following table lists the default values for "Device name", "Points", "Start", and "End". Table 7.15 Default values for "Device name", "Points", "Start", and "End" Setting item Device name Points Start...
  • Page 212 CC IE CONTROL UTILITY (5) Network range assignment screen For each station, set cyclic transmission ranges of LB, LW, LX, and LY. Figure 7.26 Network range assignment screen Table 7.18 Description of Network range assignment screen Item Description Set the total number of stations (including control stations) on the network. Total stations (Default: 2) How to enter the device range data can be switched between Points/Start and Start/End styles.
  • Page 213 CC IE CONTROL UTILITY (a) Setting ranges for Network range assignment The following are the setting ranges for Network range assignment. Table 7.19 Setting ranges for 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...
  • Page 214 CC IE CONTROL UTILITY (6) Equal assignment screen The link device points of all stations can be equally assigned to each station. The Start and End stations for equal assignment can be set within (Total link stations - (Start station No. - 1)). (a) When "LB/LW settings (1)"...
  • Page 215 CC IE CONTROL UTILITY (b) When "LX/LY settings (1)" or "LX/LY settings (2)" is set for "Switch screens" in "Network range assignment" Figure 7.28 Equal assignment screen (for LX/LY settings (1)) Table 7.21 Description of Equal assignment screen (for LX/LY settings (1) or LX/LY settings (2)) Item Description Equally assigns the entered points to link devices of each station.
  • Page 216 CC IE CONTROL UTILITY (7) Supplementary settings screen The Supplementary settings screen is useful for advanced applications. Use the default settings normally. Figure 7.29 Supplementary settings screen Table 7.22 Description of Supplementary settings screen Item Description Constant scan is a feature provided for keeping a fixed link scan time. Constant scan Set a value if variation in link scan time undesirable.
  • Page 217: Target Settings Tab

    CC IE CONTROL UTILITY Target Settings Tab Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Logical station No. can be set on this tab. When the target station is on a multiple CPU system, a logical station No. is used for accessing a programmable controller CPU that is controlled by another CPU.
  • Page 218 CC IE CONTROL UTILITY Table 7.24 Description of Target settings tab (continued) Target settings Module information Online operation Parameter settings Item Description Displays the logical station No. set for the selected "Target module", the relevant network No. and Target list station No., and the target CPU in the list.
  • Page 219 CC IE CONTROL UTILITY (4) Access that does not require a logical station No. setting In the following cases, use the station No. of a CC-Link IE Controller Network module on other station. The logical station number setting is not required. Control CPU of other station Other station CC-Link IE Controller Network module CC-Link IE Controller Network module...
  • Page 220: System Menu

    CC IE CONTROL UTILITY System Menu Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) System menu To open the system menu of CC IE Control utility, use any of the following three methods: • Right-click on the title bar. • Click the ( ) icon on the title bar.
  • Page 221 CC IE CONTROL UTILITY (2) Version information screen Version information of the CC IE Control utility is displayed. Figure 7.35 Version information screen (Example: Version 3.02C) Table 7.26 Description of Version information screen Item Description Software package SW3PVC-CCPU-E Displays the version of SW3PVC-CCPU. CC IE Control utility Displays the update date of the CC IE Control utility.
  • Page 222: Precautions

    CC IE CONTROL UTILITY Precautions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Parameter details For details of respective parameters, refer to the CC-Link IE Controller Network Reference Manual. (2) Simultaneous use of utilities Up to eight CC IE Control utilities can be used simultaneously.
  • Page 223: Chapter 8 Device Monitoring Utility

    Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Table 8.1 Device monitoring utility function list Applicability Reference Name Description Q12DCCPU-V Q06CCPU-V page Connection setting Sets the connection target of Device monitoring utility. Page 3-5 Batch monitoring Monitors only one specified device. Page 8-2 16-point register Monitors up to five bit devices and one word device at the same time.
  • Page 224: Batch Monitoring

    DEVICE MONITORING UTILITY Batch Monitoring Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Only one specified device can be monitored. (1) Precautions for batch monitoring (a) When a utility communication error has occurred When a utility communication error has occurred during connection, set the connection target again in the Connection settings so that the communication can be restarted.
  • Page 225 DEVICE MONITORING UTILITY (2) Selected menu items From the menu bar, select [Menu] [Batch monitoring]. (The above procedure is available only when 16-point register monitoring is active. Batch monitoring is displayed immediately after start of Device monitoring utility.) Select [Setting] [Device settings] and set the device to be monitored. ( Page 8- 7, Section 8.5) (3) Display screen...
  • Page 226: 16-point Register Monitoring

    DEVICE MONITORING UTILITY 16-Point Register Monitoring Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Up to five bit devices and one word device can be monitored at the same time. (1) Precautions for 16-point register monitoring (a) When a utility communication error has occurred When a utility communication error has occurred during connection, set the connection target again in the Connection settings so that the communication can be restarted.
  • Page 227 DEVICE MONITORING UTILITY (2) Selected menu items From the menu bar, select [Menu] [16-point monitoring]. (The above procedure is available only when batch monitoring is active.) Select [Setting] [Device settings] and set the device to be monitored. ( Page 8- 7, Section 8.5) (3) Display screen Figure 8.2 16-point register monitoring...
  • Page 228: Setting Monitoring Target

    DEVICE MONITORING UTILITY Setting Monitoring Target Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Set a network for which Device monitoring utility is used. Set the network at startup of Device monitoring utility. (1) Precautions for network setting When the own station is selected in "Network settings", network No."0" and station No."255"...
  • Page 229: Setting Device To Be Monitored

    DEVICE MONITORING UTILITY Setting Device to Be Monitored Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Set the device to be monitored. (1) Precautions for device setting (a) Devices available for 16-point register monitoring Only the randomly accessible devices can be monitored by 16-point register monitoring.
  • Page 230: Changing Word Device Values

    DEVICE MONITORING UTILITY Changing Word Device Values Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Data of the specified word device can be changed. WARNING Configure safety circuits external to the C Controller module to ensure that the entire system operates safely even when a fault occurs in the external power supply or the C Controller module.
  • Page 231 DEVICE MONITORING UTILITY (2) Selected menu items From the menu bar, select [Write device] [Data change]. (3) Dialog box Figure 8.5 Data change dialog box Table 8.6 Description of Data change dialog box Item Description Set the type ( Page 10-12, Section 10.12), block No. and network No. of Device type the device of which data are changed.
  • Page 232: Continuously Changing Word Device Values

    DEVICE MONITORING UTILITY Continuously Changing Word Device Values Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The specified points of word device data can be changed to the specified data. WARNING Configure safety circuits external to the C Controller module to ensure that the entire system operates safely even when a fault occurs in the external power supply or the C Controller module.
  • Page 233 DEVICE MONITORING UTILITY (2) Selected menu items From the menu bar, select [Write device] [Continuous data change]. (3) Dialog box Figure 8.6 Continuous data change dialog box Table 8.7 Description of the Continuous data change dialog box Item Description Set the type, block No., and network No. of the device whose data are changed. Device type Page 10-12, Section 10.12) Set the start No.
  • Page 234: Tuning On And Off Bit Device

    DEVICE MONITORING UTILITY Tuning On and Off Bit Device Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The specified bit device can be turned on and off. WARNING Configure safety circuits external to the C Controller module to ensure that the entire system operates safely even when a fault occurs in the external power supply or the C Controller module.
  • Page 235 DEVICE MONITORING UTILITY (2) Selected menu From the menu bar, select [Write device] [Set (Reset) bit device]. (3) Dialog box Figure 8.7 Set bit device dialog box Table 8.8 Description of the Set (reset) bit device dialog box Item Description Set the type, block No., and network No.
  • Page 236: Changing The Display Format

    DEVICE MONITORING UTILITY Changing the Display Format Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The display format in device monitoring can be changed. Note that the menu options for Batch monitoring and 16-point register monitoring are different. (1) Selected menu After selecting the [display switch] on the menu bar, select the display format of Word device, Bit device, or SPG device (special direct buffer register and intelligent function module buffer memory).
  • Page 237: Start And Stop Monitoring

    DEVICE MONITORING UTILITY 8.10 Start and Stop Monitoring Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Start monitoring Stop monitoring buttons of Device monitoring utility are operated on this screen. Start monitoring Stop monitoring buttons become operable after completing the Device setting. (1) Operation Start monitoring...
  • Page 238: Numerical Pad

    DEVICE MONITORING UTILITY 8.11 Numerical Pad Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B From the menu bar, select [Option] [Numerical pad] so that device values can be entered using the Numerical pad. Click the "Device No." entry field. As the Numerical pad appears, enter a numerical value using buttons.
  • Page 239: Other Operations

    DEVICE MONITORING UTILITY 8.12 Other Operations Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Double-clicking the device No. on the screen during monitoring enables to change word device data and to turn on and off bit devices. WARNING Configure safety circuits external to the C Controller module to ensure that the entire system operates safely even when a fault occurs in the external power supply or the C Controller module.
  • Page 240 DEVICE MONITORING UTILITY (2) Changing a word device The following describes how to change a word device. Double-click the word device No. of which value is to be changed. As the dialog box shown on the left appears, enter any given values.
  • Page 241: Precautions

    DEVICE MONITORING UTILITY 8.13 Precautions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Connection during script file processing Connection from utility to a C Controller module may not be available during processing a script file (while the RUN LED is flashing). If the RUN LED remains flashing, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation) and troubleshoot the problem.
  • Page 242: Chapter 9 Programming Using Bus Interface Functions

    PROGRAMMING USING BUS INTERFACE FUNCTIONS CHAPTER 9 PROGRAMMING USING BUS INTERFACE FUNCTIONS Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B When applying program examples introduced in this chapter into actual systems, fully examine the applicability, and confirm that they will not cause system control problems.
  • Page 243 PROGRAMMING USING BUS INTERFACE FUNCTIONS The system illustration below represents a system image based on the features described on the previous page. Intelligent function module I/O module CC-Link IE Controller Network module or C Controller module MELSECNET/H module Programmable Programmable controller CPU controller CPU 6) to 12)
  • Page 244: Bus Interface Function List

    PROGRAMMING USING BUS INTERFACE FUNCTIONS Bus Interface Function List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Bus interface function list Table 9.2 Bus interface function list 1)Q12DCCPU-V 2)Q06CCPU-V 3)Q06CCPU-V-B Availability Category Function name Function QBF_Open Opens a bus. Open/close QBF_Close Closes a bus.
  • Page 245 PROGRAMMING USING BUS INTERFACE FUNCTIONS Table 9.2 Bus interface function list (continued) 1)Q12DCCPU-V 2)Q06CCPU-V 3)Q06CCPU-V-B Availability Category Function name Function QBF_EntryTimerEvent Registers timer events. Timer event control QBF_WaitTimerEvent Waits for an occurrence of a timer event. Acquisition of Reads the status information (LED, error, etc.) of C...
  • Page 246 C Controller module. Error clear QBF_ClearError Clears an error. : Available, : N/A * 2 Not available for the following C Controller module. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier 9.2 Bus Interface Function List...
  • Page 247 : Available, : N/A * 1 For the following C Controller module, intelligent function modules cannot be accessed (reading and writing). • Q12DCCPU-V with serial number (first five digits) "12041" or earlier. (To the next page) 9.2 Bus Interface Function List...
  • Page 248 : Available, : N/A * 2 Not available for the following C Controller module. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier POINT For details of the bus interface functions, refer to the Bus Interface Function HELP of SW3PVC-CCPU.
  • Page 249: Programming Procedure

    Create the script file "STARTUP.CMD", and write it into the standard RAM, standard ROM, or CompactFlash Page 9-51, Section 9.9 card. For the Q12DCCPU-V, back up the file in the standard Page 9-46, Section 9.8, RAM since the file may be cleared when the battery life has expired.
  • Page 250: Creating And Compiling A New Project Of User Program

    Select [File] [New] [VxWorks Downloadable Kernel Module Project] from the menu bar. Enter a project name in "Project name" and click the button. Next> (To the next page) 9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V...
  • Page 251 (No setting is necessary.) Next> Select "SH7750gnule" and click the button. Finish REFERENCE To set the release mode, deselect "Debug Mode". (To the next page) 9.4 Creating and Compiling a New Project of User Program - 10 9.4.1 For the Q12DCCPU-V...
  • Page 252 Add "-IC:/MELSEC/CCPU/DVx/Include" to the setting of the include file. (When SW3PVC-CCPU is installed to "C:\MELSEC") Select [File] [New] [File] from the menu bar. (To the next page) - 11 9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V...
  • Page 253 Finish Edit the source file and include the following include files. Bus interface function: "QbfFunc.h" MELSEC communication function: "Mdfunc.h" (Completed) 9.4 Creating and Compiling a New Project of User Program - 12 9.4.1 For the Q12DCCPU-V...
  • Page 254 Navigator" window and select [Refresh] from the menu. Right-click on the project to be compiled on the "Project Navigator" window and select [Rebuild Project] from the menu. (To the next page) - 13 9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V...
  • Page 255 Generate Includes Click the button. Click the button. (No setting is necessary.) Next> Click the button. (No setting is necessary.) Next> (To the next page) 9.4 Creating and Compiling a New Project of User Program - 14 9.4.1 For the Q12DCCPU-V...
  • Page 256 File name: <Project name>.out REFERENCE In the release mode, the user programs are saved in the folder where the project is saved. (Completed) - 15 9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V...
  • Page 257 (b) Checking result The checking result is indicated as below. Execution file name: file format elf32-shl elf32-shl : Little endian elf32-sh : Big endian 9.4 Creating and Compiling a New Project of User Program - 16 9.4.1 For the Q12DCCPU-V...
  • Page 258: For The Q06ccpu-v(-b)

    PROGRAMMING USING BUS INTERFACE FUNCTIONS 9.4.2 For the Q06CCPU-V(-B) The following information is provided in this section. • How to create a new project ( Page 9-17, Section 9.4.2 (1)) • How to compile ( Page 9-21, Section 9.4.2 (2)) •...
  • Page 259 PROGRAMMING USING BUS INTERFACE FUNCTIONS (From the previous page) Select "A toolchain" and select the setting corresponding to the modules below in the pull-down menu and click the Next> button. Q06CCPU-V: SH7750gnule (Little endian) Q06CCPU-V-B: SH7750gnu (Big endian) REFERENCE This setting defines the endian format. The program does not run if the setting with a different endian format is selected.
  • Page 260 PROGRAMMING USING BUS INTERFACE FUNCTIONS (From the previous page) Double-click the ( ) icon to display the lower item. Right-click "SH7750gnule" and select [Properties] from the menu. REFERENCE For the Q06CCPU-V-B, right-click "SH7750gnu" and select [Properties] from the menu bar. (To the next page) - 19 9.4 Creating and Compiling a New Project of User Program...
  • Page 261 PROGRAMMING USING BUS INTERFACE FUNCTIONS (From the previous page) Open the <<C/C++ compiler>> tab. In the center text area on the screen, add the folder settings where the include files of the bus interface functions and MELSEC data link functions are installed, and click the button.
  • Page 262 PROGRAMMING USING BUS INTERFACE FUNCTIONS (2) How to compile POINT The following operations are required for compiling. In the <<Files>> tab on the "Workspace" window, right-click on the source file name to be compiled, and select [Dependencies] from the menu. Check the source file name to be compiled, and click the button.
  • Page 263 PROGRAMMING USING BUS INTERFACE FUNCTIONS (From the previous page) Compiling process appears on the screen as shown on the left. When compiling is finished, user programs that can be executed in the C Controller module are generated. The user programs are not generated if an error occurred during compiling.
  • Page 264: Programming Flow For Bus Interface Functions

    PROGRAMMING USING BUS INTERFACE FUNCTIONS Programming Flow for Bus Interface Functions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Programming flow The following flowchart shows the procedure for programming using the bus interface functions. Task start Open the bus. (QBF_Open function) Register a routine to the user watchdog Set the watchdog timer for the user program timer error interrupt.
  • Page 265 PROGRAMMING USING BUS INTERFACE FUNCTIONS The following flowchart shows the outline in the case of a user watchdog timer error interrupt. Interrupt routine (interrupt program) start Specify "1" (ISR) for the argument of the Access the SRAM data. function, "sFlg" since starting from inerrupt (QBF_WriteSRAM/QBF_ReadSRAM function) routine (interrupt program).
  • Page 266 PROGRAMMING USING BUS INTERFACE FUNCTIONS (b) Precautions for own station device access via CC-Link module When accessing via a CC-Link module, create a user program that provides interlocks to enable write to/read from the own station device. Data become effective only when the following conditions are satisfied. •...
  • Page 267: Precautions For Functions

    PROGRAMMING USING BUS INTERFACE FUNCTIONS Precautions for Functions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section provides precautions for the bus interface function and MELSEC data link function. (1) Endian format (Memory layout) There are two types of models for the Q06CCPU-V(-B), which are in little endian format (memory layout) and in big endian format.
  • Page 268 [For the Q12DCCPU-V] Use the Telnet tool. [For the Q06CCPU-V(-B)] Execute from the Tornado Shell. Example) When using the Telnet tool on the Q12DCCPU-V Command execution Port numbers being used in a C Controller module. Figure 9.5 When using Telnet tool on the Q12DCCPU-V (6) When writing a file from the user program by the Q06CCPU-V(-B) Do not write a file to the standard ROM.
  • Page 269 PROGRAMMING USING BUS INTERFACE FUNCTIONS (8) When the operation status is changed from RUN to STOP/PAUSE When the operation status of the C Controller module is changed from RUN to STOP/ PAUSE, the user program task does not stop. Use the QBF_Read StatusEx function when splitting the user program processing according to the operation status of the C Controller module.
  • Page 270 PROGRAMMING USING BUS INTERFACE FUNCTIONS (12)Power off and reset during writing a user file Data corruption or file system error may occur if the C Controller system is powered of or is reset (including remote RESET) during writing data to the user file in the standard RAM, standard ROM, or CompactFlash card.
  • Page 271 PROGRAMMING USING BUS INTERFACE FUNCTIONS (15)Functions that can be used in the interrupt routine (interrupt program) of the Q12DCCPU-V The following functions can be used in the interrupt routine (interrupt program) of the Q12DCCPU-V. • Bus interface function for ISR •...
  • Page 272: Precautions For Program Debugging

    3) Right-click on the "Target Manager" window. Select [New] [Connection] to open the "New Connection" dialog box. 4) Select "Wind River VxWorks 6.x Target Server Connection" and click the button. Next> - 31 9.7 Precautions for Program Debugging 9.7.1 For Q12DCCPU-V...
  • Page 273 7) Select "*" in "Files of type" to select the VxWorks image file and click the Finish button. For the folder where the VxWorks image file is stored, refer to the following. Page 9-33, Section 9.7.1 (1) (b) 9.7 Precautions for Program Debugging - 32 9.7.1 For Q12DCCPU-V...
  • Page 274 C Controller module. In addition, debugging cannot be performed normally. Remark For other debugging methods, refer to the manual for Workbench. - 33 9.7 Precautions for Program Debugging 9.7.1 For Q12DCCPU-V...
  • Page 275 2) Write the above script file, "STARTUP.CMD" to a CompactFlash card, and insert it into the C Controller module. 3) Upon start of the C Controller module, the timeout time is set to the initial value. 9.7 Precautions for Program Debugging - 34 9.7.1 For Q12DCCPU-V...
  • Page 276 When exchanging the Telnet tool with another, first close the connection with the currently used Telnet tool, and then connect the line to the C Controller module from another Telnet tool. - 35 9.7 Precautions for Program Debugging 9.7.1 For Q12DCCPU-V...
  • Page 277 Before executing a command, confirm the specifications and specified argument of the command. Example) Do not execute the "close" command without an argument. If executed, the resource reserved in the VxWorks system will be closed. 9.7 Precautions for Program Debugging - 36 9.7.1 For Q12DCCPU-V...
  • Page 278 (b) When restarting the C Controller module Before restarting the C Controller module, disconnect the connection with Workbench. Failure to do so may cause an error in the C Controller module. - 37 9.7 Precautions for Program Debugging 9.7.1 For Q12DCCPU-V...
  • Page 279: For The Q06ccpu-v(-b)

    PROGRAMMING USING BUS INTERFACE FUNCTIONS 9.7.2 For the Q06CCPU-V(-B) (1) Specifying a VxWorks image file To debug the user program, specify the same VxWorks image file as that of the C Controller module for Tornado. Must match ! VxWorks VxWorks image file image file Development environment...
  • Page 280 PROGRAMMING USING BUS INTERFACE FUNCTIONS The following screen provides an example of specifying the VxWorks image file whose serial No. (first five digits) and the function version is "09051" and "B" respectively. Figure 9.6 VxWorks image file specification (b) VxWorks image file VxWorks image files are required to be copied from C Controller module to the development environment (personal computer) by FTP.
  • Page 281 PROGRAMMING USING BUS INTERFACE FUNCTIONS Remark For other debugging methods, refer to the manual for Tornado. (2) IP address setting of C Controller module To debug the user program by connecting the development environment (personal computer) with the C Controller module in Ethernet, specify the IP address of the C Controller module to Tornado.
  • Page 282 PROGRAMMING USING BUS INTERFACE FUNCTIONS (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) Select [Tools] [Target Server] [Configure] to open the "Configure Target Servers"...
  • Page 283 PROGRAMMING USING BUS INTERFACE FUNCTIONS Remark For other debugging methods, refer to the manual for Tornado. (4) Shell display setting To display output information (such as printf) from each task of the C Controller module, the following setting is required. Without the following setting, only the output information on the Shell task is displayed.
  • Page 284 PROGRAMMING USING BUS INTERFACE FUNCTIONS (5) Precautions for Telnet connection If the line is disconnected during use of Telnet, it cannot be reconnected until TCP connection including the Telnet on the C Controller module side is timed out. If this occurs, reconnect it after timeout. The timeout time for the C Controller module side Telnet (TCP) connection can be changed by setting the values in the calculation formula by the following setting methods.
  • Page 285 PROGRAMMING USING BUS INTERFACE FUNCTIONS (6) Precautions for executing Shell commands from Tornado Shell or the Telnet tool 1) When executing the Shell command from Tornado Shell, pay attention to the following since the entered Shell commands operate on the task of priority 1 in the C Controller module.
  • Page 286 PROGRAMMING USING BUS INTERFACE FUNCTIONS 3) When executing the Shell command from Tornado Shell or the Telnet tool • 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 properly.
  • Page 287: Program Registration

    Explorer for the following C Controller module. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • The Q06CCPU-V(-B) with the serial No. (first five digits) "12081" or higher. For the above C Controller module, enter the drive name directly in the address field of Explorer.
  • Page 288 PROGRAMMING USING BUS INTERFACE FUNCTIONS (b) Login user when using FTP The following indicates the login user data (user name, password) when using FTP. Table 9.11 Login user defaults Item Value User name "target" Password "password" For addition or change of the login user etc. other than above, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
  • Page 289 C Controller module> <Drive name.> • Example) When logging into the standard RAM using the settings for module initialization of the Q12DCCPU-V ftp://target:password@192.168.3.3/RAM Figure 9.12 Logging into the standard RAM with the settings for module initialization 9.8 Program Registration...
  • Page 290 PROGRAMMING USING BUS INTERFACE FUNCTIONS 2) The screen display after logging in to the C Controller module is as follows. Figure 9.13 Connection via FTP 3) After logging in to the C Controller module, perform write and read just as normal file operations in Explorer.
  • Page 291 PROGRAMMING USING BUS INTERFACE FUNCTIONS (2) Copy registration from a CompactFlash card to the standard RAM The following explains copy registration of the files in the CompactFlash card to the standard RAM of the C Controller module. This operation is not available on the Q06CCPU-V(-B). This operation allows to easily register the same user programs to multiple C Controller modules.
  • Page 292: Creating A Script File "startup.cmd

    PROGRAMMING USING BUS INTERFACE FUNCTIONS Creating a Script File "STARTUP.CMD" Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Definition of script file "STARTUP.CMD" is a script file of a user program which starts in booting up of the C Controller module, and it contains the loading location, startup order, parameter setting, etc.
  • Page 293 C Controller module VX_FP_TASK value Q12DCCPU-V 0x1000000 Q06CCPU-V(-B) Example) When activating the "funcA" function with the VX_FP_TASK option specified: < For the Q12DCCPU-V> taskSpawn("taskA",100,0x1000000,20000,funcA,0,0,0,0,0,0,0) <For the Q06CCPU-V(-B)> taskSpawn("taskA",100,0x8,20000,funcA,0,0,0,0,0,0,0) For details on the VX_FP_TASK option, refer to the following. Manuals for VxWorks Remark 1.
  • Page 294 PROGRAMMING USING BUS INTERFACE FUNCTIONS (3) Script file storage location The script file can be stored into the standard RAM, standard ROM, and CompactFlash card. (a) Script file storage location Store the script file in the root directory. • Standard RAM Root directory of standard RAM "/RAM"...
  • Page 295 (4) Example of script file description The following provides an example of describing the script file to start user programs on the Q12DCCPU-V. (a) When loading the user program from the script file in the standard RAM The following is an example of loading a user program ("fileA.out", "fileB.out") in the standard RAM from the script file in the standard RAM.
  • Page 296 PROGRAMMING USING BUS INTERFACE FUNCTIONS (b) When loading the user program from the script file in CompactFlash card The following provides an example of loading user programs ("fileA.out", "fileB.out") in the standard RAM and CompactFlash card from the script file in the CompactFlash card.
  • Page 297: Device Types For Bus Interface Functions

    PROGRAMMING USING BUS INTERFACE FUNCTIONS 9.10 Device Types for Bus Interface Functions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B The device types used for the bus interface functions can be specified either by the code number or device name indicated in this section. (1) Motion CPU dedicated device types The motion CPU dedicated device types can be specified in the argument sDevType of the QBF_MotionDDWR, QBF_MotionDDRD function.
  • Page 298 PROGRAMMING USING BUS INTERFACE FUNCTIONS (2) Device types for accessing CC-Link IE Controller Network modules or MELSECNET/H modules Specify the device type for accessing a CC-Link IE Controller Network module or MELSECNET/H module with the argument 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 299 PROGRAMMING USING BUS INTERFACE FUNCTIONS (3) Device types for internal user or system device access The device type for access to the internal user device or the internal system device can be specified with an argument, sDevType, of the following functions. •...
  • Page 300 PROGRAMMING USING BUS INTERFACE FUNCTIONS POINT 1. Use the internal link device buffers (LX buffer, LY buffer, LB buffer, and LW buffer) by setting the following items and refresh them with link devices (LX, LY, LB, and LW). Table 9.18 Setting link device refresh cycle and ranges Network Item Reference page...
  • Page 301: Chapter 10 Programming Using Melsec Data Link Functions

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS CHAPTER 10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B When applying program examples introduced in this chapter into actual systems, fully examine the applicability, and confirm that they do not cause system control problems.
  • Page 302 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS The system illustration below represents a system image based on the features described on the previous page. Intelligent function module CC-Link module I/O modules CC-Link IE Controller Q06CCPU-V Network module or MELSECNET/H module Programmable Programmable controller CPU controller CPU...
  • Page 303 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS Table 10.1 Access targets of MELSEC data link functions Setting of Device monitoring Communication Arrow Access target given utility Remarks path above Channel name Station Programmable controller Q series Other 12: Q series bus interface sta.
  • Page 304: Melsec Data Link Function List

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 10.2 MELSEC Data Link Function List Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Table 10.2 MELSEC data link function list 1)Q12DCCPU-V 2)Q06CCPU-V Availability Category Function name Description mdOpen Opens a communication line. Open/close mdClose Closes a communication line.
  • Page 305: Creating A New Project Of User Program And Compiling

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 10.4 Creating a New Project of User Program and Compiling Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B For details of creating a new project of user program and compiling, refer to the following. Page 9-9, "9.4 Creating and Compiling a New Project of User Program"...
  • Page 306 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (2) Precautions for using MELSEC data link functions (a) Precautions for programming 1) Opening and closing of communication lines ( Opening and closing of a communication line (mdOpen and mdClose functions) is allowed only once each at the start (task start) and the end (task end) of the user program task.
  • Page 307 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (b) Precautions for accessing to CC-Link module own station devices and other station programmable controller devices. When accessing via CC-Link module, provide interlocks according to the link states of the own and other stations. 1) Access to own station device Create a user program that provides interlocks to enable write to/read from the own station device.
  • Page 308 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (d) Precautions for access to CC-Link IE Controller Network module own station devices and other station programmable controller devices When accessing via a CC-Link IE Controller Network module, provide interlocks according to the link status of the own station. 1) Access to own station devices Create a user program that provides interlocks to enable write to/read from the own station device.
  • Page 309: Precautions For The Melsec Data Link Function

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 10.6 Precautions for the MELSEC Data Link Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B For details of precautions for the MELSEC data link function, refer to the following. Page 9-26, "9.6 Precautions for Functions" 10.7 Precautions for Program Debugging...
  • Page 310: 10.11 Station No. Setting For Melsec Data Link Functions

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 10.11 Station No. Setting for MELSEC Data Link Functions Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Functions other than extended functions Table 10.4 Functions other than extended functions Communication Station No. 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 311 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (b) Station No. setting for CC-Link module (other station) Network No. <Logical station No. setting method> 0: CC-Link Set "0" in the upper byte (network No.) and a logical station No. in the lower byte (station No.). Station No.
  • Page 312: 10.12 Device Types For The Melsec Data Link Function

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 10.12 Device Types for the MELSEC Data Link Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B Device type used for the MELSEC data link functions can be specified either by code numbers or device names. (1) Common device types Table 10.6 Common device types of MELSEC data link functions...
  • Page 313: Device Types For The Melsec Data Link Function

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS Table 10.6 Common device types of MELSEC data link functions (continued) Device type Code Device Device name DEC. HEX. DevQSW Q/QnA link special register (within Q/QnACPU) DevQV Q/QnA edge relay (within Q/QnACPU) DevSTN Retentive timer (current value) DevMAIL Q/QnA SEND function (with arrival confirmation) and RECV function DevMAILNC...
  • Page 314 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (2) Dedicated device types for Q series bus interface Table 10.7 Q series bus interface dedicated device types Device types Code Device Device name DEC. HEX. DevSPB1 CPU shared memory (area for CPU No.1) DevSPB2 CPU shared memory (area for CPU No.2) DevSPB3...
  • Page 315 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS Table 10.8 Device types for accessing CC-Link module (continued) Device type Code Device Device name DEC. HEX. -32735 8021 DevRX Other station RX -32734 8022 DevRY Other station RY -32732 8024 DevRW Other station link register -32669 8063 DevSB...
  • Page 316 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (c) Message send/receive Table 10.11 Device types for message send receive Device type Code Device Device name DEC. HEX. DevMAIL Q/QnA SEND function (with arrival confirmation) and RECV function DevMAILNC Q/QnA SEND function (no arrival confirmation) * 1 The device name specification (macro) is defined in this function's include file, "MdFunc.h".
  • Page 317: Accessible Ranges And Devices Of The Melsec Data Link Function

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 10.13 Accessible Ranges and Devices of the MELSEC Data Link Function Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B This section explains accessible ranges and devices for the following accesses. Table 10.13 Access list Access route Reference page Page 10-17...
  • Page 318 : Accessible : Inaccessible * 1 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 2 To access a device of device No.32768 (8000 )or higher, use an extended function. ( Page 10-4, Section 10.2)
  • Page 319 : Accessible : Inaccessible * 1 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 2 To access a device of device No.32768 (8000 )or higher, use an extended function. ( Page 10-4, Section 10.2)
  • Page 320 * 8 The following C Controller module cannot access the extended link register (W). • Q06CCPU-V with serial number (first five digits) "10011" or earlier * 9 Only the following C Controller module is accessible. • Q12DCCPU-V (Extended mode) • Q24DHCCPU-V with serial number (first five digits) "14081" or later • Q24DHCCPU-VG * 10 BFFFF or later cannot be accessed.
  • Page 321 : Accessible : Inaccessible * 1 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 2 When accessing to the device of number 32768 (8000 ) or higher, use an extended function.
  • Page 322 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS Table 10.16 Accessible devices for accessing other CPU (continued) Device type Access target Device (Device name Programmable controller C Controller module specification) Batch Other station buffer memory DevRBM Random Other station random access Batch DevRAB buffer Random...
  • Page 323: Access Via Cc-link

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 10.13.2 Access via CC-Link Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Accessible range The following accesses are allowed via CC-Link. • Master station where the CC-Link module is connected • Local station where the CC-Link module is connected •...
  • Page 324 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (2) Accessible devices (a) How to read the table 1) Batch and random of devices Table 10.17 Batch and random of devices Item in the table Description •Batch write (mdSend, mdSendEx functions) Batch •Batch read (mdReceive, mdReceiveEx functions) •Random write (mdRandW, mdRandWEx functions) •Random read (mdRandR, mdRandREx functions) •Bit set (mdDevSet, mdDevSetEx functions)
  • Page 325 • Q06CCPU-V with serial number (first five digits) "10101" or earlier * 2 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 3 When accessing to the device of No.32768 (8000 ) or higher, use an extended function.
  • Page 326 • Q06CCPU-V with serial number (first five digits) "10101" or earlier * 2 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 3 When accessing to the device of No.32768 (8000 ) or higher, use an extended function.
  • Page 327 * 11 The following C Controller module cannot access the extended link register (W). • Q06CCPU-V with serial number (first five digits) "10011" or earlier * 12 Only the following C Controller module is accessible. • Q12DCCPU-V (Extended mode) • Q24DHCCPU-V with serial number (first five digits) "14081" or later • Q24DHCCPU-VG * 13 BFFFF or later cannot be accessed.
  • Page 328 • Q06CCPU-V with serial number (first five digits) "10101" or earlier * 2 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 3 When accessing to the device of number 32768 (8000 ) or higher, use an extended function.
  • Page 329: Access Via Melsecnet/h

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 10.13.3 Access via MELSECNET/H Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Accessible range (a) How to read the table The items from [1.Connected network] to [4.Target CPU] in Table 10.22 correspond to the numbers indicated in the figure below.
  • Page 330 • Q06CCPU-V with serial number (first five digits) "10011" or earlier * 5 Access is not allowed to PC CPU modules. * 6 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V (To the next page) - 30 10.13 Accessible Ranges and Devices of the MELSEC Data Link Function...
  • Page 331 * 5 Access is not allowed to PC CPU modules. * 6 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V 10.13 Accessible Ranges and Devices of the MELSEC Data Link Function - 31 10.13.3 Access via MELSECNET/H...
  • Page 332 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (2) Accessible devices (a) How to read the table 1) Batch and random of devices Table 10.23 Batch and random of devices Item in the table Description •Batch write (mdSend, mdSendEx functions) Batch •Batch read (mdReceive, mdReceiveEx functions) •Random write(mdRandW, mdRandWEx functions) •Random read(mdRandR, mdRandREx functions) •Bit set(mdDevSet, mdDevSetEx functions)
  • Page 333 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (b) Accessible devices for accessing own station Table 10.25 Accessible devices for accessing own station Device type (Device name Device Accessibility specification) Own station input internal Batch DevX buffer (LX buffer) Random Own station output internal Batch DevY buffer (LY buffer)
  • Page 334 : Accessible : Inaccessible * 1 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 2 When accessing to the device of number 32768 (8000 ) or higher, use an extended function.
  • Page 335 * 10 The following C Controller module cannot access the extended link register (W). • Q06CCPU-V with serial number (first five digits) "10011" or earlier * 11 Only the following C Controller module is accessible. • Q12DCCPU-V (Extended mode) • Q24DHCCPU-V with serial number (first five digits) "14081" or later • Q24DHCCPU-VG * 12 BFFFF or later cannot be accessed.
  • Page 336 : Accessible : Inaccessible * 1 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 2 When accessing to the device of number 32768 (8000 ) or higher, use an extended function.
  • Page 337 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS Table 10.26 Accessible devices for accessing other station (continued) Access target Device type Device (Device name specification) Batch Other station random access DevRAB buffer Random Batch Other station RX DevRX Random Batch Other station RY DevRY Random Batch...
  • Page 338: Access Via Cc-link Ie Controller Network

    PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 10.13.4 Access via CC-Link IE Controller Network Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) Accessible range (a) How to read the table The items from [1.Connected network] to [4.Target CPU] in the Accessibility table correspond to the numbers indicated in the figure below.
  • Page 339 * 4 Access is not allowed to the PC CPU modules. * 5 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V 10.13 Accessible Ranges and Devices of the MELSEC Data Link Function - 39 10.13.4 Access via CC-Link IE Controller Network...
  • Page 340 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (2) Accessible devices (a) How to read the table 1) Batch and random of devices Table 10.29 Batch and random of devices Item in the table Description •Batch write (mdSend, mdSendEx functions) Batch •Batch read (mdReceive, mdReceiveEx functions) •Random write(mdRandW, mdRandWEx functions) •Random read(mdRandR, mdRandREx functions) •Bit set(mdDevSet, mdDevSetEx functions)
  • Page 341 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS (b) Accessible devices for accessing own station Table 10.31 Accessible devices for accessing own station Device type (Device name Device Accessibility specification) Own station input internal Batch DevX buffer (LX buffer) Random Own station output internal Batch DevY buffer (LY buffer)
  • Page 342 : Accessible : Inaccessible * 1 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 2 When accessing to the device of number 32768 (8000 ) or higher, use an extended function.
  • Page 343 : Accessible : Inaccessible * 1 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 2 When accessing to the device of number 32768 (8000 ) or higher, use an extended function.
  • Page 344 : Accessible : Inaccessible * 1 The following C Controller module is not accessible. • Q12DCCPU-V with serial number (first five digits) "12041" or earlier • Q06CCPU-V * 2 When accessing to the device of number 32768 (8000 ) or higher, use an extended function.
  • Page 345 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS Table 10.32 Accessible devices for accessing other station (continued) Access target Device type Device (Device name specification) Batch Other station buffer memory DevRBM Random Batch Other station random access DevRAB buffer Random Batch Other station RX DevRX Random Batch...
  • Page 346: Chapter 11 Programming Using Vxworks Api Functions

    PROGRAMMING USING VxWorks API FUNCTIONS CHAPTER 11 PROGRAMMING USING VxWorks API FUNCTIONS Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B For the component list and information checking method of the VxWorks component implemented in the C Controller module, refer to the following. Page APPX-1, "Appendix 1 VxWorks Component List"...
  • Page 347 PROGRAMMING USING VxWorks API FUNCTIONS Memo...
  • Page 348: Chapter 12 Sample Programs

    Sample programs are provided as a reference used in creating user programs. Please use the sample programs at user's own discretion. (1) Sample programs for the Q12DCCPU-V Sample programs for the Q12DCCPU-V are installed in "C:\MELSEC\CCPU\CCPUTOOL\Sample\DVx" (When SW3PVC-CCPU has been installed in "C:\MELSEC".).
  • Page 349 SAMPLE PROGRAMS Table 12.1 Registered sample programs (continued) Folder name File name Description of sample program CCIEField\ For performing cyclic transmission with the master station in the CC-Link IE Field LocalStation.c LocalStation Network (local station). CCIEField\ MasterStation_Loc For performing cyclic transmission with the local station in the CC-Link IE Field MasterStation_Loc alStation.c Network (master station).
  • Page 350 SAMPLE PROGRAMS (2) Sample programs for the Q06CCPU-V(-B) Sample programs for the Q06CCPU-V(-B) are installed in "C:\MELSEC\CCPU\CCPUTOOL\Sample\Vx" (When SW3PVC-CCPU has been installed in "C:\MELSEC".). For opening sample programs, refer to the following. Page 12-5, Section 12.1 Table 12.2 Registered sample programs Folder name File name Description of sample program...
  • Page 351 SAMPLE PROGRAMS Table 12.2 Registered sample programs (continued) Folder name File name Description of sample program CCIEField\ For performing cyclic transmission with the master station in the CC-Link IE Field LocalStation.c LocalStation Network (local station). CCIEField\ MasterStation_Loc For performing cyclic transmission with the local station in the CC-Link IE Field MasterStation_Loc alStation.c Network (master station).
  • Page 352: Procedure For Opening Sample Programs

    Page 9-9, Section 9.4 (1) Procedure for opening the sample program for the Q12DCCPU-V The following windows are those of Wind River Workbench, but the procedure is the same when CW Workbench is used.
  • Page 353 SAMPLE PROGRAMS (From the previous page) Select "General" "Existing Projects into Workplace", and Next> click the button. Specify a directory name to "Select root directory" which the source file of the sample program are stored. Confirm the sample program in "Projects" is selected, and Finish click the button.
  • Page 354 SAMPLE PROGRAMS (2) Procedure for opening the sample program for the Q06CCPU-V(-B) Start Tornado. When Workspace is opened automatically, perform procedure of or later. When Workspace is not opened automatically, perform the following operations continuously. Select the [File] [New Project] from the menu bar. Select "Create downloadable application modules for VxWorks", and click the button.
  • Page 355 SAMPLE PROGRAMS (From the previous page) After confirming the setting of "Workspace", "Project", and Finish "Tool Chain" are correct, click the button. Select the "File" "Add Project to Workspace". Select the file whose extension is wpi in the same folder of the sample program, and click the button.
  • Page 356 SAMPLE PROGRAMS (From the previous page) Open the <<Build>> tab of "Workspace" window. Double click the icon ( ) to display the following items. Right click "SH7750gnu" and select "Set 'SH7750gnu' as Active Build" from the menu bar. (To the next page) 12.1 Procedure for Opening Sample Programs...
  • Page 357 SAMPLE PROGRAMS (From the previous page) The sample program can be opened from the project when opening the <<Files>> tab of the "Workspace" window. (Completed) 12.1 Procedure for Opening Sample Programs - 10...
  • Page 358: Chapter 13 Event Number List

    EVENT NUMBER LIST CHAPTER 13 EVENT NUMBER LIST Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B When an event such as an error occurs in the C Controller system, information required to correct errors such as an event No. is displayed on the Event history tab. When an event has occurred, check the event No.
  • Page 359 EVENT NUMBER LIST (1) When the source is "MQbfDrv" When taking corrective actions of corresponding error code, refer to HELP of C Controller setting utility. Table 13.2 Corrective actions Event No. Event type Event Corrective action Failed to allocate memory required for the Increase the system memory.
  • Page 360 EVENT NUMBER LIST (2) When the source is "MXwdkDrv" Table 13.3 Corrective action Event No. Event type Event Corrective action The clock data of the C Controller module have been set. This event occurs when: •Clock data was set by executing the 40000000 System(Info.) QBF_SetTime function.
  • Page 361 EVENT NUMBER LIST (4) When source is "MUtlIfMd" Table 13.5 Corrective action Event No. Event type Event Corrective action Check the port No. used and change it if C0000000 System(Err.) An illegal packet error occurred. necessary. Change the IP address. Check the utility and C Controller module C0000001 System(Err.)
  • Page 362 When taking corrective actions for an error code, refer to HELP of C Controller setting utility. Table 13.8 Corrective action Event No. Event type Event Corrective action •Q12DCCPU-V It might be a breakdown of the C Controller •Q12DCCPU-V module. The standard ROM drive was illegally Please consult your local Mitsubishi service accessed.
  • Page 363 EVENT NUMBER LIST Table 13.8 Corrective action (continued) Event No. Event type Event Corrective action Write the file again if the file was not written correctly. A timeout occurred during writing to file in the 80000406 System(Warning) If this event occurs frequently, reexamine the standard ROM drive "/ROM".
  • Page 364 EVENT NUMBER LIST (8) When the source is "MCfDrv" Table 13.9 Corrective action Event No. Event type Event Corrective action The CompactFlash Card is pulled out once, C0000480 System(Err.) The CompactFlash card is not responding. and it inserts it again. Replace the CompactFlash card.
  • Page 365 EVENT NUMBER LIST (9) When the source is "MEtherDrv" Table 13.10 Corrective action Event No. Event type Event Corrective action A system error in the C Controller is possible cause. C0000200 System(Err.) An initialization parameter error occurred. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
  • Page 366: Appendices

    C++ iostream and other standard library facilities INCLUDE_CPLUS_IOSTREAM * 1 The following C Controller module cannot be used. • The Q12DCCPU-V with the serial No. (first five digits) "12041" or higher. (To the next page) APPX Appendix 1 VxWorks Component List...
  • Page 367 INCLUDE_DISK_UTIL_SHELL_CMD file upload path initialization INCLUDE_WVUPLOAD_FILE * 1 The following C Controller module cannot be used. • The Q12DCCPU-V with the serial No. (first five digits) "12041" or higher. (To the next page) APPX Appendix 1 VxWorks Component List...
  • Page 368 MIB2 ICMP Management APIs INCLUDE_MIB2_ICMP MIB2 IF Counter Instrumentation INCLUDE_MIB2_IF * 1 The following C Controller module cannot be used. • The Q12DCCPU-V with the serial No. (first five digits) "12041" or higher. (To the next page) APPX Appendix 1 VxWorks Component List...
  • Page 369 APPENDICES Table APPX.1 VxWorks component list (continued) Component Macro MIB2 TCP Management APIs INCLUDE_MIB2_TCP MIB2 UDP Management APIs INCLUDE_MIB2_UDP MMU global map INCLUDE_MMU_GLOBAL_MAP module manager INCLUDE_MODULE_MANAGER mutex semaphore creation routine INCLUDE_SEM_MUTEX_CREATE mutex semaphores INCLUDE_SEM_MUTEX MUX support INCLUDE_MUX netBufLib INCLUDE_NETBUFLIB netBufPool INCLUDE_NETBUFPOOL NetDrv for remote IO INCLUDE_NET_DRV...
  • Page 370 APPENDICES Table APPX.1 VxWorks component list (continued) Component Macro POSIX process scheduling INCLUDE_POSIX_SCHED POSIX PSE52 support for RTPs INCLUDE_RTP_POSIX_PSE52 POSIX scheduling policies SCHED_FIFO/SCHED_RR/ INCLUDE_PX_SCHED_DEF_PLICIES SCHED_OTHER support in RTPs POSIX semaphore INCLUDE_POSIX_SEM POSIX semaphore show routine INCLUDE_POSIX_SEM_SHOW POSIX Shared Memory Objects INCLUDE_POSIX_SHM POSIX signal INCLUDE_POSIX_SIGNALS...
  • Page 371 APPENDICES Table APPX.1 VxWorks component list (continued) Component Macro signals INCLUDE_SIGNALS INCLUDE_SIO SNTP client INCLUDE_SNTPC Socket API INCLUDE_SOCKLIB Socket API System Call support INCLUDE_SC_SOCKLIB INCLUDE_SPY Stack/Application Logging Utility INCLUDE_APPL_LOG_UTIL stdio INCLUDE_STDIO stricmp INCLUDE_STRICMP strnicmp INCLUDE_STRNICMP Support for reboot hooks INCLUDE_REBOOT_HOOKS symbol shell commands INCLUDE_SYM_SHELL_CMD symbol table show routine...
  • Page 372 APPENDICES Table APPX.1 VxWorks component list (continued) Component Macro VxWorks events INCLUDE_VXEVENTS watchdog timers INCLUDE_WATCHDOGS watchdog timers creation and deletion library INCLUDE_WATCHDOGS_CREATE_DELETE WDB agent INCLUDE_WDB WDB banner INCLUDE_WDB_BANNER WDB breakpoints INCLUDE_WDB_BP WDB call functions INCLUDE_WDB_FUNC_CALL WDB callouts INCLUDE_WDB_DIRECT_CALL WDB eventpoints INCLUDE_WDB_EVENTPOINTS WDB events INCLUDE_WDB_EVENTS...
  • Page 373 APPENDICES (b) For the Q06CCPU-V(-B) The following list shows the components implemented in the C Controller module. Table APPX.2 VxWorks component list Component Macro ANSI assert INCLUDE_ANSI_ASSERT ANSI ctype INCLUDE_ANSI_CTYPE ANSI locale INCLUDE_ANSI_LOCALE ANSI math INCLUDE_ANSI_MATH ANSI stdio INCLUDE_ANSI_STDIO ANSI stdio extensions INCLUDE_ANSI_STDIO_EXTRA ANSI stdlib INCLUDE_ANSI_STDLIB...
  • Page 374 APPENDICES Table APPX.2 VxWorks component list (continued) Component Macro enable caches INCLUDE_CACHE_ENABLE END attach interface INCLUDE_END_BOOT END interface support INCLUDE_END environment variables INCLUDE_ENV_VARS exception handling INCLUDE_EXC_HANDLING exception task INCLUDE_EXC_TASK file upload path initialization INCLUDE_WVUPLOAD_FILE floating point show routine INCLUDE_HW_FP_SHOW formatted IO INCLUDE_FORMATTED_IO fpp formatting for printf INCLUDE_FLOATING_POINT...
  • Page 375 APPENDICES Table APPX.2 VxWorks component list (continued) Component Macro POSIX mman INCLUDE_POSIX_MEM POSIX scheduler INCLUDE_POSIX_SCHED POSIX semaphores INCLUDE_POSIX_SEM POSIX signals INCLUDE_POSIX_SIGNALS POSIX timers INCLUDE_POSIX_TIMERS RAM disk driver INCLUDE_RAMDRV rBuff library INCLUDE_RBUFF read the bootline INCLUDE_BOOT_LINE_INIT Remote Procedure Call system INCLUDE_RPC ring buffers INCLUDE_RNG_BUF RLOGIN/TELNET password protection...
  • Page 376 APPENDICES Table APPX.2 VxWorks component list (continued) Component Macro watchdog timers INCLUDE_WATCHDOGS WDB agent INCLUDE_WDB WDB banner INCLUDE_WDB_BANNER WDB breakpoints INCLUDE_WDB_BP WDB call functions INCLUDE_WDB_FUNC_CALL WDB callouts INCLUDE_WDB_DIRECT_CALL WDB END driver connection INCLUDE_WDB_COMM_END WDB eventpoints INCLUDE_WDB_EVENTPOINTS WDB events INCLUDE_WDB_EVENTS WDB exception notification INCLUDE_WDB_EXC_NOTIFY WDB gopher INCLUDE_WDB_GOPHER...
  • Page 377 VxWorks component information can be checked by the following procedure. VxWorks image cannot be created (changed). (a) For the Q12DCCPU-V The following windows are those of Wind River Workbench, but the procedure is the same when CW Workbench is used.
  • Page 378: Appendix 1 Vxworks Component List

    APPENDICES (b) For the Q06CCPU-V(-B) Select [File] [New Project] from the menu bar. Select "Create a bootable VxWorks image (custom configured)" and click the button. Enter "Name", "Location", and "Workspace" and then click button. Next> (To the next page) APPX - 13 Appendix 1 VxWorks Component List...
  • Page 379 APPENDICES (From the previous page) Select "A BSP" and click the button. Next> Check that the values in "Workspace", "Project", and "Basis Finish BSP" are correct and then click the button. Open the <<VxWorks>> tab of the "Workspace" window. (To the next page) APPX Appendix 1 VxWorks Component List - 14...
  • Page 380 APPENDICES (From the previous page) Click the ( ) icon to expand the items at this level of the hierarchy. Right-click on "ANSI assert" and select [Properties] from the menu. Check the information of VxWorks components with the Properties screen displayed. (Completed) APPX - 15...
  • Page 381 APPENDICES Remark The VxWorks components can be located by the following procedure. Right click to select [Find Object] from the menu. Click the button. Find APPX Appendix 1 VxWorks Component List - 16...
  • Page 382: Appendix 2 Precautions For Program Replacement

    Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B (1) When the Q06CCPU-V has been replaced with the Q12DCCPU-V When porting the programs developed by Tornado to Workbench, refer to the Migration Guide provided by Wind River Systems, Inc. The Migration Guide can be downloaded from the website: (www.windriver.com).
  • Page 383 Connection target ··········································3-5 CPU type ·····················································3-4 Creating a new project and compiling ·················9-9 Parameter setting file ····································3-14 Q06CCPU-V(-B) ······································· 9-17 Program registration ·····································9-46 Q12DCCPU-V ············································9-9 Programming procedure ································· 9-8 Development environment ·······························2-1 Sample programs ·········································12-1 Device monitoring utility ··································8-1 Opening ··················································12-5 Batch monitoring·········································8-2...
  • Page 384 Title bar······················································3-16 Uninstallation ··············································2-12 VxWorks image file specification ·····················9-31 Q06CCPU-V(-B) ·······································9-38 Q12DCCPU-V ··········································9-31 INDEX...
  • Page 385 WARRANTY Please confirm the following product warranty details before using this product. 1. Gratis Warranty Term and Gratis Warranty Range If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product within the gratis warranty term, the product shall be repaired at no cost via the sales representative or Mitsubishi Service Company.
  • Page 386 Microsoft, Windows, Windows NT, and Windows Vista are trademarks or registered trademarks of Microsoft Corporation in the United States and other countries. Intel and Pentium are either registered trademarks or trademarks of Intel Corporation in the United States and/or other countries.
  • Page 388 SH(NA)-080767ENG-M(1710)KWIX MODEL: Q12DCCPU-V-U-UP-E MODEL CODE: 13JZ18 HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN NAGOYA WORKS : 1-14 , YADA-MINAMI 5-CHOME , HIGASHI-KU, NAGOYA , JAPAN When exported from Japan, this manual does not require application to the Ministry of Economy, Trade and Industry for service transaction permission.

This manual is also suitable for:

Q06ccpu-vQ06ccpu-v-bSw3pvc-ccpu-e

Comments to this Manuals

Symbols: 0
Latest comments: