Mitsubishi MELSEC Q Series User manual

A- 1
SAFETY PRECAUTIONS
(Always read these instructions before using this product.)
Before using this product, please read this manual and the relevant manuals introduced in this manual
carefully and pay full attention to safety to handle the product correctly.
The instructions given in this manual are concerned with this product. For the safety instructions of the
programmable controller system, please read the CPU module user's manual.
In this manual, the safety instructions are ranked as "DANGER" and "CAUTION".
Note that the CAUTION level may lead to a serious consequence according to the circumstances.
Always follow the instructions of both levels because they are important to personal safety.
Please keep this manual in a safe place for future reference and also pass this manual on to the end user.
[Design Precautions]
DANGER
Provide a safety circuit outside the C Controller module to ensure that the entire system will operate
safely even if an external power failure or C Controller module failure occurs.
Failure to do so could result in accidents due to erroneous output or operation.
(1) For an emergency stop circuit, protection circuit and interlock circuit that is designed for
incompatible actions such as forward/reverse rotation or for damage prevention such as the
upper/lower limit setting in positioning, any of them must be provided outside the C Controller
module.
(2) When the C Controller module detects the following conditions, it will disable the output (Y) from
the user program and writing to buffer memory in the case of both (a) and (b) and turn off all
outputs for (b).
Whether to hold or clear all the outputs is set by a parameter.
(a) The overcurrent protector or overvoltage protector of the power supply module is activated.
(b) An error such as a watchdog timer error is detected by the self-diagnostic function of the C
Controller module.
If an error occurs in I/O control parts and the C Controller module cannot detect the error, all the
outputs may turn ON.
Provide a fail-safe circuit or a preventive mechanism outside the C Controller module so that
machines will operate safely in such a case. For fail-safe circuit examples, refer to "Chapter 5
SETTINGS AND PROCEDURES BEFORE OPERATION" in this manual.
(3) Output could be left on or off when there is a fault in an output module relay or transistor.
So build an external monitoring circuit that will monitor any output signal that could cause serious
accidents.
DANGER Indicates that incorrect handling may cause hazardous conditions,
resulting in death or severe injury.
CAUTION Indicates that incorrect handling may cause hazardous conditions,
resulting in minor or moderate personal injury or physical damage.

A- 2
[Design Precautions]
DANGER
If load current more than the rating or overcurrent due to a short circuit in the load has flowed in the
output module for a long time, it may cause a fire and smoke. Provide an external safety device
such as a fuse.
Create the circuit so that the external power supply will turn on after the C Controller system is
powered on.
Turning on the external power supply first could result in accidents due to erroneous output or
operation.
For each station's operating status in the event of a each station error, refer to the corresponding
each station manual.
Not doing so could result in erroneous output or operation.
When controlling a running C Controller module (data modification) by connecting a personal
computer to the C Controller module, create an interlock circuit on user programs so that the whole
system functions safely all the time.
This must be also done when performing any other controls (e.g. operating status change (status
control)) or operations instructed from the computer.
In these controls, especially the one performed from an external device to a C Controller module in a
remote location, some C Controller side problem may not be resolved immediately due to failure of
data communications.
To prevent this, create an interlock circuit on user programs and establish corrective procedures for
communication failure between the external device and the C Controller module.
When setting up the system, do not allow any empty slot on the base unit.
If any slot is left empty, be sure to use a blank cover (QG60).
Otherwise, in the short circuit test or when an overcurrent or overvoltage is accidentally applied to
the external I/O section, internal parts of the module may be flied.
CAUTION
Do not install the control wires or communication cables together with the main circuit or power
wires, or bring them close to each other.
Keep a distance of 100 mm (3.94 inch) or more between them.
Not doing so could result in malfunctions due to noise.
When controlling a lamp, heater or solenoid valve using an output module, large current
(approximately ten times greater than in normal conditions) may flow when the output is turned ON
from OFF.
Take preventive measures such as replacing the module with the one having sufficient rated current.

