For the safety instructions of the programmable controller system, please read the CPU module user's manual. In this manual, the safety precautions are ...
C Controller Module User's Manual (Utility Operation, Programming)
-Q12DCCPU-V (Basic mode) -Q06CCPU-V -Q06CCPU-V-B -SW3PVC-CCPU-E
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. In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".
WARNING CAUTION
Indicates that incorrect handling may cause hazardous conditions, resulting in death or severe injury.
Indicates that incorrect handling may cause hazardous conditions, resulting in minor or moderate injury or property damage.
Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious consequences. Observe the precautions of both levels because they are important for personal and system safety.
Make sure that the end users read this manual and then keep the manual in a safe place for future reference.
[Design 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. (1) Changing data of the running C Controller module from the development environment (personal
computer) connected (2) Changing the operating status (3) Operating from the development environment (personal computer) Especially, in the case of control from an external device to a remote C Controller module, immediate action cannot be taken for a problem on the C Controller module due to a communication failure. To prevent this, configure an interlock circuit in the user program, and determine corrective actions to be taken between the external device and C Controller module in case of a communication failure.
A - 1
[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. (1) Changing data of the running C Controller module from the development environment (personal
computer) connected (2) Changing the operating status (3) Operating from the development environment (personal computer) Especially, in the case of control from an external device to a remote C Controller module, immediate action cannot be taken for a problem on the C Controller module due to a failure of data communication. To prevent this, configure an interlock circuit in the user program, and determine corrective actions to be taken between the external device and C Controller module in case of a failure of data communication.
CAUTION
Before performing online operations (especially, program modification, forced output, and operation status change) for the running C Controller module from the peripheral connected, read relevant manuals carefully and ensure the safety. Improper operation may damage machines or cause accidents.
A - 2
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.
(2) The PRODUCT has been designed and manufactured for the purpose of being used in general industries. MITSUBISHI SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED TO ANY AND ALL RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT, PRODUCT LIABILITY) FOR ANY INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO PROPERTY CAUSED BY the PRODUCT THAT ARE OPERATED OR USED IN APPLICATION NOT INTENDED OR EXCLUDED BY INSTRUCTIONS, PRECAUTIONS, OR WARNING CONTAINED IN MITSUBISHI'S USER, INSTRUCTION AND/OR SAFETY MANUALS, TECHNICAL BULLETINS AND GUIDELINES FOR the PRODUCT. ("Prohibited Application") Prohibited Applications include, but not limited to, the use of the PRODUCT in; · Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the public could be affected if any problem or fault occurs in the PRODUCT. · Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality assurance system is required by the Purchaser or End User. · Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator, Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for Recreation and Amusement, and Safety devices, handling of Nuclear or Hazardous Materials or Chemicals, Mining and Drilling, and/or other applications where there is a significant risk of injury to the public or property.
Notwithstanding the above, restrictions Mitsubishi may in its sole discretion, authorize use of the PRODUCT in one or more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific applications agreed to by Mitsubishi and provided further that no special quality assurance or fail-safe, redundant or other safety features which exceed the general specifications of the PRODUCTs are required. For details, please contact the Mitsubishi representative in your region.
A - 3
REVISIONS
Print date Jun., 2009 Jan., 2010 Aug., 2010
Mar., 2011 Jul., 2011 Dec., 2012 Oct., 2013
Dec., 2013 Mar., 2014 Jul., 2014
*The manual number is given on the bottom left of the back cover.
*Manual number SH(NA)-080767ENG-A First edition SH(NA)-080767ENG-B Partial correction
Revision
SAFETY PRECAUTIONS, Chapter 11 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
CONDITIONS OF USE FOR THE PRODUCT, Section 4.8, 12.1
Section number
Section 4.8 to 4.13 Section 4.9 to 4.14 SH(NA)-080767ENG-D Partial correction
PRECAUTIONS, Section 9.2, 9.7.1, 9.7.2, Chapter 13 SH(NA)-080767ENG-E Partial correction
PRECAUTIONS, ABOUT MANUALS, GENERIC TERMS AND ABBREVIATIONS, Section 1.1, 2.1, 9.4.1, 9.6, 12.1, Appendix 1 SH(NA)-080767ENG-F Partial correction
GENERIC TERMS AND ABBREVIATIONS, Section 8.13, 10.3.1, 10.13.2, 10.13.3, 10.13.4 SH(NA)-080767ENG-G Partial correction
ABOUT MANUALS, GENERIC TERMS AND ABBREVIATIONS, Chapter 1, Appendix 2
Addition
PRODUCT ORGANIZATION
Partial correction SH(NA)-080767ENG-H GENERIC TERMS AND ABBREVIATIONS, Section 10.3.2, Section 10.3.3,
Section 10.3.4
SH(NA)-080767ENG-I
Partial correction GENERIC TERMS AND ABBREVIATIONS, Section 2.1, Section 10.13.1, Section 10.13.2, Section 10.13.3, Section 10.13.4
Partial correction
SH(NA)-080767ENG-J ABOUT MANUALS, GENERIC TERMS AND ABBREVIATIONS, Chapter 1, Section 3.2, Section 8.13, Section 10.13.1, Section 10.13.2, Section 10.13.3, Section 10.13.4
A - 4
Print date Jun., 2015 Dec., 2015 Oct., 2017
*The manual number is given on the bottom left of the back cover
*Manual number
Revision
Partial correction
ABOUT MANUALS, Section 10.13.1, Section 10.13.2, Section 10.13.3, SH(NA)-080767ENG-K Section 10.13.4
Addition
WARRANTY
SH(NA)-080767ENG-L Partial correction PACKING LIST, WARRANTY
Partial correction SH(NA)-080767ENG-M ABOUT MANUALS, GENERIC TERMS AND ABBREVIATIONS, Chapter 1,
Section 2.1
Japanese manual version SH-080765-O
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.
© 2009 MITSUBISHI ELECTRIC CORPORATION
A - 5
PRECAUTIONS
The following precautions are given in this section.
Precautions For installation, uninstallation For each utility For programming For debugging a program For using FTP For the Wind River Systems product
Reference page Page A-6 Page A-6 Page A-7 Page A-11 Page A-16 Page A-16
(1) Precautions for installation and uninstallation
(a) Installation by overwriting · When installing utility by overwriting, the same folder where the existing one is installed must be used. Any other folders cannot be used. · Installation by overwriting is available only onto the same version of SW3PVC-CCPU. To install another version of utility, uninstall existing one before installation.
(b) Uninstallation Do not terminate uninstallation during processing. If terminated, redo the uninstallation all over again. If the uninstallation fails after terminating the uninstallation, reinstall the software and then uninstall it again.
(2) Precautions for utility
(a) Communication error of utility When the line is congested, communication errors (time out errors) are more likely to occur (monitoring stops if running) in each utility. If a utility communication error has occurred, set the connection target again in Connection setting.
(b) 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). Finish the script file processing before connecting utility to a C Controller module. If the RUN LED remains flashing, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation) and troubleshoot the problem.
(c) Terminating Microsoft® Windows® Do not terminate Microsoft® Windows® while utility other than Device monitoring utility is running. Terminate all the running utility (other than Device monitoring utility) first and then Microsoft® Windows®.
A - 6
(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.
(3) Precautions for programming
(a) Restrictions on the bus interface functions and MELSEC data link functions
1) Endian format (memory layout)
There are two models of the Q06CCPU-V(-B), which are in little endian format
(memory layout) and in big endian format.
Create user programs in either little or big endian that is appropriate to the
model used.
(Set the compiler by selecting "A toolchain" when creating a project on
Tornado. (
Page 9-17, Section 9.4.2))
2) User program execution
Execute a user program by starting a task from the script file.
(
Page 9-51, Section 9.9)
The system may malfunction if the user program is executed without a task
being started.
3) Execution type priority Set the priority of a task for executing the FTP user program as described below.
[When access is not made via FTP during user program execution] Set the priority of the user program task to 100 or more (100 to 255). If the priority is set within 0 to 99, the system may not operate properly.
[When access is made via FTP during user program execution] The actual FTP processing (task) of the C Controller module is performed at the priority of 200. When accessing via FTP during executing a user program, perform programming as described below.
· Set the priority of the user program task within 201 to 255. · When setting the priority of the user program task within 100 to 200, insert
a wait processing (such as taskDalay) in the user program to let the actual FTP processing operate.
A - 7
4) To communicate with a target device by Ethernet communication (excluding utility communications) Check the port number being used in the C Controller module by using the VxWorks- standard "inetstatShow" command. Do not use any port number that has already been used. Normal communication may not be available if used. Execute the "inetstatShow" command as follows: [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. Write it to a CompactFlash card, network device (such as FTP/NFS/netDrv driver) file, or RAM disk. For details of network devices and RAM disks, refer to the manual for VxWorks.
6) 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.
A - 8
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. · Shell command · Workbench/Tornado connection · File access · Mount/unmount of CompactFlash card · Ethernet communications · NFS server communication If any of the above is used, CPU utilization for a system task with high priority may increase and a system watchdog timer error, a user watchdog timer error, and link refresh timeout may occur more frequently. For the link refresh timeout, the rate of occurrence may also increase when bus interface driver processing (connections with peripheral devices or communication with an intelligent function module, etc.) is used.
8) Common restrictions For restrictions common to the bus interface functions and MELSEC data link functions, refer to the following. Page 9-26, "9.6 Precautions for Functions"
(b) Restrictions on the bus interface function
1) Clock setting Do not set the clock of the C Controller module while the QBF_WaitEvent function or the QBF_WaitUnitEvent function is in process.
2) Execution results of remote STOP/PAUSE and the bus interface function When the operation status of the C Controller module is either the remote STOP or remote PAUSE, the following execution results will be an error during STOP/PAUSE. · Output (Y) (QBF_Y_OutBitEx function, QBF_Y_OutWordEx function) · Writing to buffer memory (QBF_ToBuf function) The Y output and writing to buffer memory can be executed from the <<Module monitoring>> tab of the C Controller setting utility.
3) Restrictions on the bus interface function Refer to the following. Page 9-23, "9.5 Programming Flow for Bus Interface Functions"
(c) Precautions on MELSEC data link functions 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 each user program. Repeating opening/closing in every communication degrades communication performance. For the Q06CCPU-V-B, the MELSEC data link functions cannot be used. For restrictions on MELSEC data link functions, refer to the following. Page 10-5, "10.5 MELSEC Data Link Function Programming Flow"
A - 9
A - 10
(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. To retain the login user settings, describe a registration (adding/deleting) of the settings in a script file. Describe either of the following in the script file. · Directly describe the login user operation commands (loginUserAdd function or loginUserDelete function). · Provide a description that starts the user program task for login user operation. For login user settings, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
(e) Power off and reset during writing a user file Data corruption or a file system error may occur if the C Controller system is powered off or is reset (including remote RESET) during writing data to a user file in the standard RAM, standard ROM, or CompactFlash card. To power off or reset the C Controller system during writing data to a user file in the standard RAM, standard ROM, or CompactFlash card, perform the following first.
1) When writing data to a file in the standard RAM or standard ROM Close the file where data are being written. (Program example 1, CHAPTER 12)
Page 12-
2) When writing data to a file in a CompactFlash card Close the file where data are being written, and unmount the CompactFlash
card. (Program example
Page 12-1, CHAPTER 12)
For the stop processing of the CompactFlash card, refer to the C Controller
Module User's Manual (Hardware Design, Function Explanation).
(f) Watchdog timer A user watchdog timer error occurs when the user watchdog timer cannot be reset due to some reasons such as user program runaway. When a user watchdog timer occurs, perform the following. · Increase the WDT time set by the QBF_StartWDT function. · Lower the CPU utilization of tasks that require high utilization. Or set them not to operate. · Review user programs. After the above operations, reset the C Controller system. For resetting, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
(g) IP address The IP address of the C Controller module cannot be set from a user program. Set in the <<Online operation>> tab of C Controller setting utility.
(h) Script file "STARTUP.CMD" In the script file, describe commands for setting a login user (adding/deleting) and user program startups as necessary. · Setting a login user C Controller Module User's Manual (Hardware Design, Function Explanation) · Creating a script file Page 9-51, "9.9 Creating a Script File "STARTUP.CMD""
(i) Task activation Always specify the VX_FP_TASK option for the third argument of taskSpawn when activating a task that: · Performs floating-point operations. · Calls a function that returns a floating-point value. · Calls a function that takes a floating-point value as an argument. If the above task is activated without the VX_FP_TASK option specified, the operating system may run away. When specifying the VX_FP_TASK option in a script file, refer to the following. Page 9-51, Section 9.9 (2)
For details on the VX_FP_TASK option, refer to the following. Manuals for VxWorks
(4) Precautions for program debugging
(a) VxWorks image file
When debugging a user program, specify the VxWorks image file same as the
one in the 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)
1) When VxWorks image files are not identical
When the VxWorks image file in the development environment (personal
computer) and in the C Controller module are not identical, copy the image file
in the C Controller module into the development environment (personal
computer). (
Page 9-46, Section 9.8)
The image file of the C Controller is stored in the system drive (/SYSTEMROM/
OS_IMAGEFILE).
2) When connected with the different VxWorks image file specified
When the VxWorks image file in the C Controller module and in Workbench or
Tornado are not identical, a system watchdog timer error may occur in the C
Controller module.
In addition, debugging cannot be performed normally. (
Page 9-31,
Section 9.7)
A - 11
(b) 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.
[Calculation formula for the Q12DCCPU-V] The timeout time is determined by the following calculation formula.
Timeout time =
net.inet.tcp.keepidle + (net.inet.tcp.keepintvl
8 (number of retries)*1) [ms]
Initial value for C Controller module: 30000 (30 seconds) Initial value for VxWorks: 7800000 (2 hours and 10 minutes)
net.inet.tcp.keepidle: Time from line disconnection to the first retry (ms) Initial value for C Controller module: 22000 Initial value for VxWorks: 7200000
net.inet.tcp.keepintvl: Retry interval (ms) Initial value for C Controller module: 1000 Initial value of VxWorks: 75000
* 1 The number of retries cannot be changed.
[Setting method for the Q12DCCPU-V] The following explains how to set the initial value to 30 seconds.
· Setting while the C Controller module is in operation 1) Connect the line to the C Controller module with the Telnet tool. 2) Execute the following two Sysct1() commands with the Telnet tool to set the timeout time to the initial value. Sysctl("net.inet.tcp.keepidle = 22000") Sysctl("net.inet.tcp.keepintvl = 1000") 3) Close the Telnet connection.
· Setting at the timing of starting C Controller module 1) Describe the following two Sysct1() commands on the script file, "STARTUP.CMD". Sysctl("net.inet.tcp.keepidle = 22000") Sysctl("net.inet.tcp.keepintvl = 1000") 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.
A - 12
[Calculation for the Q06CCPU-V(-B)] The timeout time is determined by the following calculation formula. Timeout time = tcp_keepidle + (tcp_keepintvl 2 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 tcp_keepcnt: Number of retries
Initial value: 8 [Settings methods for the Q06CCPU-V(-B)] The following explains how to set the initial value to 4 hours and 10 minutes.
· Setting while the C Controller module is in operation 1) Connect the line to the C Controller module with the Telnet tool. 2) Set the following three external variables with the Telnet tool to change the timeout time to the initial value. tcp_keepidle = 14400 tcp_keepintvl = 150 tcp_keepcnt = 8 3) Close the Telnet connection.
· Setting at the timing of starting the C Controller module 1) Describe the following three external variable settings on the script file, "STARTUP.CMD". tcp_keepidle = 14400 tcp_keepintvl = 150 tcp_keepcnt = 8 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.
A - 13
(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. · Only alphanumeric characters and special characters can be used. · Some commands, such as those exclusively using the CPU module and those including characters other than alphanumeric characters and special characters, may be regarded as a command causing a watchdog timeout error, a control code (such as "CTRL + X"), or being garbled. As a result, a system error, such as a system watchdog timer error, or stop may occur in the C Controller module. Pay full attention to the command when entering it. · Some commands (example: the status-indicating Show command) may disable an interrupt for a long time. During the time, processing called from an interrupt routine (interrupt program) (example: bus interface function for ISR) is not executed. Interrupts that are expected to occur at fixed intervals, such as multiple CPU synchronous interrupt, may delay. When executing a command, pay attention to the above.
A VxWorks message may appear on Shell during connecting from Shell to the C Controller module. For messages of VxWorks, refer to the manual for VxWorks, Workbench, or Tornado.
2) When executing the Shell command from the Telnet tool When executing a Shell command from the Telnet tool, make one-to-one connection between the Telnet tool and the C Controller module. Connection cannot be made from multiple Telnet tools to the same C Controller module. 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. For Telnet functions, refer to C Controller Module User's Manual (Hardware Design, Function Explanation).
A - 14
The Shell commands entered by the Telnet tool of the development environment (personal computer) operate on the task of the following priorities in the C Controller module.
C Controller module Q12DCCPU-V Q06CCPU-V(-B)
Priority 1 2
When using Shell commands, pay attention to the following: · Only alphanumeric characters and special characters can be used. · Some commands, such as those exclusively using the CPU module and those including characters other than alphanumeric characters and special characters, may be regarded as a command causing a watchdog timeout error, a control code (such as "CTRL + X"), or being garbled. As a result, a system error, such as a system watchdog timer error, or stop may occur in the C Controller module. Pay full attention to the command when entering it. · Some commands (example: the status-indicating Show command) may disable an interrupt for a long time. During the time, processing called from an interrupt routine (interrupt program) (example: bus interface function for ISR) is not executed. Interrupts that are expected to occur at fixed intervals, such as multiple CPU synchronous interrupt, may delay. When executing a command, pay attention to the above.
A VxWorks message may appear on the Telnet tool screen during a Telnet connection to the C Controller module. For messages of VxWorks, refer to the manual for VxWorks, Workbench, or Tornado.
3) When executing the Shell command from Workbench Shell or 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.*1 If VxWorks is rebooted, the C Controller module does not start properly. Reset it in the C Controller module. For resetting, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
* 1 Do not enter characters other than alphanumeric characters or special characters in Shell either since they may be regarded as a control code.
· Execution of command without argument specified If a command that requires an argument is executed without an argument specified, 0 is substituted for the argument. Some commands causes a system error or stop (such as a system watchdog timer error) in the C Controller module. 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.
A - 15
(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. · Decrease the number of files to read · Read the files in several batches.
(6) Precautions for the Wind River Systems product
The C Controller module has an embedded real-time operating system, VxWorks, made and sold by Wind River Systems, Inc. in the United States. We, Mitsubishi, make no warranty for the Wind River Systems product and will not be liable for any problems and damages caused by the Wind River Systems product during use of the C Controller module. For the problems or specifications of the Wind River Systems product, refer to the corresponding manual or consult Wind River Systems, Inc. Contact information is available on the following website. www.windriver.com
A - 16
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 ················································································· A - 3 REVISIONS ····························································································································· A - 4 PRECAUTIONS························································································································ A - 6 INTRODUCTION ·····················································································································A - 17 CONTENTS ····························································································································A - 17 ABOUT MANUALS···················································································································A - 21 MANUAL PAGE ORGANIZATION ·······························································································A - 22 HOW TO USE THIS MANUAL ····································································································A - 23 GENERIC TERMS AND ABBREVIATIONS ···················································································A - 24 GLOSSARY ····························································································································A - 29 PRODUCT ORGANIZATION ······································································································A - 30 PACKING LIST························································································································A - 30
CHAPTER 1 OVERVIEW
1 - 1 to 1 - 4
1.1 Features ····················································································································1 - 3
CHAPTER 2 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE 2 - 1 to 2 - 13
2.1 Development Environment·····························································································2 - 1 2.2 Installation··················································································································2 - 4 2.3 Uninstallation ············································································································ 2 - 12
CHAPTER 3 COMMON UTILITY OPERATIONS
3 - 1 to 3 - 16
3.1 Utility List ···················································································································3 - 1
3.2 Activating Utility ···········································································································3 - 2
3.3 Exiting Utility ···············································································································3 - 3
3.4 Specifying CPU Type ···································································································3 - 4
3.5 Setting Connection Target ·····························································································3 - 5
3.6 Displaying the Help Screen·························································································· 3 - 10
3.7 Checking Version ······································································································ 3 - 13
3.8 Parameter Setting File ································································································ 3 - 14
3.9 Displays on the Title Bar and Status Bar········································································· 3 - 16
A - 17
CHAPTER 4 C CONTROLLER SETTING UTILITY
4 - 1 to 4 - 50
4.1 C Controller Setting Utility Function List ··········································································· 4 - 1
4.2 Module Information Tab································································································ 4 - 2
4.3 Event History Tab ······································································································· 4 - 4
4.4 SRAM Monitoring Tab·································································································· 4 - 8
4.5 Module Monitoring Tab································································································4 - 13
4.6 Online Operation Tab··································································································4 - 21
4.7 System Settings Tab···································································································4 - 30
4.8 Device Settings Tab ···································································································4 - 35
4.9 I/O Assignment Settings Tab ························································································4 - 37
4.10 Multiple CPU Settings Tab ···························································································4 - 41
4.11 Communication Diagnostics Tab ···················································································4 - 45
4.12 System Menu ············································································································4 - 46
4.13 Reading Initial Setting File and Importing Multiple CPU Parameters ·····································4 - 48
4.14 Precautions ··············································································································4 - 50
CHAPTER 5 CC-LINK UTILITY
5 - 1 to 5 - 23
5.1 CC-Link Utility Function List ·························································································· 5 - 1
5.2 Module Information Tab································································································ 5 - 2
5.3 Other Station Monitoring Tab························································································· 5 - 6
5.4 Online Operation Tab··································································································· 5 - 9
5.5 Parameter Settings Tab·······························································································5 - 11
5.6 Target Settings Tab ····································································································5 - 15
5.7 Test Tab ··················································································································5 - 18
5.8 System Menu ············································································································5 - 21
5.9 Precautions ··············································································································5 - 23
CHAPTER 6 MELSECNET/H UTILITY
6 - 1 to 6 - 44
6.1 MELSECNET/H Utility Function List ················································································ 6 - 1
6.2 Module Information Tab································································································ 6 - 2
6.3 Error History Monitoring Tab·························································································· 6 - 9
6.4 Other Station Monitoring Tab························································································6 - 14
6.5 Online Operation Tab··································································································6 - 25
6.6 Parameter Settings Tab·······························································································6 - 27
6.7 Target Settings Tab ····································································································6 - 39
6.8 System menu ············································································································6 - 42
6.9 Precautions ··············································································································6 - 44
A - 18
CHAPTER 7 CC IE CONTROL UTILITY
7 - 1 to 7 - 39
7.1 CC IE Control Utility Function List ···················································································7 - 1
7.2 Module Information Tab ································································································7 - 2
7.3 Diagnostics Result Screen·····························································································7 - 5
7.4 Online Operation Tab ································································································· 7 - 20
7.5 Parameter Settings Tab ······························································································ 7 - 23
7.6 Target Settings Tab···································································································· 7 - 34
7.7 System Menu············································································································ 7 - 37
7.8 Precautions ·············································································································· 7 - 39
CHAPTER 8 DEVICE MONITORING UTILITY
8 - 1 to 8 - 19
8.1 Device Monitoring Utility Function List ··············································································8 - 1
8.2 Batch Monitoring ·········································································································8 - 2
8.3 16-Point Register Monitoring ··························································································8 - 4
8.4 Setting Monitoring Target ······························································································8 - 6
8.5 Setting Device to Be Monitored·······················································································8 - 7
8.6 Changing Word Device Values ·······················································································8 - 8
8.7 Continuously Changing Word Device Values ··································································· 8 - 10
8.8 Tuning On and Off Bit Device ······················································································· 8 - 12
8.9 Changing the Display Format ······················································································· 8 - 14
8.10 Start and Stop Monitoring ···························································································· 8 - 15
8.11 Numerical Pad ·········································································································· 8 - 16
8.12 Other Operations ······································································································· 8 - 17
8.13 Precautions ·············································································································· 8 - 19
CHAPTER 9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 - 1 to 9 - 59
9.1 Outline of Bus Interface Functions···················································································9 - 1
9.2 Bus Interface Function List ····························································································9 - 3
9.3 Programming Procedure ·······························································································9 - 8
9.4 Creating and Compiling a New Project of User Program ······················································9 - 9
9.4.1 9.4.2
For the Q12DCCPU-V ····························································································9 - 9 For the Q06CCPU-V(-B) ······················································································· 9 - 17
9.5 Programming Flow for Bus Interface Functions ································································ 9 - 23
9.6 Precautions for Functions ···························································································· 9 - 26
9.7 Precautions for Program Debugging ·············································································· 9 - 31
9.7.1 9.7.2
For Q12DCCPU-V ······························································································· 9 - 31 For the Q06CCPU-V(-B) ······················································································· 9 - 38
9.8 Program Registration·································································································· 9 - 46
9.9 Creating a Script File "STARTUP.CMD" ········································································· 9 - 51
A - 19
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 Creating a New Project of User Program and Compiling ····················································10 - 5 10.5 MELSEC Data Link Function Programming Flow ······························································10 - 5 10.6 Precautions for the MELSEC Data Link Function ······························································10 - 9 10.7 Precautions for Program Debugging ··············································································10 - 9 10.8 Program Registration ··································································································10 - 9 10.9 Creating a Script File "STARTUP.CMD"··········································································10 - 9 10.10 Channel ···················································································································10 - 9 10.11 Station No. Setting for MELSEC Data Link Functions ······················································ 10 - 10 10.12 Device Types for the MELSEC Data Link Function·························································· 10 - 12 10.13 Accessible Ranges and Devices of the MELSEC Data Link Function ·································· 10 - 17
10.13.1 Access via a bus································································································ 10 - 17 10.13.2 Access via CC-Link ···························································································· 10 - 23 10.13.3 Access via MELSECNET/H·················································································· 10 - 29 10.13.4 Access via CC-Link IE Controller Network ······························································· 10 - 38
CHAPTER 11 PROGRAMMING USING VxWorks API FUNCTIONS
11 - 1 to 11 - 2
CHAPTER 12 SAMPLE PROGRAMS
12 - 1 to 12 - 10
12.1 Procedure for Opening Sample Programs ·······································································12 - 5
CHAPTER 13 EVENT NUMBER LIST
13 - 1 to 13 - 8
APPENDICES
APPX - 1 to APPX - 17
Appendix 1 VxWorks Component List ·············································································· APPX - 1 Appendix 2 Precautions for Program Replacement ··························································· APPX - 17
INDEX
INDEX - 1 to INDEX - 2
A - 20
ABOUT MANUALS
The following manuals are relevant to this product. Order each manual as needed, referring to the table below.
Relevant manuals
Manual name
Manual number (code)
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-VB).
(13JZ17)
(Sold separately)
MELSEC-Q C Controller Module User's Manual
Describes the system configuration, specifications, functions, handling instructions, wiring, troubleshooting, and programming and function of C Controller module (Q24DHCCPU-V, Q24DHCCPU-VG, Q24DHCCPU-LS, Q26DHCCPU-LS, and Q12DCCPU-V (Extended mode)).
SH-081130ENG (13JZ75)
(Sold separately)
Setting/Monitoring Tools for the C Controller Module Version 4 Operating Manual
Describes the system configuration and operation method of Setting/Monitoring Tools for the C Controller Module (SW4PVC-CCPU).
(Sold separately)
SH-081131ENG (13JU76)
CW Workbench Operating Manual
Describes the system configuration, installation/uninstallation, specifications, functions, and troubleshooting of the product.
SH-080982ENG (13JU71)
(Sold separately)
CW-Sim Operating Manual
Describes the system configuration, specifications, functions, and troubleshooting of CW-Sim. (Sold separately)
SH-081159ENG (13JU77)
QCPU User's Manual (Hardware Design, Maintenance and Inspection)
Describes the specifications of CPU modules, power supply modules, base units, extension cables. and memory cards, and others.
SH-080483ENG (13JR73)
(Sold separately)
QCPU User's Manual (Multiple CPU system)
Describes the information on configuring a multiple CPU system: overview, system configuration, I/O numbers, communication between CPU modules, and communication with the I/O modules and intelligent function modules.
SH-080485ENG (13JR75)
(Sold separately)
MELSEC-Q CC-Link System Master/Local Module User's Manual
Describes the system configurations, performance specifications, functions, handling instructions, wiring, and troubleshooting for the CC-Link modules.
(Sold separately)
SH-080394E (13JR64)
Q Corresponding MELSECNET/H Network System Reference Manual (PLC to PLC network)
Describes the PLC-to-PLC network specifications, preparatory procedures and settings, parameter setting, programing, and troubleshooting for the MELSECNET/H network system.
SH-080049 (13JF92)
(Sold separately)
MELSEC-Q CC-Link IE Controller Network Reference Manual
Describes the system configurations, performance specifications, functions, handling instructions, wiring, and troubleshooting for the CC-Link IE Controller Network system.
(Sold separately)
SH-080668ENG (13JV16)
A - 21
MANUAL PAGE ORGANIZATION
Relevant models
Whether the description of the section applies to each model or not is shown in the table.
Chapter
The chapter of the current page can be easily identified by this indication on the right side.
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
5 CC-LINK UTILITY 1 5.6 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
2
a programmable controller CPU other than the control CPU of the target station.
Note that the accesses indicated below does not require the logical station No. settings.
Page 5-17, "5.6 (4) Access that does not require a logical station No. setting"
(1) Precaution for the Target settings tab
Set a programmable controller CPU in "Target CPU"
3
(2) Target settings tab
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
MELSECNET/H UTILITY
Figure 5.10 Target settings tab
Table 5.14 Description of Target settings tab
6
Module information Other station monitoring Online operation Parameter settings Target settings Test
Item Target module
Logical sta. No.
Sta. No. Target CPU Set button
Descriptio n
Select a module to configure.
(Default: "Slot 1")
Specify a logical station No. for the module selected in "Target module". (Default: 65, Setting range: 65 to 239)
7
The logical sta. No. is a logical number to be specified as "Sta. No." in Device monitoring utility and
an user program (MELSEC data link function).
Select a station No. of the CC-Link module controlled by a multiple CPU system.
(Default: 0, Setting range: 0 to 63)
Select a CPU of the access target (CPU No. in a multiple CPU system).
(Default: 1, Setting range: 1 to 4)
Enters the added and changed data (Logical sta. No., Sta. No., and Target CPU) to the Target list.
8
(To the next page)
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
5.6 Target Settings Tab
5 - 15
Reference
The section in this manual or another
relevant manual that can be referred
to is shown after
.
Section and title
The section number and title of the current page can be easily identified.
* The above page illustration is for explanation purpose only, and is different from the actual page.
Q12DCCPU-V
Q12DCCPU-V
Icon Q06CCPU-V
Q06CCPU-V
Q06CCPU-V-B
Description
Q06CCPU-V-B All or part of the description applies each model.
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B The description applies to each model with some restrictions.
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B The description does not apply to each model.
A - 22
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 CHAPTER 1 CHAPTER 2 CHAPTER 3 to CHAPTER 8 CHAPTER 9 to CHAPTER 12 CHAPTER 13
Description Features of SW3PVC-CCPU Operating environment, installing, uninstalling of SW3PVC-CCPU Parameter settings and monitoring using utility
Programming of the C Controller module Event numbers of the C Controller module
Remark
This manual does not explain the features, system configurations, specifications, handling instructions, wiring, or troubleshooting of the C Controller module. For details of the above, refer to C Controller Module User's Manual (Hardware Design, Function Explanation).
A - 23
GENERIC TERMS AND ABBREVIATIONS
Unless otherwise specified, this manual uses the following generic terms and abbreviations to explain the C Controller module.
(1) C Controller module and SW3PVC-CCPU
Generic term/abbreviation
Q12DCCPU-V
Q12DCCPU-V (Basic mode) Q12DCCPU-V (Extended mode) Q06CCPU-V Q06CCPU-V-B Q06CCPU-V(-B) Q24DHCCPU-V
Q24DHCCPU-VG
Q24DHCCPU-LS
Q26DHCCPU-LS
C Controller module SW3PVC-CCPU
SW4PVC-CCPU
Description Abbreviation for the Q12DCCPU-V C Controller module In principle, 'Q12DCCPU-V' indicates Q12DCCPU-V (Basic mode). When the classification is needed for such as comparison with other modes, 'Q12DCCPU-V (Basic mode)' and `Q12DCCPU-V (Extended mode)' are mentioned.
Status that Q12DCCPU-V is initialized with the basic mode
Status that Q12DCCPU-V is initialized with the extended mode For Q12DCCPU-V (Extended mode), refer to the following manual.
MELSEC-Q C Controller Module User's Manual Abbreviation for the Q06CCPU-V C Controller module Abbreviation for the Q06CCPU-V-B C Controller module Generic term for the Q06CCPU-V and Q06CCPU-V-B Abbreviation for the Q24DHCCPU-V C Controller module For Q24DHCCPU-V, refer to the following manual.
MELSEC-Q C Controller Module User's Manual Abbreviation for the Q24DHCCPU-VG C Controller module For Q24DHCCPU-VG, refer to the following manual.
MELSEC-Q C Controller Module User's Manual Abbreviation for the Q24DHCCPU-LS C Controller module For Q24DHCCPU-LS, refer to the following manual.
MELSEC-Q C Controller Module User's Manual Abbreviation for the Q26DHCCPU-LS C Controller module For Q26DHCCPU-LS, refer to the following manual.
MELSEC-Q C Controller Module User's Manual Generic term for the Q12DCCPU-V, Q06CCPU-V, Q06CCPU-V-B, Q24DHCCPU-V, Q24DHCCPU-VG, Q24DHCCPU-LS, and Q26DHCCPU-LS Abbreviation for Setting/Monitoring Tools for the C Controller Module (SW3PVC-CCPUE) Abbreviation for Setting/Monitoring Tools for the C Controller Module (SW4PVC-CCPU-E) For SW4PVC-CCPU, refer to the following manual.
Setting/Monitoring Tools for the C Controller Module Operating Manual
A - 24
(2) CPU modules
Generic term/abbreviation
ACPU
QnACPU QCPU (A mode) Basic model QCPU High Performance model QCPU Process CPU Redundant CPU
Universal model QCPU
QCPU (Q mode) LCPU Motion CPU CPU module Single CPU system Multiple CPU system
Control CPU
Controlled module
Non-controlled module (Non-group module)
Non-control CPU Battery PC CPU module
Description Generic term for the A1NCPU, A0J2HCPU, A1SCPU, A1SHCPU, A1SJCPU, A1SJHCPU, A2CCPU, A2CJCPU, A2NCPU, A2NCPU-S1, A2SCPU, A2SHCPU, 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, Q2ASHCPU-S1, Q3ACPU, Q4ACPU, and Q4ARCPU Generic term for the Q02CPU-A, Q02HCPU-A, and Q06HCPU-A Generic term for the Q00CPU and Q01CPU Generic term for the Q02CPU, Q02HCPU, Q06HCPU, Q12HCPU, and Q25HCPU Generic term for the Q02PHCPU, Q06PHCPU, Q12PHCPU, and Q25PHCPU Generic term for the Q12PRHCPU and Q25PRHCPU Generic term for the Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU, Q50UDEHCPU, Q100UDEHCPU, Q03UDVCPU, Q04UDVCPU, Q06UDVCPU, Q13UDVCPU, and Q26UDVCPU Generic term for the Basic model QCPU, High Performance model QCPU, Process CPU, Redundant CPU, and Universal model QCPU Generic term for the L02CPU and L26CPU-BT Generic term for the Q172CPUN, Q172CPUN-T, Q172HCPU, Q172HCPU-T, Q173CPUN, Q173CPUN-T, Q173HCPU, Q173HCPU-T, Q172DCPU and Q173DCPU Generic term for the C Controller module, QCPU(Q mode), and Motion CPU Control system where the C Controller module is mounted in the CPU slot Control system where multiple CPU modules are mounted on a main base unit CPU module that controls I/O modules and intelligent function modules mounted on the main base unit and extension base units. Example: When CPU No. 2 controls a module mounted in Slot 3, CPU No.2 is the control CPU of the module in Slot 3. I/O module and intelligent function module controlled by a control CPU. Example: When CPU No.2 controls a module mounted in Slot 3, the module in Slot 3 is the controlled module of CPU No.2. I/O module and intelligent function module other than controlled modules. Example: When CPU No. 2 controls a module mounted in Slot 3, the module in the Slot 3 is the non-controlled module of CPU No.1 and 3. CPU module that is not a control CPU. Example: When CPU No. 2 controls the module mounted in Slot 3, the module in Slot 3 is a non-control CPU of CPUs No.1 and No.3. Generic term for the Q6BAT and Q7BAT batteries for CPU module Abbreviation for the MELSEC-Q series PC CPU module manufactured by CONTEC Co., Ltd
A - 25
(3) Network modules and PC boards
Generic term/abbreviation CC-Link module CC-Link/LT module
CC-Link board
CC-Link IE Controller Network module CC-Link IE Controller Network interface board CC-Link IE Field Network master/ local module
MELSECNET/H module
MELSECNET/H interface board
Description Generic term for the QJ61BT11 and QJ61BT11N Generic term for the QJ61CL12 Generic term for the Q81BD-J61BT11 and Q80BD-J61BT11N CC-Link system master/ local interface boards, A80BD-J61BT11 CC-Link system master/local interface board, and A80BD-J61BT13 CC-Link interface board
Generic term for the QJ71GP21-SX and QJ71GP21S-SX
Generic term for the Q80BD-J71GP21-SX and Q80BD-J71GP21S-SX CC-Link IE Controller Network interface boards
Abbreviation for the QJ71GF11-T2 CC-Link IE Field Network master/local module
Generic term for the QJ71LP21-25, QJ71LP21S-25, QJ71LP21G, QJ71LP21GE, QJ72LP25-25, QJ72LP25G, QJ72LP25GE, QJ71BR11, QJ72BR15, and QJ71NT11B Generic term for the Q81BD-J71LP21-25, Q80BD-J71LP21-25, Q80BD-J71LP21G, Q80BD-J71LP21S-25, and Q80BD-J71BR11 MELSECNET/H interface boards
A - 26
(4) Power supply modules and base units
Generic term/abbreviation Q3 B
Q3 SB
Q3 RB
Q3 DB
Q5 B
Q6 B
Q6 RB
QA1S6 B Main base unit Extension base unit Slim type main base unit Redundant power main base unit Redundant power extension base unit Multiple CPU high speed main base unit Base unit Redundant power supply base unit Q series power supply module Slim type power supply module Redundant power supply module Power supply module Extension cable CPU slot
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 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, Universal model QCPU, slim type power supply module, Q series I/O modules, and intelligent function modules can be mounted Generic term for the Q38RB main base unit for redundant power supply system on which the CPU modules, redundant power supply module, Q series I/O modules, and intelligent function modules can be mounted Generic term for the Q35DB, Q38DB, and Q312DB multiple CPU high speed main base unit on which the CPU modules, Q series power supply module, Q series I/O modules, and intelligent function modules can be mounted Generic term for the Q52B and Q55B extension base units on which the Q series I/O modules and intelligent function modules can be mounted Generic term for the Q63B, Q65B, Q68B, and Q612B extension base units on which the Q series power supply modules, Q series I/O modules, and intelligent function modules can be mounted Generic term for the Q68RB extension base unit for redundant power supply system on which the redundant power supply modules, Q series I/O modules, and intelligent function modules can be mounted Generic term for the QA1S65B and QA1S68B extension base units on which the AnS series power supply modules, AnS series I/O modules, and special function modules can be mounted Generic term for the Q3 B, Q3 SB, Q3 RB, and Q3 DB Generic term for the Q5 B, Q6 B, Q6 RB, and QA1S6 B Generic term for the Q3 SB Generic term for the Q3 RB
Generic term for the Q6 RB
Generic term for the Q3 DB
Generic term for the main base unit, extension base unit, slim type main base unit, redundant power main base unit, redundant power extension base unit, and multiple CPU high speed main base unit Generic term for the redundant power main base unit and redundant power extension base unit Generic term for the Q61P-A1, Q61P-A2, Q61P, Q61P-D, Q62P, Q63P, Q64P, and Q64PN power supply modules Generic term for the Q61SP slim type power supply module Generic term for the Q63RP, Q64RP power supply module for redundant power supply system Generic term for the Q series power supply module, slim type power supply module, and redundant power supply module Generic term for the QC05B, QC06B, QC12B, QC30B, QC50B, and QC100B extension cables The slot on the right side of the power supply module on the main base unit
A - 27
(5) Others
Generic term/abbreviation Q series AnS series Ethernet MELSECNET/H GOT GX Works2 GX Developer Windows Vista® or later Windows® 7 or later CW Workbench
Wind River Workbench
Workbench
Tornado
VxWorks
Description Abbreviation for the programmable controllers, MELSEC-Q series Abbreviation for the programmable controllers, compact MELSEC-A series Generic term for the 100BASE-TX and 10BASE-T network systems Generic term for the Q series MELSECNET/H network system Abbreviation for the Mitsubishi Graphic Operation Terminal
Product name of the software package for the MELSEC programmable controllers
Generic term for the Windows Vista®, Windows® 7, Windows® 8, Windows® 8.1, Windows® 10 Generic term for the Windows® 7, Windows® 8, Windows® 8.1, Windows® 10 The abbreviation for the engineering tool for C Controller, CW Workbench Abbreviation for Workbench 2.6.1 Update manufactured by Wind River Systems, Inc. For specifications and inquiries of Wind River Workbench, visit the website of Wind River Systems, Inc.: www.windriver.com Generic term for the CW Workbench and Wind River Workbench Abbreviation for Tornado 2.1.0 for Hitachi SuperH Cumulative patch 1 manufactured by Wind River Systems, Inc. For specifications and inquiries of Tornado, visit the website of Wind River Systems, Inc.: www.windriver.com Product name of the real-time operating system manufactured by Wind River Systems, Inc.
A - 28
GLOSSARY
Definitions of the terms used in this manual are explained below.
Term FTP Telnet CompactFlash card (CF card)
Bus interface functions
MELSEC data link functions
Description FTP is an abbreviation for File Transfer Protocol, which is used to transfer data files. Network protocol, or virtual terminal software, that enables remote login in TCP/IP networks. A storage card regulated by the 'CF+ and CompactFlash Specification' issued by the CompactFlash Association. Functions offered by SW3PVC-CCPU The functions allow input to and output from the I/O modules that are controlled by C Controller modules, access to intelligent function module's buffer memories, and the status reading or control of the C Controller module. Functions offered by SW3PVC-CCPU Communication-protocol-independent and standardized communication library. When creating programs for communication with programmable controller CPUs and C Controller modules, there is no need to consider the hardware or communication protocol of the communication target. The MELSEC data link functions support the following. · Q series bus interface communication · CC-Link communication · MELSECNET/H communication · CC-Link IE Controller Network communication For the Q06CCPU-V-B, The MELSEC data link functions cannot be used.
A - 29
PRODUCT ORGANIZATION
Supported software
SW4PVC-CCPU SW3PVC-CCPU
The following shows the C Controller-compatible software. C Controller
Q12DCCPU-V
"15102" or later*1 Extended mode
Earlier than "15102"*1
Basic mode*2
Q06CCPU-V Q06CCPU-V-B
-
-
PACKING LIST
: 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.
Model name Q12DCCPU-V Q06CCPU-V Q06CCPU-V-B*1
SW3PVC-CCPU-E
The following is the product line of the C Controller module.
Product name Q12DCCPU-V C Controller module (Endian format (memory layout): Little endian) Battery (Q6BAT) Q06CCPU-V C Controller module (Endian format (memory layout): Big endian) Battery (Q6BAT) Q06CCPU-V-B C Controller module (Endian format (memory layout): Big endian) Battery (Q6BAT) Setting/Monitoring Tools for the C Controller Module (Volume license product)
(CD-ROM) Software License Agreement Software Registration Form License Agreement Industrial development tool purchasing form (Wind River Workbench) Industrial development tool purchasing form (Tornado)
* 1 Production of the Q06CCPU-V-B was discontinued in November, 2015.
Quantity
1
1 1 1 1 1
1
1 1 1
1
A - 30
Memo
A - 31
1 OVERVIEW
CHAPTER 1 OVERVIEW
This manual explains the parameter setting, monitoring, and programming required for operation of the C Controller module.
For the features, system configuration, specifications, handling, wiring, and troubleshooting of the C Controller module, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
(1) Manuals relevant to the C Controller module
The following list shows the manuals relevant to the C Controller module.
For details such as a manual No, refer to "ABOUT MANUALS" section in this manual.
(
Page A-21)
Table 1.1 Manuals relevant to the C Controller module
Purpose
Checking the part names and specifications of the C Controller module Checking the specifications and method of selecting, mounting, and installing the power supply module and base units Checking the connecting methods of the power supply module, base units, and I/O module
Hardware
(Packed)
C Controller Module User's
Manual (Hardware)
Hardware Design
C Controller Module User's
Manual (Hardware Design, Function Explanation)
Utility Operation
C Controller Module User's Manual (Utility
Operation, Programming)
Maintenance and
Inspection
Multiple CPU System
QCPU User's Manual
(Hardware Design,
Maintenance and Inspection)
QCPU User's Manual (Multiple
CPU System)
Outline
Details
*1
Details
Outline
Details
*1
Checking the functions of the C Controller module
Details
*1
Configuring a single CPU system (Start-up procedure and I/O No. assignment)
Details
*1
Configuring a multiple CPU system (Start-up procedure and I/O No. assignment)
Outline *1
Details
(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
1 - 1
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
1 OVERVIEW 1 Table 1.1 Manuals relevant to the C Controller module (continued)
Purpose
Hardware (Packed)
Hardware Design
Utility Operation
Maintenance and
Inspection
Multiple CPU System
C Controller Module User's
Manual (Hardware)
C Controller Module User's
Manual (Hardware Design, Function Explanation)
C Controller Module User's Manual (Utility
Operation, Programming)
QCPU User's Manual
(Hardware Design,
Maintenance and Inspection)
QCPU User's Manual (Multiple
CPU System)
2
Parameter settings and monitoring
Details
*2
3
Programming
Details
*1
Troubleshooting and checking error
codes
Details
*1
4
Checking Event No.
Details
*1
* 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
5
* 2 For Q24DHCCPU-V, Q24DHCCPU-VG, Q24DHCCPU-LS, Q26DHCCPU-LS, or Q12DCCPU-V
(Extended mode), refer to the following manual.
Setting/Monitoring Tools for the C Controller Module Operating Manual
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
1 - 2
1 OVERVIEW
1.1 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.
· CC-Link modules · MELSECNET/H modules · CC-Link IE Controller Network modules The setting items and functionalities vary depending on the model of the C Controller module. For the functions of each utility, refer to the following.
Page 3-1, "3.1 Utility List"
Figure 1.1 Utility screens
1 - 3
1.1 Features
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
1 OVERVIEW 1
(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
2
C or C++ language.
Providing a development group that covers all the developing processes from
"software development", "system diagnostics", "testing", to "manufacturing",
Workbench allows users to shorten development period and improve the quality.
ICE is not required since debugging is available from a development environment
(personal computer) by connecting it to the C Controller module by Ethernet.
3
CW Workbench is an OEM product of Wind River Systems, Inc. The product has
only basic functions required for user program development, such as coding,
building, and debugging, as a subset product of Wind River Workbench3.2.
4
Efficient development with an integrated development
environment (Workbench)
C Controller module
5
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
Development environment (personal computer)
6
Figure 1.2 Development with Workbench
(b) For the Q06CCPU-V(-B)
Tornado, an integrated development environment, provides efficient development
of user programs by using C or C++ language.
ICE is not required since debugging is available from a development environment
(personal computer) by connecting it to the C Controller module by Ethernet.
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
1.1 Features
1 - 4
2 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
CHAPTER 2 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
2.1 Development Environment
Item Personal computer
CPU Memory
Operating system (English version)
Development tool
Q12DCCPU-V
Q06CCPU-V, Q06CCPU-V-B Display Disk space Disk drive Ethernet card, board
Table 2.1 Product requirements for SW3PVC-CCPU Description
PC-AT compatible machine running the following operating systems For writing user programs into a CompactFlash card, a personal computer supporting CompactFlash card is required.
Page 2-2, "Table 2.2 Requirements for operating system and personal computer"
·Windows 10 (Home, Pro, Enterprise, Education) ·Windows 8.1, Windows 8.1 (Pro, Enterprise) ·Windows 8, Windows 8 (Pro, Enterprise) ·Windows 7 (Starter, Home Premium, Professional, Ultimate, Enterprise)*1 ·Windows Vista® (Home Basic, Home Premium, Ultimate, Business, Enterprise)*1 ·Windows XP® (Professional SP2 or later)*1 ·Windows 2000 (Professional SP4 or later)
CW Workbench For product requirements for CW Workbench, refer to the CW Workbench Operating Manual. Wind River Workbench 2.6.1 Update For product requirements for Wind River Workbench, refer to the manual of Wind River Workbench. Tornado 2.1.0 for Hitachi SuperH Cumulative patch 1 For product requirements for Tornado, refer to the manual of Tornado. Resolution 1024 768 dots or more 250MB or more CD-ROM disk drive 10BASE-T, 100BASE-TX
* 1: 64-bit version is not supported.
2 - 1
2.1 Development Environment
OVERVIEW
2 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE 1
Table 2.2 Requirements for operating system and personal computer
Operating system
Personal computer
CPU
Memory
Windows 10 (Home, Pro, Enterprise, Education) Windows 8.1, Windows 8.1 (Pro, Enterprise) Windows 8, Windows 8 (Pro, Enterprise)
Intel® CoreTM2 Duo
1GB or more
1GHz or more
2
Windows 7 (Starter, Home Premium, Professional, Ultimate, Enterprise)
1GB or more
Windows Vista® (Home Basic, Home Premium, Ultimate, Business, Enterprise) Windows XP® (Professional SP2) Windows 2000 (Professional SP4)
Pentium® 1GHz or more
512MB or more 256MB or more
3
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
4
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
2.1 Development Environment
2 - 2
2 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.
3. When the following functions are used, this product may not run properly. · Application start-up in Windows compatibility mode · Fast user switching · Remote desktop · Windows XP Mode · Sleep mode · Windows Touch or Touch · Modern UI · Client Hyper-V
4. In the following cases, the screen of this product may not work properly. · The size of the text and/or other items on the screen are changed to values other than default values (such as 96 DPI, 100%, and 9 pt). · The multi-display is set.
5. Use the product as a standard user or an administrator for Windows 10, Windows8.1, Windows 8, Windows 7, and Windows Vista.
2 - 3
2.1 Development Environment
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
2 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
1 2.2 Installation
(1) Preparation for installation
Before installation, perform the following.
1) Logon as a user with Administrator attribute.
2
2) Remove all the applications in the start up, restart Windows®, and logon again
as a user with Administrator attribute.
3) Change settings not to allow any update program of OS, such as Windows®
Update, or other manufacturer's software, such as Java, to start automatically.
The installer may not operate normally if an update program is activated.
3 POINT
1. Installation of SW3PVC-CCPU by overwriting is available only onto the same
version.
When installing any other version, uninstall the existing one before
installation.
2. When installing SW3PVC-CCPU by overwriting, file backups are not
4
necessary for the files stored by utility including a parameter setting file.
Files stored in the "C:\MELSEC\CCPU\Param" folder will not be removed
when installing SW3PVC-CCPU by overwriting.
3. If the installation failed, uninstall the SW3PVC-CCPU, restart Windows®, and
reinstall it.
4. Do not execute more than one "Setup.exe" in the CD-ROM at the same time. Doing so may cause the installation not to complete normally.
5
To reinstall the SW3PVC-CCPU, uninstall it and restart Windows®.
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
2.2 Installation
2 - 4
2 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 2-5, "2.2 (2) (a) Selection operation during installation"
4) In Windows® XP, Windows Vista®, or Windows® 7 or later, if the Windows® Firewall was not turned on during the installation, turn it on, referring to the following. Page 2-7, "2.2 (3) Operation after installation"
(a) Selection operation during installation
User Account Control (For Windows Vista®)
Click "Allow".
User Account Control (Windows® 7 or later) Click the YES button.
(To the next page)
2 - 5
2.2 Installation
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
2 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE 1 Selecting installation destination
Specify the folder of installation destination.
·When installation destination is "C:\MELSEC", click the Next> button.
2
·When installation destination is other than "C:\MELSEC", click the Browse button and specify the folder of installation destination.
Windows® Firewall setting (for Windows® XP, Windows Vista®, or Windows® 7 or later) To connect the development environment (personal computer) to the C
3
Controller module, turn on the Windows® Firewall.
·For a quick setup, click the YES button. The connection will be automatically enabled.
However, if the Windows® Firewall is set up not to allow exceptional
connections, manually set the Windows® Firewall, referring to the following.
Page 2-7, "2.2 (3) Operation after installation"
4
·To set it after installation, click the NO button. Be sure to refer to the following before manually setting the Windows® Firewall.
Page 2-7, "2.2 (3) Operation after installation" End of InstallShield Wizard
5
Restart Windows® at the end of the installation. (1) Eject the CD-ROM from the CD-ROM drive. (2) Select "Yes, I want to restart my computer now." and click the Finish
button. Windows® is restarted and now SW3PVC-CCPU is operable.
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
2.2 Installation
2 - 6
2 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.
1 Open the Control Panel of Windows®, click the following option for the operating system, and then click Windows® Firewall.
Table 2.3 Option
Operating system Windows® XP Windows Vista®
Security Center Security
Option
1
2 Open the <<General>> tab, and clear the following checkbox.
Table 2.4 Checkbox
Operating system Windows® XP Windows Vista®
Option Don't allow exceptions Block all programs
3 Open the <<Exceptions>> tab. Check if all of the SW3PVC-CCPU utilities are displayed on the screen.
(To the next page)
2 - 7
2.2 Installation
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
2 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
1
(From the previous page)
4 If no utility is displayed or any one is missing, click the
Add Program button.
Select a utility of SW3PVC-CCPU, and click the OK button. Repeat this operation until all utilities of SW3PVC-CCPU
2
are added.
3
5 Select all utilities of SW3PVC-CCPU, and click the OK button.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
5
(Completed)
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
2.2 Installation
2 - 8
2 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. 1 Open the Control Panel of Windows®, and click "System and Security". 2 Select "Allow a program through Windows Firewall" and click the Change settings button.
3 If the left dialog box appears, click the Yes button.
4 Check if all utilities of SW3PVC-CCPU are displayed on the screen.
(To the next page)
2 - 9
2.2 Installation
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
2 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
1
(From the previous page)
5 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 Add button.
2
Repeat this operation until all utilities of SW3PVC-CCPU
are added.
3
6 Select the "Name" and "Public" checkboxes for all utilities of SW3PVC-CCPU, and click the OK button.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
5
7 Click "Check firewall status".
6
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
7
(To the next page)
8
DEVICE MONITORING UTILITY
2.2 Installation
2 - 10
2 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
(From the previous page)
8 Click "Turn Windows Firewall on or off".
9 If the left dialog box appears, click the Yes button.
10 Check that the "Block all incoming connections, including those in the list of allowed programs" checkbox is not selected, and click the OK button. If it is selected, clear the checkbox and click the OK button.
(Completed)
2 - 11
2.2 Installation
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
2 INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
1 2.3 Uninstallation
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Preparation for uninstallation
2
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
3
displayed as image names in the process of task manager.
If displayed as image names, terminate the process before uninstalling again.
· CCIECUtl.exe
· CClnkUtl.exe
· CCpuUtl.exe
· MnethUtl.exe
4
· RtDvmonUtl.exe
2. Uninstallation must be started from Control Panel.
3. To reinstall SW PVC-CCPU, uninstall it, restart Windows®, and then
reinstall.
4. Do not terminate uninstallation during processing.
If terminated, redo the uninstallation all over again.
5
If the uninstallation fails after terminating the uninstallation, reinstall the
software and then uninstall it again.
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
2.3 Uninstallation
2 - 12
2 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 Windows® 2000 Professional Windows® XP Windows Vista® or later
Screen Add/Remove Programs Add or Remove Programs Uninstall or Change a Program
3) Select SW3PVC-CCPU and activate the uninstaller.
Figure 2.1 Add or Remove Programs
4) Perform the uninstallation, following the instructions provided by the uninstaller.
2 - 13
2.3 Uninstallation
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
3 COMMON UTILITY OPERATIONS 1
CHAPTER 3 COMMON UTILITY OPERATIONS
3.1 Utility List
2
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Table 3.1 Utilities in SW3PVC-CCPU
Utility
Description
Availability
Q12DCCPU Q06CCPU
-V
-V
Q06CCPU -V-B
Reference page
Functions of C Controller setting utility are as follows.
3
·Displays the module information (LED status, switch status,
and error information and others) of a C Controller module
C Controller setting utility
·Displays event history ·Monitors states (input, output, and buffer memories) of each
Page 4-1
module mounted with the C Controller module
·Sets parameters
CC-Link utility
·Operates the C Controller module online Performs parameter setting, network monitoring, etc. of the CC-Link module controlled by the C Controller module.
4
Page 5-1
MELSECNET/H utility
Performs parameter setting, network monitoring, etc. of the MELSECNET/H module controlled by the C Controller module.
Page 6-1
CC IE Control utility
Device monitoring utility
Performs parameter setting, network monitoring, etc. of the CC-Link IE Controller Network module controlled by the C Controller module. Monitors and tests device data of the programmable controller CPU.
Page 7-1
5
Page 8-1
: Available, : Available but partially restricted, : N/A
Remark
For functions added to the C Controller module and SW3PVC-CCPU and function versions and serial No.s of the CPU module that support the added functions,
6
refer to the C Controller Module User's Manual (Hardware Design, Function
Explanation).
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
3.1 Utility List
3 - 1
3 COMMON UTILITY OPERATIONS
3.2 Activating Utility
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
To activate a utility, select the menu in [MELSEC] [C Controller] from "Start" of Windows®*1.
* 1 [Start screen] [All apps] or [Start] [All Programs]
Activates Bus Interface Function HELP Activates C Controller setting utility Activates CC IE Control utility Activates CC-Link utility Activates Device monitoring utility Activates MELSEC Data Link Function HELP Activates MELSECNET/H utility
Figure 3.1 Items added to the Start menu
3 - 2
3.2 Activating Utility
OVERVIEW
3 COMMON UTILITY OPERATIONS 1 3.3 Exiting Utility
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Utility other than Device monitoring utility
2
To exit utility other than Device monitoring utility, click the Exit button at the bottom right of the screen.
3
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
4
Click.
Figure 3.2 Exiting C Controller setting utility
5
(2) Device monitoring utility
To exit Device monitoring utility, select [Menu] [Exit] on the menu bar.
As a dialog box appears, click the Yes button.
6
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
Click.
7
Figure 3.3 Exiting Device monitoring utility
8
DEVICE MONITORING UTILITY
3.3 Exiting Utility
3 - 3
3 COMMON UTILITY OPERATIONS
3.4 Specifying CPU Type
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Select the C Controller module for parameter setting and monitoring in utility other than Device monitoring utility.
Item CPU type
CPU type fixed
OK button Cancel button
Figure 3.4 Specify CPU type screen
Table 3.2 Description of the Specify CPU type screen Description
Specifies a C Controller module to which parameters are set or to be monitored. (Default: "Q12DCCPU-V") The specified CPU type is fixed and this screen will not be displayed on and after next utility operation. 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. (Default: Deselected (CPU type not fixed)) Sets the selected C Controller module as the CPU type and closes this screen.
Closes this screen without changing the CPU type.
Remark
1. Changing CPU type
Select [Specify CPU type] from the system menu and change the CPU type.
(
Page 4-46, Section 4.12, Page 5-21, Section 5.8, Page 6-42, Section
6.8, Page 7-37, Section 7.7)
2. When writing parameters or performing communication processing such as
monitoring to any other CPU type, change the CPU type on this screen in
advance.
For the following communication processing, CPU type change is available in
the processing.
· Connection target settings
· Parameter read
3 - 4
3.4 Specifying CPU Type
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
3 COMMON UTILITY OPERATIONS 1 3.5 Setting Connection Target
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Connect an development environment (personal computer) and the C Controller module.
2
(1) Operating procedure
1 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.
3
(Completed)
2 Select the "Write authority" check box and enter the
following.
User name: target Password: password
4
When the account of the C Controller module has been
changed, enter the user name and password currently set
to the account.
3 Check the connectivity with the C Controller by clicking the
Test button.
5
Note that in startup or after reset of the C Controller
module, the timing to click the button differs according to
the script file "STARTUP.CMD" usage.
The timing to click the Test button;
When executing "STARTUP.CMD": After the RUN LED finished flashing
6
When not executing "STARTUP.CMD":
15 seconds after the startup or reset of the module.
4 Clicking the Connect button establishes a connection
with the C Controller module, and the screen shown on the
left appears.
7
Click the Yes button when reading out parameters from the C Controller module.
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
3.5 Setting Connection Target
3 - 5
3 COMMON UTILITY OPERATIONS
Remark
1. To read parameters from the C Controller module online, use the following drive.
Table 3.3 Drives used for reading parameters
Model
Q12DCCPU-V with serial No. (first 5 digits) "12042" or later
Q12DCCPU-V with serial No. (first 5 digits) "12041" or earlier Q06CCPU-V(-B)
Drive The drive in which parameters of the operating C Controller module are stored (Standard RAM or CompactFlash card)
Standard RAM
Standard ROM
2. If a utility communication error occurred after connecting, restart monitoring
by clicking the Start monitoring button or set the connection target again in Connection settings.
3 - 6
3.5 Setting Connection Target
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
3 COMMON UTILITY OPERATIONS 1 (2) Connection settings screen
2
Item
Target module
Write authority User name Password
Test button Clear history button Detailed settings button Connect button Exit button
Figure 3.5 Connection settings screen
Table 3.4 Description of the Connection settings screen
Description
3
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)
·"192.168.3.3 (Default)"
·"Offline" (other than Device monitoring utility)
When entering a host name, do not set multiple IP addresses under the same host name. (If set, a
communication is performed with the host whose IP address is last acquired.)
4
Select the checkbox when writing parameters to the C Controller module.
For "User name" and "password", enter the user name and password set to the account of the C
Controller.
Parameters cannot be written to the C Controller module if these are not set.
These items cannot be set when:
·"Offline" is selected for "Target module" or
·This screen has been opened from Device monitoring utility. For restrictions on accessing to a login user, refer to the C Controller Module User's Manual
5
(Hardware Design, Function Explanation).
Checks the connectivity with the C Controller module specified in "Target module".
Clears the connection target log of "Target module".
Opens the Detailed settings screen. (
Page 3-8, Section 3.5 (2) (a))
Establishes a connection with the C Controller module specified in "Target module".
When "Write authority" is selected, the C Controller module authenticates the account.
6
Closes the Connection settings screen without changing the connection target.
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
3.5 Setting Connection Target
3 - 7
3 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 Communication check time
Retry count
OK button Cancel button Default button
Description Set a communication check time in Ethernet communication between the development environment (personal computer) and C Controller module. (Unit: seconds) (Default: 10, Setting range: 1 to 360) Set the number of retries in Ethernet communication between the development environment (personal computer) and C Controller module. (Default: 2, Setting range: 0 to 9)
Enables the current settings and closes the Detailed settings screen.
Closes the Detailed settings screen without enabling the settings.
Sets the values entered in "Communication check time" and "Retry count" back to default.
POINT
Communication errors may occur in Ethernet communication between the development environment (personal computer) and the C Controller module depending on the line status. When a communication error has occurred, increase the setting value for "Communication check time" and/or "Retry count".
3 - 8
3.5 Setting Connection Target
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
3 COMMON UTILITY OPERATIONS 1
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
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.
· For other than Device monitoring utility
Click the Connection settings button at the bottom left of the screen.
· For Device monitoring utility
3
Select [Setting] [Connection settings] from the menu bar.
3. The connection target when other utility is started from the system menu.
Connection is established with the same C Controller module.
4. How to check the connection target and user name
Check on the title bar and status bar. (
Page 3-16, Section 3.9)
5. When the C Controller module specified in the CPU type on utility (other than
4
Device monitoring utility) and the connection target C Controller module are
not the same type.
Change the setting to the C Controller module that is to be connected as the
CPU type, and then set it in Connection settings.
For changing the CPU type, refer to the following.
Page 3-4, "3.4 Specifying CPU Type"
5
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
3.5 Setting Connection Target
3 - 9
3 COMMON UTILITY OPERATIONS
3.6 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. Alternatively, press the F1 key while the utility is active.
Click. Figure 3.7 Starting Help of C Controller setting utility
(2) Device monitoring utility
To display the Help screen of Device monitoring utility, select [Help] [Help] from the menu bar. Alternatively, press the F1 key while the utility is active.
Click. Figure 3.8 Starting Help of Device monitoring utility
3 - 10
3.6 Displaying the Help Screen
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
3 COMMON UTILITY OPERATIONS 1
(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
2
Windows® 7
3
Link
Figure 3.9 When the Help screen does not appear on Windows® 7
4
(a) When a development environment (personal computer) is connectable to the internet:
1) Click the link shown on the screen above to display Microsoft® Help and
Support article ID No.917607 on the web browser.
5
2) Install WinHlp32.exe according to the instruction provided in the article ID No.
917607.
(b) When a development environment (personal computer) is not connectable to the internet:
1) Use another personal computer connectable to the internet and go to the
address below on the web browser to display Microsoft® Help and Support
6
article ID No.917607.
support.microsoft.com/kb/917607
2) Install WinHlp32.exe according to the instruction in the article ID No. 917607.
3) Transfer WinHlp32.exe to the development environment (personal computer)
and install it.
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
3.6 Displaying the Help Screen
3 - 11
3 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. If an error occurs in the C Controller module (host CPU), the Help screen can
be displayed from the System information screen of the C Controller setting
utility. (
Page 4-17, Section 4.5 (3))
3 - 12
3.6 Displaying the Help Screen
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
3 COMMON UTILITY OPERATIONS 1 3.7 Checking Version
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Utilities other than Device monitoring utility
2
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 5-21, Section 5.8
MELSECNET/H utility .........
Page 6-42, Section 6.8
CC IE Control utility .............
Page 7-37, Section 7.7
3
(2) Device monitoring utility
To check the version of Device monitoring utility:
(a) Operation
Click [Help] [Version] from the menu bar to open the Version information screen.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
5
Click. Figure 3.10 Checking version
(b) Version information screen
6
Figure 3.11 Version information screen
7
Table 3.6 Version information
Item Device monitoring utility
OK button
Description Displays the update date of Device monitoring utility. Closes the version information screen.
8
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
3.7 Checking Version
3 - 13
3 COMMON UTILITY OPERATIONS
3.8 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.
1) Click the Load File button to load a parameter setting file. Click the Save File button to save a parameter setting file.
Click. Figure 3.12 Loading/saving parameter setting file
2) Load/save the settings.
Item Look in (Save in) File name
Open button
( Save button)
Cancel button
Figure 3.13 Open screen
Table 3.7 Description of the Open and Save As screen Description
Specify the location where the parameter setting file is to be loaded (or saved). Enter the file name to be loaded (or saved).
Loads (or saves) the file specified in "File name".
Closes the screen without loading (or saving).
3 - 14
3.8 Parameter Setting File
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
3 COMMON UTILITY OPERATIONS 1
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.
2
Table 3.8 Extensions for parameter setting file
Utility
Extension for parameter setting file
C Controller setting utility
cst
CC-Link utility
ccl
MELSECNET/H utility
mnh
CC IE Control utility
mng
3. The standard folder, where utilities other than Device monitoring utility save
3
parameter setting files, is "C:\MELSEC\CCPU\Param". (When SW3PVC-
CCPU has been installed in "C:\MELSEC")
4. Double-clicking any saved parameter setting file (*.cst, *.ccl, *.mnh, or *.mng) starts the corresponding utility with the saved parameter setting loaded.
5. When a parameter setting file is loaded, utility will be in the following status.
Table 3.9 Utility status
4
Item
Status
CPU type
Changed back to the one set when the parameter setting file was saved.
Disconnected and monitoring is stopped.
Connection
To restart monitoring, click the Start monitoring button or set data
again in Connection settings.
5
(2) Utilizing existing parameter settings in the parameter setting file
Multiple modules can be used under the same parameter setting by loading a existing parameter file into multiple development environments (personal computers).
6
Remark
Parameter settings can be utilized without a parameter setting file with the following procedure.
1. Set parameters in utility other than Device monitoring utility.
2. Open the Connection settings screen and connect to the module where the
parameters are written.
7
3. Write the parameters to the C Controller module by clicking the Write button in the <<Online operation>> tab of each utility.
4. By repeating steps 2 and 3, the same parameter setting can be set to multiple modules.
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
3.8 Parameter Setting File
3 - 15
3 COMMON UTILITY OPERATIONS
3.9 Displays on the Title Bar and Status Bar
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
1
2
3
4
5
Figure 3.14 Title bar and status bar
Table 3.10 Display on the title bar and status bar
No.
Display
1 Utility name
2
IP address or host address of the connection target C Controller module "Offiline" is displayed when in offline.
3
Name of a parameter setting file "New" is displayed when no parameter setting file has been loaded or saved.
4 CPU type specified in the Specify CPU type screen.
5 User name who has been logged in to the C Controller module.
3 - 16
3.9 Displays on the Title Bar and Status Bar
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
4 C CONTROLLER SETTING UTILITY 1
CHAPTER 4 C CONTROLLER SETTING UTILITY
4.1 C Controller Setting Utility Function List
2
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Table 4.1 C Controller setting utility function list
Name
Description
Availability
Q12DCCPU Q06CCPU
-V
-V
Q06CCPU -V-B
Reference page
Specify CPU type
Specifies a C Controller module to which parameters are set or to be monitored.
Page 3-4
3
Connection settings
Sets parameters to a C Controller module which is to be connected with this utility.
Page 3-5
Parameter setting file saving/loading
Module information
Event history
Saves parameters set in C Controller setting utility into a file, or loads the file. Displays the LED and switch states, error information, and drive information of the C Controller module. Displays and saves the event history of a C Controller module.
Page 3-14
Page 4-2
Page 4-4
4
SRAM monitoring Module monitoring Online operation
Monitors the battery-backed-up RAM, changes and saves data. Performs the following operations to the modules installed on slots. ·Monitors inputs (X), outputs(Y), buffer memories, and CPU
shared memory. ·Executes forced output of outputs (Y) and forced write to
buffer memories and CPU shared memory. ·Displays an error code of the latest error occurred in an
intelligent function module. ·Displays the information of the C Controller system. Performs the following operations to the C Controller module. ·Reads, writes, and verifies parameters or remotely operates
the module. ·Sets IP address, clock, the MD function, and Option settings. For the Q06CCPU-V-B, the MD function setting is not available.
Page 4-8
Page 4-13
5
Page 4-21
6
System settings
Sets parameters (System settings) of a C Controller module.
Page 4-30
Device setting
Sets parameters (Device settings) of a C Controller module.
Page 4-35
I/O assignment Multiple CPU settings
Sets parameters (I/O assignment settings) of a C Controller module. Sets parameters (Multiple CPU settings) of a C Controller module.
Page 4-37
7
Page 4-41
Communication diagnostics
Diagnoses whether communication with another CPU is available when the C Controller module is in a multiple CPU configuration.
Page 4-45
: Available, : Available but partially restricted, : N/A
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4.1 C Controller Setting Utility Function List
4 - 1
4 C CONTROLLER SETTING UTILITY
4.2 Module Information Tab
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
The Module information tab displays the LED status, switch status, error information, and drive information of the C Controller module.
(1) Precautions for the Module information tab
(a) Switching a tab during monitoring Monitoring stops when a tab is switched to another during monitoring. Monitoring resumes when the <<Module monitoring>> tab is opened next time.
(b) When a utility communication error has occurred When a utility communication error has occurred during connection, click the
Start monitoring button or set the connection target again in the Connection settings so that the communication can be restarted.
(c) During reset Communications are not available while the C Controller module is being reset. Start communications after the reset is complete.
(2) Module information tab
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Figure 4.1 Module information tab
Table 4.2 Description of the Module information tab
Module information Event history SRAM monitoring Module monitoring Online operation System settings
Item Module information
LED information
Description
Reference page
Displays the information of the C Controller module.
Displays the LED states of the C Controller module.
Note that the CH3 SD/RD indication for the Q12DCCPU-V and the CH2 SD/RD
*1
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
Manual (Hardware Design, Function Explanation)
(To the next page)
4 - 2
4.2 Module Information Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
4 C CONTROLLER SETTING UTILITY
1
Table 4.2 Description of the Module information tab (continued)
Module information Event history SRAM monitoring Module monitoring Online operation System settings
Item
Description
Reference page
Module information Toggle switch information
Displays the RUN/STOP/MODE switch and RESET/SELECT switch states of the C Controller module.
*1
2
7-segment LED information
Displays the 7-segment LED status of the C Controller module. For the Q06CCPU-V(-B), this indication is disabled.
*1
CPU operating status
Displays the operating status ("RUN", "STOP", "PAUSE") of the C Controller module, including remote operation.
*1
Parameter boot drive
Displays the drive in which the parameters of the operating C Controller module are stored.
3
Error code
Displays the latest error code among stop/continue errors currently occurring.
Help in this utility
Start monitoring or Stop monitoring button
Starts or stops monitoring the C Controller module. "*" flashes in the upper right of the button during monitoring. These buttons are disabled in the offline status.
When a stop or continue error has occurred in the C Controller module,
Error information
corresponding error item for stop or continue error changes from (white) to
*2
4
(red).
Clears a continuation error detected in a C Controller module when appropriate
actions were taken for the cause of the error and the problem was resolved.
Error clear button
This button cannot be clicked when: ·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.
5
Drive information
Displays drive information of the C Controller module.
Standard RAM information
Displays its size, used space, and free space of a standard ROM.*3
*4
For the Q06CCPU-V(-B), this information is not displayed.
Standard ROM information
Displays its size, used space, and free space of a standard ROM.*3
*4
For the Q12DCCPU-V, this information is not displayed.
When a CompactFlash card is installed, entire space, used space, and free space
of the CompactFlash card are displayed.*3
6
CF card information
"Empty" is displayed for the following cases.
*4
·A CompactFlash card is not installed when the Q12DCCPU-V or Q06CCPU-V is
used.
·When the Q06CCPU-V-B is used.
Update button
Updates either of the "Standard RAM information" or "Standard ROM information", and "CF card information".
* 1 For part names and functions of the C Controller module, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
7
* 2 For corrective actions for errors, refer to the C Controller Module User's Manual (Hardware Design,
Function Explanation).
* 3 "Used space" indication of the "Standard RAM information", "Standard ROM information", and "CF
card information" includes the space used by the file system.
* 4 For data and size that can be stored, refer to the C Controller Module User's Manual (Hardware
Design, Function Explanation).
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4.2 Module Information Tab
4 - 3
4 C CONTROLLER SETTING UTILITY
4.3 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
when the Update button is clicked.
(b) Event history displays the data registered by QBF_RegistEventLog function
The event history displays the data registered by QBF_RegistEventLog function.
(
Page 9-3, Section 9.2)
(c) 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.
(d) During reset Communications are not available while the C Controller module is being reset. Start communications after the reset is complete.
(e) Precautions for using QBF_RegistEventLog function
If the same data as in "source flag" (
Page 4-7, "Table 4.5 Source flag") is
specified into the argument SrcStr[] of the QBF_RegistEventLog function, it will be
difficult to differentiate the data in the <<Event history>> tab.
Do not specify the same character string as in "source flag".
The event occurrence can be located in the following ways. · Checking "Event type" of the Detailed event information screen Page 4-6, "4.3 (3) Detailed event information screen" · Checking the event history file Page 4-7, "4.3 (4) Specifications of the Event history file"
4 - 4
4.3 Event History Tab
4 C CONTROLLER SETTING UTILITY 1 (2) Event history tab The events occurred in the C Controller module are displayed or saved in this tab.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
3
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
Figure 4.2 Event history tab
4
Table 4.3 Description of the Event history tab
Module information Event history SRAM monitoring Module monitoring Online operation System settings
Item
Event history
Date Time Source Event No. Event information*1 Update button Clear button Save event history button
Description
Reference page
Displays the history up to 512 events occurred in the C Controller module.
5
If 513 or more events have occurred, a new event is inserted by deleting the oldest one. The event history is displayed in reverse chronological order.
Page 4-6 Page 13-1
Double-clicking an event opens the Detailed event information screen.
Displays the date of event occurrence.
Page 13-1
Displays the time of event occurrence.
Page 13-1
Displays the source of event occurrence. (Example "MQbfDrv" is displayed when a event occurred in the bus interface drive (bus part).)
Page 13-1
6
Displays the No. of event occurred.
Page 13-1
Displays event information of the event occurred.
Page 13-1
Acquires and displays the latest event history in the C Controller module.
Deletes the event history in the C Controller module.
Saves the displayed event history into a CSV format file.
Page 4-7
* 1 Displaying all event information at once may not be available when too many events occurred.
7
To check all data of the event information, double-click the event to display the Detailed event
information screen and confirm the information.
8
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4.3 Event History Tab
4 - 5
4 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
Item
Description
Date, Time, Source, Event No., Event info
Event type
Displays the Detailed event information.
Displays the type of the event.
Indication
Description
System (Err.)
The event is a C Controller system error.
System (Warning)
The event is a C Controller system warning.
System (Info.)
The event is a C Controller system information.
Application
The event is registered from a user program (QBF_RegistEventLog function).
OK button
Displays the Detailed event information screen. Displays the next latest detailed event information than the currently displayed one.
Previous button Next button
Clicking the Previous button while the latest detailed event information is displayed, a message appears and the oldest detailed event information is displayed. Displays the next oldest detailed event information than the currently displayed one.
Clicking the Next button while the oldest detailed event information is displayed, a message appears and the latest detailed event information is displayed.
Help button
Starts a Help of C Controller setting utility and displays the information of the event.
Reference page
Page 4-5 Page 13-1
Page 13-1
4 - 6
4.3 Event History Tab
4 C CONTROLLER SETTING UTILITY 1 (4) Specifications of the Event history file A file format can be selected in "Files of type" on the following screen.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
Figure 4.4 Save As screen
3
To use the text data of the Event history file in a user program etc., select "EventLog File(*.csv)" when saving. To use them on Microsoft® Excel etc., select "EventLog File[Form2](*.csv)" when saving.
When "EventLog File(*.csv)" is selected
When "EventLog File[Form2](*.csv)" is selected
4
Figure 4.5 Example of Event history files
(a) Source flag
5
The source file (the third column) of the event history file indicates the following
information.
Table 4.5 Source flag
Source flag
Source*1
Data type
0000
Character string specified by the QBF_RegistEventLog function.
An event registered from QBF_RegistEventLog function.
6
0001
MQbfDrv
Bus interface driver (bus part) related
0002
MXwdkDrv
Bus interface driver (system part) related
0003
MUtlIfQbf
Utility communication interface (bus interface part) related
0004 0005
MUtlIfMd MUtlIfCom
Utility communication interface (MELSEC
communication part) related Utility communication interface (common part)
7
related
0006
MMain
C Controller module main body part related
0007
MFDrv
Flash ROM and standard RAM related
0008
MCfDrv
CompactFlash card related
0009
MEtherDrv
Ethernet related
* 1 Corresponding to "Source" in the Event history tab.
8
Remark
The folder to save the event history file is "C:\MELSEC\CCPU\Param" by default (when SW3PVC-CCPU has been installed in "C:\MELSEC").
4.3 Event History Tab
4 - 7
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4 C CONTROLLER SETTING UTILITY
4.4 SRAM Monitoring Tab
WARNING
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
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
a development environment (personal computer) to the C Controller module, configure an interlock circuit in the user program to ensure that the entire system will always operate safely. (2) Changing the operating status (3) Operating from the development environment (personal computer) Especially, in the case of a control from an external device to a remote C Controller module, immediate action cannot be taken for a problem on the C Controller due to a communication failure. To prevent this, configure an interlock circuit in the user program, and determine corrective actions to be taken between the external device and C Controller module in case of a communication failure.
(1) Precaution for SRAM monitoring tab
The SRAM monitoring tab is updated when the Start monitoring button is clicked by acquiring data only in the display area from the battery-backed-up RAM of the C Controller module.
(2) SRAM monitoring tab
Monitoring of battery-backed-up RAM and changing/saving data can be performed on this screen.
SRAM monitoring
Figure 4.6 SRAM monitoring tab
4 - 8
4.4 SRAM Monitoring Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
4 C CONTROLLER SETTING UTILITY 1
Remark
The battery-backed-up RAM data, which were entered, cleared, or restored from
the SRAM monitoring screen, can be accessed by the following functions. (
Page 9-3, Section 9.2) · QBF_ReadSRAM function
2
· QBF_WriteSRAM function
Table 4.6 Description of the SRAM monitoring tab
Module information Event history SRAM monitoring Module monitoring Online operation System settings
3
Item SRAM monitoring
Offset
Start monitoring or Stop monitoring button Clear button Numeric format Display format
Data restoration button
Save data button
Description
Monitors battery-backed-up RAM data. Double-click one of the data being monitored, or select one and then press the
Reference page
[Enter] key to enter data. (
Page 4-10)
Set the start address of the data to be monitored. (In increments of 0x10)
4
When a value is set other than in increments of 0x10, the fraction is dropped at the
start of monitoring.
When a value outside the setting range is set, it will automatically be corrected to a
value within the range, at the start of monitoring.
(Default: 0, Setting range: 0 to 1FFFF)
Starts or stops monitoring the C Controller module.
"*" flashes in the upper right of the button during monitoring.
5
These buttons are disabled in the offline status.
Changes all battery-backed-up RAM data to 0.
Select a value format to display in the SRAM monitoring. (Default: "HEX.") Select a display format of SRAM monitoring.*1(Default: "8 bits")
Restores the buttery-backed-up RAM data, which were saved by the Save data
button, to the C Controller module. Monitoring is stopped from the time the Data restoration button is pressed until
Page 4-11
6
restoration is completed.
Saves all battery-backed-up RAM data.
Monitoring stops from when the Save data button is clicked until all data are
Page 4-12
saved.
* 1 Endian format (memory layout) of the C Controller module is applied when "16 bits" or "32 bits" is
selected. Example) Display format when "32 bits" is selected
7
Memory status
SRAM monitoring screen display
Address
+00 +01 +02 +03
Address
+00
+00
Display data 12 34 56 78
Display data 78 56 34 12 12 34 56 78
For the
For the
Q12DCCPU-V Q06CCPU-V-B
and Q06CCPU-V
8
Figure 4.7 Display example when "32 bits" is selected
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4.4 SRAM Monitoring Tab
4 - 9
4 C CONTROLLER SETTING UTILITY
(3) Data settings screen
Data can be entered into the battery-backed-up RAM from this screen.
Item
Input format
Target address Input data OK button Cancel button
Target address
Input data
Figure 4.8 Data settings screen
Table 4.7 Description of the Data settings screen
Description
Select a format of the value to be entered in "Input data". (Default: "Numeric format" of the screen which opened this screen.) Displays the address of the battery-backed-up RAM where the data are to be entered. Enter data to be entered into the battery-backed-up RAM. Writes data entered in "Input data" to the battery-backed-up RAM. Closes the Data settings screen without writing the input data to the batterybacked-up RAM.
Reference page
4 - 10
4.4 SRAM Monitoring Tab
4 C CONTROLLER SETTING UTILITY 1
(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.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
3
Figure 4.9 Restore data dialog box
(a) Restorable file specification
Extension Capacity
Item
Table 4.8 Restorable file specification
Description
4
bin
The capacity of the destination battery-backed-up RAM in the C Controller module,
or less
5
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
4.4 SRAM Monitoring Tab
4 - 11
4 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 program, select "SRAM Data File(*.csv)" when saving. To use them on Microsoft® Excel etc., select "SRAM Data File[Form2](*.csv)" when saving.
When "SRAM Data File(*.csv)" is selected
When "SRAM Data File[Form2](*.csv)" is selected
Figure 4.11 Example of save files
(b) Specifications of the binary format · The extension is "bin". · When data are saved in the binary format, the battery-backed-up RAM data are saved as is.
Remark The standard folder to store the battery-backed-up RAM data is "C:\MELSEC\CCPU\Param" by default (when SW3PVC-CCPU has been installed in "C:\MELSEC").
4 - 12
4.4 SRAM Monitoring Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
4 C CONTROLLER SETTING UTILITY 1 4.5 Module Monitoring Tab
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
WARNING For the following controls, configure an interlock circuit in the user
2
program to ensure that the entire system will always operate safely.
(1) Changing data of the running C Controller module by connecting
a development environment (personal computer) to the C
Controller module, configure an interlock circuit in the user
program to ensure that the entire system will always operate
safely.
3
(2) Changing the operating status
(3) Operating from the development environment (personal
computer)
Especially, in the case of a control from an external device to a
remote C Controller module, immediate action cannot be taken for a
problem on the C Controller due to a communication failure.
4
To prevent this, configure an interlock circuit in the user program,
and determine corrective actions to be taken between the external
device and C Controller module in case of a communication failure.
(1) Precautions for Module monitoring tab
5
(a) Switching a tab during monitoring
Monitoring stops when the tab is switched to another during monitoring.
Monitoring resumes when the <<Module monitoring>> tab is opened next time.
(b) When a utility communication error has occurred
When a utility communication error has occurred during connection, click the
Start monitoring button or set the connection target again in the Connection
6
settings so that the communication can be restarted.
(c) During reset Communications are not available while the C Controller module is being reset. Start communications after the reset is complete.
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
4.5 Module Monitoring Tab
4 - 13
4 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" field of Parameter settings (I/O assignment settings) does not affect the target. Note that tests can be performed for only the modules that are controlled by the C Controller module.
(e) Monitoring of CC-Link module When monitoring or forced write to buffer memory has been performed to the CCLink module where the block data assurance per station function is enabled, cyclic data will be automatically refreshed.
However, data are automatically refreshed only when monitoring or forced write to buffer memory has been performed within the range set in "Station information settings" for the master station. The range set in "Station information settings" can be confirmed by "Slave station offset, size information" (buffer memory address: 3E0H to 5DFH) of the CC-Link module. For details of the block data assurance per station function, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
The following area will not be refreshed when monitoring or forced write to buffer memory has been performed.
· The write (send) area of link refresh devices (buffer memory) will not be refreshed when monitoring has been performed.
· The read (receive) area of link refresh devices (buffer memory) will not be refreshed when forced write to buffer memory has been performed.
(f) Precautions for changing module configuration When module configuration is changed after starting C Controller setting utility, any of the following operation updates the module configuration information. · Set the Connection settings.
· Click the Start monitoring button in the <<Module monitoring >> tab.
· Click the System info button in the <<Module monitoring >> tab.
4 - 14
4.5 Module Monitoring Tab
4 C CONTROLLER SETTING UTILITY 1
(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.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
3
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
4
Figure 4.12 Module monitoring tab
Table 4.9 Description of the Module monitoring tab
Module information Event history SRAM monitoring Module monitoring Online operation System settings
Item
Description
Reference
5
page
Specify a slot No. to be monitored.
This item cannot be changed during monitoring. Stop monitoring for changing.
Slot No.
In a multiple CPU system, the CPU shared memory can be monitored by setting the slot No. where a CPU module is mounted.
Start I/O No.
"CPU" can be set only in a multiple CPU system configuration.
(Default: 0, Setting range: "CPU", 0 to 63)
6
Displays the start I/O No. of the module installed to the slot specified in "Slot No.".
Displays the CPU No. that controls a module installed in the slot specified in "Slot
No.".
Control CPU
Displays " " (blank) when the slot where a CPU module is installed, or the slot to which "CPU (Empty)" is set as I/O assignment, is specified in "Slot No.".
("*" appears on the right side of the CPU No. of the C Controller module when it is
connected with C Controller setting utility and is a control CPU.) Displays the I/O points and type of the module if the slot where other than a CPU
7
module is installed is specified in "Slot No.".
Within parentheses, the value set in "points" in Parameter settings (I/O assignment
settings) is displayed.
Type
Displays CPU No. and "connected CPU" when the slot where a CPU module (own station) is mounted is specified in "Slot No.".
Displays CPU No. when the slot where a CPU module (another CPU) is mounted is
specified in "Slot No.".
8
Displays "CPU (Empty)" when the slot to which "CPU (Empty)" is set as I/O
assignment is specified in "Slot No.".
(To the next page)
4.5 Module Monitoring Tab
4 - 15
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4 C CONTROLLER SETTING UTILITY
Table 4.9 Description of the Module monitoring tab (continued)
Module information Event history SRAM monitoring Module monitoring Online operation System settings
Item Start monitoring or Stop monitoring button System info button Input*1
Output*1
Buffer memory, CPU shared memory
Address format
Offset
Latest error Numeric format Display format
Description
Reference page
Starts or stops monitoring the C Controller module.
"*" flashes in the upper right of the button during monitoring.
These buttons are disabled in the offline status.
Displays the System information screen. This button is disabled during monitoring.
Page 4-17
Monitors the input (X) of the module specified in "Slot No.". 0: OFF 1: ON
Monitors the output (Y) of the module specified in "Slot No.".
0: OFF
1: ON
Double-clicking this item enables forced output using the data setting screen.
(
Page 4-10, Section 4.4 (3))
Specifying an intelligent function module in "Slot No." enables monitoring of the
buffer memory.
Specifying a CPU module in "Slot No." enables monitoring of the CPU shared
memory.
Double-clicking this item enables forced output by using the data setting screen.
(
Page 4-10, Section 4.4 (3))
(Default: the value to be monitored, Setting range: see below)
·"Display format" is "16 bits": -32768 to 32767 (0H to FFFFH) ·"Display format" is "32 bits": -2147483648 to 2147483647 (0H to FFFFFFFFH)
Select the numeric format for "Address" (Default: "HEX.")
Select an address of the buffer memory or CPU shared memory to be monitored. (Default: 0, Setting range: see below)
·Buffer memory: 0 or more (
Manual for the CPU used)
·CPU shared memory: 0 to FFFH, 2710H to 5F0FH
For the Q06CCPU-V(-B), the range from 2710H to 5F0FH are not available.
C Controller Module User's Manual (Hardware Design, Function Explanation)
Displays an error code of the latest error occurred in an intelligent function module.
"No error" is displayed when the error code is "0".
"-" is displayed when monitoring other than an intelligent function module.
For error codes of the intelligent function module, refer to the manual for each
module.
Select a numeric format for the buffer memory or CPU shared memory.
(Default: "HEX.")
Select a display format for the buffer memory or CPU shared memory. (Default: "16 bits") * 1 The displayed input and output data covers the points assigned in Parameter settings (I/O
assignment settings) for the module mounted to the specified slot No.
4 - 16
4.5 Module Monitoring Tab
4 C CONTROLLER SETTING UTILITY 1 (3) System information screen Information of the C Controller system can be displayed on this screen.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
Item CPU status
CPU module Status Switch
Error code
Present error Date Time
3
System configuration
4
Figure 4.13 System information screen
Table 4.10 Description of the System information screen
Description
Reference manual
5
Displays the status of CPU modules that configure the C Controller system.
Double-clicking the C Controller module or programmable controller CPU with an
error opens the Error details screen. (
Page 4-19, Section 4.5 (3) (a))
Displays CPU No. of the CPU module.
"Empty" is displayed when no CPU module is mounted.
(Display: "No.1" to "No.4", "Empty")
Displays the operation status of the CPU module.
6
(Display: "RUN", "STOP", "PAUSE", and "RESET")
Displays the switch status of the CPU module.
(Display: "RUN", "STOP", and "RESET")
Displays an error code of the first stop error and continuous error occurred in the
CPU module.
The other errors can be confirmed on the Module information tab (
Page 4-2,
Section 4.2) or the Event history tab (
Page 4-4, Section 4.3).
7
Displays an message corresponding to the "Error code"
Displays the date of the error occurrence.
Displays the time of the error occurrence.
(To the next page)
8
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4.5 Module Monitoring Tab
4 - 17
4 C CONTROLLER SETTING UTILITY
Table 4.10 Description of the System information screen (continued)
CPU status
Item
Error code help button
System configuration
Slot
Type
Series Model name Points Start I/O No. Control CPU Serial No. Ver. Product No.
Save system information button Select button Exit button
Description
Selecting a C Controller module (own station) and clicking the Error code help button starts Help of C Controller setting utility, which displays help information of a current error. This button is available only when the C Controller module (own station) is selected. For errors of programmable controller CPU(s), refer to the manual for the programmable controller CPU used. Displays the information of CPU modules that configure the C Controller system. Double-clicking a module (or selecting a module and pressing the [Enter] key) updates the display to information of the selected module, and closes the System information screen. Note that CPU module selection is not allowed for a single CPU system. Displays the "slot No." of the module. In the parenthesis, module's base No. and mounting position in the base unit are displayed. Displays the module type. (Display: "Empty", "Input", "Hi.Input", "Output", "I/O mix", "Intelli.", "Interrupt", and "CPU") Displays the series name of the module. (Display: "Q" (fixed)) Displays the model name of the module. Displays the I/O points of the module. (Display: 0, 16, 32, 48, 64, 128, 256, 512, 1024) Displays the I/O No. of the module. (Display: 0000 to 0FF0, 3E00 to 3E30) Displays the CPU No. of the control CPU of the module. (Display: "No.1" to "No.4") Displays the serial No. of the module. Displays the function version of the module. Displays the product No. of the C Controller module. When the model does not have product No. indication, "-" is displayed. For the Q06CCPU-V(-B), this item is not displayed. Saves the displayed information of the C Controller system into the system information file.
Selecting a module and clicking the Select button changes the display to information of the selected module, and closes the System information screen.
Closes the System information screen.
Reference page
Page 4-20 Page 4-15
Remark
The information displayed on the System information screen is based on the configuration when the screen was opened. To update the information, close and reopen the System information screen.
4 - 18
4.5 Module Monitoring Tab
4 C CONTROLLER SETTING UTILITY 1 (a) Error details screen
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
Item Common error information Individual error information
Figure 4.14 Error details screen
3
Table 4.11 Description of the Error details screen
Description Displays common information corresponding to the error code. Displays individual information corresponding to the error code.
Reference *1 *1
* 1 For errors of the C Controller module, refer to the C Controller Module User's Manual (Hardware
Design, Function Explanation).
For errors of the programmable controller CPU, refer to the manual for the programmable
4
controller CPU used.
5
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
4.5 Module Monitoring Tab
4 - 19
4 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)" when saving. To use them on Microsoft® Excel etc., select "System Info File[Form2](*.csv)" when saving.
When "System Info File(*.csv)" is selected
When "System Info File[Form2](*.csv)" is selected
Figure 4.16 Example of system information save files
Remark The standard folder of the system information save file is "C:\MELSEC\CCPU\Param" (when SW3PVC-CCPU has been installed in "C:\MELSEC").
4 - 20
4.5 Module Monitoring Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
4 C CONTROLLER SETTING UTILITY 1 4.6 Online Operation Tab
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Precautions for the Online operation tab
2
(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.
(b) During reset
3
Communications are not available while the C Controller module is being reset.
Start communications after the reset is complete.
(c) The drive to which parameters are written
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
4
If the parameters are written to different drives, those of the drive, which include C
Controller setting parameters, will take effect.
(2) Online operation tab
Read, write, and verification of parameters, and remote operation, clock setting, and
IP address setting for the C Controller module are available in this tab.
5
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
6
Operation
7
Target CPU Figure 4.17 Online operation tab
8
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4.6 Online Operation Tab
4 - 21
4 C CONTROLLER SETTING UTILITY
Table 4.12 Description of the Online operation tab
Module information Event history SRAM monitoring Module monitoring Online operation System settings
Item
Target drive Read parameters Read button
Write parameters Write button
Description
Set a target drive for reading, writing, or verifying parameters. This setting is not available for the Q06CCPU-V(-B). (Default: Parameter boot drive)
Reads parameters from the C Controller module.
Writes parameters set in C Controller setting utility into the C Controller module. The written parameters take effect when the C Controller module is powered off and then on or is reset. Parameters can be written only when "Write authority" is selected in Connection settings. If "Write authority" is not selected, select it in the Connection settings
Reference page
*1
screen before writing parameters. (
Page 3-5, Section 3.5)
"Clear all parameters of all drives prior to writing." checkbox (for the Q12DCCPU-V) "Clear all parameters before writing." checkbox (for the Q06CCPU-V(-B)) Verify parameters Verify button Remote operation Operation
Target CPU
Execute button
Detail button
If the Write button is clicked with this checkbox selected, all parameters (including the following) of all drives will be cleared before parameter writing. ·CC-Link module parameters ·MELSECNET/H module parameters ·CC-Link IE Controller Network module parameters ·Intelligent function module parameters Cross-check the parameters set in the C Controller module and in C Controller setting utility. The result is displayed in a message box. Remotely controls a C Controller module or programmable controller CPU. Select a remote operation. (Default: "RUN") Select a CPU that is remote operation target. To remotely operate a own station in a multiple CPU system configuration, select "connected CPU". Selecting a CPU No. causes an error. (Default: "connected CPU") Executes a specified remote operation. For precautions for the remote RESET operation during writing a user file, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation). Opens the Detailed settings screen. Sets the IP address, clock, MD function, and Option settings. Detailed settings is available only when "Write authority" is checked in Connection settings. If "Write authority" is not checked, check it in Connection settings and
*2 *2 *2 *2
Page 4-23
then set the Detailed settings. (
Page 3-5, Section 3.5)
For the Q06CCPU-V-B, the MD function setting is not available.
* 1 For the drives to which parameters can be written (user memory), refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
* 2 For remote operation, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
4 - 22
4.6 Online Operation Tab
4 C CONTROLLER SETTING UTILITY 1
(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.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
3
Figure 4.18 Detailed settings screen
4
Table 4.13 Description of the Detailed settings screen
IP address Clock MD function Option
Item <<IP address>> tab <<Clock>> tab
<<MD function>> tab
<<Option>> tab Exit button
Description
Reference page
Set the IP address for the C Controller module. Set the clock of the C Controller module.
Page 4-24
Page 4-27
5
Set the timeout value of the communications made by the MELSEC data link
function.
Page 4-28
For the Q06CCPU-V-B, this item is not available.
Set priority of the processing for communications with the C Controller module.
Page 4-28
Closes the Detailed settings screen.
6
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
4.6 Online Operation Tab
4 - 23
4 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
Item IP address settings CH1
IP address Subnet mask Default gateway
IP address settings CH2 IP address Subnet mask Default gateway
Set button
Description
Set whether to enable or disable the 10BASE-T/100BASE-TX interface of CH1. CH1 and CH2 cannot be set to blank (disable) simultaneously. (Default: checked (enable)) Set the IP address for the 10BASE-T/100BASE-TX interface of CH1.
(Default: 192.168.3.3, Setting range:
Page 4-25, Section 4.6 (3) (a) 1))
Set the subnet mask for the 10BASE-T/100BASE-TX interface of CH1.
(Default: 255.255.255.0, Setting range:
Page 4-25, Section 4.6 (3) (a) 1))
Set the IP address of the default gateway for the 10BASE-T/100BASE-TX interface of CH1.
(Default: blank, Setting range:
Page 4-25, Section 4.6 (3) (a) 1))
Set whether to enable or disable the 10BASE-T/100BASE-TX interface for CH2.
For the Q06CCPU-V(-B), this item is not available.
CH1 and CH2 cannot be set to blank (disable) simultaneously.
(Default: not checked (enable))
Set the IP address for the 10BASE-T/100BASE-TX interface of CH2.
(Default: blank, Setting range:
Page 4-25, Section 4.6 (3) (a) 1))
Set the IP address for the default gateway for the 10BASE-T/100BASE-TX
interface of CH2.
(Default: blank, Setting range:
Page 4-25, Section 4.6 (3) (a) 1))
Set the IP address for the default gateway for the 10BASE-T/100BASE-TX interface of CH2.
(Default: blank, Setting range:
Page 4-25, Section 4.6 (3) (a) 1))
Writes the settings of "IP address settings CH1" and "IP address settings CH2" into
the C Controller module.
Reference page
4 - 24
4.6 Online Operation Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
4 C CONTROLLER SETTING UTILITY
1
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)
2
Table 4.15 IP address setting range
Class A B C
High-order bits of IP address 0 10
110
IP address range 0.0.0.0 to 126.255.255.255 (excluding 0.x.x.x)
128.0.0.0 to 191.255.255.255 192.0.0.0 to 223.255.255.255
Note that the IP address must satisfy all the conditions indicated in the following table.
3
Table 4.16 Conditions of the IP address
Conditions
·Bits in the network address portion(*1) are not set with only 0s or only 1s.
·Bits in the host portion(*1) are not set with only 0s or only 1s.
·Network address of CH1 and CH2 are different.
* 1 The network address portion is the potion where the subnet mask is corresponding to
4
bit 1 in a IP address.
The host portion is the potion where the subnet mask is corresponding to bit 0 in a IP
address. Example)
IP address Subnet mask (Binary)
Network address portion
Host portion
192. 11111111.
168. 11111111.
3. 11111111.
3 00000000
5
· Subnet mask setting range Note that the subnet mask must satisfy all the conditions indicated in the following table.
Table 4.17 Conditions of the subnet mask
Conditions
·Set with only 1s including the most significant bit. 0 is not inserted between 1s.
Setting example
6
255.255.0.0
·The least significant bit is 0.
· Update of the settings
The settings made in this tab are displayed by reading out from the C
Controller module when this tab is opened.
If failed to read out the settings, an error message appears and the
7
settings will be back to default.
· Setting IP address back to the initialization status or factory setting
To set the IP address of the C Controller module back to the initialization
status or factory setting, execute the "Default IP setting" mode by the
hardware self-diagnostic function.
For details of the hardware self-diagnostic function, refer to the C Controller Module User's Manual (Hardware Design, Function
8
Explanation).
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4.6 Online Operation Tab
4 - 25
4 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.
4 - 26
4.6 Online Operation Tab
4 C CONTROLLER SETTING UTILITY 1 (b) Clock tab Clock data of the C Controller can be set in this tab.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
3
Figure 4.20 Clock tab
Table 4.18 Description of the Clock tab
IP address Clock MD function Option
4
Item
Description
Reference page
Set the clock of the C Controller module and displays it.
Date*1
This setting is disabled when "Synchronize clock with CPU No.1" is checked.
*2
(Setting range:2000/1/1 to 2099/12/31)
Time*1
Set the clock of the C Controller module and displays it.
This setting is disabled when "Synchronize clock with CPU No.1" is checked.
*2
5
(Setting range: 00:00:00 to 23:59:59)
Clock synchronization function
Set the multiple CPU clock synchronization function of the C Controller module. For the Q06CCPU-V(-B), this setting is not available.
Set whether to enable or disable the multiple CPU clock synchronization function of
the C Controller module.
When the checkbox is checked, the clock of the C Controller module synchronizes
with the CPU No.1 in the multiple CPU system.
Synchronize clock with CPU No.1 This item cannot be set when the connected C Controller module is in a single
*2
6
CPU system or is CPU No. 1 in a multiple CPU system.
The setting takes effect when the C Controller module is powered off and then on
or is reset.
(Default: Selected (synchronized))
Set button
Writes the "Date" and "Clock" data into the C Controller module.
* 1 The clock data are displayed by reading from the C Controller module when this tab is opened. When failed to read the data, an error message appears and the clock data of a personal computer
7
is displayed.
* 2 For the clock function, refer to the C Controller Module User's Manual (Hardware Design, Function
Explanation).
1) Precautions for the clock setting
When "Synchronize clock with CPU No.1" is disabled (deselected), power off
and then on or reset the C Controller module before setting "Date" and "Time". Set "Date" and "Time" after powering off and then on or resetting the C
8
Controller module.
4.6 Online Operation Tab
4 - 27
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4 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
IP address Clock MD function Option
Item
Description
MD function timeout value
Q series bus interface (Channel No.12) MELSECNET/H (Channel No. 51 to 54)
CC-Link (Channel No.81 to 88)
CC-Link IE Controller Network (Channel No. 151 to 154) Default button Set button
Set the timeout value for the communication made by the MELSEC data link function. Default value is recommended to use unless any problem, such as too late response from the MD function, is concerned. Change the timeout time value from the default in the above case. For details of precautions for the MELSEC data link function, refer to the following.
Page 10-5, Section 10.5 Set the timeout value for the communication on the Q series bus interface (Channel No.12). (In units of seconds) (Default: 15, Setting range: 1 to 360) Set the timeout value for the communication on the MELSECNET/H (Channel No.51 to 54). (In units of seconds) (Default: 15, Setting range: 1 to 360) Set the timeout value for the communication on the CC-Link (Channel No.81 to 88). (In units of seconds) (Default: 30, Setting range: 1 to 360) Set the timeout value for the communication on the CC-Link IE Controller Network (Channel No. 151 to 154). (In units of seconds) (Default: 15, Setting range: 1 to 360)
Change the settings back to default.
Write the "MD function timeout value" data into the C Controller module. The timeout value takes effect after powering off and on or resetting the C Controller module.
Reference page
4 - 28
4.6 Online Operation Tab
4 C CONTROLLER SETTING UTILITY 1 (d) Option tab The priority of processing for communications with the C Controller module can be set in this tab.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
3
Figure 4.22 Option tab
Table 4.20 Description of the Option tab
4
IP address Clock MD function Option
Item
Description
Reference page
SW3PVC-CCPU communication
Set the processing priority for communications with the C Controller module.
setting
The smaller the value, the higher the priority. Conversely, the larger the value, the
lower the priority.
"Priority" setting may affect the communication between each utility and a C
5
Controller module or behavior of the user program.
Priority
·Priority for utility........
Page 4-29, Section 4.6 (3) (d) 1)
·Priority for user program...
Page 9-26, Section 9.6
(Default: 99, Setting range: 99 to 255)
Default button
Changed the settings back to default.
Set button
Write the "Priority" data into the C Controller module. The "Priority" takes effect after powering off and on or resetting the C Controller
6
module.
1) "Priority" for "SW3PVC-CCPU communication setting"
· The default setting can be used for normal system operation.
· Change the "Priority" value when the default value may affect the behavior
of user programs. Note that changing "Priority" value may cause timeout in a communication
7
between utility and the C Controller module.
8
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4.6 Online Operation Tab
4 - 29
4 C CONTROLLER SETTING UTILITY
4.7 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. For the CPU module No.2 and later, utilize the parameters set on the CPU No.1. For the multiple CPU parameter, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
(2) System settings tab
Figure 4.23 System settings tab
Table 4.21 Description of the System settings tab
Module information Event history SRAM monitoring Module monitoring Online operation System settings
Item Points occupied by empty slot Remote reset
Description
Reference page
Set the points to each empty slot of the main base unit and extension base unit.
In a multiple CPU, the settings for each CPU module must be identical.
(Default: 16 points)
Set whether to allow remote reset of the C Controller module.
(Default: not checked (not allowed))
(To the next page)
4 - 30
4.7 System Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
4 C CONTROLLER SETTING UTILITY
1
Table 4.21 Description of the System settings tab (continued)
Module information Event history SRAM monitoring Module monitoring Online operation System settings
Item Output mode at STOP to RUN
Description
Reference page
Select the output (Y) status in the case where the C Controller module is switched from STOP to RUN, either from "Previous state" or "Reset output (Y)".
2
(Default: "Previous state")
Intelligent function module settings
Clicking the Interrupt event setting button opens the Intelligent function module interrupt event settings screen.
Page 4-33
Reads the Initial settings of intelligent function module.
Initial settings of intelligent function The Initial settings are written to the C Controller module along with other
module
parameters. Subsequently, they are written to the buffer memory of the intelligent function module when the bus interface driver starts up.
3
Load initial setting file button
Loads the Initial settings of intelligent function module from a project file of GX Developer.
Page 4-48
Setting list
Displays "I/O address", "Module name", and "Initial setting" loaded by clicking the Load initial setting file button.
Clear button Default button WDT (Watchdog timer) setting
Deletes the information displayed in the setting list.
Change the settings back to default. Set the time of the system watchdog timer. (Default: 1000, Setting range: 20 to 2000)
4
*1
Select desired error detection.
"Battery check"
Error check
"Fuse blown check"
"Module verification"
(Default: all checked (detect errors)) Set whether to continue or stop operation of the C Controller when an error is
5
Operation mode at the time of error detected in "Fuse blown" or "Module verify error"
(Default: Stop)
Set whether to synchronize the startup of the bus interface driver with that of the
intelligent function module.
Check the checkbox when making the startup of the C Controller module
Module synchronization
synchronized with that of the intelligent function module (positioning module). When not setting "Module synchronization", interlocks must be provided between
6
the C Controller module and intelligent function module.
(Default: checked (synchronize))
Built-in Ethernet port open settings Enable MELSOFT connection
Set this for communication with peripheral devices through Ethernet. This setting is not available for the following: ·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. (Default: not checked (disable))
*1
7
* 1 For the system watchdog timer and communication with peripheral devices through Ethernet, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
(To the next page)
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4.7 System Settings Tab
4 - 31
4 C CONTROLLER SETTING UTILITY
Table 4.21 Description of the System settings tab (continued)
Module information Event history SRAM monitoring Module monitoring Online operation System settings
Item Event history registration settings
Do not register system (information) event details.
Description
Set whether to register the event history data. This setting is not available for the following: ·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. Events of System (Err.) and System (Warning) are registered to the event history regardless of this setting. If this is selected, System (Info.) events, such as clock data setting or correction, will not be registered to the event history. Therefore, if System (Info.) events have occurred frequently, overwriting and deletion of System (Err.) or System (Warning) events can be prevented. (Default: not checked (not register))
Reference page
Page 13-1
4 - 32
4.7 System Settings Tab
OVERVIEW
4 C CONTROLLER SETTING UTILITY 1
(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.
For interrupt events from the intelligent function module, refer to the C Controller
2
Module User's Manual (Hardware Design, Function Explanation).
3
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
Figure 4.24 Intelligent function module interrupt event settings screen
4
Table 4.22 Description of the Intelligent function module interrupt event settings screen
Item Interrupt event start No. Number of interrupt events Start I/O No.
Description
Set the start No. of the interrupt event. (Default: blank, Setting range: 50 to 255) Set the No. of the interrupt events. (Default: blank, Setting range: 1 to 16) Set the start I/O No. of the intelligent function module. (Default: blank, Setting range: 0000 to 0FF, 3E00 to 3E30)
Reference page
5
Start SI No.
Set the SI No. (Interrupt event No. intelligent function module. (Default: blank, Setting range: 0 to 15)
Page 4-34, Section 4.7 (3) (a)) of the
Check button
Checks whether the settings are correct. Saves the settings and closes the Intelligent function module interrupt event
6
End button
settings screen.
Cancel button
Closes the Intelligent function module interrupt event settings screen without saving the settings.
7
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
4.7 System Settings Tab
4 - 33
4 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
16 to 49
50 to 255
Interrupt factor
1st point
2nd point
3rd point
4th point
5th point
6th point
7th point
Interrupt by interrupt module
8th point 9th point
10th point
11th point
12th point
13th point
14th point
15th point
16th point
Not used
Intelligent function module interrupt
Using parameters, set which intelligent function module uses the No.
4 - 34
4.7 System Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
4 C CONTROLLER SETTING UTILITY 1 4.8 Device Settings Tab
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Parameters (device settings) of the C Controller module can be set in this tab. Set whether to enable the device function or the points of the devices used.
2
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
3
(1) Device settings tab
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
5
Figure 4.25 Device settings tab
Table 4.24 Description of the Device settings tab
Device settings I/O assignment settings Multiple CPU settings Communication diagnostics
6
Item
Description
Reference page
Set whether to use the device function or not.
(Default: not checked (Do not use the device function.))
When using the device function, the device points can be changed in 16-point units
Use device function
within the ranges shown below. Enter a value for each "Dev. point" in the number
format specified in the "Dig." field.
*1
7
Description
Sym.
Dig.
Default
Setting range
Internal relay
M
10
8K
0 to 60K
Data register
D
10
12K
0 to 4086K
Device total
Displays the total size of the devices in K bytes.*2
Word device
Displays the total size of the word devices in K bytes.*2
Bit device
Displays the total size of the bit devices in K bytes.*2
Default button
Changes the settings to default values.
8
* 1 For the device function, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
* 2 The total size is displayed as a value rounded up to the nearest integer. (Example: When the total size is 0.1KB, "1" is displayed before KB.)
4.8 Device Settings Tab
4 - 35
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4 C CONTROLLER SETTING UTILITY
Remark Special relays (SM) and special registers (SD) can be used regardless of the above setting.
4 - 36
4.8 Device Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
4 C CONTROLLER SETTING UTILITY 1 4.9 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
2
installed.
For the I/O assignment, refer to the C Controller Module User's Manual (Hardware Design,
Function Explanation).
(1) Precautions for the I/O assignment settings tab
(a) Multiple CPU system configuration
3
Set the multiple CPU parameter on the CPU No. 1.
For the CPU module No.2 and later, utilize the parameters set on the CPU No.1.
For the multiple CPU parameter, refer to the C Controller Module User's Manual
(Hardware Design, Function Explanation).
(2) I/O assignment settings tab
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
6
Figure 4.26 I/O assignment settings tab
Table 4.25 Description of the I/O assignment settings tab
Device settings I/O assignment settings Multiple CPU settings Communication diagnostics
7
Item I/O assignment
Slot
Description
Reference page
I/O assignment setting.
In a multiple CPU system, the settings for each CPU module must be identical.
Displays "slot No." of the module. In the parenthesis, module's base No. and
mounting position in the base unit are displayed.
8 (To the next page)
4.9 I/O Assignment Settings Tab
4 - 37
DEVICE MONITORING UTILITY
4 C CONTROLLER SETTING UTILITY
Device settings
Table 4.25 Description of the I/O assignment settings tab (continued)
I/O assignment settings Multiple CPU settings Communication diagnostics
Item I/O assignment
Type
Model name Points Start X/Y Switch settings button Detailed settings button Base setting Base model Power model Extension cable Slots
Base mode 8 slot default , 12 slot default button Import multiple CPU parameters button Default button
Description
Select the type of the mounted module. In a multiple CPU system, no error will be displayed when "CPU (Empty)" is set to the position where the C Controller module does not support. Check for incorrect setting. (Default: " "(blank)) Enter the model name of the mounted module. When changing I/O points, select the I/O points of the slot. (Default: " "(blank)) When changing I/O No., select the I/O No. of the slot. Opens the Switch settings for I/O and intelligent function module screen.
Opens the Intelligent function module detailed settings screen. Base unit setting. In a multiple CPU system, the settings for each CPU module must be identical. Enter the model name of the base unit. Enter the model name of the power supply module. Enter the model name of the extension cable. Select the number of slots of the base unit. (Default: none) Select Base mode either from "Auto" or "Detail" (Default: "Auto")
Batch-sets the base unit to the specified number of slots.
Reads out multiple CPU parameters either from the following file. ·Project file created with GX Developer ·Parameter setting file created with C Controller setting utility. Changes the settings back to default.
Reference page
Page 4-39 Page 4-40
Page 4-48
4 - 38
4.9 I/O Assignment Settings Tab
4 C CONTROLLER SETTING UTILITY 1
(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).
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
3
Figure 4.27 Switch settings for I/O and intelligent function module screen
Table 4.26 Description of the Switch settings for I/O and intelligent function module screen
4
Item
Description
Reference page
Input format
Select the numerical input format. (Default: "HEX.")
Slot, Type, Model name
Displays the "Slot", "Type", and "Model" set on the I/O assignment screen.
Page 4-37
Set the switches of the programmable controller CPU or intelligent function
module.
Switch 1 to Switch 5
In a multiple CPU system, the settings for each CPU module must be identical. Switch settings of the programmable controller CPU is available only in the
5
12DCCPU-V.
End button
Saves the settings and closes the Switch settings for I/O and intelligent function module screen.
Cancel button
Closes the Switch settings for I/O and intelligent function module screen without saving the settings.
6
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
4.9 I/O Assignment Settings Tab
4 - 39
4 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).
Figure 4.28 Intelligent function module detailed settings screen
Table 4.27 Description of the Intelligent function module detailed settings screen
Item
Description
Slot, Type, Model name Error time output mode H/W error time CPU operation mode
I/O response time
Control CPU End button Cancel button
Displays the "Slot", "Type", and "Model" set on the I/O assignment screen.
Select the output mode for error detection.
(Default: "Clear")
Select the operation mode of the C Controller module for H/W error detection.
(Default: "Stop")
Set the I/O response time.
Mounted module
Default
High-speed input module, interrupt module
0.2
Input module, I/O combined module
10
(In increments of ms)
Set the control CPU
In a multiple CPU system, the settings for each CPU module must be identical.
(Default: "No.1")
Saves the settings and closes the Intelligent function module detailed settings
screen.
Closes the Intelligent function module detailed settings screen without saving the
settings.
Reference page
Page 4-37
4 - 40
4.9 I/O Assignment Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
4 C CONTROLLER SETTING UTILITY 1 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.
2
Set parameters regarding the multiple CPU system.
(1) Precautions for the Multiple CPU settings tab
(a) Parameter setting
Set the multiple CPU parameters on the CPU No.1. For the CPU module No.2 or later, utilize the parameters set on the CPU No.1.
3
For the multiple CPU parameter, refer to the C Controller Module User's Manual
(Hardware Design, Function Explanation).
(2) Multiple CPU settings tab
Q12DCCPU-V
Q06CCPU-V(-B)
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
Figure 4.29 Multiple CPU settings tab
6
Table 4.28 Description of the Multiple CPU settings tab
Device settings I/O assignment settings Multiple CPU settings Communication diagnostics
Item Number of CPUs Host CPU number
Description
Reference
page
7
Set the total number of the programmable controller CPUs, C Controller modules,
and Motion CPUs that comprise the multiple CPU system.
In a multiple CPU system, the settings for each CPU module must be identical.
(Default: 1)
Set the CPU No. of the host CPU (C Controller module).
For the Q06CCPU-V(-B), this setting is not available.
This item is disabled when "Number of CPUs" is set to "1". (Default: No specification)
8
(To the next page)
4.10 Multiple CPU Settings Tab
4 - 41
DEVICE MONITORING UTILITY
4 C CONTROLLER SETTING UTILITY
Table 4.28 Description of the Multiple CPU settings tab (continued)
Device settings I/O assignment settings Multiple CPU settings Communication diagnostics
Item
Description
Reference page
Set the operation mode for a CPU stop error on each programmable controller
Operation mode
CPU. In a multiple CPU system, the settings for each CPU module must be identical. This item is disabled when "Number of CPUs" is set to "1". (Default: checked (all CPUs are to be stopped for an error on each CPU module))
Check the target CPU module(s) of the multiple CPU synchronized boot-up.
Multiple CPU synchronous startup setting
For the Q06CCPU-V(-B), this setting is not available. In a multiple CPU system, the settings for each CPU module must be identical. This item is disabled when "Number of CPUs" is set to "1".
(Default: checked (Multiple CPU synchronized boot-up is enabled))
Online module change
Set whether to allow online change on the Process CPU. In a multiple CPU system, the settings for each CPU module must be identical. This item is disabled when "Number of CPUs" is set to "1".
Set whether to import the non-group input and/or output states.
I/O sharing when using Multiple CPUs
In a multiple CPU system, the settings for each CPU module must be identical. This item is disabled when "Number of CPUs" is set to "1".
(Default: not checked (not import the input and output states)
Set the Multiple CPU high speed transmission area. Multiple CPU high speed transmission For the Q06CCPU-V(-B), this item is disabled.
area setting
In a multiple CPU system, the settings for each CPU module must be identical.
This item is disabled when "Number of CPUs" is set to "1".
Use multiple CPU high speed
Set when using multiple CPU high-speed transmission.
transmission
(Default: checked (the function is enabled))
Set the points to the multiple CPU high-speed transmission area where each CPU module uses to send data. (Default: see below, Setting range: 12 to 14 points or less (Note that total 16 points or less including the system area))
CPU specific send range
Setting of "Number of
Send range for each CPU
CPUs"
CPU No.1 CPU No.2 CPU No.3 CPU No.4
2
7
7
3
7
3
3
4
3
3
3
3
User setting area
Displays usable range in the user setting area.
Displays the points of the multiple CPU high-speed transmission area where each
CPU module performs auto refresh.
Auto refresh
For setting the multiple CPU high-speed transmission area, open the Auto refresh
settings screen by clicking the Setting button. ( (3))
Page 4-44, Section 4.10
Set size for the system area that is used as the multiple CPU high-speed
system area
transmission area. This item is disabled when "Advanced settings" is not checked.
(Default: 1)
Advanced settings
Check when using the system area. (Default: not checked (not use))
(To the next page)
4 - 42
4.10 Multiple CPU Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
4 C CONTROLLER SETTING UTILITY 1
Device settings
Table 4.28 Description of the Multiple CPU settings tab (continued)
I/O assignment settings Multiple CPU settings Communication diagnostics
Item
Description
Communication area setting (refresh setting)*1
Set the auto refresh area within CPU modules
Reference
page
2
Change screens
Select any of registered refresh setting. (Default: "Setting1")
Set the points of a shared memory by which each CPU module use to send data.
Send range for each CPU
Points for "Start" and "End" are automatically calculated and displayed.
Import multiple CPU parameters button
(Default: 0, Setting range: 0 to 2048) Reads out multiple CPU parameters either from the following file. ·Project file created with GX Developer ·Parameter setting file created with C Controller setting utility.
3
Page 4-48
Default button
Changes the settings back to default.
* 1 The following dialog box appears when switching this screen to another without setting the number smaller than the refresh setting.
4
Figure 4.30 Dialog box Clicking the OK button moves up the preset refresh setting to an empty area with the smaller No.
Example)
<At setup> Setting 1 Setting A
<After screen chan Setting 1 Setting A
5
Setting 2 No setting
Setting 2 Setting B
Setting 3 No setting
Setting 3 No setting
Setting 4 Setting B
Setting 4 No setting
Figure 4.31 Refresh settings example
POINT
6
Points for the system area used for dedicated instructions can be changed to 2K
by selecting "Advanced settings" which increases the number of dedicated
instructions to be simultaneously executed.
For dedicated instructions, refer to the manual for the Motion CPU used.
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
4.10 Multiple CPU Settings Tab
4 - 43
4 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
<<CPU No.1>> tab to <<CPU No.4>> tab
CPU specific send range points
Description Select the CPU module to be configured. Either "(Send)" or "(Receive)" is displayed with a tab name when "No.1" to "No.4" are selected for "Host CPU number". "(Send)" and "(Receive)" indicates whether respective CPU data are sent to or received from the C Controller module. Set the points to the Multiple CPU high speed transmission area where each CPU module performs auto refresh. (Default: " "(blank), Setting range: up to "Max. points")
Start End
Displays the Multiple CPU high speed transmission area set in "Auto refresh" by address. The C Controller module calculates the value to display.
Total points Settable points
Displays total of the points set in "Auto refresh". Displays the maximum points that can be set in "Auto refresh".
Check button
Check for incorrect setting.
End button Cancel button
Saves the settings and closes the Auto refresh settings screen.
Closes the Auto refresh settings screen without saving the settings.
4 - 44
4.10 Multiple CPU Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
4 C CONTROLLER SETTING UTILITY 1 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.
2
(1) Precautions for the Communication diagnostics tab
(a) When a utility communication error has occurred
When a utility communication error has occurred during diagnosing, set the
connection target again in the Connection settings so that the communication can be restarted.
3
(2) Communication diagnostics tab
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
5
Figure 4.33 Communication diagnostics tab
Table 4.30 Description of the Communication diagnostics tab
6
Device settings I/O assignment settings Multiple CPU settings Communication diagnostics
Item Communication diagnostics
Target CPU
Repeat count
Description
Performs communication diagnostics Select the CPU to diagnose. Selecting the host CPU displays the error code "19203". Selecting an empty slot displays the error code "19200". (Default: "No.1") Specify the number of times that communication diagnostics is performed. (Default: 5, Setting range 1 to 32767)
Reference page
7
Start or Stop button
Executes or stops the communication diagnostics.
Execution count
Displays the number of times that communication diagnostics has been executed. "Normal" appears when the execution result is normal.
8
Result
"Error" appears when the execution was resulted in an error.
"Diagnosing" appears during diagnosing.
Mean time to communicate
Displays the mean time required for communication.
Error code
Displays an error code of communication diagnostics. For details of error codes, refer to HELP of the MELSEC data link function.
4.11 Communication Diagnostics Tab
4 - 45
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4 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.
· Press the [Alt] key and then the [ ] key. · For Windows® 7 or later, right-click the icon (
the [Shift] key.
) on the task bar while pressing
Item Move, Minimize, Close Specify CPU type CC-Link utility MELSECNET/H utility
CC IE Control utility
Device monitoring utility Version information
Figure 4.34 System menu
Table 4.31 Description of the System menu
Description
Refer to manuals for Microsoft® Windows®. Specifies a C Controller module to which parameters are set or to be monitored. This item cannot be selected during monitoring. Starts CC-Link utility. When C Controller setting utility is connected online, this utility is started with the same connection target connected. Starts MELSECNET/H utility. When C Controller setting utility is connected online, this utility is started with the same connection target connected. Starts CC IE Control utility. When C Controller setting utility is connected online, this utility is started with the same connection target connected. For the Q06CCPU-V-B, this utility cannot be used. Starts Device monitoring utility. When C Controller setting utility is connected online, this utility is started with the same connection target connected. For the Q06CCPU-V-B, this utility cannot be used. Opens the version information screen.
Reference page
Page 3-4 Page 5-1 Page 6-1
Page 7-1
Page 8-1 Page 4-47
4 - 46
4.12 System Menu
4 C CONTROLLER SETTING UTILITY 1 (2) Version information screen Version information of C Controller setting utility can be checked on this screen.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
Item Software package
SW3PVC-CCPU-E C Controller setting utility Product information Model name Serial No. Function version
Product No. OK button
Figure 4.35 Version information screen (Example: Version 3.03D) Table 4.32 Description of the version information screen
Description
3
Reference page
Displays the version of SW3PVC-CCPU.
4
Displays the update date of C Controller setting utility.
Displays the product information of the C Controller module (Model name, Serial
No., and product No.) when this utility is connected to the module online.
The System information screen also displays the same information.
This information cannot be displayed offline.
In a multiple CPU system, the information can also be confirmed in the system
monitor (product information list) of GX Developer. For the Q06CCPU-V(-B), "-" appears for the product No.
5
Closes the version information screen.
6
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
4.12 System Menu
4 - 47
4 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. · Click the Load initial setting file button in the System settings tab. · Click the Import multiple CPU parameters button in the I/O assignment settings tab. · Click the Import multiple CPU parameters button in the Multiple CPU settings tab
(2) Open project screen
A project of the set data can be selected on this screen.
Item Project drive Drive/Path Project name
Open button
Cancel button
Figure 4.36 Open project screen Table 4.33 Description of the Open project screen
Description Select the drive where a project is saved. Enter the drive and path for the project. Enter the project name to be read. Reads out the project.
Closes the screen without reading out the project.
4 - 48
4.13 Reading Initial Setting File and Importing Multiple CPU Parameters
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
4 C CONTROLLER SETTING UTILITY 1
(3) Precautions for utilizing set data
(a) Initial setting file of intelligent function modules and multiple CPU parameters can be imported from the following files.
Table 4.34 Files to import
2
Item
Description
Initial setting file of intelligent function module
Project file in GX Developer (
Page 4-49, Section 4.13 (3) (d))
For GX Works2, the projects saved in the format of GX Developer can be reused.
·Project file in GX Developer
Multiple CPU parameters
For GX Works2, the projects saved in the format of GX Developer can be reused.
·Parameter setting file in C Controller setting utility
3
(b) When transferring data of GX Developer set by another personal computer, to a
development environment (personal computer), transfer the project folder of GX
Developer.
The project cannot be specified if only file was transferred.
(c) When multiple CPU parameters are utilized between different CPU types, (
Page 3-4, Section 3.4) default values will be displayed for the parameters not
4
supported by the CPU type.
Name GX Configurator-AD GX Configurator-DA GX Configurator-SC GX Configurator-CT GX Configurator-TC GX Configurator-TI GX Configurator-FL GX Configurator-PT GX Configurator-AS
GX Configurator-QP
GX Configurator-CC
(d) Reading out a project file of GX Developer On the C Controller module, the Initial settings of intelligent function module can be read out through a project file of GX Developer.
Note that only the initial settings made by GX Configurator can be read out.
Table 4.35 Availability of intelligent function module parameter read
5
Availability
Measures for unreadable GX Configurator
Write each parameter of the serial communication module to the buffer memory using the Bus interface function (QBF_ToBuf).
6
·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
7
2.30G or later.
GX Configurator-QP Version 2 Operating Manual
·For the Q06CCPU-V(-B)
Write parameters to a positioning module to the buffer memory using the Bus interface
function (QBF_ToBuf).
By using the sample program (QPParamSet.c), the parameter file created with GX
Configurator-QP can be transferred to the positioning module. (
Page 12-1, CHAPTER
8
12)
Set parameters for the CC-Link module using CC-Link utility of SW3PVC-CCPU.
: Read available, : Read N/A
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
4.13 Reading Initial Setting File and Importing Multiple CPU Parameters
4 - 49
4 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.
(3) Tabs available to operate offline
When C Controller setting utility connection is offline, data can be set only in the System settings tab, I/O assignment settings tab, and Multiple CPU settings tab.
(4) Terminating Microsoft® Windows®
Do not terminate Microsoft® Windows® while C Controller setting utility is running. Terminate C Controller setting utility first and then Microsoft® Windows®.
(5) 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.
(6) Time required for connection from each utility to the C Controller module
The following time is required for the C Controller module to connect to each utility after power-on or reset.
· When executing a script file, "STARTUP.CMD": Upon completion of the RUN LED flashing.
· When not executing a script file, "STARTUP.CMD": Fifteen (15) seconds after completion of start or reset
Do not attempt a connection before the above time has elapsed after completion of power-on or reset. Changing "Priority" to a larger value in the Option tab of C Controller setting utility increases the time after which the C Controller module can be connected.
4 - 50
4.14 Precautions
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
5 CC-LINK UTILITY 1
CHAPTER 5 CC-LINK UTILITY
5.1 CC-Link Utility Function List
2
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Table 5.1 CC-Link utility function list
Name
Description
Availability
Q12DCCPU Q06CCPU
-V
-V
Q06CCPU -V-B
Reference page
Specify CPU type
Specifies a C Controller module to which parameters are set or to be monitored.
Page 3-4
3
Connection settings
Sets parameters to a C Controller module which is to be connected with this utility.
Page 3-5
Parameter setting file saving/loading Module information display Other station monitoring
Saves parameters set in C Controller setting utility into a file or loads the file. Displays information of the CC-Link module (own station) controlled by the connected C Controller module. Displays line states of other stations (CC-Link network stations).
Page 3-14 Page 5-2
4
Page 5-6
Online operation
Reads, writes, verifies the CC-Link parameter.
Page 5-9
Parameter settings Sets parameters for the CC-Link modules.
Page 5-11
Target settings
Sets a logical station number for access to a CPU module in a multiple CPU system where a CC-Link module is mounted.
Page 5-15
Test
Tests the mounted CC-Link modules.
Page 5-18 : Available, : Available but partially restricted, : N/A
5
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
5.1 CC-Link Utility Function List
5 - 1
5 CC-LINK UTILITY
5.2 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 When a utility communication error has occurred during connection, click the
Start monitoring button or set the connection target again in the Connection settings so that the communication can be restarted.
(b) During reset Communications are not available while the C Controller module is being reset. Start communications after the reset is complete.
(2) Module information tab
Figure 5.1 Module information tab Table 5.2 Description of Module information tab
Module information Other station monitoring Online operation Parameter settings Target settings Test
Item
Description
Target module
Select the CC-Link module to display its information. (Default: "Slot 1 to 4")
Start monitoring button, Stop monitoring button
Starts/stops monitoring of the CC-Link module. "*" flashes in the upper right of the button during monitoring. These buttons are disabled in the offline status.
Slot n
Displays information of the CC-Link module.
(n is within the range set to "Target module") The information is displayed in ascending order of start I/O No.
Start I/O No.
Displays the start I/O No. of the CC-Link module.
Channel No.
Displays the channel No. of the CC-Link module whose parameters have been set. "-" appears when "Channel No." has not been set.
(To the next page)
5 - 2
5.2 Module Information Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
5 CC-LINK UTILITY
1
Table 5.2 Description of Module information tab (continued)
Module information Other station monitoring Online operation Parameter settings Target settings Test
Slot n
Item
Sta. No.
Link scan time Data link status Error status
Details button
Description
Displays the station No., Station type, and Operation mode. (Display example: "0: Master station (Ver.2 mode)", "1: Local station")
2
For details of operation mode, refer to the following.
Page 5-3, Section 5.2 (2) (a)
Displays current link scan time of the CC-Link module. (In increments of ms)
Displays data link status of the CC-Link module. (
Page 5-3, Section 5.2 (2) (b))
Displays error status of the CC-Link module. (
Page 5-4, Section 5.2 (2) (c))
Opens the Detailed module information screen. (
Page 5-4, Section 5.2 (3))
3
This button is disabled during monitoring.
(a) Operation mode
The following indicates details of the Operation mode.
Table 5.3 Details of Operation mode
Display
Description
4
No display
Cyclic transmission data size has not been increased. Remote net(Ver.1 mode)
Both the CC-link module supporting/not supporting the cyclic
(Additional mode)
transmission data size increase exist.
Remote net(Add. mode)
(Ver.2 mode)
Cyclic transmission data size has been increased. Remote net(Ver.2 mode)
5
(b) Data link status
The following indicates details of the Data link status.
Table 5.4 Details of Data link status
Display
Description
In data link Suspended data link
Data link is being performed. Data link is suspended.
6
Initial status
In initial status (before parameter update)
Waiting for receiving parameters Parameters have not been received.
Disconnecting (no request polling)
Disconnected from data link network due to no request from the master station.
Disconnecting (Link error)
Disconnected from data link network due to a line error.
Disconnecting (Other) Performing line test
Disconnected from data link network due to any other factor. Line test is in process.
7
Performing parameter setting test Parameter setting test is in process from the master station.
Performing auto-return
Processing for automatically returning to data link network is being performed.
Resetting
CC-Link module is being reset.
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
5.2 Module Information Tab
5 - 3
5 CC-LINK UTILITY
(c) Error status The following indicates details of the Error status.
Table 5.5 Details of error status
Display Normal Transport error Parameter error CRC error Timeout error Abort error Setting error
Other error
Description Normal status. Transmission channel error was detected. Parameter error was detected. CRC error was detected. Timeout error was detected. CC-Link module (gate array) error was detected. Setting error was detected. Any other error was detected. Refer to the manual for the CC-Link module and troubleshoot the problem.
(3) Detailed module information screen
Detailed information of the CC-Link module are displayed on this screen.
Figure 5.2 Detailed module information screen
Table 5.6 Description of Detailed module information screen
Item Start I/O No., Channel No., Sta. No. Mode switch status Data link status Error status Model name Product information
Link scan time (ms)
OK button
Save SB/SW button
Description
Displays detailed information of the CC-Link module. (
Page 5-2, Section 5.2 (2))
Displays the mode switch status of the CC-Link module. (
Page 5-5, Section 5.2 (3) (a))
Displays data link status of the CC-Link module. (
Page 5-3, Section 5.2 (2) (b))
Displays error status of the CC-Link module. (
Page 5-4, Section 5.2 (2) (c))
Displays the model name of the CC-Link module.
Displays the product information (serial No. and function version) of the CC-Link module.
Displays the maximum, minimum, and current scan time of the CC-Link module. (In increments of
ms)
Closes the Detailed module information screen.
Saves the link special relay (SB) and link special register (SW) data of the CC-Link module into a
CSV format file. (
Page 5-5, Section 5.2 (4))
Remark
The information displayed on the Detailed module information screen is based on the setting when the screen was opened. To update the information, close and reopen the Detailed module information screen.
5 - 4
5.2 Module Information Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
5 CC-LINK UTILITY
1
(a) Mode switch status The following indicates details of the Mode switch states.
Table 5.7 Details of Mode switch states
Display
0: 156kbps (Online) 1: 625kbps (Online) 2: 2.5Mbps (Online) 3: 5Mbps (Online) 4: 10Mbps (Online) 5: 156kbps (Line test ) 6: 625kbps (Line test ) 7: 2.5Mbps (Line test ) 8: 5Mbps (Line test ) 9: 10Mbps (Line test ) A: 156kbps (Hardware test) B: 625kbps (Hardware test) C: 2.5Mbps (Hardware test) D: 5Mbps (Hardware test) E: 10Mbps (Hardware test) F: Not available
Transmission speed
Mode
2
156Kbps
625Kbps
2.5Mbps
Online
5Mbps
10Mbps
156Kbps
625Kbps
Line test
3
2.5Mbps
When =1, station No. is 0.
5Mbps
When =2, station No. is 1 to 64.
10Mbps
156Kbps
625Kbps
2.5Mbps 5Mbps
Hardware test
4
10Mbps
(4) Specifications of the SB/SW save file
A file format can be selected in "Save as" on the following screen.
5
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
6
Figure 5.3 Save As screen
To use the text data of the SB/SW save file in a user program etc., select "SBSWSave File(*.csv)" when saving. To use them on Microsoft® Excel etc., select "SBSWSave File[Form2](*.csv)" when saving.
When "SBSWSave File(*.csv)" is selected
When "SBSWSave File[Form2](*.csv)" is selected
7
Figure 5.4 Examples of SB/SW save files
8
Remark
The folder of the SB/SW save file is stored in "C:\MELSEC\CCPU\Param" by default. (When SW3PVC-CCPU has been installed in "C:\MELSEC").
5.2 Module Information Tab
5 - 5
DEVICE MONITORING UTILITY
5 CC-LINK UTILITY
5.3 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.
To start monitoring, click the Start monitoring button.
(b) When a utility communication error has occurred When a utility communication error has occurred during connection, click the
Start monitoring button or set the connection target again in the Connection settings so that the communication can be restarted.
(c) During reset Communications are not available the C Controller module is reset. Start communications after the reset is complete.
(2) Other station monitoring tab
Figure 5.5 Other station monitoring
Table 5.8 Description of the Other station monitoring tab
Module information Other station monitoring Online operation Parameter settings Target settings Test
Item Target module
Start I/O No.
Own station information
Description Select the module to monitor as other station monitoring. (Default: "Slot 1", Setting range: "Slot 1" to "Slot 8") Displays the start I/O No. of the CC-Link module selected in "Target module". Displays the station No., station type, and operation mode. For details of operation mode, refer to the following.
Page 5-3, Section 5.2 (2) (a)
View all stations button No.
Opens the View all stations screen. ( Displays the connection number.
Page 5-8, Section 5.3 (3))
(To the next page)
5 - 6
5.3 Other Station Monitoring Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
5 CC-LINK UTILITY
1
Table 5.8 Description of the Other station monitoring tab (continued)
Module information Other station monitoring Online operation Parameter settings Target settings Test
Item
Description
Target module
Sta. No. Reserved station information
Displays the station No. Displays the reserved station.
2
Error invalid station information Displays the error invalid station.
Station type
Displays the error invalid station.
Occupied number
Displays the number of occupied stations.
Status
Displays the status of each station module. (
Page 5-7, Section 5.3 (2) (a))
Transient error Expanded cyclic setting
Displays the transient error of each module. Displays the expanded cyclic setting. This item are not displayed when the status of the target module is "Remote net(Ver.1 mode).
3
Remote station points
Displays the number of remote station points. This item are not displayed when the status of the target module is "Remote net(Ver.1 mode).
Start monitoring , or
Starts or stops monitoring the CC-Link module. "*" flashes in the upper right of the button during monitoring.
Stop monitoring button
These buttons are disabled in the offline status.
(a) States
4
Details of states are given below.
Table 5.9 Details of states
Display
Description
Normal
Normal
Temporary error invalidity status Temporary error is invalid.
Data link error
Link status is in error.
5
WDT error
Watchdog timer error has occurred.
Blown fuse confirmation error There is a station that has a fuse blow.
Station No. duplication
Station number is duplicated.
Switch changing
Switch setting was changed.
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
5.3 Other Station Monitoring Tab
5 - 7
5 CC-LINK UTILITY
(3) View all stations screen
The following indicates communication states of other stations.
Item Status of each station OK button
Figure 5.6 View all stations screen
Table 5.10 Description of View all stations screen
Description Communication status of each station is coded in color as follows.
White: Normal communication Red: Error station Green: Error invalid station Blue: Reserved station Yellow: Temporary error invalid station The information displayed on the screen is based on the communication status when the screen was opened. Any changes on the communication status after opening the screen does not take effect to the display. Closes the View all stations screen.
5 - 8
5.3 Other Station Monitoring Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
5 CC-LINK UTILITY 1 5.4 Online Operation Tab
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
The CC-Link parameters can be read, written, or verified from this tab.
2
(1) Precautions for the Online operation tab
(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.
3
(b) During reset
Communications are not available while the C Controller module is being reset.
Start communications after the reset is completes.
(c) The drive to which parameters are written
When writing parameters from each of the utilities to the following C Controller
module, write them to the same drive.
4
· 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.
(2) Online operation tab
5
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
6
Figure 5.7 Online operation tab
Table 5.11 Description of Online operation tab
7
Module information Other station monitoring Online operation Parameter settings Target settings Test
Item Target drive Read parameters Read button
Description
Set a target drive for reading, writing, or verifying parameters.*1
This setting is not available for the Q06CCPU-V(-B).
(Default: Parameter boot drive)
Reads out the CC-Link parameter from the C Controller module.
8
* 1 For the drives to which parameters can be written (user memory), refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
(To the next page)
5.4 Online Operation Tab
5 - 9
DEVICE MONITORING UTILITY
5 CC-LINK UTILITY
Table 5.11 Description of Online operation tab (continued)
Module information Other station monitoring Online operation Parameter settings Target settings Test
Item
Write parameters Write button
Verify parameters Verify button
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 reset. Parameters can be written only when "Write authority" is selected in Connection settings. If "Write authority" is not selected, select it in the Connection settings screen before writing parameters.
(
Page 3-5, Section 3.5)
Verifies the CC-Link parameters set in the C Controller module and in CC-Link utility. The verification result is displayed in a message box.
Remark
To read, write, or verify parameters, connect the C Controller module and the development environment (personal computer) online.
5 - 10
5.4 Online Operation Tab
OVERVIEW
5 CC-LINK UTILITY 1 5.5 Parameter Settings Tab
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Set the CC-Link module parameter in the Parameter settings tab.
2
(1) Parameter settings tab
3
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
4
Figure 5.8 Parameter settings tab Table 5.12 Description of Parameter settings tab
5
Module information Other station monitoring Online operation Parameter settings Target settings Test
Item Number of modules Target module Start I/O No.
Channel No.
Default button Check button
Description
Set the number of CC-Link modules that are to be controlled by the C Controller module.
Selecting "(Blank)" means no setting (Setting cleared).
(Default: "(Blank)")
Select a module to configure. (Default: 1)
The numbers for this item will be automatically rearranged in ascending order of start I/O numbers
6
when saving the parameter setting file or when switching the tab.
Set a start I/O No. of a CC-Link IE Controller Network module.
(Setting range: 0 to FE0H (The set value must be unique, and not duplicated with the one for
another CC-Link IE Controller Network module.))
Set a channel No. of a CC-Link IE Controller Network module.
The set value is used to open the channel from Device monitoring utility or a user program
(MELSEC data link functions). For the Q06CCPU-V-B, this setting is not available.
7
Channel No. must be unique, and not duplicated with the one for another CC-Link IE Controller
Network module.
Sets the parameters for Operation settings and Station information settings back to default.
Checks for any setting error.
(To the next page)
8
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
5.5 Parameter Settings Tab
5 - 11
5 CC-LINK UTILITY
Table 5.12 Description of Parameter settings tab (continued)
Module information Other station monitoring Online operation Parameter settings Target settings Test
Item Operation settings
Type Mode
Expanded cyclic setting
Error event: input data status
CPU stop: data link status
Occupied number
Description Set the operation mode of the CC-Link module. Select a type of the CC-Link module. (Default: "Master station") Select a mode of the CC-Link module. (Default: "Remote net(Ver.1 mode")) Select the expanded cyclic setting of the CC-Link module. This setting is available only when "Local station" is set in "Type" and other than "Remote net(Ver.1 mode)" is specified in "Mode". (Default: "Single") Set how the input data be handled in the event of data link error. (Default: "Clear") Set how the link data to be handled in the event of CPU stop. This setting is available for the J61BT11N. For the QJ61BT11, the "Refresh" is applied regardless of the setting on this tab. (Default: "Refresh") Set the number of occupied stations of the CC-Link module (local station). This setting is available only when "Local station" is set in "Type". (Default: "Exclusive station 1")
Other settings button Station information settings
All connect count Station Type
Expanded cyclic setting Occupied number Remote station points
Opens the "Other settings" screen. (
Page 5-14, Section 5.5 (2))
Set the total of connected modules and each CC-Link module station information. This setting is available only when "Master station" is set in "Type", and any of the following is set in
"Mode".
·Remote net(Ver.1 mode)
·Remote net(Ver.2 mode)
·Remote net(Add. mode)
Set the number of modules that are to be connected to the CC-Link module. (Default: 64)
Select a type of the station.
Default values are given below.
·When "Remote net(Ver.1 mode)" is set in "Mode": "Remote I/O station"
·When "Remote net(Ver.2 mode)" or "Remote net(Add. mode)" is set in "Mode": "Ver.1 Remote I/O
station"
Select a expanded cyclic points of the CC-Link module. (Default: "Single") This setting is available only when the following conditions are satisfied. ·When "Remote net(Ver.2 mode)" or "Remote net(Add. mode)" is set in "Mode". ·When "Ver.2 Remote device station" or "Ver.2 Intelligent device station" is set in "Type".
Select the number of occupied stations.
(Default: "Exclusive station 1")
Select the points of remote station. This setting is available only when "Remote net(Ver.2 mode)" is set in "Mode". For defaults and setting range, refer to the CC-Link System Master/Local Module User's Manual.
(To the next page)
5 - 12
5.5 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
5 CC-LINK UTILITY
1
Table 5.12 Description of Parameter settings tab (continued)
Module information Other station monitoring Online operation Parameter settings Target settings Test
Item
Description
Station information settings
Reserve/invalid station select
Set the CC-Link module as a reserved or invalid station. (Default: "No setting")
2
This setting is available when any of the following is set in "Type".
Intelligent buffer select (word)
·Intelligent device station ·Ver.1 Intelligent device station
·Ver.2 Intelligent device station
Send Receive
Specify the send area. (In increments of words) (Default: 64, Setting range: 0, 64 to 4096) Specify the receive area. (In increments of words) (Default: 64, Setting range: 0, 64 to 4096)
3
Automatic
Specify the automatic update area. (In increments of words) (Default: 128, Setting range: 0, 128 to 4096)
Clear button
Clears parameters set in "Station information setting" and set defeat values instead.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
5.5 Parameter Settings Tab
5 - 13
5 CC-LINK UTILITY
(2) Other settings screen
Figure 5.9 Other settings screen
Item Retry count*1
Auto return station count*1 Standby master station No.*1 CPU down: data link status*1 Delay information setting*1 Block data assurance per station Set button Cancel button
Table 5.13 Description of Other settings screen
Description Set the number of retries in the case of a communication error (transient transmission error occurrence) (Default: 3, Setting range: 1 to 7) Set the number of modules that can be automatically reconnected in one link scan. (Default: 1, Setting range: 1 to 10) Set a station No. of the standby master station. (Default: 0 (no setting), Setting range: 0 to 64) Set the data link status when an error occurs in the C Controller module. (Default: "Stop") Set "0". Set whether to use the block data assurance per station function. (Default: unchecked (not use))
Applies the settings and closes the Other settings screen.
Closes the Other settings screen without applying the settings.
* 1 This setting is available when "Master station" is set in "Type", and any of the following is set in "Mode".
·Remote net(Ver.1 mode) ·Remote net(Ver.2 mode) ·Remote net(Add mode)
5 - 14
5.5 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
5 CC-LINK UTILITY 1 5.6 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
2
a programmable controller CPU other than the control CPU of the target station.
Note that the accesses indicated below does not require the logical station No. settings.
Page 5-17, "5.6 (4) Access that does not require a logical station No. setting"
(1) Precaution for the Target settings tab
Set a programmable controller CPU in "Target CPU"
3
(2) Target settings tab
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
5
Figure 5.10 Target settings tab
Table 5.14 Description of Target settings tab
6
Module information Other station monitoring Online operation Parameter settings Target settings Test
Item Target module
Logical sta. No.
Sta. No. Target CPU Set button
Description
Select a module to configure.
(Default: "Slot 1")
Specify a logical station No. for the module selected in "Target module". (Default: 65, Setting range: 65 to 239)
7
The logical sta. No. is a logical number to be specified as "Sta. No." in Device monitoring utility and
a user program (MELSEC data link function).
Select a station No. of the CC-Link module controlled by a multiple CPU system.
(Default: 0, Setting range: 0 to 63)
Select a CPU of the access target (CPU No. in a multiple CPU system).
(Default: 1, Setting range: 1 to 4)
Enters the added and changed data (Logical sta. No., Sta. No., and Target CPU) to the Target list.
8
(To the next page)
5.6 Target Settings Tab
5 - 15
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
5 CC-LINK UTILITY
Table 5.14 Description of Target settings tab (continued)
Module information Other station monitoring Online operation Parameter settings Target settings Test
Target list
Item
Change button Delete button
Description Displays the logical No. set to the module selected in "Target module", corresponding station No., and target CPU in a list. Displays the setting data (of Logical sta. No.) selected from the target list into a Logical sta. No. field to change. (Clicking the row also displays the setting to change.)
Deletes the setting data (of Logical sta. No.) selected from the target list.
(3) Access example
When the settings in the following tab are applied in the below system, a CC-Link module controlled by the C Controller module can access CPU No.4 via another CCLink module (whose control CPU is CPU No.2) by using the logical station No. "65". The access is also available by opening channel No.81 and setting 65 for the station No. in Device monitoring utility or a user program (MELSEC data link function).
C Controller module
Master station QJ61BT11N Slot 1, Channel No. 81 (Controlled by C Controller module)
CPU CPU No. 2 No. 4 *1
Local station QJ61BT11N Station No.: 5 (Controlled by CPU No. 2)
Multiple CPU system
CC-Link
Terminating resistor
Figure 5.11 System configuration example * 1 When CPU No.4 cannot configure a multiple CPU system, access to CPU No. 4 is not available by
using a logical station No.
The following indicates the Target settings for the above access example.
5 - 16
5.6 Target Settings Tab
Figure 5.12 Target settings tab setting
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
5 CC-LINK UTILITY 1
(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.
C Controller module
Other station CC-Link module
Control CPU of other station CC-Link module
2
C Controller
module
3
CC-Link
CC-Link
Terminating resistor
Terminating resistor
Figure 5.13 Access that does not require a logical station No. setting
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
5.6 Target Settings Tab
5 - 17
5 CC-LINK UTILITY
5.7 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. While in offline, the both tests cannot be executed.
(b) Line test
Select station(s) to be tested by selecting either "All stations (1 to 64)" or
"Selected station" as necessary and then conduct the test.
(
Page 5-19, Section 5.7 (3))
(c) When an communication error has occurred To restart the communication, set data again in the Connection settings.
(2) Test tab
Figure 5.14 Test tab
Table 5.15 Description of the Test tab
Test Module information Other station monitoring Online operation Parameter settings Target settings
Item Target module
Start I/O No.
Description Select a module for testing. (Default: "1" slot) Displays the start I/O No. of the CC-Link module.
(To the next page)
5 - 18
5.7 Test Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
5 CC-LINK UTILITY 1
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.
2
Own station information
For details of the operation mode, refer to the following.
Page 5-3, Section 5.2 (2) (a)
Select the test to conduct.
Test item
Display
Description
Line test Network test
Tests the connected station for connectivity with a data link. (Selectable for the Master station only) Tests a data link start and stop.
3
Conduct a test selected in the above "Test item".
Start button
Line test........... Network test....
Page 5-19, Section 5.7 (3) (a) Page 5-20, Section 5.7 (3) (b)
(3) Testing procedure
(a) Line test
4
The line test can be conducted only when the data link status of the CC-Link
module (
Page 5-2, Section 5.2) is "In data link" or "Perform auto-return".
When the line test for "All stations (1 to 64)" resulted in error, which indicates
possible error station, conduct the line test again selecting "Selected station".
1) Setting
Select the target station of the line test and click the OK button to start the
5
test.
Figure 5.15 Line test screen
6
2) Results
For "All stations (1 to 64)"
For "Selected station"
7
Figure 5.16 Result screen
For details of error codes, refer to Help of the bus interface function.
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
5.7 Test Tab
5 - 19
5 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 OK button to start the test.
Figure 5.17 Network test screen
2) Result The test result is displayed on the following screen.
Figure 5.18 Network test result screen
For details of error codes, refer to Help of the bus interface function.
5 - 20
5.7 Test Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
5 CC-LINK UTILITY 1 5.8 System Menu
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) System menu
2
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.
· Press the [Alt] key and then the [ ] key. · For Windows® 7 or later, right-click the icon ( ) on the task bar while pressing
3
the [Shift] key.
Item Move, Minimize, Close Specify CPU type
C Controller setting utility
Device monitoring utility Version information
4
Figure 5.19 System menu
Table 5.16 Description of System menu
Description
Refer to manuals for Microsoft® Windows®.
5
Specifies a C Controller module to which parameters are set or to be monitored. ( Section 3.4) This item is disabled during monitoring.
Page 3-4,
Starts C Controller setting utility. (
Page 4-1, CHAPTER 4)
When CC-Link utility is connected online, this utility is started with the same connection target
connected. Starts Device monitoring utility. (
Page 8-1, CHAPTER 8)
6
When CC-Link utility is connected online, this utility is started with the same connection target
connected.
For the Q06CCPU-V-B, this utility cannot be used.
Opens the Version information screen. (
Page 5-22, Section 5.8 (2))
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
5.8 System Menu
5 - 21
5 CC-LINK UTILITY
(2) Version information screen
Version information of CC-Link utility can be checked on this screen.
Item Software package
SW3PVC-CCPU-E CC-Link utility
OK button
Figure 5.20 Version information screen (Example: Version 3.01B)
Table 5.17 Description of Version information screen Description
Displays the version of SW3PVC-CCPU. Displays the update date of CC-Link utility. Closes the Version information screen.
5 - 22
5.8 System Menu
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
5 CC-LINK UTILITY 1 5.9 Precautions
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Parameter details
2
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
(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.
(4) Tabs available to operate offline
When CC-Link utility connection is offline, data can be set only in the Parameter settings tab and the Target settings tab.
4
For the Q06CCPU-V-B, only parameters shown in the Target settings tab can be set.
(5) Terminating Microsoft® Windows®
Do not terminate Microsoft® Windows® while CC-Link utility is running.
Terminate CC-Link utility first and then Microsoft® Windows®.
5
(6) 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.
6
(7) Time required for connection from each utility to the C Controller
module
The following time is required for the C Controller module to connect to each utility
after power-on or reset.
· When executing a script file, "STARTUP.CMD":
Upon completion of the RUN LED flashing.
7
· When not executing a script file, "STARTUP.CMD":
Fifteen (15) seconds after completion of start or reset
Do not attempt a connection before the above time has elapsed after completion of
power-on or reset.
Changing "Priority" to a larger value in the Option tab of C Controller setting utility
increases the time after which the C Controller module can be connected.
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
5.9 Precautions
5 - 23
6 MELSECNET/H UTILITY
CHAPTER 6 MELSECNET/H UTILITY
6.1 MELSECNET/H Utility Function List
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Item
Specify CPU type
Connection settings Parameter setting file saving/loading Module information Error history monitoring Other station monitoring Online operation Parameter settings
Target settings
Table 6.1 MELSECNET/H Utility function list
Description
Specifies a C Controller module to which parameters are set or to be monitored. Sets parameters to a C Controller module which is to be connected with this utility. Saves parameters set in MELSECNET/H utility into a file or loads the file. Displays information of the MELSECNET/H (host station) controlled by the connected C Controller module. Displays the history of errors that occurred in the MELSECNET/H module. Displays line states of other stations (MELSECNET/H network stations).
Availability
Q12DCCPU Q06CCPU
-V
-V
Q06CCPU -V-B
Reference page
Page 3-4 Page 3-5 Page 3-14 Page 6-2 Page 6-9 Page 6-14
Reads, writes, verifies the MELSECNET/H parameter.
Page 6-25
Sets parameters for the MELSECNET/H modules.
Page 6-27
Sets a logical station number for access to a CPU module in a multiple CPU system where a MELSECNET/H module is mounted.
: Available,
Page 6-39 : Available but partially restricted, : N/A
6 - 1
6.1 MELSECNET/H Utility Function List
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
6 MELSECNET/H UTILITY 1 6.2 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.
2
(1) Precautions for the Module information tab
(a) When a utility communication error has occurred When a utility communication error has occurred during connection, click the
Start monitoring button or set the connection target again in the Connection
3
settings so that the communication can be restarted.
(b) During reset Communications are not available while the C Controller module is being reset. Start communication after the reset is complete.
(2) Module information tab
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
6
Figure 6.1 Module information tab
Table 6.2 Description of the Module information tab
Module information Error history monitoring Other station monitoring
Item
Description
7
Corresponding Corresponding
SB
SW
Displays total link device refresh time required to refresh the
Link device refresh time
MELSECNET/H and CC-Link IE Controller Network controlled by the C Controller module (host CPU). (In increments of ms)
Displays the maximum total link device refresh time in the past record.
Max.
"-" appears when Link device refresh cycle ( 6.6) is 0ms.
Page 6-27, Section
8
Displays the minimum total link device refresh time in the past record.
Min.
"-" appears when Link device refresh cycle (
Page 6-27, Section
6.6) is 0ms.
(To the next page)
6.2 Module Information Tab
6 - 2
DEVICE MONITORING UTILITY
6 MELSECNET/H UTILITY
Table 6.2 Description of the Module information tab (continued)
Module information Error history monitoring Other station monitoring
Item Link device refresh time
Current
Start monitoring or Stop monitoring button 1 Slot to 4 Slot
Start I/O No. Channel No.
Network No.
Group No. Sta. No. Type Status Link scan time Details button
Description
Corresponding Corresponding
SB
SW
Displays current total link device refresh time.
"-" appears when Link device refresh cycle (
Page 6-27, Section
6.6) is 0ms.
Starts or stops monitoring of the MELSECNET/H module.
"*" flashes in the upper right of the button during monitoring.
These buttons are disabled in the offline status.
Displays information of the CC-Link module.
The information is displayed in ascending order of start I/O No.
Displays the start I/O No. of the MELSECNET/H module.
Displays the channel No. of the MELSECNET/H module.
"-" appears when "Channel No." has not been set. (
Page 6-27,
Section 6.6)
Displays the network No. of the MELSECNET/H module.
"-" appears when "Network No." has not been set. ( Section 6.6) Displays the group No. of the MELSECNET/H module.
Page 6-27,
"-" appears when "Group No." has not been set. (
Page 6-27,
Section 6.6)
Displays the station No. of the MELSECNET/H module.
Displays the type of the MELSECNET/H module.
Displays the communication status of the MELSECNET/H module.
(
Page 6-3, Section 6.2 (2) (a))
Displays the scan time of the MELSECNET/H module.
(In increments of ms)
Opens the Module information tab. (
Page 6-4, Section 6.2 (3))
This button is disabled during monitoring.
SB0044
SW0040
SW0041 SW0042 SW0047
(a) Communication status Details of communication states are given below.
Table 6.3 Details of communication states
In data link
Display
Suspend data link (Other)
Suspend data link (Hostself) Baton pass (No area)
Baton pass (Parameter Halt)
Baton pass (No Receive) Disconnecting (no baton) Disconnecting (Link error) Testing Resetting
Description Data link is being performed. Cyclic transmission was stopped from the other station. Cyclic transmission was stopped by the host station. No B/W transmission assignment to the host station. An error has detected in any of the host station parameter. Common parameters have not been received. Station No. duplication, or cable not connected. Cable not connected. Online or offline test is being conducted. Hardware error.
6 - 3
6.2 Module Information Tab
6 MELSECNET/H UTILITY 1 (3) Detailed module information screen. Detailed information of the MELSECNET/H module are displayed on this screen.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
3
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
Item Model name Product information
OK button
Save SB/SW button
Own station information Start I/O No. Network No. Group No. Sta. No. Network Type
4
Figure 6.2 Detailed module information screen
Table 6.4 Description of the Detailed module information screen
Description
Displays the model name of the MELSECNET/H module. Displays the product information (serial No. and version) of the MELSECNET/H module.
Corresponding Corresponding
SB
SW
5
Closes the Detailed module information screen.
Saves the link special relay (SB) and link special register (SW) information of the MELSECNET/H module into a CSV format file.
(
Page 6-8, Section 6.2 (4))
Displays the own station information of the MELSECNET/H module.
Displays the start I/O No. of the own station.
Displays the network to of the own station.
Displays the group No. of the own station.
Displays the station No. of the own station.
Displays the network to which the MELSECNET/H module is
connected.
Displays the type of the own station.
6
SW0040
SW0041
SW0042
SB0057, SB005A
SW0046
SB0044
7
(To the next page)
8
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
6.2 Module Information Tab
6 - 4
6 MELSECNET/H UTILITY
Table 6.4 Description of the Detailed module information screen (continued)
Item
Description
Corresponding Corresponding
SB
SW
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.
Parameter setting
·Common parameter ·Common + Specific parameter
SB0054
SW0054
·Default parameter
·Default + Specific
Reserved station setting Displays whether a reserved station exists in the network.
SB0064
Displays the transmission mode of the own station. (Display: "Normal
Transmission mode
mode", "Constant scan XX ms" (XX represents the constant link scan
SW0068
setting time))
Duplex transmission setting
Displays the multiplex transmission setting of the own station. "-" is displayed in the case of a coaxial bus system. (Display: "Normal transmission", "Multiplex transmission")
SB0069
Duplex transmission status
Displays the multiplex transmission status of the own station. "-" is displayed in the case of a coaxial bus system. (Display: "Normal transmission", "Multiplex transmission", "-")
SB006A
Transmission speed
Displays the transmission speed of the own station. (Display: "10Mbps", "25Mbps")
Control station information
Displays the control station information of the MELSECNET/H network system.
Displays the specified control station in the MELSECNET/H network
Assign control station
system.
SW0057
"0" appears when the control station is faulty.
Displays the current control station in the MELSECNET/H network
Present control station system.
SW0056
"0" appears when the control station is faulty.
Displays the transmission information of the MELSECNET/H network
Transmission information
system. (Display: "Control station communication", "Sub control station
SB0056
transmission")
Sub control station transmission
Displays the sub control station transmission status of the MELSECNET/H network system. (Display: "Yes", "No")
SB0058
Remote I/O station number
Displays the station No. of the remote I/O master station for each block.
Block 1
Displays the station No. of the remote I/O master station of Block 1.
SW005C
Block 2
Displays the station No. of the remote I/O master station of Block 2.
SW005D
(To the next page)
6 - 5
6.2 Module Information Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
6 MELSECNET/H UTILITY
1
Table 6.4 Description of the Detailed module information screen (continued)
Item
Description
Corresponding Corresponding
SB
SW
Link information
Displays the network status
Mode F loop status
Displays the operation mode of the own station. (Display: "Online", "Offline", "Loop test")
SW0043
2
Displays the forward loop status. "-" is displayed in the case of a coaxial bus system. (Display: "Normal", "Loopback transmission", "Data link disable", "-")
SB0091, SB0099
Displays the No. of the station that is performing loopback on the
forward loop side.
Loopback station
"-" is displayed in the case of a coaxial bus system.
SW0099
The field goes blank when data link is not available. (Display: 1 to 64, "Not performed", "-", "(blank)")
3
R loop status
Displays the reverse loop status. "-" is displayed in the case of a coaxial bus system. (Display: "Normal", "Loopback transmission", "-")
SB0095, SB009A
Displays the No. of the station that is performing loopback on the
reverse loop side.
Loopback station
"-" is displayed in the case of a coaxial bus system. The field goes blank when data link is not available. (Display: 1 to 64, "Not performed", "-", "(blank)")
SW009A
4
Link scan time
Displays link scan time. (In increments of ms)
Max.
Displays the maximum link scan time in the past record. The field goes blank when data link is not available.
SW006B
Min.
Displays the minimum link scan time in the past record. The field goes blank when data link is not available.
SW006C
Current
Displays the current link scan time. The field goes blank when data link is not available.
SW006D
5
Data link information
Displays the data link status of the MELSECNET/H.
Total number of link stations
Displays the total number of linked stations on MELSECNET/H.
SW0059
Station of maximum normal transmission
Displays the maximum number of stations that are communicating normally.
SW005A
Station of maximum data link
Displays the maximum number of data link stations on MELSECNET/H.
SW005B
6
Transmission status
Displays the transmission status of MELSECNET/H.
(
Page 6-3, Section 6.2 (2) (a))
SW0047
Reason for transmission Displays the reason for transmission interruption on MELSECNET/H.
interruption
(
Page 6-7, Section 6.2 (3) (a))
SW0048
Reason for transmission Displays the reason for transmission stop on MELSECNET/H.
stop
(
Page 6-7, Section 6.2 (3) (b))
SW0049
7
Remark
The information displayed on the Detailed module information screen is based on
the information when the screen was opened.
To display the updated information, close and reopen the Detailed module
information screen.
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
6.2 Module Information Tab
6 - 6
6 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 Normal Offline Offline test Initial status Shift control station Online testing Baton disappearance Baton repetition Same station present Control Station repetition Reception retry error Transmission retry error Timeout error Link error Disconnecting No baton to own station Error code: XXXX
Description/Action Communicating normally Offline Offline test being conducted. Error occurred. (Error code: F101, F102, F105) Error occurred. (Error code: F104, F106) Error occurred. (Error code: F103, F109, F10A) Error occurred. (Error code: F107) Error occurred. (Error code: F108) Error occurred. (Error code: F10B) Error occurred. (Error code: F10C) Error occurred. (Error code: F10E) Error occurred. (Error code: F10F) Error occurred. (Error code: F110) Error occurred. (Error code: F112) Error occurred. (Error code: F11B) Error occurred. (Error code: F11F) Error (Refer to the displayed error code)
(b) Cause of transmission stop The following lists the description of display in the Reason for transmission stop field on the screen.
Table 6.6 Details of Reason for transmission stop
Normal
Display
Stop instruction present (All)
Stop instruction present (HostSelf) Stop instruction present (Station ) No parameter Illegal parameter
Connected CPU error
Suspend communication
Description Communicating normally Cyclic transmission of all stations was stopped from the own or other station.
Cyclic transmission of the own station was stopped.
Cyclic transmission of the own station was stopped from the other station (Station No. ). No parameter can be received. The set parameter is invalid. Medium or critical error has occurred on the CPU module in the own station. Data link error occurred on the own station.
6 - 7
6.2 Module Information Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
6 MELSECNET/H UTILITY 1 (4) Specifications of the SB/SW save file A file format can be selected in "Save as" on the following screen.
2
Figure 6.3 Save As screen
3
To use the text data of the SB/SW save file in a user program, select "SBSWSave
File(*.csv)" when saving.
To use them on Microsoft® Excel etc., select "SBSWSave File[Form2](*.csv)" when
saving.
When "SBSWSave File(*.csv)" is selected
When "SBSWSave File[Form2](*.csv)" is selected
4
Figure 6.4 Example of the SB/SW save file
5
Remark The folder of the SB/SW save file is "C:\MELSEC\CCPU\Param" by default. (When SW3PVC-CCPU has been installed in "C:\MELSEC").
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.2 Module Information Tab
6 - 8
6 MELSECNET/H UTILITY
6.3 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. When the number of stored data reaches to 16, the next error will be stored by deleting the oldest. (No.1 (oldest) to No. 16 (newest))
(b) Transient transmission error For the error codes and error types displayed in the Transient transmission errors, refer to the Q Corresponding MELSECNET/H Network System Reference Manual (PLC to PLC network)
(2) Error history monitoring tab
Figure 6.5 Error history monitoring tab
Table 6.7 Description of the Error history monitoring tab
Module information Error history monitoring Other station monitoring
Item Target module
Clear error history button Start monitoring , or Stop monitoring button
Description
Specify a MELSECNET/H for error history monitoring. (Default: 1)
Opens the Clear error history screen. (
Page 6-12,
Section 6.3 (3))
Starts or stops monitoring MELSECNET/H module.
"*" flashes in the upper right of the button during monitoring.
These buttons are disabled in the offline status.
Corresponding Corresponding
SB
SW
(To the next page)
6 - 9
6.3 Error History Monitoring Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
6 MELSECNET/H UTILITY
1
Table 6.7 Description of the Error history monitoring tab (continued)
Module information Error history monitoring Other station monitoring
Item Own station information
Start I/O No. Network No. Group No. Sta.No. Network Type Loop switching
Sta. No. Factor Switched status
Transient transmission errors
Err. code Error type
Description
Corresponding Corresponding
SB
SW
Displays the own station information of the MELSECNET/H module.
2
Displays the start I/O No. of the own station.
Displays the network No. of the own station.
SW0040
Displays the group No. of the own station.
SW0041
Displays the station No. of the own station.
SW0042
Displays the network to which the MELSECNET/H module is connected.
SB0057, SB005A
SW0046
Displays the type of the own station.
SB0044
3
Displays the factor of loop switching and the status after the
switching.
(For optical loop only)
Displays the number of the station that requested loop
SW00E0 to
switching or loopback.
SW00E7
Displays the factor of loop switching or loopback. Displays the data link status after loop switching.
SW00D0 to
SW00DF SW00D0 to
4
SW00DF
Displays error codes for transient transmission errors that
occurred on the own station.
For details of errors, refer to the Q Corresponding
MELSECNET/H Network System Reference Manual (PLC to
PLC network). Displays error codes that are reported during transient
SW00F0 to
5
transmission.
SW00FF
Displays types of errors that occurred during transient
transmission.
(To the next page)
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.3 Error History Monitoring Tab
6 - 10
6 MELSECNET/H UTILITY
Table 6.7 Description of the Error history monitoring tab
Module information Error history monitoring Other station monitoring
Item Number of error occurrences
Description
Displays the number of error occurrences. For details of factors and corrective actions, refer to the following.
Corresponding Corresponding
SB
SW
Loop switching Transient transmission errors Retry
Page 6-13, Section 6.3 (4) Displays the number of times that loop switching and loopback has been executed. "-" is displayed in the case of a coaxial bus system. Displays the number of transient transmission errors that has been occurred.
Displays the number of retries (for transmission errors).
Line trouble
"-" is displayed in the case of a coaxial bus system.
UNDER
Displays the number of UNDER errors that has been occurred.
CRC
Displays the number of CRC errors that has been occurred.
OVER
Displays the number of OVER errors that has been occurred.
Communication error
SHORTFRAME ABORT
Displays the number of short frame (too short data message) errors that has been occurred.
Displays the number of AB.IF errors that has been occurred.
TIMEOUT
Displays the number of timeout errors that has been occurred.
Exceeded 2KB DPLL ERROR
Displays the number of errors exceeding 2K bytes that has been occurred. Displays the number of DPLL (data not properly recognized in synchronization/modulation) errors.
SW00CE
SW00EE
SW00C8, SW00C9 SW00CC, SW00CD SW00B8, SW00C0 SW00B9, SW00C1 SW00BA, SW00C2 SW00BB, SW00C3 SW00BC, SW00C4 SW00BD, SW00C5 SW00BE, SW00C6 SW00BF, SW00C7
6 - 11
6.3 Error History Monitoring Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
6 MELSECNET/H UTILITY 1 (3) Clear error history screen Clear the number of errors to 0.
2
Figure 6.6 Clear error history screen
Item
Table 6.8 Description of the Clear error history screen
3
Description
Corresponding Corresponding
SB
SW
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.
SB0005
(Default: not checked (not cleared to 0))
Clear communication error counter
Select to clear the number of communication errors (link special register SW00B8 to SW00C7) to 0. (Default: not checked (not cleared to 0))
SB0006
4
Select to clear the number of forward loop side line errors (link
Clear F. loop transmission error special register SW00CC) to 0.
SB0007
(Default: not checked (not cleared to 0))
Select to clear the number of reverse loop side line errors (link
Clear R. loop transmission error special register SW00CD) to 0.
SB0008
(Default: not checked (not cleared to 0))
5
Select to clear the number of loop switching (link special
Clear loop switching counter
register SW00CE to SW00E7) to 0.
SB0009
(Default: not checked (not cleared to 0))
Select to clear the number of transient transmission errors (link
Clear transient transmission error special register SW00EE,SW00EF) to 0.
SB000A
(Default: not checked (not cleared to 0))
Execute button
Clears the item(s) selected on this screen. (Turns the corresponding SB of the selected item(s) from on to
6
off.)
Exit button
Closes the Clear error history screen.
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.3 Error History Monitoring Tab
6 - 12
6 MELSECNET/H UTILITY
Item Loop switching Transient transmission errors Retry Line trouble
UNDER
CRC
OVER SHORTFRAME
ABORT
TIMEOUT Exceeded 2KB DPLL ERROR
(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).
Table 6.9 Error factors and corrective actions
Link special register
Factor
Corrective action
SW00CE
SW00EE SW00C8, SW00C9 SW00CC, SW00CD SW00B8, SW00C0
SW00B9, SW00C1 SW00BA, SW00C2 SW00BB, SW00C3 SW00BC, SW00C4
SW00BD, SW00C5 SW00BE, SW00C6 SW00BF, SW00C7
Station's power on/off, cable fault, noise, etc.
Target station's power off, target station's CPU failure, cable fault, noise, etc.
Station's power on/off, cable fault, noise, etc. Adjacent station's power off, cable fault, noise, etc. Adjacent station's power on off, cable fault, etc. Source station of data transmission was disconnected, cable fault, hardware fault, noise, etc.
Page 6-13, Section 6.3 (4) (a) Check the error code of the transient transmission error, and take corrective actions.
Cable fault, hardware fault, noise, etc.
Page 6-13, Section 6.3 (4) (a)
Source station of data transmission was disconnected, cable fault, hardware fault, noise, etc. Too-short data link monitoring time, cable fault, noise, etc.
Cable fault, hardware fault, noise, etc.
(a) Errors other than transient transmission errors Unless the error count frequently increases during operation, no specific action is required. Take the following corrective actions if the error count frequently increases.
1) Check the status (on/off) of power supply for the own and other stations.
2) Check cables and connectors (for disconnection, loose connectors, broken cables, and improper cable lengths).
3) Conduct a self-loopback test, internal self-loopback test, and hardware test.
4) Conduct a station-to-station test and forward/reverse loop test.
5) Review its wiring, referring to the manuals for the network module and/or MELSECNET/H board used. Or, reinstall the system, referring to the user's manual for the CPU module used.
6 - 13
6.3 Error History Monitoring Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
6 MELSECNET/H UTILITY 1 6.4 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).
2
(1) Precautions for the Other station monitoring tab
(a) Monitoring status When MELSECNET/H utility is started, monitoring is in stop status.
Click the Start monitoring button to start monitoring.
3
(b) When a utility communication error has occurred
When a utility communication error has occurred during connection, click the
Start monitoring button or set the connection target again in the Connection settings so that the communication can be restarted.
(c) During reset Communications are not available while the C Controller module is being reset.
4
Start communications after the reset is complete.
(2) Other station monitoring tab
5
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
6
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
Figure 6.7 Other station monitoring tab
7
Table 6.10 Description of the Other station monitoring tab
Module information Error history monitoring Other station monitoring
Item
Target module Start monitoring or Stop monitoring button
Description
Select the MELSECNET/H module for monitoring. (Default: 1) Starts or stops monitoring the MELSECNET/H module. "*" flashes in the upper right of the button during monitoring. These buttons are disabled in the offline status.
Corresponding Corresponding
SB
SW
8
(To the next page)
6.4 Other Station Monitoring Tab
6 - 14
DEVICE MONITORING UTILITY
6 MELSECNET/H UTILITY
Table 6.10 Description of the Other station monitoring tab (continued)
Module information Error history monitoring Other station monitoring
Item Own station information
Start I/O No. Network No. Group No. Sta.No. Network Type
Other station information
Details button Other station information Error status
Description
Displays the own station information of the MELSECNET/H module. Displays the start I/O No. of the own station. Displays the network No. of the own station. Displays the group No. of the own station. Displays the station No. of the own station. Displays the network to which the MELSECNET/H module is connected. Displays the type of the own station.
Displays the error occurrence of the other stations. (
Page 6-15,
Section 6.4 (3))
Double-clicking an item opens the Details screen that displays the
detailed information of the item.
Opens the Details screen to display the detailed information of the
selected item. (
Page 6-15, Section 6.4 (3))
Displays errors in "Error status" when an error corresponding to the
item in "Other station information" has occurred.
Corresponding Corresponding
SB
SW
SB0057, SB005A SB0044
SW0040 SW0041 SW0042
SW0046
(3) Details screens
Detailed information of the item selected on the Other station monitoring tab are displayed on each screen below. The following lists the details screen corresponding to each item selected on the Other station monitoring tab.
Table 6.11 Other station monitoring tab selection and corresponding Details screen
Selection on the Other station monitoring tab
Communication status of each station Data link status of each station Parameter status of each station CPU operating status of each station CPU RUN status of each station Loop status of each station Reserved station designation of each station PSU operation states of each station extension Each station network type status
Corresponding Details screen
Communication status of each station screen Data link status of each station screen
Parameter status of each station screen
CPU operating status of each station screen CPU RUN status of each station screen Loop status of each station screen Reserved station designation of each station screen PSU operation states of each station extension screen
Each station network type status screen
Reference page
Page 6-16, Section 6.4 (3) (a) Page 6-17, Section 6.4 (3) (b) Page 6-18, Section 6.4 (3) (c)
Page 6-19, Section 6.4 (3) (d) Page 6-20, Section 6.4 (3) (e) Page 6-21, Section 6.4 (3) (f) Page 6-22, Section 6.4 (3) (g)
Page 6-23, Section 6.4 (3) (h)
Page 6-24, Section 6.4 (3) (i)
Remark
The information on the Details screens is based on the information when the screen was opened. To display the updated information, close and reopen the Details screen.
6 - 15
6.4 Other Station Monitoring Tab
6 MELSECNET/H UTILITY 1
(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.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
3
Figure 6.8 Communication status of each status screen
4
Table 6.12 Description of the Communication status of each status screen
Item
Description
Corresponding Corresponding
SB
SW
OK button
Closes the Communication status of each station screen.
Own station information
Displays the own station information of the MELSECNET/H module.
(
Page 6-14, Section 6.4 (2))
SB0044, SB0057, SB005A
SW0040, SW0041, SW0042, SW0046
5
Displays baton pass status (Availability of transient transmission)
Communication status of each
in the following color code.
SW0070 to
station
Light blue: Normally communicating station or reserved station
SW0073
Red: Communication error status (disconnected)
6
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.4 Other Station Monitoring Tab
6 - 16
6 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
OK button
Item
Own station information
Data link status of each station
Description
Closes the Data link status of each station screen.
Displays the own station information of the MELSECNET/H module.
(
Page 6-14, Section 6.4 (2))
Displays the cyclic transmission status in the following color code. Light blue: Normal or reserved station Red: Error station (Data link not performed)
Corresponding Corresponding
SB
SW
SB0044, SB0057, SB005A
SW0040, SW0041, SW0042, SW0046
SW0074 to SW0077
6 - 17
6.4 Other Station Monitoring Tab
6 MELSECNET/H UTILITY
1
(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.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
3
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
Figure 6.10 Communication status of each station screen
4
Table 6.14 Description of the Communication status of each station screen
Item
Description
Corresponding Corresponding
SB
SW
OK button Own station information
Closes the Communication status of each station screen.
Displays the own station information of the MELSECNET/H module.
(
Page 6-14, Section 6.4 (2))
SB0044, SB0057, SB005A
SW0040, SW0041, SW0042, SW0046
5
Communication status of each station parameter
Displays the parameter communication status of each station in the following color code. Light blue: Status other than "communicating with parameters", reserved station, or unconnected station Red: Communicating with parameters
SW0078 to
SW007B
6
Error status of each station parameter
Displays the parameter error status of each station in the following color code. Light blue: Parameters normal, reserved station, or unconnected station Red: Parameter error
SW007C to SW007F
7
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.4 Other Station Monitoring Tab
6 - 18
6 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
OK button
Item
Own station information
CPU operation status of each station
Description
Corresponding Corresponding
SB
SW
Closes the "CPU operation status of each station" screen.
Displays the own station information of the MELSECNET/H module.
(
Page 6-14, Section 6.4 (2))
Displays the CPU operation status in the following color code. Light blue: CPU normal, reserved station, unconnected station Red: CPU fault Medium error (WDT error, etc.) or, critical error (Hardware error, etc.) Yellow: CPU fault minor error
SB0044, SB0057, SB005A
SW0040, SW0041, SW0042, SW0046
SW0080 to SW0083, SW0088 to SW008B
6 - 19
6.4 Other Station Monitoring Tab
6 MELSECNET/H UTILITY 1
(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.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
3
OK button
Item
Own station information
CPU status
Figure 6.12 CPU RUN status of each station screen
4
Table 6.16 CPU RUN status of each station screen
Description
Corresponding Corresponding
SB
SW
Closes the CPU RUN status of each station screen.
Displays the own station information of the MELSECNET/H module.
(
Page 6-14, Section 6.4 (2))
SB0044, SB0057, SB005A
SW0040, SW0041, SW0042, SW0046
5
Displays the RUN/STOP status of each CPU. RUN: RUN, STEP RUN STOP: STOP, PAUSE DOWN: ERROR, or unconnected station Reserved Sta.: Reserved station
SW0084 to SW0087
6
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.4 Other Station Monitoring Tab
6 - 20
6 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.
Figure 6.13 Loop status of each station screen
OK button
Item
Own station information
F. loop status of each station
R. loop status of each station
Table 6.17 Description of the Loop status of each station screen
Description
Closes the Loop status of each station screen.
Displays the own station information of the MELSECNET/H module.
(
Page 6-14, Section 6.4 (2))
Displays the forward loop status in the optical loop system in the following color code. Light blue: Normal, reserved station, or unconnected station Red: Error station Displays the reverse loop status in the optical loop system in the following color code. Light blue: Normal, reserved station, or unconnected station Red: Error station
Corresponding Corresponding
SB
SW
SB0044, SB0057, SB005A
SW0040, SW0041, SW0042, SW0046
SW0091 to SW0094
SW0095 to SW0098
6 - 21
6.4 Other Station Monitoring Tab
6 MELSECNET/H UTILITY 1
(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.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
3
Figure 6.14 Reserved station designation of each station screen
4
Table 6.18 Description of the Reserved station designation of each station screen
Item
Description
Corresponding Corresponding
SB
SW
OK button
Closes the Reserved station designation of each station screen.
Own station information
Displays the own station information of the MELSECNET/H module.
(
Page 6-14, Section 6.4 (2))
SB0044, SB0057, SB005A
SW0040, SW0041, SW0042, SW0046
5
Displays the reserved station setting status in the following
Reserved station designation of each color code.
SW0064 to
station
Light blue: Non-reserved station
SW0067
Blue: Reserved station
6
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.4 Other Station Monitoring Tab
6 - 22
6 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
Item
Description
OK button Own station information
PSU operation status of each station extension
Closes the PSU operation status of each station extension.
Displays the own station information of the MELSECNET/H module.
(
Page 6-14, Section 6.4 (2))
Displays the 24VDC external power supply status of the MELSECNET/H module in the following color code. Light blue: No external power supply Blue: External power supply
Corresponding Corresponding
SB
SW
SB0044, SB0057, SB005A
SW0040, SW0041, SW0042, SW0046
SW008C to SW008F
6 - 23
6.4 Other Station Monitoring Tab
6 MELSECNET/H UTILITY
1
(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.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
3
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
Figure 6.16 Each station network type status screen
4
Table 6.20 Description of the Each station network type status screen
Item
Description
Corresponding Corresponding
SB
SW
OK button Own station information
Closes the Each station network type status screen.
Displays the own station information of the MELSECNET/H module.
(
Page 6-14, Section 6.4 (2))
SB0044, SB0057, SB005A
SW0040, SW0041, SW0042, SW0046
5
Each station network type status
Displays the consistency of the network types set in the control station and in the normal station in the following color code. Light blue: Normal, reserved, or communication error station whose network type is the same as that of the control station. Red: Normal station whose network type is different from that of the control station.
SW01E0 to SW01E3
6
7
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.4 Other Station Monitoring Tab
6 - 24
6 MELSECNET/H UTILITY
6.5 Online Operation Tab
Q12DCCPU-V
Q06CCPU-V
MELSECNET/H parameters can be read, written, or verified from this tab.
Q06CCPU-V-B
(1) Precautions for the Online operation tab
(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.
(b) During reset Communications are not available while the C Controller module is being reset. Start communications after the reset is complete.
(c) The drive to which parameters are written 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.
(2) Online operation tab
Figure 6.17 Online operation tab Table 6.21 Description of the Online operation tab
Online operation
Item
Target drive
Read parameters Read button
Parameter settings Target settings
Description Set a target drive for reading, writing, or verifying parameters.*1 This setting is not available for the Q06CCPU-V(-B). (Default: Parameter boot drive)
Reads out MELSECNET/H parameters from the C Controller module.
* 1 For the drives to which parameters can be written (user memory), refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
(To the next page)
6 - 25
6.5 Online Operation Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
6 MELSECNET/H UTILITY 1
Table 6.21 Description of the Online operation tab (continued)
Online operation Parameter settings Target settings
Item
Write parameters Write button
Verify parameters Verify button
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.
2
Parameters can be written only when "Write authority" is selected on the Connection settings screen. If "Write
authority" is not selected, select it in the Connection settings screen before writing parameters. (
Page
3-5, Section 3.5)
Compares the MELSECNET/H parameters of the C Controller module with those of the MELSECNET/H utility. The results are displayed in a message box.
Remark
3
Reading, writing, and verification of parameters can be performed only when the C Controller module and a development environment (personal computer) is connected online.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.5 Online Operation Tab
6 - 26
6 MELSECNET/H UTILITY
6.6 Parameter Settings Tab
Q12DCCPU-V
Q06CCPU-V
Parameters of the MELSECNET/H module can be set in this tab.
Q06CCPU-V-B
(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. When the defined parameters written from CC IE Control utility differs from that in
this utility, the following dialog box appears after clicking the Write button in the <<Online operation>> tab.
(2) Parameter settings tab
Figure 6.18 Dialog box
Figure 6.19 Parameter setting tab
Table 6.22 Description of the Parameter setting tab
Online operation Parameter settings Target settings
Item Number of modules
Description Set the number of MELSECNET/H modules controlled by the C Controller module. Selecting "(blank)" is regarded as no setting (setting clear). (Default: "(blank)")
(To the next page)
6 - 27
6.6 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
6 MELSECNET/H UTILITY
1
Table 6.22 Description of the Parameter setting tab (continued)
Online operation Parameter settings Target settings
Item Link device refresh cycle
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.
2
When enabling Block data assurance per station (
Page 6-37, Section 6.6 (6)), set 10 or more
to the "Link device refresh cycle" and set "Refresh parameters".
If 0 is set, refresh is not performed, all the settings for the refresh are cleared, and the
Refresh parameters button is disabled.
(Default: 100, Setting range: 0, 10 to 1000)
For details of the link device refresh cycle, refer to the C Controller Module User's (Hardware Design, Function Explanation).
3
Routing parameter button Target module
Start I/O No.
Channel No.
Refresh parameters button Check button Default button Operation settings
Network No. Group No. Network type Mode
Return
Displays the Routing parameter settings screen. (
Page 6-31, Section 6.6 (3))
Select a module to configure. (Default: 1)
The numbers for this item will be automatically rearranged in ascending order of start I/O numbers
when saving the parameter setting file or when switching the tab.
Set the start I/O No. of the MELSECNET/H module.
(Setting range: 0 to FE0H (Note that the number must be unique and cannot be duplicated with the start I/O No. of other MELSECNET/H module.)
4
Set the channel No. of the MELSECNET/H module.
Use this value when opening the channel from Device monitoring utility or a user program
(MELSEC data link function).
For the Q06CCPU-V-B, this setting is not available.
The channel No. must be unique and cannot be duplicated with a channel No. of other
MELSECNET/H modules.
Displays the Refresh parameter setting screen. (
Page 6-33, Section 6.6 (4))
5
When enabling Block data assurance per station, (
Page 6-37, Section 6.6 (6)), set 10 or
more to the "Link device refresh cycle" and set "Refresh parameters".
Checks for any setting error.
Set the operation settings, network range assignments, and refresh parameters back to default.
Operation settings for the MELSECNET/H module.
Set the network No. of the MELSECNET/H module.
6
(Default: 1, Setting range: 1 to 239)
Set the group No. of the MELSECNET/H module.
(Default: 0, Setting range: 0 to 32)
Set the type of the MELSECNET/H module.
(Default: "MNET/H mode (Control station)")
Set the mode of the MELSECNET/H module. (Default: "Online")
Return setting of the control station. This setting is available when any of the following is selected for "Network type".
7
·MNET/H mode (Control station)
·MNET/10 mode (Control station)
·MNET/H Ext. mode (Control station)
(Default: "Return as control station")
(To the next page)
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
6.6 Parameter Settings Tab
6 - 28
6 MELSECNET/H UTILITY
Table 6.22 Description of the Parameter setting tab (continued)
Online operation Parameter settings Target settings
Item Network range assignment
Total stations Assignment method Monitoring time Switch screens
Points Start End
Specify I/O master Sta. button Specify reserved Sta. button
Description Assign network ranges. ·MNET/H mode (Control station) ·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. (Default: 2) Switches the device range input method between Points/Start and Start/End. (Default: "Start/End") Set the monitoring time for the link scan time. (In increments of 10ms) (Default: 200, Setting range: 1 to 200) Select the link device to which network range is to be assigned. "Low speed LB" and "Low speed LW" can be set when MNET/H mode (Control station) or MNET/H Ext. mode (Control station) is selected for "Network type". (Default: "LB/LW settings") Set the No. of the link device points assigned to the target station. This setting is available when "Point/Start" is selected for "Assignment method".
(Default: "(blank)", Setting range:
Page 6-30, Section 6.6 (2) (a))
Set the start No. of the link device assigned to the target station.
(Default: "(blank)", Setting range:
Page 6-30, Section 6.6 (2) (a))
Set the end No. of the link device assigned to the target station.
This setting is available when "Start/End" is selected for "Assignment method".
(Default: "(blank)", Setting range:
Page 6-30, Section 6.6 (2) (a))
Sets the selected station as an I/O master station of the link device (LX/LY), or cancels the setting.
This button is enabled when "(LX/LY) settings (1)" or "(LX/LY) settings (2)" is selected for "Switch
screens".
Sets the selected station as a reserved station, or cancels the setting.
Equal assignment button Supplementary settings button Clear button
Displays the Equal assignment screen. (
Page 6-35, Section 6.6 (5))
Displays the Supplementary settings screen. (
Page 6-37, Section 6.6 (6))
Clears the "Points", "Start", and "End" settings and then sets the "Total stations" and "Monitoring
time" settings back to default.
6 - 29
6.6 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
6 MELSECNET/H UTILITY
1
(a) Network range assignment The following table indicates the setting ranges of network assignment.
Table 6.23 Setting ranges of network range assignment
Device LX
LY
LB
When "Network type"*3 is either of the following ·MNET/H mode (Control station) ·MNET/H Ext. mode (Control station)
LW
Lowspeed LB
Lowspeed LW
LB When "Network type"*3 is "MNET/10 mode (Control station)
LW
Points/Start/End Points Start End Points Start End Points Start End Points Start End Points Start End Points Start End Points Start End Points Start End
Setting range
16 to 8192*1
2
0000 to 1FF0*1
000F to 1FFF*2
16 to 8192*1
0000 to 1FF0*1
000F to 1FFF*2
16 to 16384*1
3
0000 to 3FF0*1
000F to 3FFF*2
1 to 16384
0000 to 3FFF
0000 to 3FFF
16 to 8192*1
2000 to 3FF0*1
4
200F to 3FFF*2
1 to 8192
2000 to 3FFF
2000 to 3FFF
16 to 8192*1
0000 to 1FF0*1 000F to 1FFF*2
5
1 to 8192
0000 to 1FFF
0000 to 1FFF
* 1 Only a multiple of 16 can be set to "Points" and "Start" of LX, LY, and LB.
* 2 Only a (multiple of 16 minus 1) can be set to "End" of LX, LY, and LB.
* 3 Set the "Network type" in the Parameter settings tab.
6
(
Page 6-27, Section 6.6 (2))
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.6 Parameter Settings Tab
6 - 30
6 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.
2. Routing parameters are common in the following channels. Different parameters cannot be set for each channel No. · MELSECNET/H (Channel No.51 to 54) · CC-Link IE Controller Network (Channel No.151 to 154)
Item Transfer target network No. Relay network No. Relay station No.
Figure 6.20 Routing parameter settings screen
Table 6.24 Description of the Routing parameter settings screen
Description Set the transfer target network No. (Default: "(blank)", Setting range: 1 to 239) Set the relay network No. (Default: "(blank)", Setting range: 1 to 239) Set the relay station No. (Default: "(blank)", Setting range: 1 to 120)
(To the next page)
6 - 31
6.6 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
6 MELSECNET/H UTILITY
1
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.
2
Only when the relay stations and target stations of transient transmission are the MELSEC-Q
Channel No.51 to Channel No.54
series network modules, select 960 words. When the relay stations and target stations of transient transmission are other than the MELSEC-Q
series network modules, select 480 words. If 960 words is set for this case, data may be cut off,
resulting in incorrect transient transmission.
(Default: 480 words)
Clear button Check button
Clears the "Transfer target network No.", "Relay network No.", and "Relay station No." settings.
3
Checks the "Transfer target network No.", "Relay network No.", and "Relay station No." settings.
End button
Saves the settings and closes the Routing parameter settings screen.
Cancel button
Closes the Routing parameter settings screen without saving the settings.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.6 Parameter Settings Tab
6 - 32
6 MELSECNET/H UTILITY
(4) Refresh parameter settings screen
Set refresh parameters.
Item Assignment method
Link side
Device name Points Start End CPU side Device name Points Start End Default button Check button End button Cancel button
Figure 6.21 Refresh parameter settings screen
Table 6.25 Description of the Refresh parameter settings screen
Description The device range input method can be switched between Points/Start and Start/End. (Default: "Start/End") Set the refresh parameters of the target module selected on the Parameter settings tab. Up to 64 refresh parameters can be set. Set a unique value for each device. Duplicated devices are not allowed. Set the name of the link device to be refreshed.
(Default:
Page 6-34, Section 6.6 (4) (a), Setting range:
Set the points of the link device to be refreshed.
Page 6-34, Section 6.6 (4) (b))
(Default:
Page 6-34, Section 6.6 (4) (a), Setting range:
Set the start No. of the link device to be refreshed.
Page 6-34, Section 6.6 (4) (c))
(Default:
Page 6-34, Section 6.6 (4) (a), Setting range:
Set the end No. of the link device to be refreshed.
Page 6-34, Section 6.6 (4) (c))
(Default:
Page 6-34, Section 6.6 (4) (a), Setting range:
Page 6-34, Section 6.6 (4) (c))
Displays refresh parameters of the CPU module.
Displayed data are corresponding to each setting in "Link side".
Displays the name of the device to be refreshed on the CPU module.
(Display:
Page 6-34, Section 6.6 (4) (b))
Displays the points of the device to be refreshed on the CPU module.
Displays the same start No. as the one in "Points" in the "Link side" field.
Displays the start No. of the device to be refreshed on the CPU module.
Displays the same start No. as the one in "Start" in the "Link side" field.
Displays the start No. of the device to be refreshed on the CPU module.
Displays the same start No. as the one in "End" in the "Link side" field.
Set the "Link side" and "CPU side" settings back to default.
Checks the "Link side" and "CPU side" settings for error.
Saves the settings and closes the Refresh parameter settings screen.
Closes the Refresh parameter settings screen without saving the settings.
6 - 33
6.6 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
6 MELSECNET/H UTILITY
1
(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 Trans.1 Trans.2 Trans.3 to Trans.64
Device name LB LW
Points 8192 8192
Start 0000 0000
"(Blank)"
End
1FFF
1FFF
2
(b) Device names
The following indicates the setting ranges of the "Device names" on the "Link
side", and the display of the "Device names" on the "CPU side".
Table 6.27 "Device names" on "Link side" and "CPU side"
3
"Link side" setting range
"CPU side" display
LX
LX buffer
LY
LY buffer
LB
LB buffer
LW
LW buffer
(c) Setting range on the link side The following indicates the setting ranges of the link side "Points", "Start", and
4
"End".
(The same setting ranges are applied to "Trans.1" to "Trans.64".)
Table 6.28 Setting ranges of link side "Points", "Start", and "End"
Device name
Points/Start/End
Setting range
Points
LX
Start
End
16 to 8192*1
0000 to 1FF0*1
5
000F to 1FFF*2
Points
16 to 8192*1
LY
Start
0000 to 1FF0*1
End
000F to 1FFF*2
Points
16 to 16384*1
LB
Start
End
Points
LW
Start
End
0000 to 3FF0*1
6
000F to 3FFF*2
1 to 16384
0000 to 3FFF
0000 to 3FFF
* 1 Only a multiple of 16 can be set to "Points" and "Start" of LX, LY, and LB.
* 2 Only a (multiple of 16 minus 1) can be set to "End" of LX, LY, and LB.
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.6 Parameter Settings Tab
6 - 34
6 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. - 1)) (a) When "LB/LW settings" is set for "Switch screens" in the Parameter settings tab.
Figure 6.22 Equal assignment screen (for LB/LW settings)
Table 6.29 Description of the Equal assignment screen (for LB/LW settings)
Item Identical point assignment
OK button Cancel button Equal assignment
LB equal assignment
Start station
Description Equally assigns entered points to the link devices of each station. (In increments of 16) (Default "(Blank)", Setting range: 16 or more) Validates the equal assignment setting according to entered values and closes the Equal assignment screen.
Discard the settings and closes the Equal assignment screen.
Equally divides the entered points and assigns them to the link devices of each station. Set the method for equal assignment to LB Set the first of the stations to which equal assignment will be performed. (Default "(Blank)", Setting range: 1 to (Value set in "Total stations")) The value for "Total stations" can be set in the "Network range assignment" in the Parameter
End station
settings tab. (
Page 6-27, Section 6.6 (2))
Set the last of the stations to which equal assignment will be performed.
(Default "(Blank)", Setting range: (Value set in "Start station" to "Total stations"))
The value for "Total stations" can be set on the "Network range assignment" in the Parameter
Start No. Total points assigned LW equal assignment Low speed LB equal assignment Low speed LW equal assignment
settings tab. (
Page 6-27, Section 6.6 (2))
Set the start No. of the link device to be equally assigned.
(Default "(Blank)", Setting range:
Page 6-30, Section 6.6 (2) (a))
Set the total points of the link devices to be equally assigned.
(Default "(Blank)", Setting range:
Page 6-30, Section 6.6 (2) (a))
Set the method for equal assignment to LW.
Set each item the same as for "LB equal assignment"
Set the method for equal assignment to low-speed LB.
Setting method is the same as for "LB equal assignment" described above.
Set the method for equal assignment to low-speed LW.
Setting method is the same as for "LB equal assignment" described above.
6 - 35
6.6 Parameter Settings Tab
6 MELSECNET/H UTILITY 1 (b) When "LX/LY settings (1)" or "LX/LY settings (2)" is set for "Switch screens" in the Parameter settings tab.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
3
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. (In increments of 16)
Identical point assignment
Note that the points will not be assigned to the station, which is set as the I/O master station. (
4
Page 6-27, Section 6.6 (2))
(Default "(Blank)", Setting range: 16 or more)
OK button
Validates the equal assignment setting according to entered values and closes the Equal assignment screen.
Cancel button
Discard the settings and closes the Equal assignment screen.
Equal assignment
Equally divides the entered points and assigns them to the link devices of each station.
M station to L station equal assignment
Set the method for equal assignment to LY(1) or LY(2).
5
Set the first of the stations to which equal assignment will be performed.
Start station
(Default "(Blank)", Setting range: 1 to (Value set in "Total stations")) The value for "Total stations" can be set in the "Network range assignment" in the Parameter
End station
settings tab. (
Page 6-27, Section 6.6 (2))
Set the last of the stations to which equal assignment will be performed.
(Default "(Blank)", Setting range: (Value set in "Start station" to "Total stations"))
6
The value for "Total stations" can be set in the "Network range assignment" in the Parameter
settings tab. (
Page 6-27, Section 6.6 (2))
Start No.
Set the start No. of the link device to be equally assigned.
(Default "(Blank)", Setting range:
Page 6-30, Section 6.6 (2) (a))
Set the total points of the link devices to be equally assigned.
Total points assigned
L station to M station equal
(Default "(Blank)", Setting range:
Page 6-30, Section 6.6 (2) (a))
Set the method for equal assignment to LX(1) or LX(2).
7
assignment
Setting method is the same as for "M station to L station equal assignment" described above.
8
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
6.6 Parameter Settings Tab
6 - 36
6 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 Constant scan Max. number of returned stations per scan
With multiplex transmission
Description Constant scan is used to maintain the link scan time at a constant time. Set a value to prevent fluctuation of the link scan time. (Unit: ms) (Default: "(Blank)"), Setting range: 1 to 500 Set the number of communication error stations that can return during one link scan. (Default: 2, Setting range: 1 to 64 ("Total stations" setting)) "Total station" can be set in the "Network range assignment" field in the Parameter settings tab.
(
Page 6-27, Section 6.6 (2))
Select this when executing the multiplex transmission function.
Multiplex transmission is used in the optical loop system to increase the transmission speed by
using both the forward and reverse loops simultaneously when they are in a normal condition.
This setting is available only when "Total stations" is set to 4 or more.
"Total station" can be set in the "Network range assignment" field in the Parameter settings tab.
(
Page 6-27, Section 6.6 (2))
(Default: Not selected (Not execute))
There is a data link thorough the subcontrolling station when the controlling station is down.
Select this when allowing another normal station on the network to continue communication (the control station switch function) as a alternate station (sub-control station) when the specified control station is disconnected due to some fault. (Default: Selected (Enable the control station switch function))
Select this when securing consistency*1 of link data for each station in cyclic transmission.
This enables to handle multiple word data without providing interlocks in the program.
Block send data assurance per station Note that this function*1 can be used only for the link device refresh processing between the C Controller module and MELSECNET/H module.
Set the following parameters when selecting any of these items for assuring data per station.
·"Link device refresh cycle" in the "Parameter settings" tab.
Block receive data assurance per station
(
Page 6-27, Section 6.6 (2))
·Refresh parameters in the "Refresh parameter settings" tab.
(
Page 6-33, Section 6.6 (4))
(Default:
Page 6-38, Section 6.6 (6) (a))
* 1 Securing consistency means preventing 2-word (32 bits) link data, such as the current value of the positioning module, from being divided into new and old data in units of 1 word (16 bits) due to cyclic transmission timing. The link device refresh processing between the C Controller module and MELSECNET/H module
can be set in the "Refresh parameter settings" tab. (
Page 6-33, Section 6.6 (4)).
(To the next page)
6 - 37
6.6 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
6 MELSECNET/H UTILITY
1
Table 6.31 Description of the Supplementary settings screen (continued)
Item
Description
Transient settings
Determine the conditions for transient transmission.
Max. number of transients per scan
Enter the number of transient transmissions (total of entire network) that can be performed by one network during one scan. (Default: 2, Setting range: 1 to 255)
2
Max. number of transients per
Enter the number of transient transmissions that can be performed by one station during one scan.
station
(Default: 2, Setting range: 1 to 10 ("Max. number of transients per scan" setting)
Set the execution conditions when sending link data (LB, LW) in slow cycles (low speed cyclic
Low speed cyclic transmission
transmission) in addition to the normal cyclic transmission.
settings
This setting is available only when "Low speed LB" and "Low speed LW" of "Network range
assignment" are set on the "Parameter settings" tab.
Transmit data of one station per scan
Select this when collectively sending data to another station per link scan.
3
Interval of fixed cycle
Low-speed cyclic transmission is performed at specified intervals. (Default: "(Blank)", Setting range: 1 to 65535 (Unit: Sec.))
Low-speed cyclic transmission is performed at specified time.
Any of "Hour", "Min.", and "Sec." settings cannot be skipped.
When no value are set to "Year", "Month", and "Day", the transmission is executed at specified time
Timer settings
every day.
When no value are set to "Year" and "Month", the transmission is executed at specified time every
4
month.
When no value is set to "Year", the transmission is executed at specified time every year.
(Default: "(Blank)", Setting range: 00:00:00, January 1, 2000 to 23:59:59, December 31, 2099)
End button
Saves the settings and closes the Supplementary setting screen.
Cancel button
Closes the Supplementary setting screen without saving the settings.
5
(a) "Block send data assurance per station" "Block receive data assurance per
station"
Default settings differ depending on the network type as follows. ( Section 6.6 (2))
Page 6-27,
Table 6.32 Network types and default
Network type
Default
6
MNET/H mode (Control station) MNET/10 mode (Control station)
Send and receive both deselected
MNET/H Extended mode (Control station)
Send and receive both selected
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.6 Parameter Settings Tab
6 - 38
6 MELSECNET/H UTILITY
6.7 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. Note that the logical station number setting is not required for the following access.
Page 6-41, "6.7 (4) Access that does not require a logical station No. setting"
(1) Precaution for the Target settings tab
Select a programmable controller CPU for the "Target module".
(2) The Target settings tab
Figure 6.25 Target settings tab Table 6.33 Description of the Target settings tab
Online operation Parameter settings Target settings
Item Target module Logical Sta. No.
Network No. Sta. No. Target CPU
Description Select the module to be configured. (Default: "Slot 1") Specify the logical station No. of the module selected in "Target module". (Default: 65, Setting range: 65 to 239) The logical station No. is logical numbers to be set in "Sta. No." in Device monitoring utility and MELSEC data link function (MELSECNET data link function). Set the network No. of the CC-Link IE Controller Network module and MELSECNET/H module controlled by the multiple CPU system. (Default: 1, Setting range: 1 to 239) Set the station No. of the CC-Link IE Controller Network module and MELSECNET/H module controlled by the multiple CPU system. (Default: 1, Setting range: 1 to 120) Set the CPU (CPU No. used in the multiple CPU system) to be accessed. (Default: 1, Setting range: 1 to 4)
Set button
Registers the settings (Logical Sta. No., Network No., Sta. No., and Target CPU) to the Target list.
(To the next page)
6 - 39
6.7 Target Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
6 MELSECNET/H UTILITY
1
Table 6.33 Description of the Target settings tab (continued)
Online operation Parameter settings Target settings
Target list
Item
Change button Delete button
Description
Displays a list of the Logical Sta. No. set to the module selected in "Target module" and the
corresponding network No., station No., and target CPUs Displays the data of the selected row (Logical sta. No.) in the Target list.
2
(Setting for the logical sta. No. can also be changed by double-clicking the row.)
Deletes the line (Logical sta. No.) selected in the Target list area.
(3) Access example
When the settings in the following screen are applied in the below system, a
MELSECNET/H module controlled by the C Controller module can access to the CPU No.4 via the MELSECNET/H module (controlled by CPU No. 2, network No. 1) by
3
using the logical station No. "65".
The access is also available by opening channel No. 51 and setting 65 for the station
No. in Device monitoring utility or a user program (MELSEC data link function).
C Controller module
Control station QJ71LP21G Slot 1, Channel No.51 (Controlled by C Controller module)
Normal station
QJ71LP21G Station No.: 5
4
(Controlled by CPU No.2)
CPU No.2
CPU No.4 *1
Multiple CPU system
5
MELSECNET/H
Network No.1
Figure 6.26 System configuration
* 1 When CPU No. 4 cannot configure a multiple CPU system, access to the CPU No. 4 is not
6
available by using the logical station number.
The target settings for the above access is shown below.
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
8
Figure 6.27 Target settings tab
6.7 Target Settings Tab
6 - 40
6 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.
Other station MELSECNET/H module
C Controller module
Control CPU of other station MELSECNET/H module
C Controller module
MELSECNET/H Figure 6.28 Access that does not require a logical station No. setting
MELSECNET/H
6 - 41
6.7 Target Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
6 MELSECNET/H UTILITY 1 6.8 System menu
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) System menu
2
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.
· Press the [Alt] key and then the [ ] key. · For Windows® 7 or later, right-click the icon ( ) on the task bar while pressing
3
the [Shift] key.
Item Move, Minimize, Close Specify CPU type
C Controller setting utility
Device monitoring utility Version information
4
Figure 6.29 System menu
Table 6.34 Description of the System menu
Description Refer to the Microsoft® Windows® manual.
5
Specifies a C Controller module to which parameters are set or to be monitored. ( Section 3.4) This item is not selectable during monitoring.
Page 3-4,
Starts C Controller setting utility. (
Page 4-1, CHAPTER 4)
While online, check that C Controller setting utility is connected to the same target device as for
MELSECNET/H utility.
6
Starts Device monitoring utility. (
Page 8-1, CHAPTER 8)
While online, check that Device monitoring utility is connected to the same target device as for
MELSECNET/H utility.
For the Q06CCPU-V-B, Device monitoring utility is not available.
Opens the Version information screen. (
Page 6-43, Section 6.8 (2))
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
6.8 System menu
6 - 42
6 MELSECNET/H UTILITY
(2) Version information screen
Displays the version information of MELSECNET/H utility.
Item Software package
SW3PVC-CCPU-E MELSECNET/H utility
OK button
Figure 6.30 Version information screen (Example: Version 3.01B) Table 6.35 Description of the Version information screen Description
Displays the version of SW3PVC-CCPU. Displays the update date of MELSECNET/H utility. Closes the Version information screen.
6 - 43
6.8 System menu
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
6 MELSECNET/H UTILITY 1 6.9 Precautions
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Parameter details
2
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.
3
(3) 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.
(4) Tabs available to operate offline
When MELSECNET/H utility connection is offline, data can be set only in the Parameter settings tab and the Target settings tab.
4
For the Q06CCPU-V-B, only parameters shown in the Target settings tab can be set.
(5) Terminating Microsoft® Windows®
Do not terminate Microsoft® Windows® while MELSECNET/H utility is running.
Terminate MELSECNET/H utility first and then Microsoft® Windows®.
5
(6) 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.
6
(7) Time required for connection from each utility to the C Controller
module
The following time is required for the C Controller module to connect to each utility
after power-on or reset.
· When executing a script file, "STARTUP.CMD":
Upon completion of the RUN LED flashing.
7
· When not executing a script file, "STARTUP.CMD":
Fifteen (15) seconds after completion of start or reset
Do not attempt a connection before the above time has elapsed after completion of
power-on or reset.
Changing "Priority" to a larger value in the Option tab of C Controller setting utility
increases the time after which the C Controller module can be connected.
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
6.9 Precautions
6 - 44
7 CC IE CONTROL UTILITY
CHAPTER 7 CC IE CONTROL UTILITY
7.1 CC IE Control Utility Function List
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Name
Specify CPU type
Connection settings Parameter setting file saving/loading Module information display Online operation Parameter settings
Target settings
Table 7.1 CC IE Control utility function list
Description
Specifies a C Controller module for parameter setting and monitoring. Sets the C Controller module to which CC IE Control utility is to be connected.
Applicability
Q12DCCPU Q06CCPU
-V
-V
Reference page
Page 3-4
Page 3-5
Saves parameters set in CC IE Control utility into a file or loads the file.
Page 3-14
Displays information on the CC-Link IE Controller Network module (own station) that is controlled by the connected C Controller module.
Page 7-2
Reads, writes, or verifies CC-Link IE Controller Network parameters.
Page 7-20
Sets parameters for the CC-Link IE Controller Network modules.
Page 7-23
Sets a logical station number for access to a CPU module in a multiple
CPU system when a CC-Link IE Controller Network module is mounted in
Page 7-34
the system.
: Applicable, : Applicable but partially restricted, : N/A
7 - 1
7.1 CC IE Control Utility Function List
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY 1 7.2 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.
2
(1) Precautions for the Module information tab
(a) When a utility communication error has occurred When a utility communication error has occurred during connection, click the
Start monitoring button or set the connection target again in the Connection
3
settings so that the communication can be restarted.
(b) During reset Communications are not available while the C Controller module is being reset. Start communications after the reset is complete.
(2) Module information tab
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
6
Figure 7.1 Module information tab
Table 7.2 Description of Module information tab
Module information Online operation Parameter settings Target settings
Item
Description
7
Corresponding Corresponding
SB
SW
Displays the total link device refresh time required to refresh the
Link device refresh time MELSECNET/H and CC-Link IE Controller Networks, which are controlled
by the C Controller module (host CPU). (In increments of ms)
Displays the maximum total link device refresh time recorded in the past.
Max.
When Link device refresh cycle (
Page 7-23, Section 7.5) is 0ms, "-"
8
appears.
Displays the minimum total link device refresh time recorded in the past.
Min.
When Link device refresh cycle (
Page 7-23, Section 7.5) is 0ms, "-"
appears.
(To the next page)
7.2 Module Information Tab
7 - 2
DEVICE MONITORING UTILITY
7 CC IE CONTROL UTILITY
Table 7.2 Description of Module information tab (continued)
Module information Online operation Parameter settings Target settings
Item Link device refresh time
Current
Diagnostics button Start monitoring or Stop monitoring button 1 Slot to 4 Slot
Start I/O No. Channel No.
Network No.
Group No. Sta. No. Type
Status
Link scan time Save SB/SW button
Description
Displays the current total link device refresh time.
When Link device refresh cycle (
Page 7-23, Section 7.5) is 0ms, "-"
appears.
Displays the "CC IE Control Network diagnostics result" screen.
(
Page 7-5, Section 7.3)
This button cannot be clicked in the offline status.
Starts or stops monitoring the CC-Link IE Controller Network module.
"*" flashes in the upper right of the button during monitoring.
These buttons are disabled in the offline status.
Displays CC-Link IE Controller Network module information in order of
start I/O No.
Displays the start I/O No. of the CC-Link IE Controller Network module.
Displays the channel No. of the CC-Link IE Controller Network module.
When the "Channel No." parameter is not specified (
Page 7-23,
Section 7.5), "-" appears.
Displays the network No. of the CC-Link IE Controller Network module.
When the "Network No." parameter is not specified (
Page 7-23,
Section 7.5), "-" appears.
Displays the group No. of the CC-Link IE Controller Network module.
When the "Group No." parameter is not specified (
Page 7-23,
Section 7.5), "-" appears.)
Displays the station No. of the CC-Link IE Controller Network module.
Displays the type of the CC-Link IE Controller Network module.
Displays the communication status of the CC-Link IE Controller Network
module as one of the following.
· In data link
· Suspend data link
· Baton passing
· Suspend baton pass
· Offline testing
· Offline
Displays the link scan time of the CC-Link IE Controller Network module.
(In increments of ms)
Saves information of the CC-Link IE Controller Network module's link
special relay (SB) and link special register (SW) into a CSV file. ( Page 7-4, Section 7.2 (3))
Corresponding Corresponding
SB
SW
SW0040
SB0044
SW0041 SW0042
SW0047
7 - 3
7.2 Module Information Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY 1 (3) Specifications of the SB/SW save file A file format can be selected in "Save as type" on the following screen.
2
Figure 7.2 SaveAs screen
3
To use the text data of the SB/SW save file in a user program etc, select "SBSWSave
File(*.csv)" when saving.
To use them on Microsoft® Excel etc., select "SBSWSave File[Form2](*.csv)" when
saving.
When "SBSWSave File(*.csv)" is selected
When "SBSWSave File[Form2](*.csv)" is selected
4
Figure 7.3 Example of SB/SW save files
Remark
5
The folder of the SB/SW save file is "C:\MELSEC\CCPU\Param" by default (when SW3PVC-CCPU has been installed in "C:\MELSEC").
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.2 Module Information Tab
7 - 4
7 CC IE CONTROL UTILITY
7.3 Diagnostics Result Screen
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Clicking the Diagnostics 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 destination" window is displayed prior to "CC IE Control Network diagnostics result". Select a network to be diagnosed and click the OK button.
7 - 5
Figure 7.5 Select diagnostics destination screen
7.3 Diagnostics Result Screen
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY 1
Table 7.3 Description of Select diagnostics destination
Item Change module button
Selected station
Description
Displays the Select diagnostics destination" screen when there are two or more CC-Link IE Controller
Network modules that are controlled by the C Controller module.
Change the network to one that is to be diagnosed. Entering a station No. and clicking the Change station button changes the display to the one for the
2
selected station.
The status of the selected station is displayed in the "Network device status of selected station" area.
(Default: Station No. of the connected station, Setting range: 1 to 120)
Change station button
Determines the entry in "Selected station".
Start monitoring button
Starts automatic updating of "CC IE Control Network diagnostics result".
Stop monitoring button
Stops automatic updating of "CC IE Control Network diagnostics result".
3
Network information
Displays the link status and station status of the network.
(
Page 7-7, Section 7.3 (1))
Network device status of selected Displays the detailed information on the selected station.
station
(
Page 7-10, Section 7.3 (2))
Displays the "Communication Test" screen.
Communication test button
(
Page 7-13, Section 7.3 (3))
Displays the "Link start/stop" screen.
4
Link start/stop button
(
Page 7-15, Section 7.3 (4))
Logging button
Displays the "Logging" screen.
(
Page 7-16, Section 7.3 (5))
Close button
Closes the "CC IE Control Network diagnostics result" screen.
5
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.3 Diagnostics Result Screen
7 - 6
7 CC IE CONTROL UTILITY
(1) Network information
The link status and station status of the network are displayed.
Item Module Network No. Total no. of stations I/O master station Link scan time
Icons
Prev button Next button
Figure 7.6 Network information display
Table 7.4 Description of Network information display
Description Displays the module on the network, which is being diagnosed. The number corresponds to one of Slots 1 to 4 on the "Module information" screen. Displays the network No. of the network being diagnosed. Displays the total number of connected and reserved stations. Displays the station No. of the I/O master station on the network being diagnosed. Displays the current link scan time. (In increments of ms) Displays each station status or inter-station status.
(
Page 7-8, Section 7.3 (1) (a))
Switches the screen when the total number of stations is 61 or more.
7 - 7
7.3 Diagnostics Result Screen
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
7 CC IE CONTROL UTILITY 1
(a) Icons Each icon represents its station status or inter-station status.
1)
2)
2
3)
4)
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.
3
2) Connected This word is shown for the station connected to the CC IE Control utility (own station).
3) Icons
The meanings of the icons are listed below.
4
Table 7.5 Descriptions of icons
Icon
Description
Normally operating station
Faulty station
Although cyclic transmission is performed, a fault has occurred on any of the following: ·CC-Link IE Controller Network module
5
·CC-Link IE Controller Network interface board
·Cable
Faulty station (Cyclic station is stopped.)
Disconnected station (black)
Reserved station (gray)
6
Selected station (an icon in a green frame)
·To select, click a station icon, or move the focus with the left and right arrow keys and
press the space key.
·The detailed information is displayed in "Network device status of selected station".
·Disconnected or reserved stations are not selectable.
Being focused (an icon in a dotted line frame) ·To make it selected, press the space key.
7
·Disconnected or reserved stations are not selectable.
Communication error
·Selecting the station next to a faulty station will display the detailed information in the
"Network device status of selected station" area.
4) Present control station and Specified control station Present control station: Station that is actually operating as a control station
8
Specified control station: Control station that is set with a parameter
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
7.3 Diagnostics Result Screen
7 - 8
7 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.
· All stations are in data link status. (Cyclic transmission status of each station (SB00B0) is off.)
· No loopback station (Loopback status (SB0065) is off.) · No station has a parameter error. (Parameter status of each station
(SB00E0) is off.) · The number of actually connected stations is the same as the total
number of stations (except reserved stations) set on the control station. If all the above conditions are met again after any of them was not met, the normal connection information will be updated.
POINT
(1) For acquisition of normal connection information, there are restrictions on the version of the CC-Link IE Controller Network module that is directly connected to CC IE Control utility. Check the version of the CC-Link IE Controller Network module. CC-Link IE Controller Network Reference Manual
(2) After acquisition of normal connection information, if the network configuration is changed with a cable or station disconnected, the changes cannot be displayed correctly. Update the information as instructed below. (If the network has an error, however, normal connection information cannot be obtained, and the condition is displayed as it is.) · Set Normal connection information refresh instruction (SB000C) to on. CC-Link IE Controller Network Reference Manual · Power off and then on, or reset the connected station. · Take corrective actions to set all stations into normal states.
(3) If a station that is not included in the normal connection information is added, it is displayed on the IN side of the CC IE Control utility connected station.
2) If the station has not obtained normal connection information A disconnected station is displayed on the IN side of the CC IE Control utility connected station.
7 - 9
Figure 7.9 When the disconnected station has not obtained normal connection information
7.3 Diagnostics Result Screen
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
7 CC IE CONTROL UTILITY 1 (2) Network device status of selected station The detailed information of a selected station is displayed.
2
Figure 7.10 Network device status of selected station
3
Table 7.6 Description of Network device status of selected station
Item
Display
Description
Group No.
Displays the group No. of the selected station. (Range: 0 to 32)
Mode
Displays the mode of the selected station.
(Display item: "Online", "Line test")
Normal operation
4
Operating status
Error (data link continued) (yellow)
Error (data link stopped) (red)
LEDs of selected station network device
Displays the operating status of the selected station.
(
Page 7-11, Section 7.3 (2) (a))
5
In data link
Communication status Error details button
Cable disconnection
6
Communication error (other than cable disconnection)
Module error (CC-Link IE Controller Network parameter error or transient transmission error)
Displayed in the faulty area.
, etc.
(
Page 7-12, Section 7.3 (2) (b))
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.3 Diagnostics Result Screen
7 - 10
7 CC IE CONTROL UTILITY
(a) LEDs of the selected station network device The operating status of the selected station is displayed.
LED RUN MODE SD
ERR.
PRM D LINK RD EXT.PW*1
Figure 7.11 LEDs of the selected station network device
Table 7.7 Description of LEDs of the selected station network device
LED status On, green Off On, green Flashing, green Off On, green Off
On, red
Off On, green Off On, green Flashing, green Off On, green Off On, green Off
Description In normal operation Hardware fault or watchdog timer error Online mode Test mode Offline mode Sending data Not yet sending data ·Received data are erroneous. (Receive frame error) ·A certain level frame error has occurred between stations. ·Control station or station No. is duplicated. ·Cables are disconnected or incorrectly connected between OUT and IN. ·Network parameters are corrupted, or some settings (reserved station setting, total number of stations, network No., etc.) are inconsistent between control and normal stations. Normal status Operating as a control station Operating as a normal station In data link (cyclic transmission operated) In data link (cyclic transmission stopped) Not yet in data link (being disconnected) Receiving data Not yet receiving data External power is being supplied External power not yet supplied
* 1 Displayed only when the module is equipped with an external power supply.
7 - 11
7.3 Diagnostics Result Screen
7 CC IE CONTROL UTILITY 1 (b) Error details button Clicking the button displays the "Error details" screen. The detailed information, error factor, and troubleshooting tips are displayed.
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
3
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
4
Figure 7.12 Error details screen
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.3 Diagnostics Result Screen
7 - 12
7 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.
Item Communication test details
Network No. Station No. Length Communication count W.D.T. Execute test button Communication test result <<Outward>> tab <<Inward>> tab
Network No.
Station No.
Figure 7.13 Communication Test screen
Table 7.8 Description of Communication Test screen
Description Set the destination and communication data. Set a network No. of the destination. (Default:1, Setting range: 1 to 239) Set a station No. of the destination. (Default: 1, Setting range: 0 (I/O master station), 1 to 120 (control/normal station)) Set a communication data length. (Default: 100, Setting range: 1 to 900) Specify how many times the communication is to be made. (Default: 1, Setting range: 1 to 100) Set a timeout time for the communication test (in units of seconds). (Default: 5, Setting range: 1 to 100)
Executes the communication test.
Displays the destination and communication data. Displays the numbers of the networks and stations that are on the route from the source station (connected station) to the specified destination. Displays the numbers of the networks and stations that are on the route back from the specified destination to the source station (connected station). Displays the network No. of the turn-around point on the way from the source station (connected station) to the specified destination. (Range: 1 to 239) Displays the station No. of the turn-around point on the way from the source station (connected station) to the specified destination). (Range: 0 to 120)
(To the next page)
7 - 13
7.3 Diagnostics Result Screen
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY 1
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.
2
Communication count
Displays how many times the communication has been made. (Range: 1 to 100)
Communication time
Displays the communication time. (In increments of 100ms) (Range: 0 or greater)
Destination
Displays the information on the destination.
Network No.
Displays the network No. that was entered in the Target settings.
Station No.
Displays the station No. that was entered in the Target settings.
3
Close button
Closes the "Communication Test" screen.
Remark
On the default screen, only the communication test setting area is displayed as
below.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
MELSECNET/H UTILITY
6
Figure 7.14 Default Communication Test screen
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.3 Diagnostics Result Screen
7 - 14
7 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
Item Network information
Network Type Network No. Group No. Station No. Status of all stations
Selected/non-selected
Station No.
Link status Group Type
Link start/stop
Execute button Close button
Table 7.9 Description of Link start/stop screen
Description Displays the information on the selected network (own station). Displays the name of the selected network (own station). (Display item: "CC IE Control" (fixed)) Displayed the station type of the selected network (own station). (Display item: "Controller network control station", "Controller network normal station") Displays the network No. of the selected network (own station). Displays the group No. of the selected network (own station). Displays the station No. of the selected network (own station). Displays the information on each station that is connected to the selected network (own station). Select a station to start or stop the link. By right-clicking on each information area in "Status of all stations", a pop-up menu appears. From the pop-up menu, the displayed status can be changed. (Default: Not checked (Link start or stop)) Displays station No. on the specified network. Reserved station numbers are not displayed. (Range: 1 to 120) Displays the link status of a station on the specified network. (Display item: "Linking (blue)", "Suspended (red)") Displays the group No. of a station on the specified network. (Range: 0 to 32) Displays the type of a station on the specified network. (Display item: "Control station", "Normal station") Specify the link start or stop. When "Forced start" is selected, the link can be started from a station other than the stop-requested station. (Default: "Start")
Executes the operation selected in the Link start/stop setting for the selected station.
Closes the "Link start/stop" screen.
7 - 15
7.3 Diagnostics Result Screen
7 CC IE CONTROL UTILITY 1
(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
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
3
Item Connected station
Network No.
Group No.
Station No.
Figure 7.16 Logging screen
Table 7.10 Description of Logging screen
Description Displays the information on the connected stations. Displays the network No. of the connected station. (Range: 1 to 239) Displays the group No. of the connected station. (Range: 0 to 32) Displays the station No. of the connected station. (Range: 1 to 120)
4
5
(To the next page)
6
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.3 Diagnostics Result Screen
7 - 16
7 CC IE CONTROL UTILITY
Item <<Monitoring details>> tab
Transmission path switch Loop status Loopback station IN Loopback station OUT Date/time
Transient transmission error Error code
Target network
Target station No. Date/time
Table 7.10 Description of Logging screen (continued)
Description Displays logs in the Transmission path switch and Transient transmission error areas. Up to 100 transmission path switch logs can be displayed. If more than 100 logs have occurred, the oldest log will be deleted to record the latest log. Displays the information on the transmission lines on the entire network. (Display item: "Normal", "Loopback", "Error in all stations") Displays the station No. of the station where an IN-side loopback has occurred. (Range: 1 to 120) Displays the station No. of the station where an OUT-side loopback has occurred. (Range: 1 to 120) Displays the date and time at which the transmission path was switched. Displays up to 100 transient transmission error logs. If more than 100 logs have occurred, the oldest log will be deleted to record the latest log. Displays error codes. For details of the error codes, refer to the CC-Link IE Controller Network Reference Manual. When a transient transmission error has occurred, the network No. of the error-detected station is displayed. (Range: 1 to 239) When a transient transmission error has occurred, the station No. of the error-detected station is displayed. (Range: 1 to 120) Displays the date and time at which the transient transmission error occurred. Saves the <<Monitoring details>> tab data to a CSV file.
Select a CSV file format by clicking the Browse button.
(
Page 7-19, Section 7.3 (6))
Save error log button
Start monitoring button Stop monitoring button
·Drive/Path: Specify where the CSV file is saved. ·File name: Specify a name for the CSV file to be saved.(*.csv) Starts or stops the on-screen Logging monitoring.
During monitoring, the Start monitoring button is enabled. While monitoring is stopped, the Start monitoring button is enabled. When a utility communication error has occurred, the Start monitoring and Stop monitoring buttons will be disabled.
(To the next page)
7 - 17
7.3 Diagnostics Result Screen
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY 1
Table 7.10 Description of Logging screen (continued)
Item
Description
<<Clear error>> tab
Clears the errors.
Clear communication error counter
The communication error counter can be cleared to zeros. (Default: Checked (Clears to 0))
Clear IN side transmission error counter
The areas for detected IN-side line errors (SW0068, SW0069, SB006E, SB0140, SW0074, and
2
SW0140 to SW0147) can be cleared to zeros.
(Default: Checked (Clears to 0))
Clear OUT side transmission error counter
The areas for detected OUT-side line errors (SB006F, SB0150, SW006A, SW006B, SW0084, and SW0150 to SW0157) can be cleared to zeros. (Default: Checked (Clears to 0))
The areas for path switch detection of the own station (SB008E, SB0160, SW006E, and
Clear loop switching counter
SW0160 to SW0167) can be cleared to zeros. (Default: Checked (Clears to 0))
3
The areas for transient transmission errors of the own station (SB008F, SB0170, SW006F, and
Clear transient transmission error
SW0170 to SW0177) cam be cleared to zeros.
(Default: Checked (Clears to 0))
Clear error info. button
Clears the selected information.
Closes the "Logging" screen.
Close button
The 17th and later logs displayed are deleted when this screen is closed. To save all of the displayed logs, click the "Save error log" button.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.3 Diagnostics Result Screen
7 - 18
7 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. To save the file, go back to the error log save screen by clicking the Open button after selecting the format.
Figure 7.17 Open screen
To use the text data of the SB/SW save file in a user program etc, select "Error Log File(*.csv)" when saving. To use them on Microsoft® Excel etc., select "Error Log File[Form2](*.csv)" when saving.
(a) For Transmission path switch The following data are saved in an error log file for transmission path switch. · Loop status · Loopback station No. (IN side) · Loopback station No. (OUT side) · Date and time The following is an example error log file for transmission path switch.
When "Error Log File(*.csv)" is selected
When "Error Log File[Form2](*.csv)" is selected
Figure 7.18 Examples of error log files (Transmission path switch)
(b) For Transient transmission error The following data are saved in an error log file for transient transmission errors. · Error code · Network No. · Station No. · Date and time The following is an example error log file for transient transmission errors.
When "Error Log File(*.csv)" is selected
When "Error Log File[Form2](*.csv)" is selected
7 - 19
Figure 7.19 Examples of error log files (Transient transmission error)
Remark Only the logs displayed in the <<Monitoring details>> tab can be saved in an error log file by clicking the Save error log button.
7.3 Diagnostics Result Screen
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY 1 7.4 Online Operation Tab
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
The CC-Link IE Controller Network parameters can be read, written, or verified from this tab.
2
(1) Precautions for the Online operation tab
(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.
3
(b) During reset Communications are not available while the C Controller module is being reset. Start communications after the reset is complete.
(c) The drive to which parameters are written
When writing parameters from each of the utilities to the following C Controller
4
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.
(2) Online operation tab
5
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
6
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
7
Figure 7.20 Online operation tab
Table 7.11 Description of Online operation tab
Module information Online operation Parameter settings Target settings
Item Target drive
Description
Set a target drive for reading, writing, or verifying parameters.*1 This setting is not available for the Q06CCPU-V(-B).
8
(Default: Parameter boot drive)
* 1 For the drives to which parameters can be written (user memory), refer to the C Controller Module
User's Manual (Hardware Design, Function Explanation).
(To the next page)
7.4 Online Operation Tab
7 - 20
DEVICE MONITORING UTILITY
7 CC IE CONTROL UTILITY
Table 7.11 Description of Online operation tab (continued)
Module information Item
Read parameters Read button
Write parameters Write button
Verify parameters Verify button
Online operation
Parameter settings Target settings Description
Reads CC-Link IE Controller Network parameters from the C Controller module.
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 reset. Parameters can be written only when "Write authority" is selected in Connection settings. If "Write authority" is not selected, select it in the Connection settings screen before writing parameters.
(
Page 3-5, Section 3.5)
Check for consistency between the CC-Link IE Controller Network parameters of the C Controller
module and those set in CC IE Control utility.
The verification results are shown in a message box.
If a mismatch is found, a message appears and prompts the user to save the results to a file.
(
Page 7-22, Section 7.4 (3))
Remark
Reading, writing, and verification are available while the C Controller module is connected online to the development environment (personal computer).
7 - 21
7.4 Online Operation Tab
OVERVIEW
7 CC IE CONTROL UTILITY 1
(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 Yes button and enter appropriate data on the following screen.
2
The verification results file is saved in text format.
For "Save as" operations, refer to the following.
Page 3-14, Section 3.8
3
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
4
Figure 7.21 Save As screen
The following is an example of a verification results file.
5
Remark
The default folder for saving a verification results file is
"C:\MELSEC\CCPU\Param" (when SW3PVC-CCPU has been installed in
"C:\MELSEC").
6
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.4 Online Operation Tab
7 - 22
7 CC IE CONTROL UTILITY
7.5 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. When some of the set values written from MELSECNET/H utility are different from
those set in this utility, clicking the Write button in <<Online operation>> will display the following dialog box.
(2) Parameter settings tab
Figure 7.22 Dialog box
Figure 7.23 Parameter settings tab
Table 7.12 Description of Parameter settings tab
Module information Online operation Parameter settings Target settings
Item Number of modules
Description Set the number of CC-Link IE Controller Network modules that are to be controlled by the C Controller module. Selecting "(Blank)" means no setting (Setting cleared). (Default: "(Blank)")
(To the next page)
7 - 23
7.5 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
7 CC IE CONTROL UTILITY
1
Table 7.12 Description of Parameter settings tab (continued)
Module information Online operation Parameter settings Target settings
Item Link device refresh cycle
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.
2
To enable the "Block data assurance per station" setting (
Page 7-33, Section 7.5 (7)), enter
10ms or more for "Link device refresh cycle", and set refresh parameters.
Setting 0 for "Link device refresh cycle" disables any refresh with all refresh parameter settings
deleted, and disables the Refresh parameters button.
(Default: 100, Setting range: 0, 10 to 1000)
For further details, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
3
Routing parameter button Target module Start I/O No.
Channel No.
Default button Check button Refresh parameters button
Displays the "Routing parameter settings" screen. (
Page 7-25, Section 7.5 (3))
Select a module to configure. (Default: 1)
The numbers for this item will be automatically rearranged in ascending order of start I/O numbers
when saving the parameter setting file or when switching the tab.
Set a start I/O No. of a CC-Link IE Controller Network module.
(Setting range: 0 to FE0H (The set value must be unique, and not duplicated with the one for another CC-Link IE Controller Network module.))
4
Set a channel No. of a CC-Link IE Controller Network module.
The set value is used to open the channel from Device monitoring utility or a user program
(MELSEC data link functions).
Channel No. must be unique, and not duplicated with the one for another CC-Link IE Controller
Network module.
Sets the operation settings, network range assignments, and refresh parameters to default values.
Checks for any setting error.
5
Displays the "Refresh parameter settings" screen. (
Page 7-27, Section 7.5 (4))
To enable the Block data assurance per station" setting (
Page 7-33, Section 7.5 (7)), enter
10ms or more for "Link device refresh cycle", and set refresh parameters.
Network range assignment button
Displays the "Network range assignment" screen. (
Page 7-29, Section 7.5 (5))
When "CC IE Control (Control station)" is selected for "Network type", this button is enabled.
Operation settings
Specify the CC-Link IE Controller Network module operation.
6
Network type
Set a type of the CC-Link IE Controller Network module. (Default: "CC IE Control (Control station)")
Set a mode of the CC-Link IE Controller Network module.
Mode
"Line test" can be set when "CC IE Control (Control station)" is selected for "Network type".
(Default: "Online")
Network No. Group No.
Set a network No. of the CC-Link IE Controller Network module. (Default: 1, Setting range: 1 to 239) Set a group No. of the CC-Link IE Controller Network module. (Default: 0, Setting range: 0 to 32)
7
Station No.
Set a station No. of the CC-Link IE Controller Network module. (Default: 1, Setting range: 1 to 120)
8
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
7.5 Parameter Settings Tab
7 - 24
7 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.
2. Common routing parameters must be used for the following channels. Different settings for each channel No. are not allowed. · CC-Link IE Controller Network (Channel No.151 to 154) · MELSECNET/H (Channel No.51 to 54)
Item Transfer target network No. Relay network No. Relay station No.
Figure 7.24 Routing parameter settings screen
Table 7.13 Description of Routing parameter settings screen
Description Set a transfer target network No. (Default: "(Blank)", Setting range: 1 to 239) Set a relay network No. (Default: "(Blank)", Setting range: 1 to 239) Set a relay station No. (Default: "(Blank)", Setting range: 1 to 120)
(To the next page)
7 - 25
7.5 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY
1
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.
2
Only when all of the relay and target stations of the transient transmission are MELSEC-Q series
Channel No.151 to
network modules, select 960 words.
Channel No.154
Select 480 words if a module other than the MELSEC-Q series network modules is included in the
relay and target stations. Setting 960 words in this case may truncate some of the data, disabling
normal transient transmission.
(Default: 480 words)
Clear button Check button
Clears the "Transfer target network No.", "Relay network No.", and "Relay station No." settings.
3
Checks the "Transfer target network No.", "Relay network No.", and "Relay station No." settings.
End button
Saves the settings and closes the "Routing parameter settings" screen.
Cancel button
Closes the "Routing parameters settings" screen without saving the settings.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.5 Parameter Settings Tab
7 - 26
7 CC IE CONTROL UTILITY
(4) Refresh parameter settings screen
Refresh parameters are set on this screen.
Item Assignment method
Link side
Device name Points Start End CPU side Device name Points Start End Default button Check button End button Cancel button
Figure 7.25 Refresh parameter settings screen
Table 7.14 Description of Refresh parameter settings screen
Description How to enter the device range data can be switched between Points/Start and Start/End styles. (Default: "Start/End") Set refresh parameters of the module selected on the "Parameter settings" tab. Up to 64 refresh parameters can be set. Since duplicated device setting is not allowed, prevent any overlapped settings. Set a link device name to be refreshed.
(Default:
Page 7-28, Section 7.5 (4) (a), Setting range:
Set points of the link device to be refreshed.
Page 7-28, Section 7.5 (4) (b))
(Default:
Page 7-28, Section 7.5 (4) (a), Setting range:
Set the start No. of the link device to be refreshed.
Page 7-28, Section 7.5 (4) (c))
(Default:
Page 7-28, Section 7.5 (4) (a), Setting range:
Set the end No. of the link device to be refreshed.
Page 7-28, Section 7.5 (4) (c))
(Default:
Page 7-28, Section 7.5 (4) (a), Setting range:
Page 7-28, Section 7.5 (4) (c))
Displays refresh parameters of the CPU module.
Data corresponding to respective "Link side" settings are shown.
Displays the name of the device whose data are refreshed onto the CPU module.
(Range:
Page 7-28, Section 7.5 (4) (b))
Displays the points of the device whose data are refreshed onto the CPU module.
The points is the same as those shown in "Points" of "Link side".
Displays the start No. of the device whose data are refreshed onto the CPU module.
The start No. is the same as that shown in "Start" of "Link side".
Displays the end No. of the device whose data are refreshed onto the CPU module.
The end No. is the same as that shown in "END" of "Link side".
Resets the "Link side" and "CPU side" settings back to defaults.
Checks the "Link side" and "CPU side" settings for errors.
Saves the settings and closes the "Refresh parameter settings" screen.
Closes the "Refresh parameter settings" screen without saving the settings.
7 - 27
7.5 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
7 CC IE CONTROL UTILITY
1
(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 Trans.1
Device name LB
Points 32768
Start 0000
End 7FFF
2
Trans.2 Trans.3 to Trans.64
LW
131072
00000
1FFFF
"(blank)"
(b) "Device names" on "Link side" and "CPU side"
The following table lists the setting range for "Device name" of "Link side" and
"CPU side" "Device name" displays.
3
Table 7.16 "Device names" on "Link side" and "CPU side"
"Link side" setting range
"CPU side" display
LX
LX buffer
LY
LY buffer
LB
LB buffer
LW
LW buffer
(c) Setting ranges for the link side "Points", "Start", and "End"
4
The following table lists the setting ranges for the link side "Points", "Start", and
"End".
(These setting ranges apply to all of "Trans.1" to "Trans.64".)
Table 7.17 Setting ranges for the link side "Points", "Start", and "End"
Device name LX LY LB LW
Points/Start/End Points Start End Points Start End Points Start End Points Start End
Setting range
16 to 8192*1
5
0000 to 1FF0*1
000F to 1FFF*2
16 to 8192*1
0000 to 1FF0*1
000F to 1FFF*2
16 to 32768*1
6
0000 to 7FF0*1
000F to 7FFF*2
1 to 131072
00000 to 1FFFF
00000 to 1FFFF
* 1 Only a multiple of 16 can be set for "Points" and "Start" of LX, LY, and LB. * 2 Only (a multiple of 16 minus 1) can be set for "End" of LX, LY, and LB.
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.5 Parameter Settings Tab
7 - 28
7 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
Item Total stations Assignment method Monitoring time Switch screens
Points
Start
End
Specify I/O master station button
Table 7.18 Description of Network range assignment screen
Description Set the total number of stations (including control stations) on the network. (Default: 2) How to enter the device range data can be switched between Points/Start and Start/End styles. (Default: "Start/End") Set a monitoring time for the link scan time. (In increments of ms) (Default: 2000, Setting range: 5 to 2000) Select a link device for which network ranges are assigned. (Default: "LB/LW settings (1)") Set the number of link device points assigned to the target station. This setting is available when "Points/Start" is selected for "Assignment method".
(Default: "(Blank)", Setting range:
Page 7-30, Section 7.5 (5) (a))
Set the start No. of the link device, which is assigned to the target station.
(Default: "(Blank)", Setting range:
Page 7-30, Section 7.5 (5) (a))
Set the end No. of the link device, which is assigned to the target station.
This setting is available when "Start/End" is selected for "Assignment method".
(Default: "(Blank)", Setting range:
Page 7-30, Section 7.5 (5) (a))
Specifies the selected station as an I/O master station of the link device (LX/LY), or cancels the setting. This button can be used when "LX/LY settings (1)" or "LX/LY settings (2)" is selected for "Switch screens".
Specify reserved station button
Specifies the selected station as a reserved station, or cancels the setting.
Equal assignment button
Displays the "Equal assignment" screen. (
Page 7-31, Section 7.5 (6))
Supplementary settings button Displays the "Supplementary settings" screen. (
Page 7-33, Section 7.5 (7))
Clear button
Erases the "Points", "Start", and "End" settings, and sets "Total stations" and "Monitoring time" back to defaults.
Check button End button Cancel button
Checks the "Points", "Start", "End", "Total stations", and "Monitoring time" settings for errors. Saves the settings and closes the "Network range assignment" screen. Closes the "Network range assignment" screen without saving the settings.
7 - 29
7.5 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY
1
(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
LX
Start
16 to 8192 *1 0000 to 1FF0 *1
2
End
000F to 1FFF*2
Points
16 to 8192 *1
LY
Start
0000 to 1FF0*1
End
000F to 1FFF*2
Points
LB
Start
16 to 32768*1
0000 to 7FF0 *1
3
End
Points
LW
Start
End
000F to 7FFF *2 1 to 131072
00000 to 1FFFF 00000 to 1FFFF
* 1 Only a multiple of 16 can be set for "Points" and "Start" of LX, LY, and LB.
* 2 Only (a multiple of 16 minus 1) can be set for "End" of LX, LY, and LB.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.5 Parameter Settings Tab
7 - 30
7 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)" or "LB/LW settings (2)" is set for "Switch screens" in
"Network range assignment"
Figure 7.27 Equal assignment screen (for LB/LW settings (1))
Table 7.20 Description of Equal assignment screen (for LB/LW settings (1) or LB/LW settings (2))
Item Identical point assignment OK button Cancel button Equal assignment
LB equal assignment
Start station
End station
Start No. Total points assigned LW equal assignment
Description Equally assigns the entered points to link devices of each station. (In increments of 16 points) (Default: "(Blank)", Setting range: 16 or greater)
Executes equal assignment according to the settings, and closes the "Equal assignment" screen.
Closes the "Equal assignment" screen without executing equal assignment.
Equally divides the entered points and assigns them to link devices of each station. Set data for equal assignment of LB (1) or LB (2). Specify the start station. (Default: "(Blank)", Setting range: 1 to ("Total stations" setting))
"Total stations" is set on the "Network range assignment" screen. (
Page 7-29, Section 7.5
(5))
Specify the end station.
(Default: "(Blank)", Setting range: (Start station" setting) to ("Total stations" setting))
"Total stations" is set on the "Network range assignment" screen. ( (5)) Set the start No. of the link device.
Page 7-29, Section 7.5
(Default: "(Blank)", Setting range: Set the total link device points.
Page 7-30, Section 7.5 (5) (a))
(Default: "(Blank)", Setting range:
Page 7-30, Section 7.5 (5) (a))
Set data for equal assignment of LW (1) or LW (2).
Set respective items as in "LB equal assignment".
7 - 31
7.5 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
7 CC IE CONTROL UTILITY 1 (b) When "LX/LY settings (1)" or "LX/LY settings (2)" is set for "Switch screens" in "Network range assignment"
2
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))
3
Item
Description
Equally assigns the entered points to link devices of each station. (In increments of 16 points)
Identical point assignment
Note that no points are assigned to any I/O master station. ( (Default: "(Blank)", Setting range: 16 or greater)
Page 7-29, Section 7.5 (5))
OK button
Cancel button Equal assignment
Executes equal assignment according to the settings, and closes the "Equal assignment" screen.
Closes the "Equal assignment" screen without executing equal assignment.
4
Equally divides the entered points and assigns them to link devices of each station.
M station to L station equal assignment
Set data for equal assignment of LY (1) or LY (2).
Start station End station
Specify the start station. (Default: "(Blank)", Setting range: 1 to ("Total stations" setting))
"Total stations" is set on the "Network range assignment" screen. ( (5))
Page 7-29, Section 7.5
5
Specify the end station.
(Default: "(Blank)", Setting range: ("Start station" setting) to ("Total stations" setting))
"Total stations" is set on the "Network range assignment" screen. ( (5))
Page 7-29, Section 7.5
Set the start No. of the link device.
Start No.
(Default: "(Blank)", Setting range: Set the total link device points.
Page 7-30, Section 7.5 (5) (a))
6
Total points assigned
(Default: "(Blank)", Setting range:
Page 7-30, Section 7.5 (5) (a))
L station to M station equal assignment
Set data for equal assignment of LX (1) or LX (2). Set respective items as in "M station to L station equal assignment".
7
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.5 Parameter Settings Tab
7 - 32
7 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 Constant scan
Block data assurance per station
Description Constant scan is a feature provided for keeping a fixed link scan time. Set a value if variation in link scan time undesirable. (In increments of ms) (Default: "(Blank)", Setting range: 1 to 500, "(Blank)") Select this to assure the station-based link data consistency in cyclic transmissions.*1 No interlock program is needed for operation of multiple word data if this item is selected. Note that this function*1 is available only for link device refresh processing between a C Controller module and a CC-Link IE Controller Network module. When selecting this item, make sure the following parameters are set. ·"Link device refresh cycle" on the "Parameter settings" tab
(
Page 7-23, Section 7.5 (2))
·Refresh parameters on the "Refresh parameter settings" tab
Transient settings
(
Page 7-27, Section 7.5 (4))
(Default: Checked (Allow))
Set execution conditions for transient transmissions.
Constant scan time assurance Set whether or not to assure the constant scan time. ( (Default: Checked (Enabled))
Page 7-33, Section 7.5 (7) (a))
Max. number of transients per Set the number of transient transmissions that one station can execute during one link scan.
station
(Default: 2, Setting range: 1 to 10)
End button
Saves the settings and closes the "Supplementary settings" screen.
Cancel button
Closes the "Supplementary settings" screen without saving the settings.
* 1 A two-word (32-bit) link data, such as a present value of a positioning module, may be divided into two one-word data (new 16-bit data and old 16-bit data) at a timing of cyclic transmission. This function prevents this situation from occurring. Set link device refresh processing between a C Controller module and a CC-Link IE Controller
Network module on the "Refresh parameter settings" screen. (
Page 7-27, Section 7.5 (4))
(a) Link scan operations by the Constant scan time assurance setting
Table 7.23 Link scan operations by Constant scan time assurance setting
Constant scan time assurance Selected Deselect
Link scan operation ·Link scan time is kept constant. ·Link scan time is longer compared with the deselected setting. ·The larger the "Max. number of transients per station" value is, the longer the link scan time will become. ·Link scan time varies when a transient transmission is requested. ·The larger the "Max. number of transients per station" value is, the larger the link scan time variation will become.
7 - 33
7.5 Parameter Settings Tab
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY 1 7.6 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
2
accessing a programmable controller CPU that is controlled by another CPU.
For the access in the following section, however, the logical station No. setting is not
required.
Page 7-36, "7.6 (4) Access that does not require a logical station No. setting"
(1) Precautions for the Target settings tab
3
Set a programmable controller CPU for "Target CPU".
(2) Target settings tab
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
5
Figure 7.30 Target settings tab Table 7.24 Description of Target settings tab
6
Module information Online operation Parameter settings Target settings
Item Target module Logical station No.
Network No. Station No. Target CPU Set button
Description
Select a module to configure.
(Default: "Slot 1")
Specify a logical station No. of the module selected for "Target module". (Default: 65, Setting range: 65 to 239)
7
Logical station No. is a logical number that is specified as "station No." in Device monitoring utility or
user programs (MELSEC data link functions).
Set a network No. of a CC-Link IE Controller Network module or MELSECNET/H module that is
controlled by a multiple CPU system.
(Default: 1, Setting range: 1 to 239)
Set a station No. of a CC-Link IE Controller Network module or MELSECNET/H module that is
controlled by a multiple CPU system. (Default: 1, Setting range: 1 to 120)
8
Set an access target CPU (CPU No. used in the multiple CPU system).
(Default: 1, Setting range: 1 to 4)
Registers the set or modified data (Logical station No., Network No., Station No., and Target CPU) to
the Target list.
(To the next page)
7.6 Target Settings Tab
7 - 34
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
7 CC IE CONTROL UTILITY
Table 7.24 Description of Target settings tab (continued)
Module information Online operation Parameter settings Target settings
Target list
Item
Change button Delete button
Description Displays the logical station No. set for the selected "Target module", the relevant network No. and station No., and the target CPU in the list. Updates a setting change (logical station No.) of a row selected in the Target list into the above Logical station No. box. (Logical No. setting can be also changed by double-clicking the row.)
Deletes the selected row (logical station No.) from the Target list.
(3) Access example
When the settings in the following screen are applied in the below system, a CC-Link IE Controller Network module controlled by a C Controller module can access CPU No. 4 via another CC-Link IE Controller Network module (controlled by CPU No.2, network No.1) by using logical station No."65". The access is also available by opening channel No.151 and setting 65 for the station No. in Device monitoring utility or a user program (MELSEC data link functions).
Control station QJ71GP21-SX Slot 1, Channel No.151 (Controlled by C Controller module)
C Controller module
CPU No.2
CPU No.4 *1
Normal station QJ71GP21-SX Station No.: 5 (Controlled by CPU No.2)
Multiple CPU system
CC-Link IE Controller Network Network No.1 Figure 7.31 System configuration * 1 When CPU No.4 cannot configure a multiple CPU system, access to CPU No. 4 is not available by using the logical No.
The following is the target setting for the above access.
7 - 35
7.6 Target Settings Tab
Figure 7.32 Target settings tab setting
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY 1
(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.
Other station CC-Link IE Controller Network module
2
Control CPU of other station CC-Link IE Controller Network module
C Controller module
C Controller module
3
CC-Link IE Controller Network
CC-Link IE Controller Network
Figure 7.33 Access that does not require a logical station No. setting
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.6 Target Settings Tab
7 - 36
7 CC IE CONTROL UTILITY
7.7 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. · Press the [Alt] key and then the [ ] key. · For Windows® 7 or later, right-click the icon ( ) on the task bar while pressing
the [Shift] key.
Item Move, Minimize, and Close Specify CPU type
C Controller setting utility
Device monitoring utility Version information
Figure 7.34 System menu
Table 7.25 Description of System menu
Description Refer to the Microsoft® Windows® manual.
Specifies a C Controller module to which parameters are set or to be monitored. ( Section 3.4) This item is not selectable while monitoring is active.
Page 3-4,
Starts C Controller setting utility. (
Page 4-1, CHAPTER 4)
If CC IE Control utility is connected online, this utility is started with the same target being
connected.
Starts Device monitoring utility. (
Page 8-1, CHAPTER 8)
If CC IE Control utility is connected online, this utility is started with the same target being
connected.
Opens the "Version information" screen. (
Page 7-38, Section 7.7 (2))
7 - 37
7.7 System Menu
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
7 CC IE CONTROL UTILITY 1
(2) Version information screen
Version information of the CC IE Control utility is displayed.
2
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.
3
CC IE Control utility
Displays the update date of the CC IE Control utility.
OK button
Closes the "Version information" screen.
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
5
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
7.7 System Menu
7 - 38
7 CC IE CONTROL UTILITY
7.8 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.
(3) 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.
(4) Tabs available to operate offline
When CC IE Control utility connection is offline, data can be set only in the Parameter settings and the Target settings tab.
(5) Terminating Microsoft® Windows®
Do not terminate Microsoft® Windows® while CC IE Control utility is running. Terminate CC IE Control utility first and then Microsoft® Windows®.
(6) 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.
(7) Time required for connection from each utility to the C Controller module
The following time is required for the C Controller module to connect to each utility after power-on or reset.
· When executing a script file, "STARTUP.CMD": Upon completion of the RUN LED flashing.
· When not executing a script file, "STARTUP.CMD": Fifteen (15) seconds after completion of start or reset.
Do not attempt a connection before the above time has elapsed after completion of power-on or reset. Changing "Priority" to a larger value in the Option tab of C Controller setting utility increases the time after which the C Controller module can be connected.
7 - 39
7.8 Precautions
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
8 DEVICE MONITORING UTILITY 1
CHAPTER 8 DEVICE MONITORING UTILITY
8.1 Device Monitoring Utility Function List
2
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Table 8.1 Device monitoring utility function list
Name
Connection setting Batch monitoring
Description
Sets the connection target of Device monitoring utility. Monitors only one specified device.
Applicability
Reference
Q12DCCPU-V Q06CCPU-V page
Page 3-5
3
Page 8-2
16-point register monitoring
Monitors up to five bit devices and one word device at the same time.
Page 8-4
Setting monitoring target
Sets a network for which Device monitoring utility is used.
Page 8-6
Setting device to be monitored Word device value change
Sets the device(s) to be monitored. Changes the specified word device data.
Page 8-7
4
Page 8-8
Continuous word device value change
Changes the specified points of word device data to the specified data.
Page 8-10
ON/OFF of bit device Turns on or off the specified bit device.
Page 8-12
Changing the format Changes the display format for device monitoring.
Page 8-14
Start/stop monitoring Starts or stops monitoring by Device monitoring utility.
Numerical pad
Enters numerical data by a mouse.
Page 8-15 Page 8-16
5
: Applicable, : Applicable but partially restricted, : N/A
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
8.1 Device Monitoring Utility Function List
8 - 1
8 DEVICE MONITORING UTILITY
8.2 Batch Monitoring
Only one specified device can be monitored.
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(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.
(b) CC-Link module monitoring When monitoring has been performed to the CC-Link module (specified as own station) where the block data assurance per station is enabled, cyclic data are will be automatically refreshed.
However, data are automatically refreshed only when monitoring has been performed within the range set in "Station information settings" for the master station. The range set in "Station information settings" can be confirmed by "Slave station offset, size information" (buffer memory address: 3E0H to 5DFH) of the CC-Link module. For details of the block data assurance per station, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
Note also that the write (send) area of the link refresh devices (the buffer memory) will not be refreshed when monitoring has been performed.
8 - 2
8.2 Batch Monitoring
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
8 DEVICE MONITORING UTILITY 1
(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-
2
7, Section 8.5)
(3) Display screen
3
1)
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
5
2)
3)
Figure 8.1 Batch monitoring
Table 8.2 Description of Batch monitoring screen
6
Item
Description
1) Device information
Displays the current device status.
Changing display format (
Page 8-14, Section 8.9)
2) Network status
Displays the status of the currently specified network.
Network setting (
Page 8-6, Section 8.4)
The following items describe devices shown on the display. ·Device type (word device or bit device)
7
·Display format
3) Display format
·Display format for a SPG device (special direct buffer register or intelligent function module buffer memory)
(only when monitoring a SPG device)
Changing device type (
Page 8-7, Section 8.5)
Changing display format (
Page 8-14, Section 8.9)
8
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
8.2 Batch Monitoring
8 - 3
8 DEVICE MONITORING UTILITY
8.3 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.
(b) CC-Link module monitoring When monitoring has been performed to the CC-Link module (specified as own station) where the block data assurance per station is enabled, cyclic data will be automatically refreshed.
However, data are automatically refreshed only when monitoring has been performed within the range set in "Station information settings" for the master station. The range set in "Station information settings" can be confirmed by "Slave station offset, size information" (buffer memory address: 3E0H to 5DFH) of the CC-Link module. For details of the block data assurance per station, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
Note also that the write (send) area of the link refresh devices (the buffer memory) will not be refreshed when monitoring has been performed.
8 - 4
8.3 16-Point Register Monitoring
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
8 DEVICE MONITORING UTILITY 1
(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)
2
(3) Display screen
3
1)
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
5
2)
3)
Figure 8.2 16-point register monitoring
Table 8.3 Description of 16-point register monitoring
6
Item
Description
1) Device information
Displays the current device status.
Changing display format (
Page 8-14, Section 8.9)
2) Network status
Displays the status of the currently specified network.
Network setting (
Page 8-6, Section 8.4)
3) Display format
Displays the device type (word device or bit device) and display format.
Changing device type (
Page 8-7, Section 8.5)
7
Changing display format (
Page 8-14, Section 8.9)
8
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
8.3 16-Point Register Monitoring
8 - 5
8 DEVICE MONITORING UTILITY
8.4 Setting Monitoring Target
Q12DCCPU-V
Set a network for which Device monitoring utility is used. Set the network at startup of Device monitoring utility.
Q06CCPU-V
Q06CCPU-V-B
(1) Precautions for network setting
When the own station is selected in "Network settings", network No."0" and station No."255" are displayed in the network status area.
(2) Selected menu items
From the menu bar, select [Setting] [Network settings].
(3) Dialog box
Channel
Item
Network settings
Figure 8.3 Network settings dialog box
Table 8.4 Description of Network settings dialog box
Select a channel.
Description
(
Page 10-1, Section 10.1, Page 10-9, Section 10.10)
Select Own or Other station, and set network No. and station No.
(
Page 10-1, Section 10.1, Page 10-10, Section 10.11)
8 - 6
8.4 Setting Monitoring Target
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
8 DEVICE MONITORING UTILITY 1 8.5 Setting Device to Be Monitored
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Set the device to be monitored.
2
(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.
If random access is not allowed for the specified device, a device type error (-3) will occur.
3
For random accessibility of each device, refer to the following.
Page 10-17, Section 10.13
(2) Selected menu items
From the menu bar, select [Setting] [Device settings].
4
(3) Dialog box
Batch monitoring
16-point register monitoring
5
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
6
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
Figure 8.4 Device settings dialog box
7
Table 8.5 Description of Device settings dialog box
Item
Description
Device type
Set the type (
Page 10-12, Section 10.12), block No., and network No. of
the device to be monitored.
Device No. Register device list
Set the start No. of the device to be monitored. (HEX: Hexadecimal, DEC: Decimal, OCT: Octal) Lists the registered devices.
8
Set button
Registers the device type and device No. settings, and adds the information in the Register device list.
Change button
Changes the registered data of the selected device.
Delete button
Deletes the registered data of the selected device from the Register device list.
8.5 Setting Device to Be Monitored
8 - 7
DEVICE MONITORING UTILITY
8 DEVICE MONITORING UTILITY
8.6 Changing Word Device Values
Q12DCCPU-V
Data of the specified word device can be changed.
Q06CCPU-V
Q06CCPU-V-B
WARNING
Configure safety circuits external to the C Controller module to ensure that the entire system operates safely even when a fault occurs in the external power supply or the C Controller module. 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 from the
development environment (personal computer) connected (2) Changing the operating status (3) Operating from the development environment (personal
computer) Especially, in the case of a control from an external device to a remote C Controller module, immediate action cannot be taken for a problem on the C Controller module due to a communication failure. To prevent this, configure an interlock circuit in the user program, and determine corrective actions to be taken between the external device and C Controller module in case of a communication failure.
(1) Precautions for changing word device values
(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.
(b) CC-Link module monitoring When devices has been written to a CC-Link module (specified as own station) where the block data assurance per station is enabled, cyclic data will be automatically refreshed.
However, data are automatically refreshed only when device writing has been performed within the range set in "Station information settings" for the master station. The range set in "Station information settings" can be confirmed by "Slave station offset, size information" (buffer memory address: 3E0H to 5DFH) of the CC-Link module. For details of the block data assurance per station, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
Note also that the read (receive) area of the link refresh devices (the buffer memory) will not be refreshed when devices have been written.
8 - 8
8.6 Changing Word Device Values
8 DEVICE MONITORING UTILITY 1
(2) Selected menu items
From the menu bar, select [Write device] [Data change].
(3) Dialog box
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
Item Device type
Device No. Setting data
3
Figure 8.5 Data change dialog box
Table 8.6 Description of Data change dialog box
Description
Set the type (
Page 10-12, Section 10.12), block No. and network No. of
4
the device of which data are changed.
Set the start No. of the device of which data are changed.
(HEX: Hexadecimal, DEC: Decimal, OCT: Octal)
Set new data. (HEX: Hexadecimal, DEC: Decimal)
5
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
8.6 Changing Word Device Values
8 - 9
8 DEVICE MONITORING UTILITY
8.7 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. 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 from the
development environment (personal computer) connected (2) Changing the operating status (3) Operating from the development environment (personal
computer) Especially, in the case of a control from an external device to a remote C Controller module, immediate action cannot be taken for a problem on the C Controller module due to a communication failure. To prevent this, configure an interlock circuit in the user program, and determine corrective actions to be taken between the external device and C Controller module in case of a communication failure.
(1) Precautions for continuous change of word device values
(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.
(b) CC-Link module monitoring When devices have been written to a CC-Link module (specified as own station) where the block data assurance per station is enabled, cyclic data will be automatically refreshed.
However, data are automatically refreshed only when device writing has been performed within the range set in "Station information settings" for the master station. The range set in "Station information settings" can be confirmed by "Slave station offset, size information" (buffer memory address: 3E0H to 5DFH) of the CC-Link module. For details of the block data assurance per station, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
Note also that the read (receive) area of the link refresh devices (the buffer memory) will not be refreshed when devices have been written.
8 - 10
8.7 Continuously Changing Word Device Values
8 DEVICE MONITORING UTILITY 1
(2) Selected menu items
From the menu bar, select [Write device] [Continuous data change].
(3) Dialog box
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
3
Figure 8.6 Continuous data change dialog box
Table 8.7 Description of the Continuous data change dialog box
4
Item
Description
Device type
Set the type, block No., and network No. of the device whose data are changed.
(
Page 10-12, Section 10.12)
Device No.
Set the start No. of the device whose data are changed. (HEX: Hexadecimal, DEC: Decimal, OCT: Octal)
Setting data
Set the data to be changed continuously. (HEX: Hexadecimal, DEC: Decimal)
5
Points
Set the points for which data are to be changed continuously. (HEX: Hexadecimal, DEC: Decimal, OCT: Octal)
6
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
8.7 Continuously Changing Word Device Values
8 - 11
8 DEVICE MONITORING UTILITY
8.8 Tuning On and Off Bit Device
The specified bit device can be turned on and off.
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
WARNING
Configure safety circuits external to the C Controller module to ensure that the entire system operates safely even when a fault occurs in the external power supply or the C Controller module. 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 from the
development environment (personal computer) connected (2) Changing the operating status (3) Operating from the development environment (personal
computer) Especially, in the case of a control from an external device to a remote C Controller module, immediate action cannot be taken for a problem on the C Controller module due to a communication failure. To prevent this, configure an interlock circuit in the user program, and determine corrective actions to be taken between the external device and C Controller module in case of a communication failure.
(1) Precaution for turning on and off the bit device
(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.
(b) CC-Link module monitoring When devices have been written to a CC-Link module (specified as own station) where the block data assurance per station is enabled, cyclic data will be automatically refreshed.
However, data are automatically refreshed only when device writing has been performed within the range set in "Station information settings" for the master station. The range set in "Station information settings" can be confirmed by "Slave station offset, size information" (buffer memory address: 3E0H to 5DFH) of the CC-Link module. For details of the block data assurance per station, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
Note also that the read (receive) area of the link refresh devices (the buffer memory) will not be refreshed when devices have been written.
8 - 12
8.8 Tuning On and Off Bit Device
8 DEVICE MONITORING UTILITY 1
(2) Selected menu
From the menu bar, select [Write device] [Set (Reset) bit device].
(3) Dialog box
2
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
Figure 8.7 Set bit device dialog box
3
Table 8.8 Description of the Set (reset) bit device dialog box
Item Device type Device No.
Description Set the type, block No., and network No. of the device to be turned on or off.
(
Page 10-12, Section 10.12)
Set the bit device No. of the device to be turned on or off.
4
(HEX: Hexadecimal, DEC: Decimal, OCT: Octal)
5
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
6
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
8.8 Tuning On and Off Bit Device
8 - 13
8 DEVICE MONITORING UTILITY
8.9 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).
Item Word device
Bit device
Figure 8.8 Data Format menu
Table 8.9 Display format Description
Selects the numeric format and units of displays for values to be monitored. Selects the numeric format, units of displays, and order of the bits for values to be monitored. Selects the numeric format for the following values when a SPG device is monitored.
SPG device display format
8 - 14
8.9 Changing the Display Format
Start I/O No./16
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
8 DEVICE MONITORING UTILITY 1 8.10 Start and Stop Monitoring
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
The Start monitoring and Stop monitoring buttons of Device monitoring utility are operated on this screen.
2
The Start monitoring and Stop monitoring buttons become operable after completing the Device setting.
(1) Operation
Monitoring can be started and stopped by using the Start monitoring and
3
Stop monitoring buttons.
(2) Screen
4
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
5
Figure 8.9 Screen for monitoring start and stop
6
Table 8.10 Description of buttons
Item Start monitoring button and Stop monitoring button
Description Starts or stops monitoring. "*" flashes in the bottom right of the button during monitoring. These buttons are disabled in the offline status.
7
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
8.10 Start and Stop Monitoring
8 - 15
8 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.
1 Click the "Device No." entry field.
2 As the Numerical pad appears, enter a numerical value using buttons. Then click the OK button.
3 The numerical value is entered.
8 - 16
8.11 Numerical Pad
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
8 DEVICE MONITORING UTILITY 1 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.
2
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.
3
(1) Changing data of the running C Controller module from the
development environment (personal computer) connected
(2) Changing the operating status
(3) Operating from the development environment (personal computer)
Especially, in the case of a control from an external device to a
remote C Controller module, immediate action cannot be taken for a
4
problem on the C Controller module due to a communication failure.
To prevent this, configure an interlock circuit in the user program,
and determine corrective actions to be taken between the external
device and C Controller module in case of a communication failure.
(1) Precautions for changing the word device and bit device
5
(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.
(b) CC-Link module monitoring
6
When devices have been written to a CC-Link module (specified as own station)
where the block data assurance per station is enabled, cyclic data will be
automatically refreshed.
However, data are automatically refreshed only when device writing has been
performed within the range set in "Station information settings" for the master
station.
7
The range set in "Station information settings" can be confirmed by "Slave station
offset, size information" (buffer memory address: 3E0H to 5DFH) of the CC-Link
module.
For details of the block data assurance per station, refer to the C Controller
Module User's Manual (Hardware Design, Function Explanation).
Note also that the read (receive) area of the link refresh devices (the buffer
8
memory) will not be refreshed when devices have been written.
CC-LINK UTILITY
MELSECNET/H UTILITY
CC IE CONTROL UTILITY
DEVICE MONITORING UTILITY
8.12 Other Operations
8 - 17
8 DEVICE MONITORING UTILITY
(2) Changing a word device
The following describes how to change a word device.
1 Double-click the word device No. of which value is to be changed.
2 As the dialog box shown on the left appears, enter any given values. Click the Execute button.
3 To accept the change, click the Yes button in the dialog box shown on the left. To cancel the change, click the No button.
(3) Changing a bit device
The following describes how to turn on and off a bit device. Note that this operation is available only when the display format is set to "Vertical".
1 Double-click the bit device No. of which value is to be changed.
2 To accept the change, click the Yes button in the dialog box shown on the left. To cancel the change, click the No button.
8 - 18
8.12 Other Operations
OVERVIEW
INSTALLATION AND UNINSTALLATION OF SOFTWARE PACKAGE
8 DEVICE MONITORING UTILITY 1 8.13 Precautions
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Connection during script file processing
2
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.
(2) Time required for connection from each utility to the C Controller
3
module
The following time is required for the C Controller module to connect to each utility
after power-on or reset.
· When executing the script file, "STARTUP.CMD":
Upon completion of the RUN LED flashing.
· When not executing the script file, "STARTUP.CMD": Fifteen (15) seconds after completion of start or reset.
4
Do not attempt a connection before the above time has elapsed after completion of
power-on or reset.
Changing "Priority" to a larger value in the Option tab of C Controller setting utility
increases the time after which the C Controller module can be connected.
(3) When accessing Q24DHCCPU-V/-VG
5
The accessible range of B device in Device monitoring utility is within 0 to 65534.
6
COMMON UTILITY OPERATIONS
C CONTROLLER SETTING UTILITY
CC-LINK UTILITY
MELSECNET/H UTILITY
7
CC IE CONTROL UTILITY
8
DEVICE MONITORING UTILITY
8.13 Precautions
8 - 19
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
CHAPTER 9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9.1
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.
Outline of Bus Interface Functions
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
To access and control programmable controllers and each module in a user program, functions provided by SW3PVC-CCPU must be used.
(1) The following indicates features of bus interface functions.
1) Input and output control of I/O modules controlled by the C Controller module.
2) Access to the buffer memories of the intelligent function modules controlled by the C Controller module. (X/Y access, buffer memory access, and wait for an interrupt event from an intelligent function module or an interrupt module are available)
3) Linkage between the programmable controller CPU and the Motion CPU that are in the same system as the C Controller module.
4) Message exchange with the following modules or personal computers via CCLink IE Controller Network module(s) or MELSECNET/H module(s) controlled by the C Controller module. · C Controller module (another station) · Programmable controller CPU (another station) · Personal computer equipped with MELSECNET/H board (only via MELSECNET/H module(s))
5) Access to link devices of the CC-Link IE Controller Network module or MELSECNET/H module controlled by the C Controller module.
6) Start of a routine from the user watchdog timer error interrupt.
7) Remote RUN/STOP/PAUSE control of the C Controller module.
8) Registration of the event log to the event history file.
9) Mounting and unmounting of the CompactFlash card.
10)Shutdown of the standard ROM.
11)Setting and reading of the clock data.
12)Writing data to or reading data from the battery-backed-up RAM.
9 - 1
9.1 Outline of Bus Interface Functions
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
The system illustration below represents a system image based on the features described on the previous page.
I/O module C Controller module
Intelligent function module CC-Link IE Controller Network module or
MELSECNET/H module
Programmable controller CPU
6) to 12) 1)
3)
Programmable controller CPU
2) 5) 4)
Motion CPU
CC-Link module
CC-Link IE Controller Network or MELSECNET/H
Figure 9.1 Bus interface function image
Table 9.1 Access targets of bus interface functions
Arrow
Access target
Input module/output module
No. given above
1)
Remarks
·Input (X): Reading enabled ·Output (Y): Reading and writing enabled
Intelligent function module
2)
Reading from and writing to buffer memory enabled
Programmable controller CPU/MotionCPU CC-Link IE Controller Network module (another station), or MELSECNET/H module (another station) CC-Link IE Controller Network module (own station), or MELSECNET/H module (host station)
C Controller module
3) 4)
5)
6) to 12)
The following operations are available. ·Remote RUN/STOP/PAUSE ·Setting and reading clock data ·Reading from and writing to battery-backed-up RAM
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A
I
9.1 Outline of Bus Interface Functions
9 - 2
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9.2 Bus Interface Function List
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Bus interface function list
Category Open/close
I/O access
Function name
QBF_Open QBF_Close QBF_X_In_BitEx QBF_X_In_WordEx QBF_Y_Out_BitEx QBF_Y_Out_WordEx QBF_Y_In_BitEx QBF_Y_In_WordEx
CPU shared memory/buffer memory access
QBF_ToBuf QBF_FromBuf
Link device refresh
QBF_RefreshLinkDevice
Link device access
QBF_WriteLinkDevice QBF_ReadLinkDevice
QBF_SEND
Message communication
QBF_RECV
Acquisition of module information
WDT control
QBF_UnitInfo
QBF_StartWDT QBF_ResetWDT QBF_StopWDT QBF_EntryWDTInt
Table 9.2 Bus interface function list
Opens a bus.
1)Q12DCCPU-V 2)Q06CCPU-V 3)Q06CCPU-V-B
Function
Availability
1)
2)
3)
Closes a bus.
Reads a single point in the input signal (X).
Reads input signal (X) in 1-word units. Outputs a single point in the output signal (Y). Outputs output signal (Y) in 1-word units.
Reads a single point in the output signal (Y).
Reads output signal (Y) in 1-word units. Writes data to the CPU shared memory of the specified module and the buffer memory of the intelligent function module (To instruction). Reads data from the CPU shared memory of the specified module and the buffer memory of the intelligent function module (From instruction).
Refreshes the CC-Link module link device.
Writes data to link devices of a CC-Link IE Controller Network module (own station) or MELSECNET/H module (own station). Reads data from link devices of a CC-Link IE Controller Network module (own station) or MELSECNET/H module (own station). Sends messages to another station via CC-Link IE Controller Network module or MELSECNET/H module. (Equivalent to SEND instruction of CC-Link IE Controller Network module or MELSECNET/H module.) Receives messages from another station via CC-Link IE Controller Network module or MELSECNET/H module. (Equivalent to RECV instruction of CC-Link IE Controller Network module or MELSECNET/H module.)
Reads module configuration information.
Sets an interval of WDT and starts up the user WDT. Resets the user WDT. Stops the user WDT. Registers a routine for the user WDT error interrupt.
: Available, : N/A
(To the next page)
9 - 3
9.2 Bus Interface Function List
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
Table 9.2 Bus interface function list (continued)
Category
Function name
Timer event control Acquisition of module status information
User LED control
QBF_EntryTimerEvent QBF_WaitTimerEvent
QBF_ReadStatusEx
QBF_ControlLED QBF_Control7SegLED QBF_Reset*1
CPU operating status control
QBF_Control QBF_ControlEx
Event registration QBF_RegistEventLog
CF card mount/ QBF_MountCfCard
unmount
QBF_UnmountCfCard
Standard ROM shutdown
QBF_ShutdownRom
Clock data
QBF_SetTime QBF_GetTime
Battery backed-up QBF_WriteSRAM
RAM access
QBF_ReadSRAM
QBF_WaitUnitEvent
QBF_WaitEvent
Interrupt event control
QBF_GINT QBF_EntryMultiCPUSyncInt QBF_EnableMultiCPUSyncInt QBF_DisableMultiCPUSyncInt
1)Q12DCCPU-V 2)Q06CCPU-V 3)Q06CCPU-V-B
Function
Availability
1)
2)
3)
Registers timer events.
Waits for an occurrence of a timer event.
Reads the status information (LED, error, etc.) of C Controller module.
Controls USER LED of C Controller module. Controls the 7-segment LED of C Controller module.
Resets the bus master CPU (CPU No.1).
Controls remote operations (RUN/STOP/PAUSE) for the C Controller module. Controls remote operations (RUN/STOP/PAUSE) for specified CPU. Registers event logs in the event history file. Mounts a CompactFlash card. (Q06CCPU-V only) Unmounts a CompactFlash card. (Q06CCPU-V only) Sets C Controller module to power-off-available condition. (Shuts down the standard ROM.) Sets up clock data. Reads clock data. Writes data to the battery-backed-up RAM. Reads data from the battery-backed-up RAM. Waits for an interrupt event notification from an intelligent function module or an interrupt module. Waits for an interrupt event notification from another CPU. Issues an interrupt to another CPU. (Equivalent to the S(P). GINT instruction of programmable controller CPU.) Registers a routine so that it can be called when a multiple CPU synchronization interrupt occurs. Enables the routine registered for the multiple CPU synchronization interrupt. Disables the routine registered for the multiple CPU synchronization interrupt.
: Available, : N/A
* 1 For precautions on remote RESET during writing a user file, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
9.2 Bus Interface Function List
9 - 4
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
Category
Interrupt event control
Ladder program control Motion CPU control (program start)
Motion CPU control (operations)
Motion device access
C Controller module's internal user or system device access Error clear
Table 9.2 Bus interface function list (continued)
Function name QBF_EntryCpuInt QBF_EnableCpuInt QBF_DisableCpuInt QBF_EntryUnitInt QBF_EnableUnitInt QBF_DisableUnitInt
1)Q12DCCPU-V 2)Q06CCPU-V 3)Q06CCPU-V-B
Function
Availability
1)
2)
3)
Registers an interrupt so that the routine can be called
*2
when the interrupt is issued from another CPU.
Enables the routine registered for an interrupt from
*2
another CPU.
Disables the routine registered for an interrupt from
*2
another CPU.
Registers an interrupt so that the routine can be called
when the interrupt is issued from an intelligent function
*2
module or an interrupt module.
Enables the routine registered for an interrupt from an
*2
intelligent function module or an interrupt module.
Disables the routine registered for an interrupt from an
*2
intelligent function module or an interrupt module.
QBF_ControlProgram
Controls execution type of a ladder program.
QBF_MotionSFCS QBF_MotionSVST
QBF_MotionCHGA
QBF_MotionCHGV
QBF_MotionCHGT
QBF_MotionDDWR QBF_MotionDDRD QBF_WriteDevice QBF_ReadDevice QBF_SetDevice QBF_ResetDevice QBF_ClearError
Requests to start the specified Motion SFC program.
(Equivalent to S(P).SFCS instruction of programmable
controller CPU.)
Requests to start the specified servo program.
(Equivalent to S(P).SVST instruction of programmable
controller CPU.)
Requests to change the current value of the specified
axis.
(Equivalent to S(P).CHGA instruction of programmable
controller CPU.)
Requests to change the speed of the specified axis.
(Equivalent to S(P).CHGV instruction of programmable
controller CPU.)
Requests to change the torque limit value of the
specified axis.
(Equivalent to S(P).CHGT instruction of programmable
controller CPU.)
Writes data to the Motion CPU devices.
(Equivalent to S(P).DDWR instruction or D(P).DDWR
instruction of programmable controller CPU.)
Reads data from the Motion CPU devices.
(Equivalent to S(P).DDRD instruction or D(P).DDRD
instruction of programmable controller CPU.)
Writes data to the internal user or system devices of
*2
the C Controller module.
Reads data from the internal user or system devices of
*2
the C Controller module.
Sets the internal user or system devices (bit devices) of
*2
the C Controller module.
Resets the internal user or system devices (bit devices)
*2
of the C Controller module.
Clears an error.
*2
* 2 Not available for the following C Controller module. · Q12DCCPU-V with serial number (first five digits) "12041" or earlier
: Available, : N/A
9 - 5
9.2 Bus Interface Function List
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
(2) Bus interface function for ISR list
Category I/O access
CPU shared memory
User LED control Battery-backedup RAM access
Table 9.3 Bus interface function for ISR
Function name
1)Q12DCCPU-V 2)Q06CCPU-V 3)Q06CCPU-V-B
Function
Availability
1)
2)
3)
QBF_X_In_Word_ISR
Reads input signal (X) in 1-word units.
QBF_Y_Out_Word_ISR
Outputs output signal (Y) in 1-word units.
QBF_Y_In_Word_ISR
Reads output signal (Y) in 1-word units.
QBF_ToBuf_ISR
Writes data to the CPU shared memory of a specified module and a buffer memory*1 in an intelligent function module (To instruction).
QBF_FromBuf_ISR
Reads data from the CPU shared memory of a specified module and a buffer memory*1 in an intelligent function module (From instruction).
QBF_ControlLED_ISR
Controls USER LED of C Controller module.
QBF_Control7SegLED_ISR
Controls the 7-segment LED of the C Controller module.
QBF_WriteSRAM_ISR
Writes data to the battery backup RAM (user area).
QBF_ReadSRAM_ISR
Reads data from the battery backup RAM (user area).
: 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)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
10 11 12
SAMPLE PROGRAMS
13
EVENT NUMBER LIST
A
I
9.2 Bus Interface Function List
9 - 6
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
Category
Interrupt event control
C Controller's internal user or system device access
Table 9.3 Bus interface function for ISR (continued)
1)Q12DCCPU-V 2)Q06CCPU-V 3)Q06CCPU-V-B
Function name
Function
Availability
1)
2)
3)
QBF_EnableMultiCPUSyncInt_IS Enables a routine registered for a multiple CPU
R
synchronization interrupt.
QBF_DisableMultiCPUSyncInt_I Disables a routine registered for a multiple CPU
SR
synchronization interrupt.
QBF_EnableCpuInt_ISR
Enables a routine registered for an interrupt from another CPU.
*2
QBF_DisableCpuInt_ISR
Disables a routine registered for an interrupt from another CPU.
*2
QBF_EnableUnitInt_ISR
Enables a routine registered for an interrupt from an
*2
intelligent function module or an interrupt module.
QBF_DisableUnitInt_ISR
Disables a routine registered for an interrupt from an
*2
intelligent function module or an interrupt module.
QBF_WriteDevice_ISR
Writes data to the internal user or system devices of
*2
the C Controller module.
QBF_ReadDevice_ISR
Reads data from the internal user or system devices of
*2
the C Controller module.
QBF_SetDevice_ISR
Sets the internal user or system devices (bit devices)
*2
of the C Controller module.
QBF_ResetDevice_ISR
Resets the internal user or system devices (bit devices) of the C Controller module.
*2
* 2 Not available for the following C Controller module. · Q12DCCPU-V with serial number (first five digits) "12041" or earlier
: Available, : N/A
POINT
For details of the bus interface functions, refer to the Bus Interface Function HELP of SW3PVC-CCPU.
9 - 7
9.2 Bus Interface Function List
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 9.3 Programming Procedure
PROGRAMMING USING BUS INTERFACE FUNCTIONS
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
This section provides the procedure for programming using the bus interface functions or MELSEC data link functions.
10
Start
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Complete the settings of a C Controller module.
Install Workbench or Tornado into the development environment (personal computer).
C Controller Module User's Manual (Hardware Design, Function Explanation)
Manual for Workbench or Tornado
11
PROGRAMMING USING VxWorks API FUNCTIONS
Check that the image file in the system memory of the development environment (personal computer) matches with that of the C Controller module.
Activate Workbench or Tornado on the development environment (personal computer), and create a project of the user program.
Complete the settings for bus interface functions and MELSEC data link functions.
Create an user program using the bus interface functions and MELSEC data link functions.
Debug the user program with Workbench or Tornado.
No Is debugging completed?
Yes Write the user program created into the standard RAM, standard ROM, or CompactFlash card.
Create the script file "STARTUP.CMD", and write it into the standard RAM, standard ROM, or CompactFlash card.
Page 9-31, Section 9.7
Page 9-9, Section 9.4
Page 9-9, Section 9.4 Page 9-23, Section 9.5, Page 9-26, Section 9.6, Page 10-5, Section 10.5, Page 10-9, Section 10.6 Page 9-31, Section 9.7
Error codes of bus interface functions and MELSEC data link functions
HELP for each function
Page 9-46, Section 9.8
Page 9-51, Section 9.9
EVENT NUMBER LIST
SAMPLE PROGRAMS
12 13 A I
For the Q12DCCPU-V, back up the file in the standard RAM since the file may be cleared when the battery life has expired.
Page 9-46, Section 9.8, Page 12-1, CHAPTER 12
End Figure 9.2 Programming procedure
9.3 Programming Procedure
9 - 8
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9.4 Creating and Compiling a New Project of User Program
9.4.1 For the Q12DCCPU-V
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
This section explains:
· How to create a new project (
Page 9-9, Section 9.4.1 (1))
· How to compile (
Page 9-13, Section 9.4.1 (2))
· How to check the endian format (memory layout) of the execution file (
Page
9-16, Section 9.4.1 (3))
This section explains the procedures of when Wind River Workbench is used. When using
CW Workbench, refer to the CW Workbench Operating Manual.
(1) How to create a new project
1 Start Wind River Workbench.
2 Select [File] [New] [VxWorks Downloadable Kernel Module Project] from the menu bar.
3 Enter a project name in "Project name" and click the Next> button.
(To the next page)
9 - 9
9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V
PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9 (From the previous page)
4 Click the Next> button. (No setting is necessary.)
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING VxWorks API FUNCTIONS
11
5 Click the Next> button. (No setting is necessary.)
12
SAMPLE PROGRAMS
(To the next page)
13
EVENT NUMBER LIST
6 Select "SH7750gnule" and click the Finish button.
REFERENCE
A
To set the release mode, deselect "Debug Mode".
I
9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V
9 - 10
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
(From the previous page)
7 Right-click on the created project on the "Project Navigator" window and select [Properties] from the menu.
8 Open the <<Build Paths>> tab by selecting "Build Properties" in the tree on the left side of the screen. Add the settings of the include files for each function to "Include paths:" and click the OK button.
REFERENCE Use "/" as a delimiter of the folder path. "\" cannot be used. Add "-IC:/MELSEC/CCPU/DVx/Include" to the setting of the include file. (When SW3PVC-CCPU is installed to "C:\MELSEC")
9 Select [File] [New] [File] from the menu bar.
(To the next page)
9 - 11
9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V
PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9 (From the previous page)
10 Enter the file name of the source file in the "File name:" field and click the Finish button.
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
11
PROGRAMMING USING VxWorks API FUNCTIONS
11 Edit the source file and include the following include files.
12
Bus interface function: "QbfFunc.h"
MELSEC communication function: "Mdfunc.h"
SAMPLE PROGRAMS
13
EVENT NUMBER LIST
A
(Completed)
I
9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V
9 - 12
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
(2) How to compile
POINT
The following operations are required for compiling.
1 Right-click on the source file to be compiled on the "Project Navigator" window and select [Refresh] from the menu.
2 Right-click on the project to be compiled on the "Project Navigator" window and select [Rebuild Project] from the menu.
(To the next page)
9 - 13
9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V
PROGRAMMING USING BUS INTERFACE FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING VxWorks API FUNCTIONS
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9 (From the previous page) 3 Click the Generate Includes button. 10
4 Click the Next> button. (No setting is necessary.)
11
12
13
5 Click the Next> button. (No setting is necessary.)
A
I
SAMPLE PROGRAMS
EVENT NUMBER LIST
(To the next page)
9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V
9 - 14
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
(From the previous page)
6 Select only "SH7750gnule" to "Modify include search paths for selected build specs:" and click the Finish button.
(Completed)
7 Compiling process appears on the "Build Console" window as shown on the left.
8 When compiling is finished, user programs that are executable in the C Controller module are generated. The user programs are not generated if an error occurred during compiling. The user programs are saved with the following folder and file names.
9 Folder: <Folder where the project is saved>\SH7750gnule_DEBUG
10 File name: <Project name>.out
REFERENCE In the release mode, the user programs are saved in the folder where the project is saved.
9 - 15
9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
(3) How to check the endian format (memory layout) of the execution file
(a) Checking method
The endian format of the execution file can be checked by the objdumpsh
command of VxWorks. Execute the objdumpsh command on the VxWorks Development Shell from the
10
development environment (personal computer) as follows:*1
objdumpsh -p Execution file name [Enter]
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
* 1 Start the VxWorks Development Shell by selecting [Start] [All Programs] [Wind River] [VxWorks 6.4 and General Purpose Technologies] [VxWorks Development Shell].
11
PROGRAMMING USING VxWorks API FUNCTIONS
(b) Checking result The checking result is indicated as below.
Execution file name: file format elf32-shl
elf32-shl : Little endian
12
elf32-sh : Big endian
SAMPLE PROGRAMS
13
EVENT NUMBER LIST
A
I
9.4 Creating and Compiling a New Project of User Program 9.4.1 For the Q12DCCPU-V
9 - 16
9 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))
· How to check the endian format (memory layout) of the execution file (
9-22, Section 9.4.2 (3))
(1) How to create a new project
The screens shown in this section are of the Q06CCPU-V.
For the Q06CCPU-V-B, refer to REFERENCE .
Page
1 Start Tornado. When the work space automatically opens, proceed to step
7. If not, perform the following operations.
2 Select [File] [New Project] from the menu bar.
3 Select "Create downloadable application modules for VxWorks" and click the OK button.
4 Enter "Name", "Location", and "Workspace" and then click the Next> button.
9 - 17
(To the next page)
9.4 Creating and Compiling a New Project of User Program 9.4.2 For the Q06CCPU-V(-B)
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9
(From the previous page)
PROGRAMMING USING BUS INTERFACE FUNCTIONS
5 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)
10
Q06CCPU-V-B: SH7750gnu (Big endian)
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
REFERENCE This setting defines the endian format. The program does not run if the setting with a different endian format is selected.
11
6 Check that the settings of "Workspace" and "Tool Chain" are valid and then click the Finish button.
PROGRAMMING USING VxWorks API FUNCTIONS
12
SAMPLE PROGRAMS
EVENT NUMBER LIST
13
7 Open the <<Builds>> tab on the "Workspace" window.
A
I
(To the next page)
9.4 Creating and Compiling a New Project of User Program 9.4.2 For the Q06CCPU-V(-B)
9 - 18
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
(From the previous page)
8 Double-click the ( ) icon to display the lower item.
9 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)
9 - 19
9.4 Creating and Compiling a New Project of User Program 9.4.2 For the Q06CCPU-V(-B)
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9
(From the previous page)
PROGRAMMING USING BUS INTERFACE FUNCTIONS
10 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 OK button.
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
IMPORTANT Use "/" as a delimiter of the folder path.
"\" cannot be used.
For the include file setting, add the following according to
11
the model.(When the SW3PVC-CCPU is installed to
"C:\MELSEC")
Q06CCPU-V: "-IC:/Melsec/CCPU/Vx/Include"
Q06CCPU-V-B: "-IC:/Melsec/CCPU/VxB/Include"
PROGRAMMING USING VxWorks API FUNCTIONS
11 Select [File] [New] from the menu bar.
12
SAMPLE PROGRAMS
(Completed)
13
12 Select "C/C++ Source File", enter the source file name into "File name", and click the OK button.
EVENT NUMBER LIST
A
13 A screen to edit the source file appears.
Include "QbfFunc.h" when using the bus interface functions.
Include "MdFunc.h" when using the MELSEC
communication functions.
I
9.4 Creating and Compiling a New Project of User Program 9.4.2 For the Q06CCPU-V(-B)
9 - 20
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
(2) How to compile
POINT
The following operations are required for compiling.
1 In the <<Files>> tab on the "Workspace" window, right-click on the source file name to be compiled, and select [Dependencies] from the menu.
2 Check the source file name to be compiled, and click the OK button.
3 Select [Build] [Rebuild All] from the menu bar.
(To the next page)
9 - 21
9.4 Creating and Compiling a New Project of User Program 9.4.2 For the Q06CCPU-V(-B)
PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9 (From the previous page)
4 Compiling process appears on the screen as shown on the left.
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
5 When compiling is finished, user programs that can be
executed in the C Controller module are generated.
6 The user programs are not generated if an error occurred
11
during compiling.
PROGRAMMING USING VxWorks API FUNCTIONS
7
8 The user programs are saved with the following folder and file names.
9 Folder: <Folder where the project is saved>\SH7750gnule
10 File name: <Project name>.out
12
SAMPLE PROGRAMS
(Completed)
REFERENCE For the Q06CCPU-V-B, user programs are generated in the "SH7750gnu" folder.
13
EVENT NUMBER LIST
(3) How to check the endian format (memory layout) of the execution file
(a) Checking method
The endian format of the execution file can be checked by the objdumpsh
command of VxWorks. Execute the objdumpsh command on the command prompt from the development
A
environment (personal computer) as follows:*1
objdumpsh -p Execution file name [Enter]
* 1 To use the objdumpsh command, execute the following file and set environment variable.
<Tornado InstallDir> \host\x86-win32\bin\torVars.bat
I
(<Tornado InstallDir> is a folder where Tornado has been installed.)
(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 9.4.2 For the Q06CCPU-V(-B)
9 - 22
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9.5 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 timer error interrupt.*1 (QBF_EntryWDTInt function)
Set and start the watchdog timer. *1 (QBF_StartWDT function)
*1 Set the watchdog timer for the user program to monitor the hardware, user program runaway, and processing overtime. This process can be skipped when monitoring is not necessary.
Control the module by using bus interface functions.
Acquire the information of the C Controller module. (QBF_ReadStatusEx function)
Has error occurred?
Yes (Error occurrence)
No (Normal)
Reset the watchdog timer. *1 (QBF_ResetWDT function)
Error notification
Stop the watchdog timer.*1 (QBF_StopWDT function)
Deregister the routine of the user watchdog timer error interrupt. (QBF_EntryWDTInt function)
Close the bus. (QBF_Close function)
Task end Figure 9.3 Bus interface function programming flow
9 - 23
9.5 Programming Flow for Bus Interface Functions
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9 The following flowchart shows the outline in the case of a user watchdog timer error interrupt.
Interrupt routine (interrupt program) start
PROGRAMMING USING BUS INTERFACE FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Access the SRAM data. *2 (QBF_WriteSRAM/QBF_ReadSRAM function)
Register the event history. *2 (QBF_RegistEventLog function)
*2 Specify "1" (ISR) for the argument of the function, "sFlg" since starting from inerrupt routine (interrupt program).
10
Interrupt routine (interrupt program) end
Figure 9.4 User watchdog timer error interrupt programming outline
11
(2) Precautions for using the bus interface functions
PROGRAMMING USING VxWorks API FUNCTIONS
(a) Programming precautions
1) Open/close processing
Perform the bus open and close processing (QBF_Open function/QBF_Close
functions) only once at the beginning and end of the program respectively.
12
Communication performance will decrease if open/close is repeated at each
communication.
SAMPLE PROGRAMS
2) Simultaneous processing of bus interface functions
Bus interface functions are serialized in the C Controller module for
processing.
When the MELSEC data link function are requested simultaneously in multiple tasks, one of the task starts its processing and the other tasks will have to wait
13
until the processing is complete.
EVENT NUMBER LIST
3) User watchdog timer error interrupt When using the bus interface functions on multiple tasks, register the routine for the user watchdog timer error interrupt from one of the tasks.
4) Clock setting When setting the clock of the C Controller module, confirm that both the
A
QBF_WaitEvent and QBF_WaitUnitEvent functions are not in process.
5) Remote STOP/PAUSE and bus interface function execution result
When the operation status of the C Controller module is remote STOP or
remote PAUSE, the execution result of the following operations by the user
program will be STOP/PAUSE error. · Output (Y) (QBF_Y_OutBitExfunction, QBF_Y_OutWordEx function)
I
· Buffer memory writing (QBF_ToBuf function)
Y output and buffer memory writing can be executed from the <<Module monitoring>> tab of the C Controller setting utility.
6) The sequence program control function (QBF_ControlProgram function) can be executed only to the High Performance model QCPU.
7) For tasks that use bus interface funtions, do not use a mutual-exclusion semaphore that specifies the SEM_INVERSION_SAFE option.
9.5 Programming Flow for Bus Interface Functions
9 - 24
9 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. · Module error (Xn0) is off (normal) · Module ready (XnF) is on (operable) · Own data link status (Xn1) is on (in data link) Write to/read from the own station is terminated normally irrespective of the above conditions.
(c) Precautions for host station device access via MELSECNET/H module When accessing via MELSECNET/H module, create a user program that provides interlocks to enable writing to/reading from the host station device. Data become valid only when the following conditions are satisfied. · Module status (SB20) is off (normal) · Baton pass status of host station (SB47) is off (normal) · Data link status of host station (SB49) is off (in data link) Write to/read from the host station is terminated normally irrespective of the above conditions.
(d) Precautions for own station device access via CC-Link IE Controller Network module When accessing via CC-Link IE Controller Network 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. · Data link status of own station (SB49) is off (in data link) · Data link status (the bit corresponding to the communication targets in SWB0 to B7 which is read from the own station) is off (normal)
Write to/read from the own station is terminated normally irrespective of the above conditions.
9 - 25
9.5 Programming Flow for Bus Interface Functions
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 9.6 Precautions for Functions
PROGRAMMING USING BUS INTERFACE FUNCTIONS
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
This section provides precautions for the bus interface function and MELSEC data link function.
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(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.
Create user programs in either little or big endian that is appropriate to the model
used.
11
(Set the compiler by selecting "A toolchain" when creating a project on Tornado.
(
Page 9-17, Section 9.4.2)
PROGRAMMING USING VxWorks API FUNCTIONS
(2) Execution type priority
Set the priority of a task for executing the FTP user program as described below.
(a) When access is not made via FTP during user program execution
12
Set the priority of the user program task to 100 or more (100 to 255).
If the priority is set within 0 to 99, the system may not operate properly.
SAMPLE PROGRAMS
(b) When access is made via FTP during user program execution
The actual FTP processing (task) of the C Controller module is performed at the
priority of 200.
When accessing via FTP during user program execution, perform programming
13
as described below.
· Set the priority of the user program task within 201 to 255.
· When setting the priority of the user program task within 100 to 200, insert
EVENT NUMBER LIST
wait processing (such as taskDalay) in the user program to enable the actual
FTP processing.
(3) User program execution
A
Execute a user program by starting a task from the script file.
(
Page 9-51, Section 9.9)
The system may malfunction if the user program is executed without a task being
started.
(4) When communicating from utility while a user program is running
I
If a communication from utility may affect the user program, lower the task priority of
utility communication than that of the user program.
9.6 Precautions for Functions
9 - 26
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
(5) To communicate with a target device by Ethernet communication (excluding utility communications)
Check the port number being used in the C Controller module by using the VxWorksstandard "inetstatShow" command. Do not use any port number that has already been used. Normal communication may not be available if used.
Execute the "inetstatShow" command as follows: [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. Write it to a CompactFlash card, network device (such as FTP/NFS/netDrv driver) file, or RAM disk. For details of network devices and RAM disks, refer to the manual for VxWorks.
(7) CompactFlash card replacement
Refer to the C Controller Module User's Manual (Hardware Design, Function
Explanation) when replacing the CompactFlash card while the power is on.
Close all the files being written if any. (Program example
Page 12-1, CHAPTER
12)
9 - 27
9.6 Precautions for Functions
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
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.
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(9) When a user watchdog timer cannot be reset
A user watchdog timer error occurs when the user watchdog timer cannot be reset
due to some reasons such as user program runaway.
When a user watchdog timer has occurred, perform the following.
· Increase the WDT time set by the QBF_StartWDT function. · Lower the CPU utilization of tasks that require high utilization.
11
PROGRAMMING USING VxWorks API FUNCTIONS
Or set them not to operate.
· Review the user program.
After the above operations, reset the C Controller system.
For resetting, refer to the C Controller Module User's Manual (Hardware Design,
Function Explanation).
12
(10)Relation between system tasks and the system watchdog timer, user
SAMPLE PROGRAMS
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.
· Shell command
· Workbench/Tornado connection
13
· File access
EVENT NUMBER LIST
· Mount/unmount of CompactFlash card
· Ethernet communications
· NFS server communication
If any of the above is used, CPU utilization for a system task with high priority may
increase and a system watchdog timer error, a user watchdog timer error, and link refresh timeout may occur more frequently.
A
For the link refresh timeout, the rate of occurrence may also increase when bus
interface driver processing (connections with peripheral devices or communication
with an intelligent function module, etc.) is used.
(11)IP address setting
The IP address of the C Controller module cannot be set from the user program.
I
Set it in the <<Online operation>> tab of C Controller setting utility.
9.6 Precautions for Functions
9 - 28
9 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. To power off or reset the C Controller system, perform the following first.
(a) When writing data to a file in the standard RAM or standard ROM Close the file where data are being written. (Program example CHAPTER 12)
Page 12-1,
(b) When writing data to a file in a CompactFlash card
Close the file where data are being written, and unmount the CompactFlash card.
(Program example
Page 12-1, CHAPTER 12)
For halting the CompactFlash card processing, refer to the C Controller Module
User's Manual (Hardware Design, Function Explanation)
(13)Login user
The login user settings are cleared and return to default when the C Controller module is powered off or is reset. To retain the login user settings, describe a registration (adding/deleting) of the settings in a script file.
Describe either of the following in the script file.
· Directly describe the login user operation commands (loginUserAdd function or loginUserDelete function).
· Provide a description that starts the user program task for login user operation. For login user settings, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
(14)VxWorks real-time process applications
The C Controller module does not support applications running in VxWorks real-time process. Create a user program as an application based on the VxWorks kernel.
9 - 29
9.6 Precautions for Functions
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
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
10
· QBF_RegistEventLog
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
· QBF_WriteSRAM
· QBF_ReadSRAM
Do not use bus interface functions and MELSEC data link functions other than the
above in the interrupt routine (interrupt program). Using any of those functions may
cause the operating system to run away. When using the functions offered by the operating system, understand the restrictions
11
on Interrupt Service Routine of VxWorks 6.4.
For the restrictions on Interrupt Service Routine of VxWorks 6.4, refer to VxWorks
Kernel Programmer's Guide 6.4.
PROGRAMMING USING VxWorks API FUNCTIONS
(16)Functions that can be used in the interrupt routine (interrupt program)
registered by the QBF_EntryWDTInt function when using the Q06CCPU- 12
V(-B)
SAMPLE PROGRAMS
The following functions can be used in the interrupt routine (interrupt program)
registered by the QBF_EntryWDTInt function when using the Q06CCPU-V(-B).
· QBF_RegistEventLog
· QBF_WriteSRAM
· QBF_ReadSRAM
13
Do not use bus interface functions other than the above or MELSEC data link
EVENT NUMBER LIST
functions in the interrupt routine (interrupt program). Using any of those functions may
cause the operating system to run away.
When using the functions offered by the operating system, understand the restrictions
on Interrupt Service Code of VxWorks 5.4.
For the restrictions on Interrupt Service Code of VxWorks 5.4, refer to VxWorks Kernel Programmer's Guide 5.4.
A
I
9.6 Precautions for Functions
9 - 30
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9.7 Precautions for Program Debugging
9.7.1 For Q12DCCPU-V
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Specifying a VxWorks image file and IP address
To debug the user program, specify the following for Workbench. · IP address of the C Controller module · The same VxWorks image file as that of the C Controller module
VxWorks image file
Must match !
VxWorks image file
Development environment (personal computer)
C Controller module
(a) Specifying method
1) Check that the VxWorks image file in the system memory of the development
environment (personal computer) is identical with that of the C Controller
module.
(
Page 9-33, Section 9.7.1 (1) (b))
2) Start Workbench.
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
Next> button.
9 - 31
9.7 Precautions for Program Debugging 9.7.1 For Q12DCCPU-V
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9 5) Set "Backend settings" as follows.
PROGRAMMING USING BUS INTERFACE FUNCTIONS
Table 9.4 Backend settings
Backend: Cpu:
Item
Target name / IP address:
Port:
Value wdbrpc SH-4A 192.168.3.3 (If the IP address of the C Controller module has been changed, enter the latest one.) " " blank
6) Select the "File" radio button in the "Kernel image" field and click the Browse button.
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
10 11 12
SAMPLE PROGRAMS
7) Select "*" in "Files of type" to select the VxWorks image file and click the Finish button.
13
EVENT NUMBER LIST
For the folder where the VxWorks image file is stored, refer to the following. Page 9-33, Section 9.7.1 (1) (b)
A
I
9.7 Precautions for Program Debugging 9.7.1 For Q12DCCPU-V
9 - 32
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
(b) VxWorks image file VxWorks image files are required to be copied from C Controller module to the development environment (personal computer) by FTP.
1) VxWorks image file storage source VxWorks image files are stored in the following system drive of C Controller module.
Table 9.5 VxWorks image file storage source
Model Q12DCCPU-V (Basic mode) Q12DCCPU-V (Extended mode)
File \SYSTEMROM\OS_IMAGEFILE\Q12DCCPU-V_XXXXX-Y*1 \SYSTEMROM\OS_IMAGEFILE\Q12DCCPU-V_XXXXX-Y_ModeEX*1
* 1 XXXXX: First five digits of the serial No. of the C Controller module Y : Function version of the C Controller module For the checking method of the serial No. and function version, refer to the following manuals. Q12DCCPU-V(Basic mode):
C Controller Module User's Manual (Hardware Design, Function Explanation) Q12DCCPU-V(Extended mode):
Setting/Monitoring Tools for the C Controller Module Operating Manual
2) VXWorks image file copy destination
Copy the VxWorks image files from C Controller module to the development
environment (personal computer) by FTP. (
Page 9-46, Section 9.8)
Table 9.6 Example of VXWorks image file copy destination
Model Q12DCCPU-V (Basic mode) Q12DCCPU-V (Extended mode)
File C:\MELSEC\CCPU\DVx\Tools\
3) When VxWorks image files are not identical When the VxWorks image file of the development environment (personal computer) is not identical with that of the C Controller module, copy the image file from the C Controller module to the development environment (personal
computer) via FTP. (
Page 9-46, Section 9.8)
POINT
When the VxWorks image files in the C Controller module and in Workbench are not identical, a system watchdog timer error may occur in the C Controller module. In addition, debugging cannot be performed normally.
Remark For other debugging methods, refer to the manual for Workbench.
9 - 33
9.7 Precautions for Program Debugging 9.7.1 For Q12DCCPU-V
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
(2) 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.
10
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.
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
[Calculation formula]
Timeout time is determined by the following calculation formula.
11
Timeout time = net.inet.tcp.keepidle
+ (net.inet.tcp.keepintvl 8 (Retry count)*1) [ms]
PROGRAMMING USING VxWorks API FUNCTIONS
Default value of the C Controller module: 30000 (30 sec.) Default value of VxWorks: 7800000 (2 hr. 10 min.)
net.inet.tcp.keepidle: Time from line disconnection to the first retry (ms)
12
Initial value for C Controller module: 22000
SAMPLE PROGRAMS
net.inet.tcp.keepintvl:
Initial value for VxWorks: 7200000 Retry interval (ms)
Initial value for C Controller module: 1000
Initial value for VxWorks: 75000
* 1 The number of retries cannot be changed.
[Setting method]
13
The following explains how to set the initial value to 30 seconds.
EVENT NUMBER LIST
· Setting while the C Controller module is in operation
1) Connect the line to the C Controller module with the Telnet tool.
2) Execute the following two Sysct1() commands with the Telnet tool to set the timeout time to the initial value.
A
Sysctl("net.inet.tcp.keepidle = 22000")
Sysctl("net.inet.tcp.keepintvl = 1000") 3) Close the Telnet connection.
· Setting at the timing of starting C Controller module
1) Describe the following two Sysct1() commands on the script file,
I
"STARTUP.CMD".
Sysctl("net.inet.tcp.keepidle = 22000")
Sysctl("net.inet.tcp.keepintvl = 1000") 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 9.7.1 For Q12DCCPU-V
9 - 34
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
(3) Precautions for executing a Shell command from Workbench Shell or the Telnet tool
1) When executing a Shell command from Workbench Shell When executing a Shell command from Workbench Shell, pay attention to the following since the entered Shell commands operate on the task of priority 1 in the C Controller module. · Only alphanumeric characters and special characters can be used. · Some commands, such as those exclusively using the CPU module and those including characters other than alphanumeric characters and special characters, may be regarded as a command causing a watchdog timeout error, a control code (such as "CTRL + X"), or being garbled. As a result, a system error, such as a system watchdog timer error, or stop may occur in the C Controller module. Pay full attention to the command when entering it. · Some commands (example: the status-indicating Show command) may disable an interrupt for a long time. During the time, processing called from an interrupt routine (interrupt program) (example: bus interface functions for ISR) is not executed. Interrupts that are expected to occur at fixed intervals, such as multiple CPU synchronous interrupt, may delay. When executing a command, pay attention to the above.
A VxWorks message may appear on Shell during connecting from Shell to the C Controller module. For messages of VxWorks, refer to the manual for VxWorks or Workbench.
2) When executing the Shell command from the Telnet tool Make one to one connection between the Telnet tool and the C Controller module. Connection cannot be made from multiple Telnet tools to the same C Controller module. 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.
9 - 35
9.7 Precautions for Program Debugging 9.7.1 For Q12DCCPU-V
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9
The Shell commands entered by the Telnet tool of the development environment (personal computer) operate on the task of priority 1 in the C Controller module. Pay full attention to the command when entering it.
PROGRAMMING USING BUS INTERFACE FUNCTIONS
When using a Shell command, pay attention to the following.
10
· Only alphanumeric characters and special characters can be used.
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
· Some commands, such as those exclusively using the CPU module and
those including characters other than alphanumeric characters and
special characters, may be regarded as a command causing a watchdog
timeout error, a control code (such as "CTRL + X"), or being garbled. As a
result, a system error, such as a system watchdog timer error, or stop may occur in the C Controller module. Pay full attention to the command when
11
PROGRAMMING USING VxWorks API FUNCTIONS
entering it.
· Some commands (example: the status-indicating Show command) may
disable an interrupt for a long time.
During the time, processing called from an interrupt routine (interrupt
program) (example: bus interface functions for ISR) is not executed.
Interrupts that are expected to occur at fixed intervals, such as multiple
12
CPU synchronous interrupt, may delay. When executing a command, pay
attention to the above.
SAMPLE PROGRAMS
A VxWorks message may appear on the Telnet tool screen during a Telnet
connection to the C Controller module.
For messages of VxWorks, refer to the manual for VxWorks or Workbench.
13
3) When executing the Shell command from Workbench Shell or the Telnet tool
EVENT NUMBER LIST
· Execution of VxWorks reboot command
Do not reboot VxWorks by executing the reboot function or pressing the
CTRL + X keys.*1
If VxWorks is rebooted, the C Controller module does not start properly.
Reset it in the C Controller module. For resetting, refer to the C Controller Module User's Manual (Hardware
A
Design, Function Explanation).
* 1 Do not enter characters other than alphanumeric characters or special characters in Shell either
since they may be regarded as a control code.
· Execution of command without argument specified
If a command that requires an argument is executed without any
argument specified, 0 is substituted for the argument. A system error or
I
stop (such as a system watchdog timer error) may occur in the C
Controller module depending on the command (example: command that
occupies CPU processing).
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 9.7.1 For Q12DCCPU-V
9 - 36
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
(4) Precautions for debugging from Workbench
(a) When downloading by specifying the user program from Workbench A system error or stop (such as a system watchdog timer error) may occur in the C Controller module during downloading if the program is too large. When a system error or stop (such as a system watchdog timer error) has occurred, take either of the following measures. · Increase the value of "WDT (watchdog timer) setting" on the System settings tab of the C Controller setting utility. · Load the program in the C Controller module before debugging.
An interrupt to the C Controller module may be disabled during debugging. During the time, processing called from an interrupt routine (interrupt program) (example: bus interface functions for ISR) is not executed. Interrupts that are expected to occur at fixed intervals, such as multiple CPU synchronous interrupt, may delay. For debugging from Workbench, pay attention to the above.
(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.
9 - 37
9.7 Precautions for Program Debugging 9.7.1 For Q12DCCPU-V
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9
9.7.2 For the Q06CCPU-V(-B)
PROGRAMMING USING BUS INTERFACE FUNCTIONS
(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.
10
VxWorks image file
Must match !
VxWorks image file
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
11
PROGRAMMING USING VxWorks API FUNCTIONS
Development environment (personal computer)
C Controller module
12
SAMPLE PROGRAMS
(a) Specifying method of VxWorks image file
1) Check that the VxWorks image file in the system memory of the development
environment (personal computer) is identical with that of the C Controller
module.
(
Page 9-39, Section 9.7.2 (1) (b))
13
EVENT NUMBER LIST
2) Start Tornado.
3) Select [Tools] [Target Server] [Configure] to open the "Configure Target Servers" dialog box.
4) Select "Core File and Symbols" in the "Target Server Properties" pull-down
menu.
A
5) Select the "File" radio button and specify the storage location of the VxWorks
image file to the text box.
For the VXWorks image file copy destination, refer to the following section.
(
Page 9-39, Section 9.7.2 (1) (b))
6) Click the OK button.
I
9.7 Precautions for Program Debugging 9.7.2 For the Q06CCPU-V(-B)
9 - 38
9 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.
4) 5)
9 - 39
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.
1) VxWorks image file storage source VxWorks image files are stored in the following system drive of C Controller module.
Table 9.7 VxWorks storage source
Model Q06CCPU-V Q06CCPU-V-B
File \SYSTEMROM\OS_IMAGEFILE\Q06CCPU-V_XXXXX-Y*1 \SYSTEMROM\OS_IMAGEFILE\Q06CCPU-V-B_XXXXX-Y*1
* 1 XXXXX: First five digits of the serial No. of the C Controller module Y : Function version of the C Controller module For the checking method of the serial No. and function version, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
2) VXWorks image file copy destination
Copy the VxWorks image files from C Controller module to the development
environment (personal computer) by FTP. (
Page 9-46, Section 9.8)
Table 9.8 Example of VXWorks image file copy destination
Model Q06CCPU-V Q06CCPU-V-B
File C:\MELSEC\CCPU\Vx\Tools\ C:\MELSEC\CCPU\VxB\Tools\
3) When VxWorks image files are not identical When the VxWorks image file in the development environment (personal computer) is not identical with that of the C Controller module, copy the image file from the C Controller module to the development environment (personal
computer) via FTP. (
Page 9-46, Section 9.8)
POINT
When the VxWorks image files in the C Controller module and in Workbench are not identical, a system watchdog timer error may occur in the C Controller module. In addition, debugging cannot be performed normally.
9.7 Precautions for Program Debugging 9.7.2 For the Q06CCPU-V(-B)
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
Remark For other debugging methods, refer to the manual for Tornado.
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(2) IP address setting of C Controller module
10
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.
1) Start Tornado. 2) Select [Tools] [Target Server] [Configure] from the menu bar to open the
11
"Configure Target Servers" dialog box.
PROGRAMMING USING VxWorks API FUNCTIONS
3) Select "Back End" in the "Target Server Properties" pull-down menu.
4) Select "wdbrpc" from the "Available Back Ends" list.
5) In "Target Name/IP Address", set the IP address of the C Controller module to
be connected.
12
As the IP address for the C Controller module, set the same value as in "IP
address" in the <<Online operation>> tab of the C Controller setting utility.
6) Click the OK button.
SAMPLE PROGRAMS
13
EVENT NUMBER LIST
3)
4)
A
5)
I
Figure 9.7 IP address setting of the C Controller module
Remark For other debugging methods, refer to the manual for Tornado.
9.7 Precautions for Program Debugging 9.7.2 For the Q06CCPU-V(-B)
9 - 40
9 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" dialog box. 3) Select "Core File and Symbols" in the "Target Server Properties" pull-down
menu. 4) Check the "Synchronize Target/Host Symbol Tables" checkbox. 5) Click the OK button.
3) 4)
Figure 9.8 Symbol information synchronization setting
6) Select [Tools] [Options] from the menu bar to open the "Options" dialog box, and select the "Tornado Registry" tab.
7) Select the "Remote registry" radio button and specify the IP address or host name of the development environment (personal computer).
8) Click the OK button.
7)
Figure 9.9 Development environment (personal computer) IP address setting
9 - 41
9.7 Precautions for Program Debugging 9.7.2 For the Q06CCPU-V(-B)
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
Remark For other debugging methods, refer to the manual for Tornado.
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(4) Shell display setting
10
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.
1) Start Tornado. 2) Select [Tools] [Target Server] [Configure] to open the "Configure Target
11
Servers" dialog box.
PROGRAMMING USING VxWorks API FUNCTIONS
3) Select "Console and Redirection" in the "Target Server Properties" pull-down menu.
4) Check the "Redirect Target IO" checkbox.
5) Click the OK button.
12
SAMPLE PROGRAMS
EVENT NUMBER LIST
13
3) 4)
A
Figure 9.10 Shell display setting
Remark
I
For other debugging methods, refer to the manual for Tornado.
9.7 Precautions for Program Debugging 9.7.2 For the Q06CCPU-V(-B)
9 - 42
9 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.
[Calculation formula] The timeout time is determined by the following calculation formula.
Timeout time = tcp_keepidle + (tcp_keepintvl 2 tcp_keepcnt) [s]
Initial value: 15000 (4 hours and 10 minutes)
tcp_keepidle: tcp_keepintvl: tcp_keepcnt:
Time from disconnection to the first retry (s) Initial value: 14400
Retry interval (in 0.5s units) Initial value: 150
Number of retries Initial value: 8
[Setting method] The following explains how to set the initial value to 4 hours and 10 minutes.
· Setting while the C Controller module is in operation
1) Connect the line to the C Controller module with the Telnet tool. 2) Set the following three external variables with the Telnet tool to change the
timeout time to the initial value. tcp_keepidle = 14400 tcp_keepintvl = 150 tcp_keepcnt = 8
3) Close the Telnet connection.
· Setting at the timing of starting C Controller module
1) Describe the following three external variable settings on the script file, "STARTUP.CMD". tcp_keepidle = 14400 tcp_keepintvl = 150 tcp_keepcnt = 8
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 - 43
9.7 Precautions for Program Debugging 9.7.2 For the Q06CCPU-V(-B)
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
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.
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
· Only alphanumeric characters and special characters can be used.
· Some commands, such as those exclusively using the CPU module and
those including characters other than alphanumeric characters and
special characters, may be regarded as a command causing a watchdog
timeout error, a control code (such as "CTRL + X"), or being garbled. As a
11 result, a system error, such as a system watchdog timer error, or stop may
occur in the C Controller module. Pay full attention to the command when
entering it.
PROGRAMMING USING VxWorks API FUNCTIONS
A VxWorks message may appear on the Telnet tool screen during a Telnet
connection to the C Controller module.
For messages of VxWorks, refer to the manual for VxWorks or Tornado.
12
SAMPLE PROGRAMS
2) When executing the Shell command from the Telnet tool
Make one-to-one connection between the Telnet tool and the C Controller
module.
Connection cannot be made from multiple Telnet tools to the same C
Controller module.
When exchanging the Telnet tool with another, first close the connection with
13
the currently used Telnet tool, and then connect the line to the C Controller
module from another Telnet tool.
EVENT NUMBER LIST
Pay attention to the following since the Shell commands entered by the Telnet
tool of the development environment (personal computer) operate on the task
of priority 2 in the C Controller module.
A
When using Shell commands, pay attention to the following.
· Only alphanumeric characters and special characters can be used.
· Some commands, such as those exclusively using the CPU module and
those including characters other than alphanumeric characters and
special characters, may be regarded as a command causing a watchdog
timeout error, a control code (such as "CTRL + X"), or being garbled. As a
I
result, a system error, such as a system watchdog timer error, or stop may
occur in the C Controller module. Pay full attention to the command when
entering it.
A VxWorks message may appear on the Telnet tool screen during a Telnet connection to the C Controller module. For messages of VxWorks, refer to the manual for VxWorks or Tornado.
9.7 Precautions for Program Debugging 9.7.2 For the Q06CCPU-V(-B)
9 - 44
9 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.*1 If VxWorks is rebooted, the C Controller module does not start properly. Reset it in the C Controller module. For resetting, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
* 1 Do not enter characters other than alphanumeric characters or special characters in Shell either since they may be regarded as a control code.
· Execution of command without argument specified If a command that requires an argument is executed without any argument specified, 0 is substituted for the argument. Some commands may cause a system error or stop (such as a system watchdog timer error) in the C Controller module. Before executing a command, confirm the specifications and specified argument of the command.
Example) Do not execute the close command without the argument specified. If executed, the resource reserved in the VxWorks system will be closed.
9 - 45
9.7 Precautions for Program Debugging 9.7.2 For the Q06CCPU-V(-B)
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 9.8 Program Registration
PROGRAMMING USING BUS INTERFACE FUNCTIONS
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
To register respective file to the C Controller module, write the file to a standard RAM or standard ROM of the C Controller module or a CompactFlash card.
Table 9.9 How to write to each drive
Writing method
Registration via FTP Copy registration from CompactFlash card Copy registration from development environment (personal computer) to CompactFlash card
Standard RAM
Program storage location
Standard ROM
CompactFlash card
RAM disk (When creating
a RAM disk)
: Available, : N/A
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
10 11
PROGRAMMING USING VxWorks API FUNCTIONS
POINT 12 Before registering a file to the standard RAM, standard ROM, or a CompactFlash
card, close all the tasks running on the C Controller module.
SAMPLE PROGRAMS
(1) Registration via FTP
This section explains file registration to the C Controller module via FTP.
(a) Drives and operations allowed via FTP The following table indicates the drive names and operations allowed for registration via FTP.
Table 9.10 Drives available for FTP
Drive Standard RAM Standard ROM CompactFlash card System drive
Drive name /RAM /ROM /CF /SYSTEMROM
Operation Write/read available Write/read available Write/read available Only read available
RAM disk (When creating a RAM disk)*2
/RAMDISK*1
Write/read available
* 1 This drive name is for the sample program (MakeRAMDisk.c). Do not use "/RAM", "/ROM", "/CF", or "/SYSTEMROM" for a drive name of a RAM disk. The system may not operate properly if any of the above name is used.
* 2 The RAM disk drive name is not displayed in Windows® 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. Example) When the RAM disk drive name is "/RAMDISK," enter the following.
ftp://192.168.3.3/RAMDISK
EVENT NUMBER LIST
13 A I
9.8 Program Registration
9 - 46
9 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).
(c) Precautions for program registration via FTP
1) Login user setting The user login setting of the C Controller module is for limiting users and setting operation of the C Controller module. It does not completely prevent illegal access from the outside.
2) When security against illegal access from the outside is needed
Take measures at user's discretion when it is necessary to secure the safety of
the C Controller system against illegal access from the outside.
(
C Controller Module User's Manual (Hardware Design, Function
Explanation)
3) When registering by overwriting using FTP Before registering a file of the C Controller module by overwriting using FTP, close the file being opened by a user program. If the registering the file by overwriting without closing them, the registration may fail.
4) Number of FTP tools that are simultaneously connectable Up to 10 FTP tools can be simultaneously connected to the C Controller module. Connection may become unavailable if the FTP tool is repeatedly used since Windows® Explorer does not immediately disconnect the connection when terminated. When a connection is not available in Explorer, perform either of the following. · Terminate Explorer from Windows® Task Manager. · Reconnect 200 seconds after terminating Explorer. · Use the FTP tool other than in Explorer.
9 - 47
9.8 Program Registration
PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9 5) Precautions for Internet Explorer6 Service Pack2 · When the following dialog box appeared, restart Internet Explorer6 Service Pack2 or use another FTP tool.
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Figure 9.11 Dialog box
· When the file is not displayed in Internet Explorer6 Service Pack2 after
registering it to the C Controller module, update the information by
pressing the [F5] key. If the file is found not registered, check the free space of the registration
11
destination.
· When too many files are registered into the directory created in the C
Controller module, the total size may not be displayed correctly.
In this case, use another FTP tool.
PROGRAMMING USING VxWorks API FUNCTIONS
SAMPLE PROGRAMS
(d) Registration procedure using FTP The following indicates an example procedure of a registration of a user program
12
via FTP using Windows® Explorer.
1) Start Explorer and enter the address of the C Controller module into the Address bar in the following format.
ftp://<User name>:<Password>@<IP address of the C Controller module>
<Drive name.>
13
· 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
EVENT NUMBER LIST
A
Figure 9.12 Logging into the standard RAM with the settings for module initialization
I
9.8 Program Registration
9 - 48
9 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.
*1
*1
Drag & drop to transfer a file.
Figure 9.14 File operation
POINT
1. Other than Explorer, registration via FTP is available by Internet Explorer and the FTP command which is started up from command prompt. (For error messages of Internet Explorer, go to Microsoft® Help and Support, enter keyword such as "Internet Explorer" and "FTP", and check the information.)
2. If registration by FTP fails when using Internet Explorer7, use other FTP tools such as Explorer.
9 - 49
9.8 Program Registration
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
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
10
Controller modules.
In the following copy registration procedure, an example with "STARTUP.CMD" is
used as a script file for installation into the standard RAM.
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(a) Copy registration procedure from CompactFlash card to standard RAM
PROGRAMMING USING VxWorks API FUNCTIONS
1) Install the CompactFlash card into the development environment (personal
computer) and write the following files to it.
11
Table 9.12 Written file list
File name STARTUP.CMD STARTUP.RAM ********.out
Description Script file for installation into the standard RAM Script file to be used in the standard RAM User program to be used in the standard RAM
2) Remove CompactFlash card from the development environment (personal computer), and install it in the C Controller module.
12
SAMPLE PROGRAMS
3) Power on the C Controller module.
4) The installation script file "STARTUP.CMD" in the CompactFlash card is started and each file in the CompactFlash card is copied to the standard RAM of the C Controller module.
13 5) When copying is completed, the "sysLedSet" command is executed, and "FF" is displayed in the 7-segment LED.
EVENT NUMBER LIST
6) After confirming that "FF" is displayed in the 7-segment LED, power off the C Controller module and remove the CompactFlash card.
7) When the C Controller module is powered on, the script file copied into the
standard RAM is started and a user program is executed.
(b) Program example of script file for installation into standard RAM
A
STARTUP.CMD
copy "/CF/project.out", "/RAM/project.out"
1)
copy "/CF/STARTUP.RAM", "/RAM/STARTUP.CMD"
2)
sysLedSet(OxFF)
3)
1) The user program "project.out" in the CompactFlash card is copied as
I
the user program "project.out" of the standard RAM.
2) The script file for standard RAM "STARTUP.ROM" in the CompactFlash card is copied as the script file "STARTUP.CMD" of the standard RAM.
3) Describe the command "sysLedSet(0xFF)" at the end of the installation script file for confirmation of the completion of the copy.
Figure 9.15 Program example of a script file for installation
9.8 Program Registration
9 - 50
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9.9 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. of the user program.
Standard RAM/ standard ROM 1) STARTUP.CMD
2) User program (***.out)
Describe the loading location, startup order, etc. of the user program.
A file specified in STARTUP.CMD
9 - 51
Figure 9.16 Script file is stored into the standard RAM or standard ROM
(2) Precautions for creating a script file
(a) Restrictions on command description In the script file, only one command can be described in one line.
For the Q06CCPU-V(-B), up to 128 characters can be specified in one command
(in one line).
If more than 128 characters are specified, the following stop error occurs.
· Other (error code: 2502, CAN'T EXE.PRG.)
The error (event No.:0xC0000111) is registered to the event history. (
Page
13-5, CHAPTER 13 (6))
(b) Argument that can be specified for one command. Up to 12 arguments can be specified for one command.
(c) When C++ function is executed in a script file Describe the function declaration part of C++ source code as follows.
extern "C" { Function declaration part }
(d) At user program start Describe a command that starts the task (priority 100 to 255) when the user program is executed. The system may malfunction if the user program is executed without the task being started.
(e) Description of comment statement To describe a comment statement, describe "//" at the beginning of a command (line). The line where "//" has been described is handled as a comment statement. No restrictions are applied on the number of characters in a comment statement.
9.9 Creating a Script File "STARTUP.CMD"
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
(f) Task activation
Always specify the VX_FP_TASK option for the third argument of taskSpawn
when activating a task that:
· Performs floating-point operations.
· Calls a function that returns a floating-point value. · Calls a function that takes a floating-point value as an argument.
10
If the above task is activated without the VX_FP_TASK option specified, the
operating system may run away.
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Use the following value when specifying a VX_FP_TASK option for the third
argument of taskSpawn in a script file.
Table 9.13 VX_FP_TASK values
11
C Controller module
VX_FP_TASK value
Q12DCCPU-V
0x1000000
Q06CCPU-V(-B)
0x8
PROGRAMMING USING VxWorks API FUNCTIONS
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)>
12
taskSpawn("taskA",100,0x8,20000,funcA,0,0,0,0,0,0,0)
SAMPLE PROGRAMS
For details on the VX_FP_TASK option, refer to the following. Manuals for VxWorks
13
Remark
EVENT NUMBER LIST
1. Depending on the description in the script file, the following operation can be
performed from the CompactFlash card to the standard RAM or standard
ROM (excluding the Q06CCPU-V-B).
· Copy registration of a program to the standard RAM or standard ROM
(
Page 9-46, Section 9.8)
A
· Standard RAM and standard ROM formatting (
C Controller Module
User's Manual (Hardware Design, Function Explanation))
2. Commands described in a script file are identical with those described in the
startup script file for VxWorks. (
Manual for VxWorks)
3. The RUN LED of the C Controller module flashes while the script file
(command) is in process.
I
4. For precautions for the user program, refer to the following.
Page 9-23, "9.5 Programming Flow for Bus Interface Functions"
Page 9-26, "9.6 Precautions for Functions"
Page 10-5, "10.5 MELSEC Data Link Function Programming Flow" In the script file, describe commands used for login user setting (addition/ change) and user program task start as necessary. For login user, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation). 6. For the sample program of the script file, refer to the following.
Page 12-1, "CHAPTER 12 SAMPLE PROGRAMS"
9.9 Creating a Script File "STARTUP.CMD"
9 - 52
9 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"
· Standard ROM Root directory of standard ROM "/ROM"
· CompactFlash card Root directory of CompactFlash card "/CF"
(b) When a script file is stored into either the standard RAM or standard ROM and CompactFlash card When a script file is stored into either the standard RAM or standard ROM and CompactFlash card, the one in the CompactFlash card is started by priority. (The script file in the standard RAM or standard ROM is ignored.)
For example, the script file used for maintenance can be processed by installing the Compact Flash card with a maintenance script file stored, even when the script file in the standard RAM or standard ROM is used for system operation.
Standard RAM/standard ROM STARTUP.CMD (For system operation)
CompactFlash card STARTUP.CMD (For maintenance)
Install !
Script file of CompactFlash card is started with priority! Figure 9.17 Example of the use when script files are stored in both locations
9 - 53
9.9 Creating a Script File "STARTUP.CMD"
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
(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
10
the standard RAM from the script file in the standard RAM.
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
<Stored files>
Files in standard RAM
/RAM
"STARTUP.CMD"
/DirA "fileA.out" *1 /DirB "fileB.out" *2
11
PROGRAMMING USING VxWorks API FUNCTIONS
*1 "funcA" function already included in fileA.out *2 "funcB" function already included in fileB.out
<Task settings>
C Controller module
Startup order
Task name
1 Default: tN (N=1, 2, ...)
Priority Default: 100
2 taskB
120
Stack size (byte) Default: 20000 5000
Function name
Argument specification
funcA None
funcB Specified (First argument: 10)
File storage location /RAM/DirA/fileA.out /RAM/DirB/fileB.out
<Example of script file description >
ld (1, 0, "/RAM/DirA/fileA.out")
1)
ld (1, 0, "/RAM/DirB/fileB.out")
2)
sp (funcA, 0, 0, 0, 0, 0, 0, 0, 0, 0)
3)
taskSpawn ("taskB", 120, 0, 5000, funcB,10, 0, 0, 0, 0, 0, 0)
4)
1) The "fileA.out" file is loaded from the standard RAM "DirA" directory. 2) The "fileB.out" file is loaded from the standard RAM "DirB" directory. 3) The "funcA" function is generated under the default task name (t1). 4) The "funcB" function is generated under the task name "taskB".
Figure 9.18 Example of script file description (loaded from standard RAM)
POINT
Since the maximum number of arguments to be specified for one command is 12, up to seven arguments can be given to the function entry specified in taskSpawn (funcB in the above example). The task will not start if eight or more arguments are specified for the function entry specified in task Spawn (funcB in the above example).
EVENT NUMBER LIST
SAMPLE PROGRAMS
12 13 A I
9.9 Creating a Script File "STARTUP.CMD"
9 - 54
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
<Stored files>
(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.
File in standard RAM /RAM
/DirB "fileB.out" *2
C Controller module
File in CompactFlash card
/CF
"STARTUP.CMD"
/ DirA "fileA.out" *1
*1 "funcA" function already included in fileA.out *2 "funcB" function already included in fileB.out
<Task settings>
Startup order
Task name
1 Default: tN (N=1, 2, ...)
2 taskB
Priority Default: 100 120
Stack size (byte) Default: 20000 5000
Function name
Argument specification
funcA None
funcB Specified (First argument: 10)
File storage location /CF/DirA/fileA.out /RAM/DirB/fileB.out
<Script file description example>
ld (1, 0, "/CF/DirA/fileA.out")
1)
ld (1, 0, "/RAM/DirB/fileB.out")
2)
sp (funcA, 0, 0, 0, 0, 0, 0, 0, 0, 0)
3)
taskSpawn ("taskB", 120, 0, 5000, funcB,10, 0, 0, 0, 0, 0, 0)
4)
1) The "fileA.out" file is loaded from the CompactFlash card "DirA" directory. 2) The "fileB.out" file is loaded from the standard RAM "DirB" directory. 3) The "funcA" function is generated under the default task name (t1). 4) The "funcB" function is generated under the task name "taskB".
Figure 9.19 Example of script file description (loaded from CompactFlash card)
POINT
Since the maximum number of arguments to be specified for one command is 12, up to seven arguments can be given to the function entry specified in taskSpawn (funcB in the above example). The task will not start if eight or more arguments are specified for the function entry specified in task Spawn (funcB in the above example).
9 - 55
9.9 Creating a Script File "STARTUP.CMD"
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 9.10 Device Types for Bus Interface Functions
PROGRAMMING USING 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.
Table 9.14 Motion CPU dedicated device types
Device type
Code specification
Dec.
Hex.
Device name specification*1
Device
1
1H
QBFDev_MCPU_X Input (X)
2
2H
QBFDev_MCPU_Y Output (Y)
3
3H
QBFDev_MCPU_L
Latch relay (L)*2
4
4H
QBFDev_MCPU_M Internal relay (M)
5
5H
QBFDev_MCPU_SM Special relay (SM)*3
6
6H
QBFDev_MCPU_F Annunciator (F)
13
DH
QBFDev_MCPU_D Data register (D)
14
EH
QBFDev_MCPU_SD Special register (SD)*4
23
17H
QBFDev_MCPU_B Link relay (B)
24
18H
QBFDev_MCPU_W Link register (W)
61
3DH
QBFDev_MCPU_MR Motion register (#)
* 1 The device name specification (macro) is defined in the include file "QbfFunc.h" of the bus
interface function. (
Page 9-9, Section 9.4)
* 2 For the Q172DCPU and Q173DCPU, L (latch relay) cannot be used.
* 3 When SM (special relay) is specified in sDevType, the ulDevNo specification is as follows.
[When using the Q172DCPU or Q173DCPU]
0 to 1999 (SM2000 to SM2255 are SM compatibility areas in the Motion CPU other than the
Q172DCPU and Q173DCPU.)
[When using the Motion CPU other than the Q172DCPU and Q173DCPU]
0 and higher (corresponds to M9000 and higher areas in the Motion CPU)
* 4 When SD (special register) is specified in sDevType, the ulDevNo specification is as follows.
[When using the Q172DCPU or Q173DCPU]
0 to 1999 (SD2000 to SD2255 are SD compatibility areas in the Motion CPU other than the
Q172DCPU and Q173DCPU.)
[When using the Motion CPU other than the Q172DCPU and Q173DCPU]
0 and higher (corresponds to M9000 and higher areas in the Motion CPU)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
10 11 12 13 A I
9.10 Device Types for Bus Interface Functions
9 - 56
9 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.
(a) Internal buffer access
Table 9.15 Device types for internal buffer access
Device type
Code specification
Device name
Device
Dec.
Hex.
specification*1
1
1H
QBFDev_LXBuf
Link input internal buffer (LX buffer)
2
2H
QBFDev_LYBuf
Link output internal buffer (LY buffer)
23
17H
QBFDev_LBBuf
Link relay internal buffer (LB buffer)
24
18H
QBFDev_LWBuf
Link register internal buffer (LW buffer)
* 1 The device name specification (macro) is defined in the include file "QbfFunc.h" of the bus
interface function. (
Page 9-9, Section 9.4)
(b) Direct access
Table 9.16 Device types for internal direct access
Device type
Code specification
Dec.
Hex.
1000 2000
3E8H 7D0H
23000
59D8H
Device name specification*1
QBFDev_LX QBFDev_LY QBFDev_LB
Direct link input (LX) Direct link output (LY) Direct link relay (LB)*2
Device
24000 25000 28000
5DC0H 61A8H 6D60H
QBFDev_LW
Direct link register (LW)*2
QBFDev_LSB
Direct link special relay (SB)
QBFDev_LSW Direct link special register (SW)
* 1 The device name specification (macro) is defined in the include file "QbfFunc.h" of the bus
interface function. (
Page 9-9, Section 9.4)
* 2 Only CC-Link IE Controller Network modules can access to the areas of LB4000 and higher and
LW4000 and higher.
9 - 57
9.10 Device Types for Bus Interface Functions
9 PROGRAMMING USING BUS INTERFACE FUNCTIONS 9
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.
· QBF_WriteDevice
· QBF_ReadDevice
10
· QBF_SetDevice
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
· QBF_ResetDevice · QBF_WriteDevice_ISR
· QBF_ReadDevice_ISR
· QBF_SetDevice_ISR
· QBF_ResetDevice_ISR
11
Table 9.17 Device types for internal user or system device access
PROGRAMMING USING VxWorks API FUNCTIONS
Device type
Code specification
Dec.
Hex.
Device name specification*1
Device
4
4H
QBFDev_CCPU_M Internal relay (M)
5
5H
QBFDev_CCPU_SM Special relay (SM)
13
DH
QBFDev_CCPU_D Data register (D)
12
14
EH
QBFDev_CCPU_SD Special register (SD)
* 1 The device name specification (macro) is defined in the include file "QbfFunc.h" of the bus
interface function. (
Page 9-9, Section 9.4)
SAMPLE PROGRAMS
13
EVENT NUMBER LIST
A
I
9.10 Device Types for Bus Interface Functions
9 - 58
9 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 CC-Link IE Controller Network
MELSECNET/H
Item Link device refresh cycle Refresh parameters Link device refresh cycle Refresh parameters
Reference page Page 7-23, Section 7.5 (2) Page 7-27, Section 7.5 (4) Page 6-27, Section 6.6 (2) Page 6-33, Section 6.6 (4)
2. The link devices (SB, SW) are accessible only by direct access. The internal link device buffers cannot be used for access since the setting of the CC IE Control utility or MELSECNET/H utility (setting of link device refresh cycle and ranges) does not enable the refresh.
Remark
For the link device accessing method, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
9 - 59
9.10 Device Types for Bus Interface Functions
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
9
CHAPTER 10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
10
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.
10.1 Outline of MELSEC Data Link Functions
PROGRAMMING USING VxWorks API FUNCTIONS
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
11
To access and control a programmable controller CPU and each module in a user program, the functions provided by SW3PVC-CCPU must be used.
(1) The following indicates features of bus interface functions.
12 1) Access to the programmable controller CPU that is in the same system as the C Controller module.
SAMPLE PROGRAMS
2) Access to the programmable controller on another station via CC-Link module(s) controlled by the C Controller module.
3) Access to the programmable controller on another station via CC-Link
module(s) or MELSECNET/H module(s) controlled by the C Controller module.
13 4) Message exchange with the following modules or personal computers via CC-
Link IE Controller Network module(s) or MELSECNET/H module(s) controlled
EVENT NUMBER LIST
by the C Controller module.
· C Controller module (another station)
· Programmable controller (another station)
· Personal computer equipped with MELSECNET/H board (only via
MELSECNET/H module(s))
A
I
10.1 Outline of MELSEC Data Link Functions
10 - 1
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
The system illustration below represents a system image based on the features described on the previous page.
I/O modules Q06CCPU-V
Programmable controller CPU
Intelligent function module CC-Link module
CC-Link IE Controller Network module or
MELSECNET/H module
Programmable controller CPU
1) Motion CPU
3) to 4)
CC-Link IE Controller Network or MELSECNET/H CC-Link module Programmable controller CPU
2)
CC-Link Figure 10.1 MELSEC data link function image
10 - 2
10.1 Outline of MELSEC Data Link Functions
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Table 10.1 Access targets of MELSEC data link functions
Arrow
Access target
Programmable controller CPU C Controller module CC-Link module (own station) Programmable controller CPU (other station) Programmable controller CPU (other station in multiple CPU system) MELSECNET/H module (host station) CC-Link IE Controller Network module (own station)
Programmable controller (other station)
Programmable controller CPU (other station in multiple CPU system)
No. given above
Communication path
Setting of Device monitoring
utility
Channel name
Station
Remarks
1)
Q series bus
12: Q series bus interface
Other sta.
Q series bus
12: Q series bus interface
Own Only CPU shared memory sta. accessible
CC-Link
8n: CC-Link (Channel No.8n)*1
Own sta.
2) CC-Link
8n: CC-Link (Channel No.8n)*1
Other sta.
Station No.: 0 to 63 (access to control CPU of other station CC-Link module)
2) CC-Link
8n: CC-Link (Channel No.8n)*1
Other sta.
Station No.: 65 to 239*2 (access to CPU that does not control other station CC-Link module)
MELSECNET/H
CC-Link IE Controller Network
5n: MELSECNET/H (Channel No.5n)*3 15n: CC-Link IE Controller Network (Channel No.15n)*4
Own sta.
MELSECNET/H
3), 4)
CC-Link IE Controller Network
5n: MELSECNET/ H(Channel No.5n)*3
15n: CC-Link IE Controller Network (Channel No.15n)*4
Other sta.
Station No.: 1 to 64 (access to control CPU of other station MELSECNET/H module) Station No.: 1 to 120 (access to control CPU of other station CC-Link IE Controller Network module)
MELSECNET/H
3), 4)
CC-Link IE Controller Network
5n: MELSECNET/H (Channel No.5n)*3
15n: CC-Link IE Controller Network (Channel No.15n)*4
Other sta.
Station No.: 65 to 239*5 (access to CPU that does not control other station MELSECNET/H module) Station No.: 65 to 239*6 (access to CPU that does not control other station CC-Link IE Controller Network)
* 1 "n" indicates the last digit of the channel No. set in the CC-Link utility. * 2 The logical station No. must be set in the <<Target settings>> tab of the CC-Link utility to access
the CPU that does not control other station CC-Link module. * 3 "n" indicates the last digit of the channel No. set in the MELSECNET/H utility. * 4 "n" indicates the last digit of the channel No. set in the CC IE Control utility. * 5 The logical station No. must be set in the <<Target settings>> tab of the MELSECNET/H utility to
access the CPU that does not control the other station MELSECNET/H module. * 6 The logical station No. must be set in the <<Target settings>> tab of the CC IE Control utility to
access the CPU that does not control the other station CC-Link IE Controller Network module.
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
10.1 Outline of MELSEC Data Link Functions
10 - 3
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
10.2 MELSEC Data Link Function List
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Category Open/close Remote control CPU model read
Device access
Initialize
Table 10.2 MELSEC data link function list
Function name mdOpen
Description Opens a communication line.
1)Q12DCCPU-V 2)Q06CCPU-V
Availability
1)
2)
mdClose mdControl mdTypeRead mdSend mdSendEx mdReceive mdReceiveEx
Closes a communication line. Remote operations (RUN/STOP/PAUSE) of the programmable controller CPU. Reads the model name of the programmable controller CPU. ·Batch writes devices. ·Sends messages (SEND function) Batch writes devices. (Extended function) ·Batch reads devices. ·Receives messages. (RECV function) Batch reads devices. (Extended function)
mdDevSet
Sets bit devices.
mdDevSetEx mdDevRst mdDevRstEx
Sets bit devices. (Extended function) Resets bit devices. Resets bit devices. (Extended function)
mdRandR
Reads devices randomly.
mdRandREx
Reads devices randomly. (Extended function)
mdRandW mdRandWEx
Writes devices randomly. Writes devices randomly. (Extended function)
mdInit
Refreshes the programmable controller device address table.
: Available, : N/A
POINT
For details of the MELSEC data link functions, refer to the MELSEC data link function HELP of SW3PVC-CCPU.
10.3 Programming Procedure
Q12DCCPU-V
For details of programming procedures, refer to the following. Page 9-8, "9.3 Programming Procedure"
Q06CCPU-V
Q06CCPU-V-B
10 - 4
10.2 MELSEC Data Link Function List
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
9 10.4 Creating a New Project of User Program and Compiling
PROGRAMMING USING BUS INTERFACE FUNCTIONS
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"
10
10.5 MELSEC Data Link Function Programming Flow
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Programming flow
The following flowchart shows the procedure for programming using the MELSEC data link functions.
Task start
Opens a communication line. (mdOpen function)
Makes dummy access (reading a device, a model name, etc.) to each access target.
11) 33)
22)
Using a MELSEC data link function, accesses the target (Programmable controller CPU, CC-Link IE Controller Network module, MELSECNET/H module, CC-Link module, etc.).
4
4), 5)
PROGRAMMING USING VxWorks API FUNCTIONS
SAMPLE PROGRAMS
11 12 13
EVENT NUMBER LIST
No Terminate the program (task)?
A
Yes
Closes the communication line. (mdClose function)
11)
Task end
I
For details of precautions for each process, refer to the following. Page 10-6, "10.5 (2) (a) Precautions for programming" Figure 10.2 Programming using MELSEC data link functions
10.4 Creating a New Project of User Program and Compiling
10 - 5
10 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 ( 1 )
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. Repeating opening and closing for every communication degrades communication performance.
2) Execution time for initial execution ( 2 )
When a device is added, the function collects information of the programmable controller in detail at first execution, which increases the execution time. To avoid the increase, make dummy access to each target in advance.
3) MELSEC data link function execution in multiple tasks ( 3 )
The MELSEC data link functions cannot be simultaneously processed in multiple tasks within the C Controller module. When processing by the MELSEC data link function are requested simultaneously in multiple tasks, one of the tasks starts its processing and the other tasks will be in waiting status since the processing is performed one at a time.
Create a program that completes all preparatory processing ( 3 ) first and then execute the main processing( 4 ).
4) Accessing to other station ( 4 )
When accessing other station from the C Controller module via any of the following, one of the communication processing starts and the others will be in the waiting status.
· Q series bus interface · CC-Link IE Controller Network module · MELSECNET/H module · CC-Link module Note that if one communication processing times out, the other communication processing may time out.
10 - 6
10.5 MELSEC Data Link Function Programming Flow
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 9
PROGRAMMING USING BUS INTERFACE 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.
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
1) Access to own station device Create a user program that provides interlocks to enable write to/read from the
10
own station device.
Data take effect only when the following conditions are satisfied.
· Module error (Xn0) is off (normal)
· Own station link status (Xn1) is off (in data link)
· Module ready (XnF) is on (operable) Write to/read from the own station is terminated normally irrespective of the
11
above conditions.
PROGRAMMING USING VxWorks API FUNCTIONS
2) Transient access to other stations (other station programmable controller CPU
remote operation and device access)
Create a user program that allows to access under the following conditions, in
addition to the interlocks for own station device access. · Data link status of the access target station (Bits corresponding to a
12
communication target station of SW80 to 83, which are read from the own
station) is off (normal communication).
SAMPLE PROGRAMS
(c) Precautions for access to MELSECNET/H module host station devices and other
station programmable controller devices
When accessing via MELSECNET/H module, provide interlocks according to the
13
link status of the host station.
EVENT NUMBER LIST
1) Access to host station device Create a user program that provides interlocks to enable write to/read from the host station devices. Data take effect only when the following conditions are satisfied.
· Module status (SB20) is off (normal)
A
· Baton pass status of the host station (SB47) is off (normal)
· Data link status of the host station (SB49) is off (in data link)
Write to/read from the host station is terminated normally irrespective of the above conditions.
2) Transient access to other stations (other station programmable controller CPU
remote operation and device access)
I
Create a user program that makes access when any of the following conditions
is satisfied, in addition to the interlocks for the host station device access.
· Baton pass status of the access target station (Bits corresponding to a communication target station of SW70 to 73, which are read from the host station) is off (normal communication).
· Data link status (Bits corresponding to the communication target station of SW74 to 77, which are read from the host station) is off (normal communication).
10.5 MELSEC Data Link Function Programming Flow
10 - 7
10 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. Data take effect only when the following conditions are satisfied. · Data link status of own station (SB49) is off (in data link) · Data link status (Bits corresponding to the communication target station of SWB0 to B7, which are read from the own station) is off (normal communication). Write to/read from the own station is terminated normally irrespective of the above conditions.
2) Transient access to other stations (other station programmable controller CPU remote operation and device access) Create a user program that allows to access under the following conditions, in addition to the interlocks for own station device access. · Baton pass status of own station (SB47) is off (normal) · Baton pass status of the access target station (Bits corresponding to the communication target station of SWA0 to A7, which are read from the own station) is off (normal communication)
(e) Other precautions
1) Time out value setting for MELSEC data link function
When either of the following problems occur, change the communication
timeout value for the MELSEC data link function in C Controller setting utility.
(
Page 4-28, Section 4.6 (3) (c))
· Frequent communication timeouts due to line congestion. Increase the timeout value
· To allow communication timeout at shorter timing Decrease the timeout value
When the above problems do not occur, operate by default setting.
Figure 10.3 MD function communication timeout value setting screen
10 - 8
10.5 MELSEC Data Link Function Programming Flow
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
9 10.6 Precautions for the MELSEC Data Link Function
PROGRAMMING USING BUS INTERFACE FUNCTIONS
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
10.7 Precautions for Program Debugging
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING VxWorks API FUNCTIONS
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
For details of precautions for program debugging, refer to the following.
11
Page 9-31, "9.7 Precautions for Program Debugging"
10.8 Program Registration
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
12
For details of program registration, refer to the following. Page 9-46, "9.8 Program Registration"
SAMPLE PROGRAMS
10.9 Creating a Script File "STARTUP.CMD"
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
13
For details of creating a script file "STARTUP.CMD", refer to the following. Page 9-51, "9.9 Creating a Script File "STARTUP.CMD""
EVENT NUMBER LIST
10.10 Channel
A
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
Table 10.3 Channels used for MELSEC data link functions
No. 12
51 to 54
Channel name Q series bus interface
MELSECNET/H (Channel No.51 to 54)
Description
Used when communication is performed via a bus. Used when communication is performed via a MELSECNET/H module controlled by the C
I
Controller module.
Channel No. is set for each target module in the <<Parameter settings>> tab of
MELSECNET/H utility. (
Page 6-27, Section 6.6)
81 to 88
CC-Link (Channel No.81 to 88)
Used when communication is performed via CC-Link module controlled by the C
Controller module.
Channel No. is set for each target module in the <<Parameter settings>> tab of CC-Link
utility. (
Page 5-11, Section 5.5)
151 to 154
CC-Link IE Controller Network (Channel No.151 to 154)
Used when communication is performed via CC-Link IE Controller Network module
controlled by the C Controller module.
Channel No. is set for each target module in the <<Parameter settings>> tab of CC IE
Control utility. (
Page 7-23, Section 7.5)
10.6 Precautions for the MELSEC Data Link Function
10 - 9
10 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
Communication Q series bus interface CC-Link IE Controller Network MELSECNET/H
CC-Link
Table 10.4 Functions other than extended functions
Station No. specification
Own station: 255 (FFH)*1 Other station: 1 (CPU No.1), 2 (CPU No.2), 3 (CPU No.3), 4 (CPU No.4) Own station: 255 (FFH)
Other station:
Page 10-10, Section 10.11 (1) (a)
Host station: 255 (FFH)
Other station:
Page 10-10, Section 10.11 (1) (a)
Own station: 255 (FFH) Other station: 0 (0H) to 63 (3FH), 65 (41H) to 239 (EFH)
Page 10-11, Section 10.11 (1) (b)
* 1 Transmission to the C Controller module (own station) using a MELSEC data link function may take a longer time than the one using a bus interface function. Use bus interface functions when creating a user program for which performance quality is required (such as a control program).
(a) Station No. setting for CC-Link IE Controller Network module (other station) and MELSECNET/H (other station)
Network No. 1(1H) to 239(EFH): When specifying the other station in the local network or a station in other network (When making a send request to CC-Link IE Controller Network, MELSECNET/H or MELSECNET/10)
Upper Lower
Station No., group No. or all stations 1(1H) to 120(78H) : Other stations
129(81H) to 160(A0H): Group No.1 to 32
Group No.1 to 9 (129(81H) to 137(89H)) are used in the MELSECNET/10 mode when the target CPU is the QnACPU.
240(F0H)
: All stations (Available only when the SEND function (mdSend) is used.)
<Logical station No. setting method> Set "0" in the upper byte (network No.) and a logical station No. in the lower byte (station No.).
<Setting range of logical station No.>
Set it in the target settings of the MELSECNET/H utility, CC IE Control utility.
65 (41H) to 239 (EFH): MELSECNET/H communication
65 (41H) to 239 (EFH): CC-Link IE Controller Network communication
(
Page 6-39, Section 6.7, Page 7-34, Section 7.6)
Figure 10.4 Station No. setting for CC-Link IE Controller Network module and MELSECNET/H module
10 - 10
10.11 Station No. Setting for MELSEC Data Link Functions
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
Upper Lower
(b) Station No. setting for CC-Link module (other station)
Network No.
0: CC-Link
<Logical station No. setting method> Set "0" in the upper byte (network No.) and a logical station No. in
Station No.
the lower byte (station No.).
0(0H) to 63(3FH) : Other station <The setting range of logical station No.> Set it in the target settings of the CC-Link utility.
65 (41H) to 239 (EFH): CC-Link communication
(
Page 5-15, Section 5.6 )
Figure 10.5 Station No. setting for CC-Link module
Station No. 64 cannot be specified for the CC-Link (other station). When the own station No. is 64, the other station cannot be specified. (Access is allowed only to the own station.) Specify the station No. other than 64.
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
10 11
PROGRAMMING USING VxWorks API FUNCTIONS
(2) Extended functions
Table 10.5 Extended function
Communication
Network No. specification
Station No. specification
Q series bus interface
0(0H)
Own station: 255(FFH)*4 Other station: 1 (CPU No.1), 2 (CPU No.2),
3 (CPU No.3), 4 (CPU No.4)
Own (host) station: 0(0H) CC-Link IE Controller Network, or MELSECNET/H Other station: 1(1H) to 239(EFH)
Own (Host) station: 255(FFH) Other station: 1(1H) to 120(78H)*1
Logical station: 0(0H)
Logical station: 65(41H) to 239(EFH)*2
Own station: 255(FFH)
CC-Link
0(0H)
Other station: 0(0H) to 63(3FH)*3
Logical station: 65(41H) to 239(EFH)*2
* 1 65(41H) to 120(78H) can be specified for other station on a CC-Link IE Controller Network.
* 2 Logical station No. is set in the <<Target settings>> tab of CC IE Control utility (
Page 7-34),
MELSECNET/H utility (
Page 6-39), or CC-Link utility (
Page 5-15).
* 3 For CC-Link (other station), station No. 64 cannot be specified.
When the own station No. is 64, other station cannot be specified. (Access is allowed only to the
own station.)
Specify the station No. other than 64.
* 4 Transmission to the C Controller module (own station) using a MELSEC data link function may take
a longer time than the one using a bus interface function.
Use bus interface functions when creating a user program for which performance quality is
required (such as a control program).
EVENT NUMBER LIST
SAMPLE PROGRAMS
12 13 A
I
10.11 Station No. Setting for MELSEC Data Link Functions
10 - 11
10 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
DEC. 1 2 3 4
Code
Device type
HEX. 1H 2H 3H 4H
5
5H
6
6H
7
7H
8
8H
9
9H
10
AH
11
BH
12
CH
13
DH
14
EH
15 16 16002 16003 17 18 18002 18003 19 20 21 22
220
FH 10H 3E82H 3E83H 11H 12H 4652H 4653H 13H 14H 15H 16H
00DCH
22000 to 22256 55F0H to 56F0H
23
17H
24
18H
25
19H
26
1AH
27
1BH
Device name*1
Device
DevX
X
DevY
Y
DevL
L
DevM
M
DevSM
SM(special relay), SB(link special relay for MELSECNET/H, CC-Link IE Controller Network, and CC-Link)
DevF
F
DevTT
T (contact)
DevTC
T (coil)
DevCT
C (contact)
DevCC
C (coil)
DevTN
T (current value)
DevCN
C (current value)
DevD
D
DevSD
SD (special register), SW(link special register for MELSECNET/H, CC-Link IE Controller Network, and CC-Link)
DevTM
T (main setting)
DevTS
T (sub setting 1)
DevTS2
T (sub setting 2)
DevTS3
T (sub setting 3)
DevCM
C (main setting)
DevCS
C (sub setting 1)
DevCS2
C (sub setting 2)
DevCS3
C (sub setting 3)
DevA
A
DevZ
Z*2
DevV
V (index register)
DevR
R (file register)*2
DevZR
ZR (file register)*2
DevER(0) to DevER(256)
ER (extended file register) Argument value of device name (0 to 256*2) is Block No.
DevB
B
DevW
W
DevQSB
Q/QnA link special relay (within Q/QnACPU)
DevSTT
Retentive timer (contact)
DevSTC
Retentive timer (coil)
* 1 The device name specification (macro) is defined in this function's include file "MdFunc.h". (
Page 9-9, Section 9.4) * 2 Even if a non-existing device is specified in mdRandR or mdRandREx functions, they complete
normally. (The read data is "-1".)
(To the next page)
10 - 12
10.12 Device Types for the MELSEC Data Link Function
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Table 10.6 Common device types of MELSEC data link functions (continued)
DEC. 28 30 35 101 102
Code
Device type
HEX. 1CH 1EH 23H 65H 66H
1001 to 1255 3E9H to 4E7H
2001 to 2255 7D1H to 8CFH
23001 to 23255 24001 to 24255
59D9H to 5AD7H
5DC1H to 5EBFH
25001 to 25255 61A9H to 62A7H
28001 to 28255 6D61H to 6E5FH
29000 to 29255 7148H to 7247H
31000 to 31255 7918H to 7A17H
32000 to 32255
7D00H to 7DFFH
Device name*1
Device
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
Q/QnA SEND function (no arrival confirmation)
DevLX(1) to
Direct link input (other station side)
DevLX(255)
Argument value of device name (1 to 255*2) is Network No.
DevLY(1) to DevLY(255)
Direct link output (other station side) Argument value of device name (1 to 255*2) is Network No.
DevLB(1) to DevLB(255)
Direct link relay (other station side) Argument value of device name (1 to 255*2) is Network No.
DevLW(1) to
Direct link register (other station side)
DevLW(255)
Argument value of device name (1 to 255*2) is Network No.
DevLSB(1) to DevLSB(255)
Direct link special relay (other station side) Argument value of device name (1 to 255*2) is Network No.
DevLSW(1) to DevLSW(255)
Direct link special register (other station side) Argument value of device name (1 to 255*2) is Network No.
DevSPG(0) to DevSPG(255)
Special direct buffer register, Intelligent function module buffer memory Argument value of device name (1 to 255*2) is start I/O No. divided by 16
DevEM(0) to
EM (shared device)*3
DevEM(255)
Argument value of device name (0 to 255*2) is Block No.
DevED(0) to
ED (shared device)*3
DevED(255)
Argument value of device name (0 to 255*2) is Block No.
* 1 The device name specification (macro) is defined in this function's include file "MdFunc.h". (
Page 9-9, Section 9.4) * 2 Even if a non-existing device is specified in mdRandR or mdRandREx functions, they complete
normally. (The read data is "-1".) * 3 Available for accessing other station's personal computers. (Only when the communication target
is on Microsoft R Windows NT R Workstation 4.0 where MX Links (SW2D5F-CSKP or later) is running).
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A
I
10.12 Device Types for the MELSEC Data Link Function
10 - 13
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(2) Dedicated device types for Q series bus interface
DEC. 501 502 503 504
Table 10.7 Q series bus interface dedicated device types
Code
Device types HEX.
Device name*1
Device
1F5H
DevSPB1
CPU shared memory (area for CPU No.1)*2
1F6H 1F7H
DevSPB2 DevSPB3
CPU shared memory (area for CPU No.2)*2 CPU shared memory (area for CPU No.3)*2
1F8H
DevSPB4
CPU shared memory (area for CPU No.4)*2
* 1 The device name specification (macro) is defined in this function's include file "MdFunc.h". (
Page 9-9, Section 9.4)
* 2 The device cannot be used in the mdRandR, mdRandREx, mdRandW, mdRandWEx, mdDevSet, mdDevSetEx, mdDevRst, or mdDevRstEx function.
(3) Device types for accessing the CC-Link modules
DEC. 1 2 5 14 25 28 33 36 37 50
-32768 -32736
Code
Table 10.8 Device types for accessing CC-Link module
Device type HEX.
Device name*1
Device
1H
DevX
Own station RX*5
2H
DevY
Own station RY*5
5H
DevSM
Own station SB (link special relay for CC-Link)*3
EH
DevSD
Own station SW (link special register for CC-Link)*4
19H
DevQSB
Own station SB (link special relay for CC-Link)*3
1CH
DevQSW
Own station SW (link special register for CC-Link)*4
21H
DevMRB
Own station random access buffer
24H
DevWw
Own station link register (for sending)*5
25H
DevWr
Own station link register (for receiving)*5
32H
DevSPB
Own station buffer memory*5
8000H 8020H
DevRBM
Other station buffer memory*2
DevRAB
Other station random access buffer*2
* 1 The device name specification (macro) is defined in this function's include file "MdFunc.h". (
Page 9-9, Section 9.4) * 2 The device cannot be used in the mdRandR, mdRandREx, mdRandW, mdRandWEx, mdDevSet,
mdDevSetEx, mdDevRst, or mdDevRstEx functions. * 3 These (DevSM, DevQSB) are the same device. * 4 These (DevSD, DevQSW) are the same device. * 5 Note that maximum of one scan time may delay when the block data assurance per station
function is enabled and the link device is continuously accessed (mdSend, mdSendEx(1), mdReceive(1), mdReceiveEx, mdDevSet, mdDevSetEx, mdDevRst, mdDevRstEx). (This is the same behavior when the auto refresh method is selected as CC-Link refreshing method in the QBF_ToBuf and QBF_FromBuf functions.) Moreover, block data assurance per station cannot be used in dReadR, mdRandREx, mdReadW, and mdRandWEx functions. For details, refer to the following. For block data assurance per station, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation). For the MELSEC data link functions, refer to the HELP of the MELSEC data link function.
(To the next page)
10 - 14
10.12 Device Types for the MELSEC Data Link Function
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
DEC. -32735 -32734 -32732 -32669 -32668
Code
Table 10.8 Device types for accessing CC-Link module (continued)
Device type
HEX. 8021H 8022H 8024H 8063H 8064H
Device name*1
DevRX DevRY DevRW DevSB DevSW
Device
Other station RX Other station RY Other station link register*2 Other station SB (link special relay for CC-Link) Other station SW (link special register for CC-Link)*2
* 1 The device name specification (macro) is defined in this function's include file, "MdFunc.h". ( Page 9-9, Section 9.4)
* 2 The device cannot be used in the mdRandR, mdRandREx, mdRandW, mdRandWEx, mdDevSet, mdDevSetEx, mdDevRst, or mdDevRstEx functions.
(4) Device types for accessing CC-Link IE Controller Network modules or MELSECNET/H modules
In a user program, link device access methods and message send/receive can be selected by specifying a device.
(a) Internal buffer access
DEC. 1 2 23 24
Code
Table 10.9 Device types for internal buffer access
Device Type
HEX. 1H 2H 17H 18H
Device name*1
Device
DevX
Own station link input internal buffer (LX buffer)
DevY
Own station link output internal buffer (LY buffer)
DevB
Own station link relay internal buffer (LB buffer)
DevW
Own station link register internal buffer (LW buffer)
* 1 The device name specification (macro) is defined in this function's include file, "MdFunc.h". (
Page 9-9, Section 9.4)
(b) Direct access
DEC. 5 14 25 28
1000 2000 23000 24000 25000 28000
Code
Table 10.10 Device types for direct access
Device Type
HEX.
Device name*1
Device
5H
DevSM
Own station direct link special relay (SB)*2
EH
DevSD
Own station direct link special register (SW)*3
19H
DevQSB
Own station direct link relay (SB)*2
1CH 3E8H 7D0H 59D8H
DevQSW DevLX(0) DevLY(0) DevLB(0)
Own station direct link register (SW)*3 Own station direct link input (LX) Own station direct link output (LY) Own station direct link relay (LB)*4
5DC0H
DevLW(0)
Own station direct link register (LW)*4
61A8H
DevLSB(0)
Own station direct link special relay (SB)*2
6D60H
DevLSW(0)
Own station direct link special register (SW)*3
* 1 The device name specification (macro) is defined in this function's include file, "MdFunc.h". (
Page 9-9, Section 9.4) * 2 These (DevSM, DevQSB, and DevLSB(0)) are the same device.
* 3 These (DevSD, DevQSW, and DevLSW(0)) are the same device. * 4 Only for CC-Link IE Controller Network modules, access can be made to areas of LB4000 and
higher and LW4000 and higher.
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
10.12 Device Types for the MELSEC Data Link Function
10 - 15
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(c) Message send/receive
DEC. 101 102
Code
Table 10.11 Device types for message send receive
Device type
HEX. 65H 66H
Device name*1
Device
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 9-9, Section 9.4)
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 10.12 Setting link device refresh cycle and ranges
Network CC-Link IE Controller Network
MELSECNET/H
Item Link device refresh cycle Refresh parameters Link device refresh cycle Refresh parameters
Reference page Page 7-23, Section 7.5 (2) Page 7-27, Section 7.5 (4) Page 6-27, Section 6.6 (2) Page 6-33, Section 6.6 (4)
2. The link devices (SB and SW) are accessible only by direct access. Access by using internal link device buffers cannot be made since the settings (link device refresh cycle and ranges) of the CC IE Control utility and MELSECNET/H utility cannot perform link device refresh.
Remark
For the link device accessing method, refer to the C Controller Module User's Manual (Hardware Design, Function Explanation).
10 - 16
10.12 Device Types for the MELSEC Data Link Function
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
9 10.13 Accessible Ranges and Devices of the MELSEC Data Link
Function
PROGRAMMING USING BUS INTERFACE FUNCTIONS
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 Bus CC-Link MELSECNET/H CC-Link IE Controller Network
Reference page Page 10-17 Page 10-23 Page 10-29 Page 10-38
10.13.1 Access via a bus
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
10 11
PROGRAMMING USING VxWorks API FUNCTIONS
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
SAMPLE PROGRAMS
12
(1) Accessible range
Via a bus connection, access to the following is allowed. · Own station (Own station (C Controller module)) · Other station (Programmable controller CPU or C Controller module)
Other CPU (programmable controller CPU
or C Controller module)
Own CPU (own station (C Controller module))
13
CPU CPU CPU No.1 No.2 No.3
EVENT NUMBER LIST
A
Figure 10.6 Range accessible via a bus
(2) Accessible devices
(a) How to read the table
I
1) Batch and random of devices
Item in the table Batch
Random
Table 10.14 Batch and random
Description ·Batch write (mdSend, mdSendEx functions) ·Batch read (mdReceive, mdReceiveEx functions) ·Random write (mdRandW, mdRandWEx functions) ·Random read (mdRandR, mdRandREx functions) ·Bit set (mdDevSet, mdDevSetEx functions) Only bit devices can access. ·Bit reset (mdDevRst, mdDevRstEx functions) Only bit devices can access.
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.1 Access via a bus
10 - 17
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Device X Y M*2 SM (special relay), SB D*2 SD (special register), SW Special direct buffer register, Intelligent function module buffer memory
CPU shared memory*4,*5
(b) Accessible device range for accessing own CPU
Table 10.15 Accessible devices for accessing own CPU
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Device type (Device name specification)
DevX DevY DevM DevSM DevD DevSD
Access target Own station (C Controller module)
*1 *1 *1, *3 *1 *1, *3 *1
Batch
DevSPG(0) to DevSPG(255)
*1
Random
Batch Random
DevSPB1 (for CPU No.1), DevSPB2 (for CPU No.2), DevSPB3 (for CPU No.3), DevSPB4 (for CPU No.4)
: 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 (8000H)or higher, use an extended function. ( 10-4, Section 10.2)
Page
* 3 Available only when the device function is used. (
Page 4-35, Section 4.8)
* 4 The CPU shared memory is accessible only when multiple CPU setting has been done.
(
Page 4-41, Section 4.10)
* 5 Specify the device No.10000 (2710H) or later for accessing to the Multiple CPU high speed
transmission area.
10 - 18
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.1 Access via a bus
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(c) Accessible device range for accessing other CPU
Device
X
Y
L
M*2 SM (special relay), SB (link special relay for MELSECNET/ H, CC-Link IE Controller Network and CC-Link) F
T (contact)
T (coil)
C (contact)
C (coil)
T (current value)
C (current value)
D*2 SD (special register), SW (link special register for MELSECNET/H, CC-Link IE Controller Network and CCLink)
Table 10.16 Accessible devices for accessing other CPU
Batch Random
Batch Random
Batch Random
Batch Random
Device type (Device name specification)
DevX
Access target
Programmable controller
C Controller
CPU
module
*1
DevY
*1
DevL
DevM
*3
*1,*4
Batch
DevSM
*1,*4
Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch
DevF DevTT DevTC DevCT DevCC DevTN DevCN DevD
*5
*1,*4
DevSD
*1,*4
Random
: 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 (8000H)or higher, use an extended function. (
Page
10-4, Section 10.2)
* 3 The following C Controller module cannot access the internal relay (M) of device No.32768 (8000H)
or higher.
· Q06CCPU-V
* 4 Available only when the device function is used. (
Page 4-35, Section 4.8)
* 5 The following C Controller module cannot access the extended data register (D).
· Q06CCPU-V with serial number (first five digits) "10011" or earlier
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.1 Access via a bus
10 - 19
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Table 10.16 Accessible devices for accessing other CPU (continued)
Device
T (main setting) T (sub setting 1) T (sub setting 2) T (sub setting 3) C (main setting) C (sub setting 1) C (sub setting 2) C (sub setting 3) A Z V (index register) R (file register) ZR (file register)*2 ER (extended file register) B*2 W*2
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Device type (Device name specification)
DevTM DevTS DevTS2 DevTS3 DevCM DevCS DevCS2 DevCS3 DevA DevZ DevV DevR DevZR DevER(0) to DevER(256) DevB DevW
Access target
Programmable controller CPU
C Controller module
*6
*7
*9,*10
*8
*9
Q/QnA link special relay (within Q/QnACPU)
Batch Random
DevQSB
: Accessible : Inaccessible
* 2 When accessing to the device of No.32768 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
* 6 For the access, use ZR (file register) or ER (extended file register).
* 7 The following C Controller module cannot access the link relay (B) of device No.32768 (8000H) or
higher.
· Q06CCPU-V
* 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 BFFFFH or later cannot be accessed.
(To the next page)
10 - 20
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.1 Access via a bus
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Table 10.16 Accessible devices for accessing other CPU (continued)
Device Retentive timer (contact) Retentive timer (coil)
Batch Random
Batch Random
Device type (Device name specification)
DevSTT
DevSTC
Access target
Programmable controller CPU
C Controller module
Q/QnA link special register (within Q/QnACPU) Q/QnA edge relay (within Q/ QnACPU) Own station random access buffer
Retentive timer (current value)
Own station link register (for sending) Own station link register (for receiving)
Own station buffer memory
Direct link input (other station side) Direct link output (other station side) Direct link relay (other station side) Direct link register (other station side)*2 Direct link special relay (other station side) Direct link special register (other station side) Special direct buffer register, Intellligent function module buffer memory
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch
Random
DevQSW DevQV DevMRB DevSTN DevWw DevWr DevSPB DevLX(1) to DevLX(255) DevLY(1) to DevLY(255) DevLB(1) to DevLB(255) DevLW(1) to DevLW(255) DevLSB(1) to DevLSB(255) DevLSW(1) to DevLSW(255)
DevSPG(0) to DevSPG(255)
*1 *1 *1 *1 *1 *1
*1
: 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 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.1 Access via a bus
10 - 21
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Device
Other station buffer memory Other station random access buffer Other station RX
Other station RY
Other station link register Other station SB (link special relay for CC-Link) Other station SW (link special relay for CC-Link)
CPU shared memory*6,*7
Table 10.16 Accessible devices for accessing other CPU (continued)
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch
Random
Device type (Device name specification)
DevRBM
Access target
Programmable controller CPU
C Controller module
DevRAB
DevRX
DevRY
DevRW
DevSB
DevSW
DevSPB1 (for CPU No.1), DevSPB2 (for CPU No.2), DevSPB3 (for CPU No.3), DevSPB4 (for CPU No.4)
: Accessible : Inaccessible
* 6 The CPU shared memory is accessible only when multiple CPU setting has been done. (
Page 4-41, Section 4.10) * 7 Specify the device number 10000 (2710H) or and higher for accessing to the multiple CPU high
speed transmission area.
10 - 22
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.1 Access via a bus
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
9
10.13.2 Access via CC-Link
PROGRAMMING USING BUS INTERFACE FUNCTIONS
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
(1) Accessible range
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
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
· C Controller module
· PC CPU module
· Intelligent device station of CC-Link · Personal computer with the CC-Link board is installed
11
Own station (master or local station controlled by C Controller module)
Other station programmable controller CPU, C Controller module, PC CPU module (master or local station)
PROGRAMMING USING VxWorks API FUNCTIONS
12
SAMPLE PROGRAMS
CC-Link board (personal computer)
Intelligent device station
13
EVENT NUMBER LIST
Figure 10.7 Accessible range for access via CC-Link
POINT
When the own station is station No.64, access to another station is not allowed. Access is allowed only to the own station.
A
I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.2 Access via CC-Link
10 - 23
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(2) Accessible devices
(a) How to read the table 1) Batch and random of devices
Item in the table Batch
Random
Table 10.17 Batch and random of devices
Description ·Batch write (mdSend, mdSendEx functions) ·Batch read (mdReceive, mdReceiveEx functions) ·Random write (mdRandW, mdRandWEx functions) ·Random read (mdRandR, mdRandREx functions) ·Bit set (mdDevSet, mdDevSetEx functions) Only bit devices can access. ·Bit reset (mdDevRst, mdDevRstEx functions) Only bit devices can access.
2) Access targets for accessing other station
Table 10.18 Access targets for accessing other station
No.
Access target
1) A1NCPU
2) A0J2HCPU, A1S(H)CPU, A1SJ(H)CPU, A2NCPU(-S1), A2S(H)CPU
3)
A2ACPU(-S1), A2UCPU(-S1), A2USCPU(-S1), A2USHCPU-S1 Q02(H)CPU-A, Q06HCPU-A
4) A3NCPU, A3ACPU, A3UCPU
5) A4UCPU
Q2ACPU(-S1), Q3ACPU, Q4ACPU, Q4ARCPU, Q2ASCPU(-S1), Q2ASHCPU(-S1)
Q00JCPU, Q00CPU, Q01CPU
Q02(H)CPU, Q06HCPU, Q12HCPU, Q25HCPU
Q02PHCPU, Q06PHCPU, Q12PHCPU, Q25PHCPU
6) Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU,
Q10UDHCPU, Q13UDHCPU, Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU,
Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU,
Q50UDEHCPU, Q100UDEHCPU, Q03UDVCPU, Q04UDVCPU, Q06UDVCPU, Q13UDVCPU,
Q26UDVCPU
C Controller module that controls a CC-Link module,
7)
PC CPU module that controls a CC-Link module, Personal computer with a CC-Link board,
Intelligent device station on CC-Link
8) L02CPU, L26CPU-BT
10 - 24
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.2 Access via CC-Link
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Device
Own station RX
Own station RY
Own station SB (link special relay for CC-Link) Own station SW (link special register for CC-Link) Own station link register (for sending) Own station link register (for receiving)
Own station buffer memory
Own station random access buffer
(b) Accessible devices for accessing own station
Table 10.19 Accessible devices for accessing own station
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Device type (Device name specification)
DevX DevY DevSM DevSD DevWw DevWr DevSPB DevMRB
Accessibility
: Accessible : Inaccessible
Device
X Y L M*3,*4 SM (special relay), SB (link special relay for MELSEC/H, CC-Link IE Controller Network, and CC-Link)
F T (contact) T (coil)
(c) Accessible devices for accessing other station
Table 10.20 Accessible devices for accessing other station
Device type (Device name specification)
Access target
1)
2)
3)
4)
5)
6)
Batch Random
Batch Random
Batch Random
Batch Random
DevX DevY DevL DevM
7)
8)*1
*2
*2
*2,*5
Batch
DevSM
*2,*5
Random
Batch Random
Batch Random
Batch Random
DevF DevTT DevTC
: Accessible : Inaccessible
* 1 The following C Controller module is not accessible.
· 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 (8000H) or higher, use an extended function. (
Page 10-4, Section 10.2)
* 4 The following C Controller module cannot access the internal relay (M) of device No.32768 (8000H) or higher.
· Q06CCPU-V
* 5 Available only when the device function is used. (
Page 4-35, Section 4.8)
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.2 Access via CC-Link
10 - 25
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Table 10.20 Accessible devices for accessing other station (continued)
C (contact) C (coil) T (current value) C (current value) D*3,*6
Device
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Device type (Device name specification)
DevCT DevCC DevTN DevCN DevD
Access target 1) 2) 3) 4) 5) 6)
7)
8)*1
*2,*5
SD (special register), SW (link special
Batch
register for MELSECNET/H and CC-
DevSD
*2,*5
Link)
Random
T (main setting)
Batch Random
DevTM
Batch
*7
T (sub setting 1)
DevTS
Random
T (sub setting 2)
Batch Random
DevTS2
T (sub setting 3)
Batch Random
DevTS3
C (main setting)
Batch Random
DevCM
Batch
*7
C (sub setting 1)
DevCS
Random
C (sub setting 2)
Batch Random
DevCS2
C (sub setting 3) A Z
Batch Random
DevCS3
Batch Random
DevA
Batch Random
DevZ
: Accessible : Inaccessible
* 1 The following C Controller module is not accessible. · 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 (8000H) or higher, use an extended function. (
Page 10-4, Section 10.2)
* 5 Available only when the device function is used. (
Page 4-35, Section 4.8)
* 6 The following C Controller module cannot access the extended data register (D). · Q06CCPU-V with serial number (first five digits) "10011" or earlier
* 7 Access is not allowed for the A2ACPU(-S1).
(To the next page)
10 - 26
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.2 Access via CC-Link
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Device
V (index register)
R (file register)
ZR (file register)*3
ER (extended file register)
B*3,*10
W*3,*11 Q/QnA link special relay (within Q/QnACPU) Retentive timer (contact)
Retentive timer (coil) Q/QnA link special register (within Q/QnACPU) Q/QnA edge relay (within Q/ QnACPU) Own station random access buffer Retentive timer (current value) Own station link register (for sending) Own station link register (for receiving) Own station buffer memory Q/QnA SEND function (with arrival confirmation) Q/QnA SEND function (no arrival confirmation)
Table 10.20 Accessible devices for accessing other station (continued)
Batch Random
Batch Random
Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random
Device type (Device name specification)
DevV DevR DevZR DevER(0) to DevER(256) DevB DevW DevQSB DevSTT DevSTC DevQSW DevQV DevMRB DevSTN DevWw DevWr DevSPB DevMAIL DevMAILNC
Access target
1)
2)
3)
4)
5)
6)
7)
8)*1
*8 *9 *9
*12,*13 *12
: Accessible : Inaccessible
* 1 The following C Controller module is not accessible. · Q06CCPU-V with serial number (first five digits) "10101" or earlier
* 3 When accessing to the device of number 32768 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
* 8 For the access, use ZR (file register) or ER (extended file register).
* 9 Access is not allowed for the Q00JCPU.
* 10 The following C Controller module cannot access the link relay (B) of device No.32768 (8000H) or
higher.
· Q06CCPU-V
* 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 BFFFFH or later cannot be accessed.
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.2 Access via CC-Link
10 - 27
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Device
Direct link input (Other station side) Direct link output (Other station side) Direct link relay (Other station side) Direct link register (Other station side)*3 Direct link special relay (Other station side)
Direct link special register (Other station side) Special direct buffer register, Intelligent function module buffer memory
Other station buffer memory*14
Other station random access buffer*14
Other station RX*14
Other station RY*14
Other station link register*14
Other station SB (Link special relay for CC-Link) *14 Other station SW (Link special register for CC-Link)*14
Table 10.20 Accessible devices for accessing other station (continued)
Batch Random
Batch Random
Batch Random
Batch Random
Batch
Random
Device type (Device name specification)
DevLX(1) to DevLX(255) DevLY(1) to DevLY(255) DevLB(1) to DevLB(255) DevLW(1) to DevLW(255)
DevLSB(1) to DevLSB(255)
Access target
1)
2)
3)
4)
5)
6)
Batch Random
Batch
Random
DevLSW(1) to DevLSW(255) DevSPG(0) to DevSPG(255)
7)
8)*1
*2
*2
*2
*2
*2
*2
*2
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
DevRBM DevRAB DevRX DevRY DevRW DevSB DevSW
: Accessible : Inaccessible
* 1 The following C Controller module is not accessible.
· 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 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
* 14 Indicates the access to the buffer memory of a CC-Link module (intelligent device station) installed
with each CPU module.
Access is not allowed to multiple CPU systems (when the logical station number is specified).
10 - 28
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.2 Access via CC-Link
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
9
10.13.3 Access via MELSECNET/H
PROGRAMMING USING BUS INTERFACE FUNCTIONS
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.
C Controller module
1 Connected network
2 Connected Connected Relayed station CPU module module
3 Relayed network
4 Target Destination CPU module Figure 10.8 Accessible range via MELSECNET/H
The numbers in the [4.Target CPU] column indicate the modules or boards for personal computer as in the table below.
Table 10.21 Routing target CPU
No.
CPU type
1) C Controller module, PC CPU module
2) MELSECNET/H board (personal computer)
3) CC-Link IE Controller Network interface board (personal computer)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
SAMPLE PROGRAMS
10 11 12 13
EVENT NUMBER LIST
A
I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.3 Access via MELSECNET/H
10 - 29
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(b) Accessible range for own station and [2.Connected station CPU] The own station and [2.Connected station CPU] are all accessible.
(c) Accessible range for [4.Target CPU]
1.Connected network
MELSECNET/H
Table 10.22 Accessibility table
4.Target CPU
2.Connected station CPU
3.Relayed network
QCPU
QnA CPU
ACPU
1)
Board for personal computer
LCPU
Q mode A mode
2)
3)
CC-Link IE Controller
*4,*5
Network*1
CC-Link IE Field Network
QCPU (Q mode)
MELSECNET/H*2 MELSECNET/10*3
MELSECNET(II)
Ethernet
Computer link
CC-Link
CC-Link IE Controller Network
CC-Link IE Field Network
C Controller module*6
MELSECNET/H MELSECNET/10 MELSECNET(II)
Ethernet
Computer link
CC-Link
: Accessible : Inaccessible
* 1 Only when all the CPU module connected and relay stations are Universal model QCPU, a CCLink IE Controller Network module of station number 65 or higher can be accessed.
* 2 Access is allowed when the MELSECNET/H module of the connected station is in the MELSECNET/ H mode.
* 3 Access is allowed when the MELSECNET/H module of the connected station is in the MELSECNET/ 10 mode.
* 4 The following C Controller module cannot access the C Controller module allocated to [4. Target CPU]. · 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)
10 - 30
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.3 Access via MELSECNET/H
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Table 10.22 Accessibility table (continued)
1.Connected 2.Connected
network
station CPU
3.Relayed network
QCPU
QCPU (Q mode)
CC-Link IE Controller Network*1 CC-Link IE Field Network
MELSECNET/H
MELSECNET/10
Q mode A mode
QnA CPU
4.Target CPU
ACPU
1)
*4,*5
*5 *5
Board for
personal
computer
2)
3)
LCPU
MELSECNET(II)
Ethernet
Computer link
CC-Link
CC-Link IE Controller Network
CC-Link IE Field Network
MELSECNET/H
QnACPU
MELSECNET/10
*5
MELSECNET/10
QCPU (A mode), ACPU
C Controller module*6
MELSECNET(II)
Ethernet
Computer link
CC-Link
CC-Link IE Controller Network
CC-Link IE Field Network
MELSECNET/H
MELSECNET/10
*5
MELSECNET(II)
Ethernet
Computer link
CC-Link
CC-Link IE Controller Network
CC-Link IE Field Network
MELSECNET/H
MELSECNET/10
MELSECNET(II)
Ethernet
Computer link
CC-Link
: Accessible : Inaccessible
* 1 Only when all the CPU module connected and relay stations are Universal model QCPU, a CCLink IE Controller Network module of station number 65 or higher can be accessed.
* 4 The following C Controller module cannot access the C Controller module allocated to [4. Target CPU]. · 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
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.3 Access via MELSECNET/H
10 - 31
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(2) Accessible devices
(a) How to read the table 1) Batch and random of devices
Item in the table Batch
Random
Table 10.23 Batch and random of devices
Description ·Batch write (mdSend, mdSendEx functions) ·Batch read (mdReceive, mdReceiveEx functions) ·Random write(mdRandW, mdRandWEx functions) ·Random read(mdRandR, mdRandREx functions) ·Bit set(mdDevSet, mdDevSetEx functions) Only bit devices can access. ·Bit reset(mdDevRst, mdDevRstEx functions) Only bit devices can access.
2) Access target for accessing other station
Table 10.24 Access target for accessing other station
No.
Access target
1) A1NCPU
2) A0J2HCPU, A1S(H)CPU, A1SJ(H)CPU, A2NCPU(-S1), A2S(H)CPU
3)
A2ACPU(-S1), A2UCPU(-S1), A2USCPU(-S1), A2USHCPU-S1 Q02(H)CPU-A, Q06HCPU-A
4) A3NCPU, A3ACPU, A3UCPU
5) A4UCPU
Q2ACPU(-S1), Q3ACPU, Q4ACPU, Q4ARCPU, Q2ASCPU(-S1), Q2ASHCPU(-S1)
Q00JCPU, Q00CPU, Q01CPU
Q02(H)CPU, Q06HCPU, Q12HCPU, Q25HCPU
Q02PHCPU, Q06PHCPU, Q12PHCPU, Q25PHCPU
6) Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU,
Q10UDHCPU, Q13UDHCPU, Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU,
Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU,
Q50UDEHCPU, Q100UDEHCPU, Q03UDVCPU, Q04UDVCPU, Q06UDVCPU, Q13UDVCPU,
Q26UDVCPU
C Controller module that controls a CC-Link IE Controller Network module,
C Controller module that controls a MELSECNET/H module,
7) PC CPU module that controls a MELSECNET/H module,
Personal computer with a CC-Link IE Controller Network interface board,
Personal computer with a MELSECNET/H board
8) L02CPU, L26CPU-BT
10 - 32
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.3 Access via MELSECNET/H
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(b) Accessible devices for accessing own station
Device
Own station input internal buffer (LX buffer) Own station output internal buffer (LY buffer) Own station link relay internal buffer (LB buffer) Own station link register internal buffer (LW buffer)
Q/QnA RECV function
Own station direct link input (LX) Own station direct link output (LY) Own station direct link relay (LB) Own station direct link register (LW) Own station direct link special relay (SB) Own station direct link special register (SW)
Table 10.25 Accessible devices for accessing own station
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Device type (Device name specification) DevX DevY DevB DevW
DevMAIL
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
DevLX(0) DevLY(0) DevLB(0) DevLW(0) DevSB(0) DevSW(0)
9
Accessibility
10
11
12
13 : Accessible : Inaccessible
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
SAMPLE PROGRAMS
EVENT NUMBER LIST
A
I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.3 Access via MELSECNET/H
10 - 33
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Device
X
Y
L
M*2,*3 SM (special relay), SB (link special relay for MELSECNET/ H, CC-Link IE Controller Network and CC-Link) F
T (contact)
T (coil)
C (contact)
C (coil)
T (current value)
C (current value)
D*2,*5 SD (special register), SW (link special register for MELSECNET/H, CC-Link IE Controller Network and CCLink)
(c) Accessible devices for accessing other station
Table 10.26 Accessible devices for accessing other station
Device type
Access target
(Device name specification)
1)
2)
3)
4)
5)
6)
Batch Random
DevX
Batch Random
DevY
Batch Random
DevL
Batch Random
DevM
Batch Random
DevSM
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch
DevF DevTT DevTC DevCT DevCC DevTN DevCN DevD
Random
DevSD
7)
8)
*1
*1
*1,*4 *1
*1,*4 *1
: 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 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
* 3 The following C Controller module cannot access the internal relay (M) of device No.32768 (8000H) or higher. · Q06CCPU-V
* 4 Available only when the device function is used. (
Page 4-35, Section 4.8)
* 5 The following C Controller module cannot access the extended data register (D). · Q06CCPU-V with serial number (first five digits) "10011" or earlier
(To the next page)
10 - 34
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.3 Access via MELSECNET/H
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Device T (main setting) T (sub setting 1) T (sub setting 2) T (sub setting 3) C (main setting) C (sub setting 1) C (sub setting 2) C (sub setting 3) A Z V (index register) R (file register) ZR (file register)*2 ER (extended file register) B*2,*9 W*2,*10 Q/QnA link special relay (within Q/QnACPU)
Table 10.26 Accessible devices for accessing other station (continued)
Device type
Access target
(Device name specification)
1)
2)
3)
4)
5)
6)
7)
8)
Batch Random
DevTM
Batch
*6
DevTS
Random
Batch Random
DevTS2
Batch Random
DevTS3
Batch Random
DevCM
Batch
*6
DevCS
Random
Batch Random
DevCS2
Batch Random
DevCS3
Batch Random
DevA
Batch Random
DevZ
Batch Random
DevV
Batch
DevR
*7
Random
Batch
DevZR
*8
Random
Batch
DevER(0) to DevER(256)
*8
Random
Batch Random
DevB
*11,*12
Batch
DevW
*11
Random
Batch Random
DevQSB
: Accessible : Inaccessible
* 2 When accessing to the device of number 32768 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
* 6 Access is not allowed for the A2ACPU(-S1). * 7 For the access, use ZR (file register) or ER (extended file register). * 8 Access is not allowed for the Q00JCPU. * 9 The following C Controller module cannot access the link relay (B) of device No.32768 (8000H) or
higher. · Q06CCPU-V * 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 BFFFFH or later cannot be accessed.
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.3 Access via MELSECNET/H
10 - 35
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Table 10.26 Accessible devices for accessing other station (continued)
Device
Device type
Access target
(Device name specification)
1)
2)
3)
4)
5)
6)
7)
8)
Retentive timer (contact)
Batch Random
DevSTT
Retentive timer (coil)
Batch Random
DevSTC
Q/QnA link special register (within Q/QnACPU)
Batch Random
DevQSW
Q/QnA edge relay (within Q/ QnACPU)
Batch Random
DevQV
Own station random access buffer
Batch Random
DevMRB
Retentive timer (current value)
Batch Random
DevSTN
Own station link register (for sending)
Batch Random
DevWw
Own station link register (for receiving)
Batch Random
DevWr
Own station buffer memory
Batch Random
DevSPB
Q/QnA SEND function (with arrival
Batch
*14
confirmation)*13
Random
DevMAIL
Q/QnA SEND function (no arrival
Batch
*14
confirmation)*13
Random
DevMAILNC
Direct link input (other station side)
Batch
DevLX(1) to DevLX(255)
*1
Random
Direct link output (other station side)
Batch Random
DevLY(1) to DevLY(255)
*1
Direct link relay (other station side)
Batch
DevLB(1) to DevLB(255)
*1
Random
Direct link register (other station side)*2
Batch Random
DevLW(1) to DevLW(255)
*1
Direct link special relay (other station side)
Batch Random
DevLSB(1) to DevLSB(255)
*1
Direct link special register (other station side)
Special direct buffer register, Intelligent function module buffer memory
Other station buffer memory
Batch Random
Batch
Random Batch
Random
DevLSW(1) to DevLSW(255) DevSPG(0) to DevSPG(255)
DevRBM
*1
: 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 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
* 13 This function is used to send messages to a network module on the other station via a
MELSECNET/H module.
Access is not allowed to a multiple CPU system (when the logical station numbers are specified).
* 14 Access is not allowed for MELSECNET/H modules (PC CPU modules) and CC-Link IE Controller
Network interface boards (personal computers).
(To the next page)
10 - 36
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.3 Access via MELSECNET/H
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Table 10.26 Accessible devices for accessing other station (continued)
Device
Device type
Access target
(Device name specification)
1)
2)
3)
4)
5)
6)
Other station random access buffer
Batch Random
DevRAB
Other station RX
Batch Random
DevRX
Other station RY
Batch Random
DevRY
Other station link register
Batch Random
DevRW
Other station SB (link special relay for CC-Link)
Batch Random
DevSB
Other station SW (link special register for CC-Link)
Batch Random
DevSW
: Accessible
7)
8)
: Inaccessible
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 10 11
PROGRAMMING USING VxWorks API FUNCTIONS
12
SAMPLE PROGRAMS
13
EVENT NUMBER LIST
A
I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.3 Access via MELSECNET/H
10 - 37
10 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.
C Controller module
1 Connected network
2 Connected Connected Relayed station CPU module module
3 Relayed network
4 Target Destination CPU module Figure 10.9 Accessible range via CC-Link IE Controller Network
The numbers in the [4.Target CPU] column indicate the modules or boards for personal computer as in the table below.
Table 10.27 Routing target CPU
No.
CPU type
1) C Controller module, PC CPU module
2) MELSECNET/H board (personal computer)
3) CC-Link IE Controller Network interface board (personal computer)
10 - 38
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.4 Access via CC-Link IE Controller Network
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS 9
(b) Accessible range for own station and [2.Connected station CPU] The own station and [2.Connected station CPU] are all accessible.
PROGRAMMING USING BUS INTERFACE FUNCTIONS
1.Connected network
CC-Link IE Controller Network
(c) Accessible range for [4.Target CPU]
2.Connected station CPU
QCPU (Q mode)
C Controller module*5
Table 10.28 Accessibility table
3.Relayed network
CC-Link IE Controller Network*1 CC-Link IE Field Network MELSECNET/H
QCPU Q mode A mode
*2
*2
QnACPU
4.Target CPU
ACPU
1)
*3,*4
*4
Board for personal computer
2)
3)
LCPU
MELSECNET/10
*2
*4
MELSECNET(II)
Ethernet
Computer link
CC-Link CC-Link IE Controller Network
CC-Link IE Field Network
MELSECNET/H
MELSECNET/10 MELSECNET(II)
Ethernet
Computer link CC-Link
: Accessible : Inaccessible
* 1 Only when all the CPU module on the connected and relay stations are Universal model QCPU, a CC-Link IE Controller Network module of station number 65 or higher can be accessed.
* 2 Access is not allowed when the connected station CPU is the Q00CPU or Q01CPU. * 3 The following C Controller module cannot access the C Controller module allocated to [4. Target
CPU]. · Q06CCPU-V with serial number (first five digits) "10011" or earlier * 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
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
10 11 12 13 A
I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.4 Access via CC-Link IE Controller Network
10 - 39
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(2) Accessible devices
(a) How to read the table 1) Batch and random of devices
Item in the table Batch
Random
Table 10.29 Batch and random of devices
Description ·Batch write (mdSend, mdSendEx functions) ·Batch read (mdReceive, mdReceiveEx functions) ·Random write(mdRandW, mdRandWEx functions) ·Random read(mdRandR, mdRandREx functions) ·Bit set(mdDevSet, mdDevSetEx functions) Only bit devices can access. ·Bit reset(mdDevRst, mdDevRstEx functions) Only bit devices can access.
2) Access target for accessing other station
Table 10.30 Access target for accessing other station
No.
Access target
1) A1NCPU
2) A0J2HCPU, A1S(H)CPU, A1SJ(H)CPU, A2NCPU(-S1), A2S(H)CPU
3)
A2ACPU(-S1), A2UCPU(-S1), A2USCPU(-S1), A2USHCPU-S1 Q02(H)CPU-A, Q06HCPU-A
4) A3NCPU, A3ACPU, A3UCPU
5) A4UCPU
Q2ACPU(-S1), Q3ACPU, Q4ACPU, Q4ARCPU, Q2ASCPU(-S1), Q2ASHCPU(-S1)
Q00JCPU, Q00CPU, Q01CPU
Q02(H)CPU, Q06HCPU, Q12HCPU, Q25HCPU
Q02PHCPU, Q06PHCPU, Q12PHCPU, Q25PHCPU
6) Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU,
Q10UDHCPU, Q13UDHCPU, Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU,
Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU,
Q50UDEHCPU, Q100UDEHCPU, Q03UDVCPU, Q04UDVCPU, Q06UDVCPU, Q13UDVCPU,
Q26UDVCPU
C Controller module that controls a CC-Link IE Controller Network module,
C Controller module that controls a MELSECNET/H module,
7) PC CPU module that controls a MELSECNET/H module,
Personal computer with a CC-Link IE Controller Network interface board,
Personal computer with a MELSECNET/H board
8) L02CPU, L26CPU-BT
10 - 40
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.4 Access via CC-Link IE Controller Network
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
(b) Accessible devices for accessing own station
Device
Own station input internal buffer (LX buffer) Own station output internal buffer (LY buffer) Own station link relay internal buffer (LB buffer) Own station link register internal buffer (LW buffer)
Q/QnA RECV function
Own station direct link input (LX) Own station direct link output (LY) Own station direct link relay (LB) Own station direct link register (LW)*1 Own station direct link special relay (SB) Own station direct link special register (SW)
Table 10.31 Accessible devices for accessing own station
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Device type (Device name specification) DevX DevY DevB DevW
DevMAIL
Accessibility
Batch Random
Batch Random
Batch Random
Batch Random
DevLX(0) DevLY(0) DevLB(0) DevLW(0)
Batch Random
Batch Random
DevSB(0) DevSW(0)
: Accessible : Inaccessible
* 1 When accessing to the device of number 32768 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
SAMPLE PROGRAMS
9 10 11 12 13
EVENT NUMBER LIST
A
I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.4 Access via CC-Link IE Controller Network
10 - 41
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Device
X
Y
L
M*2,*3 SM (special relay), SB (link special relay for MELSECNET/H, CC-Link IE Controller Network and CCLink) F
T (contact)
T (coil)
C (contact)
C (coil)
T (current value)
C (current value)
D*2,*5 SD (special register), SW (link special register for MELSECNET/H, CC-Link IE Controller Network and CCLink)
(c) Accessible devices for accessing other station
Table 10.32 Accessible devices for accessing other station
Batch Random
Batch Random
Batch Random
Batch Random
Device type (Device name specification)
DevX
DevY
DevL
DevM
Access target
1)
2)
3)
4)
5)
6)
Batch Random
DevSM
7)
8)
*1
*1
*1,*4 *1
Batch Random
DevF
Batch Random
DevTT
Batch Random
DevTC
Batch Random
DevCT
Batch Random
DevCC
Batch Random
DevTN
Batch Random
DevCN
Batch Random
DevD
*1,*4
Batch
DevSD
*1
Random
: 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 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
* 3 The following C Controller module cannot access the internal relay (M) of device No.32768 (8000H) or higher. · Q06CCPU-V
* 4 Available only when the device function is used. (
Page 4-35, Section 4.8)
* 5 The following C Controller module cannot access the extended data register (D). · Q06CCPU-V with serial number (first five digits) "10011" or earlier
(To the next page)
10 - 42
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.4 Access via CC-Link IE Controller Network
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Table 10.32 Accessible devices for accessing other station (continued)
T (main setting)
Device
Batch Random
Device type (Device name specification)
DevTM
Access target
1)
2)
3)
4)
5)
6)
Batch
*6
T (sub setting 1)
DevTS
Random
T (sub setting 2)
Batch Random
DevTS2
T (sub setting 3)
Batch Random
DevTS3
C (main setting)
Batch Random
DevCM
Batch
*6
C (sub setting 1)
DevCS
Random
C (sub setting 2)
Batch Random
DevCS2
C (sub setting 3)
Batch Random
DevCS3
A
Batch
DevA
Random
Z
Batch Random
DevZ
V (index register)
Batch Random
DevV
R (file register)
Batch Random
DevR
*7
ZR (file register)*2
Batch
DevZR
*8
Random
ER (extended file register)
Batch Random
DevER(0) to DevER(256)
*8
B*2, *9
Batch Random
DevB
W*2, *10
Batch Random
DevW
Q/QnA link special relay (within Q/ QnACPU)
Batch Random
DevQSB
7)
8)
*11,*12 *11
: 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 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
* 6 Access is not allowed for the A2ACPU(-S1). * 7 For the access, use ZR (file register) or ER (extended file register). * 8 Access is not allowed for the Q00JCPU. * 9 The following C Controller module cannot access the link relay (B) of device No.32768 (8000H) or higher.
· Q06CCPU-V * 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 BFFFFH or later cannot be accessed.
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.4 Access via CC-Link IE Controller Network
10 - 43
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Device
Retentive timer (contact)
Retentive timer (coil)
Q/QnAlink special register (within Q/QnACPU) Q/QnA edge relay (within Q/ QnACPU) Own station random access buffer
Retentive timer (current value)
Own station link register (for sending) Own station link register (for receiving)
Own station buffer memory
Q/QnA SEND function (with arrival confirmation)*13 Q/QnA SEND function (no arrival confirmation)*13
Direct link input (other station)
Direct link output (other station)
Direct link relay (other station)
Direct link register (other station)*2 Direct link special relay (other station)
Direct link special register (other station) Special direct buffer register, Intelligent function module buffer memory
Table 10.32 Accessible devices for accessing other station (continued)
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch Random
Batch
Random
Batch
Random Batch
Random Batch
Random Batch
Random Batch
Random
Batch
Random
Device type
Access target
(Device name specification)
1)
2)
3)
4)
5)
6)
7)
8)
DevSTT
DevSTC
DevQSW
DevQV
DevMRB
DevSTN
DevWw
DevWr
DevSPB
*14
DevMAIL
*14
DevMAILNC
DevLX(1) to DevLX(255)
*1
DevLY(1) to DevLY(255)
*1
DevLB(1) to DevLB(255)
*1
DevLW(1) to DevLW(255)
*1
DevLSB(1) to DevLSB(255)
*1
Batch
DevLSW(1) to DevLSW(255)
*1
Random
Batch Random
DevSPG(0) to DevSPG(255)
*1
: 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 (8000H) or higher, use an extended function.
(
Page 10-4, Section 10.2)
* 13 This function is used to send messages to a network module on the other station via a CC-Link IE Controller Network module. Access is not allowed to a multiple CPU system (when the logical station numbers are specified).
* 14 Access is not allowed for MELSECNET/H modules (PC CPU modules) and CC-Link IE Controller Network interface boards (personal computers).
(To the next page)
10 - 44
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.4 Access via CC-Link IE Controller Network
10 PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
Device
Other station buffer memory Other station random access buffer Other station RX
Other station RY
Other station link register Other station SB (link special relay for CC-Link) Other station SW (link special register for CC-Link)
Table 10.32 Accessible devices for accessing other station (continued)
Device type
Access target
(Device name specification)
1)
2)
3)
4)
5)
6)
Batch Random
DevRBM
Batch Random
DevRAB
Batch Random
DevRX
Batch Random
DevRY
Batch Random
DevRW
Batch Random
DevSB
Batch Random
DevSW
: Accessible
7)
8)
: Inaccessible
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
9 10 11
PROGRAMMING USING VxWorks API FUNCTIONS
12
SAMPLE PROGRAMS
13
EVENT NUMBER LIST
A
I
10.13 Accessible Ranges and Devices of the MELSEC Data Link Function 10.13.4 Access via CC-Link IE Controller Network
10 - 45
11 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"
For each component functionality and VxWorks API functions, refer to the manual for VxWorks.
(1) Sample program using VxWorks functions
Installing SW3PVC-CCPU registers the sample programs of the following functions.
(
Page 12-1, CHAPTER 12)
· The Connect function between C Controller module and GOT (Microcomputer
connection)
· The RAM disk function
(2) Precautions for using VxWorks API functions
(a) Changing the system clock rate The C Controller module supports system clock rate of 60 to 1000. (Default: 60) When changing the system clock rate, use the sysClkRateSet function. For setting and changing the system clock rate, refer to the manual for VxWorks.
(3) Precautions for the Wind River Systems product
We, Mitsubishi, make no warranty for the Wind River Systems product and will not be liable for any problems and damages caused by the Wind River Systems product during use of the C Controller module. For the problems or specifications of the Wind River Systems product, refer to the corresponding manual or consult Wind River Systems, Inc. Contact information is available on the following website. www.windriver.com
11 - 1
11 PROGRAMMING USING VxWorks API FUNCTIONS 9
Memo
10 11 12 13 A I
11 - 2
EVENT NUMBER LIST
SAMPLE PROGRAMS
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
12 SAMPLE PROGRAMS
CHAPTER 12 SAMPLE PROGRAMS
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
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".). For opening sample programs, refer to the following.
Page 12-5, Section 12.1
Table 12.1 Registered sample programs
Folder name GOTtest
File name GOTtest.c
DevAccess\DevAcc DevAccessChanC
essChanCCIEC
CIEC.c
MDtest
DevAccess\DevAcc DevAccessChanC
essChanCCL
CL.c
DevAccess\DevAcc DevAccessChanM
essChanMNH
NH.c
DevAccess\DevAcc DevAccessChanQ
essChanQBF
BF.c
Description of sample program For connection to GOT. For access to the following modules using MELSEC data link functions ·A CC-Link IE Controller Network module (own station) controlled by the C Controller module. ·CC-Link IE Controller Network modules or programmable controller CPUs on other stations via a CC-Link IE Controller Network module controlled by the C Controller module. For access to the following modules using MELSEC data link functions ·A CC-Link module (own station) controlled by the C Controller module. ·CC-Link modules or programmable controller CPUs on other stations via a CCLink module controlled by the C Controller module. For access to the following modules using MELSEC data link functions ·A MELSECNET/H module (host station) controlled by the C Controller module. ·MELSECNET/H modules or programmable controller CPUs on other stations via a MELSECNET/H module controlled by the C Controller module. For access to the following module using MELSEC data link functions ·CPU No.1 mounted together with the C Controller module in a multiple CPU system.
(To the next page)
12 - 1
12 SAMPLE PROGRAMS
Table 12.1 Registered sample programs (continued)
Others
QBFtest Script
Folder name
File name
CCIEField\ LocalStation
LocalStation.c
CCIEField\ MasterStation_Loc alStation
MasterStation_Loc alStation.c
CCIEField\ MasterStation_Rem oteIO
MasterStation_Re moteIO.c
CFTaskPrioritySet.c
CFTaskPrioritySet. c
FTPGet.c
FTPGet.c
MakeRAMDisk.c MakeRAMDisk.c
QD75Status.c
QD75Status.c
QPParamSet.c
SntpTimeSet.c CFChange EntryWDTInt MotionLink\ MotionLink MotionLink\ MotionSyncInt QBFMessage LoginUserRegist ParamBackUp ParamRestore RAMFormat
QPParamSet.c
SntpTimeSet.c CFChange.c EntryWDTInt.c
MotionLink.c
MotionSyncInt.c
QBFMessage.c STARTUP.CMD STARTUP.CMD STARTUP.CMD STARTUP.CMD
Description of sample program For performing cyclic transmission with the master station in the CC-Link IE Field Network (local station).
For performing cyclic transmission with the local station in the CC-Link IE Field Network (master station).
For performing cyclic transmission with the intelligent device station in the CCLink IE Field Network (master station).
For priority (default: 50) change of the system task (XBD service task) which operates when accessing to a CompactFlash card. For FTP communications For RAM disk creation For 1-shot monitoring of the positioning module status (current feed value, axis error No., and axis warning No.) For automatic transfer of the parameter file created in GX Configurator-QP to a positioning module For setting clock data by acquiring the data from the SNTP server computer For unmounting a CompactFlash card when X0 turns on For user watchdog timer error interrupt registration
The linkage with the Motion CPU is utilized for this sample program.
For execution of the interrupt process synchronizing with the multiple CPU high speed transmission with either the Q172DCPU or Q173DCPU. For sending messages via MELSECNET/H Sample script file for login user registration Sample script file for parameter backup Sample script file for parameter restoration Sample script file for standard RAM formatting
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
SAMPLE PROGRAMS
9 10 11 12 13
EVENT NUMBER LIST
A
I
12 - 2
12 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
Folder name GOTtest
DevAccess\ DevAccessChanC CIEC
MDtest
DevAccess\ DevAccessChanC CL
DevAccess\ DevAccessChanM NH
DevAccess\ DevAccessChanQ BF
Table 12.2 Registered sample programs
File name GOTtest.c
DevAccessChanC CIEC.c
DevAccessChanC CL.c
DevAccessChanM NH.c
DevAccessChanQ BF.c
Description of sample program For connection to GOT For access to the following modules using MELSEC data link functions For the Q06CCPU-V-B, this sample program cannot be used. ·A CC-Link IE Controller Network module (own station) controlled by the C Controller module. ·CC-Link IE Controller Network modules or programmable controller CPUs on other stations via a CC-Link IE Controller Network module controlled by the C Controller module. For access to the following modules using MELSEC data link functions For the Q06CCPU-V-B, this sample program cannot be used. ·A CC-Link module (own station) controlled by the C Controller module. ·CC-Link modules and programmable controller CPUs on other stations via a CCLink module controlled by the C Controller module. For access to the following modules using MELSEC data link functions For the Q06CCPU-V-B, this sample program cannot be used. ·A MELSECNET/H module (host station) controlled by the C Controller module. ·MELSECNET/H modules and programmable controller CPUs on other stations via a MELSECNET/H module controlled by the C Controller module. For access to the following module using MELSEC data link functions For the Q06CCPU-V-B, this sample program cannot be used. ·CPU No.1 configuring a multiple CPU system with the C Controller module.
(To the next page)
12 - 3
12 SAMPLE PROGRAMS
Table 12.2 Registered sample programs (continued)
Others
QBFtest Script
Folder name
File name
CCIEField\ LocalStation
LocalStation.c
CCIEField\ MasterStation_Loc alStation
MasterStation_Loc alStation.c
CCIEField\ MasterStation_Rem oteIO
MasterStation_Re moteIO.c
FTPGet.c
FTPGet.c
MakeRAMDisk.c MakeRAMDisk.c
QD75Status.c
QD75Status.c
QPParamSet.c
SntpTimeSet.c
CFChange
EntryWDTInt MotionLink QBFMessage Shutdown LoginUserRegist ParamBackUp ParamRestore ROMFormat
QPParamSet.c
SntpTimeSet.c
CFChange.c
EntryWDTInt.c MotionLink.c QBFMessage.c ROMShutdown.c STARTUP.CMD STARTUP.CMD STARTUP.CMD STARTUP.CMD
Description of sample program For performing cyclic transmission with the master station in the CC-Link IE Field Network (local station).
For performing cyclic transmission with the local station in the CC-Link IE Field Network (master station).
For performing cyclic transmission with the intelligent device station in the CCLink IE Field Network (master station).
For FTP communication For RAM disk creation For 1-shot monitoring of the positioning module status (current feed value, axis error No., and axis warning No.) For automatic transfer of the parameter file created in GX Configurator-QP to a positioning module For setting clock data by acquiring the data from the SNTP server computer For unmounting a CompactFlash card when X0 turns on For the Q06CCPU-V-B, this sample program cannot be used. For user watchdog timer error interrupt registration The linkage with the Motion CPU is used for this sample program. For sending messages via MELSECNET/H For shutting down the standard ROM when X0 turns on Sample script file for login user registration Sample script file for parameter backup Sample script file for parameter restoration Sample script file for standard ROM formatting
Remark
Sample programs which cannot be used in the C Controller module contain the notification message as shown below.
/**************************************************************************/
/* Sample program
*/
/* When X0 is ON, unmount the CF card.
*/
/* Note)
*/
/* This sample program cannot be used because
*/
/* Q06CCPU-V-B does not support CF card interface.
*/
/* If the following functions are executed, unsupported
*/
/* communications path error (19203 [0x4B03]) will be
*/
/* returned.
*/
Figure 12.1 A sample program which cannot be used in the Q06CCPU-V-B
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
12 - 4
12 SAMPLE PROGRAMS
12.1 Procedure for Opening Sample Programs
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
This section describes the procedure for opening sample programs when SW3PVC-CCPU is installed in "C:\MELSEC".
When installing SW3PVC-CCPU in folders other than "C:\MELSEC", create a new project with reference to the following procedure. Copying the contents of the sample program to the source file enables the compiling.
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.
1 Start Workbench. 2 Select the [File] [Import].
(To the next page)
12 - 5
12.1 Procedure for Opening Sample Programs
PROGRAMMING USING BUS INTERFACE FUNCTIONS
12 SAMPLE PROGRAMS 9 (From the previous page)
3 Select "General" "Existing Projects into Workplace", and click the Next> button.
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
11
PROGRAMMING USING VxWorks API FUNCTIONS
4 Specify a directory name to "Select root directory" which the source file of the sample program are stored.
12
Confirm the sample program in "Projects" is selected, and
click the Finish button.
SAMPLE PROGRAMS
13
EVENT NUMBER LIST
A
5 Double click the file name of the sample program with imported project so that the sample program is opened to use.
I
(Completed)
12.1 Procedure for Opening Sample Programs
12 - 6
12 SAMPLE PROGRAMS
(2) Procedure for opening the sample program for the Q06CCPU-V(-B)
1 Start Tornado. When Workspace is opened automatically, perform procedure of 7 or later. When Workspace is not opened automatically, perform the following operations continuously.
2 Select the [File] [New Project] from the menu bar.
3 Select "Create downloadable application modules for VxWorks", and click the OK button.
4 Enter the "Name", "Location", and "Workspace", and click the Next> button.
12 - 7
5 Select "A toolchain", a setting corresponding to the machine from a pull down menu shown below, and click the Next> button. Q06CCPU-V: SH7750gnule (Little endian) Q06CCPU-V-B: SH7750gnu (Big endian) REFERENCE An endian format will be decided by this setting. When other setting is selected by the endian format, the program does not operate.
(To the next page)
12.1 Procedure for Opening Sample Programs
PROGRAMMING USING BUS INTERFACE FUNCTIONS
12 SAMPLE PROGRAMS 9 (From the previous page)
6 After confirming the setting of "Workspace", "Project", and "Tool Chain" are correct, click the Finish button.
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING VxWorks API FUNCTIONS
11
7 Select the "File" "Add Project to Workspace".
12
SAMPLE PROGRAMS
EVENT NUMBER LIST
13
8 Select the file whose extension is wpi in the same folder of the sample program, and click the Add button.
A
9 For the Q06CCPU-V, the sample program can be opened
I
from the project added to Workspace.
For the Q06CCPU-V-B, operate the following procedures.
(To the next page)
12.1 Procedure for Opening Sample Programs
12 - 8
12 SAMPLE PROGRAMS
(From the previous page)
10 Open the <<Build>> tab of "Workspace" window.
11 Double click the icon ( ) to display the following items.
12 Right click "SH7750gnu" and select "Set 'SH7750gnu' as Active Build" from the menu bar.
(To the next page)
12 - 9
12.1 Procedure for Opening Sample Programs
PROGRAMMING USING BUS INTERFACE FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING VxWorks API FUNCTIONS
12 SAMPLE PROGRAMS 9 (From the previous page) 13 The sample program can be opened from the project when opening the <<Files>> tab of the "Workspace" window. 10
11
(Completed)
12
13
A
I
SAMPLE PROGRAMS
EVENT NUMBER LIST
12.1 Procedure for Opening Sample Programs
12 - 10
13 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. in the following procedure and take corrective actions.
POINT
When more than one event occur, take corrective actions for each event in chronological order.
1) Open the "Detailed event information" screen by double-clicking on a event to
correct on the history screen of C Controller setting utility. (
Page 4-6,
Section 4.3 (3))
13 - 1
Figure 13.1 Detailed event information screen
2) When "Application" is shown in the "Event type" field, it indicates that the event was registered by the user program (QBF_RegistEventLog function). Take corrective actions determined by user.
3) The following "Event type" indicate that the event has occurred in the C Controller system. · System (Info.) · System (Warning) · System (Err.) Check "source" and "event No." on the Detailed event information screen, and take corrective actions referring to the following table.
Source
MQbfDrv MXwdkDrv MUtlIfQbf
MUtlIfMd
MUtlIfCom MMain MFDrv MCfDrv MEtherDrv
Table 13.1 Source list
Data type
Bus interface driver (bus part) related Bus interface driver (system part) related Utility communication interface (bus interface part) related Utility communication interface (MELSEC communication part) related Utility communication interface (common part) related C Controller module main part related Flash ROM and standard RAM related CompactFlash card related Ethernet related
Reference page
Page 13-2 Page 13-3 Page 13-3
Page 13-4
Page 13-4 Page 13-5 Page 13-5 Page 13-7 Page 13-8
13 EVENT NUMBER LIST 9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
Event No. C000011EH C0000127H C0000131H C0000201H C0000202H C0000204H C0000206H C0000207H C0000208H
C0000209H
C000020AH
C000020BH
C000020EH
C0000210H
C0000211H C0000212H C0000213H
C0000214H C0000215H C0000216H C0000217H C0000218H C0000219H C000021AH
C000021BH
C000021CH
(1) When the source is "MQbfDrv"
When taking corrective actions of corresponding error code, refer to HELP of C Controller setting utility.
Event type
System(Err.)
System(Err.) System(Err.) System(Err.)
System(Err.)
System(Err.)
Table 13.2 Corrective actions Event
Failed to allocate memory required for the driver start-up. SYSTEM WDT ERROR occurred. USER WDT ERROR occurred. AC/DC DOWN occurred.
CONTROL-BUS.ERR. occurred.
UNIT VERIFY ERR. occurred.
Corrective action Increase the system memory. Reduce the memory usage of other programs. Take corrective actions for error code 5000. Take corrective actions for error code 5001. Take corrective actions for error code 1500. Take corrective actions for error code 1413, 1414, 1415, and 1416. Take corrective actions for error code 2000.
System(Err.)
FUSE BREAK OFF occurred.
Take corrective actions for error code 1300.
System(Err.) System(Err.) System(Err.)
System(Err.)
System(Err.)
System(Err.) System(Err.) System(Err.) System(Err.) System(Err.) System(Err.) System(Err.) System(Err.) System(Err.) System(Err.) System(Err.) System(Err.) System(Err.) System(Err.)
SP.UNIT DOWN occurred. CONTROL-BUS.ERR. occurred.
SP.UNIT LAY ERR. occurred.
PARAMETER ERROR occurred. An error occurred during module initialization. (Only the first error is displayed.) A CPU module built-in battery error occurred. MULTI CPU DOWN occurred.
MULTI EXE.ERROR occurred. MULTI CPU ERROR occurred. SP.PARAMETER ERROR occurred.
LINK PARAMETER ERROR occurred. I/O INT.ERROR occurred. MAIN CPU DOWN occurred. A momentary stop occurred. LINK REFRESH TIME OVER occurred. SINGLE PS.DOWN occurred. SINGLE PS.ERROR occurred.
MULTI-C.BUS.ERR. occurred.
CPU LAY ERROR occurred.
Take corrective actions for error code 1401 and 1403. Take corrective actions for error code 1412. Take corrective actions for error code 2100, 2103, 2106, 2107, 2108, 2120, 2121, 2122, 2124, 2125, 2126, and 2150. Take corrective actions for error code 3000, 3001, 3010, 3012, 3014, 3015, and 3016.
Take corrective actions corresponding to the error code displayed in the event information.
Take corrective actions for error code 1600.
Take corrective actions for error code 7000 and 7002. Take corrective actions for error code 7010, 7011, and 7013. Take corrective actions for error code 7020. Take corrective actions for error code 3300, 3301, 3302, and 3303. Take corrective actions for error code 3100, 3101, 3102, 3103, 3104, 3105, and 3107. Take corrective actions for error code 1310. Take corrective actions for error code 1000 and 1009. Take corrective actions for error code 1500. Take corrective actions for error code 5012. Take corrective actions for error code 1510. Take corrective actions for error code 1520. Take corrective actions for error code 1430, 1431, 1432, 1433, 1434, 1435, 1436, 1437, and 1439. Take corrective actions for error code 7036.
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
10 11 12 13 A I
13 - 2
13 EVENT NUMBER LIST
Event No. 40000000H
C0000001H 40000002H
(2) When the source is "MXwdkDrv"
Event type System(Info.)
System(Err.) System(info.)
Table 13.3 Corrective action
Event The clock data of the C Controller module have been set. This event occurs when: ·Clock data was set by executing the QBF_SetTime function. ·Clock data was set by C Controller setting utility. ·Clock data was set by peripheral devices such as GOT and MX Component.
An exceptional error occurred.
The clock data were corrected by the clock synchronization function. This event is registered when a clock data difference from a CPU No. 1 is detected after enabling the Clock synchronization function.
Corrective action
Reexamine the user program by checking the event detail information (such as error details, task names, and program counters). Check the operation methods of Workbench or Tornado as well. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
Event No. C0000000H
(3) When source is "MUtlIfQbf"
Event type
Table 13.4 Corrective action Event
System(Err.)
An illegal packet error occurred.
C0000001H System(Err.)
An instruction error occurred.
C0000002H System(Err.)
A socket generation error occurred.
C0000003H System(Err.)
A port acquisition error occurred.
C0000004H System(Err.)
A bind error occurred.
Corrective action Check the port No. used and change it if necessary. Change the IP address. Check the utility and the C Controller module versions. Restart the C Controller module. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. Check the port No. used. Check for overlap between the C Controller module ports. Restart the C Controller module. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
13 - 3
13 EVENT NUMBER LIST
Event No. C0000000H
(4) When source is "MUtlIfMd"
Event type
Table 13.5 Corrective action Event
System(Err.)
An illegal packet error occurred.
C0000001H System(Err.)
An instruction error occurred.
C0000002H System(Err.)
A socket generation error occurred.
C0000003H System(Err.)
A port acquisition error occurred.
C0000004H System(Err.)
A bind error occurred.
Event No. C0000000H
(5) When the source is "MUtlIfCom"
Event type
Table 13.6 Corrective action Event
System(Err.)
An illegal packet error occurred.
C0000001H System(Err.)
An instruction error occurred.
C0000002H System(Err.)
A socket generation error occurred.
C0000003H System(Err.)
A port acquisition error occurred.
C0000004H System(Err.)
A bind error occurred.
Corrective action Check the port No. used and change it if necessary. Change the IP address. Check the utility and C Controller module versions. Restart the C Controller module. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. A port acquisition error occurred. Check the port No. used. Check for overlap between the C Controller module ports. Restart the C Controller module. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
Corrective action Check the port No. used and change it if necessary. Change the IP address. Check the utility and C Controller module versions. Restart the C Controller module. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. Check the port No. used. Check for overlap between the C Controller module ports. Restart the C Controller module. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
13 - 4
13 EVENT NUMBER LIST
Event No. C0000110H C0000111H
C0000330H
Event No. 80000000H C0000400H C0000401H
(6) When the source is "MMain"
When taking corrective actions for an error code, refer to HELP of C Controller setting utility.
Event type System(Err.) System(Err.)
System(Err.)
Table 13.7 Corrective action Event
A script execution error occurred.
·One of commands (lines) in the script file has more than 129 characters. ·The command in the script file cannot be executed. (An error exists in the syntax, or the command does not exist.) (A stop error occurs in the C Controller module [CPU error code 2502] and the module stops execution of the script command.)
Failed to access LAN.
Corrective action A system error in the C Controller module is possible. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
Take corrective actions for error code 2502.
The parameter file (IP address setting area) does not exist. Using the C Controller setting utility, set the IP address or write the parameters. A system error in the C Controller is possible cause. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
(7) When the source is "MFDrv"
When taking corrective actions for an error code, refer to HELP of C Controller setting utility.
Event type System(Warning) System(Err.) System(Err.)
Table 13.8 Corrective action
Event
Corrective action
·Q12DCCPU-V The standard ROM drive was illegally accessed. ·Q06CCPU-V(-B) The number of standard ROM drive "/ROM" deletions exceeded 100 thousand times.
·Q12DCCPU-V It might be a breakdown of the C Controller module. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. ·Q06CCPU-V(-B) Change the writing media from the standard ROM drive to the CompactFlash card "/CF", or replace the C Controller module.
A standard ROM drive "/ROM" format error occurred.
Reformat the standard ROM drive "/ROM".
Usage of the battery backup RAM exceeded the capacity
A system error in the C Controller is possible cause. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
(To the next page)
13 - 5
13 EVENT NUMBER LIST
Event No.
Event type
80000406H
System(Warning)
C0000408H System(Err.)
C0000409H System(Err.) C000040AH System(Err.) C0000410H System(Err.)
C0000416H C0000417H
System(Err.) System(Err.)
Table 13.8 Corrective action (continued)
Event A timeout occurred during writing to file in the standard ROM drive "/ROM".
A battery backup RAM error was detected.
An internal ROM ("/ROM","/SYSTEMROM") error was detected. MAIN CPU DOWN occurred.
A standard RAM drive "/RAM" format error occurred.
A standard RAM drive "/RAM" error was detected. RAM ERROR occurred.
Corrective action Write the file again if the file was not written correctly. If this event occurs frequently, reexamine the user program (processing, task priority, etc.) that runs on the C Controller module. Check if an interrupt ruotine (interrupt program) is writing data into the same SRAM area. If the error persists, a system error in the C Controller module is probable. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. A system error in the C Controller module is probable. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. It refers to the Error Code 1000. Reformat the standard RAM drive "/RAM". When this event is generated even if it formats it again, it might be a breakdown of the C Controller module. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
It refers to the Error Code 1106.
It refers to the Error Code 1106.
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
SAMPLE PROGRAMS
9 10 11 12 13
EVENT NUMBER LIST
A
I
13 - 6
13 EVENT NUMBER LIST
Event No. C0000480H C0000481H C0000482H C0000483H C0000490H C0000491H
C0000492H
C0000493H
(8) When the source is "MCfDrv"
Event type System(Err.) System(Err.) System(Err.) System(Err.) System(Err.) System(Err.)
System(Err.)
System(Err.)
Table 13.9 Corrective action
Event The CompactFlash card is not responding. An error occurred while obtaining the CompactFlash card drive information. An error occurred while reading master boot record (MBR). The master boot record (MBR) cannot be recognized in this format. A resource shortage error occurred.
A CF driver initialization error occurred.
A device name registration error occurred.
A block No. error occurred.
Corrective action The CompactFlash Card is pulled out once, and it inserts it again. Replace the CompactFlash card. The CompactFlash Card is pulled out once, and it inserts it again. Replace the CompactFlash card. The CompactFlash Card is pulled out once, and it inserts it again. Reformat the CompactFlash card on a personal computer, etc. Replace the CompactFlash card. Reformat the CompactFlash card on a personal computer, etc. Replace the CompactFlash card. Check the utilization of the memory, provide a free space, and execute again. A system error in the C Controller is possible cause. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. A system error in the C Controller is possible cause. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. A system error in the C Controller is possible cause. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
13 - 7
13 EVENT NUMBER LIST
Event No. C0000200H C0000201H C0000202H C0000203H C0000210H
(9) When the source is "MEtherDrv"
Event type System(Err.) System(Err.) System(Err.) System(Err.) System(Err.)
Table 13.10 Corrective action
Event An initialization parameter error occurred.
A resource shortage error occurred. An END or MIB-II structure initialization error occurred. An interrupt registration error occurred.
An MII clock stop was detected.
Corrective action A system error in the C Controller is possible cause. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. A system error in the C Controller is possible cause. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. A system error in the C Controller is possible cause. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. A system error in the C Controller is possible cause. Please consult your local Mitsubishi service center or representative, explaining the details of the problem. A system error in the C Controller is possible cause. Please consult your local Mitsubishi service center or representative, explaining the details of the problem.
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
SAMPLE PROGRAMS
9 10 11 12 13
EVENT NUMBER LIST
A
I
13 - 8
APPENDICES
APPENDICES
Appendix 1 VxWorks Component List
Q12DCCPU-V
Q06CCPU-V
Q06CCPU-V-B
This section describes the components implemented in the C Controller module and how to check information of the components.
(1) VxWorks component list
(a) For the Q12DCCPU-V The following list shows the components implemented in the C Controller module.
Table APPX.1 VxWorks component list
Component
Macro
Address Space Allocator Show Routines address space shell commands ANSI assert
INCLUDE_ADR_SPACE_SHOW INCLUDE_ADR_SPACE_SHELL_CMD INCLUDE_ANSI_ASSERT
ANSI ctype ANSI errno to erro string conversion function ANSI locale
INCLUDE_ANSI_CTYPE INCLUDE_ANSI_STRERROR INCLUDE_ANSI_LOCALE
ANSI math ANSI stdio ANSI stdio extensions ANSI stdlib ANSI string ANSI string duplication function ANSI time application initialization arpLib Attach END to IPv4
INCLUDE_ANSI_MATH INCLUDE_ANSI_STDIO INCLUDE_ANSI_STDIO_EXTRA INCLUDE_ANSI_STDLIB INCLUDE_ANSI_STRING INCLUDE_ANSI_STRDUP INCLUDE_ANSI_TIME INCLUDE_USER_APPL INCLUDE_ARP_API INCLUDE_IPATTACH
AUX clock basic memory allocator basic MMU basic network support
INCLUDE_AUX_CLK INCLUDE_MEM_MGR_BASIC INCLUDE_MMU_BASIC INCLUDE_NETWORK
Basic PPP Components*1 binary semaphore creation routine binary semaphores Boot parameter process BPF Support BSD socket support BSP Memory Configuration buffer manager built-in symbol table c line interpreter
INCLUDE_BASIC_PPP
INCLUDE_SEM_BINARY_CREATE INCLUDE_SEM_BINARY INCLUDE_NET_BOOT INCLUDE_BPF INCLUDE_BSD_SOCKET INCLUDE_MEMORY_CONFIG INCLUDE_BUF_MGR INCLUDE_STANDALONE_SYM_TBL INCLUDE_SHELL_INTERP_C
C++ symbol demangler C++ compiler support routines C++ core runtime
INCLUDE_CPLUS_DEMANGLER INCLUDE_CPLUS_LANG INCLUDE_CPLUS
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 - 1 Appendix 1 VxWorks Component List
APPENDICES
Table APPX.1 VxWorks component list (continued)
cache support
Component
Macro INCLUDE_CACHE_SUPPORT
command line interpreter coprocessor coprocessor show routine Core NFS client counting semaphore creation routine counting semaphores
INCLUDE_SHELL_INTERP_CMD INCLUDE_COPROCESSOR INCLUDE_COPROCESSOR_SHOW INCLUDE_CORE_NFS_CLIENT INCLUDE_SEM_COUNTING_CREATE INCLUDE_SEM_COUNTING
Create Basic PPP Framework*1 debug shell commands debugging facilities Device Manager DHCP client show routines DHCP client timestamp setup DHCP Core files DHCPv4 boot-time client
INCLUDE_PPP_FRAMEWORK INCLUDE_DEBUG_SHELL_CMD INCLUDE_DEBUG INCLUDE_DEVICE_MANAGER INCLUDE_DHCPC_SHOW INCLUDE_DHCPC_LEASE_GET INCLUDE_DHCP_CORE INCLUDE_DHCPC_BOOT
DHCPv4 client common library DHCPv4 Client Lease Verification/Assignment DHCPv4 client timestamp storage
INCLUDE_DHCPC_SHARE INCLUDE_DHCPC_LEASE_TEST INCLUDE_DHCPC_LEASE_SAVE
DHCPv4 runtime client DNS resolver DNS resolver debug output
INCLUDE_DHCPC INCLUDE_DNS_RESOLVER INCLUDE_DNS_RESOLVER_DEBUG
DOS File System Consistency Checker DOS File System FAT12/16/32 Handler DOS File System Old Directory Format Handler DOS File System VFAT Directory Handler DOS File System Volume Fomatter Module DOS filesystem backward-compatibility dosfs File System Main Module (dosFs2) doubly linked lists ED&R shell commands ED&R show routines enable caches enable guard pages for kernel task stacks enable non-executable kernel task stacks END driver polled statistics support END interface support error status table Ethernet interface support Event Reporting Framework exception handling exception show routines exception task Extended Block Device extended object library
INCLUDE_DOSFS_CHKDSK INCLUDE_DOSFS_FAT INCLUDE_DOSFS_DIR_FIXED INCLUDE_DOSFS_DIR_VFAT INCLUDE_DOSFS_FMT INCLUDE_DOSFS INCLUDE_DOSFS_MAIN INCLUDE_DLL INCLUDE_EDR_SHELL_CMD INCLUDE_EDR_SHOW INCLUDE_CACHE_ENABLE INCLUDE_PROTECT_TASK_STACK INCLUDE_TASK_STACK_NO_EXEC INCLUDE_END_POLLED_STATS INCLUDE_END INCLUDE_STAT_SYM_TBL INCLUDE_ETHERNET INCLUDE_ERF INCLUDE_EXC_HANDLING INCLUDE_EXC_SHOW INCLUDE_EXC_TASK INCLUDE_XBD INCLUDE_OBJ_OPEN
File System and Disk Utilities File System Event Utilities File System Monitor
INCLUDE_DISK_UTIL INCLUDE_FS_EVNET_UTIL INCLUDE_FS_MONITOR
file system shell commands file upload path initialization
INCLUDE_DISK_UTIL_SHELL_CMD 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)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
APPX Appendix 1 VxWorks Component List
- 2
APPENDICES
Table APPX.1 VxWorks component list (continued)
Component floating point show routine
Macro INCLUDE_WH_FP_SHOW
formatted IO formatted output routines fpp formatting for printf FTP client full featured memory allocator General BSP macros get name info get serv by name GNU compiler support routines GTF support gtf_timer_start handle show routines hardware fpp support hash library high resolution timestamping Highly Reliable File System host table Host/target breakpoint synchronization host/target modules and symbols synchronization
INCLUDE_FORMATTED_IO INCLUDE_FORMATTED_OUT_BASIC INCLUDE_FLOATING_POINT INCLUDE_FTP INCLUDE_MEM_MGR_FULL INCLUDE_BSP_MACROS INCLUDE_GETNAMEINFO INCLUDE_GETSERVBYNAME INCLUDE_GNU_INTRINSICS INCLUDE_GTF INCLUDE_GTF_TIMER_START INCLUDE_HANDLE_SHOW INCLUDE_HW_FP INCLUDE_HASH INCLUDE_TIMESTAMP INCLUDE_HRFS INCLUDE_HOST_TBL INCLUDE_WDB_BP_SYNC INCLUDE_WDB_MDL_SYM_SYNC
ICMP show routines*1
INCLUDE_ICMP_SHOW
ICMP v4 IF ifIndex Initialization IGMP v2/v3
INCLUDE_ICMPV4 INCLUDE_IF INCLUDE_IFINDEX INCLUDE_IGMP
Include Protocol Framework*1 inetLib initialize system symbol table IO system IP v4 IPv4 interface address library Job Queue support job task kernel link BufPool
INCLUDE_PROTOCOL_FRAMEWORK
INCLUDE_INETLIB INCLUDE_SYM_TBL_INIT INCLUDE_IO_SYSTEM INCLUDE_IPV4 INCLUDE_IFLIB INCLUDE_JOB_QUEUE INCLUDE_JOB_TASK INCLUDE_KERNEL INCLUDE_LINKBUFPOOL
linked list library logical set library loopback interface support mapped files shell commands md5 memory allocator info routines memory show routine message logging message queue creation and deletion library message queue info routines message queue show routine message queues MIB2 ICMP Management APIs
INCLUDE_LSTLIB INCLUDE_SET INCLUDE_LOOPBACK INCLUDE_MAPPED_FILES_SHOW_SHELL_CMD INCLUDE_NET_MD5 INCLUDE_MEM_MGR_INFO INCLUDE_MEM_SHOW INCLUDE_LOGGING INCLUDE_MESSAGE_Q_CREATE_DELETE INCLUDE_MESSAGE_Q_INFO INCLUDE_MSG_Q_SHOW INCLUDE_MESSAGE_Q 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 - 3 Appendix 1 VxWorks Component List
APPENDICES
Table APPX.1 VxWorks component list (continued)
Component MIB2 TCP Management APIs MIB2 UDP Management APIs MMU global map module manager mutex semaphore creation routine mutex semaphores MUX support netBufLib netBufPool NetDrv for remote IO netstat netstat for IPv4 network boot device configuration Network Daemon Support network device netmask setup Network function binding network init Network interface show routines network remote I/O access Network route show routines Network route show snprintf buffering Network Stack Memory Pool Configuration NETWORK SYSCTL NFS client All NFS server NFS server All NFS server V2 NFS server V3 NFS v2 client NFS v3 client non-blocking message logging object management object management ownership old route persistent error log persistent memory PING client pipes pool allocation library POSIX advisory file locking POSIX AIO driver POSIX asynchronous IO POSIX clocks POSIX directory utilities POSIX ftruncate POSIX Memory Mapped Files for RTPs POSIX message queue show routine POSIX message queues POSIX mman
Macro INCLUDE_MIB2_TCP INCLUDE_MIB2_UDP INCLUDE_MMU_GLOBAL_MAP INCLUDE_MODULE_MANAGER INCLUDE_SEM_MUTEX_CREATE INCLUDE_SEM_MUTEX INCLUDE_MUX INCLUDE_NETBUFLIB INCLUDE_NETBUFPOOL INCLUDE_NET_DRV INCLUDE_NETSTAT INCLUDE_NETSTAT_IPV4 INCLUDE_NET_BOOT_CONFIG INCLUDE_NET_DAEMON INCLUDE_NETMASK_GET INCLUDE_NET_FUNCBIND INCLUDE_NET_INIT INCLUDE_NET_IF_SHOW INCLUDE_NET_REM_IO INCLUDE_NET_ROUTE_SHOW INCLUDE_NET_ROUTE_SHOW_SNPRINTF INCLUDE_NET_POOL INCLUDE_NET_SYSCTL INCLUDE_NFS_CLIENT_ALL INCLUDE_CORE_NFS_SERVER INCLUDE_NFS_SERVER_ALL INCLUDE_NFS2_SERVER INCLUDE_NFS3_SERVER INCLUDE_NFS2_CLIENT INCLUDE_NFS3_CLIENT INCLUDE_NBIO_LOG INCLUDE_OBJ_LIB INCLUDE_OBJ_OWNERSHIP INCLUDE_OLDROUTE INCLUDE_EDR_ERRLOG INCLUDE_EDR_PM INCLUDE_PING INCLUDE_PIPES INCLUDE_POOL INCLUDE_POSIX_ADVISORY_FILE_LOCKING INCLUDE_POSIX_AIO_SYSDRV INCLUDE_POSIX_AIO INCLUDE_POSIX_CLOCKS INCLUDE_POSIX_DIRLIB INCLUDE_POSIX_FTRUNC INCLUDE_POSIX_MAPPED_FILES INCLUDE_POSIX_MQ_SHOW INCLUDE_POSIX_MQ INCLUDE_POSIX_MEM
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
APPX Appendix 1 VxWorks Component List
- 4
APPENDICES
Table APPX.1 VxWorks component list (continued)
Component POSIX process scheduling POSIX PSE52 support for RTPs POSIX scheduling policies SCHED_FIFO/SCHED_RR/ SCHED_OTHER support in RTPs POSIX semaphore POSIX semaphore show routine POSIX Shared Memory Objects POSIX signal POSIX thread CPU-time clock POSIX thread scheduler in RTPs POSIX threads POSIX timers process shell commands process show shell commands Pseudo terminal driver public hostname setup RAM Disk RAM disk driver random raw filesystem RAW v4 rBuff library read the bootline Remote Command Reverse ARP client ring buffers route route_storage Routing Socket RPC RTP RTP Hook Support RTP Show RTP Startup Facility: User-defined code run static initializers select semaphore deletion routines semaphore info routines semaphore show routine SH-4A 32-Bit Address Extended Mode shared data region support in RTPs or kernel Shared Data Show shared data show shell commands shared library commands Shared Library Show shared library support in RTPs shell banner Show routines for memory mapped objects sigevent notification library
Macro INCLUDE_POSIX_SCHED INCLUDE_RTP_POSIX_PSE52
INCLUDE_PX_SCHED_DEF_PLICIES
INCLUDE_POSIX_SEM INCLUDE_POSIX_SEM_SHOW INCLUDE_POSIX_SHM INCLUDE_POSIX_SIGNALS INCLUDE_POSIX_THREAD_CPUTIME INCLUDE_POSIX_PTHREAD_SCHEDULER INCLUDE_POSIX_PTHREADS INCLUDE_POSIX_TIMERS INCLUDE_RTP_SHELL_CMD INCLUDE_RTP_SHOW_SHELL_CMD INCLUDE_PTYDRV INCLUDE_NET_HOST_SETUP INCLUDE_RAM_DISK INCLUDE_RAMDRV INCLUDE_KERN_RANDOM INCLUDE_RAWFS INCLUDE_RAWV4 INCLUDE_RBUFF INCLUDE_BOOT_LINE_INIT INCLUDE_REMLIB INCLUDE_RARP INCLUDE_RING_BUF INCLUDE_ROUTE INCLUDE_ROUTE_STORAGE INCLUDE_ROUTING_SOCKET INCLUDE_RPC INCLUDE_RTP INCLUDE_RTP_HOOKS INCLUDE_RTP_SHOW INCLUDE_RTP_APPL_USER INCLUDE_CTORS_DTORS INCLUDE_SELECT INCLUDE_SEM_DELETE INCLUDE_SEM_INFO INCLUDE_SEM_SHOW INCLUDE_SH4A_EXTENDED_32BIT_SUPPORT INCLUDE_SHARED_DATA INCLUDE_SHARE_DATA_SHOW INCLUDE_SHARED_DATA_SHOW_SHELL_CMD INCLUDE_SHL_SHELL_CMD INCLUDE_SHL_SHOW INCLUDE_SHL INCLUDE_SHELL_BANNER INCLUDE_MAPPED_FILES_SHOW INCLUDE_SIGEVENT
(To the next page)
APPX - 5 Appendix 1 VxWorks Component List
APPENDICES
Table APPX.1 VxWorks component list (continued)
Component signals SIO SNTP client Socket API Socket API System Call support spy Stack/Application Logging Utility stdio stricmp strnicmp Support for reboot hooks symbol shell commands symbol table show routine SYSCTL SYSCTL CLI sysctl System Call System Call Hook Support System clock system debug flag System Viewer class instrumentation System Viewer library system-defined timestamping target loader target loader shell command target symbol table target unloader target-resident kernel shell task hook show routine task hooks task shell commands task show routine task variables TCP v4 Telnet server TELNET/FTP password protection terminal driver terminal driver support TFTP client timex TSFS upload path initialization UDP v4 uipc_domain unix compatible environment variables unloader shell command vi-like editing mode VIO driver virtual memory show shell commands Virtual Root File Sytem VM library show routine
Macro INCLUDE_SIGNALS INCLUDE_SIO INCLUDE_SNTPC INCLUDE_SOCKLIB INCLUDE_SC_SOCKLIB INCLUDE_SPY INCLUDE_APPL_LOG_UTIL INCLUDE_STDIO INCLUDE_STRICMP INCLUDE_STRNICMP INCLUDE_REBOOT_HOOKS INCLUDE_SYM_SHELL_CMD INCLUDE_SYM_TBL_SHOW INCLUDE_SYSCTL INCLUDE_SYSCTL_CLI INCLUDE_SC_SYSCTL INCLUDE_SYSCALL_HOOKS INCLUDE_SYSCLK_INIT INCLUDE_EDR_SYSDBG_FLAG INCLUDE_WINDVIEW_CLASS INCLUDE_WINDVIEW INCLUDE_SYS_TIMESTAMP INCLUDE_LOADER INCLUDE_MODULE_SHELL_CMD INCLUDE_SYM_TBL INCLUDE_UNLOADER INCLUDE_SHELL INCLUDE_TASK_HOOKS_SHOW INCLUDE_TASK_HOOKS INCLUDE_TASK_SHELL_CMD INCLUDE_TASK_SHOW INCLUDE_TASK_VARS INCLUDE_TCPV4 INCLUDE_TELNET INCLUDE_SECURITY INCLUDE_TTY_DEV INCLUDE_TYLIB INCLUDE_TFTP_CLIENT INCLUDE_TIMEX INCLUDE_WVUPLOAD_TSFSSOCK INCLUDE_UDPV4 INCLUDE_DOMAIN_INIT INCLUDE_ENV_VARS INCLUDE_UNLOADER_SHELL_CMD INCLUDE_SHELL_VI_MODE INCLUDE_WDB_VIO INCLUDE_VM_SHOW_SHELL_CMD INCLUDE_VRFS INCLUDE_VM_SHOW
9 10 11 12 13 A I
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
APPX Appendix 1 VxWorks Component List
- 6
APPENDICES
Table APPX.1 VxWorks component list (continued)
Component VxWorks events watchdog timers watchdog timers creation and deletion library WDB agent WDB banner WDB breakpoints WDB call functions WDB callouts WDB eventpoints WDB events WDB exception notification WDB gopher WDB memory access WDB network connection WDB post kernel initialization WDB register access WDB RTP breakpoints WDB RTP control support WDB RTP support WDB target server file system WDB task breakpoints WDB task creation WDB task debugging WDB task exit notification WDB task hooks WDB task registers WDB tasks WDB user event WDB virtual I/O library XBD Block Device XBD Disk Partition Handler XBD Ram Drive XDR
Macro INCLUDE_VXEVENTS INCLUDE_WATCHDOGS INCLUDE_WATCHDOGS_CREATE_DELETE INCLUDE_WDB INCLUDE_WDB_BANNER INCLUDE_WDB_BP INCLUDE_WDB_FUNC_CALL INCLUDE_WDB_DIRECT_CALL INCLUDE_WDB_EVENTPOINTS INCLUDE_WDB_EVENTS INCLUDE_WDB_EXC_NOTIFY INCLUDE_WDB_GOPHER INCLUDE_WDB_MEM INCLUDE_WDB_COMM_NETWORK INCLUDE_WDB_POST_KERNEL_INIT INCLUDE_WDB_REG INCLUDE_WDB_RTP_BP INCLUDE_WDB_RTP_CONTROL INCLUDE_WDB_RTP INCLUDE_WDB_TSFS INCLUDE_WDB_TASK_BP INCLUDE_WDB_START_NOTIFY INCLUDE_WDB_TASK INCLUDE_WDB_EXIT_NOTIFY INCLUDE_WDB_TASK_HOOKS INCLUDE_WDB_TASK_REG INCLUDE_WDB_CTXT INCLUDE_WDB_USER_EVENT INCLUDE_WDB_VIO_LIB INCLUDE_XBD_BLK_DEV INCLUDE_XBD_PART_LIB INCLUDE_XBD_RAMDRV INCLUDE_XDR
APPX - 7 Appendix 1 VxWorks Component List
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 ANSI assert ANSI ctype ANSI locale ANSI math ANSI stdio ANSI stdio extensions ANSI stdlib ANSI string ANSI time API to ARP tables application initialization basic C++ iostreams basic network support binary semaphores BOOT protocol client library BSD 4.4 TCPv4 BSD 4.4. UDPv4 BSD SOCKET BSP hardware initialization BSP Memory Configuration buffer manager built-in symbol table C++ runtime support C++ standard template library C++ string i/o C++ string type C++ symbol demangler cache support CBIO (Cached Block I/O) Support, cbioLib configure the network boot device counting semaphores DHCP client timestamp removal Disk Cache Handler Disk Partition Handler DNS resolver DOS File System Consistency Checker DOS File System FAT12/16/32 Handler DOS File System Old Directory Format Handler DOS File System VFAT Directory Handler DOS File System Volume Formatter DOSFS2 File System Primary Module doubly linked lists
Macro INCLUDE_ANSI_ASSERT INCLUDE_ANSI_CTYPE INCLUDE_ANSI_LOCALE INCLUDE_ANSI_MATH INCLUDE_ANSI_STDIO INCLUDE_ANSI_STDIO_EXTRA INCLUDE_ANSI_STDLIB INCLUDE_ANSI_STRING INCLUDE_ANSI_TIME INCLUDE_ARP_API INCLUDE_USER_APPL INCLUDE_CPLUS_IOSTREAMS INCLUDE_NETWORK INCLUDE_SEM_BINARY INCLUDE_BOOTP INCLUDE_TCP INCLUDE_UDP INCLUDE_BSD_SOCKET INCLUDE_SYSHW_INIT INCLUDE_MEMORY_CONFIG INCLUDE_BUF_MGR INCLUDE_STANDALONE_SYM_TBL INCLUDE_CPLUS INCLUDE_CPLUS_STL INCLUDE_CPLUS_STRING_IO INCLUDE_CPLUS_STRING INCLUDE_CPLUS_DEMANGLER INCLUDE_CACHE_SUPPORT INCLUDE_CBIO INCLUDE_NETDEV_CONFIG INCLUDE_SEM_COUNTING INCLUDE_DHCPC_LEASE_CLEAN INCLUDE_DISK_CACHE INCLUDE_DISK_PART INCLUDE_DNS_RESOLVER INCLUDE_DOSFS_CHKDSK INCLUDE_DOSFS_FAT INCLUDE_DOSFS_DIR_FIXED INCLUDE_DOSFS_DIR_VFAT INCLUDE_DOSFS_FMT INCLUDE_DOSFS_MAIN INCLUDE_DLL
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
APPX Appendix 1 VxWorks Component List
- 8
APPENDICES
Table APPX.2 VxWorks component list (continued)
enable caches
Component
Macro INCLUDE_CACHE_ENABLE
END attach interface END interface support environment variables exception handling exception task file upload path initialization floating point show routine formatted IO fpp formatting for printf full C++ iostreams full featured memory allocator hardware fpp support hash library HOST TBL
INCLUDE_END_BOOT INCLUDE_END INCLUDE_ENV_VARS INCLUDE_EXC_HANDLING INCLUDE_EXC_TASK INCLUDE_WVUPLOAD_FILE INCLUDE_HW_FP_SHOW INCLUDE_FORMATTED_IO INCLUDE_FLOATING_POINT INCLUDE_CPLUS_IOSTREAMS_FULL INCLUDE_MEM_MGR_FULL INCLUDE_HW_FP INCLUDE_HASH INCLUDE_HOST_TBL
ICMP show routines *1 ICMPv4 IGMPv4
INCLUDE_ICMP_SHOW INCLUDE_ICMP INCLUDE_IGMP
initialize network at boot time initialize symbol table IO system
INCLUDE_NET_INIT INCLUDE_SYM_TBL_INIT INCLUDE_IO_SYSTEM
IPv4 kernel loopback driver message logging message queue show routine message queues minimal memory allocator module manager mutex semaphores network buffer initialization network device name selection network device netmask setup network host setup network library support network mux initialization network remote I/O access
INCLUDE_IP INCLUDE_KERNEL INCLUDE_LOOPBACK INCLUDE_LOGGING INCLUDE_MSG_Q_SHOW INCLUDE_MSG_Q INCLUDE_MEM_MGR_BASIC INCLUDE_MODULE_MANAGER INCLUDE_SEM_MUTEX INCLUDE_NET_SETUP INCLUDE_NETDEV_NAMEGET INCLUDE_NETMASK_GET INCLUDE_NET_HOST_SETUP INCLUDE_NET_LIB INCLUDE_MUX INCLUDE_NET_REM_IO
NetWork show routines*1 NFS client NFS mount all NFS server PING client pipes POSIX AIO driver POSIX asynchronous IO POSIX clocks POSIX ftruncate POSIX message queues
INCLUDE_NET_SHOW
INCLUDE_NFS INCLUDE_NFS_MOUNT_ALL INCLUDE_NFS_SERVER INCLUDE_PING INCLUDE_PIPES INCLUDE_POSIX_AIO_SYSDRV INCLUDE_POSIX_AIO INCLUDE_POSIX_CLOCKS INCLUDE_POSIX_FTRUNC INCLUDE_POSIX_MQ
* 1 The following C Controller module cannot be used. · The Q06CCPU-V(-B) with the serial No. (first five digits) "11101" or higher.
(To the next page)
APPX - 9 Appendix 1 VxWorks Component List
APPENDICES
Table APPX.2 VxWorks component list (continued)
POSIX mman
Component
INCLUDE_POSIX_MEM
Macro
POSIX scheduler POSIX semaphores POSIX signals POSIX timers RAM disk driver rBuff library read the bootline Remote Procedure Call system ring buffers RLOGIN/TELNET password protection select sequential timestamping shell banner signals SIO component SNTP client software fpp support stdio symbol table
INCLUDE_POSIX_SCHED INCLUDE_POSIX_SEM INCLUDE_POSIX_SIGNALS INCLUDE_POSIX_TIMERS INCLUDE_RAMDRV INCLUDE_RBUFF INCLUDE_BOOT_LINE_INIT INCLUDE_RPC INCLUDE_RNG_BUF INCLUDE_SECURITY INCLUDE_SELECT INCLUDE_SEQ_TIMESTAMP INCLUDE_SHELL_BANNER INCLUDE_SIGNALS INCLUDE_SIO INCLUDE_SNTPC INCLUDE_SW_FP INCLUDE_STDIO INCLUDE_SYM_TBL
synchronize host and target symbol tables System clock component system startup code target debugging target loader target shell target unloader task hooks task show routine task variables support library
INCLUDE_SYM_TBL_SYNC INCLUDE_SYSCLK_INIT INCLUDE_SYS_START INCLUDE_DEBUG INCLUDE_LOADER INCLUDE_SHELL INCLUDE_UNLOADER INCLUDE_TASK_HOOKS INCLUDE_TASK_SHOW INCLUDE_TASK_VARS
TCP show routines*1 TELNET server terminal driver TFTP client TSFS upload path initialization
INCLUDE_TCP_SHOW INCLUDE_TELNET INCLUDE_TTY_DEV INCLUDE_TFTP_CLIENT INCLUDE_WVUPLOAD_TSFSSOCK
UDP show routines*1 utility to measure function execution time VIO driver
INCLUDE_UDP_SHOW INCLUDE_TIMEX INCLUDE_WDB_VIO
* 1 The following C Controller module cannot be used. · The Q06CCPU-V(-B) with the serial No. (first five digits) "11101" or higher.
(To the next page)
PROGRAMMING USING VxWorks API FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING BUS INTERFACE FUNCTIONS
EVENT NUMBER LIST
SAMPLE PROGRAMS
9 10 11 12 13 A I
APPX Appendix 1 VxWorks Component List
- 10
APPENDICES
Table APPX.2 VxWorks component list (continued)
Component watchdog timers WDB agent WDB banner WDB breakpoints WDB call functions WDB callouts WDB END driver connection WDB eventpoints WDB events WDB exception notification WDB gopher WDB hardware fpp support WDB memory access WDB register access WDB system agent hardware fpp support WDB system debugging WDB target server file system WDB task breakpoints WDB task creation WDB task debugging WDB task exit notification WDB task hardware fpp support WDB tasks WDB user event WDB virtual I/O library windview class instrumentation windview library
Macro INCLUDE_WATCHDOGS INCLUDE_WDB INCLUDE_WDB_BANNER INCLUDE_WDB_BP INCLUDE_WDB_FUNC_CALL INCLUDE_WDB_DIRECT_CALL INCLUDE_WDB_COMM_END INCLUDE_WDB_EVENTPOINTS INCLUDE_WDB_EVENTS INCLUDE_WDB_EXC_NOTIFY INCLUDE_WDB_GOPHER INCLUDE_WDB_HW_FP INCLUDE_WDB_MEM INCLUDE_WDB_REG INCLUDE_WDB_SYS_HW_FP INCLUDE_WDB_SYS INCLUDE_WDB_TSFS INCLUDE_WDB_TASK_BP INCLUDE_WDB_START_NOTIFY INCLUDE_WDB_TASK INCLUDE_WDB_EXIT_NOTIFY INCLUDE_WDB_TASK_HW_FP INCLUDE_WDB_CTXT INCLUDE_WDB_USER_EVENT INCLUDE_WDB_VIO_LIB INCLUDE_WINDVIEW_CLASS INCLUDE_WINDVIEW
APPX - 11 Appendix 1 VxWorks Component List
APPENDICES
9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
(2) VxWorks component information checking method
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
10
the same when CW Workbench is used.
1 Select [Help] [Help Contents] from the menu bar.
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
11
PROGRAMMING USING VxWorks API FUNCTIONS
2 HELP information for Workbench is displayed in a web browser.
12
SAMPLE PROGRAMS
EVENT NUMBER LIST
13 3 Enter the string to be searched in the "Search:" combo box and click the GO button.
4 Select the information to review from "Search Result" and review the component information.
A
(Completed)
I
APPX Appendix 1 VxWorks Component List
- 12
APPENDICES
(b) For the Q06CCPU-V(-B) 1 Select [File] [New Project] from the menu bar.
2 Select "Create a bootable VxWorks image (custom configured)" and click the OK button.
3 Enter "Name", "Location", and "Workspace" and then click the Next> button.
(To the next page)
APPX - 13 Appendix 1 VxWorks Component List
PROGRAMMING USING BUS INTERFACE FUNCTIONS
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
PROGRAMMING USING VxWorks API FUNCTIONS
APPENDICES
9
(From the previous page)
4 Select "A BSP" and click the Next> button.
10
11
5 Check that the values in "Workspace", "Project", and "Basis BSP" are correct and then click the Finish button.
12
13
6 Open the <<VxWorks>> tab of the "Workspace" window.
A
I
(To the next page)
SAMPLE PROGRAMS
EVENT NUMBER LIST
APPX Appendix 1 VxWorks Component List
- 14
APPENDICES
(From the previous page)
7 Click the ( ) icon to expand the items at this level of the hierarchy.
8 Right-click on "ANSI assert" and select [Properties] from the menu.
9 Check the information of VxWorks components with the Properties screen displayed.
(Completed)
APPX - 15 Appendix 1 VxWorks Component List
APPENDICES
9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
Remark The VxWorks components can be located by the following procedure.
1 Right click to select [Find Object] from the menu.
10
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
11
PROGRAMMING USING VxWorks API FUNCTIONS
2 Click the Find button.
12
SAMPLE PROGRAMS
13
EVENT NUMBER LIST
A
I
APPX Appendix 1 VxWorks Component List
- 16
APPENDICES
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).
APPX - 17 Appendix 2 Precautions for Program Replacement
INDEX
9
PROGRAMMING USING BUS INTERFACE FUNCTIONS
[A]
Continuously changing word device values ·····8-10
Activating utility ·············································3-2
Function list··············································· 8-1 Numerical pad ··········································8-16
[B] Basic mode········································· A-24,A-30
Setting device to be monitored ······················ 8-7
Setting monitoring target ······························ 8-6 Start and stop monitoring ····························8-15
10
Bus interface functions ····································9-1
16-point register monitoring ·························· 8-4
Outline······················································9-1 Device Settings Tab······································4-35
PROGRAMMING USING MELSEC DATA LINK FUNCTIONS
[C]
[E]
C Controller setting utility ·································4-1 Exiting utility ················································· 3-3
Communication diagnostics tab ··················· 4-45 Extended mode···································· A-24,A-30
Event history tab ·········································4-4
Function list ···············································4-1 Importing multiple CPU parameters ·············· 4-48
[F]
11
I/O assignment settings tab ························· 4-37 FTP ···························································9-46
PROGRAMMING USING VxWorks API FUNCTIONS
Module information tab·································4-2
Module monitoring tab ······························· 4-13 [G]
Multiple CPU settings tab ··························· 4-41 GX Configurator ···········································4-49
Online operation tab ·································· 4-21 Reading initial setting file ···························· 4-48 [H]
12
SRAM monitoring tab···································4-8 System menu ··········································· 4-46
Help screen·················································3-10
SAMPLE PROGRAMS
System settings tab ··································· 4-30 CC IE Control utility ········································7-1 [I]
Diagnostics result screen······························7-5 Installation ··················································· 2-4
Function list ···············································7-1
Module information tab·································7-2 Online operation tab ·································· 7-20 Parameter settings tab ······························· 7-23 System menu ··········································· 7-37 Target settings tab ···································· 7-34 CC-Link utility················································5-1 Function list ···············································5-1 Module information tab·································5-2 Online operation tab ····································5-9 Other station monitoring tab ··························5-6 Parameter settings tab ······························· 5-11 System menu ··········································· 5-21 Target settings tab ···································· 5-15 Test tab ·················································· 5-18 Channel ····················································· 10-9 Checking version ········································· 3-13 Connection target ··········································3-5
[M]
MELSECNET/H data link function ····················10-1 Accessible ranges and devices ·················· 10-17 Device types ·········································· 10-12 Outline ····················································10-1 Station No. setting ··································· 10-10
MELSECNET/H utility····································· 6-1 Error history monitoring tab ·························· 6-9 Function list··············································· 6-1 Module Information Tab ······························· 6-2 Online operation tab···································6-25 Other station monitoring tab ························6-14 Parameter settings tab ·······························6-27 System menu ···········································6-42 Target settings tab·····································6-39
EVENT NUMBER LIST
13 A I
CPU type ·····················································3-4 [P]
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
[D]
Development environment ·······························2-1 Device monitoring utility ··································8-1
Batch monitoring·········································8-2 Bit device ON/OFF ···································· 8-12 Changing the display format ························ 8-14 Changing word device values ························8-8
[S]
Sample programs ·········································12-1 Opening ··················································12-5
Script file ····················································9-51 Shell display setting
Q06CCPU-V(-B) ·······································9-42 Status bar ···················································3-16
INDEX - 1
[T] Title bar······················································3-16 [U] Uninstallation ··············································2-12 [V] VxWorks image file specification ·····················9-31
Q06CCPU-V(-B) ·······································9-38 Q12DCCPU-V ··········································9-31
INDEX - 2
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. However, if repairs are required onsite at domestic or overseas location, expenses to send an engineer will be solely at the customer's discretion. Mitsubishi shall not be held responsible for any re-commissioning, maintenance, or testing on-site that involves replacement of the failed module. [Gratis Warranty Term] The gratis warranty term of the product shall be for one year after the date of purchase or delivery to a designated place. Note that after manufacture and shipment from Mitsubishi, the maximum distribution period shall be six (6) months, and the longest gratis warranty term after manufacturing shall be eighteen (18) months. The gratis warranty term of repair parts shall not exceed the gratis warranty term before repairs. [Gratis Warranty Range] (1) The range shall be limited to normal use within the usage state, usage methods and usage environment, etc., which
follow the conditions and precautions, etc., given in the instruction manual, user's manual and caution labels on the product. (2) Even within the gratis warranty term, repairs shall be charged for in the following cases. 1. Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure caused
by the user's hardware or software design. 2. Failure caused by unapproved modifications, etc., to the product by the user. 3. When the Mitsubishi product is assembled into a user's device, Failure that could have been avoided if functions
or structures, judged as necessary in the legal safety measures the user's device is subject to or as necessary by industry standards, had been provided. 4. Failure that could have been avoided if consumable parts (battery, backlight, fuse, etc.) designated in the instruction manual had been correctly serviced or replaced. 5. Failure caused by external irresistible forces such as fires or abnormal voltages, and Failure caused by force majeure such as earthquakes, lightning, wind and water damage. 6. Failure caused by reasons unpredictable by scientific technology standards at time of shipment from Mitsubishi. 7. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.
2. Onerous repair term after discontinuation of production
(1) Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is discontinued. Discontinuation of production shall be notified with Mitsubishi Technical Bulletins, etc.
(2) Product supply (including repair parts) is not available after production is discontinued.
3. Overseas service
Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at each FA Center may differ.
4. Exclusion of loss in opportunity and secondary loss from warranty liability
Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation to: (1) Damages caused by any cause found not to be the responsibility of Mitsubishi. (2) Loss in opportunity, lost profits incurred to the user by Failures of Mitsubishi products. (3) Special damages and secondary damages whether foreseeable or not, compensation for accidents, and
compensation for damages to products other than Mitsubishi products. (4) Replacement by the user, maintenance of on-site equipment, start-up test run and other tasks.
5. Changes in product specifications
The specifications given in the catalogs, manuals or technical documents are subject to change without prior notice.
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. Ethernet is a registered trademark of Fuji Xerox Co., Ltd. in Japan CompactFlash is either a registered trademark or a trademark of SanDisk Corporation. Tornado, VxSim, VxWorks, and Wind River are either registered trademarks or trademarks of Wind River Systems, Inc. The company names, system names and product names mentioned in this manual are either registered trademarks or trademarks of their respective companies. In some cases, trademark symbols such as 'TM' or '®' are not specified in this manual.
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.
Specifications subject to change without notice.