Mitsubishi Electric Q12DCCPU-V User manual

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

A- 1
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".
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.
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.

A- 2
[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- 3
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- 4
REVISIONS
*The manual number is given on the bottom left of the back cover.
Print date *Manual number Revision
Jun., 2009 SH(NA)-080767ENG-A First edition
Jan., 2010 SH(NA)-080767ENG-B
SAFETY PRECAUTIONS, Chapter 11
Aug., 2010 SH(NA)-080767ENG-C
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
CONDITIONS OF USE FOR THE PRODUCT, Section 4.8, 12.1
Section 4.8 to 4.13 Section 4.9 to 4.14
Mar., 2011 SH(NA)-080767ENG-D
PRECAUTIONS, Section 9.2, 9.7.1, 9.7.2, Chapter 13
Jul., 2011 SH(NA)-080767ENG-E
PRECAUTIONS, ABOUT MANUALS, GENERIC TERMS AND
ABBREVIATIONS, Section 1.1, 2.1, 9.4.1, 9.6, 12.1, Appendix 1
Dec., 2012 SH(NA)-080767ENG-F
GENERIC TERMS AND ABBREVIATIONS, Section 8.13, 10.3.1, 10.13.2,
10.13.3, 10.13.4
Oct., 2013
SH(NA)-080767ENG-G
ABOUT MANUALS, GENERIC TERMS AND ABBREVIATIONS, Chapter 1,
Appendix 2
PRODUCT ORGANIZATION
Dec., 2013 SH(NA)-080767ENG-H GENERIC TERMS AND ABBREVIATIONS, Section 10.3.2, Section 10.3.3,
Section 10.3.4
Mar., 2014 SH(NA)-080767ENG-I GENERIC TERMS AND ABBREVIATIONS, Section 2.1, Section 10.13.1,
Section 10.13.2, Section 10.13.3, Section 10.13.4
Jul., 2014 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
Partial correction
Partial correction
Addition
Section number
Partial correction
Partial correction
Partial correction
Partial correction
Addition
Partial correction
Partial correction
Partial correction

A- 5
*The manual number is given on the bottom left of the back cover
Japanese manual version SH-080765-O
© 2009 MITSUBISHI ELECTRIC CORPORATION
Print date *Manual number Revision
Jun., 2015 SH(NA)-080767ENG-K
ABOUT MANUALS, Section 10.13.1, Section 10.13.2, Section 10.13.3,
Section 10.13.4
WARRANTY
Dec., 2015 SH(NA)-080767ENG-L PACKING LIST, WARRANTY
Oct., 2017 SH(NA)-080767ENG-M ABOUT MANUALS, GENERIC TERMS AND ABBREVIATIONS, Chapter 1,
Section 2.1
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.
Partial correction
Addition
Partial correction
Partial correction

A- 6
PRECAUTIONS
The following precautions are given in this section.
(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®.
Precautions Reference page
For installation, uninstallation Page A-6
For each utility Page A-6
For programming Page A-7
For debugging a program Page A-11
For using FTP Page A-16
For the Wind River Systems product Page A-16

A- 7
(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- 8
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
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.
Figure A.1 When using Telnet tool on the Q12DCCPU-V
Port numbers being used
in a C Controller module.
Command execution

A- 9
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- 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 Page 12-
1, CHAPTER 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.

A- 11
(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- 12
(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.
* 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
• Setting at the timing of starting C Controller module
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) 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.
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- 13
[Calculation for the Q06CCPU-V(-B)]
The timeout time is determined by the following calculation formula.
[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
• Setting at the timing of starting the C Controller module
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
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.
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- 14
(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- 15
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.
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.
C Controller module Priority
Q12DCCPU-V 1
Q06CCPU-V(-B) 2

A- 16
(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- 17
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
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

A- 18
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