A- 3
[Installation Precautions]
CAUTION
Use the C Controller module in an environment that meets the general specifications shown in this
manual.
Using this C Controller module in an environment outside the range of the general specifications
could result in an electric shock, fire, erroneous operation, and damage to or deterioration of the
product.
While pressing the installation lever located at the bottom of module, insert the module fixing tab into
the fixing hole in the base unit until it stops. Then, mount the module with the fixing hole as a
supporting point.
Incorrect loading of the module can cause a malfunction, failure or drop.
When using the C Controller module in the environment of frequent vibrations, tighten the module
with screws.
Tighten the screws in the specified torque range.
Undertightening can cause a drop, short circuit or malfunction.
Overtightening can cause a drop, short circuit or malfunction due to damage to the screw or module.
Connect extension cables to the connectors of the base unit and the extension module correctly.
After connection, check them for looseness.
Poor contact could cause an input or output failure.
Be sure to set the CompactFlashTM card by pressing it into the CompactFlashTM card slot.
Confirm it is completely set.
Poor contact may lead to malfunctions.
Completely turn off the externally supplied power used in the system before mounting or removing
the module.
Not doing so could result in damage to the product.
Do not directly touch the module's conductive parts.
Doing so could cause an operation failure or give damage to the module.

A- 4
[Wiring Precautions]
DANGER
Completely turn off the externally supplied power used in the system when wiring.
Failure to do so could result in an electric shock or damage to the product.
Before energizing or operating the system after wiring, be sure attach the terminal cover supplied
with the product.
Failure to do so could result in an electric shock.
CAUTION
Be sure to ground the FG and LG terminals to the protective ground conductor.
Not doing so could result in an electric shock or erroneous operation.
Prevent foreign matter such as dust or wiring debris from entering the module.
Failure to do so could cause fires, damage, or erroneous operation.
When wiring, check the rated voltage and terminal layout.
Connecting a power supply of a different voltage rating or incorrect wiring may result in a fire or
failure.
Connect the Ethernet and/or RS-232 cables to the corresponding connectors of the C Controller
module properly.
Tighten the terminal screws with the specified torque.
If the terminal screws are loose, it could result in short circuits, fire or erroneous operation.
Tightening them too much may cause damages to the screws and/or the module, resulting in fallout,
short circuits or malfunction.
Be sure to place the communication and power cables into a duct or fasten them using clamps.
Failure to do so may damage the module or cables by pulling a dangling cable inadvertently or cause
the module to malfunction due to poor contact.
When disconnecting the communication and power cables from the module, do not pull a cable part
by hand.
For a cable with connectors, hold the connector by hand and disconnect it from the module.
Loosen screws on the part connected to the module before disconnecting a cable.
Pulling a cable that is still connected to the module may cause a malfunction or damage the module
or the cable.
Do not connect the outputs of multiple power supply modules in parallel.
Doing so can heat the power supply modules, causing fires or failures.
Crimp, pressure weld, or solder external connectors properly with the tools specified by the maker.
Refer to the I/O Module User's Manual for the tools.
Incomplete connection can cause a short circuit, fire or failure.

A- 5
[Startup and Maintenance Precautions]
DANGER
Do not touch the terminals while power is on.
Doing so may cause an electric shock.
Correctly connect the battery.
Also, do not charge, disassemble, heat, place in fire, short circuit, or solder the battery.
Mishandling of the battery can cause overheating or cracks which could result in injury and/or fires.
Be sure to shut off all phases of the external power supply before retightening the terminal screws
and module fixing screws or cleaning.
Failure to do so may result in an electric shock.
If a terminal screw is loose, it may cause a short circuit or malfunction.
If too tight, it may cause damage to the screws and/or module, resulting in an accidental drop of the
module, short circuit or malfunctions.
When controlling a running C Controller module (data modification) by connecting a personal
computer to the C Controller module, create an interlock circuit on user programs so that the whole
system functions safely all the time.
This must be also done when performing any other controls (e.g. operating status change (status
control)) or operations instructed from the computer.
In these controls, especially the one performed from an external device to a C Controller module in a
remote location, some C Controller side problem may not be resolved immediately due to failure of
data communications.
To prevent this, create an interlock circuit on user programs and establish corrective
procedures for communication failure between the external device and the C Controller module.

