(Always read these instructions before using this equipment.)
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 "
!
WARNING
!
CAUTION
!
Note that the
Always follow the instructions of both levels because they are important to personal safety.
Please save this manual to make it accessible when required and always forward it to the end user.
CAUTION level may lead to a serious consequence according to the circumstances.
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.
[Design Instructions]
!
WARNING" and "!CAUTION".
!
WARNING
• When performing data changes or status control from the personal computer to the running CPU
module, configure up an interlock circuit outside the CPU module system to ensure that the
whole system will operate safely.
In addition, predetermine corrective actions for the system so that you can take measures
against any communication error caused by a cable connection fault or the like in online
operations performed from the peripheral device to the CPU module.
!
CAUTION
• Read the manual carefully before performing the online operations (especially forced output and
operating status change) which will be executed with the personal computer connected to the
running CPU module.
Not doing so can damage the machine or cause an accident due to incorrect operation.
A - 1 A - 1
• CONDITIONS OF USE FOR THE PRODUCT •
(1) Mitsubishi programmable controller ("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;
y 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.
y 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.
y 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 - 2 A - 2
REVISIONS
* The manual number is given on the bottom left of the back cover.
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.
4) Instructions for the use of other MELSOFT products
5) Instructions for the use of Ethernet modules
6) Instructions for the use of CC-Link modules
7) Instructions for the use of MELSECNET(II), MELSECNET/10 and MELSECNET/H
8) Instructions for the use of computer link and serial communication modules
9) Instructions for modem communication
10) Instructions for programming
11) Instructions for the use of Microsoft
12) Instructions for the use of Microsoft
13) Instructions for the use of VBScript and ASP function
R
Excel
R
Access
Instructions for used OS and personal computer
(1) When using Microsoft
Microsoft
Windows
R
WindowsR2000 Professional Operating System,
R
XP, Windows VistaRor WindowsR7
Note that the following restrictions apply when a user without Administrator’s
authority operates MX Component.
(a) Communication Setup Utility
• The logical station number cannot be created, changed or deleted.
• Target settings cannot be imported.
• This utility cannot be started up if the communication settings have been
made using MX Component earlier than Version 3.00A. *1
(b) PLC Monitor Utility
• This utility cannot be started up if the communication settings have been
made using MX Component earlier than Version 3.00A. *1
• Device registration cannot be performed on "Entry Device" tab.
(c) Communication board
• Various settings cannot be made on the CC-Link IE Controller Network,
MELSECNET/H, MELSECNET/10, MELSECNET(II), CC-Link, AF and
CPU board utilities.
*1: If the following error message appears, start up and close the utility as a user
with Administrator’s authority, once. This operation enables a user without
Administrator’s authority to start up the utility.
R
Windows NTRWorkstation Operating System Version 4.0,
(2) About Ethernet communication, computer link communication and CPU COM
communication on Microsoft
R
WindowsR95 Operating System
(a) Making Ethernet communication using TCP/IP and UDP/IP on Windows
of the version older than OSR2 will cause a memory leak. When performing
continuous operation on Windows
R
95, use WindowsR95 OSR2 or later.
A - 7 A - 7
R
95
(b) On Windows
R
95, communication using the COM port, e.g. computer link
communication or CPU COM communication, will cause a memory leak.
Therefore, do not perform continuous operation.
(3) Precautions for the use of Microsoft
R
WindowsRMillennium Edition Operating
System
It is not recommended to use MX Component with the "system restoring function"
made invalid by the operating system.
If the free space of the system drive becomes less than 200MB, the "system
restoring function" is made invalid by the operating system. When using
Windows
R
Me, reserve a 200MB or more free space for the system drive.
(4) About the resume and other functions of personal computer
A communications error may occur if communications are made with the
programmable controller CPU after setting the resume function, suspend setting,
power-saving function and/or standby mode of the personal computer.
Therefore, do not set the above functions when making communications with the
programmable controller CPU.
(5) Restrictions by DEP (Data Execution Prevention)
Note that restrictions by DEP may apply when using Windows
Service Pack2 or later, Windows Vista
R
or WindowsR7.
R
XP
For details, refer to "Appendix 9 Restrictions by DEP function".
Instructions for installation and uninstallation
(1) About installation
(a) When performing overwrite installation, install the software in the folder where
it had already been installed.
(b) If you install the MELSEC board driver or GX Developer into the personal
computer where MX Component has already been installed, communication
using a specific path (e.g. ASCII packet of the AJ71E71) may result in a
receive, device number or other error.
If any of these phenomena has occurred, perform overwrite installation of MX
Component again.
(2) Precautions for performing installation and uninstallation on a dual boot machine
where two different operating systems are installed in a single IBM-PC/AT
compatible personal computer
On a dual boot machine having Windows NT
to as OS1) and Windows
the following points when MX Component was installed on OS1 first and MX
Component was then installed over the same folder on OS2.
(a) If MX Component is uninstalled first on the OS2 side, uninstallation does not
delete the control DLLs and ACT folders, and they remain within the IBMPC/AT compatible.
To delete the control DLLs and ACT folders, perform uninstallation also on
the OS1 side.
R
R
95 or WindowsR98 (hereafter referred to as OS2), note
Workstation 4.0 (hereafter referred
A - 8 A - 8
(b) If MX Component is uninstalled first on the OS1 side, the control DLLs and
ACT folders are deleted.
In this case, MX Component may not operate properly or cannot be
uninstalled on the OS2 side.
Install MX Component again on the OS2 side to operate MX Component
properly or uninstall it on the OS2 side.
(3) About start menu
When you have uninstalled MX Component, the item may remain in the start
menu.
In that case, restart the IBM-PC/AT compatible personal computer.
Programmable controller CPU-related instructions
(1) About transmission speed
As the transmission speed of the QCPU(Q mode), LCPU and QCPU(A mode),
you can set 9600bps, 19200bps, 38400bps, 57600bps or 11520bps.
For the QnACPU of version 9707B or later, you can set the transmission speed of
9600bps, 19200bps or 38400bps.
For the QnACPU of other versions, you can set 9600bps or 19200bps.
The transmission speeds of the ACPU (except A2USHCPU-S1), FXCPU and
motion controller CPU are fixed to 9600bps. (The A2USHCPU-S1 may be set to
19200bps.)
(2) Precautions for USB communication
Frequently disconnecting/reconnecting the USB cable or resetting or powering
ON/OFF the programmable controller CPU during communications with the
programmable controller CPU may cause a communications error which cannot
be recovered.
If it is not recovered, completely disconnect the USB cable once and then
reconnect it after 5 or more seconds have elapsed.
(If this error occurs at the initial communication after the above operation, the
function will be performed properly in and after the second communications.)
(3) About clock data of the programmable controller CPU
(a) For the ACPU (including the motion controller CPU), clock data setting may
be made only when the programmable controller CPU is in the STOP status.
For the QCPU (Q mode), LCPU, QCPU (A mode), QnACPU and FXCPU,
clock data setting may be made if the programmable controller CPU is in the
RUN status.
(b) For the A0J2HCPU, A2CCPU and A2CJCPU, setting cannot be made as
they do not have the clock function.
(c) For the ACPU, setting can be made independently of whether the clock
setting special relay "M9028" is ON or OFF. (Note that the special relay
"M9028" turns OFF after execution.)
For the QCPU (Q mode), LCPU, QCPU (A mode) and QnACPU, setting can
be made independently of whether the clock setting device "SM1028" is ON
or OFF.
(d) Among the FXCPUs, setting may be made for only the FX
FX
RTC cassette is fitted), FX
cassette is fitted) and FX
(e) Note that an error for transfer time will be produced in clock setting.
1N (clock built-in),
U (when RTC cassette is fitted), FX2C (when RTC
3G (clock built-in).
A - 9 A - 9
(4) Precautions for the use of Q4ARCPU
The redundant function cannot be used.
(5) Restrictions on use of the FXCPU
(a) When the FXCPU is used, access to the TN devices (timer present values) or
CN devices (counter present values) is not permitted if the device numbers
specified are split across 199 or earlier and 200 or later.
(b) As the FXCPU does not have a PAUSE switch as the programmable
controller CPU, an error is returned if remote pause is specified in
SetCpuStatus.
(c) Note that specifying the first I/O number of a non-existing module and
executing the WriteBuffer( ) method will not return an error.
(d) For the index registers (Z, V) of the FXCPU, data cannot be written to 2 or
more consecutive points using WriteDeviceBlock(). (Data may be written to
only one point.)
(6) Serial communication function of Q00UJ/Q00/Q00U/Q01/Q01U/Q02U/CPU*1
When the following conditions are all satisfied, communication between the
personal computer and the serial communication function compatible CPU is
made at 9600bps speed.
*1: In this paragraph, "serial communication function compatible CPU" indicates
Q00UJ/Q00/Q00U/Q01/Q01U/Q02UCPU.
1) The serial communication function of the connected CPU is valid.
2) The personal computer side transmission speed setting differs from the serial
communication function compatible CPU side transmission speed setting.
To increase the communication speed, match the personal computer side
transmission speed with the serial communication function compatible CPU side
transmission speed.
(7) Precautions for the use of Built-in Ethernet port CPU
If you reset the programmable controller CPU during TCP/IP connection setting
(during opening) using MX Component, a communication or receive error will
occur at the time of communication after that. In that case, close the application
that uses MX Component and then perform open processing again.
(8) Precautions for the use of QSCPU
In order to protect the safety programmable controller system, functions writing to
buffer memory, writing and setting devices and writing clock data cannot be
executed.
Instructions for use of other MELSOFT products
(1) About simultaneous use of MX Component and GX Developer
When using GX Developer and MX Component together for the same E71
module to make Ethernet communication, make the following settings.
(a) Set the protocol of the communication setting wizard screen to "UDP/IP".
(b) Set "SW2" of the communications setting switches of the E71 module to OFF
(binary).
A - 10 A - 10
(2) Precautions for GX Simulator communication
Before executing the monitor utility, communication setting utility or user program,
make sure that GX Simulator and GX Developer are operating.
In addition, do not terminate the GX Simulator and GX Developer while the user
program is running.
If you do so, you will not be able to terminate the user program normally.
Instructions for use of Ethernet modules
(1) Resetting the programmable controller CPU during TCP/IP connection
establishment
When resetting the programmable controller CPU during TCP/IP connection
establishment (during opening) using MX Component, a communication error or
receive error occurs at communication after that. In that case, perform close
processing in the application that uses MX Component and then perform open
processing again.
(2) About target existence check starting interval*1 of Ethernet module
If close processing (Close) is executed from the IBM-PC/AT compatible, the
Ethernet module may not perform close processing (Close).
One of its causes is the open cable.
If open processing (Open) is executed from the IBM-PC/AT compatible with the
Ethernet module not performing close processing (Close), open processing
(Open) from the IBM-PC/AT compatible is not terminated normally until the
Ethernet module makes a target existence check and executes close processing
(Close).
If you want to terminate open processing (Open) early from the IBM-PC/AT
compatible, shorten the target existence check starting interval setting of the
Ethernet module.
(The target existence check starting interval setting of the Ethernet module
defaults to 10 minutes.)
*1: It can be set for the E71 of AJ71E71-S3 or later.
(3) Replacement of Ethernet module
If you changed the Ethernet module during Ethernet communication due to
debugging, failure or like, the other node (IBM-PC/AT compatible) must be
restarted.
(Since the Ethernet addresses (MAC addresses) differ between devices)
(4) Simultaneous access when using Q series-compatible Ethernet module
The following conditions should be satisfied when communication is to be made
simultaneously from multiple IBM-PC/AT compatibles to the same module using
the TCP/IP protocol.
• Q series-compatible E71 module (except QJ71E71-100) whose first five digits of
the serial number is "02122" or later and whose function version is B or later.
• Using GX Developer Version 6.05F or later, set "MELSOFT connection" in the
Ethernet parameter [open system].
A - 11 A - 11
(5) Unlocking password when using QJ71E71
The range where the password can be unlocked by remote operation is up to the
connection target station.
If the password is set also on the lower layer, communication cannot be made
with the programmable controller CPU on the lower layer.
Enter password to
unlock.
AAAA
Ethernet
Remote Password
No.
1)
With setting (AAAA)
2)
Without setting
3)
With setting (AAAA)
4)
With setting (BBBB)
5)
Without setting
QCPU
(Q
mode)
1)
QJ71
E71
Starting
source
2)
QJ71
E71
QCPU
(Q
mode)
Ethernet
4)
3)
QJ71
E71
QCPU
QJ71
(Q
E71
mode)
1) Unlocking QJ71E71 password enables
access to Programmable controller CPUs in this range.
QCPU
(Q
mode)
5)
QJ71
E71
: Accessible
: Inaccessible
(6) About use of the Q4ARCPU
When using the UDP/IP protocol of Ethernet communication, use the Q4ARCPU
whose year and month of manufacture is "0012" or later and whose function
version is B or later.
(7) About Ethernet communication
(a) When access is made to the QnACPU, AnUCPU, QCPU (A mode) or motion
controller CPU via the E71, the device range is equivalent to that of the
AnACPU.
(b) When making access to the programmable controller CPU through Ethernet
communication, the functions may not be executed depending on the
programmable controller CPU status.
1) When the protocol is TCP/IP (target module: E71, QE71)
The functions can be executed only when the communication target
programmable controller CPU is in the RUN mode.
An error is returned if the programmable controller CPU is in other than
the RUN mode.
2) When the protocol is UDP/IP (target module: E71, QE71)
The functions cannot be executed until the communication target
programmable controller CPU is RUN once.
An error is returned if the programmable controller CPU has not been
RUN once.
(c) The communication line is broken if the CPU becomes faulty or the Ethernet
module is reset during Ethernet communication (when the protocol is TCP/IP).
In that case, perform line close processing (Close) and then execute reopen
processing (Open).
A - 12 A - 12
(d) When two different communication systems (protocols) are used to make
access from one IBM-PC/AT compatible to one Q series-compatible E71, two
station numbers, i.e. for TCP/IP and for UDP/IP, must be set. However, it is
not required to set different station numbers for TCP/IP and UDP/IP when
using MX Component Version 3 or later and Q series-compatible E71 with
serial No. 05051 or later.
(Example) When MX Component uses TCP/IP and GX Developer uses
UDP/IP
IBM-PC/AT compatible
(TCP/IP) station number for MX Component: 2
(UDP/IP) station number for GX Developer : 3
GX Developer(UDP/IP)
MX Component(TCP/IP)
Set different station numbers as the (TCP/IP) station number for MX Component
and (UDP/IP) station number for GX Developer. If they are set to the same station
number, an error will occur on the Ethernet module side.
Q series-compatible E71
(Station number: 1)
(8) About switch settings of E71 and QE71
If the four lower digits of the error code that occurred during Ethernet
communication using the E71 or QE71 is not indicated in the E71 or QE71 manual,
check the DIP switch (SW2) setting of the E71 or QE71.
If the DIP switch is not set correctly, a difference has occurred in the packet format
(ASCII/binary) and therefore the error code returned from the module cannot be
recognized correctly.
Instructions for use of CC-Link modules
(1) Software version of CC-Link master/local module
As the CC-Link master/local module used in CC-Link communication or CC-Link
G4 communication (only when the AJ65BT-G4 is used), use the module of
software version "N" or later.
The module of software version "M" or earlier will not operate properly.
(2) Software version of CC-Link G4 module
As the CC-Link G4 module used in CC-Link G4 communication (only when the
AJ65BT-G4 is used), use the module of software version "D" or later.
The module of software version "C" or earlier will not operate properly.
A - 13 A - 13
Instructions for the use of MELSECNET(II), MELSECNET/10 and MELSECNET/H
(1) About relaying from the MELSECNET/10 loaded station
When the module is loaded to the AnNCPU or AnACPU, it is recognized as a
MELSECNET(II) module.
When the connected station is the AnNCPU or AnACPU, set the relayed network
as MELSECNET(II).
In addition, set the station number to "0" when making access to the control
station.
(2) Instructions for relaying the MELSECNET(II)
When access is made to the QnACPU, AnUCPU, QCPU (A mode) or motion
controller CPU via the MELSECNET(II), the device range is equivalent to that of
the AnACPU.
Instructions for use of computer link and serial communication modules
(1) About computer link communication
(a) If the connected station CPU is the AnUCPU and the computer link module is
the UC24 for computer link connection, remote operation will result in an error
when access is made to the AnNCPU, AnACPU or QnACPU via the
MELSECNET/10.
(b) On any computer link modules other than the UC24 and C24, remote
"PAUSE" operation will result in an error for all connections.
(c) For the QC24, note that the illegal case of specifying the first I/O number of a
non-existing module and reading/writing U
software version of the module is "k" or earlier.
(d) In any connection form (direct coupling, relaying) where the target station of
the UC24 or C24 is the QnACPU, an error is returned if clock data read/write
is executed.
(e) The FX extended port is required when performing the computer link
communication using FX
0N, FX1S, FX1N(C), FX3G, FX3U(C)CPU.
(2) Precautions for connecting personal computer and serial communication module
(a) When QJ71C24-R2 of function version A is used
An MX Component application can use only either of CH1 and CH2.
When the MELSOFT product, such as GX Developer or GOT, is using one
channel, the application cannot use the other channel.
When the QJ71C24-R2 of function version B is used, the application can use
both channels.
(b) When AJ71QC24-R2 or A1SJ71QC4-R2 or AJ71QC24N-R2 or
A1SJ71QC24N-R2 is used
The MX Component application can use only CH1.
It cannot use CH2.
\G will not return an error if the
A - 14 A - 14
Instructions for modem communication
(1) Simultaneous modem communications
It is not allowed to simultaneously perform modem communications using MX
Component and other application such as GX Developer.
Do not perform a modem communication using other applications during a modem
communication using MX Component.
If modem communications are simultaneously performed using MX Component
and other application, this will result in a communication error, disconnection of
telephone line or similar problem.
(2) Instructions for the use of telephone line
(a) Do not use the call-waiting phone line.
On the call-waiting phone line, data corruption, telephone line disconnection
or similar may occur due to interrupt reading sounds.
(b) Do not connect the line to master/slave phones.
If the handset of the slave phone is lifted while the telephone line is
connecting to the master/slave phones, the telephone line may be
disconnected.
(c) Use an analog 2 wire type telephone line.
When using a digital line, use a terminal adaptor.
When the telephone line is of 4 wire type, the line may not be connected
depending on the wiring type of the modular jack.
For the 4 wire type, conduct connection tests in advance to check for
connection.
(3) Instructions for the use of cellular phone
(a) Modem for radio communication using a cellular phone
Although the modem name is different depending on the maker, the modem
is generically referred to as the cellular phone communication unit in this
manual.
Select the model of the cellular phone communication unit according to the
cellular phone used.
For details, contact the company of your cellular phone.
(b) Cellular phone without auto answer function
For the cellular phone without auto answer function, use a cellular phone
communication unit that has the ANS/ORG/TEL select switch.
If the cellular phone communication unit does not have the ANS/ORG/TEL
select switch, it is impossible to connect the line.
The line connection procedure is different depending on the cellular phone
company and cellular phone model.
For details, contact the maker of your cellular phone.
A - 15 A - 15
Instructions for programming
(1) About sample programs, test programs and sample sequence programs
(2) About forced termination of processes during communication
(3) About error at communication start
(4) CheckDeviceString
(5) About ActUMsg control, ActUWzd control, ActMnet2BD control and ActAFBD
(6) Precautions for the use of Act(ML)QJ71E71TCP, Act(ML)AJ71QE71TCP and
(7) Instructions for execution of Disconnect
(a) Sample programs, test programs
The sample programs are attached for your reference to create user
programs.
The test programs are attached to conduct communication tests.
Use these programs on your own responsibility.
(b) Sample sequence programs
The sample sequence programs attached to MX Component must be
modified depending on the system configuration and parameter settings.
Modify them to be best for the system.
Please note that it is user’s responsibility to use the same sequence
programs.
If communication is being made with the same type of control open for multiple
processes, forcing one process to be terminated by Task Manager or the like may
stop the other processes at the communication function execution area.
A communication error may occur within the preset time-out period at a
communication start, e.g. when the communication diagnostic button is pressed,
at a monitor start, or at the execution of any function.
These errors are assumed to be detected before a time-out error.
(Example: Connection cable not connected, at programmable controller power-off)
Do not use the CheckDeviceString method of each ACT control.
control
Installing MX Component registers the ActUMsg control, ActUWzd control,
ActMnet2BD control and ActAFBD control, but do not use them.
Act(ML)AJ71E71TCP controls
(a) Provide an interval longer than the sequence scan time of the Ethernet
module loaded station from when the Open method is executed until the
Close method is executed.
(b) Provide an interval of at least 500ms from when the Close method is
executed until the Open method is executed again.
If execution of Disconnect cannot disconnect the telephone line for some reason,
power off the modem used to make a call to forcibly disconnect the telephone line.
A - 16 A - 16
Instructions for use of Microsoft
(1) Precautions for starting multiple Excel files on Windows
Note that Windows
which use many control objects.
* This phenomenon is not attributable to this product.
(a) Conditions on which this phenomenon has been confirmed to occur
(b) Cause
(c) How to judge whether the phenomenon is the same or not
(d) Corrective action
(2) Precautions for the use of EXCEL VBA
Do not set the page feed preview function in the application that uses EXCEL VBA.
Doing so can cause a memory leak or OS basic operation (file operation, printing
or other) fault.
(3) Precautions for the use of Microsoft
(a) If you paste the control to Excel, it may sometimes not be pasted.
(b) Excel allows ACT control resizing, which does not affect the operation of MX
R
Excel
R
R
Me has been confirmed to stop if you run multiple Excel files
Graphic driver : Matrox make MGA Mystique display driver
OS : Windows
R
Me (English version)
Me
Number of controls pasted to Excel files
: A total of 150 or more controls used in the whole BOOK
<Other devices checked by Mitsubishi (reference)>
CPU : Pentium
R
166MHz
Memory : 64MB
Hard disk : 8GB (free space 6GB)
The phenomenon has been confirmed to occur when the Matrox make MGA
Mystique graphic card display driver is used.
This is because Version 4.12 of the MGA Mystique graphic card display driver
is not compatible with Windows
R
Me.
After changing the used graphic driver for the standard VGA driver, delete the
temporary data (*.emf) left in the temporary folder.
After that, try starting multiple Excel files.
The phenomenon seems to be the same if it does not occur by changing the
driver for the standard VGA driver.
If this phenomenon occurs, the temporary data (*.emf) will be left in the
temporary folder of the system.
You have to delete the remaining temporary data (*.emf) manually.
The temporary folder of the system is normally in "C:\Temp".
After that, take either of the following actions.
1) Use the graphic card and display driver which support Windows
R
Me.
2) Reduce the number of control objects pasted to the Excel files.
R
Excel
This phenomenon occurs if the cache file (temporary file) of Excel remains.
In such a case, perform operation in the following procedure.
1) Close Excel.
2) Delete "*.exd" in the Excel 8.0 folder of the temp folders. *1, *2
3) Restart Excel.
*1: The temp folder is located depending on the OS.
*2: When the corresponding folder and file are not displayed, Make the
settings in folder option setting. So that all files and folders will be
displayed.
Component.
To restore the size, set the Height and Width properties of ACT control to "24"
again.
A - 17 A - 17
Instructions for use of Microsoft
(1) Precautions for the use of Microsoft
(a) When you paste the ACT control to an Access form and double-click the ACT
(b) When you paste the ACT control and display the properties, the property
(c) Access allows ACT control resizing, which does not affect the operation of
R
Access
R
Access
control or select the custom control in the property, the following error
message will appear but this does not affect the operation of ACT control.
(Other error message may appear.)
names displayed may be broken.
As this phenomenon occurs for only the property indication, there will be no
problem in the property functions.
MX Component.
To restore the size, set the Height and Width properties of ACT control to "24"
again.
Instructions for use of VBScript and ASP function
(1) Security of the Internet/intranet when using VBScript
MX Component does not have the Internet/intranet security function.
When you need the security function, make setting on the user side.
(2) Precautions for making CPU COM communication, computer link communication,
CC-Link G4 communication or Ethernet (TCP/IP) communication on ASP page
and application*1 when Windows
If the ASP page opens CPU COM, computer link, CC-Link G4 or Ethernet
(TCP/IP) communication earlier than the application, communication in the same
path cannot be made on the application until the ASP page is closed. Therefore,
note the following points.
(a) CPU COM, computer link, CC-Link G4 or Ethernet (TCP/IP) communication
should be opened on the application earlier.
After it has been opened on the application, communication can be made on
both the application and ASP page until it is closed.
(b) When CPU COM, computer link, CC-Link G4 or Ethernet (TCP/IP)
communication has been opened on the ASP page, always close the
communication.
*1: The application indicates any of the user applications created using the MX
series and MELSOFT products.
R
2000 Professional is used.
A - 18 A - 18
INTRODUCTION
Thank you for choosing the Mitsubishi MELSOFT series Integrated FA software.
Read this manual and make sure you understand the functions and performance of MELSOFT series
thoroughly in advance to ensure correct use.
HOW TO USE THIS MANUAL ........................................................................................................................A-25
GENERIC TERMS AND ABBREVIATIONS ...................................................................................................A-26
MEANINGS AND DEFINITIONS OF TERMS.................................................................................................A-30
1 OVERVIEW 1- 1 to 1- 6
1.1 Features ..................................................................................................................................................... 1- 1
2 SYSTEM CONFIGURATIONS 2- 1 to 2-32
2.1 System Configuration List.......................................................................................................................... 2- 1
R
2.1.1 When using W indows NT
2.1.2 When using W indows
2.1.3 When using W indows
2.1.4 When using W indows
2.1.5 When using W indows
2.1.6 When using W indows
2.1.7 When using W indows
2.1.8 When using W indows Vista
2.1.9 When using W indows Windows
Workstation Operating System Version 4.0........................................... 2- 1
2.2 System Configuration for the Use of Each Connection Form ................................................................2- 10
2.2.1 System configurations .......................................................................................................................2- 10
2.2.2 Details of the communication forms ................................................................................................... 2-12
3.2.3 When using VBA ................................................................................................................................. 3- 4
3.2.4 When using VBScript ..........................................................................................................................3- 5
4.1 Starting the Utility .......................................................................................................................................4- 1
4.2 Exiting the Utility ......................................................................................................................................... 4- 3
4.3 Confirming the Version .............................................................................................................................. 4- 3
5 UTILITY OPERATIONS 5- 1 to 5-32
5.1 Communication Setup Utility...................................................................................................................... 5- 1
5.1.1 Operations on target setting screen ...................................................................................................5- 2
5.1.2 Operations on list view screen ............................................................................................................5- 3
5.1.3 Operations on connection test screen ................................................................................................ 5- 4
5.1.4 Operations on com setup import screen ............................................................................................5- 5
5.1.5 Operations on com setup export screen ............................................................................................5- 6
5.1.6 Operations on communication setting wizard screens ......................................................................5- 7
5.1.7 Operations on line setting screen ....................................................................................................... 5-12
6.6 CPU USB Communication......................................................................................................................... 6-43
6.8 CC-Link Communication ............................................................................................................................ 6-52
8.7 For CC-Link Communication .....................................................................................................................8-26
Appendix 2.2 Conditions of usable personal computers........................................................................APP- 5
Appendix 2.3 How to install Web server .................................................................................................APP- 6
Appendix 2.4 Setting the Internet access account .................................................................................APP- 7
Appendix 2.5 Making Web pages public ................................................................................................APP-15
Appendix 2.6 Checking whether access can be made to Web server properly or not .........................APP-19
Appendix 3 RS-232 Cable wiring example when performing computer link communication ...................APP-20
Appendix 3.1 A Series.............................................................................................................................APP-20
Appendix 3.3 Q Series ............................................................................................................................APP-24
Appendix 3.4 FX Series...........................................................................................................................APP-25
Appendix 4 Multi-CPU System ...................................................................................................................APP-26
Appendix 5 Number of Loadable Network Modules When Q00JCPU, Q00UJCPU,Q00CPU, Q00UCPU,
Q01CPU or Q01UCPU Is Used ..............................................................................................APP-27
Appendix 6 Flowchart for the case where access cannot be performed during modem communication
Appendix 9.3 DEP Configurations that May Cause Problems ..............................................................APP-44
Appendix 9.4 Configurations for Avoiding Problems due to the Effect of DEP.....................................APP-45
Appendix 9.5 Workarounds for Problems...............................................................................................APP-53
Appendix 9.6 Distinguishing Types of Projects ......................................................................................APP-62
A - 23 A - 23
MANUALS
The following lists the manuals for this software package.
Refer to the following table when ordering manuals.
Related Manuals
Manual Name
MX Component Version 3 Operating Manual (Startup)
Explains procedures for installing and uninstalling MX Component and for browsing the operating manual.
(Sold separately)
MX Component Version 3 Programming Manual
Explains the programming procedures, detailed explanations and error codes of the ACT controls.
(Sold separately)
Manual Number
(Model Code)
SH-080270
(13JU31)
SH-080272
(13JF66)
Type A70BDE-J71QLP23/A70BDE-J71QLP23GE/A70BDE-J71QBR13/A70BDE-J71QLR23
MELSECNET/10 Interface Board User's Manual (For SW3DNF-MNET10)
Explains the features, specifications, part names and setting of the MELSECNET/10 board, and the
installation, uninstallation and others of the driver. (Sold separately)
IB-0800035
(13JL93)
Type A80BDE-J61BT11 Control & Communication Link System Master/Local Interface Board
User's Manual (For SW4DNF-CCLINK-B)
Explains the features, specifications, part names and setting of the CC-Link master board, and the installation,
uninstallation and others of the driver. (Sold separately)
IB-0800175
(13JR28)
Type A80BDE-J61BT13 Control & Communication Link System Local Interface Board
User's Manual (For SW4DNF-CCLINK-B)
Explains the features, specifications, part names and setting of the CC-Link local board, and the installation,
uninstallation and others of the driver. (Sold separately)
IB-0800176
(13JR29)
Type Q80BD-J61BT11N/Q81BD-J61BT11 CC-Link System Master/ Local Interface Board User's
Manual (For SW1DNC-CCBD2-B)
Explains the system configuration, software package installation, uninstallation and each utility's operation
method, accessible range, devices and troubleshooting. (Sold separately)
SH-080527ENG
(13JR77)
Type A80BDE-A2USH-S1 programmable controller CPU Board User's Manual
(For SW1DNF-ANU-B)
Explains the features, specifications, part names and setting of the CPU board, and the installation,
uninstallation and others of the driver. (Sold separately)
Explains the features, specifications, part names and setting of the MELSECNET/H board, and the installation,
uninstallation and others of the driver. (Sold separately)
Explains system configuration, installation/uninstallation of the software package, operating methods of each
utility, accessible range, devices, and troubleshooting of the CC-Link IE Controller Network board.
(Sold separately)
GX Simulator Version 7 Operating Manual
Explains the setting and operating method for monitoring the device memory and simulating the machine side
operations using GX Simulator. (Sold separately)
GX Works2 Version 1 Operating Manual (Common)
Explains the system configuration of GX Works2 and the functions common to a Simple project and Structured
project such as parameter setting, operation method for the online function. (Sold separately)
SH-080691ENG
SH-080468ENG
SH-080779ENG
(13JZ02)
(13JU51)
(13JU63)
Note: The MX Component Version 3 Operating Manual (Startup) and MX Component Version 3 Programming
Manual are stored on the CD-ROM of the corresponding software package in PDF format.
When you want to purchase the manual alone, it is optionally available as the printed matter of the
manual number (Model code) in the above table.
A - 24 A - 24
HOW TO USE THIS MANUAL
"HOW TO USE THIS MANUAL" is given purpose-by-purpose for the use of MX
Component.
Refer to the following outlines and use this manual.
(1) To know the features (Section 1.1)
Section 1.1 gives the features.
(2) To know the system configurations (Sections 2.1, 2.2)
The system configurations using MX Component are provided.
(3) To know the MX Component operating environment and usable programmable
controller CPUs (Sections 2.3, 2.4)
Section 2.3 gives the operating environment of MX Component and Section 2.4
indicates usable programmable controller CPUs.
(4) To know the MX Component operating procedures (Chapter 3)
Chapter 3 provides the operation procedures of MX Component.
(5) To know how to operate the utilities (Chapters 4, 5)
Chapter 4 describes operations common to the utilities, and Chapter 5 explains
how to operate the utilities.
Read these chapters when using the utilities.
(6) To know the communication setting examples of the utility setting type
(Chapter 6)
Chapter 6 gives the setting example of each communication path using the utility
setting type.
(7) To know the communication setting examples of the program setting type
(Chapter 7)
Chapter 7 provides the setting example of each communication path using the
program setting type.
(8) To know the accessible devices and ranges (Chapter 8)
Chapter 8 contains the accessible devices and accessible ranges.
A - 25 A - 25
GENERIC TERMS AND ABBREVIATIONS
Unless otherwise started, this manual uses the following abbreviations and terms for
the explanation of MX Component.
Generic Term/Abbreviation Description
MX Component
IBM-PC/AT compatible Abbreviation for IBM PC/AT or its compatible personal computer
PC CPU module
GX Developer
GX Works2 Generic product name for SWnDNC-GXW2 (n: version)
GX Simulator
MELSECNET/10 board
MELSECNET/H board
CC-Link IE Controller Network
board
CC-Link IE Field Network
board
CC-Link board
CPU board Abbreviation for Type A80BDE-A2USH-S1 programmable controller CPU board
AnNCPU
AnACPU
AnUCPU
QnACPU
ACPU Generic term for AnNCPU, AnACPU and AnUCPU
QCPU (A mode) Generic term for Q02CPU-A, Q02HCPU-A and Q06HCPU-A
QCPU (Q mode)
Built-in Ethernet port QCPU
LCPU Generic term for L02CPU, L26CPU-BT
Built-in Ethernet port CPU Generic term for built-in Ethernet port QCPU and LCPU
Generic product name for SWnD5C-ACT-E and SWnD5C-ACT-EA (n: version)
-EA means a volume-license product.
Abbreviation for MELSEC-Q series compatible PC CPU module
(CONTEC CO., LTD. make)
Generic product name for SWnD5C-GPPW-E, SWnD5C-GPPW-EA,
SWnD5C-GPPW-EV, and SWnD5C-GPPW-EVA (n: version)
-EA means a volume-license product, and -EV an updated product.
Generic product name for SWnD5C-LLT-E, SWnD5C-LLT-EA, SWnD5C-LLT-EV, and
SWnD5C-LLT-EVA (n: version)
-EA means a volume-license product, and -EV an updated product.
Abbreviation for Type A70BDE-J71QLP23/A70BDE-J71QLP23GE/A70BDE-J71QBR13/
A70BDE-J71QLR23 MELSECNET/10 interface board
Abbreviation for Type Q80BD-J71LP21-25/Q81BD-J71LP21-25/
Q80BD-J71LP21S-25/Q80BD-J71LP21G/Q80BD-J71BR11 MELSECNET/H board
Abbreviation for Type Q80BD-J71GP21-SX/Q80BD-J71GP21S-SX CC-Link IE
Controller Network interface board
Abbreviation for Type Q81BD-J71GF11-T2 CC-Link IE Field Network interface board
Generic term for Type A80BDE-J61BT11 CC-Link system master/local interface board,
Type A80BDE-J61BT13 CC-Link interface board, and Type Q80BD-J61BT11N/
Q81BD-J61BT11 CC-Link system master/local interface board
Generic term for A0J2HCPU, A1SCPU, A1SCPU-S1, A1SCPUC24-R2, A1SHCPU,
A1SJCPU, A1SJHCPU, A1NCPU, A2CCPU, A2CCPUC24, A2CCPUC24-PRF,
A2CJCPU, A2NCPU, A2NCPU-S1, A2SCPU, A2SCPU-S1, A2SHCPU, A2SHCPU-S1,
A3NCPU and A1FXCPU
Generic term for A2ACPU, A2ACPU-S1, A2ACPUP21/R21, A2ACPUP21-S1, A3ACPU
and A3ACPUP21/R21
Generic term for A2UCPU, A2UCPU-S1, A2USCPU, A2USCPU-S1, A2ASCPU,
A2ASCPU-S1, A2ASCPU-S30, A2USHCPU-S1, A3UCPU and A4UCPU
Generic term for Q2ACPU, Q2ACPU-S1, Q2ASCPU, Q2ASCPU-S1, Q2ASHCPU,
Q2ASHCPU-S1, Q3ACPU, Q4ACPU and Q4ARCPU
Generic term for Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q26UDEHCPU, Q50UDEHCPU and Q100UDEHCPU
A - 26 A - 26
Generic Term/Abbreviation Description
QSCPU Abbreviation for a safety CPU module (QS001CPU)
Generic term for FX
FXCPU
Motion controller CPU
FX
1SCPU, FXUCPU, FX2CCPU, FX2NCPU, FX2NCCPU, FX3GCPU, FX3UCPU and
FX
3UCCPU
Generic term for A171SHCPU, A172SHCPU, A173UHCPU, A173UHCPU-S1,
A273UHCPU and A273UHCPU-S3
C Controller CPU Abbreviation for Q12DCCPU-V
Programmable controller CPU
C24
UC24
QC24
QC24N
Generic term for QCPU(Q mode), LCPU, QSCPU, QCPU(A mode), QnACPU, ACPU,
FXCPU, motion controller CPU and C Controller CPU
Generic term for A1SCPUC24-R2, A1SJ71C24-PRF, A1SJ71C24-R2,
A1SJ71C24-R4, A2CCPUC24, A2CCPUC24-PRF, AJ71C24-S6 and AJ71C24-S8
Generic term for AJ71UC24, A1SJ71UC24-R2, A1SJ71UC24-R4 and
A1SJ71UC24-PRF
Generic term for AJ71QC24, AJ71QC24-R2, AJ71QC24-R4, A1SJ71QC24-R2 and
A1SJ71QC24-R2
Generic term for AJ71QC24N, AJ71QC24N-R2, AJ71QC24N-R4, A1SJ71QC24N
and A1SJ71QC24N-R2
QC24(N) Generic term for QC24 and QC24N
Q series-compatible C24
Generic term for QJ71C24, QJ71C24-R2, QJ71C24N, QJ71C24N-R2 and
QJ71C24N-R4
L series-compatible C24 Generic term for LJ71C24, LJ71C24-R2
FX extended port
Generic term for FX
FX3G-485-BD, FX3U-485-BD and FX3U-485ADP
Generic term for C24, UC24, QC24(N), Q series-compatible C24,
Computer link module
(Serial communication module)
L series-compatible C24 and FX extended port
Described as the serial communication module especially to indicate QC24(N) or
Q series-compatible C24, L series-compatible C24.
Generic term for AJ71E71, AJ71E71-S3, A1SJ71E71-B2, A1SJ71E71-B5,
Abbreviation for communication with programmable controller CPU using the
Computer link communication
(Serial communication)
Ethernet communication
CPU COM communication
CPU USB communication
MELSECNET/10 communication
MELSECNET/H communication
CC-Link IE Controller Network
communication
CC-Link IE Field Network
communication
CC-Link communication
CC-Link G4 communication
CPU board communication
Q series bus communication
GX Simulator communication Abbreviation for communication with GX Simulator
GX Simulator2 communication Abbreviation for communication using the simulation functions of GX Works2
Modem communication
Gateway function communication
GOT transparent communication
Utility setting type Abbreviation for user program creation using the communication settings utility
Program setting type
ACT controls Generic term for ActiveX controls offered by MX Component
Redundant CPU Generic term for Q12PRHCPU and Q25PRHCPU
Redundant type extension base
unit
computer link module
Described as serial communication especially in communication that uses QC24(N)
or Q series-compatible C24, L series-compatible C24.
Abbreviation for communication by connecting the IBM-PC/AT compatible to
Ethernet module or the built-in Ethernet port CPU
Abbreviation of communication made by connecting the IBM-PC/AT compatible to
the RS-232 or RS-422 connector of programmable controller CPU
Abbreviation for communication by connecting IBM-PC/AT compatible to the USB
connector of QCPU (Q mode), LCPU
Abbreviation for communication with programmable controller CPU using
MELSECNET/10 board
Abbreviation for communication with programmable controller CPU using
MELSECNET/H board
Abbreviation for communication with programmable controller CPU using CC-Link
IE Controller Network board
Abbreviation for communication with programmable controller CPU using CC-Link
IE Field Network board
Abbreviation for communication with programmable controller CPU using CC-Link
board
Abbreviation for communication with programmable controller CPU using CC-Link
G4 module
Abbreviation for communication with programmable controller CPU using CPU
board
Abbreviation for communication with programmable controller CPU on the same
base using PC CPU module
Abbreviation for communication with programmable controller CPU via modems
using QC24N (except AJ71QC24N-R4), Q series-compatible C24, L seriescompatible C24, A6TEL, Q6TEL or FXCPU
Abbreviation for communication with programmable controller CPU and third-party
programmable controllers using the gateway functions of GOT
Abbreviation for communication with programmable controller CPU using the GOT
transparent functions of GOT
Abbreviation for user program creation without using the communication settings
utility
Abbreviation for Q65WRB extension base unit for redundant system
A - 28 A - 28
Loading...
+ 354 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.