A- 6
[Startup and Maintenance Precautions]
CAUTION
Do not disassemble or modify the modules.
Doing so could cause malfunction, erroneous operation, injury, or fire.
Perform online operations connecting peripheral devices to the running C Controller module
(especially program modification, forced output, and operation status change) after reading the
manual carefully and fully ensuring the safety.
Operation mistakes could cause mechanical damage or accidents.
Completely turn off the externally supplied power used in the system before mounting or removing
the module.
Not doing so could result in module failure or malfunction.
Do not mount/remove the module onto/from the base unit more than 50 times
(IEC 61131-2 compliant), after the first use of the product.
Doing so may cause malfunction.
Use any radio communication device such as a cellular phone or a PHS phone more than 25cm
(9.85 inch) away in all directions of the C Controller module.
Not doing so can cause malfunction.
Do not drop or give an impact to the battery installed to the module.
Doing so may damage the battery, causing the battery fluid to leak inside the battery.
If the battery is dropped or given an impact, dispose of it without using.
Before handling the module, touch a grounded metal object to discharge the static electricity from
the human body.
Not doing so can cause the module to fail or malfunction.

A- 7
[Disposal Precautions]
[Transportation Precautions]
CAUTION
When disposing of this product, treat it as industrial waste.
When disposing of batteries, separate them from other wastes according to the local regulations.
(For details of the battery directive in EU member states, refer to Appendix 4.)
CAUTION
When transporting lithium batteries, make sure to treat them based on the transport regulations.
(Refer to Appendix 3 for details of the relevant models.)

A- 8
REVISIONS
*The manual number is given on the bottom left of the back cover.
Print Date *Manual Number Revision
Jun., 2005 SH(NA)-080555ENG-A First edition
Oct., 2005 SH(NA)-080555ENG-B
Precautions for programming, HOW THIS MANUAL IS ORGANIZED,
GENERIC TERMS AND ABBREVIATIONS USED IN THIS MANUAL, Chapter 1,
Section 2.3, 2.4, Section 4.9, 4.12 to 4.14, Section 5.2, 5.6, 5.7.1, 5.7.3, 5.9.1,
Section 6.6.2, Section 9.5.1, Section 10.2.6, 10.3.10, Section 12.1.1, 12.1.4 to
12.1.6, 12.3, Section 13.1, 13.2, 13.4.2, 13.6, 13.7, Section 14.2, 14.3.1, 14.3.2,
Section 15.1, Section 18.2.8, 18.2.10, 18.2.11, 18.3, 18.4.2, INDEX
Section 9.5.10, Appendix 5
Oct., 2006 SH(NA)-080555ENG-C
SAFETY PRECAUTIONS, GENERIC TERMS AND ABBREVIATIONS,
Section 1.1, 2.2.1, 2.2.2, 2.3, 3.3, 4.4.5, 4.5.3, 4.6, 4.7, 5.7.3, 5.7.4, 9.1.6, 9.2,
9.2.1, 9.2.2, 9.2.5, 9.2.7 to 9.2.9, 9.2.11, 9.3, 9.3.2, 9.3.5, 9.3.6, 9.3.8, 9.4, 9.4.2,
9.4.4, 9.4.6 to 9.4.8, 9.5, 9.5.4, 10.2.1, 10.3.11, 10.3.12, 11.1, 12.2.1, 14.2,
17.2.3, 17.2.4, 18.1, 18.2.1 to 18.2.3, 18.2.5 to 18.2.7, 18.2.9, 18.2.10, 18.2.12,
18.3, 18.4.1, 18.4.3, Appendix 1, 2, 5, INDEX
Section 4.3.1, Appendix 6
Nov., 2006 SH(NA)-080555ENG-D
Section 9.2.6, 18.4.1, 18.4.3
Feb., 2007 SH(NA)-080555ENG-E
“PLC” was changed to “programmable controller”.
OPERATING PRECAUTIONS, Section 2.2.2, 10.3.12
Apr., 2007 SH(NA)-080555ENG-F
SAFETY PRECAUTIONS, GENERIC TERMS AND ABBREVIATIONS,
Section 1.1, 2.1.4, 2.1.5, 2.2.1, 2.2.2, 4.1, 4.4, 4.4.1, 4.4.2, 4.4.5, 4.5.1, 4.14,
9.4.7, 10.1, 10.2.5, 11.1, 12.1.1, 12.1.4 to 12.1.6, 14.2, 14.3.3, 18.3,
Appendix 5, 6
Oct., 2007 SH(NA)-080555ENG-G
SAFETY PRECAUTIONS, OPERATING PRECAUTIONS, HOW THIS MANUAL
IS ORGANIZED, GENERIC TERMS AND ABBREVIATIONS, PACKING LIST,
Section 2.1.4, 2.2.1, 2.2.2, 2.3, 3.2, 3.3, 4.5, 4.5.3, 4.5.4, 5.1, 5.2, 5.4, 5.7.4,
5.8.3, 5.10, 5.11.2, 8.1, 8.4, 9.1.3, 9.3.6, 9.4.2, 9.4.7, 10.2.3, 10.2.5, 11.1, 12.2.1,
12.3, 13.1, 14.5, 18.2, 18.4.1, 18.4.3, Appendix 1
Section 18.2.14
Modifications
Additions
Modifications
Additions
Modifications
Change of a term
Modifications
Modifications
Modifications
Additions

A- 9
*The manual number is given on the bottom left of the back cover.
Japanese Manual Version SH-080519-H
2005 MITSUBISHI ELECTRIC CORPORATION
Print Date *Manual Number Revision
Sep., 2008 SH(NA)-080555ENG-H
SAFETY PRECAUTIONS, Section 2.2.1
Appendix 4 Appendix 5, Appendix 5 Appendix 6, Appendix 6 Appendix 7
Appendix 4
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.
Modifications
Change of section No.
Additions
C

A- 10
OPERATING PRECAUTIONS
This section explains precautions in the following order.
1) Precautions for system configuration
2) Precautions for standard ROM and CompactFlash card
3) Precautions for battery
4) Precautions for clock setting
5) Precautions for installation and uninstallation
6) Precautions for each utility
7) Precautions for programming
8) Precautions for program debugging
9) Precautions for use of FTP
(1) Compatible modules
In the system configuration where the C Controller module is used, some main and
extension base units ( Section 2.1.5) are inapplicable, and modules of some
function versions ( Section 2.2) are also not applicable.
(2) Multiple CPU system
(a) Applicable CPU modules
Refer to Section 12.2.1 for the CPU modules that can be used with the C
Controller module in multiple CPU systems.
(b) MT Developer connection in multiple CPU system (For Version 00Y or
earlier)
When a multiple CPU system includes the C Controller module as CPU No.1 and
the Motion CPU, the MT Developer's (Version 00Y or earlier) communication test
cannot be performed.(A Motion CPU communication test error (error
code:12288))will occur.
Perform either of the following for testing the MT Developer's communication.
• Use MT Developer Version 00Z or later.
• When using MT Developer Version 00Y or earlier, CPU No.1 must be a
programmable controller CPU in the multiple CPU system.
(3) Connection with GX Developer
Refer to Section 2.3 (6) for GX Developer connection.
Precautions for system configuration

A- 11
(1) Formatting of standard ROM
(a) When formatting the standard ROM
Be sure to use the method described in Section 5.10 (4)(a).
Do not format it using a command from Shell of Tornado.
(b) While standard ROM is being formatted
Do not power off or reset the C Controller module.
Doing so may result in unusual startup of the C Controller module.
(2) Allowable No. of writes (life) of standard ROM
A Flash ROM is used for the standard ROM and it has a limit in the allowable number
of writes (life). ( Section 5.9)
(3) Allowable No. of writes (life) of CompactFlash card
Refer to the following manual for the allowable number of writes (life) of the
CompactFlash card.
Manual supplied with the CompactFlash card
If the number of writes has exceeded the limit (life), replace the CompactFlash card.
(4) CompactFlash card replacement
While a file is being written to the CompactFlash card, do not turn the power off or
remove the CompactFlash card.
Doing so may cause CompactFlash card data corruption or a file system error.
• When removing the CompactFlash card during file writing: Section 5.8.2
• When turning the power off: Section 7.2.2
(5) Unmounting CompactFlash card by RESET/SELECT switch
(a) Unmounting during access
Unmounting a CompactFlash card by the RESET/SELECT switch while writing a
file to the CompactFlash card may corrupt the CompactFlash card data or cause a
file system error.
In such a case, stop access to the CompactFlash card. ( Section 5.8.2)
(b) When turning power off
Refer to Section 7.2.2 for turning power off.
(c) Switch operation
The C Controller module will be reset if the RESET/SELECT switch is accidentally
held in the RESET position.
Please pay special attention when unmounting the CompactFlash card by
operating the RESET/SELECT switch. ( Section 5.8.3)
Precautions for standard ROM and CompactFlash card

A- 12
(1) File corruption
(a) When battery is not replaced after battery error occurrence
The standard ROM/battery-backed-up RAM data during access or the clock data
may be corrupted, or a file system error may occur.
(b) When shutdown operation is not performed after running without battery
The standard ROM/battery-backed-up RAM data during access or the clock data
may be corrupted, or a file system error may occur.
(c) When steps shown in Section 5.7.4 are not followed
The standard ROM/battery-backed-up RAM data during access or the clock data
may be corrupted, or a file system error may occur.
(2) Restrictions on running without battery
(a) When having been powered on without battery
When the C Controller module has been powered on without a battery, it will start
up with the clock data uncertain.
Be sure to set the clock data since programs using the event history and/or clock
data cannot operate properly under this condition. ( Section 5.7.4)
(b) When having been run without battery
When the C Controller module has been run without a battery, be sure to perform
shutdown operation before powering off the C Controller module. ( Section
5.7.4 (2))
(3) Battery replacement
Always observe the procedures described in the manual when replacing the battery.
( Section 5.7.3 (4))
(1) Clock setting
(a) Setting method
Set the clock of the C Controller module by the operation described in Section 4.8
(4)(a).
If the year exceeds 2100 after the clock setting, the C Controller module can be
used with the clock data of 2100 or later until it is restarted.
At the time of the restart, the year data will be re-set to 2000 - 2099.
(b) Condition for setting
Set the clock of the C Controller module without the QBF_WaitEvent or
QBF_WaitUnitEvent function being executed.
Precautions for battery
Precautions for clock setting

A- 13
(1) Installation
When overwriting the SW PVC-CCPU, install the new one into the folder where the
old one has already been stored.
Installing into any other folder is not allowed.
SW PVC-CCPU of another version cannot be overwritten.
In this case, perform installation after uninstalling already installed SW PVC-CCPU.
(2) Uninstallation
Do not stop the processing during uninstallation.
If uninstallation has been stopped before termination, perform uninstallation again.
If re-uninstallation attempted after the stop is completed unsuccessfully, reinstall the
software and then uninstall it again.
(1) Communication error
In the case of line congestion, a communication error (timeout error) is likely to occur
(monitor is stopped during monitor) on each utility.
If a communication error has occurred, make connection target setting again.
(2) Connection during script file execution
While a script file is being processed (RUN LED is flashing), connection from each
utility to the C Controller module may be disabled.
Connect each utility to the C Controller module after the processing of the script file is
finished.
(3) Exiting Microsoft Windows
Do not exit Microsoft Windows while the C Controller setting utility, CC-Link utility
or MELSECNET/H utility is running.
Exit Microsoft Windows after closing the C Controller setting utility, CC-Link utility
or MELSECNET/H utility.
(4) Parameters
Parameters written from the C Controller setting utility, CC-Link utility or
MELSECNET/H utility to the C Controller module become effective when the C
Controller module is powered off and then on or is reset.
The written parameters are not made effective even if the C Controller module status
is changed from STOP to RUN by remote or switch operation.
Precautions for installation and uninstallation
Precautions for each utility
R R
R R
R R

A- 14
(1) Restrictions on bus interface functions and MELSEC data link functions
(a) Endian format (Memory layout)
The C Controller module uses the endian format (memory layout) of little endian.
Perform programming of the user program in little endian.
(The compiler is set in little endian by selecting "SH7750gnule" in "A toolchain"
when creating a project on Tornado.)
( Section 10.2.3)
(b) User program execution
Execute the user program by starting a task from a script file.
( Section 10.2.8)
The system may malfunction if the user program is executed without a task being
started.
(c) Execution task priority
Set the priority of the task that executes the user program as described below.
1) When FTP access is not made during user program execution
Set the priority of the user program task to 100 or higher (100 to 255).
If the priority is set to 0 to 99, the system may not operate properly.
2) When FTP access is made during user program execution
The actual FTP processing (task) of the C Controller module is performed at
the priority of 200.
When making FTP access during user program execution, perform
programming as described below.
• Set the priority of the user program task to 201 to 255.
• When setting the priority of the user program task to 100 to 200, insert wait
processing (such as taskDelay) in the user program to enable the actual FTP
processing.
(d) Ethernet communications from user program
The port numbers 20756, 21012, and 21268 are not applicable.
(e) File writing from user program
Do not write files to the standard ROM.
Write data to the files such as CompactFlash card and network device (FTP/NFS/
netDrv driver, etc.).
For details of network device, refer to the manual for VxWorks.
(f) When operation status changes from RUN to STOP/PAUSE
When the operation status of the C Controller module changes from RUN to
STOP/PAUSE, the user program task does not stop.
Use the QBF_ReadStatusEx function when changing the user program
processing based on the operation status of the C Controller module.
Precautions for programming

A- 15
(g) Relations between Tornado, system watchdog timer and user watchdog
timer
When using Browser's Spy Chart function or Wind Power tool (e.g. WindView) in
Tornado environment, set a sufficiently long time to the system watchdog timer
and user watchdog timer.
Since using Browser's Spy Chart function or Wind Power tool (e.g. WindView)
activates tasks of high CPU utilization, a system watchdog timer error and user
watchdog timer error tend to occur.
(h) Common restrictions
Refer to Section 10.2.5 for the restrictions common to the bus interface functions
and MELSEC data link functions.
(2) Restrictions on bus interface functions
(a) Clock setting
Set the clock of the C Controller module without the QBF_WaitEvent or
QBF_WaitUnitEvent function being executed.
(b) 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 user program operation is a STOP/
PAUSE error.
• 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
monitor>> tab of the C Controller setting utility.
(c) Restrictions on bus interfaces
Refer to Section 10.2.4.
(3) Restrictions on MELSEC data link functions
Perform the open/close (mdOpen/mdClose function) processing of the
communication line only once at the beginning (task start) and end (task end) of a
program task.
Communication performance will decrease if open/close is repeated at each
communication.
Refer to Section 10.3.4 for the restrictions on the MELSEC data link functions.
(4) Login user
(a) Default account
Delete the default account (user name and password) with the loginUserDelete
function to prevent illegal access.
(b) Retention of set login user information
The set login user information is cleared and returns to the default when the C
Controller module is powered off or reset.
To hold the login user setting, describe a script file from which the login user
setting will be registered (added/deleted). ( Section 5.11)
Describe either of the following in the script file.
• Directly describe the login user operation commands (loginUserAdd and/or
loginUserDelete functions)
• Describe the procedure for starting the user program task for login user
operation.

A- 16
(5) Power off (including reset) during file operation
If the C Controller system is powered off or reset (remote RESET included) while a
user file within the standard ROM or CompactFlash card is being written, data
corruption or a file system error may occur.
In this case, execute the following before powering off or resetting the system.
(a) When a file in the standard ROM is being written
Close the file.
(b) When a file in CompactFlash card is being written
Close the file, and unmount the CompactFlash card. ( Section 5.8.2, 5.8.3)
(6) Watchdog timer
(a) Application of user watchdog timer
Use the user watchdog timer to check the hardware and user program for
runaway and processing timeout when accessing or controlling modules through
the user program.
(b) When user watchdog timer cannot be reset
If the user watchdog timer cannot be reset due to some reason such as user
program runaway, a user watchdog timer error will occur.
(c) Watchdog timer setting range
The user watchdog timer setting can be changed within the range of 100ms to
10000ms (unit: 10ms).
The system watchdog timer setting can be changed within the range of 20ms to
2000ms (unit: 10ms).
(7) IP address
The IP address of the C Controller module cannot be set from the user program.
Set it on the <<Online operation>> tab of the C Controller setting utility.
(8) Script file "STARTUP.CMD"
In the script file, describe the login user setting commands (add/change) or the
procedure for starting user program task as necessary. ( Section 5.11, 10.2.8)

A- 17
(1) VxWorks image file
When debugging the user program with Tornado in the development environment
(personal computer) connected to the C Controller module, it is necessary to specify
the VxWorks image file "vxWorks_XXXXX-Y" whose function version is identical with
the first five digits of the C Controller module's serial No.
(a) Confirmation before debugging
When debugging the user program using Tornado, make sure that the VxWorks
image files in the system memories of the development environment (personal
computer) and C Controller module are matched. ( Section 10.2.2, Section
10.2.6(1)(b))
(b) When VxWorks image files are not matched
When the VxWorks image files in the development environment (personal
computer) and C Controller module are not matched, copy the VxWorks image file
from the system drive (/SYSTEM/OS_IMAGEFILE) of the C Controller module to
the development environment (personal computer) using FTP.
( Section 10.2.7)
(c) If connection is made with different VxWorks image files specified
If connection is made with different VxWorks image files specified, a system
watchdog timer error may occur in the C Controller module.
In addition, normal debugging cannot be done. ( Section 10.2.6)
(2) Precautions for executing Shell command from Shell of Tornado or from
Telnet tool
(a) When executing Shell command from Shell of Tornado
In the case of the Shell command execution from Shell of Tornado, the entered
Shell command runs on the task of Priority 1 in the C Controller module.
Since a system error/stop (such as a system watchdog timer error) may occur in
the C Controller module depending on the entered command (example: command
that occupies CPU processing), special care must be taken to the entered
command. ( Section 10.2.6)
(b) When executing Shell command from Telnet tool
When executing the Shell command from the Telnet tool, make one-to-one
connection between the Telnet tool and the C Controller module.
Connections from multiple Telnet tools to the same C Controller module are not
allowed. ( Section 4.16)
A Shell command entered with the Telnet tool in the development environment
(personal computer) runs on the task of Priority 2 in the C Controller module.
Since a system error/stop (e.g. a system watchdog timer error) may occur in the C
Controller module depending on the entered command (example: command that
occupies CPU processing), special care must be taken to the entered command.
( Section 10.2.6)
Precautions for program debugging

A- 18
(c) Execution of VxWorks reboot command
Do not reboot VxWorks by executing the reboot function or pressing the CTRL + X
keys.
If VxWorks is rebooted, the C Controller module does not start up properly.
Reset it on the C Controller module. ( Section 4.5.3, 13.6)
(d) Command execution without argument specified
If a command having an argument was executed with no argument specified, it
means that the command was executed with 0 specified as the argument.
Depending on the command executed, a system error/stop (e.g. a system
watchdog timer error) may occur in the C Controller module.
Before executing a command, be sure to confirm the command specifications and
its argument.
Example) Do not execute the "close" command without an argument specified.
Doing so will close the resource reserved in the VxWorks system.
(1) File reading from the C Controller module
If many files are read (downloaded) at once from the C Controller module by FTP,
a 426 (Data connection error) error may occur.
In that case, take following actions and read files again.
• Reduce the number of files to be read.
• Read the files not at once but several times.
Precautions for use of FTP