MX Component Version 4

Operating Manual

-SW4DNC-ACT-E
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using this product, please read this manual and the relevant manuals carefully and pay full attention to safety to handle
the product correctly.
The precautions given in this manual are concerned with this product. For the safety precautions of the programmable
controller system, refer to the User's Manual for the CPU module.
In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".

Indicates that incorrect handling may cause hazardous conditions, resulting in

WARNING death or severe injury.

Indicates that incorrect handling may cause hazardous conditions, resulting in

CAUTION minor or moderate injury or property damage.
Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious
consequences.
Observe the precautions of both levels because they are important for personal and system safety.
Make sure that the end users read this manual and then keep the manual in a safe place for future reference.

[Design Precautions]
WARNING
● When data change, program change, or status control is performed from a personal computer to a
running programmable controller, create an interlock circuit outside the programmable controller to
ensure that the whole system always operates safely.
Furthermore, for the online operations performed from a personal computer to a programmable
controller CPU, the corrective actions against a communication error due to such as a cable
connection fault should be predetermined as a system.

[Design Precautions]
CAUTION
● The online operations performed from a personal computer to a running programmable controller
CPU (forced output and operating status changes) must be executed after the manual has been
carefully read and the safety has been ensured.
The operation failure may cause the injury or machine damage.

[Security Precautions]
WARNING
● To maintain the security (confidentiality, integrity, and availability) of the programmable controller and
the system against unauthorized access, denial-of-service (DoS) attacks, computer viruses, and other
cyberattacks from external devices via the network, take appropriate measures such as firewalls,
virtual private networks (VPNs), and antivirus solutions.

1
 CONDITIONS OF USE FOR THE PRODUCT
(1) MELSEC 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 ELECTRIC 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 ELECTRIC USER'S, 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 Electric 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 Electric 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 Electric representative in your region.
(3) Mitsubishi Electric shall have no responsibility or liability for any problems involving programmable controller trouble and
system trouble caused by DoS attacks, unauthorized access, computer viruses, and other cyberattacks.

2
OPERATING CONSIDERATIONS
This section explains the considerations in the following order.
1. Considerations of operating system and personal computer to be used
2. Considerations of installation and uninstallation
3. Programmable controller CPU-related considerations
4. Considerations for using other MELSOFT products
5. Considerations for using Ethernet modules
6. Considerations for using CC-Link modules
7. Considerations for using serial communication modules
8. Considerations of modem communication
9. Considerations of programming
10. Considerations for using of Microsoft Excel
11. Considerations for using of Microsoft Access
12. Considerations for using of VBScript
13. Considerations for using Robot controller
14. Considerations of communication
15. Considerations for saving the setting of Communication Setup Utility

Considerations of operating system and personal computer to be used

■Restrictions applied when a user without Administrator’s authority operates MX Component
Note that the following restrictions are applied when a user without Administrator’s authority operates MX Component.
Item Restrictions
Communication Setup Utility The logical station number cannot be created, changed, or deleted.
Communication settings cannot be imported.
This utility cannot be started up if the communication settings are set using MX Component earlier than
version 3.00A.*1
PLC Monitor Utility This utility cannot be started up if the communication settings are set using MX Component earlier than
version 3.00A.*1
Device registration cannot be performed on the [Entry Device] tab.
Communication board Various settings cannot be set on the CC-Link IE Controller Network, CC-Link IE Field Network,
MELSECNET/H, and CC-Link Ver.2 board utilities.

*1 If the following error message is displayed, start up and close the utility as a user with Administrator’s authority.
This operation enables a user without Administrator’s authority to start up the utility.

■Resume and other functions of personal computer

A communications error may occur when communicating 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 communicating with the programmable controller CPU.

3
 Considerations of installation and uninstallation
■Installation
When performing overwrite installation, install the software in the same folder where it is installed previously.

■Start menu
When MX Component is uninstalled, the item may remain in the start menu.
In this case, restart the personal computer.

■When downloading the installer

When downloading the installer, save the installer to a directory which does not include any space and execute it.

Programmable controller CPU-related considerations

■Considerations for performing USB communication
ON/OFF of a programmable controller CPU during communications with the programmable controller CPU may cause a
communication error which cannot be recovered.
If it is not recovered, completely disconnect the USB cable and then reconnect it after 5 or more seconds.
If this error occurs at the initial communication after the above operation, the function will be performed properly in and after
the second communications.

■Clock data of programmable controller CPU

• For QCPU (Q mode), LCPU, and FXCPU, the clock data setting can be set if the programmable controller CPU is in the
RUN status.
• For QCPU (Q mode) and LCPU, the setting can be set regardless of the ON/OFF status of the time setting device
"SM1028".
• The clock data can be set on FXCPUs with the built-in clock or FXU/FX2C/FX2NC with the RTC cassette.
• Note that an error for transfer time occurs in the time setting.

■Restrictions on using FXCPU

• When an FXCPU is used, the TN devices (timer present values) or CN devices (counter present values) cannot be
accessed if the device numbers specified are split across 199 or lower and 200 or higher.
• Since FXCPUs do not feature the PAUSE switch as the programmable controller CPU, an error is returned if remote pause
is specified in SetCpuStatus.
• Note that specifying the first I/O number of a non-existing module and executing the WriteBuffer() method will not return an
error.
• For the index registers (Z, V) of FXCPUs, data cannot be written to 2 or more consecutive points using WriteDeviceBlock().
(Data may be written to only one point.)

■Serial communication function of Q00UJ/Q00/Q00U/Q01/Q01U/Q02UCPU

In this section, "serial communication function compatible CPU" indicates Q00UJ/Q00/Q00U/Q01/Q01U/Q02UCPU.
When the following conditions are all satisfied, communication between the personal computer and the serial communication
function compatible CPU is set at 9600bps speed.
• The serial communication function of the connected CPU is valid.
• The transmission speed settings differ between the personal computer and the serial communication function compatible
CPU side.
To increase the communication speed, match the transmission speed of personal computer with that of serial communication
function compatible CPU.

■Considerations for using built-in Ethernet CPU

• When resetting the programmable controller CPU during TCP/IP connection establishment (during opening) using MX
Component, a communication error or receive error occurs at subsequent communication.
In this case, perform the close processing in the application that uses MX Component, and perform the open processing
again.
• The communication error may occur while establishing the Ethernet direct connection for the CPU, which communicates
using Ethernet direct connection with another personal computer. In such case, retry the communication by resetting the
CPU.

4
■Considerations for using RnSFCPU
In order to protect the safety programmable controller system, the "write to buffer memory" and "write to safety devices in
safety mode" functions cannot be executed.

■Considerations for using QSCPU

In order to protect the safety programmable controller system, the "write to buffer memory" and "write to safety devices in
safety mode" functions cannot be executed.

■Considerations for using FX5CPU

• Multiple simultaneous communications cannot be established via the route specified by a different adapter when an adapter
to be used for Ethernet direct connection is specified to establish a communication.
• Personal computer-side adapter information of communication settings may need to reset depending on the change in
personal computer environment or other MELSOFT application settings.

Considerations for using other MELSOFT products

■Considerations for performing GX Simulator communication
Before executing PLC Monitor Utility, Communication Setup Utility, or a user program, check that GX Simulator and GX
Developer are operating. Do not terminate GX Simulator and GX Developer while executing the user program.
Otherwise, the user program will not be terminated normally.

■Considerations for performing MT Simulator2 communication

• After installing MX Component, install MT Developer2.
• The maximum number of connections to MT Simulator2 is 4.
MT Developer2 is included in the maximum number of connections.
When two MT Developer2s and one MT Simulator2 are activated, three connections can be established from MX Component.

Considerations for using Ethernet modules

■Resetting the programmable controller CPU during TCP/IP connection establishment
When resetting programmable controller CPU during TCP/IP connection establishment (during opening) using MX
Component, a communication error or receive error occurs at subsequent communication.
In this case, perform close the processing in the application that uses MX Component, and perform the open processing
again.

■Target existence check starting interval of Ethernet module

If the close processing (Close) is executed from the personal computer, the Ethernet module may not perform the close
processing (Close). One of its causes is the cable disconnection.
If the open processing (Open) is executed from the personal computer with the Ethernet module not executing the close
processing (Close), the open processing (Open) from the personal computer is not terminated normally until the Ethernet
module performs a target existence check and executes the close processing (Close).
When terminating the open processing (Open) early from the personal computer, shorten the target existence check starting
interval setting of the Ethernet module.
(The default setting of target existence check starting interval of the Ethernet module is 10 minutes.)

■Replacement of Ethernet module

If the Ethernet modules are changed during Ethernet communication due to debugging, failure or the like, the other node
(personal computer) must be restarted.
(Because the Ethernet addresses (MAC addresses) differ between devices)

5
 ■Simultaneous access when using Q series-compatible Ethernet module
The following conditions should be satisfied when communication is performed simultaneously from multiple personal
computers to the same module using the TCP/IP protocol.
• Using Q series-compatible E71 module (except QJ71E71-100) whose first five digits of the serial number are "02122" or
higher 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].

■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 also set on the lower layer, communication cannot be performed with the programmable controller CPU on
the lower layer.

Enter password to
Starting
unlock.
source
AAAA

No. Remote Password

Ò With setting (AAAA)
Ethernet Ó Without setting
Ô With setting (AAAA)
QCPU Ò Ó Õ With setting (BBBB)
(Q QJ71 QJ71
E71 E71
Ö Without setting
mode)

Ethernet : Accessible
QCPU Ô QCPU Õ QCPU Ö
(Q QJ71 (Q QJ71 (Q QJ71 : Inaccessible
mode) E71 mode) E71 mode) E71

Ò Unlocking QJ71E71 password enables access to

programmable controller CPUs in this range.

■Ethernet communication
• The communication line is disconnected if the CPU becomes faulty or the Ethernet module is reset during Ethernet
communication (when the protocol is TCP/IP).
In this case, perform the line close processing (Close) and then perform the reopen processing (Open).
• When two different communication systems (protocols) are used to access from one personal computer to one Q series-
compatible E71, two station numbers TCP/IP and for UDP/IP must be set.
However, it is not required to set different station numbers for TCP/IP and for UDP/IP when using MX Component Version 3
or later and Q series-compatible E71 with serial number "05051" or higher.

Ex.
When MX Component uses TCP/IP and GX Developer uses UDP/IP

Personal computer
(TCP/IP) station number for MX Component: 2 Q series-compatible E71
(Station number: 1)
(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.

6
Considerations for using CC-Link modules
■Software version of CC-Link master/local module
For CC-Link master/local modules used in CC-Link communication, use modules of software version "N" or later.
Modules of software version "M" or earlier do not operate normally.

Considerations for using serial communication modules

■Serial communication
• On any serial communication modules, remote "PAUSE" operation will result in an error for all connections.
• The FX extended port is required when performing the serial communication using FX0N, FX1S, FX1N(C), FX2N(C),
FX3S, FX3G(C), or FX3U(C)CPU.

■Considerations for connecting personal computer and serial communication module

• When using QJ71C24-R2 of function version A
An MX Component application can use only either one of CH1 and CH2.
When the MELSOFT product, (GX Developer, GOT, or the like) is using one channel, the application cannot use the other
channel.
When QJ71C24-R2 of function version B is used, the application can use both channels.

Considerations of modem communication

■Simultaneous modem communications
The simultaneous modem communications using MX Component and other applications (GX Developer or the like) cannot be
performed.
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.

■Considerations for using telephone line

• Do not use the call-waiting phone line.
On the call-waiting phone line, data corruption, telephone line disconnection, or similar problem may occur due to interrupt
reading sounds.
• 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.
• Use an analog 2 wire type telephone line.
When using a digital line, use a terminal adapter.
When the telephone line is 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 connections.

■Considerations for using cellular phone

• Modem for radio communication using a cellular phone
Although the modem name is different according to the manufacturer, 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.
• Cellular phone without auto answer function
For the cellular phone without auto answer function, use a cellular phone communication unit that features the ANS/ORG/
TEL select switch.
If the cellular phone communication unit does not have the ANS/ORG/TEL select switch, the line cannot be connected.
The line connection procedure is different according to the cellular phone company and cellular phone model.
For details, contact the manufacturer of your cellular phone.

7
 Considerations of programming
■Sample programs, test programs, and sample sequence programs
• Sample programs and test programs
Sample programs are included for references when creating user programs.
Test programs are included for conducting communication tests.
Use the programs with your responsibility.
• Sample sequence programs
Sample sequence programs included in MX Component require modifications according to the system configuration and
parameter settings.
Modify the program to suit the system.
Use the programs with your responsibility.

■Forced termination of processes during communication

If communication is performed 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.

■Error at communication start

A communication error may occur within the preset time-out period at a communication start, for example, when the
communication diagnostic button is pressed, when a monitoring is started, or when any function is executed.
These errors are assumed to be detected before a time-out error.
(Example: When the communication cable is not connected or when the programmable controller power is off)

■CheckDeviceString
Do not use the CheckDeviceString method of ACT control.

■ActUMsg control and ActUWzd control

Installing MX Component registers the ActUMsg control and the ActUWzd control, however, do not use them.

■Considerations for using Ethernet modules

• Provide an interval longer than the sequence scan time of the Ethernet module mounted station for a period from when the
Open method is executed until the Close method is executed.
• Provide an interval of at least 500 ms for a period from when the Close method is executed until the Open method is
executed again.

■Considerations for execution of Disconnect

If a telephone line cannot be disconnected by executing the Disconnect function for some reason, power OFF the modem
being used to forcibly disconnect the telephone line.

■Error at building sample programs

• When the message "System.Runtime.InteropServices.COMException was not handled." appears, specify "x86" (32-bit) for
the target CPU when creating a program using MX Component.
• When using MX Component in a 64-bit program, consider the method to communicate between a 64-bit program and a 32-
bit program using MX Component by referring to the following sample program.
(Reference) "Sample\64bit" in the CD-ROM

8
Considerations for using Microsoft Excel
■When controls are not pasted to Excel
This symptom occurs if the cache file (temporary file) of Excel remains.
In such a case, perform the operation in the following procedure.

Operating procedure
1. Close Excel.

2. Delete "*.exd" in the Excel8.0 folder of the temp folders.

• The location of temp folder differs according to the operating system.
• When the corresponding folder and file are not displayed, set the settings in the folder option setting to display all files and
folders.

3. Restart Excel.

■Resizing of ACT control

Resizing of ACT control in Excel does not affect the operation of MX Component.
To restore the size, set the Height and Width properties of ACT control to "24".

■Considerations for using Excel VBA

Do not set the page feed preview function in the application that uses Excel VBA.
A memory leak or operating system basic operation (file operation, printing, or the like) failure may occur.

Considerations for using Microsoft Access

■When an error message is displayed after pasting ACT control to an Access form and double-
clicking the ACT control or selecting the custom control
The following error message is displayed. However, this does not affect the operation of ACT control.
(An error message other than the following message may be displayed.)

■When the displayed property name is collapsed after pasting ACT control and displaying
property
This symptom only occurs on the display, and this does not affect the functions of the property.

■Resizing of ACT control

Resizing of ACT control in Access does not affect the operation of MX Component.
To restore the size, set the Height and Width properties of ACT control to "24".

Considerations for using VBScript

■Security of the Internet/intranet when using VBScript
MX Component does not feature the Internet/intranet security function.
When the security function is required, set the setting on the user side.

9
 Considerations for using Robot controller
■When connecting robot controller with USB
For the considerations when connecting a robot controller with USB, refer to the following manual.
CR750/700/500 series RT ToolBox2 / RT ToolBox2 mini User's Manual
When connecting a robot controller with USB, an error does not occur for Open method of the control even when the robot
controller cannot be used.
If an error code 106 (connection is disconnected) occurred in the method after executing Open, execute Open again after
executing Close.

■Multiplex communication
Do not perform multiplex communication for one robot controller.

Considerations of communication
■When the socket object generation error (0x01808007) occurs during communication
No. Condition Corrective action
1 When using GT SoftGOT Right-click and select [Run as administrator] when starting the application.
2 When the error cannot be solved by the above Set a port number different from one used for another application to the personal computer side.
No.1
3 When the error cannot be solved by the above Check the following items, and consult your local Mitsubishi representative.
No.1 and No. 2 • System configuration (model name of the target programmable controller, model name of the
module, and used network)
• Name of personal computer (Manufacturer), CPU, memory size
• OS, Edition, 32-bit/64-bit
• MX Component version
• A function and argument of MX Component in which the symptom occurs
• Settings within "Communication Setup Utility"
• Occurrence frequency and procedure for a symptom

Considerations for saving the setting of Communication Setup Utility

■Errors which occur when saving the setting with Communication Setup Utility and corrective
actions
Error message Corrective action Considerations
Updating the system information data failed. Select [Communication Setup Utility] from the start When Label Utility is executed, the status is
• There is a possibility without the operation menu, right-click, and select [Run as switched to the administrator authority
authority. Please execute it by the administrator administrator], start up the application. automatically.
authority user. The performance differs according to the user
• There is a possibility that the operating account control (UAC) settings.
environment of the application is corrupt. Re-
install the application and try again.

10
INTRODUCTION
Thank you for your patronage. We appreciate your purchase of the engineering software, MELSOFT.
This manual is designed for users to understand operations of MX Component.
Before using the product, thoroughly read this manual and related manuals to develop full familiarity with the functions and
performance of MX Component and supported modules to ensure correct use.

11
 CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
OPERATING CONSIDERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
DEFINITIONS OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

CHAPTER 1 OVERVIEW 23
1.1 Overview of MX Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

CHAPTER 2 SYSTEM CONFIGURATIONS 30

2.1 System Configuration List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
When using Windows XP Professional Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
When using Windows XP Home Edition Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
When using Windows Vista Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
When using Windows 7 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
When using Windows 8 Operating System and Windows 8.1 Operating System. . . . . . . . . . . . . . . . . . . . . . . . 34
When using Windows 10 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.2 System Configuration for Use of Each Connection Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
System configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Details of communication forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.3 Operating Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.4 Applicable Programmable Controller CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

CHAPTER 3 INSTALLATION AND UNINSTALLATION 53

3.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.2 Registered Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.3 Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

CHAPTER 4 OPERATION PROCEDURES 64

4.1 Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.2 Selecting Development Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.3 User Application Creating Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
When using Visual Basic .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
When using Visual C++ .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
When using Visual C# .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
When using VBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
When using VBScript. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.4 PLC Monitor Utility Operating Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

CHAPTER 5 SYSTEM LABELS 71

5.1 Using System Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Register system labels in MX Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Utilizing labels used in MELSOFT Navigator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Applying device settings changed in GX Works2 to MX Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

12
 Using System Labels on another personal computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

CHAPTER 6 STARTING AND EXITING UTILITIES 88

6.1 Starting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Administrator authority when executing each utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.2 Exiting Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.3 Confirming Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

CHAPTER 7 UTILITY OPERATIONS 92

CONTENTS
7.1 Communication Setup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Operations on Target setting tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Operations on List view tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Operations on Connection test tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Importing communication settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Exporting communication settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Operations on Communication Setting Wizard screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Operations on Connect Line screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7.2 PLC Monitor Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Operations on Transfer setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Operations on Device Batch tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Operations on Buffer Memory tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Operation on Entry Device tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Operations on Write to Device screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Operations on Time setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Operations on telephone line connection, disconnection screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
7.3 Label Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Operations on Label screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Registering/deleting logical station numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
System label list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Setting Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Referring and registering/canceling Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Change notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Updating system label data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Exporting LabelSpace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Importing LabelSpace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

CHAPTER 8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE 134

8.1 Serial Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Settings of serial communication modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
8.2 Ethernet Communication (When Using Ethernet Modules) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
8.3 Ethernet Communication (When Using Built-in Ethernet CPUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8.4 Ethernet Communication (When Using Ethernet Adapter Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
8.5 Ethernet Communication (When Using Ethernet Adapter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
8.6 CPU COM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

13
 8.7 CPU USB Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
8.8 CC-Link Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
8.9 CC-Link G4 Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Switch settings of CC-Link G4 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
8.10 GX Simulator Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
8.11 GX Simulator2 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
8.12 GX Simulator3 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.13 MT Simulator2 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
8.14 MELSECNET/H Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
8.15 CC-Link IE Controller Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
8.16 CC-Link IE Field Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
8.17 Q Series Bus Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
8.18 Modem Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Switch settings of Q series-compatible C24, L series-compatible C24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
8.19 Gateway Function Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
8.20 GOT Transparent Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
8.21 Inverter COM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
8.22 Inverter USB Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
8.23 Robot controller COM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
8.24 Robot controller USB Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
8.25 Robot controller Ethernet Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

CHAPTER 9 COMMUNICATION SETTING EXAMPLES OF PROGRAM SETTING TYPE 264

CHAPTER 10 ACCESSIBLE RANGES 266

10.1 Considerations for Access Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
10.2 For Serial Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
10.3 For Ethernet Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Accessible ranges (when using Ethernet modules). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

14
 Accessible ranges (when using Built-in Ethernet CPUs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Accessible ranges (for transferring logging files using built-in Ethernet CPUs) . . . . . . . . . . . . . . . . . . . . . . . . 284
Accessible ranges (when using Ethernet adapter module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Accessible ranges (when using Ethernet adapter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Accessible ranges (when using CC-Link IE TSN modules). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
10.4 For CPU COM Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
10.5 For CPU USB Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

CONTENTS
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Accessible ranges (for transferring logging files). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
10.6 For CC-Link Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
10.7 For CC-Link G4 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
10.8 For MELSECNET/H Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
10.9 For CC-Link IE Controller Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Accessible ranges (for transferring logging files). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
10.10 For CC-Link IE Field Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
10.11 For Q Series Bus Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
10.12 For Modem Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Accessible ranges (When using Q series-compatible C24 and L series-compatible C24) . . . . . . . . . . . . . . . . 328
Accessible ranges (When using FXCPU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
10.13 For Gateway Function Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
10.14 For GX Simulator Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
10.15 For GX Simulator2 Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
10.16 For GX Simulator3 Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
10.17 For MT Simulator2 Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Accessible ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
10.18 For GOT Transparent Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

15
 Accessible devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Accessible ranges (Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Direct connection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Accessible ranges (Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Direct connection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Accessible ranges (Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Bus connection). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Accessible ranges (Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Bus connection). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Accessible ranges (Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Serial communication module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Accessible ranges (Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Serial communication module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Accessible ranges (Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Ethernet module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Accessible ranges (Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Ethernet module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Accessible ranges (Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Ethernet port). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Accessible ranges (Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Ethernet port). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Accessible ranges (Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Ethernet adapter module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Accessible ranges (Personal computer side port :USB, GOT2000/1000 side port: USB, CPU side port:
Ethernet adapter module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Accessible ranges (Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Ethernet adapter/module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Accessible ranges (Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Ethernet adapter/module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Accessible ranges (Personal computer side port: Ethernet board, GOT2000/1000 side port:
Ethernet port, CPU side port: Serial) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Accessible ranges (Personal computer side port: Ethernet board, GOT2000/1000 side port:
Ethernet port, CPU side port: Serial communication module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Accessible ranges (Personal computer side port: Ethernet board, GOT2000/1000 side port:
Ethernet port, CPU side port: Bus connection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Accessible ranges (Personal computer side port: Ethernet board, GOT2000/1000 side port:
Ethernet port, CPU side port: Ethernet port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Accessible ranges (Personal computer side port: Ethernet board, GOT2000/1000 side port:
Ethernet port, CPU side port: Q series-compatible E71). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
10.19 For Inverter Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Accessible monitor type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
10.20 For Robot Controller Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Accessible monitor type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

APPENDIX 381
Appendix 1 Concept of Routing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Appendix 2 How to Configure Internet/Intranet Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Operating procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Conditions of usable personal computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
How to install Web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

16
 Setting the Internet access account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Releasing Web pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Checking whether Web server can be accessed properly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Appendix 3 RS-232 Cable Wiring Examples for Serial Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Q Series. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
FX Series. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Appendix 4 Multi-CPU System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Appendix 5 Number of Mountable Network Modules for Q00JCPU, Q00UJCPU, Q00CPU, Q00UCPU,
Q01CPU or Q01UCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

CONTENTS
Appendix 6 Flowchart for When Access cannot be Performed during Modem Communication . . . . . . . . . . . . 403
Appendix 7 Compatibility with Redundant CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
RnPCPU (redundant mode) and RnPSFCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
QnPRH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Appendix 8 Differences with previous version of MX Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Comparison with MX Component Version 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Appendix 9 Version Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Appendix 10Character Strings that cannot be Used for Label Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Appendix 11 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Performance of MX Component (Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Performance of the Label Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Performance of the Label Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Appendix 12USB Driver Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Appendix 13Updating USB Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Appendix 14Warning Messages on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Overview of warning messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Methods for disabling warning messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Appendix 15Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Appendix 16Functions Added Since Previous Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .449
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .450

17
 RELEVANT MANUALS
Manual name [manual number] Description Available form
MX Component Version 4 Operating Manual Explains the setting and operation methods of each utility on MX Print book
[SH-081084ENG] (this manual) Component.
PDF
MX Component Version 4 Programming Manual Explains the programming procedures, detailed explanations and error Print book
[SH-081085ENG] codes of the ACT controls.
PDF
Type Q80BD-J61BT11N/Q81BD-J61BT11 CC-Link System Explains the system configuration, specifications, functions, handling, Print book
Master/Local Interface Board User's Manual (For SW1DNC- wiring, and troubleshooting of the type Q80BD-J61BT11N/Q81BD-
PDF
CCBD2-B) J61BT11 CC-Link system master/local interface board.
[SH-080527ENG]
MELSECNET/H Interface Board User's Manual (For Explains the system configuration, specifications, functions, handling, Print book
SW0DNC-MNETH-B) wiring, and troubleshooting of the MELSECNET/H board.
PDF
[SH-080128]
CC-Link IE Controller Network Interface Board User's Explains the system configuration, specifications, functions, handling, Print book
Manual (For SW1DNC-MNETG-B) wiring, and troubleshooting of the CC-Link IE Controller Network
PDF
[SH-080691ENG] board.
CC-Link IE Field Network Interface Board User's Manual Explains the system configuration, specifications, functions, handling, Print book
(For SW1DNC-CCIEF-B) wiring, and troubleshooting of the CC-Link IE Field Network board.
e-Manual
[SH-080980ENG]
PDF
C Controller Module User's Manual (Hardware Design, Explains the system configuration, specifications, functions, handling, Print book
Function Explanation) wiring, and troubleshooting of Q12DCCPU-V (Basic mode) and
PDF
[SH-080766ENG] Q06CCPU-V.
MELSEC-Q C Controller Module User's Manual Explains the system configuration, specifications, functions, handling, Print book
[SH-081130ENG] wiring, troubleshooting, and programming and function of
PDF
Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG, Q26DHCCPU-
LS, and Q12DCCPU-V (Extended mode).
GX Simulator Version 7 Operating Manual Explains the setting and operating method for monitoring the device Print book
[SH-080468ENG] memory and simulating the machine side operations using GX PDF
Simulator.
GX Works2 Version 1 Operating Manual (Common) Explains the system configuration of GX Works2 and the functions Print book
[SH-080779ENG] common to a Simple project and Structured project such as parameter
PDF
setting, operation method for the online function.
MELSEC iQ-R Ethernet User's Manual (Application) Functions, parameter settings, programming, troubleshooting, I/O Print book
[SH-081257ENG] signals, and buffer memory of Ethernet.
e-Manual
PDF

e-Manual refers to the Mitsubishi Electric FA electronic book manuals that can be browsed using a dedicated
tool.
e-Manual has the following features:
• Required information can be cross-searched in multiple manuals.
• Other manuals can be accessed from the links in the manual.
• Hardware specifications of each part can be found from the product figures.
• Pages that users often browse can be bookmarked.
• Sample programs can be copied to an engineering tool.

18
TERMS
Unless otherwise specified, this manual uses the following terms.
Term Description
.NET control Generic term for .NET control provided by MX Component.
Access Abbreviation for Microsoft Access 2003, Microsoft Access 2007, Microsoft Access 2010 (32-bit version), Microsoft Access
2013 (32-bit version), Microsoft Access 2016 (32-bit version), and Microsoft Access 2019 (32-bit version).
ACT control Generic term for ActiveX control provided by MX Component.
Built-in Ethernet CPU Generic term for RCPU, LHCPU, built-in Ethernet port QCPU, LCPU, and FX5CPU.
Built-in Ethernet port QCPU Generic term for Q03UDE, Q03UDV, Q04UDEH, Q04UDV, Q06UDEH, Q06UDV, Q10UDEH, Q13UDEH, Q13UDV,
Q20UDEH, Q26UDEH, Q26UDV, Q50UDEH, and Q100UDEH.
C Controller module Generic term for R12CCPU-V, Q12DCCPU-V (Basic mode), Q12DCCPU-V (Extended mode), Q24DHCCPU-V,
Q24DHCCPU-LS, Q24DHCCPU-VG, and Q26DHCCPU-LS.
CC-Link communication Abbreviation for communication with programmable controller CPU using CC-Link Ver.2 board.
CC-Link G4 communication Abbreviation for communication with programmable controller CPU using CC-Link G4 module.
CC-Link G4 module Abbreviation for AJ65BT-G4-S3 GPP function peripheral connection module.
CC-Link IE Controller Network Generic term for Q80BD-J71GP21-SX, Q80BD-J71GP21S-SX, and NZ81GP21-SX.
board Abbreviation for CC-Link IE Controller Network interface board.
CC-Link IE Controller Network Abbreviation for communication with programmable controller CPU using CC-Link IE Controller Network board.
communication
CC-Link IE Field Network board Abbreviation for Q81BD-J71GF11-T2 CC-Link IE Field Network interface board.
CC-Link IE Field Network Abbreviation for communication with programmable controller CPU using CC-Link IE Field Network board.
communication
CC-Link IE TSN module Another term for RJ71GN11-T2.
CC-Link Ver.2 board Generic term for Q80BD-J61BT11N and Q81BD-J61BT11.
Abbreviation for CC-Link system master/local interface board.
CPU COM communication Abbreviation of communication performed by connecting the personal computer to the RS-232 or RS-422 connector of
programmable controller CPU.
CPU USB communication Abbreviation for communication by connecting personal computer to the USB connector of Programmable controller CPU.
Ethernet adapter module Abbreviation for NZ2GF-ETB CC-Link IE Field Network Ethernet adapter module.
Ethernet adapter/module Generic term for FX3U-ENET-ADP and FX3U-ENET(-L).
Ethernet communication Abbreviation for communication by connecting the personal computer to Ethernet module or the built-in Ethernet CPU.
Ethernet module Generic term for R series-compatible E71, Q series-compatible E71, and L series-compatible E71.
Excel Abbreviation for Microsoft Excel 2003, Microsoft Excel 2007, Microsoft Excel 2010 (32-bit version), Microsoft Excel 2013
(32-bit version), Microsoft Excel 2016 (32-bit version), and Microsoft Excel 2019 (32-bit version).
FX extended port Generic term for FX0N-485ADP, FX2NC-485ADP, FX1N-485-BD, FX2N-485-BD, FX3G-485-BD, FX3U-485-BD, and
FX3U-485ADP.
FX5CPU Generic term for FX5U, FX5UC, and FX5UJ.
FXCPU Generic term for FX0, FX0S, FX0N, FX1, FX1N, FX1NC, FX1S, FXU, FX2C, FX2N, FX2NC, FX3S, FX3G, FX3GC, FX3U,
and FX3UC.
Gateway function communication Abbreviation for communication with programmable controller CPU and third-party programmable controllers using the
gateway functions of GOT.
GOT Abbreviation for Graphic Operation Terminal.
GOT transparent communication Abbreviation for communication with programmable controller CPU using the GOT transparent functions of GOT.
GOT1000 Abbreviation for Graphic Operation Terminal GOT1000 series.
GOT2000 Abbreviation for Graphic Operation Terminal GOT2000 series.
GT SoftGOT Generic term for GT SoftGOT2000 Version1, GT SoftGOT1000 Version2, and GT SoftGOT1000 Version3.
GX Developer Generic product name for SWnD5C-GPPW-E, SWnD5C-GPPW-EA, SWnD5C-GPPW-EV, and SWnD5C-GPPW-EVA. (n:
version)
-EA indicates a volume-license product, and -EV an updated product.
GX Simulator Generic product name for SWnD5C-LLT-E, SWnD5C-LLT-EA, SWnD5C-LLT-EV, and SWnD5C-LLT-EVA. (n: version)
-EA indicates a volume-license product, and -EV an updated product.
GX Simulator communication Abbreviation for communication with GX Simulator.
GX Simulator2 communication Abbreviation for communication using the simulation functions of GX Works2.
GX Simulator3 communication Abbreviation for communication using the simulation functions of GX Works3.
GX Works2 Generic product name for SWnDNC-GXW2 and SWnDND-GXW2. (n: version)
GX Works3 Generic product name for SWnDND-GXW3. (n: version)

19
 Term Description
Inverter Abbreviation for FREQROL-A800 series.
Inverter COM communication Abbreviation for communication by connecting the inverter to the COM port of personal computer.
Inverter USB communication Abbreviation for communication by connecting the inverter to the USB port of personal computer.
L series-compatible C24 Generic term for LJ71C24 and LJ71C24-R2.
L series-compatible E71 Another term for LJ71E71.
Label Generic term for label names assigned to each device.
It can be used instead of devices in programs.
LCPU Generic term for L02S, L02, L06, L26, and L26-BT.
LHCPU Generic term for L04H, L08H, and L16H.
Logging file A file where device data sampled from a programmable controller CPU is stored.
MELSECNET/H board Generic term for Q80BD-J71LP21-25, Q80BD-J71LP21S-25, Q81BD-J71LP21-25, Q80BD-J71LP21G, and Q80BD-
J71BR11.
Abbreviation for MELSECNET/H interface board.
MELSECNET/H communication Abbreviation for communication with programmable controller CPU using MELSECNET/H board.
MELSOFT Navigator Product name for the integrated development environment included in SWnDNC-IQWK (MELSOFT iQ Works). (n:
version)
Modem communication Abbreviation for communication with programmable controller CPU via modems using Q series-compatible C24, L series-
compatible C24 or FXCPU.
MT Developer2 Generic product name for SWnDNC-MTW2. (n: version)
MT Simulator2 communication Abbreviation for communication using the simulation functions of MT Developer2.
MX Component Generic product name for SWnDNC-ACT(-E) and SWnDNC-ACT-A(-EA). (n: version)
-EA indicates a volume-license product.
PC CPU module Abbreviation for MELSEC-Q series compatible PC CPU module (CONTEC CO., LTD.product).
Personal computer Generic term for personal computers on which Windows operates.
Program setting type A development type for creating user programs without using Communication Setup Utility.
Programmable controller CPU Generic term for RCPU, LHCPU, QCPU (Q mode), LCPU, FX5CPU, FXCPU, R motion CPU, Q motion CPU, QSCPU,
and C Controller module.
Q motion CPU Generic term for Q172, Q173, Q172H, Q173H, Q172D, Q173D, Q172DS, and Q173DS.
Q series bus communication Abbreviation for communication with programmable controller CPU on the same base using PC CPU module.
Q series-compatible C24 Generic term for QJ71C24, QJ71C24-R2, QJ71C24N, QJ71C24N-R2, and QJ71C24N-R4.
Q series-compatible E71 Generic term for QJ71E71, QJ71E71-B2, QJ71E71-B5, and QJ71E71-100.
Q12DCCPU-V (Basic mode) Status that Q12DCCPU-V is initialized with the basic mode.
For Q12DCCPU-V (Basic mode), refer to the following manual.
C Controller Module User's Manual (Hardware Design, Function Explanation)
Q12DCCPU-V (Extended mode) Status that Q12DCCPU-V is initialized with the extended mode.
For Q12DCCPU-V (Extended mode), refer to the following manual.
MELSEC-Q C Controller Module User's Manual
QCCPU Generic term for Q12DCCPU-V (Basic mode), Q12DCCPU-V (Extended mode), Q24DHCCPU-V, Q24DHCCPU-LS,
Q24DHCCPU-VG, and Q26DHCCPU-LS.
QCPU (Q mode) Generic term for Q00J, Q00UJ, Q00, Q00U, Q01, Q01U, Q02, Q02H, Q02PH, Q02U, Q03UD, Q03UDE, Q03UDV,
Q04UDH, Q04UDEH, Q04UDV, Q06H, Q06PH, Q06UDH, Q06UDEH, Q06UDV, Q10UDH, Q10UDEH, Q12H, Q12PH,
Q12PRH, Q13UDH, Q13UDEH, Q13UDV, Q20UDH, Q20UDEH, Q25H, Q25PH, Q25PRH, Q26UDH, Q26UDEH,
Q26UDV, Q50UDEH, and Q100UDEH.
QnPRH Generic term for Q12PRH and Q25PRH.
QSCPU Abbreviation for a safety CPU module (QS001CPU).
R motion CPU Generic term for R16MT and R32MT.
R series-compatible C24 Generic term for RJ71C24, RJ71C24-R2, and RJ71C24-R4.
R series-compatible E71 Another term for RJ71EN71.
RCCPU Another term for R12CCPU-V.
RCPU Generic term for R00, R01, R02, R04, R04EN, R08, R08EN, R08P, R08PSF, R08SF, R16, R16EN, R16P, R16PSF,
R16SF, R32, R32EN, R32P, R32PSF, R32SF, R120, R120EN, R120P, R120PSF, and R120SF.
Redundant CPU Generic term for QnPRH, RnPCPU, and RnPSFCPU.
Redundant type extension base Abbreviation for Q65WRB extension base unit for redundant system.
unit
RnCPU Generic term for R00, R01, R02, R04, R08, R16, R32, and R120.
RnENCPU Generic term for R04EN, R08EN, R16EN, R32EN, and R120EN.
RnPCPU Generic term for R08P, R16P, R32P, and R120P.

20
Term Description
RnPSFCPU Generic term for R08PSF, R16PSF, R32PSF, and R120PSF.
RnSFCPU Generic term for R08SF, R16SF, R32SF, and R120SF.
Robot controller Abbreviation for CR750-D/CRnD-700 series.
Robot controller COM Abbreviation for communication by connecting the robot controller to the COM port of personal computer.
communication
Robot controller Ethernet Abbreviation for communication by connecting the robot controller and personal computer to Ethernet.
communication
Robot controller USB Abbreviation for communication by connecting the robot controller to the USB port of personal computer.
communication
Serial communication Abbreviation for communication with programmable controller CPU using the serial communication module.
Serial communication module Generic term for R series-compatible C24, Q series-compatible C24, L series-compatible C24, and FX extended port.
System label A label that can be used commonly among iQ Works-supported products.
It is managed by MELSOFT Navigator.
There are two kinds of system labels; system label Ver.1 and system label Ver.2. The system label Ver.2 is supported by
MX Component Version 4.07H or later and MX Sheet Version 2.04E or later.
Utility setting type A development type for creating user programs using Communication Setup Utility.

Visual Basic .NET Generic term for Visual Basic version Microsoft Visual Studio 2005, Microsoft Visual Studio 2008, Microsoft Visual Studio
2010, Microsoft Visual Studio 2012, Microsoft Visual Studio 2013, Microsoft Visual Studio 2015, and Microsoft Visual
Studio 2017.
Visual C#.NET Generic term for Visual C# version Microsoft Visual Studio 2005, Microsoft Visual Studio 2008, Microsoft Visual Studio
2010, Microsoft Visual Studio 2012, Microsoft Visual Studio 2013, Microsoft Visual Studio 2015, and Microsoft Visual
Studio 2017.
Visual C++.NET Abbreviation for creation of an application using .NET Framework.
Windows 7 or later Generic term for Windows 7, Windows 8, Windows 8.1, and Windows 10.
Windows Vista or later Generic term for Windows Vista, Windows 7, Windows 8, Windows 8.1, and Windows 10.

21
 DEFINITIONS OF TERMS
The following are the definitions of terms used in this manual.

Logical station number

The connection target information required to open the communication line is combined into one data using Communication
Setup Utility, and that data is provided with a logical number.
This number can be used with the utility setting type only.

Ex.
For CPU COM communication

Q25HCPU
Personal computer (Communication target CPU)

Q25HCPU

MELSECNET/H
(Network No. 1)

QJ71LP21
CPU COM communication (Station number: 3)
(COM 1) QJ71LP21
Transmission speed (Station number: 1)
Time-out period Transmission control

Target information up to Communication target CPU is combined

into one data, to which logical station number is assigned.

Utility setting type

Communication Setup Utility (logical station number) is used to create a user program.
In the user program, the communication line can be connected easily by simply specifying the logical station number set on
Communication Setting Wizard.

Program setting type

A user program is created without using Communication Setup Utility.
Set the ACT control settings for the corresponding communication in the user program or on the property page or the like of
Visual Basic or Visual C++.
The required settings for the properties depend on the ACT control.

22
1 OVERVIEW
1
1.1 Overview of MX Component
MX Component is a tool designed to implement communication from an personal computer to the programmable controller
without any knowledge of communication protocols and modules.
Program development with serial communication and Ethernet communication used be complicated, however, it is simplified
by using the common functions.
When applying any of the following program examples to the actual system, examine the applicability and confirm that no
problem will occur in the system control.

1.2 Features

Support of a wide range of communication routes for programmable controller

A wide range of communication routes to the programmable controller are supported to enable the user to configure up a
system as desired.

Substantial improvement in user's development efficiency

MX Component comes with the wizard type Communication Setup Utility.
By simply setting dialog-based communication settings on the screen, the user can achieve communication settings to access
the programmable controller CPU to communicate with.
Once the communication settings are set, stations can be accessed by merely specifying the logical station number of the
programmable controller CPU stored on Communication Setup Utility.

Save and read of communication settings

MX Component features the functions to save and read the communication settings set on Communication Setup Utility.
The set data can easily be moved from the personal computer used for development to that used for operation.
MX Component must be installed in both the personal computer used for development and the actually used personal
computer.

Communication setting
Personal computer Personal computer
data are moved.
used for development used for operation

MX MX
Component Component

Enter and save Read communication setting data and

communication establish communication path.
setting data.
Shorten the time for operations

1 OVERVIEW
1.1 Overview of MX Component 23
 Label function
This function allows users to create a program with labels.
Programs can be created without considering device numbers, and devices can be read or written using labels names.

'Execute the processing of function "ReadDeviceRandom2".

iReturnCode=
DotUtlType.ReadDeviceRandom2(
Structured data type label
"Amount of production",
D0 Word
3,
CN200 Word
objData) D1 Word

Specify the label name.

'Execute the processing of function "ReadDeviceRandom2".

iReturnCode=
DotUtlType.ReadDeviceRandom2(
Array type label
"AlarmArray",
[0] : D0 Word
3,
[1] : D1 Word
objectValue) [2] : D2 Word

Free from complex use of data-type-dedicated methods.

Device monitor function

Utilizing PLC Monitor Utility enables users to monitor the status of the specified device and change its data.
Device data of QSCPU cannot be changed.

X39 is ON.
X39 is ON!

MX
Component

Device status is checked.

Set and connect communication path on

MX Component.

Access to buffer memory of special function module

Not only the devices of the programmable controller CPU but also the buffer memory of an intelligent function or special
function module can be accessed.
Buffer memory data of QSCPU cannot be written.

Buffer memory data of connected intelligent or

special function module can be read/written!

MX
Component
Access to buffer memory

1 OVERVIEW
24 1.2 Features
Read/write of programmable controller CPU clock data
The clock data of the programmable controller CPU connected to the personal computer can be read/written.
1
Clock data of QSCPU cannot be written.

Clock data of connected programmable

controller CPU can be read/written!

MX
Component
Access to clock data

Multi-thread communication
The same communication route can be accessed from multiple threads at the same time.

User program

Thread 1 Thread 2

Control 1 Control 2

The simulator function for offline debugging

By using the simulation function, debugging can be performed on a single personal computer without connecting the
programmable controller.

MX
Component

Personal computer Programmable controller

Programmable controller is
not required to be connected.

■Software required for Simulation function

This function is not supported by QSCPU.
• GX Developer and GX Simulator are separately required to use GX Simulator.
• GX Works2 is required to use GX Simulator2.
The maximum of 4 projects can be simulated simultaneously.
• GX Works3 is required to use GX Simulator3.
Number of projects the GX Simulator3 can simultaneously simulate depends on the number of starts of GX Works3.

■When using the simulation function (MT Simulator2) of MT Developer2

• MT Developer2 is required to use MT Simulator2.
• The maximum of 3 projects can be simulated simultaneously.
• This function is supported by Q motion CPU only.

1 OVERVIEW
1.2 Features 25
 A wide variety of programming languages supported
MX Component supports VBScript and VBA as well as Visual Basic, Visual C++, and Visual C#.

■Creation of monitoring page using VBScript

• Monitoring page can be created in HTML format
A graphical monitoring home page (HTML format) can be created by using the text editor.
Visual Basic, Visual C++, Visual C# or the like is not required to be purchased.

Monitoring using Internet Explorer

MX Component
Web browser
(Internet Explorer 5.0 or later)
HTML for programmable controller monitoring

MELSECNET/H or the like

• Using ASP function for monitoring via Internet/intranet

Using the ASP function of VBScript and releasing the Web pages on the factory side (side which monitors data using MX
Component) enables the programmable controller device status or remote operation for an error to be performed from a
remote location or during business trip via the Internet/intranet by merely specifying the factory side URL on Internet
Explorer.

Internet
Intranet
<Factory side>
MX Component
Programmable controller Web server *1
accessing ASP *1: Web server supported by operating system
(Internet Information Server, Personal Web
Server, etc.)

<Office side>
Web browser
MELSECNET/H or the like
(Internet Explorer 5.0 or later)

1 OVERVIEW
26 1.2 Features
■VBA-driven data collection and monitoring function
Programming using VBA allows Excel or Access functions to be utilized to create an application for providing a real-time
graph display. 1
Device data of the programmable controller can be logged and device data can be sampled/saved in real time.

<Excel> <Access>

Compatibility with multi-CPU system of QCPU (Q mode)

Setting Communication Setup Utility or control properties enables access to the multi-CPU system.

Operability on PC CPU module

Q series bus communication from the PC CPU module enables access to the QCPU (Q mode) on the same base.
Using the MELSECNET/H communication control and CC-Link communication control enables access to other stations via
the MELSECNET/H module and CC-Link module controlled by the PC CPU module.

QCPU (Q mode) QCPU (Q mode) or the like

PC CPU
module

CC-Link
MELSECNET/H

QCPU (Q mode) or the like

1 OVERVIEW
1.2 Features 27
 Accessibility to gateway devices of GOT
The gateway device data of GOT can be read/written by using the gateway function communication of MX Component.
The device data of the programmable controller CPU that is being monitored by GOT can be read/written by reading from/
writing to the gateway device data of GOT.

MX
Component

Gateway device data of GOT can be

read/written using MX Component
(gateway functions).
Ethernet

GOT GOT GOT

Programmable controller CPU data

are read/written with GOT.

Mitsubishi Company A Company B

programmable programmable programmable
controller controller controller

Compatibility with GOT transparent function

Using the GOT transparent function, the programmable controller CPU can be accessed via GOT.

MX
Component
GOT

Reduction of error description search time

The ActSupport control for troubleshooting function is supported.
The error description and corrective action are displayed within the user application by only specifying the error code.
Therefore, checking error description or corrective action on the programming manual is not required when an error occurs in
a control.

<Example of displaying error description on message box>

Error description and corrective action

are displayed.

1 OVERVIEW
28 1.2 Features
Logging file transfer supported
A logging file in the SD memory card inserted in an RCPU can be transferred to a personal computer.
1
For controls for transferring logging files, refer to the following manual.
MX Component Version 4 Programming Manual

1 OVERVIEW
1.2 Features 29
 2 SYSTEM CONFIGURATIONS
This chapter explains the system configurations, operating environment and usable CPUs of MX Component.

2.1 System Configuration List

This section lists the systems that can be configured for each operating system.

When using Windows XP Professional Operating System

The following table lists the systems that can be configured for the use of Windows XP Professional.
: Configurable, : Not configurable
Item Description
Serial communication 
Ethernet communication 
CPU COM communication 
CPU USB communication 
MELSECNET/H communication *1
CC-Link IE Controller Network communication *2
CC-Link IE Field Network communication *3
CC-Link communication *4
CC-Link G4 communication 
Q series bus communication (only when PC CPU module is used) 
GX Simulator communication 
GX Simulator2 communication 
GX Simulator3 communication 
MT Simulator2 communication 
Modem communication 
Gateway function communication 
GOT transparent communication 
Inverter COM communication 
Inverter USB communication 
Robot controller COM communication 
Robot controller USB communication 
Robot controller Ethernet communication 

*1 Supported by SW0DNC-MNETH-B version 70H or later

*2 Applicable board: CC-Link IE Controller Network board
Applicable driver: SW1DNC-MNETG-B or later
*3 Applicable board: CC-Link IE Field Network board
Applicable driver: SW1DNC-CCIEF-B or later
*4 Supported by SW4DNF-CCLINK-B version 40E or later

2 SYSTEM CONFIGURATIONS
30 2.1 System Configuration List
When using Windows XP Home Edition Operating System
The following table lists the systems that can be configured for the use of Windows XP Home Edition.
: Configurable, : Not configurable
Item Description
Serial communication  2
Ethernet communication 
CPU COM communication 
CPU USB communication 
MELSECNET/H communication 
CC-Link IE Controller Network communication *1
CC-Link IE Field Network communication *2
CC-Link communication 
CC-Link G4 communication 
Q series bus communication (only when PC CPU module is used) 
GX Simulator communication 
GX Simulator2 communication 
GX Simulator3 communication 
MT Simulator2 communication 
Modem communication 
Gateway function communication 
GOT transparent communication 
Inverter COM communication 
Inverter USB communication 
Robot controller COM communication 
Robot controller USB communication 
Robot controller Ethernet communication 

*1 Applicable board: CC-Link IE Controller Network board

Applicable driver: SW1DNC-MNETG-B or later
*2 Applicable board: CC-Link IE Field Network board
Applicable driver: SW1DNC-CCIEF-B or later

The ASP function of VBScript cannot be used.

2 SYSTEM CONFIGURATIONS
2.1 System Configuration List 31
 When using Windows Vista Operating System
The following table lists the systems that can be configured for the use of Windows Vista.
: Configurable, : Not configurable
Item Description
Serial communication 
Ethernet communication 
CPU COM communication 
CPU USB communication 
MELSECNET/H communication 
CC-Link IE Controller Network communication 
CC-Link IE Field Network communication 
CC-Link communication 
CC-Link G4 communication 
Q series bus communication (only when PC CPU module is used) 
GX Simulator communication 
GX Simulator2 communication 
GX Simulator3 communication 
MT Simulator2 communication 
Modem communication 
Gateway function communication 
GOT transparent communication 
Inverter COM communication 
Inverter USB communication 
Robot controller COM communication 
Robot controller USB communication 
Robot controller Ethernet communication 

2 SYSTEM CONFIGURATIONS
32 2.1 System Configuration List
When using Windows 7 Operating System
The following table lists the systems that can be configured for the use of Windows 7.
: Configurable, : Not configurable
Item Description
32-bit version 64-bit version 2
Serial communication  
Ethernet communication  
CPU COM communication  
CPU USB communication  
MELSECNET/H communication  
CC-Link IE Controller Network communication  
CC-Link IE Field Network communication  
CC-Link communication  
CC-Link G4 communication  
Q series bus communication (only when PC CPU module is used)  
GX Simulator communication  
GX Simulator2 communication  
GX Simulator3 communication  
MT Simulator2 communication  
Modem communication  
Gateway function communication  
GOT transparent communication  
Inverter COM communication  
Inverter USB communication  
Robot controller COM communication  
Robot controller USB communication  
Robot controller Ethernet communication  

2 SYSTEM CONFIGURATIONS
2.1 System Configuration List 33
 When using Windows 8 Operating System and Windows 8.1
Operating System
The following table lists the systems that can be configured for the use of Windows 8 and Windows 8.1.
: Configurable, : Not configurable
Item Description
32-bit version 64-bit version
Serial communication  
Ethernet communication  
CPU COM communication  
CPU USB communication  
*1
MELSECNET/H communication  *1
*1
CC-Link IE Controller Network communication  *1
CC-Link IE Field Network communication *1 *1
*1
CC-Link communication  *1
CC-Link G4 communication  
Q series bus communication (only when PC CPU module is used)  
GX Simulator communication  
GX Simulator2 communication  
GX Simulator3 communication  
MT Simulator2 communication  
Modem communication  
Gateway function communication  
GOT transparent communication  
Inverter COM communication  
Inverter USB communication  
Robot controller COM communication  
Robot controller USB communication  
Robot controller Ethernet communication  

*1 Not supported when using Windows 8.1

2 SYSTEM CONFIGURATIONS
34 2.1 System Configuration List
When using Windows 10 Operating System
The following table lists the systems that can be configured for the use of Windows 10.
: Configurable, : Not configurable
Item Description
32-bit version 64-bit version 2
Serial communication  
Ethernet communication  
CPU COM communication  
CPU USB communication  
MELSECNET/H communication *1*3 *1*2*3
CC-Link IE Controller Network communication *1*4 *1*2*4
*1*5
CC-Link IE Field Network communication  *1*2*5
CC-Link communication *1*6 *1*2*6
CC-Link G4 communication  
Q series bus communication (only when PC CPU module is used)  
GX Simulator communication  
GX Simulator2 communication  
GX Simulator3 communication  
MT Simulator2 communication  
Modem communication  
Gateway function communication  
GOT transparent communication  
Inverter COM communication  
Inverter USB communication  
Robot controller COM communication  *2
Robot controller USB communication  *2
Robot controller Ethernet communication  *2

*1 Not supported when using Windows 10 Education

*2 Not supported when using Windows 10 IoT Enterprise 2016 LTSB
*3 Applicable board: MELSECNET/H board
Applicable driver: SW0DNC-MNETH-B (Version 30G) or later
*4 Applicable board: CC-Link IE Controller Network board
Applicable driver: SW1DNC-MNETG-B (Version 1.22Y) or later
*5 Applicable board: CC-Link IE Field Network board
Applicable driver: SW1DNC-CCIEF-B (Version 1.10L) or later
*6 Applicable board: CC-Link Ver.2 board
Applicable driver: SW1DNC-CCBD2-B (Version 1.19V) or later

2 SYSTEM CONFIGURATIONS
2.1 System Configuration List 35
 2.2 System Configuration for Use of Each Connection
Form
This section provides the system configurations for the use of MX Component on a communication form basis.
For details and considerations on each communication form, refer to the following section.
Page 38 Details of communication forms

System configurations
Personal computer

R series-compatible C24,
RS-232 Q series-compatible C24,
Serial communication
L series-compatible C24
RS-232/RS-485 conversion FX extended port
(FX***-485-BD,FX***-485ADP)

Ethernet Ethernet
communication Ethernet module

Ethernet
board Built-in Ethernet CPU

Ethernet adapter CC-Link IE Field CC-Link IE Field

module Network Network module

Ethernet adapter/module

CC-Link IE TSN module

CPU COM
communication RS-232
FX5CPU (FX5-232-BD, FX5-232ADP)

RS-232, RS-232/RS-422 conversion

QCPU (Q mode), LCPU,
Q motion CPU, FXCPU

Converter/cable FXCPU
(FX0/FX0S/FX0N/FX1S/FX1N/FX2N/FX1NC/
FX2NC/FX3S/FX3G/FX3GC/FX3U/FX3UC)
CPU USB
communication USB RCPU, R motion CPU, LHCPU, FX5CPU (FX5UJ),
QCPU (Q mode), LCPU, C Controller module, QSCPU,
Q motion CPU, FXCPU (FX3S/FX3G/FX3GC)
MELSECNET/H
communication MELSECNET/H MELSECNET/H module
MELSECNET/H board

CC-Link IE Controller CC-Link IE CC-Link IE controller

Network Controller Network
communication Network module
CC-Link IE Controller Network board

CC-Link IE Field
Network CC-Link IE Field CC-Link IE Field
communication Network
Network module
CC-Link IE Field Network board

CC-Link CC-Link module

communication CC-Link
(Software version "N" or later)
CC-Link Ver.2 board
CC-Link G4 RS-232/RS-422
communication conversion CC-Link module
CC-Link
(Software version "N" or later)
CC-Link G4 module
(Software version "D" or later)

2 SYSTEM CONFIGURATIONS
36 2.2 System Configuration for Use of Each Connection Form
 Personal computer

GX Developer Version 5
GX Developer (SW5D5C-GPPW-E) or later
GX Simulator
+ GX Simulator GX Simulator
communication
(offline debugging) (SW5D5C-LLT-E 10B) or later
Must be purchased separately. 2
GX Simulator2 Simulation function of GX Works2 GX Works2 Version 1
communication (GX Simulator2) (SW1DNC-GXW2-E) or later
Must be purchased separately
GX Simulator3 Simulation function of GX Works3 GX Works3
communication (GX Simulator3) (SW1DND-GXW3-E)
Must be purchased separately
MT Simulator2 Simulation function of MT Developer2 MT Developer2 Version 1
communication (MT Simulator2) (SW1DNC-MTW2-E) or later
Must be purchased separately
Telephone line FXCPU,
Modem
communication Q series-compatible C24,
Modem Modem L series-compatible C24

Gateway function Ethernet

communication GOT
Ethernet board

USB, RS-232 RS-232 RCPU, QCPU (Q mode),

GOT transparent
LCPU, C Controller module,
communication Ethernet Q motion CPU
GOT
RS-232/RS-422
FX5CPU, FXCPU

RS-232 R series-compatible C24,

Q series-compatible C24,
L series-compatible C24

Bus connection
QCPU (Q mode), QCCPU,
Q motion CPU

Ethernet
Ethernet module

Ethernet
Built-in Ethernet CPU

Ethernet
Ethernet adapter module
CC-Link IE Field CC-Link IE Field
Network Network module

Ethernet
Ethernet adapter/module

Inverter COM RS-232/RS-485 conversion

Inverter
communication

Inverter USB USB

Inverter
communication

Robot controller COM RS-232

communication Robot controller

Robot controller USB USB

communication Robot controller

Robot controller Ethernet Ethernet

Robot controller
communication
Ethernet board

Q series bus On the same base

PC CPU module QCPU (Q mode)
communication

2 SYSTEM CONFIGURATIONS
2.2 System Configuration for Use of Each Connection Form 37
 Details of communication forms

Serial communication
For connecting the serial communication module, refer to the manual of serial communication module.

■Applicable modules
The following table indicates the applicable modules for accessing programmable controller CPU with serial communication
module.
Category Module model
R series-compatible C24 RJ71C24, RJ71C24-R2, RJ71C24-R4
Q series-compatible C24 QJ71C24, QJ71C24-R2, QJ71C24N,QJ71C24N-R2, QJ71C24N-R4
L series-compatible C24 LJ71C24, LJ71C24-R2
FX extended port FX0N-485ADP, FX2NC-485ADP, FX3U-485ADP, FX1N-485-BD, FX2N-485-BD, FX3G-485-BD, FX3U-485-BD

■About connection of applicable modules

When accessing the programmable controller CPU from a personal computer via serial communication modules, note that
modules that can be connected to the personal computer are limited.
Even if a module cannot be directly connected to the personal computer, it may be applicable as the nth module in multi-
dropped connection.
: Applicable, : Not applicable
Model Interface 1:1 system configuration Multi-dropped connection
1st module nth module
RJ71C24 RS-232(CH1)   
RS-422/485(CH2)   
RJ71C24-R2 RS-232(CH1)   
RS-232(CH2)   
RJ71C24-R4 RS-422/485(CH1)   
RS-422/485(CH2)   
QJ71C24 RS-232(CH1)   
QJ71C24N
RS-422/485(CH2)   
QJ71C24-R2 RS-232(CH1)   
QJ71C24N-R2
RS-232(CH2)   
(Function version B or later)
QJ71C24N-R4 RS-422/485(CH1)   
RS-422/485(CH2)   
LJ71C24 RS-232(CH1)   
RS-422/485(CH2)   
LJ71C24-R2 RS-232(CH1)   
RS-232(CH2)   
FX0N-485ADP RS-422/485   
FX2NC-485ADP
FX3U-485ADP
FX1N-485-BD
FX2N-485-BD
FX3G-485-BD
FX3U-485-BD

■Switch settings of the serial communication module

For the switch settings for the use of MX Component, refer to the following section.
Page 134 Settings of serial communication modules

■Cable for connection

For the connection cable, refer to the manual of serial communication module.
For cable pin assignment, refer to the following appendix.
Page 399 RS-232 Cable Wiring Examples for Serial Communication

2 SYSTEM CONFIGURATIONS
38 2.2 System Configuration for Use of Each Connection Form
 Only the RS-232 connector applicable for connection of the personal computer and serial communication
module.
The RS-422 connector or RS-422/485 terminal block cannot be used.

Ethernet communication (When Ethernet module is used) 2

For connecting the Ethernet module, refer to the manual of Ethernet module.

■Applicable modules
The following table indicates the applicable modules for accessing the programmable controller CPU via Ethernet modules.
For the FX series Ethernet module, refer to the user's manuals for the FX series.
Category Module model
R series-compatible E71 RJ71EN71
Q series-compatible E71 QJ71E71,QJ71E71-B2,QJ71E71-B5,QJ71E71-100
L series-compatible E71 LJ71E71

Ethernet communication (When built-in Ethernet CPU is used)

For connecting built-in Ethernet CPU, refer to the manual of built-in Ethernet CPU.

Ethernet communication (When Ethernet adapter module is used)

For connecting the Ethernet adapter module, refer to the manual of Ethernet adapter module.

Ethernet communication (When Ethernet adapter is used)

For connecting the Ethernet adapter, refer to the manual of Ethernet adapter.

Ethernet communication (When a CC-Link IE TSN module is used)

For connecting a CC-Link IE TSN module, refer to the manual of the CC-Link IE TSN module.

CPU COM communication

■Cable for connection of QCPU (Q mode) and LCPU
The following cable is required for communications between the personal computer and of QCPU (Q mode).
RS-232 adaptor (L6ADP-R2) is required for the connection of LCPU.
Model name Manufacturer
QC30R2 Mitsubishi Electric Corporation RS-232 cable
(Personal computer connector: 9-pin D-sub)

• High-speed communication
For high-speed communication (transmission speed: 115.2/57.6kbps), use a personal computer compatible
with high-speed communication.
When a communication error occurs, retry the communication after reducing the transmission speed
setting.

2 SYSTEM CONFIGURATIONS
2.2 System Configuration for Use of Each Connection Form 39
 ■Cable for connection of FX5CPU
The following cable is required for communications between the personal computer and of FX5CPU.
Function expansion board and special adapter RS-232 cable
FX5-232ADP FX-232CAB-1
FX5-232-BD

For details of cables, refer to the following manuals.

MELSEC iQ-F FX5U User's Manual (Hardware)

■Cables for connection of FXCPU

The following cable is required for communications between the personal computer and of FXCPU.
<When using Mitsubishi Electric Corporation product>
Personal computer side (RS-232 cable) RS-232/RS-422 Programmable controller CPU side (RS-422 cable)
converter
For FX1/FXU/FX2C

F2-232CAB
(25-pin D-sub  25-pin D-sub) FX-422CAB (0.3m)
FX-422CAB-150 (1.5m)

FX-232AW
F2-232CAB-1
(9-pin D-sub  25-pin D-sub)
For FX0/FX0S/FX0N/FX1S/FX1N/FX1NC/FX2N/FX2NC/FX3S/FX3G/
FX3GC/FX3U/FX3UC

F2-232CAB-2 FX-232AWC
(Half pitch  25-pin D-sub)
FX-422CAB0 (1.5m)

AC30N2A (25-pin  25-pin)

FX-232AWC-H

• Transmission speed
When connecting to FX3S/FX3G/FX3GC/FX3U/FX3UC using FX-232AWC-H, select any of 9.6kbps,
19.2kbps, 38.4kbps, 57.6kbps, or 115.2kbps for the transmission speed.
When connecting using FX-232AWC or FX-232AW, select either 9.6kbps or 19.2kbps for the transmission
speed.
• Connecting to FXCPU
Be sure to use equipment shown in the table when connecting to FXCPU.

2 SYSTEM CONFIGURATIONS
40 2.2 System Configuration for Use of Each Connection Form
■Considerations on using RS-422 interface cables/converters
For the specifications of an RS-422 interface conversion cable/converter and the considerations on using them, read the
following instructions as well as the manuals of each product for correct handling.
• Connecting/disconnecting the conversion cable/converter
When connecting/disconnecting a peripheral device, conversion cable or converter to/from the RS-422 interface, be sure to
touch a grounding strap or grounded metal to discharge static electricity stored in the cable or in your body before the 2
operation, regardless of whether electricity is being supplied or not. After doing this, follow the procedure below.
Turn the programmable controller CPU OFF before connecting/disconnecting a conversion cable/ converter that receives 5
VDC power supply from the RS-422 interface.

Operating procedure
1. Turn OFF the personal computer.

2. Turn OFF the conversion cable/converter. Ground the FG terminal if provided.

3. Connect/disconnect the conversion cable/converter to/from the personal computer and the programmable controller
CPU.
4. Turn ON the conversion cable/converter.

5. Turn ON the personal computer.

6. Start up the software package.

■Cables for connection of Q motion CPU

For communications between the personal computer and Q motion CPU, use the cables as indicated below.
Page 39 Cable for connection of QCPU (Q mode) and LCPU

■Converter/Cable (FXCPU compatible) for connecting to the USB on personal computer

• Applicable devices

FX-USB-AW USB cable (included)

• Using a USB cable for the first time

Install the driver from the CD-ROM included with FX-USB-AW and FX3U-USB-BD.
• Considerations and restrictions
For the considerations and restrictions relating to FX-USB-AW, refer to the user's manual included.

2 SYSTEM CONFIGURATIONS
2.2 System Configuration for Use of Each Connection Form 41
 ■USB cables and function expansion boards (compatible with FX3U, FX3UC)
• Applicable devices

FX3U-USB-BD USB cable (included)

• Using a USB cable for the first time

Install the driver from the CD-ROM included with FX-USB-AW and FX3U-USB-BD.
• Considerations and restrictions
For the considerations and restrictions relating to FX3U-USB-BD, refer to the user's manual included.
• PLC parameter
When "Operate Communication Setting" is selected on the [PLC System (2)] tab of PLC parameter in GX
Works2, the corresponding port cannot communicate with the programmable controller CPU. Write the
setting in which "Operate Communication Setting" is cleared from the built-in programming port of the
programmable controller CPU.
For the method of PLC parameter settings, refer to the following manual.
GX Works2 Version 1 Operating Manual (Common)

■USB cables (compatible with FX3S, FX3G, and FX3GC)

For details of cables, refer to the following manuals.
FX3S Series User's Manual- Hardware Edition
FX3G Series User's Manual- Hardware Edition
FX3GC Series User's Manual- Hardware Edition

• Using a USB cable for the first time

Install the USB driver. (Page 431 Updating USB Driver)

■RS-422 function expansion board for FXCPU

Series Function expansion board
FX3U, FX3UC (FX3UC-32MT-LT and FX3UC-32MT-LT-2 only) FX3U-422-BD
FX3S, FX3G FX3G-422-BD
FX2N FX2N-422-BD
FX1S, FX1N FX1N-422-BD

• PLC parameter
When "Operate Communication Setting" is selected on the [PLC System (2)] tab of PLC parameter in GX
Works2, the corresponding port cannot communicate with the programmable controller CPU. Write the
setting in which "Operate
Communication Setting" is cleared from the built-in programming port of the programmable controller CPU.
For the method of PLC parameter settings, refer to the following manual.
GX Works2 Version 1 Operating Manual (Common)

2 SYSTEM CONFIGURATIONS
42 2.2 System Configuration for Use of Each Connection Form
■RS-232 cable and function expansion board (special adaptor) for FXCPU
Serial port shape of Series Function expansion board and special adapter RS-232 cable
personal computer
9-pin D-sub FX3U, FX3UC FX3U-232-BD*1 FX-232CAB-1
Function expansion board (FX3U-***-BD)*2 + FX3U-232ADP
FX3G, FX3GC FX3G-232-BD*3 FX-232CAB-1 2
FX3G-CNV-ADP*4 + FX3U-232ADP
FX3S FX3G-232-BD FX-232CAB-1
FX3S-CNV-ADP + FX3U-232ADP
FX2N FX0N-232ADP + FX2N-CNV-BD F2-232CAB-1
FX2N-232-BD FX-232CAB-1
FX2NC-232ADP + FX2N-CNV-BD
FX1NC, FX2NC FX0N-232ADP F2-232CAB-1
FX2NC-232ADP FX-232CAB-1
FX1S, FX1N FX0N-232ADP + FX1N-CNV-BD F2-232CAB-1
FX1N-232-BD FX-232CAB-1
FX2NC-232ADP + FX1N-CNV-BD
Half pitch 14-pin FX3U, FX3UC FX3U-232-BD FX-232CAB-2
Function expansion board (FX3U-***-BD)*2 + FX3U-232ADP
FX3G, FX3GC FX3G-232-BD*3 FX-232CAB-2
FX3G-CNV-ADP*4 + FX3U-232ADP
FX3S FX3G-232-BD FX-232CAB-2
FX3S-CNV-ADP + FX3U-232ADP
FX2N FX0N-232ADP + FX2N-CNV-BD F2-232CAB-2
FX2N-232-BD FX-232CAB-2
FX2NC-232ADP + FX2N-CNV-BD
FX1NC, FX2NC FX0N-232ADP F2-232CAB-2
FX2NC-232ADP FX-232CAB-2
FX1S, FX1N FX0N-232ADP + FX1N-CNV-BD F2-232CAB-2
FX1N-232-BD FX-232CAB-2
FX2NC-232ADP + FX1N-CNV-BD
25-pin D-sub FX3U, FX3UC FX3U-232-BD F2-232CAB-1
*2
Function expansion board (FX3U-***-BD) + FX3U-232ADP
FX3G, FX3GC FX3G-232-BD*3 F2-232CAB-1
FX3G-CNV-ADP*4 + FX3U-232ADP
FX3S FX3G-232-BD F2-232CAB-1
FX3S-CNV-ADP + FX3U-232ADP
FX2N FX0N-232ADP + FX2N-CNV-BD F2-232CAB
FX2N-232-BD F2-232CAB-1
FX2NC-232ADP + FX2N-CNV-BD
FX1NC, FX2NC FX0N-232ADP F2-232CAB
FX2NC-232ADP F2-232CAB-1
FX1S, FX1N FX0N-232ADP + FX1N-CNV-BD F2-232CAB
FX1N-232-BD F2-232CAB-1
FX2NC-232ADP + FX1N-CNV-BD

*1 For FX3UC series, only FX3UC-32MT-LT and FX3UC-32MT-LT-2 are connectable.

*2 *** of the function expansion board (FX3U-***-BD) indicates 232, 485, 422, USB, CNV, or 8AV.
Function expansion board (FX3U-***-BD) is not required for FX3UC (D, DS, DSS) series.
The serial communication is also available for FX3U-485-BD. For setting for the serial communication, refer to the following section.
Page 137 FX extended port
*3 FX3GC series are not connectable.
*4 ADP (FX3G-CNV-ADP) for FX3U adapter connection is not required for FX3GC series.

2 SYSTEM CONFIGURATIONS
2.2 System Configuration for Use of Each Connection Form 43
 • PLC parameter
When "Operate Communication Setting" is selected on the [PLC System (2)] tab of PLC parameter in GX
Works2, the corresponding port cannot communicate with the programmable controller CPU.
Write the setting in which "Operate Communication Setting" is cleared from the built-in programming port of
the programmable controller CPU.
For the method of PLC parameter settings, refer to the following manual.
GX Works2 Version 1 Operating Manual (Common)

CPU USB communication

■USB cables
The following table shows the USB cables whose operations have been confirmed by Mitsubishi Electric.
Product name Model name Manufacturer
USB cable (USB A type  USB B type) AU230 BUFFALO INC.
USB cable (USB A type  USB miniB type) KU-AMB530 SANWA SUPPLY INC.
U2C-M30BK ELECOM Co., Ltd.
MR-J3USBCBL3M Mitsubishi Electric Corporation
GT09-C30USB-5P Mitsubishi Electric System & Service Co., Ltd.

■Applicable CPU modules

Refer to "Access Target" of the accessible device table in the following section.
Page 295 Accessible devices

• Using a USB cable for the first time

Install the USB driver. For the installation of the USB driver, refer to the following appendix.
Page 423 USB Driver Installation
• Considerations and restrictions
For the considerations and restrictions when accessing a programmable controller CPU, refer to the
following section.
Page 4 Programmable controller CPU-related considerations

MELSECNET/H communication
■Considerations
• Use the communication driver SW0DNC-MNETH-B or later.
The other communication drivers cannot be used.
• For details of the supported operating system of the network board to be used for communication, refer to the manual of
each network board.

CC-Link IE Controller Network communication

■Considerations
• Use the communication driver SW1DNC-MNETG-B or later.
The other communication drivers cannot be used.
• For details of the supported operating system of the network board to be used for communication, refer to the manual of
each network board.

2 SYSTEM CONFIGURATIONS
44 2.2 System Configuration for Use of Each Connection Form
CC-Link IE Field Network communication
■Considerations
• Use the communication driver SW1DNC-CCIEF-B or later.
The other communication drivers cannot be used.
• For details of the supported operating system of the network board to be used for communication, refer to the manual of 2
each network board.

CC-Link communication
■Considerations
• Use the communication driver SW1DNC-CCBD2-B or later.
The other communication drivers cannot be used.
• For details of the supported operating system of the network board to be used for communication, refer to the manual of
each network board.
• The CC-Link master station module used should be of software version "N" or later.

■Applicable CPU modules

QCPU (Q mode), LCPU, RCPU

CC-Link G4 communication
■Considerations
• The CC-Link G4 module used should be of software version "D" or later.
• The CC-Link master station module used should be of software version "N" or later.

■Switch settings of the CC-Link G4 module

For the switch settings for the use of MX Component, refer to the following section.
Page 180 Switch settings of CC-Link G4 module

■Cables
Communications between the personal computer and CC-Link G4 module require the RS-232/RS-422 conversion cables as
used in CPU COM communication.
For details, refer to the following section.
Page 40 Cables for connection of FXCPU

Q series bus communication (only when PC CPU module is used)

■Considerations
Use the MELSECNET/H communication and CC-Link communication controls to access other stations via the MELSECNET/
H module and CC-Link module controlled by the PC CPU module.

2 SYSTEM CONFIGURATIONS
2.2 System Configuration for Use of Each Connection Form 45
 GX Simulator communication
■Considerations
When performing GX Simulator communication, use GX Developer Version 8 (SW8D5C-GPPW) and GX Simulator Version 7
(SW7D5C-LLT) or later.

GX Developer and GX Simulator must be purchased separately.

GX Simulator2 communication
■Considerations
When performing GX Simulator2 communication, use GX Works2 Version 1 (SW1DNC-GXW2) or later.

GX Works2 must be purchased separately.

GX Simulator3 communication
■Considerations
When performing GX Simulator3 communication, use GX Works3 (SW1DND-GXW3) or later.

GX Works3 must be purchased separately.

MT Simulator2 communication
■Considerations
When performing MT Simulator2 communication, use MT Developer2 Version 1 (SW1DNC-MTW2) or later.

MT Developer2 must be purchased separately.

2 SYSTEM CONFIGURATIONS
46 2.2 System Configuration for Use of Each Connection Form
Modem communication
■Considerations
• For modem communication using FXCPU, FX1S, FX1N, FX1NC, FX2N, FX2NC, FX3S, FX3G, FX3GC, FX3U, and FX3UC
are applicable.
• Use the RS-232 cable supplied with the modem for connection between the personal computer and modem. 2
■Softwares used for module settings
When performing modem communication, set the setting in the parameters and sequence program for the connected module.
Use any of the following software to set the corresponding module.
Module Software
GX Developer*1 GX Works2*2
FXCPU Version 3 (SW3D5C-GPPW-E/SW3D5F-GPPW-E) or later Version 1.08J (SW1DNC-GXW2-E) or later*3
Q series-compatible C24 Version 4 (SW4D5C-GPPW-E) or later Version 1.05F (SW1DNC-GXW2-E) or later
L series-compatible C24 Version 8.89T (SW8D5C-GPPW-E) or later Version 1.24A (SW1DNC-GXW2-E) or later

*1 For details on the supported versions of each module, refer to the manual of GX Developer.
*2 For details on the supported versions of each module, refer to the manual of GX Works2.
*3 FX3GC is supported by version 1.77F or later and FX3S is supported by version 1.492N or later.

■Modem specifications
When performing modem communication, select the modem that satisfies the following specifications.
• AT commands are supported. (Initialization command)
• DR terminal can be turned ON (High) independently.
(<Example> A modem, whose CD terminal turns ON as the DR terminal turns ON, cannot be used.)
• Communication standard: ITU-T V.90/V.34/V.32bis/V.32/V.22bis/V.22/V.21/V.FC, Bell 212A/103

• MX Component is not compatible with manual line connection (connection via an operator).
Use a subscriber telephone line or private telephone line to perform modem communication
• It is required to set the COM port when performing modem communication by using modem built in the
personal computer or the PC card (PCMCIA).
For the COM port of the modem built in the personal computer or the PC card (PCMCIA), refer to the
manual of the corresponding product.
• For modem communication, the standard AT command cannot be used for some modems.
If the line cannot be connected by selecting "Modem standard" for "AT command" within Communication
Setup Utility, specify the AT command on the user side.
For the setting of "AT command" within Communication Setup Utility, refer to the following section.
Page 102 Connect Line screen
• For details on the callback function, refer to the manual of the module used.

2 SYSTEM CONFIGURATIONS
2.2 System Configuration for Use of Each Connection Form 47
 Gateway function communication
■Gateway function compatible GOT
For the gateway function compatible GOT, refer to the manual of gateway function for GOT series used.

■GOT setting and setting between GOT and programmable controller

For the settings of GOT and settings between GOT and programmable controller, refer to the manual of gateway function for
GOT series used.

GOT transparent communication

■Considerations
For GOT setting and the setting between GOT and programmable controller, refer to the following manual.
Connection manuals for GOT2000 series
(Mitsubishi Products), (Non-Mitsubishi Products 1), (Non-Mitsubishi Products 2), (Microcomputer, MODBUS/Fieldbus
Products, Peripherals)
Connection manuals for GOT1000 series
(Mitsubishi Products), (Non-Mitsubishi Products 1), (Non-Mitsubishi Products 2), (Microcomputer, MODBUS Products,
Peripherals)

Inverter (COM/USB) communication

■Cables
For the connection cables, refer to the manual of inverter used.

Robot controller(COM/USB/Ethernet) communication

■Cables
For the connection cables, refer to the following manual.
CR750/700/500 series RT ToolBox2 / RT ToolBox2 mini User's Manual

2 SYSTEM CONFIGURATIONS
48 2.2 System Configuration for Use of Each Connection Form
2.3 Operating Environment

MX Component operating environment

The following table summarizes the operating environment for MX Component.
2
Item Description
Personal computer Microsoft Windows supported personal computer
CPU Intel Core2 Duo 2GHz or higher is recommended.
Required memory 1GB or more*1
PC CPU module MELSEC-Q series compatible PC CPU module (CONTEC CO., LTD.product)*2
Available hard disk capacity At installation: 300MB or more*3
At operation: Virtual memory available capacity is 512MB or more.
Display Resolution 1024  768 dots or more
*5*6
Operating system Microsoft Windows 10 (Home, Pro, Enterprise, Education, IoT Enterprise 2016 LTSB*7)
(English version) Microsoft Windows 8.1, Microsoft Windows 8.1 (Pro, Enterprise)
(32-bit/64-bit) Microsoft Windows 8, Microsoft Windows 8 (Pro, Enterprise)
Microsoft Windows 7 (Starter, Home Premium, Professional, Ultimate, Enterprise)
Microsoft Windows Vista (Home Basic SP2, Home Premium SP2, Ultimate SP2, Business SP2, Enterprise SP2)*4
Microsoft Windows XP (Professional SP3, Home Edition SP3)*4

*1 For 64-bit Windows 7 or later, 2GB or more is required.

*2 Production of the PC CPU module was discontinued in March, 2011.
*3 At installation of .NET Framework, 1GB or more free capacity is required.
*4 Supported only by 32-bit version.
*5 When the following functions are used, this product may not run properly.
Application start-up in Windows compatibility mode
Fast user switching
Remote desktop
Windows XP Mode
Windows Touch and Touch
Modern UI
Client Hyper-V
Virtual Desktops
Tablet mode
Windows Hibernate and Standby
Unified Write Filter
*6 In the following case, the screen of this product may not work properly.
The size of the text and other items in the screen is other than 100% (96 DPI, 9 pt etc.).
*7 Supported only by 64-bit version.

Precautions
Surrogate pair characters and environment dependent characters are not available in MX Component utilities.

2 SYSTEM CONFIGURATIONS
2.3 Operating Environment 49
 MX Component development environment
The following table summarizes the development environment of MX Component.
Programming language*1 Description
Visual Basic Microsoft Visual Studio 2005 Visual Basic (English version)*2
Microsoft Visual Studio 2008 Visual Basic (English version)*3
Microsoft Visual Studio 2010 Visual Basic (English version)
Microsoft Visual Studio 2012 Visual Basic (English version)
Microsoft Visual Studio 2013 Visual Basic (English version)*4
Microsoft Visual Studio 2015 Visual Basic (English version)*4
Microsoft Visual Studio 2017 Visual Basic (English version)*4
Visual C++ Microsoft Visual Studio 2005 Visual C++ (English version)*2
Microsoft Visual Studio 2008 Visual C++ (English version)*3
Microsoft Visual Studio 2010 Visual C++ (English version)
Microsoft Visual Studio 2012 Visual C++ (English version)
Microsoft Visual Studio 2013 Visual C++ (English version)*4
Microsoft Visual Studio 2015 Visual C++ (English version)*4
Microsoft Visual Studio 2017 Visual C++ (English version)*4
Visual C# Microsoft Visual Studio 2005 Visual C# (English version)*2
Microsoft Visual Studio 2008 Visual C# (English version)*3
Microsoft Visual Studio 2010 Visual C# (English version)
Microsoft Visual Studio 2012 Visual C# (English version)
Microsoft Visual Studio 2013 Visual C# (English version)*4
Microsoft Visual Studio 2015 Visual C# (English version)*4
Microsoft Visual Studio 2017 Visual C# (English version)*4
VBScript*5*6 Text editor and commercially available HTML tool
VBA Microsoft Excel 2003 (English version)*7
Microsoft Excel 2007 (English version)
32-bit Microsoft Excel 2010 (English version)*8
32-bit Microsoft Excel 2013 (English version)*9
32-bit Microsoft Excel 2016 (English version)*10
32-bit Microsoft Excel 2019 (English version)*11
Microsoft Access 2003 (English version)*7
Microsoft Access 2007 (English version)
32-bit Microsoft Access 2010 (English version)*8
32-bit Microsoft Access 2013 (English version)*9
32-bit Microsoft Access 2016 (English version)*10
32-bit Microsoft Access 2019 (English version)*11

*1 User programs created in the English environment are applicable to the English environment only, cannot be used in the other
environment.
*2 When using Visual Studio 2005 on Windows Vista, Visual Studio 2005 Service Pack 1 or Visual Studio 2005 Service Pack 1 Update for
Windows Vista is required.
*3 When using Visual Studio 2008 on Windows 7, Visual Studio 2008 Service Pack 1 is required.
*4 Supported by Windows 7 or later.
*5 To operate VBScript, use Internet Explorer with the following version.
Version 5.00.2919.6307 or later
*6 When Windows XP Home Edition is used, the ASP function cannot be used.
*7 When using Microsoft Excel 2003 or Microsoft Access 2003 on Windows 7, Microsoft Office 2003 Service Pack 3 or later is required.
*8 64-bit Microsoft Excel 2010 and 64-bit Microsoft Access 2010 are not supported.
*9 64-bit Microsoft Excel 2013 and 64-bit Microsoft Access 2013 are not supported.
*10 64-bit Microsoft Excel 2016 and 64-bit Microsoft Access 2016 are not supported.
*11 64-bit Microsoft Excel 2019 and 64-bit Microsoft Access 2019 are not supported.

2 SYSTEM CONFIGURATIONS
50 2.3 Operating Environment
Development environment of controls for transferring logging files
Controls for transferring logging files (ActUtlDataLogging, ActProgDataLogging) are supported by the following development
environments.
Programming language*1 Description
Visual Basic Microsoft Visual Studio 2010 Visual Basic (English version)
Microsoft Visual Studio 2012 Visual Basic (English version)
2
Microsoft Visual Studio 2013 Visual Basic (English version)*2
Microsoft Visual Studio 2015 Visual Basic (English version)*2
Microsoft Visual Studio 2017 Visual Basic (English version)*2
Visual C++ (MFC) Microsoft Visual Studio 2010 Visual C++ (English version)
Microsoft Visual Studio 2012 Visual C++ (English version)
Microsoft Visual Studio 2013 Visual C++ (English version)*2
Microsoft Visual Studio 2015 Visual C++ (English version)*2
Microsoft Visual Studio 2017 Visual C++ (English version)*2
Visual C# Microsoft Visual Studio 2010 Visual C# (English version)
Microsoft Visual Studio 2012 Visual C# (English version)
Microsoft Visual Studio 2013 Visual C# (English version)*2
Microsoft Visual Studio 2015 Visual C# (English version)*2
Microsoft Visual Studio 2017 Visual C# (English version)*2

*1 User programs created in the English environment are applicable to the English environment only, cannot be used in the other
environment.
*2 Supported by Windows 7 or later.

• When creating a user program, select "x86" (32-bit) as a target CPU.

• Create a user program using either of the following applications.
Windows Forms application
Console application
(MX Component cannot be accessed from Windows Service applications.)

2 SYSTEM CONFIGURATIONS
2.3 Operating Environment 51
 2.4 Applicable Programmable Controller CPUs
The following are the applicable programmable controller CPUs.
Programmable Module model
controller CPU
RCPU R00CPU, R01CPU, R02CPU, R04CPU, R04ENCPU, R08CPU, R08ENCPU, R08PCPU, R08PSFCPU, R08SFCPU,
R16CPU, R16ENCPU, R16PCPU, R16PSFCPU, R16SFCPU, R32CPU, R32ENCPU, R32PCPU, R32PSFCPU, R32SFCPU,
R120CPU, R120ENCPU, R120PCPU, R120PSFCPU, R120SFCPU
RCCPU R12CCPU-V
R motion CPU R16MTCPU, R32MTCPU
LHCPU L04HCPU, L08HCPU, L16HCPU
FX5CPU FX5UCPU, FX5UCCPU, FX5UJCPU
QCPU (Q mode) Q00JCPU, Q00UJCPU, Q00CPU, Q00UCPU, Q01CPU, Q01UCPU, Q02CPU, Q02HCPU, Q02PHCPU, Q02UCPU,
Q03UDCPU, Q03UDECPU, Q03UDVCPU, Q04UDHCPU, Q04UDEHCPU, Q04UDVCPU, Q06HCPU, Q06PHCPU,
Q06UDHCPU, Q06UDEHCPU, Q06UDVCPU, Q10UDHCPU, Q10UDEHCPU, Q12HCPU, Q12PHCPU, Q12PRHCPU,
Q13UDHCPU, Q13UDEHCPU, Q13UDVCPU, Q20UDHCPU, Q20UDEHCPU, Q25HCPU, Q25PHCPU, Q25PRHCPU,
Q26UDHCPU, Q26UDEHCPU, Q26UDVCPU, Q50UDEHCPU, Q100UDEHCPU
LCPU L02SCPU, L02CPU, L06CPU, L26CPU, L26CPU-BT
QCCPU Q12DCCPU-V (Basic mode)*1, Q12DCCPU-V (Extended mode), Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG,
Q26DHCCPU-LS
QSCPU QS001CPU
Q motion CPU Q172CPU, Q173CPU, Q172HCPU, Q173HCPU, Q172DCPU, Q173DCPU, Q172DSCPU, Q173DSCPU
FXCPU FX0CPU, FX0SCPU, FX0NCPU, FX1CPU, FX1NCPU, FX1NCCPU, FX1SCPU, FXUCPU, FX2CCPU, FX2NCPU,
FX2NCCPU, FX3SCPU, FX3GCPU, FX3GCCPU, FX3UCPU, FX3UCCPU

*1 The first five digits of the serial number is 12042 or higher are supported.

2 SYSTEM CONFIGURATIONS
52 2.4 Applicable Programmable Controller CPUs
3 INSTALLATION AND UNINSTALLATION
This chapter explains the installation and uninstallation procedure of MX Component.

3.1 Installation
The following explains the installation procedure. Screens from Windows 7 are used except for different operations required in
other operating systems. 3
• Before installing MX Component, close the other applications running on Windows.
• The installer may not work normally because of the operating system's or other companies' update
programs (Windows Update, the Java update program, or the like) start automatically. Install MX
Component after configuring those update programs not to start automatically.
• When installing MX Component, log on as a user with the administrator authority.
• For the required personal computer operating environment to install MX Component, refer to the following
section.
Page 49 Operating Environment
• For Windows 8, Windows 8.1, and Windows 10, ".NET Framework 3.5 (includes .NET 2.0 and 3.0)" needs
to be enabled in "Turn Windows features on or off" on Control Panel.
• When updating MX Component from a removable media, uninstall MelfaRXM English before the
installation.
• If do not use labels, refer to the following section.
Page 416 Installation of ACT version

Installing the product

Operating procedure
1. Right-click [Start] and select [Explorer].
Click the drive in which the disk is inserted, and double-
click "SETUP.EXE".
When user account control is enabled, the following screen is
displayed.
Click the [Yes] button. ("Allow" for Windows Vista)

3 INSTALLATION AND UNINSTALLATION

3.1 Installation 53
 2. If the message on the left is displayed, click the [Cancel]
button to uninstall MX Component, and then reinstall it.

If the message on the left is displayed, click the [OK] button

to uninstall MX Component, and then reinstall it.
(Message on the left is displayed if "SETUP.EXE" of MX
Component Version 4.11M or later is executed when MX
Component Version 4.10L or earlier is installed.)

3. If the message on the left is displayed, install EnvMEL

(Page 58 When the message "This package is not
in proper operating environment." is displayed at the
start of installation).
After the operation is complete, restart installation
operation.

4. Check that all applications is closed and click the [OK]

button.
If the applications are running, close all running
applications.
If a USB device is connected, turn it off or unplug the
USB cable.

5. Starting setup.
Enter the name and company name and click the [Next]
button.

3 INSTALLATION AND UNINSTALLATION

54 3.1 Installation
6. Check the registered name and company name.
Check if the registered content is correct, and click the
[Yes] button.
In order to change the information, click the [No] button
to return to the previous screen.

3
7. Register the product ID.
Enter the product ID and click the [Next] button.
The product ID is printed on the license certificate
included with the product.

8. Specify the installation destination folder.

If do not change the destination folder, click the [Next]
button.
In order to change the destination folder, click the
[Browse] button and specify a new drive and folder.

3 INSTALLATION AND UNINSTALLATION

3.1 Installation 55
 <Windows Vista or later> 9. When installing a MELSOFT product, the message on
the left may be displayed.
Click the [Install] button to continue the installation.
When using Windows XP, click the [Continue Anyway]
button.
(The screen display may be different partially depending
on the used operating system. This does not affect the
operation.)
(We have checked the operation and confirmed that no
error occurs after the installation.)

<Windows XP>

If an ACT version (Page 416 Installation of ACT version)

has been installed, the message shown on the left may be
displayed.
Select "Skip this installation" to proceed the installation.

3 INSTALLATION AND UNINSTALLATION

56 3.1 Installation
 If an ACT version (Page 416 Installation of ACT version)
has been installed, the message shown on the left may be
displayed.
Click the [OK] button to proceed the installation.

3
<When installing MelfaRXM English> 10. Install MelfaRXM English.
When the message shown on the left is displayed, click
the [Next] button.

<When updating MelfaRXM English> When the message shown on the left is displayed, click the
[Yes] button.
If a warning message is displayed, terminate the installation.
After uninstalling MelfaRXM English, reinstall MX
Component. (Page 59 When MelfaRXM English warning
message is displayed during installation from a removable
media)

When the message shown on the left is displayed, click the

[No] button.

When a screen that indicates the completion of installation or

update of MelfaRXM English is displayed, click the [Finish]
button.
When the message on the left is displayed, installation is
complete.

11. Click the [OK] button to close the screen.

When the following screen is displayed, select "Yes, I
want to restart my computer now."

Installation complete

3 INSTALLATION AND UNINSTALLATION

3.1 Installation 57
 When message is displayed at start of installer
The following explains the countermeasures when the message is displayed at start of installer.

■When the message "This package is not in proper operating environment." is displayed at the
start of installation
When starting the installation of this product, the "This package is not in proper operating environment" message is displayed,
disabling normal completion of installation.
In such a case, close all applications and perform the following operation.

Operating procedure
1. Execute SETUP.EXE in the "EnvMEL" folder within the product CD-ROM.
When user account control is enabled, the following screen is displayed.
Click the [Yes] button. ("Allow" for Windows Vista)

When using any of the following operating systems, refer to the corresponding technical bulletin.
• When using Windows Vista
TECHNICAL BULLETIN No.FA-A-0008
• When using Windows 7
TECHNICAL BULLETIN No.FA-A-0091
• When using Windows 8 and 8.1
TECHNICAL BULLETIN No.FA-A-0153
• When using Windows 10
TECHNICAL BULLETIN No.FA-A-0207

2. Reinstall the product.

If this product is not installed properly at this time, restart the personal computer.

3 INSTALLATION AND UNINSTALLATION

58 3.1 Installation
■When the "Program Compatibility Assistant" screen is displayed after installation
The "Program Compatibility Assistant" screen may be displayed after installation.
Select "This program installed correctly" and restart the personal computer.

If "Reinstall using recommended settings" is selected, the "Windows XP SP2 compatibility mode" is automatically set. Disable
the "Windows XP SP2 compatibility mode" by the following procedure, and install the product again.
1. Right-click on the setup.exe icon of the installation target in
Clear the check box. the Windows explorer, and open the "SETUP.EXE
Properties" screen.

2. Select the [Compatibility] tab and click the [Change

settings for all users] button.

3. Clear the "Run this program in compatibility mode for:"

check box of compatibility mode in the [Compatibility for all
users] tab, and click the [OK] button.

4. Click the [OK] button on the "SETUP.EXE Properties"

screen.

5. Install the product again. (Page 53 Installing the

product)

■When MelfaRXM English warning message is displayed during installation from a removable
media
The warning message of MelfaRXM English may be displayed during the installation from a removable media. In this case,
perform the following operations.
In this case, perform the following operations.
1. Click the [Cancel] button.

2. Terminate the installation.

3. Uninstall MelfaRXM English.

4. Install MX Component again. (Page 53 Installing the

product)

3 INSTALLATION AND UNINSTALLATION

3.1 Installation 59
 When the screen is not displayed at start of the installer
The following explains the countermeasures when the screen is not displayed (installation does not start) at start of the
installer of this product.

■Start the installer by the following methods.

• Copy the installer to a directory in a shallow layer such as "C:\temp", and start it.
• Right-click SETUP.EXE, select [Run as administrator], and start the installer.
• Exit the resident software for a keyboard/mouse, and restart the installer.

■If the problem cannot be solved by the above method, check whether the personal computer
used applies to the following conditions.
• "ntvdm.exe" is high load in the task manager (the usage rate of one CPU core is the maximum).
• The personal computer is equipped with the 6th generation Intel Core processor.
• An image is output by using the on-board video (CPU built-in).
• Any edition of Microsoft Windows 7 (32-bit version) is used.
If any of the above conditions are applied, the Windows system module "ntvdm.exe" may be executed abnormally due to an
incomplete BIOS code on the personal computer side, which causes failure to install correctly.
Please contact the used personal computer manufacturer, and obtain the corrected BIOS and apply it.

When self-registration is not performed at the time of executing the installer

Some policies of [User Account Control] in the local security policy may not be installed properly on Windows Vista or later.
Check the following policy settings.

■Detect application installations and prompt for elevation

Select [Enabled].
If selecting [Disabled], a self-registration error may occur during installation.

■Only elevate executables that are signed and validated

Select [Disabled].
If selecting [Enabled], an unsigned execution file cannot be executed and the installer cannot start properly.

■Behavior of the elevation prompt for standard users

Select [Prompt for credentials on the secure desktop] or [Prompt for credentials].
If selecting [Automatically deny elevation requests], elevation fails and the installer cannot start properly.

3 INSTALLATION AND UNINSTALLATION

60 3.1 Installation
3.2 Registered Icons
Installation of MX Component registers the following icons to [Start]  [All Programs]  [MELSOFT]  [MX Component]*1.
*1
Does not appear in Windows 8 or later.
Icon Name Description
Label Utility Starts Label Utility.

PLC Monitor Utility Starts PLC Monitor Utility.

Communication Setup Utility Starts Communication Setup Utility.

3

3 INSTALLATION AND UNINSTALLATION

3.2 Registered Icons 61
 3.3 Uninstallation
The following explains the uninstallation procedure.
Screens from Windows 7 are used except for different operations required in other operating systems.

Uninstalling deletes all the settings within "Communication Setup Utility".

To avoid this, export the file storing the settings.

Operating procedure
1. Select [Start]  [Control Panel]  "Uninstall a program"
<Windows XP>
Select [Start]  [Control Panel]  "Add/Remove
Programs"

2. Select "MX Component" from the list of programs and

select "Change/Remove".
<Windows XP>
Select "MX Component" from the list of programs and
click the [Remeove] button.
When user account control is enabled, the following screen is
displayed.
Click the [Yes] button or the [Continue] button.
<Windows 7 or later>

<Windows Vista>

3 INSTALLATION AND UNINSTALLATION

62 3.3 Uninstallation
 3. Click the [Yes] button.
When not uninstalling MX Component, click the [No]
button to return to the preceding screen.
Components indicate the icons and files installed.

3
When the screen on the left is displayed, uninstall is
complete.

4. Click the [OK] button to close the screen.

5. Restart the personal computer.

Uninstallation complete

The MelfaRXM English used for communication with a robot controller is not uninstalled even if MX
Component is uninstalled.
MelfaRXM English can be uninstalled by any of the following methods.
• Uninstall MelfaRXM English from the control panel with the same procedure as MX Component.
Select MelfaRXM English from the list of programs.
• Execute SetupRXM.exe in the "EZSocketRc" folder within the product CD-ROM.
The software package with the version which has been installed must be used.

3 INSTALLATION AND UNINSTALLATION

3.3 Uninstallation 63
 4 OPERATION PROCEDURES
This chapter explains the selection of the MX Component utilities, development type, and the procedures for creating user
applications.

4.1 Utilities
The following are the utilities used in MX Component.
Item Description Reference
Communication Setup Utility Set the parameter for communication with the wizard. Page 92 Communication
Setup Utility
PLC Monitor Utility Set a connection destination using the logical station number set with Page 109 PLC Monitor Utility
Communication Setup Utility, and monitor devices and buffer memories of a
programmable controller.
Label Utility Register/utilize the system labels. Page 121 Label Utility

4.2 Selecting Development Type

When using MX Component to create user applications, select the utility setting type or program setting type before creating a
user application.
The following explains utility setting type and program setting type.

Utility setting type

Set the communication settings using Communication Setting Wizard.
With Communication Setup Utility, a user program can be created without being aware of the complicated parameters of any
communication.
In the user program, the communication line can be connected by simply setting the logical station number set on
Communication Setting Wizard for the ACT control or the .NET control property or into a user program.

Program setting type

A user program is created without using Communication Setup Utility.
Set the ACT control settings for the corresponding communication on the property window directly or within the user program.
The required settings for the properties differ depending on the ACT control.

Comparison
The following table compares the utility setting type and program setting type.
Item Utility setting type Program setting type
Feature Communication settings can be set easily using All communication settings can be set in the user program.
Communication Setting Wizard. Communication settings can be changed flexibly in the user
In program creation, communication can be performed by program.
merely setting the parameter (logical station number) on
Communication Setting Wizard.
(The number of development processes can be reduced.)
Used ACT control ActUtlType, ActMLUtlType, ActUtlDataLogging (When the ActProgType, ActMLProgType, ActProgDataLogging (When
logging file transfer function is used) the logging file transfer function is used)
Used .NET control DotUtlType (when labels are used) 
Communication Setup Utility Used Not used
How to connect PLC Monitor Select the logical station number. Change the settings every connection. (Use the wizard)
Utility

4 OPERATION PROCEDURES
64 4.1 Utilities
4.3 User Application Creating Procedures
When using Visual Basic .NET
The following describes the creation procedures when using Visual Basic .NET.

Power on the personal computer and start Windows.

Install MX Component Version 4. (1)

Program setting type

Select the setting type.

Utility setting type

4
Yes Start Visual Basic .NET.
Use labels.

No Add controls to Visual Basic .NET. (5)

Start Label Utility, and create and
register labels.
Create a form and paste the controls.
(4) (ActProgType)
Start Communication Setup Utility and set the communication Start Communication Setup Utility and set the communication
settings by following the instructions of wizard. (2)(3) settings by following the instructions of wizard.
Set the property of the pasted controls. (3)
Start Visual Basic .NET. Start Visual Basic .NET.

Add controls to Visual Basic .NET. (5) Add controls to Visual Basic .NET. (5)

Create a form and paste the controls. Create a form and paste the controls.
(ActUtlType) (DotUtlType)

Set the property (logical station number) Set the property (logical station number)
of the pasted controls. (3) of the pasted controls. (3)

Create a program using the functions supported by (5)

corresponding controls.

Debug the program using PLC Monitor Utility. (5)

Completion of user application

(1) Page 53 INSTALLATION AND UNINSTALLATION

(2) Page 92 Communication Setup Utility
(3) Page 134 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE
(4) Page 121 Label Utility
(5) MX Component Version 4 Programming Manual

4 OPERATION PROCEDURES
4.3 User Application Creating Procedures 65
 When using Visual C++ .NET
The following describes the creation procedures when using Visual C++ .NET.

Power on the personal computer and start Windows.

Install MX Component Version 4. (1)

Program setting type

Select the setting type.

Utility setting type

Yes Start Visual C++ .NET.

Use labels.

No Add controls to Visual C++ .NET.

Start Label Utility, and create and
register labels. (5)
Create a form and paste the controls.
(4) (ActProgType)
Start Communication Setup Utility and set the communication Start Communication Setup Utility and set the communication
settings by following the instructions of wizard. (2) (3) settings by following the instructions of wizard.
Define the pasted controls as dialog
Start Visual C++ .NET. Start Visual C++ .NET. members using Class Wizard.

Add controls to Visual C++ .NET. Add controls to Visual C++ .NET. Set the property of the pasted controls. (3)

(5) (5)
Create a form and paste the controls. Create a form and paste the controls.
(ActUtlType) (DotUtlType)

Define the pasted controls as dialog Define the pasted controls as dialog
members using Class Wizard. members using Class Wizard.

Set the property (logical station number) (3) Set the property (logical station number) (3)
of the pasted controls. of the pasted controls.

Create a program using the functions supported by

(5)
corresponding controls.

Debug the program using PLC Monitor Utility.

(5)

Completion of user application

(1) Page 53 INSTALLATION AND UNINSTALLATION

(2) Page 92 Communication Setup Utility
(3) Page 134 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE
(4) Page 121 Label Utility
(5) MX Component Version 4 Programming Manual

4 OPERATION PROCEDURES
66 4.3 User Application Creating Procedures
When using Visual C# .NET
The following describes the creation procedures when using Visual C# .NET.

Power on the personal computer and start Windows.

Install MX Component Version 4. (1)

Program setting type

Select the setting type.

Utility setting type

Yes Start Visual C# .NET.

Use labels.

No Add controls to Visual C# .NET. (5)

4
Start Label Utility, and create and
register labels.
Create a form and paste the controls.
(4) (ActProgType)
Start Communication Setup Utility and set the communication Start Communication Setup Utility and set the communication
settings by following the instructions of wizard. (2) (3) settings by following the instructions of wizard.
Set the property of the pasted controls. (3)

Start Visual C# .NET. Start Visual C# .NET.

Add controls to Visual C# .NET. (5) Add controls to Visual C# .NET. (5)

Create a form and paste the controls. Create a form and paste the controls.
(ActUtlType) (DotUtlType)

Set the property (logical station number) Set the property (logical station number)
(3) (3)
of the pasted controls. of the pasted controls.

Create a program using the functions supported by

corresponding controls. (5)

Debug the program using PLC Monitor Utility. (5)

Completion of user application

(1) Page 53 INSTALLATION AND UNINSTALLATION

(2) Page 92 Communication Setup Utility
(3) Page 134 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE
(4) Page 121 Label Utility
(5) MX Component Version 4 Programming Manual

4 OPERATION PROCEDURES
4.3 User Application Creating Procedures 67
 When using VBA
The following describes the creation procedures when using VBA.

Power on the personal computer and start Windows.

Install MX Component Version 4. (1)

Program setting type

Select the setting type.

Utility setting type

Start Communication Setup Utility and set the communication

(2) (3) Start Excel or Access.
settings by following the instructions of wizard.

Start Excel or Access. Start Visual Basic Editor and create an (4)
application.

Start Visual Basic Editor and create an (4) Form the controls to be used in VBA.
application. (ActProgType)

Form the controls to be used in VBA. Set the property of the formed controls. (3)
(ActUtlType)

Set the property of the formed controls. (3)

(Set the logical station number only.)

Create a program using the functions supported by (4)

corresponding controls.

Debug the program using PLC Monitor Utility. (4)

Completion of user application

(1) Page 53 INSTALLATION AND UNINSTALLATION

(2) Page 92 Communication Setup Utility
(3) Page 134 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE
(4) MX Component Version 4 Programming Manual

4 OPERATION PROCEDURES
68 4.3 User Application Creating Procedures
When using VBScript
The following describes the creation procedures when using VBScript.

Power on the personal computer and start Windows.

Install MX Component Version 4. (1)

Program setting type

Select the setting type.

Utility setting type

Start Communication Setup Utility and set the communication (2) (3) Create a website using the text editor
settings by following the instructions of wizard. and the HTML editor.

Create a website using the text editor

On the website, form the controls for
4
and the HTML editor. (4)
MX Component controls to be used in
VBScript. (ActProgType)
On the website, form the controls for
MX Component controls to be used in (4)
VBScript. (ActUtlType) Set the property of the formed controls. (3)

Set the property of the formed controls.

(3)
(Set the logical station number only.)

Create a program using the functions supported by

corresponding controls. (4)

Debug the program using PLC Monitor Utility. (4)

Completion of user application

(1) Page 53 INSTALLATION AND UNINSTALLATION

(2) Page 92 Communication Setup Utility
(3) Page 134 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE
(4) MX Component Version 4 Programming Manual

For starting the Internet/intranet environment, refer to the following appendix.

Page 384 How to Configure Internet/Intranet Environment

4 OPERATION PROCEDURES
4.3 User Application Creating Procedures 69
 4.4 PLC Monitor Utility Operating Procedure
The following is the PLC Monitor Utility operating procedure.

Start

Program setting type

Select the setting type.

Utility setting type

Start Communication Setup Utility and set

the communication settings by following the (2) (4) Start PLC Monitor Utility.
instructions of wizard.

After the transfer setting screen is

Start PLC Monitor Utility. displayed, select the program setting type. (1) (3)

After the transfer setting screen is (1) (3) Press the wizard button on the transfer
displayed, select the utility setting type. setting screen and set the target setting.

Select the logical station number set on

Communication Setup Utility. Is connection
destination correct? No Click the image diagram of the location you
(Look at the connection image (3) (5)
want to correct, and make setting again.
diagram to check)
Yes

Select the monitor from among three

tabs according to the application. (3)

Press the monitor start button.

Monitor execution

(1) Page 88 STARTING AND EXITING UTILITIES

(2) Page 92 Communication Setup Utility
(3) Page 109 PLC Monitor Utility
(4) Page 134 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE
(5) Page 264 COMMUNICATION SETTING EXAMPLES OF PROGRAM SETTING TYPE

4 OPERATION PROCEDURES
70 4.4 PLC Monitor Utility Operating Procedure
5 SYSTEM LABELS
System labels are labels that can be used with sharing them with multiple projects by opening devices of programmable
controller projects and motion controller projects as system labels.
Therefore, programming efficiency is improved.
As the device assignment settings are changed in bulk, device assignment changes on applications are not required.

5.1 Using System Labels

Register a label using Label Utility of MX Component, and use it from controls.

Act.LogifalNumber=1;
Act.Open();
ret=Act.GetDevice("Temperature", Data); User application

5
Act.Close();
Microsoft
Visual Basic Visual C++ Visual C#
Excel

MX Sheet

MX Component
Label Utility
Syetem label
Data base

The following section explains the usage of system label.

The procedure shown below with the screens are of Windows 7, it may differ depending on the operating system.

• System labels
Define labels one-to-one with devices, and register the labels.
Structure can be used. Structure consists of aggregate of various devices.
Set data types. Any data types can be set as array.
System labels used in MELSOFT Navigator can be utilized in MX Component.
• System label data base
A system label data base is a data base to manage system labels.
• System label Ver.2
The labels can be registered to system label Ver.2 using MX Component Version 4.07H or later.
Structure labels and array labels can also be registered.
System label structure of up to five-level can be used by MX Component Version 4.11M or later.

5 SYSTEM LABELS
5.1 Using System Labels 71
 Register system labels in MX Component
Register a system label with Label Utility.

Register system labels

Operating procedure
1. Select [Start]  [All Programs]  [MELSOFT]  [MX
Component]  [Label Utility].
Label Utility starts.

2. Right-click "Undefined_name" on the LabelSpace

window, and select [Rename LabelSpace]. (Page
121 Operations on Label screen)
Change the LabelSpace name.

3. Right-click "System Label List" on the Navigation

window, and select [System Label List]  [New].
(Page 124 System label list)
Set the system label list name.

5 SYSTEM LABELS
72 5.1 Using System Labels
Select the set system label list name to display the system
label list.

4. Set system label names, data types, and devices.

(Page 124 System label list)

5. Right-click "Logical Station Number" on the Navigation 5

window, and select [Logical Station Number]  [Regist].
(Page 123 Registering/deleting logical station
numbers)

6. Select a logical station number, and click the [OK]

button. (Page 123 Registering/deleting logical
station numbers)
For setting the communication settings, click the
[Communication Settings] button, and set the settings
with Communication Setting Wizard.
(Page 98 Operations on Communication Setting
Wizard screens)

5 SYSTEM LABELS
5.1 Using System Labels 73
 The logical station number is displayed on the Navigation
window.

7. Select [Menu]  [Save LabelSpace].

(Page 121 Operations on Label screen)
The system label is registered.

8. Select [Menu]  [Refresh system label data for Control].

(Page 132 Updating system label data)
The labels referred from controls are updated.

Registration complete

5 SYSTEM LABELS
74 5.1 Using System Labels
Deleting system labels
Operating procedure
1. Select "Delete" for a system label to be deleted.

2. Select [Menu]  [Save LabelSpace].

(Page 121 Operations on Label screen)
The system label is deleted.

3. Select [Menu]  [Refresh system label data for Control].

(Page 132 Updating system label data)
The labels referred from controls are updated.

Deletion complete

5 SYSTEM LABELS
5.1 Using System Labels 75
 Registering system labels (structured data type)
Operating procedure
1. Select [Start]  [All Programs]  [MELSOFT]  [MX
Component]  [Label Utility].
Label Utility starts.

2. Right-click "Undefined_name" on the LabelSpace

window, and select [Rename LabelSpace]. (Page
121 Operations on Label screen)
Change the LabelSpace name.

3. Right-click "Structured Data Types" on the Navigation

window, and select [Structured Data Types]  [New].
(Page 129 Setting Structure)
Set the structure name.

5 SYSTEM LABELS
76 5.1 Using System Labels
Select the set structure name to display the structure setting
list.

4. Set label names and data types for structure member.

(Page 129 Setting Structure)

5. Right-click "System Label List" on the Navigation 5

window, and select [System Label List]  [New].
(Page 124 System label list)
Set the system label list name.

Select the set system label list name to display the system
label list.

6. Set system label names and data types.

(Page 124 System label list)
Click "Detail Setting" on the "Device" column of the
system label list.

5 SYSTEM LABELS
5.1 Using System Labels 77
 7. Specify a device.

8. Select [Menu]  [Save LabelSpace].

(Page 121 Operations on Label screen)
The system label is registered.

9. Select [Menu]  [Refresh system label data for Control]

(Page 132 Updating system label data)
The labels referred from controls are updated.

Registration complete

5 SYSTEM LABELS
78 5.1 Using System Labels
Utilizing labels used in MELSOFT Navigator
Refer a system label from existing Workspace, and register it with Label Utility.

Operating procedure
1. [Start]  [All Programs]  [MELSOFT]  [MX
Component]  [Label Utility].
Label Utility starts.

2. Right-click "Undefined_name" on the LabelSpace

window, and select [Rename LabelSpace]. (Page
121 Operations on Label screen)
Change the LabelSpace name.

3. Right-click "Reference Workspace" on the Navigation

window, and select [Workspace]  [Reference
Registration].
(Page 130 Referring and registering/canceling
Workspaces)

5 SYSTEM LABELS
5.1 Using System Labels 79
 4. Select a Workspace that is to be referred and
registered. (Page 130 Referring and registering/
canceling Workspaces)

The referred and registered Workspace name is displayed on

the Navigation window.
Select the system label name to display the referred system
label list.

5. Select [Menu]  [Save LabelSpace]

(Page 121 Operations on Label screen)
The system label is registered.
For referring more than one Workspace, add
LabelSpace first, and operate the procedure 2 to 4.

5 SYSTEM LABELS
80 5.1 Using System Labels
 6. Select [Menu]  [Refresh system label data for Control]
(Page 132 Updating system label data)
The labels referred from controls are updated.

Registration complete 5

5 SYSTEM LABELS
5.1 Using System Labels 81
 Applying device settings changed in GX Works2 to MX
Component
Update the settings with Label Utility after changing the device assignment settings of referred and registered system labels
with GX Works2.

Operating procedure
1. Select [Start]  [All Programs]  [MELSOFT]  [MX
Component]  [Label Utility].
Label Utility starts.

The system label notification icon is displayed on the status

bar of Label Utility.

2. Select the LabelSpace name.

System label notification icon

3. Right-click the system label notification icon, and select

[Change Contents of System Label Database].
(Page 131 Change notification)

4. Click the [Yes] button.

5 SYSTEM LABELS
82 5.1 Using System Labels
 Select the system label list name to display the system label
list.

5. Select [Menu]  [Save LabelSpace].

(Page 121 Operations on Label screen) 5
The system label is registered.
For referring more than one Workspace, select
LabelSpace from the LabelSpace window first, and
operate the procedure 2 to 4.

The system label notification icon is displayed while referring

more than one Workspace.

6. Select [Menu]  [Refresh system label data for Control]

(Page 132 Updating system label data)
The labels referred from controls are updated.

Registration complete

The system label notification icon is not displayed when the system labels are used without referring and
registering the Workspace.

5 SYSTEM LABELS
5.1 Using System Labels 83
 Using System Labels on another personal computer
Export a LabelSpace, and import it to another personal computer to use a system label.

Exporting LabelSpaces
Export a LabelSpace, and create a file.

Operating procedure
1. Select [Start]  [All Programs]  [MELSOFT]  [MX
Component]  [Communication Setup Utility].
Communication Setup Utility starts.

2. Select [Menu]  [COM setup export].

(Page 97 Exporting communication settings)

3. Enter the file name to be saved.

4. Select [Start]  [All Programs]  [MELSOFT]  [MX

Component]  [Label Utility].
Label Utility starts.

5 SYSTEM LABELS
84 5.1 Using System Labels
 5. Select [Menu]  [Export].
(Page 132 Exporting LabelSpace)

6. Enter the file name to be saved.

5

Registration complete

5 SYSTEM LABELS
5.1 Using System Labels 85
 Importing LabelSpaces
Import an exported file to LabelSpace of another personal computer.
Copy the exported files of the communication setting and the LabelSpace to the personal computer to be imported
beforehand.

Operating procedure
1. Select [Start]  [All Programs]  [MELSOFT]  [MX
Component]  [Communication Setup Utility].
Communication Setup Utility starts.

2. Select [Menu]  [COM setup import].

(Page 96 Importing communication settings)

3. Specify the file name of communication setting to be

imported.

4. Select [Start]  [All Programs]  [MELSOFT]  [MX

Component]  [Label Utility].
Label Utility starts.

5 SYSTEM LABELS
86 5.1 Using System Labels
 5. Select [Menu]  [Import].
(Page 133 Importing LabelSpace)

5
6. Specify the file name of LabelSpace to be imported.

7. Select [Menu]  [Refresh system label data for Control]

(Page 132 Updating system label data)
The labels referred from controls are updated.

Registration complete

5 SYSTEM LABELS
5.1 Using System Labels 87
 6 STARTING AND EXITING UTILITIES
This chapter explains how to start and exit the utilities.

6.1 Starting Utilities

Operating procedure
Select [Start]  [All Programs]  [MELSOFT]  [MX Component]*1.
*1Does not appear in Windows 8 or later.
For the registered icons, refer to the following section.
Page 61 Registered Icons

Window

Starts Communication Setup Utility.

Starts Label Utility.

Starts PLC Monitor Utility.

Administrator authority when executing each utility

Administrator authority
When Label Utility is executed, the status is switched to the administrator authority automatically.
When executing Communication Setup Utility and PLC Monitor Utility, the performance differs according to the user account
control (UAC) settings.

■When user account control (UAC) is enabled

All users including administrator are fixed at and operate as "standard user".
To execute programs with administrator authority, specify "Run as administrator".

■When user account control (UAC) is disabled

Programs can be executed by login user.

6 STARTING AND EXITING UTILITIES

88 6.1 Starting Utilities
Operating procedure for administrator authority
The following shows a procedure to execute Communication Setup Utility with the administrator authority when UAC is
enabled.
(The procedure is also applied to PLC Monitor Utility.)

Operating procedure
1. Select [Communication Setup Utility], right-click, and
select [Run as administrator] for execution.

<Windows 7 or later> For administrator users, the message shown on the left is
displayed.

2. Click the [Yes] button or "Allow" to execute a program

with the administrator authority.
Click the [No] button or "Cancel" to cancel the
execution.

<Windows Vista>

Setting complete

6 STARTING AND EXITING UTILITIES

6.1 Starting Utilities 89
 Setting to always execute programs as an administrator
Set the following setting to "Run as administrator" at all times.
(The procedure is also applied to PLC Monitor Utility.)

Operating procedure
1. Select [Communication Setup Utility], right-click, and
select [Properties].

<Windows 7 or later> 2. Select the [Compatibility] tab, and select "Run this
program as an administrator" of "Privilege Level".

Setting complete

6 STARTING AND EXITING UTILITIES

90 6.1 Starting Utilities
6.2 Exiting Utilities

Communication Setup Utility

Operating procedure
• Select [Menu]  [Exit Communication Setup Utility].
• Click the [Exit] button at bottom right of the screen.

PLC Monitor Utility

Operating procedure
• Select [Menu]  [Exit PLC Monitor Utility].
• Click the [Exit] button at bottom right of the screen.

Label Utility
Operating procedure 6
Select [Menu]  [Exit].

6.3 Confirming Version

Operating procedure
Select [Help]  [About].

6 STARTING AND EXITING UTILITIES

6.2 Exiting Utilities 91
 7 UTILITY OPERATIONS
This chapter explains how to operate each utility.

For communication setting examples using Communication Setup Utility, refer to the following chapter.
Page 134 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

7.1 Communication Setup Utility

This section explains how to operate and set Communication Setup Utility used to perform communication with the utility
setting type.

7 UTILITY OPERATIONS
92 7.1 Communication Setup Utility
Operations on Target setting tab
This tab is used to display the setting details of the logical station number set on Communication Setting Wizard and to edit.

Window

Connection image
diagram

7
Item Description
Logical station number Select the logical station number to display and edit the setting details set on Communication Setting Wizard.
[Wizard] button Start Communication Setting Wizard and set the logical station number.
[Delete] button Delete the preset logical station number.
Connection image diagram Display the connection image diagram of the selected logical station number.
Click any sketch (personal computer, programmable controller CPU) in the connection image diagram to start the
Communication Setting Wizard, and the settings can be changed.

For details of Communication Setting Wizard, refer to the following section.

Page 98 Operations on Communication Setting Wizard screens

7 UTILITY OPERATIONS
7.1 Communication Setup Utility 93
 Operations on List view tab
This tab is used to list and edit the registered logical station number, and list the properties required for the program setting
type.

Window

Property list

Item Description
Property list Display the settings of the registered logical station numbers.
Double-clicking the logical station number starts Communication Setting Wizard.
[Wizard] button Start Communication Setting Wizard and set the logical station number.
[Delete] button Delete the preset logical station number.
Display Utility : Display the settings set for the logical station numbers in the property list.
Program: Display the property list required for setting with the program setting type.
[Save text] button Save the settings of property list into a file in the .txt format.

For details of Communication Setting Wizard, refer to the following section.

Page 98 Operations on Communication Setting Wizard screens

7 UTILITY OPERATIONS
94 7.1 Communication Setup Utility
Operations on Connection test tab
This tab is used to conduct a communication test on the registered logical station number.

Window

Item Description
Logical station number Select the logical station number on which a communication test will be performed.
Communication diagnosis count Set how many times (1 to 32767) the communication test will be repeated for the specified logical station
number.
[Test] button ([Cancel] button) Start (stop) the communication test.
When the logical station number where the modem communication data are set is selected, the following
screen is displayed after [Test] button is clicked.
When the password is set, enter the password and click the [OK] button.

Result Diagnosis count Display the number of connections during the communication test.
Result Display the test result. An error code is displayed at error occurrence. 0 is displayed at normal termination, or
any value other than 0 is displayed at abnormal termination.
CPU name Display the connected CPU type.
Mean time of Display the average time taken until one communication test is established. (Unit: ms)
communication

7 UTILITY OPERATIONS
7.1 Communication Setup Utility 95
 Importing communication settings
Apply the exported communication settings saved to the file (Page 97 Exporting communication settings) to the utility.
This screen is used when the communication settings set on another personal computer are to be applied to the personal
computer being used.

Operating procedure
Select [Menu]  [COM setup import].

Window

To import the communication settings, use MX Component of a version of the one used for export, or later.
Using a MX Component version earlier than that may cause incorrect import.

7 UTILITY OPERATIONS
96 7.1 Communication Setup Utility
Exporting communication settings
Save the communication settings set on the personal computer in a file. (The file where data are saved is called the ACT
registered file.)
This screen is used to apply the communication settings on another personal computer.

• Uninstalling deletes all the settings within "Communication Setup Utility".

• To avoid this, export the file storing the settings.
• When importing a file using Communication Setup Utility with MX Component Version 4.11M or earlier, a file
of which '*.act' is selected when saving the file can be used.

Operating procedure
Select [Menu]  [COM setup export].

Window

7 UTILITY OPERATIONS
7.1 Communication Setup Utility 97
 Operations on Communication Setting Wizard screens
These screens are used to set the logical station number required to perform communication with the utility setting type.

Outline of Communication Setting Wizard

The logical station number required to perform communication with the utility setting type is set with the wizard.
The following are the places and descriptions of the settings set on the Communication Setting Wizard screens.
For the wizard screen settings, refer to the following section.
Page 99 Explanation of Communication Setting Wizard screens

Wizard (1), (6) Wizard (3) Wizard (5)

Connected station Relayed station

Personal computer

MX
Component

Connected network Relayed network

Wizard (2) Wizard (4)

Screen Name Description

Wizard (1) Set the logical station number.
Wizard (2) Set the connected network between the personal computer and connected station (programmable controller CPU and module).
Wizard (3) Set the connected station (programmable controller CPU and module).
Wizard (4) Set the relayed network between the connected station (programmable controller CPU and module) and relayed station
(programmable controller CPU and module).
Wizard (5) Set the relayed station programmable controller CPU.
Wizard (6) Comment the logical station number.

Starting procedure
Operating procedure
• Select [Menu]  [Wizard].
• Click the [Wizard] button on the utility screen.

7 UTILITY OPERATIONS
98 7.1 Communication Setup Utility
Explanation of Communication Setting Wizard screens
Communication Setting Wizard screens are shown from wizard (1) to wizard (6) in order.
The following explains Communication Setting Wizard screens in displayed order.

• The displays or available setting items of Communication Setting Wizard screens differ depending on the
communication settings.
Set all available setting items being displayed.
• Some of Communication Setting Wizard screens may not be displayed depending on the settings.

Operating procedure
Start Communication Setting Wizard. 1. Enter or select the logical station number and click
[Next] the button.
The logical station number can be registered from 0 to
Wizard (1) 1023.

Wizard (2) 2. Select "PC side I/F" to communicate with.

The items shown in "Communication setting" differ
depending on the setting set in "PC side I/F".
Set all available setting items and click the [Next] button.
The following table indicates the items corresponding to
the communications in "PC side I/F".
Page 101 Items corresponding to the
communications in "PC side I/F"

7 UTILITY OPERATIONS
7.1 Communication Setup Utility 99
 Wizard (3) 3. Wizard (3) differs in available setting items depending
on the settings on Wizard (2).
Set all available setting items and click the [Next] button.
When via GOT is selected on Wizard (2), the following
screen is displayed. (Wizard (3) differs in available
setting items depending on the settings on Wizard (2).)
Set all available setting items and click the [Next] button.

Wizard (4) 4. Wizard (4) differs in available setting items depending

on the settings on Wizard (2) and Wizard (3).
Set all available setting items and click the [Next] button.
When the modem is selected on Wizard (2), the
"Connect Line" screen is displayed between Wizard (3)
and Wizard (4).
For details on the "Connect Line" screen, refer to the
following section.
Page 102 Operations on Connect Line screen

Wizard (5) 5. Wizard (5) differs in available setting items

depending on the settings on Wizard (2), Wizard (3) and
Wizard (4).
Set all available setting items and click the [Next] button.

7 UTILITY OPERATIONS
100 7.1 Communication Setup Utility
Wizard (6) 6. Comment the logical station number being set.
The maximum number of characters for comment is 32.
Enter a comment and click [Finish] button.
If a comment is not required, click the [Finish] button
without entering it.

Setting completion
When the registration of the logical station number is completed on Communication Setting Wizard, the settings are displayed
on the [Target setting] tab.

<Before registration> <After registration>

■Items corresponding to the communications in "PC side I/F"

Setting Item Communication Name
USB USB communication
USB (via GOT) GOT transparent communication
Serial Serial communication, CPU COM communication, CC-Link G4 communication
Serial (via GOT) GOT transparent communication
Ethernet board Ethernet communication, Gateway function communication
Ethernet (via GOT) GOT transparent communication
Modem Modem communication
CC IE Control board CC-Link IE Controller Network communication
MELSECNET/H board MELSECNET/H communication
CC IE Field board CC-Link IE Field Network communication
CC-Link board CC-Link communication
Q Series Bus Q Series bus communication
GX Simulator3 GX Simulator3 communication
GX Simulator2 GX Simulator2 communication
GX Simulator GX Simulator communication
MT Simulator2 MT Simulator2 communication

7 UTILITY OPERATIONS
7.1 Communication Setup Utility 101
 Operations on Connect Line screen
This screen is used to set the telephone line settings required to set modem communication in Communication Setup Utility.

Connect Line screen

Set the line connection system, telephone line, AT command, and the like.

Window

Item Description Reference

Connect way Set the line connection system. 
When Q series-compatible C24 or L series-compatible C24 is used any of the following
items can be selected.
(Fixed to "Auto line connect" when FXCPU is used.)
Page 103 Selection items for "Connect way"
Callback number Set the telephone number used with the callback function of Q series-compatible C24 and 
L series-compatible C24.
This item can be set only when "Auto line connect (Callback number specification)",
"Callback connect (Number specification)" or "Callback connect (Number specification)" is
selected in the line connection system.
Line Line type Select a line type: Tone, Pulse, or ISDN. 
Outside line Set the number as required when calling through the outside line. 
number
Port Select the COM port number which is connected to the modem. 
Connection Set the phone number of the target. Page 104 Setting TEL
The previously-registered phone numbers in the telephone directory can be specified by data
clicking the [Browse] button.
AT command Modem standard Use the AT command set on the modem. 
AT command When a difficulty of line connection occurs using the standard AT command, create an AT Page 106 Registering
setting command with referring to the manual of the modem and the content displayed by clicking AT commands
the [Help of AT command] button.
[Details setting] button Display the "Detail setting" screen. Page 108 Details
setting screen

7 UTILITY OPERATIONS
102 7.1 Communication Setup Utility
■Selection items for "Connect way"
Item Description
Auto line connect Select this when the callback function is not set.
Auto line connect (Callback fixation) For details on the connection format of each callback function, refer to the following
manual.
Auto line connect (Callback number specification)
MX Component Version 4 Programming Manual
Callback connect (Fixation)
Callback connect (Number specification)
Callback request (Fixation)
Callback request (Number specification)
Callback reception waiting

7 UTILITY OPERATIONS
7.1 Communication Setup Utility 103
 Setting TEL data
Set the telephone numbers used on the "Connect Line" screen.

List of registered
phone numbers

Displayed items
Item Description
List of registered phone numbers Display group names and user names of phone numbers.
Display cursor position Display the registered information of the data selected on the list of registered phone numbers.
[New group] button Create a new group.
The "Group setting" screen is displayed by clicking the [New group] button.
Enter a group name. The maximum number of characters that can be set is 50.
[Edit] button Edit the registered data.
Select a registered data to be edited on the "list of registered phone numbers".
The "Call number setting" screen is displayed by clicking the [Edit] button.
Edit the data.
[Copy] button Copy a registered phone number to another group.
Select the registered data to be copied on the "list of registered phone numbers".
The "Group" screen is displayed by clicking the [Copy] button.
Select the group to which data is pasted, and click the [OK] button.
[Move group] button Move a registered phone number to another group.
Select the registered data to be moved on the "list of registered phone numbers".
The "Group" screen is displayed by clicking the [Move group] button.
Select the group to which data is moved, and click the [OK] button.
[Delete] button Delete a registered group and phone number. Data cannot be deleted in bulk in group unit.
[Find] button Search for a registered phone number. The search condition is a partial match.
Target data is searched from all registered data. When entering search conditions to both "Destination Name" and
"Phone Number", the data which satisfies the both search conditions is searched.
[Select] button Perform a selection processing of phone number setting when referring from the "Connect Line" screen.
[Read file] button Read phone number data from the specified file and add it to the directory.
To replace the data with the read phone number data, execute the read file function after deleting all groups and
phone numbers.
[Write file] button Write the data set on the "AT command registration" screen to the specified file.

7 UTILITY OPERATIONS
104 7.1 Communication Setup Utility
 Operating procedure
1. Select a group for which the phone number to be registered on the "list of registered phone numbers".

2. Click the [New call number] button.

The "Call number setting" screen is displayed.

3. Set the items on the screen.

Item Description
Group name Display the group name to which the information is registered. 7
Destination name Enter the name of the phone number to be set.
The maximum number of characters that can be set is 50.
Call number Enter the phone number. The maximum number of characters that can be set is 50.
Outside line number Set the outside line number. The maximum number of characters that can be set is 10.
For only line connection When a password is set for Q series-compatible C24 or L series-compatible C24, this setting enables to process the password
authorization automatically to connect the line.
Comment Enter notes on the registered information.
The maximum number of characters that can be set is 60.

4. Click the [OK] button.

The phone number is registered.

The phone book created using GX Developer can be read in MX Component.

The phone book of GX Developer is stored in the following folders.
[User-specified folder] - [Gppw]

7 UTILITY OPERATIONS
7.1 Communication Setup Utility 105
 Registering AT commands
Set the AT commands used on the "Connect Line" screen.

List of registered
AT commands

Displayed items
Item Description
List of registered AT commands Display titles of AT commands.
Display cursor position Display the registered information of the data selected on the list of registered AT commands.
[Edit] button Edit the registered data.
Select the registered data to be edited on the "list of registered AT commands".
The "AT command registration" screen is displayed by clicking the [Edit] button.
Edit the data.
[Copy] button Copy a registered AT command to another group.
Select the registered data to be copied on the "list of registered AT commands".
The "Group" screen is displayed by clicking the [Copy] button.
Select the group (to which data is pasted), and click the [OK] button.
[Move group] button Move a registered AT command to another group.
Select the registered data to be moved on the "list of registered AT commands".
The "Group" screen is displayed by clicking the [Move group] button.
Select the group (to which data is moved), and click the [OK] button.
[Delete] button Delete a registered AT command.
[Select] button Perform a selection processing of AT command when referring from the "Connect Line" screen.
[Read file] button Read AT command from the specified file and add it to the directory.
To replace the commands with the read AT commands, execute the read file function after deleting all AT commands.
[Write file] button Write data set on the "AT command registration" screen to the specified file.

7 UTILITY OPERATIONS
106 7.1 Communication Setup Utility
 Operating procedure
1. Select "Modem at MELSOFT application side" on the list of registered AT commands.

2. Click the [New AT command] button.

The "AT command registration" screen is displayed.

3. Set the items on the screen.

Item Description
Group name Display the newly created group name.
Title Enter a title for the AT command to be registered.
AT command Set the command for modem initialization. The maximum number of characters that can be entered is 70 in ASCII code.

4. Click the [OK] button.

7
The AT command is registered.

The AT commands created using GX Developer can be read in MX Component.

The AT commands of GX Developer are stored in the following folders.
[User-specified folder] - [Gppw]

7 UTILITY OPERATIONS
7.1 Communication Setup Utility 107
 Details setting screen
Set details for telephone line connection.
Set the settings according to the modem used.

Window

Item Description
Line connection CD signal wait time Set the line connection CD signal confirmation time. (1 to 999 seconds)
Increase the set time if the CD signal does not turn ON within the set time depending on the line-connected
region (example: overseas).
Line connection modem report wait time Set the line connection modem report wait time. (1 to 999 seconds)
Increase the set time if the response speed of the modem is low.
Line disconnection CD signal wait time Set the line disconnection CD signal confirmation time. (1 to 999 seconds)
Increase the set time if the CD signal does not turn OFF within the preset time depending on the line-connected
region (example: overseas).
Line disconnection delay time Set the line disconnection delay time. (1 to 999 seconds)
Increase the set time if the response speed of the modem is low.
Data transmission delay time Set the data transmission delay time. (1 to 999 seconds)
Increase the set time if the response speed of the modem is low.
AT command response wait time Set the AT command response wait time. (1 to 999 seconds)
Increase the set time if the response speed of the modem is low.
Password cancellation response wait time Set the password cancellation response wait time. (1 to 999 seconds)
Increase the set time if the quality of the line with the other end is low.
AT command/password cancellation retry Set the AT command/password cancellation retry count. (1 to 999 times)
times Increase the set count if the AT command cannot be sent or the password cannot be canceled.
Line callback cancel wait time Set the Line callback cancel wait time. (1 to 180 seconds)
Increase the set time if the line at the other end (Q series-compatible C24 side) is not disconnected within the
set time depending on the line-connected region (example: overseas).
Call back delay time Set the callback delay time. (1 to 999 seconds)
Increase the set time if the device for relaying connection to the line (example: modem, etc.) requires the set
time for reconnection after line disconnection.
Call back reception waiting time-out Set the callback reception waiting time-out. (1 to 3600 seconds)
Increase the set time if a time-out occurs in a callback receive waiting status.

7 UTILITY OPERATIONS
108 7.1 Communication Setup Utility
7.2 PLC Monitor Utility
This section explains how to operate and set PLC Monitor Utility.

Operations on Transfer setting screen

This screen is used to set connection from the personal computer to the programmable controller CPU.

Operating procedure
Select [Online]  [Transfer setting].
(This screen is also displayed when PLC Monitor Utility is started.)

When selecting the utility setting type

Window

Item Description
Utility setting type Select this to set the transfer setting using the logical station number set on Communication Setup Utility.
Logical station number Select the logical station number set on Communication Setup Utility.
When the logical station number where the modem communication data are set is selected, the following screen is displayed
after the [OK] button is clicked.
When the password is set, enter the password and click the [OK] button.

Connect Retry Times Set the number of retries (0 to 9) to be performed when an error occurs during monitoring with PLC Monitor Utility.

Before specifying the logical station number, confirm that the settings of the logical station number, (the CPU
type, station number, or the like) are correct on Communication Setup Utility.

7 UTILITY OPERATIONS
7.2 PLC Monitor Utility 109
 When selecting the program setting type
Window

Item Description
Program setting type Select when the program setting type is used to create programs.
[Wizard] button Start Communication Setting Wizard and set the transfer setting.
When the modem communication data is set on Communication Setting Wizard, the following screen is displayed after the
[OK] button is clicked.
When the password is set, enter the password and click the [OK] button.

Connect Retry Times Set the number of retries (0 to 9) to be performed when an error occurs during monitoring with PLC Monitor Utility.

7 UTILITY OPERATIONS
110 7.2 PLC Monitor Utility
When the program setting type is selected, the details of the transfer setting can be changed by clicking the
programmable controller or personal computer sketch.

The setting can be changed by

clicking the corresponding portion
of the screen.

7 UTILITY OPERATIONS
7.2 PLC Monitor Utility 111
 Operations on Device Batch tab
This tab is used to monitor the specified device.

Window

(1)

(2) (3) (4)

Item Description
Device Enter the device name to be monitored in batch.
For the X and Y devices of FXCPU and FX5CPU, enter the device number in octal.
[Start monitor] button ([Stop Start (stop) monitor.
monitor] button)
Monitor format Set the monitor format.
■Item
Bit&Word: Set the monitor screen to the bit and word display.
Bit: Set the monitor screen to the bit display only.
Word: Set the monitor screen to the word display only.
Display Set the display format of the device values to be displayed when the monitor format is "Bit&Word" or "Word".
■Item
16bit integer: Set to the 16-bit integer display.
32bit integer: Set to the 32-bit integer display.
Real number (single precision): Set to the real number (single precision) display.
Real number (double precision): Set to the real number (double precision) display.
ASCII character: Set to the ASCII character string display.
Data format Set the radix when the display is "16 bit integer" or "32 bit integer".
■Item
DEC: Set to the decimal display.
HEX: Set to the hexadecimal display.
Bit order Set the order of the bit devices being monitored.
■Item
F-0: Display in order of F, E, ... 1, 0 from left to right.
0-F: Display in order of 0, 1, ... E, F from left to right.
(1) Monitor screen Display the device status.
• For the bit device status, 1 indicates an ON status and 0 an OFF status.
• Bit devices are monitored in units of 16 points.
If any device outside the range supported by the programmable controller CPU is included in the 16 points, its value is
displayed "0".
• For the C devices of FXCPU, C0 to C199 (16 bit) and C200 and later (32 bit) are displayed separately.
The "Write to Device" screen is displayed by clicking the device name. (Page 118 Operations on Write to Device
screen)
"*" flickers under the scroll button during monitoring.
(2) Target CPU name Display the communication target CPU name specified on Communication Setting Wizard.
(3) Communication route Display such information as the network type, network number, start I/O address and station number.
information
(4) Logical station number Display the logical station number set for the utility setting type.
This number is not displayed when the program setting type is used.

7 UTILITY OPERATIONS
112 7.2 PLC Monitor Utility
• Specifying the device memory in the U*\G format enables the buffer memory to be monitored.
• When monitoring the setting values of the timers and counters, indirectly specify the data registers.
• Devices cannot be monitored if the connection destination is not established.
• The transfer settings cannot be set during monitoring.

7 UTILITY OPERATIONS
7.2 PLC Monitor Utility 113
 Operations on Buffer Memory tab
This tab is used to monitor the specified buffer memory.

Window

(1)

(2) (3) (4)

Item Description
Module I/O Enter the start address of the module to be monitored.
For access to FXCPU, enter the block number of the special expansion device into Module I/O.
Memory address Enter the address of the buffer memory to be monitored in hexadecimal or decimal.
[Start monitor] button ([Stop Start (stop) monitor.
monitor] button)
Monitor format Set the monitor format.
■Item
Bit&Word: Set the monitor screen to the bit and word display.
Bit: Set the monitor screen to the bit display only.
Word: Set the monitor screen to the word display only.
Display Set the display format of the device values to be displayed when the monitor format is "Bit&Word" or "Word".
■Item
16bit integer: Set to the 16-bit integer display.
32bit integer: Set to the 32-bit integer display.
Real number (single precision): Set to the real number (single precision) display.
Real number (double precision): Set to the real number (double precision) display.
ASCII character: Set to the ASCII character string display.
Data format Set the radix when the display is "16 bit integer" or "32 bit integer".
■Item
DEC: Set to the decimal display.
HEX: Set to the hexadecimal display.
Bit order Set the order of the bit devices being monitored.
■Item
F-0: Display in order of F, E, ... 1, 0 from left to right.
0-F: Display in order of 0, 1, ... E, F from left to right.
(1) Monitor screen Display the buffer memory status.
For the bit device status, 1 indicates an ON status and 0 an OFF status.
"*" flickers under the scroll button during monitoring.
(2) Target CPU name Display the communication target CPU name specified on Communication Setting Wizard.
(3) Communication route Display such information as the network type, network number, start I/O address and station number.
information
(4) Logical station number Display the logical station number set for the utility setting type.
This number is not displayed when the program setting type is used.

7 UTILITY OPERATIONS
114 7.2 PLC Monitor Utility
• Devices cannot be monitored if the connection destination is not established.
• The transfer settings cannot be set during monitoring.
• Monitoring for FX5CPU are not supported.
• The devices cannot be monitored during gateway function communication.

7 UTILITY OPERATIONS
7.2 PLC Monitor Utility 115
 Operation on Entry Device tab
This tab is used to monitor the specified devices on a single screen at the same time.

Window

(1)

(2) (3) (4)

Item Description
[Register device] button Register the device to be monitored.
The following screen is displayed by clicking the [Register device] button.
Page 117 The "Register device" screen
[Delete device] button Delete the device to be monitored.
[Clear device] button Delete all devices registered in device entry monitor from the monitor screen.
[Start monitor] button Start (stop) monitor.
([Stop monitor] button)
(1) Monitor screen Display the device status.
The "Write to Device" screen is displayed by clicking the device name. (Page 118 Operations on Write to Device screen)
"*" flickers under the scroll button during monitoring.
(2) Target CPU name Display the communication target CPU name specified on Communication Setting Wizard.
(3) Communication route Display such information as the network type, network number, start I/O address and station number.
information
(4) Logical station Display the logical station number set for the utility setting type.
number This number is not displayed when the program setting type is used.

7 UTILITY OPERATIONS
116 7.2 PLC Monitor Utility
The "Register device" screen
The screen is displayed by clicking the [Register device] button.
Register the device to be monitored.

Window

Item Description
Device Enter the device to be registered.
Value Set the value to be entered when a word device is specified.
■Item
DEC: Set to decimal.
HEX: Set to hexadecimal.
Display Set the display format when a word device is specified.
■Item
16bit integer: Set to the 16-bit integer display.
32bit integer: Set to the 32-bit integer display.
Real number (single precision): Set to the real number (single precision) display.
7
Real number (double precision): Set to the real number (double precision) display.
ASCII character: Set to the ASCII character string display.
[Register] button Register the device.
[Close] button Close the dialog box.

• When monitoring the setting values of the timers and counters, indirectly specify the data registers.
• Devices cannot be monitored if the connection destination is not established.
• The transfer settings cannot be set during monitoring.

7 UTILITY OPERATIONS
7.2 PLC Monitor Utility 117
 Operations on Write to Device screen
This screen is used to change the ON/OFF of a bit device or the present value of a word device or buffer memory.

Operating procedure
• Select [Online]  [Device write].
[Device write] cannot be selected when QSCPU is connected.
• Double-click the monitor screen of the corresponding tab.

Window

Item Description
Bit device Device Enter the device name.
[Force ON] button Forcibly change the specified device to the ON status.
[Force OFF] button Forcibly change the specified device to the OFF status.
[Toggle force] button Forcibly change the specified device from the ON to OFF status or from the OFF to ON status.
Word device/Buffer Device Select this to enter the word device to be written.
memory
Buffer memory Select this to enter a module start I/O address and a buffer memory address.
Setting value Enter the value to be written.
The following table indicates the input range.
■Item
16bit integer: -32768 to 32767
32bit integer: -2147483648 to 2147483647
Real number (single precision), Real number (double precision): -999999999999999 to
9999999999999999 Number of significant figures: 13 digits
[Set] button Write the set data.

When using RnSFCPU, you cannot write to the safety device in the safety mode.
MX Component Version 4 Programming Manual

7 UTILITY OPERATIONS
118 7.2 PLC Monitor Utility
Operations on Time setting screen
This screen is used to read or change the clock data of the programmable controller.

Operating procedure
Select [Online]  [Set time].

Window

For QSCPU, the clock data cannot be changed.

Item Description
PC Time Display the time of the personal computer. (Write disabled)
PLC Time Display the time of the programmable controller CPU. 7
[Register] button Write the "PLC Time" information to the programmable controller CPU.
[Close] button Close the "Time setting" screen.

Time setting is not available when either of the following communications is selected.
• GX Simulator communication (Only the time of the personal computer is displayed.)
• Gateway function communication (An error occurs.)

7 UTILITY OPERATIONS
7.2 PLC Monitor Utility 119
 Operations on telephone line connection, disconnection screens
Connect and disconnect the telephone line for modem communication.

Telephone line connection

Operating procedure
1. Select [Online]  [Connect].
[Connect] cannot be selected when RnSFCPU/QSCPU is connected.

2. For telephone line connection, the following dialog box is displayed.

Enter the password and click the [OK] button.

Telephone line disconnection

Select [Online]  [Disconnect].
[Disconnect] cannot be selected when RnSFCPU/QSCPU is connected.

7 UTILITY OPERATIONS
120 7.2 PLC Monitor Utility
7.3 Label Utility
This section explains how to operate and set Label Utility.

Operations on Label screen

Window

LabelSpace
window

Work window

Navigation
window

Task window

Status bar 7
Item Description Reference
LabelSpace window Display the list of LabelSpace. 
The LabelSpace names are displayed on the list in ascending order based on the
date of creation.
Navigation window Display the logical station number, structured data type and system label list of 
LabelSpace in tree format.
Work window Display the system label list and the Structure Setting screen. Page 124 System label list
Page 129 Setting Structure
Task window Display the processing result in list format. 
Status bar Display the current status. Page 131 Change notification

7 UTILITY OPERATIONS
7.3 Label Utility 121
 Basic operations
Operating procedure
■Adding LabelSpace
• Select [Menu]  [Add LabelSpace].
• Right-click the LabelSpace window, and select [Add LabelSpace].
For system label Ver.1, select [Add LabelSpace]. As for system label Ver.2, select [Add LabelSpace Ver.2].

The maximum number of LabelSpaces is 8. Note that the sum of LabelSpaces and referred Workspaces
should be 16 or less.

■Changing LabelSpace name

• Select the LabelSpace name on the LabelSpace window, and select [Menu]  [Rename LabelSpace].
• Right-click the LabelSpace name on the LabelSpace window, and select [Rename LabelSpace].

Up to 64 characters can be used to change the label space name using System label Ver.2.

■Saving LabelSpace
• Select [Menu]  [Save LabelSpace].
• Exit Label Utility.

■Deleting LabelSpace
• Select the LabelSpace name on the LabelSpace window, and select [Menu]  [Delete LabelSpace].
• Right-click the LabelSpace name on the LabelSpace window, and select [Delete LabelSpace].

7 UTILITY OPERATIONS
122 7.3 Label Utility
Registering/deleting logical station numbers

Registration
Register a logical station number to LabelSpace.

Operating procedure
• Select a LabelSpace name on the LabelSpace window, and select [Menu]  [Logical Station Number]  [Regist].
• Select a LabelSpace name on the LabelSpace window, right-click "Logical Station Number" on the Navigation window, and
select [Logical Station Number]  [Regist].

Window

Item Description
Logical Station Number Select the logical station number defined on Communication Setup Utility from the list box.

[Communication Settings]
The logical station number which has already been registered to other LabelSpace is not displayed.
Start Communication Setup Utility.
7
button
[OK] button Register the logical station number, and close the screen.
[Cancel] button Close the screen without registering the logical station number.

Deletion
Delete the logical station number registered to LabelSpace.

Operating procedure
• Select the station number to be deleted from the Navigation window, and select [Menu]  [Logical Station Number] 
[Deregist].
• Right-click the station number to be deleted from the Navigation window, and select [Logical Station Number]  [Deregist].

• After registering the logical station number, save the LabelSpace.

• The logical station number and LabelSpace will be registered on a one-to-one basis.
When the logical station number is registered in some other label space, delete the registered logical station
number from the label space and then register a new one.

7 UTILITY OPERATIONS
7.3 Label Utility 123
 System label list
Register, edit, and browse a system label.

Window

<System label Ver.1> <System label Ver.2>

Item Description Maximum number of

characters
Ver.1 Ver.2
Delete Select the system label to be deleted. 
System Label Enter a desired system label name. 32 characters 256
Name For characters that cannot be used for label names, refer to (Page 417 Character Strings that cannot characters
be Used for Label Names).
Data Type Set a data type from the "Data Type Selection" screen displayed by clicking [...]. (Page 125 Selecting 128 512
data types) characters characters
It can also be entered directly.
Device Set the device to be assigned to system label Ver.1. 50 characters 
The bit-specified word device (D0.1) can be specified.
If the structure is set for data type, "Detail Setting" is displayed.
Set the items on the "Structured Data Device Setting" screen displayed by clicking "Detail Setting".
(Page 127 Assigning devices to structured data type labels, Page 128 Assigning devices to structure
array type labels)
Label Name Enter the label name to be managed by system label Ver.2.  587
characters

Basic operations
Operating procedure
■Adding system label list
• Select a LabelSpace name on the LabelSpace window, and select [Menu]  [System Label]  [System Label List] 
[New].
• Select a LabelSpace name on the LabelSpace window, right-click "System Label List" on the Navigation window, and select
[New].

■Changing system label list name

• Select the system label list name on the Navigation window, and select [Menu]  [System Label]  [System Label List] 
[Rename].
• Right-click the system label list name on the Navigation window, and select [System Label List]  [Rename].

Up to 64 characters can be used to change the label space name using System label Ver.2.

7 UTILITY OPERATIONS
124 7.3 Label Utility
■Deleting system label list
• Select the system label list name to be deleted on the Navigation window, and select [Menu]  [System Label]  [System
Label List]  [Delete].
• Right-click the system label list name to be deleted on the Navigation window, and select [System Label List]  [Delete].
• Select the system label list name to be deleted on the Navigation window, and press the  key.

Selecting data types

The applicable data types are as follows.
: Supported, : Not supported
Data type System Label MX Component
Ver.2 Ver.1 Simple Types Structure
Bit    
Word [Signed]    
Double Word [Signed]    
Word [Unsigned]/Bit String [16-bit]    
Double Word [Unsigned]/Bit String [32-bit]    
FLOAT(Single Precision)    
FLOAT(Double Precision)    
String    
*1
String[Unicode]    
Time    
7
Timer*1    
Timer[Unsigned]*1    
Long Timer*1    
*1
Counter    
*1
Counter[Unsigned]    
Long Counter*1    
*1
Retentive Timer    
Retentive Timer[Unsigned]*1    
Long Retentive Timer*1    
Pointer    
Structure    *2

*1 Select "Simple type" when arraying.

An error occurs during usage, when "Structure" is selected.
*2 A five-level structure can be used by MX Component Version 4.11M or later.

7 UTILITY OPERATIONS
7.3 Label Utility 125
 Window
Click [...] on the data type entry field of the system label list or the structure setting.

Operating procedure
1. Select a type from "Type Class".
Item Description
Simple Types Specify this to select a data type from basic types: bit, word.
Structure Specify this to select a data type from the defined structures.
(Not displayed for the structured data settings)

2. In the "Data Type" field, select the data type and structure.

3. Click the [OK] button.

The settings are displayed in the "Data Type" column.

■Setting arrays for data type

Define a data type as an array.
To define a data type as an array, set the items of "Array Element" on the "Type Selection" screen.

Operating procedure
1. Click [...] on the data type entry field of the system label list or the structure setting.
2. Select the check box under "Array Element".

3. Set "Element (One Dimension)", and if necessary, set "Element (Two Dimension)", "Element (Three Dimension)".

4. Set the data type of the array element in the same manner as setting the normal data type.

7 UTILITY OPERATIONS
126 7.3 Label Utility
Assigning devices to structured data type labels
Window
Click "Detail Setting" on the Device column of System Label List.

Operating procedure
Set the items on the screen. 7
Item Description
Label Name Display label names defined as structure.
Data Type Display data types set to data names.
Device Set device names to be assigned.

7 UTILITY OPERATIONS
7.3 Label Utility 127
 Assigning devices to structure array type labels
Window
Click "Detail Setting" on the Device column of System Label List.

Operating procedure
Set the items on the screen.
Item Description
Structure Array Display elements of the structure array in tree format.
The device setting of the element selected in the tree is displayed in the right area of the screen.
Label Name Display label names defined as the structure.
Data Type Display data types set to label names.
Device Set device names to be assigned.
Device names can be entered for the start array element only.

7 UTILITY OPERATIONS
128 7.3 Label Utility
Setting Structure
Register, edit, and browse each data (element) that is configured in the structure managed in the LabelSpace.

Window

Item Description Reference

Label Name Display a label name. 
Data Type Display a data type of the label. Page 125 Selecting data types
Specify a data type from the "Type Selection" screen displayed by clicking [...]. 7
Basic operations
Operating procedure
■Adding structured data type
• Select a LabelSpace name on the LabelSpace window, and select [Menu]  [System Label]  [Structured Data Types] 
[New].
• Select a LabelSpace name on the LabelSpace window, right-click "Structured Data Types" on the Navigation window, and
select [Structured Data Types]  [New].

■Changing structure name

• Select the structure name on the Navigation window, and select [Menu]  [System Label]  [Structured Data Types] 
[Rename].
• Right-click the structure name on the Navigation window, and select [Structured Data Types]  [Rename].

Up to 64 characters can be used to change the label space name using System label Ver.2.

■Deleting structured data type

• Select the structure name to be deleted on the Navigation window, and select [Menu]  [System Label]  [Structured Data
Types]  [Delete].
• Right-click the structure name to be deleted on the Navigation window, and select [Structured Data Types]  [Delete].
• Select the structure name to be deleted on the Navigation window, and press the  key.

7 UTILITY OPERATIONS
7.3 Label Utility 129
 Referring and registering/canceling Workspaces

Referring and registering

Register a Workspace to be referred when importing a system label.
• A system label can be used in MX Component independently by canceling the reference.
• When registering a canceled reference, the reference is regarded as a new reference. (The canceled references are not
restored.)
• The label information within the LabelSpace cannot be edited after the reference registration. (Note that the logical station
numbers can be registered.)

Operating procedure
• Select the LabelSpace name on the LabelSpace window, and select [Menu]  [Workspace]  [Reference Registration].
• Right-click "Reference Workspace" on the Navigation window, and select [Workspace]  [Reference Registration].

Window

Item Description
Save Folder Path Click the [Browse] button, and select a folder in the "Browse for Folder" screen.
Workspace List Display the list of Workspaces.

The structure array labels whose devices are automatically assigned or whose devices are bit-specified
cannot be referred and registered properly.
Register them with the system label list.

Canceling
Cancel the reference of registered Workspace for importing the system label.
• The label information within the LabelSpace can be edited after canceling the reference registration.

Operating procedure
• Select the LabelSpace name on the LabelSpace window, and select [Menu]  [Workspace]  [Dereference Registration].
• Right-click "Reference Workspace" on the Navigation window, and select [Workspace]  [Dereference Registration].

7 UTILITY OPERATIONS
130 7.3 Label Utility
Change notification

Change notification
When Workspace is referred and registered, the system label notification icon is displayed by executing the change
confirmation when the status-changed labels exist.

Operating procedure
Select [Menu]  [System Label]  [Check Changes of System Label Database].
(The change confirmation is also executed when Label Utility starts.)

Window

• For using the change notification function, use MELSOFT Navigator Version 1.39R or later.
• Receive a change notification when executing any of the following operations on the reference Workspace.
(The change notification is not sent when creating a new system label.)
 Change in system labels (including the change of comment and remark)
 Deletion of system labels 7

Applying the changed data

Apply the status-changed label information when Workspace is referred and registered.
When more than one Workspace is referred, apply them for each LabelSpace.

Operating procedure
• Select [Menu]  [System Label]  [Change Contents of System Label Database].
• Right-click the system label notification icon ( ), and select [Change Contents of System Label Database].

7 UTILITY OPERATIONS
7.3 Label Utility 131
 Updating system label data
Update the system label data.

Operating procedure
Select [Menu]  [Refresh system label data for Control].

Exporting LabelSpace
Save the information used in Label Utility.

Operating procedure
Select [Menu]  [Export].

Window

The assignment information of the logical station number is not included in the exported information.
When using the exported information by importing it, the assignment of logical station number is required.

7 UTILITY OPERATIONS
132 7.3 Label Utility
Importing LabelSpace
Import the saved information saved in a file by exporting LabelSpace (Page 132 Exporting LabelSpace) to Label Utility.

Operating procedure
Select [Menu]  [Import].

Window

7 UTILITY OPERATIONS
7.3 Label Utility 133
 8 COMMUNICATION SETTING EXAMPLES OF
UTILITY SETTING TYPE
This chapter explains the setting procedure and setting example of each communication route when the utility setting type is
used for programming.

• The communication settings can be registered or changed in order to run MX Component Version 3
programs in MX Component Version 4.
• For the settings other than "As set by user", set the value shown in the table.
• When performing communication using MX Component for the first time, check if MX Component can
communicate with a module properly using GX Developer first so that the cause of the communication
failure can be identified easily.
• For details for the settings of modules, refer to the manual of each module.

8.1 Serial Communication

This section provides the serial communication procedure and its setting example using the utility setting type.

Settings of serial communication modules

This section explains the settings of serial communication modules for the use of MX Component.
The settings of MX Component need to be the same as the module.
The following sketches are used to explain each module.
<When using Q series-compatible C24 or L series-compatible C24>

(For 1:1 communication) (For 1:n communication)

Personal Computer 0 Station Personal Computer 0 Station*2 1 Station

*1

*1: Use of CH1 *2: Use of both CH1 and CH2

<When using FX extended port>

Personal computer
Module 1 Module 2

FX-485PC-IF

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

134 8.1 Serial Communication
R series-compatible C24
For details, refer to the following manual.
MELSEC iQ-R Serial Communication Module User's Manual(Application)

Q series-compatible C24, L series-compatible C24

When connecting a personal computer with Q/L series compatible C24 on a 1:1 basis, the communication can
be performed without the switch setting of Q/L series compatible C24. When the switch setting is not set, the
module operates as GX Developer/MELSOFT connection as shown below.

■For 1:1 communication

Item Setting Setting value
b15 to b8 b7 to b0
Switch 1 CH1 communication speed CH1 transmission setting 0000H
Switch 2  CH1 communications protocol 0000H
Switch 3 CH2 communication speed CH2 transmission setting 0000H
Switch 4  CH2 communications protocol 0000H
Switch 5 Module station number 0000H

When the communication protocol is set to '00H' (GX Developer/MELSOFT connection), the module operates with the value
shown in the following table.
For details, refer to the following manual.
 Q Corresponding Serial Communication Module User's Manual (Basic)
MELSEC-L Serial Communication Module User's Manual (Basic) 8
Transmission setting Setting
Data bit 8
Parity bit Yes
Odd/even number parity Odd number
Stop bit 1
Sum check code Yes
Online change Enable

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.1 Serial Communication 135
 ■For 1:n communication
0 Station
Item Setting Setting value
b15 to b8 b7 to b0 Synchronous operation
Switch 1 CH1 communication speed CH1 transmission setting 07E6H
Switch 2  CH1 communications protocol 0008H
Switch 3 CH2 communication speed CH2 transmission setting 07E7H
Switch 4  CH2 communications protocol 0000H
Switch 5 Module station number 0000H (As set by user)

1 Station
Item Setting Setting value
b15 to b8 b7 to b0 Independent operation
Switch 1 CH1 communication speed CH1 transmission setting Set to satisfy the application of CH1.
Switch 2  CH1 communications protocol
Switch 3 CH2 communication speed CH2 transmission setting 07E6H
Switch 4  CH2 communications protocol 0005H
Switch 5 Module station number 0000H (As set by user)

The module operates with the value shown in the following table.
Transmission setting Setting
Operation setting 0 Station Synchronous
1 Station Independent
Data bit 8
Parity bit Yes
Odd/even number parity Odd number
Stop bit 1
Sum check code Yes
Online change Enable
Transmission speed setting 19200bps

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

136 8.1 Serial Communication
FX extended port
Set the FXCPU parameters with GX Works2 before using FX extended port to perform communication.
Execute either of the following two setting methods by following the instruction described on the reference page.
• To use the PLC parameters (Page 137 Settings with PLC parameters)
• To write values to special data registers (D8120, D8121, D8129) in a sequence program. (For FX0NCPU, only this method
is applicable.)
(Page 138 Settings by writing values to the special data registers in a sequence program)

■Settings with PLC parameters

Operating procedure
1. Start GX Works2.

2. Select [Parameter]  [PLC parameter] in the project list.

3. Click the [PLC System(2)] tab in the "FX Parameter" screen.

4. Set the items on the screen.

Item Description
Operate communication setting Select the checkbox.
Protocol*1 Select the communication protocol.
Data length*1 7bit/8bit
Parity*1 NONE/Odd/Even
*1
Stop bit 1bit/2bit
Transmission speed*1 300bps/600bps/1200bps/2400bps/4800bps/9600bps/19200bps
*1
H/W type Select the cable type used in the communication.
Sum check*1 Select/clear
Transmission control procedure*1 Select the transmission control procedure.
*1
Station number setting Set the station number.
Time out judge time*1 Set the time out period.

*1 Not applicable when "Operate Communication Setting" is OFF.

• When communication setting is set, turn on the FXCPU again after writing to programmable controller.
• When performing multi-drop connection, set the same communication settings for the devices.
However, check that the station number is not overlapped.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.1 Serial Communication 137
 ■Settings by writing values to the special data registers in a sequence program
D8120 (communication format)

b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0

D8120

Bit Description Setting detail

b0 Data length 0: 7 bit
1: 8 bit
b1 Parity None: b2=0, b1=0
Odd number: b2=0, b1=1
Even number: b2=1, b1=1

b2

b3 Stop bit 0: 1 bit

1: 2 bit
b4 Transmission speed Set transmission speed.*1

b5

b6

b7

b8  0
b9 0
b10 H/W type RS-485: b11=0, b10=0
b11
b12  0
b13 Sum check 0: Not available
1: Available
b14 Communication protocol 1: Serial communication
b15 Transmission control procedure 0: Form 1

*1 The setting contents of transmission speed are shown as below:

Transmission speed b7 b6 b5 b4
300bps 0 0 1 1
600bps 0 1 0 0
1200bps 0 1 0 1
2400bps 0 1 1 0
4800bps 0 1 1 1
9600bps 1 0 0 0
19200bps 1 0 0 1

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

138 8.1 Serial Communication
D8121 (station number setting)
Specify the station number.
The station number can be specified in the range of 00H to 0FH.

b15 to b0
D8121 Station number range: 00H to 0FH

D8129 (time out judge time setting)

Specify the FXCPU time out judge time in 10ms units.
The setting range is as follows:
For FX0N, FX1S, FX1N, FX1NC, FX3S, FX3G, FX3GC, FX3U, FX3UC, 1 to 255 (10 to 2550ms).
For FX2N, FX2NC, 1 to 3276 (10 to 32760ms).
If "0" is stored, 100ms is set.

b15 to b0
D8129 FX0N, FX1S, FX1N(C), FX3S, FX3G(C), FX3U(C): 1 to 255 FX2N(C): 1 to 3276

• When communication setting is performed, turn on FXCPU again after writing to programmable controller.
• When performing multi-drop connection, set the same communication settings for the devices.
However, check that the station number is not overlapped.

The following shows an example of setting values to the special data registers.

The following shows the setting details of each special data register in the above program.
• D8120
Transmission control procedure: Form 1
Communication protocol: Serial communication
Sum check: Available
H/W type: RS-485
Transmission speed: 9600bps
Stop bit: 1 bit
Parity: NONE
Data length: 7 bit
• D8121
Station number : 12
• D8129
Time out time : 200ms

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.1 Serial Communication 139
 Access procedure
The following is the procedure for accessing the programmable controller CPU using serial communication.

Start

When using Q series-compatible C24, set the

software switches. (1)
When using the FX extended port, set the PLC
parameters.

Connect the serial communication module and

personal computer. (2)

Start Communication Setup Utility and set the

(3)
items on Communication Setting Wizard.

On the communication test screen, check whether

(4)
communication can be performed properly.

Complete

(1)Page 134 Settings of serial communication modules

(2)Page 30 SYSTEM CONFIGURATIONS
(3)Page 141 Setting the logical station number (setting on Communication Setting Wizard)
(4)Page 143 Checking the logical station number settings (conducting a communication test)

System examples
The following system examples are used in this section.

(For 1:1 communication) (For 1:n communication)

Module Ò
Q25H Q series-compatible Q00J Q series-compatible
CPU C24 (Sta. No.1) CPU C24 (Sta. No.1)

Serial communication
(Multi-drop)

Personal computer Personal computer

Module Ó
(MX Component) (MX Component)
COM1 is used. COM1 is used. Q00J Q series-compatible
CPU C24 (Sta. No.3)
Logical station number
of "1" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

140 8.1 Serial Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number for 1:n communication using the system example in this section
(Page 140 System examples).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "1" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Serial
Connect port: COM1
Time out: 10000
8

4. Set the following items and click the [Next] button.

PLC side I/F: C24 module
Module type: QJ71C24
Station No.: 1
Transmission speed: 19200
Parity: Odd
Control: DTR or RTS Control

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.1 Serial Communication 141
 5. Set the following items and click the [Next] button.
Station type: Other station
Network: C24
Network type: Multidrop(combine)

6. Set the following items and click the [Next] button.

CPU type: Q00J
Station No.: 3

7. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

142 8.1 Serial Communication
Checking the logical station number settings (conducting a communication test)
Check the serial communication settings, using the logical station number set in this section (Page 141 Setting the logical
station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "1".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "1".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.1 Serial Communication 143
 8.2 Ethernet Communication (When Using Ethernet
Modules)
This section provides the procedure for Ethernet communication with the Ethernet module and its setting example using the
utility setting type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using Ethernet communication.

Start

Set the Ethernet module parameters. (1)

Connect the Ethernet module and personal

(2)
computer.

Edit the HOSTS file. *1

Start Communication Setup Utility and set the

items on Communication Setting Wizard. (3)

On the communication test screen, check whether

communication can be performed properly. (4)

Complete

*1 The HOSTS file is not required to be edited when entering the IP address in the host name (IP Address) of Communication Setup Utility
and the ActHostAddress property of the Ethernet communication control.
(1)Page 145 Setting parameter setting,Page 147 Setting routing parameter setting
(2)Page 30 SYSTEM CONFIGURATIONS
(3)Page 148 Setting the logical station number (setting on Communication Setting Wizard)
(4)Page 150 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Personal computer
Logical station number of "2" is used.

Network No.1 Station Number: 2

Q series-compatible E71 (192.168.0.2)

Station number: 2

CPU1
Q02HCPU Q series-compatible E71 (192.168.0.1)
Station number: 1

CPU2
Q02HCPU
Network No.2

Q series-compatible E71 (192.168.0.3)

Station number: 3

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

144 8.2 Ethernet Communication (When Using Ethernet Modules)
Setting parameter setting
Set the network type, start I/O number, network number, station number, mode and operational settings on the Network
Parameter - MELSECNET/CC IE/Ethernet Module Configuration screen of GX Works2.
CPU to be set Setting screen example
CPU 1 Ethernet parameters

Operational settings

CPU 2 Ethernet parameters

Operational settings

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.2 Ethernet Communication (When Using Ethernet Modules) 145
 Set the parameters in GX Works3 for RCPU.
Refer to the following manual, for details on parameter settings.
 MELSEC iQ-R Ethernet User's Manual (Application)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

146 8.2 Ethernet Communication (When Using Ethernet Modules)
Setting routing parameter setting
Set the following items on the Network Parameter - Setting the Ethernet/CC IE/MELSECNET Routing Information screen of
GX Works2.
For the routing parameters, refer to the following appendix.
Page 381 Concept of Routing Parameters
CPU to be set Setting screen example
CPU 1

CPU 2

Set the routing parameters in GX Works3 for RCPU.

Refer to the following manual, for details on routing parameter settings.
 MELSEC iQ-R Ethernet User's Manual (Application)
8
Performing communications check
After completion of preparations for Ethernet communication, execute ping in the MS-DOS mode to check connection before
starting communications on MX Component.
• When normal
C:\>ping 192.168.0.2
Reply from 192.168.0.2:bytes=32 time<10ms TTL=32
• When abnormal
C:\>ping 192.168.0.2
Request timed out.
If ping does not pass through, check cable and module connections and Windows side IP address and other settings.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.2 Ethernet Communication (When Using Ethernet Modules) 147
 Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 144 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "2" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Ethernet board
Connect module: QJ71E71
Protocol: TCP
Network No.: 1
Station No.: 2
Time out: 60000

4. Set the following items and click the [Next] button.

PLC side I/F: Ethernet module
Module type: QJ71E71
Host (IP Address): 192.168.0.1
Station No.: 1

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

148 8.2 Ethernet Communication (When Using Ethernet Modules)
 5. Set the following items and click the [Next] button.
Station type: Other station
Network: Ethernet

6. Set the following items and click the [Next] button.

CPU type: Q02(H)
Network No.: 2
Station No.: 3
Multiple CPU: None

7. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.2 Ethernet Communication (When Using Ethernet Modules) 149
 Checking the logical station number settings (conducting a communication test)
Check the Ethernet communication settings, using the logical station number set in this section (Page 148 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "2".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "2".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

150 8.2 Ethernet Communication (When Using Ethernet Modules)
8.3 Ethernet Communication (When Using Built-in
Ethernet CPUs)
This section provides the procedure for the Ethernet communication with the built-in Ethernet CPU and its setting example
using the utility setting type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using Ethernet communication.

Start

Connect the Built-in Ethernet CPU

and personal computer.
<Connecting by specified host (IP address)> <Connecting to the Ethernet port directly>

Set parameters of the Built-in

(1)
Ethernet CPU.

*1
Edit the HOSTS file.

Start Communication Setup Utility

Start Communication Setup Utility 8
and set the settings of the direct
and set the IP address on (2)
(2) connection on Communication
Communication Setting Wizard.
Setting Wizard.

On the communication test screen, check

whether communication can be performed
properly.

Complete

*1 The HOSTS file is not required to be edited when entering the IP address in the host name (IP address) of Communication Setup Utility
and the ActHostAddress property of the Ethernet communication control.
(1)Page 152 Setting parameters (in case of connection by specified Host (IP address only))
(2)Page 153 Setting the logical station number (setting on Communication Setting Wizard)

System example
The following system example is used in this section.

Personal computer
Logical station number of "3" is used.

IP address (192.168.0.1)

Built-in Ethernet CPU

Q04UDEH

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.3 Ethernet Communication (When Using Built-in Ethernet CPUs) 151
 Setting parameters (in case of connection by specified Host (IP address only))
Parameter settings are set from the PLC parameter of GX Works2.
Select the [Built-in Ethernet Port Setting] tab and set the communication settings : IP address or the like.

For RCPU and LHCPU, set the parameters in GX Works3.

Refer to the following manual, for details on parameter settings.
MELSEC iQ-R Ethernet User's Manual (Application)

Performing communications check

After completion of preparations for Ethernet communication, execute ping in the MS-DOS mode to check connection before
starting communications on MX Component.
• When normal
C:\>ping 192.168.0.1
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
• When abnormal
C:\>ping 192.168.0.1
Request timed out.
If ping does not pass through, check cable and module connections and Windows side IP address and other settings.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

152 8.3 Ethernet Communication (When Using Built-in Ethernet CPUs)
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 151 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "3" in Logical station number and click the [Next]

button.
Execute either of the following two ways of steps of the
programmable controller side settings.
Follow 3) and 4) of steps in case of connection by
specified Host (IP address).
Follow 5) and 6) of steps in case of Ethernet port direct
connection.

Step 3) or jump to step 5)

3. Set the following items and click the [Next] button.
PC side I/F: Ethernet board
Connect module: CPU module
Protocol: TCP 8
Time out: 60000

4. Set the following items and click the [Next] button.

PLC side I/F: CPU module
Host (IP Address): 192.168.0.1

Step 7)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.3 Ethernet Communication (When Using Built-in Ethernet CPUs) 153
 5. Set the following items and click the [Next] button.
PC side I/F: Ethernet board
Connect module: CPU module
Protocol: UDP
Time out: 60000

6. Set the following items and click the [Next] button.

Select the check box "Ethernet port direct connection".

7. Set the following items and click the [Next] button.

Station type: Host station
CPU type: Q04UDEH
Multiple CPU: None

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

154 8.3 Ethernet Communication (When Using Built-in Ethernet CPUs)
 8. Enter a comment and click the [Finish] button.

Registration complete
Perform the built-in Ethernet CPU search on the following screen displayed by clicking the [Find CPU (Built-in Ethernet port)
on network] button when use it.
Built-in Ethernet CPUs on the same network is the target of the search.
Choosing the target CPU from the list and clicking the [OK]
button enables to update the IP address on the
"Communication Setting Wizard - PLC side" setting.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.3 Ethernet Communication (When Using Built-in Ethernet CPUs) 155
 Checking the logical station number settings (conducting a communication test)
Check the Ethernet communication settings, using the logical station number set in this section (Page 153 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "3".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "3".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

156 8.3 Ethernet Communication (When Using Built-in Ethernet CPUs)
8.4 Ethernet Communication (When Using Ethernet
Adapter Module)
This section provides the procedure for the Ethernet communication with in case of using Ethernet adapter module and its
setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using Ethernet communication.

Start

Connect the Ethernet adapter module and personal

computer.

Connect the Ethernet adapter module and CC-Link IE

Field Network.

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (1)

On the communication test screen, check whether

(2)
communication can be performed properly.

8
Complete

(1)Page 158 Setting the logical station number (setting on Communication Setting Wizard)
(2)Page 160 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

CC-Link IE Field
Network module
Personal computer
Ethernet adapter
module

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.4 Ethernet Communication (When Using Ethernet Adapter Module) 157
 Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 157 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "4" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Ethernet board
Connect module: CC IE Field Ethernet adapter
Protocol: TCP
Time out: 60000

4. Set the following items and click the [Next] button.

PLC side I/F: CC IE Field Ethernet adapter
Host (IP Address): 192.168.3.30

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

158 8.4 Ethernet Communication (When Using Ethernet Adapter Module)
 5. Set the following items and click the [Next] button.
Station type: Other station (Single)

6. Set the following items and click the [Next] button.

CPU type: Q13UDH
Network No.: 1
Station No.: 0
Multiple CPU: None

7. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.4 Ethernet Communication (When Using Ethernet Adapter Module) 159
 Checking the logical station number settings (conducting a communication test)
Check the Ethernet communication settings, using the logical station number set in this section (Page 158 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "4".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "4".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

160 8.4 Ethernet Communication (When Using Ethernet Adapter Module)
8.5 Ethernet Communication (When Using Ethernet
Adapter)
This section provides the procedure for the Ethernet communication with in case of using Ethernet adapter and its setting
example using the utility setting type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using Ethernet communication.

Start

Connect the Ethernet Adaptor

and personal computer.

< Connecting by specified host (IP address) > < Connecting to the Ethernet port directly >

Edit the HOSTS file. *1

Start Communication Setup Start Communication Setup

Utility and set the IP address Utility and set the settings of the
(1) (1)
on Communication Setting direct connection on
Wizard. Communication Setting Wizard.

On the communication test screen, check whether

(2)
communication can be performed properly.

Complete

*1 The HOSTS file is not required to be edited when entering the IP address in the host name (IP address) of Communication Setup Utility
and the ActHostAddress property of the Ethernet communication control.
(1)Page 163 Setting the logical station number (setting on Communication Setting Wizard)
(2)Page 166 Checking the logical station number settings (conducting a communication test)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.5 Ethernet Communication (When Using Ethernet Adapter) 161
 System example
■Example of the system for the IP address specified communication
Personal computer
FX3U(C)/FX3G(C)/FX3S

Hub
Ethernet Ethernet

FX3U-ENET-ADP

■Example of the system for the direct communication

Personal computer
FX3U(C)/FX3G(C)/FX3S

Ethernet

FX3U-ENET-ADP

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

162 8.5 Ethernet Communication (When Using Ethernet Adapter)
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 162 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "18" in Logical station number and click the [Next]

button.
Execute either of the following two ways of steps of the
programmable controller side settings.
Follow 3) and 4) of steps in case of connection by
specified Host (IP address).
Follow 5) and 6) of steps in case of Ethernet port direct
connection.

Step 3) or jump to step 5)

3. Set the following items and click the [Next] button.
PC side I/F: Ethernet board
Connect module: FX3U-ENET-ADP
Time out: 60000 8

4. Set the following items and click the [Next] button.

PLC side I/F: FX3U-ENET-ADP
Host (IP Address): 192.168.0.101

Step 7)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.5 Ethernet Communication (When Using Ethernet Adapter) 163
 5. Set the following items and click the [Next] button.
PC side I/F: Ethernet board
Connect module: FX3U-ENET-ADP
Time out: 60000

6. Set the following items and click the [Next] button.

Select the check box "Ethernet port direct connection".

7. Set the following items and click the [Next] button.

Station type: Host station
CPU type: FX3U(C)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

164 8.5 Ethernet Communication (When Using Ethernet Adapter)
 8. Enter a comment and click the [Finish] button.

Registration complete
Perform the built-in Ethernet CPU search on the following screen displayed by clicking the [Find CPU (Built-in Ethernet port)
on network] button when use it.
FX3U(C)/FX3G(C)/FX3SCPU on the same network is the target of the search.
Choosing the target CPU from the list and clicking the [OK]
button enables to update the IP address on the
"Communication Setting Wizard - PLC side" setting.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.5 Ethernet Communication (When Using Ethernet Adapter) 165
 Checking the logical station number settings (conducting a communication test)
Check the Ethernet communication settings, using the logical station number set in this section (Page 163 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "18".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "18".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

166 8.5 Ethernet Communication (When Using Ethernet Adapter)
8.6 CPU COM Communication
This section provides the CPU COM communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using CPU COM communication.

Start

Connect the programmable controller CPU and

(1)
personal computer.

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (2)

On the communication test screen, check whether

communication can be performed properly. (3)

Complete

(1)Page 30 SYSTEM CONFIGURATIONS

(2)Page 168 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 170 Checking the logical station number settings (conducting a communication test)

8
System example
The following system example is used in this section.

Q02H Normal station

CPU (Sta. No.2)

MELSECNET/H
(Network No. 5)

Personal computer
(MX Component) Q02H Normal station
COM1 is used. CPU (Sta. No.5)

Logical station number of "5" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.6 CPU COM Communication 167
 Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 167 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "5" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Serial
Connect port: COM1
Time out: 10000

4. Set the following items and click the [Next] button.

PLC side I/F: CPU module
CPU type: Q02(H)
Transmission speed: 19200
Control: DTR or RTS Control

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

168 8.6 CPU COM Communication
 5. Set the following items and click the [Next] button.
Station type: Other station
Network: MELSECNET/10(H)
Mode: MELSECNET/H

6. Set the following items and click the [Next] button.

CPU type: Q02(H)
Network No.: 5
Station No.: 5
Multiple CPU: None

7. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.6 CPU COM Communication 169
 Checking the logical station number settings (conducting a communication test)
Check the CPU COM communication settings, using the logical station number set in this section (Page 168 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "5".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "5".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

170 8.6 CPU COM Communication
8.7 CPU USB Communication
This section provides the CPU USB communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using CPU USB communication.

Start

Connect the programmable controller CPU and

(1)
personal computer.

Install the USB driver. (2)

Start Communication Setup Utility and set the items on

(3)
Communication Setting Wizard.

On the communication test screen, check whether

(4)
communication can be performed properly.

Complete

(1)Page 30 SYSTEM CONFIGURATIONS 8

(2)Page 423 USB Driver Installation
(3)Page 172 Setting the logical station number (setting on Communication Setting Wizard)
(4)Page 174 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Q02H Normal station

CPU (Sta. No.2)

MELSECNET/H
(Network No.1)

Personal computer
(MX Component)
Q02H Normal station
USB port is used.
CPU (Sta. No.8)
Logical station number of "6" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.7 CPU USB Communication 171
 Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 171 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "6" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: USB
Time out: 10000

4. Set the following items and click the [Next] button.

PLC side I/F: CPU module
CPU type: Q02(H)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

172 8.7 CPU USB Communication
 5. Set the following items and click the [Next] button.
Station type: Other station
Network: MELSECNET/10(H)
Mode: MELSECNET/H

6. Set the following items and click the [Next] button.

CPU type: Q02(H)
Network No.: 1
Station No.: 8
Multiple CPU: None

7. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.7 CPU USB Communication 173
 Checking the logical station number settings (conducting a communication test)
Check the CPU USB communication settings, using the logical station number set in this section (Page 172 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "6".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "6".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

174 8.7 CPU USB Communication
8.8 CC-Link Communication
This section provides the CC-Link communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using CC-Link communication.

Start

Set the CC-Link Ver.2 board.

Connect the personal computer to CC-Link. (1)

Start Communication Setup Utility and set the items on

(2)
Communication Setting Wizard.

On the communication test screen, check whether

(3)
communication can be performed properly.

Complete

(1)Page 30 SYSTEM CONFIGURATIONS, Page 176 Checking the CC-Link Ver.2 board 8
(2)Page 177 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 179 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Master station
(Station number 1)
Number of occupied
stations 1 Transmission speed: 10Mbps

CC-Link

Q02H Local station

CPU (Sta. No.5)
Logical station number of "7" is used.

Personal computer
(MX Component)
First CC-Link Ver.2 board is used.

• Accessible to FXCPU with CC-Link communication only via the serial/USB connection of QCPU or via Q series-compatible
C24.
Supported CPUs and module in CC-Link communication to FXCPU are as follows.
CC-Link module Compatible CPU Station number
FX3U-64CCL FX3G, FX3GC, FX3U, FX3UC 1 to 63

Supported CPUs and module in CC-Link communication via a personal computer board to RCPU are as follows.
CC-Link module Compatible CPU Station number
RJ61BT11 RCPU 0 to 64

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.8 CC-Link Communication 175
 Checking the CC-Link Ver.2 board
Check whether the personal computer is connected properly to CC-Link.

Operating procedure
1. Select [Start]  [All Programs]  [MELSEC] 
[MELSEC CC-Link Ver.2 Utility].

2. Click the [Parameter settings] tab and set the following

items.
Channel No.: Channel No. 81
Sta. No.: 1
Type: Local station
Transmission rate: 10Mbps
Mode: Remote net (Ver.1 mode)
Occupied Sta.: Occupies 1 station
Input for Err Sta.: Clear

3. Click the [Online operation] tab and click the [Write]

button.

4. Click the [Board information] tab.

Check that the loop of the own station is normal.

Check complete 5. Click the [Exit] button to exit from the utility.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

176 8.8 CC-Link Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 175 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "7" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: CC-Link board
Board No: 1st module

4. Set the following items and click the [Next] button.

Station type: Other station (Single)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.8 CC-Link Communication 177
 5. Set the following items and click the [Next] button.
CPU type: Q02(H)
Station No: 5
Multiple CPU: None

6. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

178 8.8 CC-Link Communication
Checking the logical station number settings (conducting a communication test)
Check the CC-Link communication settings, using the logical station number set in this section (Page 177 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "7".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "7".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.8 CC-Link Communication 179
 8.9 CC-Link G4 Communication
This section provides the CC-Link G4 communication procedure and its setting example using the utility setting type.

Switch settings of CC-Link G4 module

This section explains the switch settings of CC-Link G4 modules for the use of MX Component.
The following sketches are used to explain each module.
The settings of MX Component need to be the same as the module.

CC-Link module

Personal computer

CC-Link G4 module

Switch (switch number) Setting

Q mode
Station number setting switch 1 (local station)
Data link transmission speed setting switch 4 (10Mbps)
(match to the transmission speed of the CC-Link module)
Operation setting DIP switch Operation mode setting (SW1, SW6) SW1: OFF
SW6: ON
Inter-peripheral transmission speed setting (SW2, SW3) Setting is not required (automatic setting)
Parity bit setting (SW4, SW5) Set, Odd number
SW4: OFF
SW5: OFF
(SW7) OFF
Test mode setting (SW8) OFF (online mode)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

180 8.9 CC-Link G4 Communication
Access procedure
The following is the procedure for accessing the programmable controller CPU using CC-Link G4 communication.

Start

Set the operation setting DIP switches of the CC-Link G4 module. (1)

Connect the CC-Link G4 module to the CC-Link module. (2)

Connect the personal computer to the CC-Link G4 module. (3)

Set the network parameters. (4)

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (5)

On the communication test screen, check whether

communication can be performed properly. (6)

Complete

8
(1)Page 180 Switch settings of CC-Link G4 module
(2)Page 182 Wiring the CC-Link G4 module
(3)Page 30 SYSTEM CONFIGURATIONS
(4)Page 182 Setting the network parameters
(5)Page 184 Setting the logical station number (setting on Communication Setting Wizard)
(6)Page 186 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Transemission speed: 19200bps

Transemission speed: 10Mbps

CC-Link

CC-Link G4 module
Personal computer Q00J Master station
(Q mode)
(MX Component) CPU (Sta. No.0)
Station number: 1
COM1 is used.
Logical station number of "8" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.9 CC-Link G4 Communication 181
 Wiring the CC-Link G4 module
The diagram of wiring the CC-Link G4 module to the CC-Link module is shown below.

CC-Link module AJ65BT-G4-S3

Termination DA DA Termination
resistor DB DB resistor

DG DG

SLD SLD
FG +24V
24VDC
24G
FG

Setting the network parameters

Parameter setting may either be set on the Network Parameter - CC-Link Module Configuration screen of GX Works2 or from
a sequence program.

■Setting parameter setting on CC-Link setting screen

Set the start I/O number, type, total number of modules connected, and station information.
Set other setting items as required.
<CC-Link parameter setting screen>

<Station information setting screen>

After setting the CC-Link parameters, write them to the programmable controller CPU.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

182 8.9 CC-Link G4 Communication
■Setting parameter setting in sequence program
The parameter setting items for data link and the sequence program example are described below.
<Parameter setting items>
Address Item Description Setting value
1H Number of Set the number of modules on the remote/local stations connected. 1H
connected modules
20H Station information AJ65BT-G4-S3 2101H

<Sequence program>

This sample sequence program is installed into the following folders after installation of MX Component.
[User-specified folder] - [Act] - [Samples] - [GppW] - [CCG4A]

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.9 CC-Link G4 Communication 183
 Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 181 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "8" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Serial
Connect port: COM1
Time out: 10000

4. Set the following items and click the [Next] button.

PLC side I/F: G4 module
Mode: Q
Transmission speed: 19200
Control: DTR or RTS Control

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

184 8.9 CC-Link G4 Communication
 5. Set the following items and click the [Next] button.
Station type: Host station
CPU type: Q00J
CC-Link module No: 0

6. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.9 CC-Link G4 Communication 185
 Checking the logical station number settings (conducting a communication test)
Check the CC-Link G4 communication settings, using the logical station number set in this section (Page 184 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "8".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "8".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

186 8.9 CC-Link G4 Communication
8.10 GX Simulator Communication
This section provides the GX Simulator communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing GX Simulator using GX Simulator communication.

Start

Start GX Developer and GX Simulator. (1)

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (2)

On the communication test screen, check whether

(3)
communication can be performed properly.

Complete

(1)Page 30 SYSTEM CONFIGURATIONS

(2)Page 188 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 189 Checking the logical station number settings (conducting a communication test)
8
System example
The following system example is used in this section.

Starting!
Personal computer
GX Developer

GX Simulator
MX
Component Q02HCPU

Logical station number of "9" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.10 GX Simulator Communication 187
 Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 187 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "9" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: GX Simulator
Station type: Host station
CPU type: Q02(H)
Time out: 10000

4. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

188 8.10 GX Simulator Communication
Checking the logical station number settings (conducting a communication test)
Check the GX Simulator communication settings, using the logical station number set in this section (Page 188 Setting
the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "9".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "9".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.10 GX Simulator Communication 189
 8.11 GX Simulator2 Communication
This section provides GX Simulator2 communication procedure and its setting example using the utility setting type.

The simulation function of GX Works2 cannot be terminated even if stopped by GX Works2 while connecting
to MX Component. (The simulation function of GX Works2 cannot be terminated even if GX Works2 is
terminated.)
The simulation function of GX Works2 can be terminated after disconnected to MX Component.

Access procedure
The following is the procedure for accessing the simulation function of GX Works2 using GX Simulator2 communication.

Start

Start GX Works2 and the simulation function. (1)

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (2)

On the communication test screen, check whether

(3)
communication can be performed properly.

Complete

(1)Page 30 SYSTEM CONFIGURATIONS

(2)Page 191 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 192 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Starting!
Personal computer
GX Works2
The simulation
function
MX
Component Q02HCPU

Logical station number of "10" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

190 8.11 GX Simulator2 Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 190 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "10" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: GX Simulator2
Target Simulator: Simulator A
CPU series: QCPU (Q mode)
8

4. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.11 GX Simulator2 Communication 191
 Checking the logical station number settings (conducting a communication test)
Check the GX Simulator2 communication settings, using the logical station number set in Page 191 Setting the logical station
number (setting on Communication Setting Wizard).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "10".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "10".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

192 8.11 GX Simulator2 Communication
8.12 GX Simulator3 Communication
This section provides GX Simulator3 communication procedure and its setting example using the utility setting type.

• When the simulation function of GX Works3 is stopped while connecting to MX Component

The simulation function of GX Works3 can be stopped while connecting to MX Component by using GX
Simulator3.
However, it is necessary to open after closing on the communication line of MX Component in order to
restart the simulation function of GX Works3.
If the function is restarted without closing on the communication line of MX Component, an error occurs.

Access procedure
The following is the procedure for accessing the simulation function of GX Works3 using GX Simulator3 communication.

Start

Start GX Works3 and the simulation function. (1)

Start Communication Setup Utility and set the items on

(2)
Communication Setting Wizard.

8
On the communication test screen, check whether (3)
communication can be performed properly.

Complete

(1)Page 30 SYSTEM CONFIGURATIONS

(2)Page 194 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 195 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Starting!
Personal computer
GX Works3
The simulation
function
MX
Component R32CPU

Logical station number of "25" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.12 GX Simulator3 Communication 193
 Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 193 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "25" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: GX Simulator3
CPU type: R32
PortNumber*1: Unselected
System No: 1
PLC No*2: 1
TimeOut: 10000
*1
When specifying a port number, select the checkbox and
then specify a port number. The target port number is
calculated with the following calculation formula.
PortNumber=5500+ System No. 10+ Unit No.
<Example>For System No.=1, Unit No.=1
5511=5500+110+1
*2
For the system number and PLC number, refer to the
following manual.
GX Works3 Operating Manual
4. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

194 8.12 GX Simulator3 Communication
Checking the logical station number settings (conducting a communication test)
Check the GX Simulator3 communication settings, using the logical station number set in this section (Page 194 Setting
the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "25".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "25".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.12 GX Simulator3 Communication 195
 8.13 MT Simulator2 Communication
This section provides MT Simulator2 communication procedure and its setting example using the utility setting type.

The communication will be disconnected when the simulation function is stopped by MT Developer2 while
communicating to MX Component.

Access procedure
The following is the procedure for accessing the simulation function of MT Developer2 using MT Simulator2 communication.

Start

Start MT Developer2 and the simulation function. (1)

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (2)

On the communication test screen, check whether

(3)
communication can be performed properly.

Complete

(1)Page 30 SYSTEM CONFIGURATIONS

(2)Page 197 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 198 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Starting!
Personal computer
MT Developer2
The simulation
function
MX
Component Q173DSCPU

Logical station number of "19" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

196 8.13 MT Simulator2 Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 196 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "19" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: MT Simulator2
Target Simulator: Simulator No.2

4. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.13 MT Simulator2 Communication 197
 Checking the logical station number settings (conducting a communication test)
Check the MT Simulator2 communication settings, using the logical station number set in this section (Page 197 Setting
the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "19".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "19".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

198 8.13 MT Simulator2 Communication
8.14 MELSECNET/H Communication
This section provides the MELSECNET/H communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using MELSECNET/H communication.

Start

Set the MELSECNET/H board.

Connect the personal computer to the MELSECNET/H. (1)

Start Communication Setup Utility and set the items on

(2)
Communication Setting Wizard.

On the communication test screen, check whether

(3)
communication can be performed properly.

Complete

(1)Page 30 SYSTEM CONFIGURATIONS, Page 200 Checking the MELSECNET/H board 8

(2)Page 201 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 192 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Normal station
(Sta. No. 1)

Personal computer (MX Component)

First MELSECNET/H board is used.

Numeral within indicates station number.

1
Q06HCPU (No. 2) at normal station
(station number: 2) on network number 2
4 Network No. 1 2 3 Network No. 2 2 is accessed.

3 Logical station number of "11" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.14 MELSECNET/H Communication 199
 Checking the MELSECNET/H board
Check whether the personal computer is connected properly to MELSECNET/H.

Operating procedure
1. Select [Start]  [All Programs]  [MELSEC] 
[MELSECNET/H Utility].

2. Click the [Board information] tab and set the following

items, and click the [Board Ser] button.
Channel: 51: MELSECNET/H (1 slot)
Mode: Online (auto.reconnection)
Baud rate: Any (10Mbps is set for this example.)
NET mode: MNET/H mode
Then, click the [Routing Param.Setting] button.

3. Set the following items and click the [Set] button.

Transfer to Network No.: 2
Intermediate Network No.: 1
Intermediate Sta.No.: 2
Then, click the [OK] button to close the dialog box.

4. Click the [Routing Param.Transfer] button to transfer the

routing parameters to the MELSECNET/H board.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

200 8.14 MELSECNET/H Communication
 5. Click the [Loop monitor] tab.
Check that the loop is normal.

Check complete 6. Click the [Exit] button to exit from the utility.

Setting the logical station number (setting on Communication Setting Wizard)

The following explains how to set the logical station number using the system example in this section (Page 199 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "11" in Logical station number and click the [Next]

8
button.

3. Set the following items and click the [Next] button.

PC side I/F: MELSECNET/H board
Board No: 1st module

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.14 MELSECNET/H Communication 201
 4. Set the following items and click the [Next] button.
Station type: Other station (Single)

5. Set the following items and click the [Next] button.

CPU type: Q06PH
Network No.: 2
Station No.: 2
Multiple CPU: No.2

6. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

202 8.14 MELSECNET/H Communication
Checking the logical station number settings (conducting a communication test)
Check the MELSECNET/H communication settings, using the logical station number set in this section (Page 201 Setting
the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "11".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "11".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.14 MELSECNET/H Communication 203
 8.15 CC-Link IE Controller Network Communication
This section provides the CC-Link IE Controller Network communication procedure and its setting example using the utility
setting type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using CC-Link IE Controller Network
communication.

Start

Set the CC-Link IE Controller Network board.

Connect the personal computer to the CC-Link IE Controller Network. (1)

Start Communication Setup Utility and set the items on

(2)
Communication Setting Wizard.

On the communication test screen, check whether

(3)
communication can be performed properly.

Complete

(1)Page 30 SYSTEM CONFIGURATIONS, Page 205 Checking the CC-Link IE Controller Network board
(2)Page 206 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 208 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Normal station
(Sta. No. 2)

Personal computer (MX Component)

First CC-Link IE Controller Network board is used.

Numeral within indicates station number.

Q06HCPU at normal station (station number: 1)

on network number 1 is accessed.
Network No. 1 1
Logical station number of "12" is used.

Supported CPUs and module in CC-Link IE Controller Network communication via a personal computer board to RCPU are
as follows.
CC-Link module Compatible CPU Station number
RJ71GP21-SX RCPU 1 to 63
RJ71EN71*1 RCPU 1 to 120

*1 CCIEC setting or CCIEC + Ether setting only

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

204 8.15 CC-Link IE Controller Network Communication
Checking the CC-Link IE Controller Network board
Check whether the personal computer is connected properly to CC-Link IE Controller Network.

Operating procedure
1. Select [Start]  [All Programs]  [MELSEC]  [CC IE
Control Utility].

2. Click the [Setting] button.

3. Set the following items and click the [End] button.

Channel No.: 151
Network type: CC IE Control (Normal station) 8
Mode: Online
Network No.: 1
Group No.: 0
Station No.: 2

4. Click the [Yes] button and write the parameter to the

CC-Link IE Controller Network board.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.15 CC-Link IE Controller Network Communication 205
 5. Click the [Diagnostics] button on the CC IE Control utility
screen.
Check that the loop is normal.

Check complete 6. Click the [Close] button to exit from the utility.

Setting the logical station number (setting on Communication Setting Wizard)

The following explains how to set the logical station number using the system example in this section (Page 204 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "12" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: CC IE Control board
Board No: 1st module

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

206 8.15 CC-Link IE Controller Network Communication
 4. Set the following items and click the [Next] button.
Station type: Host station

5. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.15 CC-Link IE Controller Network Communication 207
 Checking the logical station number settings (conducting a communication test)
Check the CC-Link IE Controller Network communication settings, using the logical station number set in this section
(Page 206 Setting the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "12".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "12".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

208 8.15 CC-Link IE Controller Network Communication
8.16 CC-Link IE Field Network Communication
This section provides the CC-Link IE Field Network communication procedure and its setting example using the utility setting
type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using CC-Link IE Field Network
communication.

Start

Set the CC-Link IE Field Network board.

Connect the personal computer to the

(1)
CC-Link IE Field Network.

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (2)

On the communication test screen, check whether

(3)
communication can be performed properly.

Complete
8

(1)Page 30 SYSTEM CONFIGURATIONS, Page 210 Checking the CC-Link IE Field Network board
(2)Page 211 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 213 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Master station
(Sta. No. 0)

Personal computer (MX Component)

First CC-Link IE Field Network board is used.

Numeral within indicates station number.

Q13UDHCPU at local station (station number: 1)

on network number 1 is accessed.
Network No. 1 1
Logical station number of "13" is used.

Supported CPUs and module in CC-Link IE Field Network communication via a personal computer board to RCPU are as
follows.
CC-Link module Compatible CPU Station number
RJ71GF11-T2 RCPU 1 to 63
RJ71EN71*1 RCPU 1 to 120

*1 CCIEF setting or CCIEF + Ether setting only

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.16 CC-Link IE Field Network Communication 209
 Checking the CC-Link IE Field Network board
Check whether the personal computer is connected properly to CC-Link IE Field Network.

Operating procedure
1. Select [Start]  [All Programs]  [MELSEC]  [CC IE
Field Board]  [CC IE Field Utility].

2. Select [Project]  [New].

3. Set the following items and click the [End] button.

Network Type: CC IE Field (Master Station)
Channel No.: 181
Network No.: 1
Total Stations: 1
Mode: Online (Normal Mode)

4. Select [Online]  [Write to Board].

Write the parameter settings of the project to the CC-
Link IE Field Network board.
5. Select [Diagnostics]  [Board Diagnostics].
Check that the loop is normal.

Check complete 6. Click the [Close] button to exit from the utility.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

210 8.16 CC-Link IE Field Network Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 209 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "13" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: CC IE Field board
Board No: 1st module

4. Set the following items and click the [Next] button.

Station type: Other station (Single)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.16 CC-Link IE Field Network Communication 211
 5. Set the following items and click the [Next] button.
CPU type: Q13UDH
Network No.: 1
Station No.: 1
Multiple CPU: None

6. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

212 8.16 CC-Link IE Field Network Communication
Checking the logical station number settings (conducting a communication test)
Check the CC-Link IE Field Network communication settings, using the logical station number set in this section (Page
211 Setting the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "13".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "13".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.16 CC-Link IE Field Network Communication 213
 8.17 Q Series Bus Communication
This section provides the Q series bus communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the programmable controller CPU using Q series bus communication.

Start

Mount the programmable controller CPU and

PC CPU on the same base.

Set the PC CPU module. (1)

Start Communication Setup Utility and set the items on (2)

Communication Setting Wizard.

On the communication test screen, check whether (3)

communication can be performed properly.

Complete

(1) PC CPU module manual

(2)Page 215 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 217 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

PC CPU module
Q12HCPU (No. 3)
Logical station number of "14" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

214 8.17 Q Series Bus Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 214 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "14" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Q Series Bus

4. Set the following items and click the [Next] button.

CPU type: Q12H
Multiple CPU: No.3

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.17 Q Series Bus Communication 215
 5. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

216 8.17 Q Series Bus Communication
Checking the logical station number settings (conducting a communication test)
Check the Q series bus communication settings, using the logical station number set in this section (Page 215 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "14".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "14".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.17 Q Series Bus Communication 217
 8.18 Modem Communication
This section provides the modem communication procedures and its setting examples using the utility setting type.

When performing modem communication for the first time on MX Component, check whether normal modem
communication can be performed using GX Works2, and then start modem communication using MX
Component.
By doing so, the cause of the communication failure can be identified easily.

Switch settings of Q series-compatible C24, L series-compatible

C24
This section explains the switch settings of the modules for the use of MX Component.
The settings of MX Component need to be the same as the module.

Q series-compatible C24, L series-compatible C24 (performing modem communication

on CH1 side)
Item Setting Setting value
b15 to b8 b7 to b0
Switch 1 CH1 communication speed*1 CH1 transmission setting*2 *1*2

Switch 2  CH1 communications protocol 0005H

Switch 3 CH2 communication speed CH2 transmission setting As set by user
Switch 4  CH2 communications protocol As set by user
Switch 5 Module station number 0000H (As set by user)

*1 Set the settings to meet the modem specifications.

*2 The transmission setting of CH1 is indicated below.

Transmission setting Setting

Operation setting Independent
Data bit 8
Parity bit No
Odd/even number parity Odd number
Stop bit 1
Sum check code Yes
Online change Enable
Setting change Enable/disable

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

218 8.18 Modem Communication
Access procedure
The following is the procedure for accessing the programmable controller CPU using modem communication.
<When using Q series-compatible C24 or L series-compatible C24>

Start

Set the software switches. (1)

In the sequence program, set the following items. (2)

1) Write the AT command (ATS0=1).
2) Set the initialization request.

Start Communication Setup Utility and set the items on (3)

Communication Setting Wizard.

On the communication test screen, check whether (4)

communication can be performed properly. *1

Complete

*1 If normal communication cannot be performed, refer to "Flowchart for When Access cannot be Performed during Modem
Communication" ( Page 403 Flowchart for When Access cannot be Performed during Modem Communication) and take corrective
action.
(1)Page 218 Switch settings of Q series-compatible C24, L series-compatible C24
8
(2)Page 221 Connecting Q series-compatible C24 or L series-compatible C24 to the modem
(3)Page 232 Setting the logical station number (setting on Communication Setting Wizard)
(4)Page 234 Checking the logical station number settings (conducting a communication test)
<When FXCPU is used>

Start

Set the FXCPU and connect it to the modem. (1)

Start Communication Setup Utility and set the items on

(2)
Communication Setting Wizard.

On the communication test screen, check whether (3)

communication can be performed properly. *1

Complete

*1 If normal communication cannot be performed, refer to "Flowchart for When Access cannot be Performed during Modem
Communication" (Page 403 Flowchart for When Access cannot be Performed during Modem Communication) and take corrective
action.
(1)GX Works2 Version 1 Operating Manual (Common)
(2)Page 232 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 234 Checking the logical station number settings (conducting a communication test)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.18 Modem Communication 219
 System example
The following system examples are used in this section.

<Q series-compatible C24, L series-compatible C24>

<FXCPU>
Q series-compatible C24
Q25HCPU L series-compatible C24 FX2NC
(Station No. 0)
Modem
ModemÓ Logical station number of
"15" is used.

Pushbutton dialing line (tone)

ModemÒ Modem
Personal computer Personal computer
(MX Component) (MX Component)
COM1 is used. COM1 is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

220 8.18 Modem Communication
Connecting Q series-compatible C24 or L series-compatible C24 to the modem
Using the Q series-compatible C24 or L series-compatible C24 requires a sequence program to set the following buffer
memory addresses.
The following table indicates the buffer memory addresses that must be set and the sequence program.
Setting Item (Buffer Memory Setting
Address)
Modem connection channel designation 0: Not connected (modem function is not used)
(2EH) 1: CH1 side interface
2: CH2 side interface
Initialization data number designation 0H: Send of initialization data specified in the sending user registration frame specifying area
(34H)*1 7D0H to 7DDH: Initialization data number
GX Developer/MELSOFT connection 0: Not connected
designation (36H) 1: Connected
Callback function designation (2001H) 0H: Auto line connect
1H: Callback connect (Fixation)
3H: Callback connect (Number specification)
7H: Callback connect (Number specification (maximum of 10 modules))
9H: Auto line connect (Callback fixation)
BH: Auto line connect (Callback number specification)
FH: Auto line connect (Callback number specification (maximum of 10 modules))

*1 The following initialization data are factory-registered to Q series-compatible C24.

When the modem used corresponds to the initialization data (7D0H to 7DAH), specify the following registration number.
When using the modem where the initialization data is not registered, register the AT command to the buffer memory address (1B00H)
of Q series-compatible C24.

Registration Initialization Command Corresponding Device

Number
Hexad Decim Manufacturer Model 8
ecimal al
7D0H 2000 ATQ0V1E1X1\J0\Q2\V2\N3S0=1 Aiwa PV-AF2881WW
PV-BF288M2
7D1H 2001 ATQ0V1E1X1\Q2\V2\N3S0=1 Micro General Laboratory MC288XE
MC288X1
7D2H 2002 ATQ0V1E1X1&K3\N3S0=1 Microcom DESKPORTE22.8S
DESKPORTE33.6S
7D3H 2003 ATQ0V1E1X1&H1&R2&A3&D2S0=1 Omron ME3314B
7D4H 2004 ATQ0V1E1X1\J0\Q2\N3S0=1 Sun Electronic MS336AF
7D5H 2005 ATE1Q0V1&C1&D2&H1&I0&R2&S0S0=1 Omron ME5614B
7D6H 2006 ATE1Q0V1&C1&D2&K3&S0S0=1 Sun Electronic MS56KAF
Micro General Laboratory MRV56XL
Matsushita Electric VS-2621A
7D7H 2007 ATE1Q0V1&C1&D2&K3&S1S0=1 VC-173
7D8H 2008 ATE1Q0V1&C1&D2&K3&S0S0=1 Omron MT128B II -D
7D9H 2009 ATE1Q0V1&C1&D1\Q2&S0S0=1 Sun Electronic TS128JX II
7DAH 2010 ATE1Q0V1&C1&D2\Q3&S0S0=1 Sharp DN-TA1
7DCH 2012 AT&S0S0=1 Gener * Use this device for operation check.
al If the device does not operate, create the initialization command which
7DDH 2013 ATX1&S0S0=1
matches the modem specifications on the user side.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.18 Modem Communication 221
 ■When callback function is not used
Setting Item (Buffer Memory Address) Setting
Modem connection channel designation (2EH) 1 (CH1)
Initialization data number designation (34H) 2006 (No. 2006)
GX Developer/MELSOFT connection designation (36H) 1 (Connected)
Callback function designation (2001H) 

This sample sequence program is installed into the following folders after installation of MX Component.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

222 8.18 Modem Communication
[User-specified folder] - [Act] - [Samples] - [GppW] - [QJ71C24TEL]

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.18 Modem Communication 223
 ■When "Auto line connect (Callback fixation)" is used as callback function
Setting Item (Buffer Memory Address) Setting
Modem connection channel designation (2EH) 1 (CH1)
Initialization data number designation (34H) 2012 (No. 2012)
GX Developer/MELSOFT connection 1 (Connected)
designation (36H)
Callback function designation (2001H) 9H (Auto line connect (Callback fixation))

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

224 8.18 Modem Communication
 8

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.18 Modem Communication 225
 This sample sequence program is installed into the following folders after installation of MX Component.
[User-specified folder] - [Act] - [Samples] - [GppW] - [QJ71C24Callback]

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

226 8.18 Modem Communication
■When "Auto line connect (Callback number specification (maximum of 10 modules))" is used
as callback function
Setting Item (Buffer Memory Address) Setting
Modem connection channel designation (2EH) 1 (CH1)
Initialization data number designation (34H) 2012 (No. 2012)
GX Developer/MELSOFT connection 1 (Connected)
designation (36H)
Callback function designation (2001H) FH (Auto line connect (Callback number specification (maximum of 10 modules)))

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.18 Modem Communication 227
 8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE
228 8.18 Modem Communication
 8

This sample sequence program is installed into the following folders after installation of MX Component.
[User-specified folder] - [Act] - [Samples] - [GppW] - [QJ71C24Callback_Number]

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.18 Modem Communication 229
 Connecting FXCPU and the modem
A sequence program is required for the use of FXCPU.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

230 8.18 Modem Communication
 8

This sample sequence program is installed into the following folders after installation of MX Component.
[User-specified folder] - [Act] - [Samples] - [GppW] - [FXCPUTEL]

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.18 Modem Communication 231
 Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number for Q series-compatible C24 using the system example in this
section (Page 220 System example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "15" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Modem
Connect module: QJ71C24
Time out: 10000

4. Set the following items and click the [Next] button.

Line type: TONE
Outside line number: None
Port: COM1
Call number: **********
(Enter the programmable controller side phone
number.)
AT command: Modem standard

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

232 8.18 Modem Communication
 5. Set the following items and click the [Next] button.
PLC side I/F: Modem
Module type: QJ71C24
Station No: 0
Transmission speed: 19200

6. Set the following items and click the [Next] button.

Station type: Host station
CPU type: Q25H
Multiple CPU: None

7. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.18 Modem Communication 233
 Checking the logical station number settings (conducting a communication test)
Check the modem communication settings, using the logical station number set in this section (Page 232 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "15".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "15".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

234 8.18 Modem Communication
8.19 Gateway Function Communication
This section provides the gateway function communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the GOT using gateway function communication.

Start

Set the GOT.

(1)

Connect the GOT to Ethernet.

Connect the personal computer to Ethernet.

Edit the HOSTS file. *1

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (2)

On the communication test screen, check whether

communication can be performed properly. (3) 8

Complete

*1 The HOSTS file is not required to be edited when entering the IP address in the host name (IP address) of Communication Setup Utility
and the ActHostAddress property of the Ethernet communication control.
(1) GOT operating manual
(2)Page 236 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 238 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Personal computer (MX Component)

Logical station number of "16" is used.

Ethernet

GOT (192.168.0.1)

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.19 Gateway Function Communication 235
 Performing communications check
After completion of preparations for performing gateway function communication, execute ping in the MS-DOS mode before
starting communication using MX Component.
• When normal
C:\>ping 192.168.0.1
Reply from 192.168.0.1 : bytes=32 time<10ms TTL=32
• When abnormal
C:\>ping 192.168.0.1
Request timed out.
If ping does not pass through, check cable and module connections and Windows side IP address and other settings.

Setting the logical station number (setting on Communication Setting Wizard)

The following explains how to set the logical station number using the system example in this section (Page 235 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "16" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Ethernet board
Connect module: GOT
Port No: 5011
Time out: 60000

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

236 8.19 Gateway Function Communication
 4. Set the following items and click the [Next] button.
PLC side I/F: Ethernet module
Module type: GOT
Host (IP Address): 192.168.0.1

5. Enter a comment and click the [Finish] button.

8
Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.19 Gateway Function Communication 237
 Checking the logical station number settings (conducting a communication test)
Check the gateway function communication settings, using the logical station number set in this section (Page 236
Setting the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "16".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "16".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

238 8.19 Gateway Function Communication
8.20 GOT Transparent Communication
This section provides the GOT transparent communication procedure and its setting example using the utility setting type.

For applicable system configuration, refer to the following manual.

 Connection manuals for GOT2000 series
(Mitsubishi Products), (Non-Mitsubishi Products 1), (Non-Mitsubishi Products 2), (Microcomputer, MODBUS/
Fieldbus Products, Peripherals)
 Connection manuals for GOT1000 series
(Mitsubishi Products), (Non-Mitsubishi Products 1), (Non-Mitsubishi Products 2), (Microcomputer, MODBUS
Products, Peripherals)

Access procedure
The following is the procedure for accessing the GOT using GOT transparent communication.

Start

Set the GOT.

Connect the GOT to personal computer. (1)

Connect the GOT to the programmable controller CPU. 8

Install the USB driver. (2)

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (3)

On the communication test screen, check whether

communication can be performed properly. (4)

Complete

(1) GOT operating manual

(2)Page 423 USB Driver Installation
(3)Page 240 Setting the logical station number (setting on Communication Setting Wizard)
(4)Page 243 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Q02H Normal station

CPU (Sta. No.2)

GOT MELSECNET/H
(Network No. 1)

Personal computer
(MX Component) USB Q02H Normal station
port is used. CPU (Sta. No.8)
Logical station number of "17" is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.20 GOT Transparent Communication 239
 Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 239 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "17" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: USB (via GOT)
Time out: 10000

4. Set the following items and click the [Next] button.

GOT - PLC I/F: Serial
Connect module: CPU module

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

240 8.20 GOT Transparent Communication
 5. Set the following items and click the [Next] button.
PLC side I/F: CPU module
CPU type: Q02(H)

6. Set the following items and click the [Next] button.

Station type: Other station
Network: MELSECNET/10(H)
Mode: MELSECNET/H

7. Set the following items and click the [Next] button.

CPU type: Q02(H)
Network No.: 1
Station No.: 8
Multiple CPU: None

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.20 GOT Transparent Communication 241
 8. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

242 8.20 GOT Transparent Communication
Checking the logical station number settings (conducting a communication test)
Check the GOT transparent communication settings, using the logical station number set in this section (Page 240
Setting the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "17".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "17".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation and PLC Monitor Utility.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.20 GOT Transparent Communication 243
 8.21 Inverter COM Communication
section provides the inverter COM communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the inverter using inverter COM communication.

Start

Connect the inverter and personal computer. (1)

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (2)

On the communication test screen, check whether

communication can be performed properly. (3)

Complete

(1)Page 30 SYSTEM CONFIGURATIONS

(2)Page 245 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 247 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Inverter

Personal computer
(MX Component)
COM1 is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

244 8.21 Inverter COM Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 244 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "20" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Serial
Connect port: COM1
Time out: 10000
8

4. Set the following items and click the [Next] button.

PLC side I/F: Inverter
Inverter: A800
Station No: 0
Transmission speed: 19200
Parity: Even
Data bit: 8
Stop bit: 1
Delimiter: CR
Transmission wait time: 0

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.21 Inverter COM Communication 245
 5. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

246 8.21 Inverter COM Communication
Checking the logical station number settings (conducting a communication test)
Check the inverter COM communication settings, using the logical station number set in this section (Page 245 Setting
the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "20".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "20".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.21 Inverter COM Communication 247
 8.22 Inverter USB Communication
This section provides the inverter USB communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the inverter using inverter USB communication.

Start

Connect the inverter and personal computer. (1)

Install the USB driver. (2)

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (3)

On the communication test screen, check whether

(4)
communication can be performed properly.

Complete

(1)Page 30 SYSTEM CONFIGURATIONS

(2)Page 423 USB Driver Installation
(3)Page 249 Setting the logical station number (setting on Communication Setting Wizard)
(4)Page 251 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Inverter

Personal computer
(MX Component)
USB port is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

248 8.22 Inverter USB Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 248 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "24" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: USB
Time out: 10000

4. Set the following items and click the [Next] button.

PLC side I/F: Inverter
Inverter: A800
Station No: 0
Transmission wait time: 0

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.22 Inverter USB Communication 249
 5. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

250 8.22 Inverter USB Communication
Checking the logical station number settings (conducting a communication test)
Check the inverter USB communication settings, using the logical station number set in this section (Page 249 Setting the
logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "24".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "24".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.22 Inverter USB Communication 251
 8.23 Robot controller COM Communication
This section provides the robot controller COM communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the robot controller using robot controller COM communication.

Start

Connect the robot controller and personal computer. (1)

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (2)

On the communication test screen, check whether

communication can be performed properly. (3)

Complete

(1)Page 30 SYSTEM CONFIGURATIONS

(2)Page 253 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 255 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Robot controller

Personal computer
(MX Component)
COM1 is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

252 8.23 Robot controller COM Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 252 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "22" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Serial
Connect port: COM1
Time out: 10000
8

4. Set the following items and click the [Next] button.

PLC side I/F: Robot controller
R/C type: CRnD-7xx/CR75x-D
Transmission speed: 19200
Parity: Even
Character Size: 8
Stop bit: 1
Send timeout: 5000
Receive timeout : 30000
Retries : 3
Usage protocol : Procedural

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.23 Robot controller COM Communication 253
 5. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

254 8.23 Robot controller COM Communication
Checking the logical station number settings (conducting a communication test)
Check the robot controller COM communication settings, using the logical station number set in this section (Page 253
Setting the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "22".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "22".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.23 Robot controller COM Communication 255
 8.24 Robot controller USB Communication
This section provides the robot controller USB communication procedure and its setting example using the utility setting type.

Access procedure
The following is the procedure for accessing the robot controller using robot controller USB communication.

Start

Connect the robot controller and personal computer. (1)

Install the USB driver. (2)

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (3)

On the communication test screen, check whether communication

can be performed properly. (4)

Complete

(1)Page 30 SYSTEM CONFIGURATIONS

(2)Page 423 USB Driver Installation
(3)Page 257 Setting the logical station number (setting on Communication Setting Wizard)
(4)Page 259 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Robot controller

Personal computer
(MX Component)
USB port is used.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

256 8.24 Robot controller USB Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 256 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "23" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: USB
Time out: 10000

4. Set the following items and click the [Next] button.

PLC side I/F: Robot controller
R/C type: CRnD-7xx/CR75x-D
Send timeout: 5000
Receive timeout: 30000
Retries: 3

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.24 Robot controller USB Communication 257
 5. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

258 8.24 Robot controller USB Communication
Checking the logical station number settings (conducting a communication test)
Check the robot controller USB communication settings, using the logical station number set in this section (Page 257
Setting the logical station number (setting on Communication Setting Wizard)).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "23".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "23".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.24 Robot controller USB Communication 259
 8.25 Robot controller Ethernet Communication
This section provides the robot controller Ethernet communication procedure and its setting example using the utility setting
type.

Access procedure
The following is the procedure for accessing the robot controller using robot controller Ethernet communication.

Start

Connect the robot controller to Ethernet. (1)

Connect the personal computer to Ethernet.

Start Communication Setup Utility and set the items on

Communication Setting Wizard. (2)

On the communication test screen, check whether

communication can be performed properly. (3)

Complete

(1) Robot controller Manual

(2)Page 261 Setting the logical station number (setting on Communication Setting Wizard)
(3)Page 263 Checking the logical station number settings (conducting a communication test)

System example
The following system example is used in this section.

Personal computer
Logical station number of "24" is used.

Robot
controller

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

260 8.25 Robot controller Ethernet Communication
Setting the logical station number (setting on Communication Setting Wizard)
The following explains how to set the logical station number using the system example in this section (Page 260 System
example).

Operating procedure
1. Start Communication Setup Utility and click the [Wizard]
button.

2. Enter "24" in Logical station number and click the [Next]

button.

3. Set the following items and click the [Next] button.

PC side I/F: Ethernet board
Connect module: Robot controller
Port No: 10001
8

4. Set the following items and click the [Next] button.

PLC side I/F: Robot controller
R/C type: CRnD-7xx/CR75x-D
Host (IP Address): 192.168.0.1
Send timeout: 5000
Receive timeout: 30000
Retries: 3

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.25 Robot controller Ethernet Communication 261
 5. Enter a comment and click the [Finish] button.

Registration complete

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

262 8.25 Robot controller Ethernet Communication
Checking the logical station number settings (conducting a communication test)
Check the robot controller Ethernet communication settings, using the logical station number set in Page 261 Setting the
logical station number (setting on Communication Setting Wizard).

Operating procedure
1. Click the [Target setting] tab and select the logical
station number "24".
Check the logical station number settings.

2. Click the [Connection test] tab and select the logical

station number "24".

3. Click the [Test] button to check that communication is

being performed normally.
Click! If an error occurs, check the error code and remove the
error.
The error code is displayed in Result. (At normal
termination, "0x00000000" is displayed in Result.)
For details of error code, refer to the following manual.
MX Component Version 4 Programming Manual

Communication test complete Through the above steps, it is confirmed that the logical
station number settings are correct.
This logical station number can be used for user program
creation.
Collect device data, using this logical station number.

8 COMMUNICATION SETTING EXAMPLES OF UTILITY SETTING TYPE

8.25 Robot controller Ethernet Communication 263
 9 COMMUNICATION SETTING EXAMPLES OF
PROGRAM SETTING TYPE
To perform communication using the program setting type, the properties of the corresponding ACT controls is required to be
set.
For the properties of the corresponding ACT controls, directly enter them on the property window or change their settings in
the user program.
For details of the properties which must be set for the corresponding ACT controls, refer to the following manual.
MX Component Version 4 Programming Manual
For module settings when using MX Component, refer to the following sections.
Item Reference
Serial communication Page 134 Serial Communication
Ethernet communication (when using Ethernet modules) Page 144 Ethernet Communication (When Using Ethernet Modules)
CC-Link G4 communication Page 180 CC-Link G4 Communication
Modem communication Page 218 Modem Communication

Setting properties using Communication Setting Wizard

On MX Component, the following property setting method is available for those who are not familiar with property setting.

Operating procedure
1. Specify the communication route where the property
settings are to be set using the "Communication
Setting Wizard" on Communication Setup Utility.
For details of Communication Setting Wizard, refer to
the following section.
Page 98 Operations on Communication Setting
Wizard screens

2. Click the [List View] tab.

For details of the [List View] tab, refer to the following
section.
Page 94 Operations on List view tab

9 COMMUNICATION SETTING EXAMPLES OF PROGRAM SETTING TYPE

264
 3. Select "Program" from "Display".

9
Click!

4. Control the scroll bar to confirm the properties.

The file can be saved in the .txt format by clicking the [Save
Control names to be used and
properties to be set are displayed.
text] button on the [List View] tab.

Saved into file

in .txt format.

5. When creating a user program, directly enter the

confirmed property values into Properties of the
property window or change the property setting in the
user program.
The screen shown left uses Visual Basic.

Directly enter properties in property window

or change property setting on the user program.

9 COMMUNICATION SETTING EXAMPLES OF PROGRAM SETTING TYPE

265
 10 ACCESSIBLE RANGES
This chapter provides the accessible ranges in each communication form.

10.1 Considerations for Access Targets

The following devices and CPUs are not supported by MX Component. Therefore, do not specify them.
• Devices that are not in the list of accessible devices
• Connected station CPUs and relayed station CPUs that are not in the list of accessible devices

10 ACCESSIBLE RANGES
266 10.1 Considerations for Access Targets
10.2 For Serial Communication
This section provides the accessible devices and accessible ranges for serial communication.

Accessible devices
10
The following table indicates the accessible devices for serial communication.

When access target is programmable controller CPU

Device (device name) Access target
RCPU RCCPU LHCPU QCPU QCCPU LCPU QSCPU FXCPU
(Q mode)
Function input (FX)        
Function output (FY)        
Function register (FD)        
Special relay (SM)        
Special register (SD)        
Input relay (X)        *1
Output relay (Y)        *1
Internal relay (M)        *1
Latch relay (L)        
Annunciator (F)        
Edge relay (V)        
Link relay (B)     *2   
Data register (D)        *1
Link register (W)     *2   
Timer (T) Contact (TS)        *1
Coil (TC)        
Present value (TN)        *1
Counter (C) Contact (CS)        *1
Coil (CC)        
Present value (CN)        *1
Retentive timer (ST) Contact (STS/SS)        
Coil (STC/SC)        
Present value (STN/SN)        
Long timer (LT) Contact (LTS)        
Coil (LTC)        
Present value (LTN)        
Long counter (LC) Contact (LCS)        
Coil (LCC)        
Present value (LCN)        
Long retentive timer Contact (LSTS/LSS)        
(LST)
Coil (LSTC/LSC)        
Present value (LSTN/        
LSN)
Link special relay (SB)        
Link special register (SW)        
Step relay (S)        *1
Direct input (DX)        
Direct output (DY)        
Accumulator (A)        
Index register (Z)        *1
(V)        *1
Long index register (LZ)        

10 ACCESSIBLE RANGES
10.2 For Serial Communication 267
 Device (device name) Access target
RCPU RCCPU LHCPU QCPU QCCPU LCPU QSCPU FXCPU
(Q mode)
File register (R)    *3    *4
*3
(ZR)        
Refresh device for modules (RD)        
Extended file register (ER*\R)        
Direct link Link input (J*\X)        
Link output (J*\Y)        
Link relay (J*\B)        
Link special relay (J*\SB)        
Link register (J*\W)        
Link special register        
(J*\SW)
Special direct buffer memory (U*\G)    *5    

*1 FX0CPU, FX0SCPU, FX1CPU, FXUCPU, and FX2CCPU cannot be accessed when using the FX extended port.
*2 Q12DCCPU-V (Basic mode) cannot be accessed.
*3 Q00JCPU and Q00UJCPU cannot be accessed.
*4 When specifying a file register in FX series CPU other than FX3G(C)CPU and FX3U(C)CPU, specify the data register (D). The extended
register (R) can be specified only in FX3G(C)CPU or FX3U(C)CPU.
*5 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.

10 ACCESSIBLE RANGES
268 10.2 For Serial Communication
When access target is Motion CPU
Device (device name) Access target
R16MT/R32MT Q172/Q173/ Q172D/Q173D Q172DS/Q173DS
Q172H/Q173H
Input relay (X)
Output relay (Y)








10
Internal relay (M)    
Latch relay (L)    
Annunciator (F)    
Link relay (B)    
Data register (D)    
Link register (W)    
Special register M (SPM)    
Special register D (SPD)    
Motion register (#)    
Coasting timer (FT)    
Special register (SD)    
Special relay (SM)    
*1
CPU buffer Multiple CPU area device    *1
memory access (U3En\G)
device
CPU buffer memory    
(U3En\G)
CPU buffer memory fixed    
scan communication area
(U3En\HG)
Module access device (U*\G)    

*1 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.

10 ACCESSIBLE RANGES
10.2 For Serial Communication 269
 Accessible ranges
This section indicates the accessible ranges for serial communication.

Configuration

Connected station
Connected module Relayed module
CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Connected Relayed network Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU R series-compatible CC IE TSN     
C24 *2
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)
Multi-drop connection     
(Synchronous mode)*6

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
RCPU R series-compatible CC IE TSN      
C24
CC IE Control   *2   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)
Multi-drop connection      
(Synchronous mode)*6

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCCPU*3 R series-compatible CC IE TSN     
C24
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
270 10.2 For Serial Communication
Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
RCCPU*3 R series-compatible CC IE TSN      
C24
CC IE Control      
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion LHCPU FX5CPU
CPU
R motion R series-compatible CC IE TSN     
CPU*3*8 C24
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCP
mode) CPU U
R motion R series-compatible CC IE TSN      
CPU*3*8 C24
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion LHCPU FX5CPU
CPU
QCPU (Q Q series-compatible CC IE TSN     
mode), C24
CC IE Control     
QCCPU*3
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)
Multi-drop connection     
(Synchronous mode)*6

10 ACCESSIBLE RANGES
10.2 For Serial Communication 271
 Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
QCPU (Q Q series-compatible CC IE TSN      
mode), C24 *1 *2 *1 *1
CC IE Control      
QCCPU*3
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication *4     
CC-Link      *5
*4
Multi-drop connection      
(Independent mode)
Multi-drop connection *4     
(Synchronous mode)*6

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
Q motion CPU Q series-compatible CC IE TSN     
C24
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
Q motion CPU Q series-compatible CC IE TSN      
C24
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU L series-compatible CC IE TSN     
C24
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)
Multi-drop connection     
(Synchronous mode)

10 ACCESSIBLE RANGES
272 10.2 For Serial Communication
Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCP
mode) CPU U
LCPU L series-compatible CC IE TSN      
C24 *1
CC IE Field      
MELSECNET/H
Ethernet












10
Serial communication *4     
CC-Link      
*4
Multi-drop connection      
(Independent mode)
Multi-drop connection *4     
(Synchronous mode)

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU FX extended port CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
FXCPU FX extended port CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      *7
CC-Link      

*1 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode), QSCPU, and Q motion CPU relayed by CC-Link IE Field
Network cannot be accessed.
*2 Since CC-Link IE Controller Network is not supported, RCPU and LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*4 For redundant CPU, serial communication modules on the main base cannot be accessed.
*5 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.
*6 Validate "SW6 (sum check)" for the transmission specification software switch setting of the R series-compatible C24 and Q series-
compatible C24 parameter.
*7 FX0CPU, FX0SCPU, FX1CPU, FXUCPU, and FX2CCPU cannot be accessed.
*8 Relayed station CPUs cannot be accessed via R motion CPU.

10 ACCESSIBLE RANGES
10.2 For Serial Communication 273
 10.3 For Ethernet Communication
This section provides the accessible devices and accessible ranges for Ethernet communication.

Accessible devices
The following table indicates the accessible devices for Ethernet communication.

When access target is programmable controller CPU

Device (device name) Access target
RCPU RCCPU LHCPU FX5CP QCPU (Q QCCP LCPU QSCPU FXCP
*1
U mode) U U*2
Function input (FX)         
Function output (FY)         
Function register (FD)         
Special relay (SM)         
Special register (SD)         
Input relay (X)         
Output relay (Y)         
Internal relay (M)         
Latch relay (L)         
Annunciator (F)         
Edge relay (V)         
Link relay (B)      *3   
Data register (D)         
Link register (W)      *3   
Timer (T) Contact (TS)         
Coil (TC)         
Present value (TN)         
Counter (C) Contact (CS)         
Coil (CC)         
Present value (CN)         
Retentive timer (ST) Contact (STS/SS)         
Coil (STC/SC)         
Present value (STN/SN)         
Long timer (LT) Contact (LTS)         
Coil (LTC)         
Present value (LTN)         
Long counter (LC) Contact (LCS)         
Coil (LCC)         
Present value (LCN)         
Long retentive timer Contact (LSTS/LSS)         
(LST)
Coil (LSTC/LSC)         
Present value (LSTN/LSN)         
Link special relay (SB)         
Link special register (SW)         
Step relay (S)         
Direct input (DX)         
Direct output (DY)         
Accumulator (A)         
Index register (Z)         
(V)         
Long index register (LZ)         

10 ACCESSIBLE RANGES
274 10.3 For Ethernet Communication
Device (device name) Access target
RCPU RCCPU LHCPU FX5CP QCPU (Q QCCP LCPU QSCPU FXCP
*1
U mode) U U*2
File register (R)     *4    
*4
(ZR)         
Refresh device for modules (RD)
Extended file register (ER*\R)


















10
Direct link Link input (J*\X)         
Link output (J*\Y)         
Link relay (J*\B)         
Link special relay (J*\SB)         
Link register (J*\W)         
Link special register         
(J*\SW)
Module access device (U*\G)     *5    

*1 Writing to device data cannot be performed.

*2 For the supported FXCPU and devices, refer to the manuals of Ethernet module and setting software.
*3 Q12DCCPU-V (Basic mode) cannot be accessed.
*4 Q00JCPU and Q00UJCPU cannot be accessed.
*5 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.

10 ACCESSIBLE RANGES
10.3 For Ethernet Communication 275
 When access target is RnSFCPU (Safety devices)
The safety devices described in the following table can be used when access target is RnSFCPU.
The safety mode is read-only. An attempt to write into the safety device will cause an error.
Device (device name) Access target
RnSFCPU
Safety input (SA\X) 
Safety output (SA\Y) 
Safety internal relay (SA\M) 
Safety link relay (SA\B) 
Safety timer (SA\T) 
Safety retentive timer (SA\ST) 
Safety counter (SA\C) 
Safety data register (SA\D) 
Safety link register (SA\W) 
Safety special relay (SA\SM) 
Safety special register (SA\SD) 

When access target is Motion CPU

For accessible device list of Motion CPU, refer to the following section.
Page 269 When access target is Motion CPU

10 ACCESSIBLE RANGES
276 10.3 For Ethernet Communication
Accessible ranges (when using Ethernet modules)
This section indicates the accessible ranges for Ethernet communication using the Ethernet modules.

Configuration
10
Connected station
Connected module Relayed module
CPU

Relayed network
Ethernet

Relayed station Relayed module

Personal computer
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).

The Ethernet parameters are required to be set in the PLC parameter setting of GX Works2/GX Works3.

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU, R R series-compatible CC IE TSN     
motion CPU*4*7 E71*8
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
RCPU, R R series-compatible CC IE TSN      
motion CPU*4*7 E71*8
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCCPU*4 R series-compatible CC IE TSN     
E71
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
10.3 For Ethernet Communication 277
 Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
RCCPU*4 R series-compatible CC IE TSN      
E71
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q Q series-compatible CC IE TSN     
mode), E71
CC IE Control     
QCCPU*4
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
QCPU (Q Q series-compatible CC IE TSN      
mode), E71 *2 *3 *2 *2
CC IE Control      
QCCPU*4
CC IE Field
MELSECNET/H      
*5
Ethernet      
Serial communication *6     
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
QSCPU*1, Q Q series-compatible CC IE TSN     
motion CPU*4*5 E71
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
QSCPU*1, Q Q series-compatible CC IE TSN      
motion CPU*4*5 E71
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

10 ACCESSIBLE RANGES
278 10.3 For Ethernet Communication
Connected Connected Relayed network Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU L series-compatible CC IE TSN     
E71
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
10
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCP
mode) CPU*5 U
LCPU L series-compatible CC IE TSN      
E71 *2 *3 *1*2 *2
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet    *1  
Serial communication *6  *6  *6 
CC-Link      

*1 Relayed station CPUs cannot be accessed via QSCPU.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode), QSCPU, and Q motion CPU relayed by CC-Link IE Field
Network cannot be accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*5 Only Q172D, Q173D, Q172DS, and Q173DS can be accessed.
*6 For redundant CPU, serial communication modules on the main base cannot be accessed.
*7 Relayed station CPUs cannot be accessed via R motion CPU.
*8 Relayed station CPUs cannot be accessed when directly connecting to an R series-compatible E71.

10 ACCESSIBLE RANGES
10.3 For Ethernet Communication 279
 Accessible ranges (when using Built-in Ethernet CPUs)
This section indicates the accessible ranges for Ethernet communication using the built-in Ethernet CPUs.

Configuration

Connected station
Relayed module
CPU

Relayed network
Ethernet

Relayed station Relayed module

Personal computer
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).

When using TCP/IP on the built-in Ethernet CPU, the Ethernet parameters are required to be set in the PLC
parameter setting of GX Works2/GX Works3.

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU CC IE TSN     
CC IE Control *2    *8
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
RCPU CC IE TSN      
CC IE Control   *2   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*5
RCCPU CC IE TSN     
CC IE Control *2    
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
280 10.3 For Ethernet Communication
Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
RCCPU*5 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
R motion CPU*5*7 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
R motion CPU*5*7 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LHCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LHCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

10 ACCESSIBLE RANGES
10.3 For Ethernet Communication 281
 Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FX5CPU CC IE TSN     
CC IE Control     *8
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FX5CPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QnUDE(H)CPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QnUDE(H)CPU CC IE TSN      
*1 *2 *1 *1
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication *3     
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU*4*5 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
282 10.3 For Ethernet Communication
Connected station Relayed network Relayed station CPU
CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
*4*5
QCCPU CC IE TSN      
CC IE Control  *1 *2 *1 *1 
CC IE Field
MELSECNET/H      
Ethernet      
10
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
Q motion CPU*5*6 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
Q motion CPU*5*6 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LCPU CC IE TSN      
CC IE Field  *1    
MELSECNET/H      
Ethernet      
Serial communication *3     
CC-Link      

*1 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode), QSCPU, and Q motion CPU relayed by CC-Link IE Field
Network cannot be accessed.
*2 Since CC-Link IE Controller Network is not supported, RCPU and LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.
*4 QCCPU does not support MELSOFT direct connection. It cannot be accessed with Ethernet port direct connection.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*6 Only Q172D, Q173D, Q172DS, and Q173DS can be accessed.
*7 Relayed station CPUs cannot be accessed via R motion CPU.
*8 Only CC-Link IE Field Network can be accessed.

10 ACCESSIBLE RANGES
10.3 For Ethernet Communication 283
 Accessible ranges (for transferring logging files using built-in
Ethernet CPUs)
This section indicates the accessible ranges for transferring logging files using a built-in Ethernet CPU.

Configuration

Connected station
CPU

Ethernet

Personal computer

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs described in this section are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).

When using TCP/IP in a built-in Ethernet CPU, setting the module parameter in GX Works3 is required.

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
RCPU*1 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LHCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
284 10.3 For Ethernet Communication
Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LHCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

*1 RnPCPUs (redundant mode) are not supported.

10 ACCESSIBLE RANGES
10.3 For Ethernet Communication 285
 Accessible ranges (when using Ethernet adapter module)
This section indicates the accessible ranges for Ethernet communication using the Ethernet adapter module.

Configuration

Connected station CC-Link IE Field

Relayed module
CPU Network module

Ethernet adapter
Relayed network
module

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QnUDE(H)CPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QnUDE(H)CPU CC IE TSN      
CC IE Control  *1 *2   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
286 10.3 For Ethernet Communication
Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LCPU CC IE TSN      
*1
CC IE Field      
MELSECNET/H
Ethernet












10
Serial communication      
CC-Link      

*1 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

10 ACCESSIBLE RANGES
10.3 For Ethernet Communication 287
 Accessible ranges (when using Ethernet adapter)
This section indicates the accessible ranges for Ethernet communication using Ethernet adapter.

Configuration

Connected station
Ethernet adapter Relayed module
CPU

Relayed network

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FXCPU*1 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Only FX3SCPU, FX3G(C)CPU, and FX3U(C)CPU can be accessed.

10 ACCESSIBLE RANGES
288 10.3 For Ethernet Communication
Accessible ranges (when using CC-Link IE TSN modules)
This section indicates the accessible ranges for Ethernet communication using a CC-Link IE TSN module.

Configuration
10
Connected station CC-Link IE TSN
Relayed module
CPU module

Relayed network
Ethernet

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
RCPU*1 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Access to a CC-Link IE TSN module with a direct connection is not supported.

10 ACCESSIBLE RANGES
10.3 For Ethernet Communication 289
 10.4 For CPU COM Communication
This section provides the accessible devices and accessible ranges for CPU COM communication.

Accessible devices
The following table indicates the accessible devices for CPU COM communication.

When access target is programmable controller CPU

Device (device name) Access target
RCPU RCCPU LHCPU FX5CP QCPU QCCPU LCPU QSCP FXCP
U (Q mode) U U
Function input (FX)         
Function output (FY)         
Function register (FD)         
Special relay (SM)         
Special register (SD)         
Input relay (X)         
Output relay (Y)         
Internal relay (M)         
Latch relay (L)         
Annunciator (F)         
Edge relay (V)         
Link relay (B)      *1   
Data register (D)         
Link register (W)      *1   
Timer (T) Contact (TS)         
Coil (TC)         
Present value (TN)         
Counter (C) Contact (CS)         
Coil (CC)         
Present value (CN)         
Retentive timer (ST) Contact (STS/SS)         
Coil (STC/SC)         
Present value (STN/SN)         
Long timer (LT) Contact (LTS)         
Coil (LTC)         
Present value (LTN)         
Long counter (LC) Contact (LCS)         
Coil (LCC)         
Present value (LCN)         
Long retentive timer Contact (LSTS/LSS)         
(LST)
Coil (LSTC/LSC)         
Present value (LSTN/LSN)         
Link special relay (SB)         
Link special register (SW)         
Step relay (S)         
Direct input (DX)         
Direct output (DY)         
Accumulator (A)         
Index register (Z)         
(V)         
Long index register (LZ)         

10 ACCESSIBLE RANGES
290 10.4 For CPU COM Communication
 Device (device name) Access target
RCPU RCCPU LHCPU FX5CP QCPU QCCPU LCPU QSCP FXCP
U (Q mode) U U
File register (R)     *2    *3
*2
(ZR)         
Refresh device for modules (RD)
Extended file register (ER*\R)


















10
Direct link Link input (J*\X)         
Link output (J*\Y)         
Link relay (J*\B)         
Link special relay (J*\SB)         
Link register (J*\W)         
Link special register         
(J*\SW)
Module access device (U*\G)     *4    *5

*1 Q12DCCPU-V (Basic mode) cannot be accessed.

*2 Q00JCPU and Q00UJCPU cannot be accessed.
*3 When specifying a file register in FX series CPU other than FX3G(C)CPU and FX3U(C)CPU, specify the data register (D). The extended
register (R) can be specified only in FX3G(C)CPU or FX3U(C)CPU.
*4 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.
*5 Only FX3U(C)CPU can be accessed.

When access target is Motion CPU

For accessible device list of Motion CPU, refer to the following section.
Page 269 When access target is Motion CPU

10 ACCESSIBLE RANGES
10.4 For CPU COM Communication 291
 Accessible ranges
This section indicates the accessible ranges for CPU COM communication.

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FX5CPU CC IE TSN     
CC IE Control     *7
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FX5CPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode), CC IE TSN     
QCCPU*6 CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
292 10.4 For CPU COM Communication
Connected station Relayed network Relayed station CPU
CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
QCPU (Q mode), CC IE TSN      
QCCPU*6
CC IE Control  *1 *2 *1 *1 
CC IE Field
MELSECNET/H      
Ethernet      
10
Serial communication *4     
CC-Link      *5

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LCPU CC IE TSN      
CC IE Field  *1    
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
Q motion CPU*3*6 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
Q motion CPU*3*6 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

10 ACCESSIBLE RANGES
10.4 For CPU COM Communication 293
 Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FXCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      *5

*1 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode), QSCPU, and Q motion CPU relayed by CC-Link IE Field
Network cannot be accessed.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 Only Q172D, Q173D, Q172DS, and Q173DS can be accessed.
*4 For redundant CPU, serial communication modules on the main base cannot be accessed.
*5 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.
*6 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*7 Only CC-Link IE Field Network can be accessed.

10 ACCESSIBLE RANGES
294 10.4 For CPU COM Communication
10.5 For CPU USB Communication
This section provides the accessible devices and accessible ranges for CPU USB communication.

Accessible devices
10
The following table indicates the accessible devices for CPU USB communication.

When access target is programmable controller CPU

Device (device name) Access target
RCP RCCP LHCP FX5CP QCPU QCCP LCPU QSCPU* FXCPU
1
U U U U(FX5U (Q mode) U
J)
Function input (FX)         
Function output (FY)         
Function register (FD)         
Special relay (SM)         
Special register (SD)         
Input relay (X)         *2
Output relay (Y)         *2
Internal relay (M)         *2
Latch relay (L)         
Annunciator (F)         
Edge relay (V)         
*3
Link relay (B)         
Data register (D)         *2
Link register (W)      *3   
Timer (T) Contact (TS)         *2
Coil (TC)         *2
Present value (TN)         *2
Counter (C) Contact (CS)         *2
Coil (CC)         *2
Present value (CN)         *2
Retentive timer (ST) Contact (STS/SS)         
Coil (STC/SC)         
Present value (STN/SN)         
Long timer (LT) Contact (LTS)         
Coil (LTC)         
Present value (LTN)         
Long counter (LC) Contact (LCS)         
Coil (LCC)         
Present value (LCN)         
Long retentive timer Contact (LSTS/LSS)         
(LST)
Coil (LSTC/LSC)         
Present value (LSTN/LSN)         
Link special relay (SB)         
Link special register (SW)         
Step relay (S)         *2
Direct input (DX)         
Direct output (DY)         
Accumulator (A)         
Index register (Z)         *2
(V)         *2
Long index register (LZ)         

10 ACCESSIBLE RANGES
10.5 For CPU USB Communication 295
 Device (device name) Access target
RCP RCCP LHCP FX5CP QCPU QCCP LCPU QSCPU* FXCPU
1
U U U U(FX5U (Q mode) U
J)
File register (R)     *4    *2
(ZR)     *4    
Refresh device for modules (RD)         
Extended file register (ER*\R)         
Direct link Link input (J*\X)         
Link output (J*\Y)         
Link relay (J*\B)         
Link special relay (J*\SB)         
Link register (J*\W)         
Link special register         
(J*\SW)
Special direct buffer memory (U*\G)     *5    

*1 Writing to device data cannot be performed.

*2 When specifying a file register in FX series CPU other than FX3G(C)CPU and FX3U(C)CPU, specify the data register (D). The extended
register (R) can be specified only in FX3G(C)CPU or FX3U(C)CPU.
*3 Q12DCCPU-V (Basic mode) cannot be accessed.
*4 Q00JCPU and Q00UJCPU cannot be accessed.
*5 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.

When access target is RnSFCPU

For accessible device list of RnSFCPU, refer to the following section.
Page 276 When access target is RnSFCPU (Safety devices)

When access target is Motion CPU

For accessible device list of Motion CPU, refer to the following section.
Page 269 When access target is Motion CPU

10 ACCESSIBLE RANGES
296 10.5 For CPU USB Communication
Accessible ranges
This section indicates the accessible ranges for CPU USB communication.

Configuration
10
Connected station Relayed module
CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU, R motion CC IE TSN     
CPU*4*9
CC IE Control *3    *5
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
RCPU, R motion CC IE TSN      
CPU*4*9 *3
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LHCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
10.5 For CPU USB Communication 297
 Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LHCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FX5CPU*10 CC IE TSN     
CC IE Control     *11
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FX5CPU*10 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode), CC IE TSN     
QSCPU*1
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCPU (Q mode), CC IE TSN      
QSCPU*1
CC IE Control  *2 *3 *2 *2 
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication *6     
CC-Link      *7

10 ACCESSIBLE RANGES
298 10.5 For CPU USB Communication
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
10
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCCPU CC IE TSN      
*2 *3 *2 *2
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LCPU CC IE TSN      
CC IE Field  *2    
MELSECNET/H      
Ethernet      
Serial communication *6     
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
Q motion CPU*8 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
10.5 For CPU USB Communication 299
 Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
Q motion CPU*8 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FXCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      *7

*1 Relayed station CPUs cannot be accessed via QSCPU.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode), QSCPU, and Q motion CPU relayed by CC-Link IE Field
Network cannot be accessed.
*3 Since CC-Link IE Controller Network is not supported, RCPU and LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*5 Only CC-Link IE Field Network on which connected station CPU is RCPU can be accessed.
*6 For redundant CPU, serial communication modules on the main base cannot be accessed.
*7 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.
*8 Except for Q172, Q173, Q172H, and Q173H, only CPU No.2 or later in multiple CPU configuration can be accessed.
*9 Relayed station CPUs cannot be accessed via R motion CPU.
*10 Only FX5UJCPU can be accessed.
*11 Only CC-Link IE Field Network can be accessed.

10 ACCESSIBLE RANGES
300 10.5 For CPU USB Communication
Accessible ranges (for transferring logging files)
The following table indicates the accessible ranges for transferring logging files in a USB connection.

Configuration
10
Connected station
CPU

Personal computer

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs described in this section are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
RCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
RCPU*1 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LHCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
10.5 For CPU USB Communication 301
 Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LHCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 RnPCPUs (redundant mode) are not supported.

10 ACCESSIBLE RANGES
302 10.5 For CPU USB Communication
10.6 For CC-Link Communication
This section provides the accessible devices and accessible ranges for CC-Link communication.

Accessible devices
10
The following table indicates the accessible devices for CC-Link communication.

For another station access

Device (device name) Access target
RCPU RCCPU LHCPU QCPU QCCPU LCPU QSCPU FXCPU
(Q mode)
Function input (FX)        
Function output (FY)        
Function register (FD)        
Special relay (SM)        
Special register (SD)        
Input relay (X)        *1
Output relay (Y)        *1
Internal relay (M)        *1
Latch relay (L)        
Annunciator (F)        
Edge relay (V)        
Link relay (B)     *2   
Data register (D)        *1
Link register (W)     *2   
Timer (T) Contact (TS)        *1
Coil (TC)        *1
Present value (TN)        *1
Counter (C) Contact (CS)        *1
Coil (CC)        *1
Present value (CN)        *1
Retentive timer (ST) Contact (STS/SS)        
Coil (STC/SC)        
Present value (STN/SN)        
Long timer (LT) Contact (LTS)        
Coil (LTC)        
Present value (LTN)        
Long counter (LC) Contact (LCS)        
Coil (LCC)        
Present value (LCN)        
Long retentive timer Contact (LSTS/LSS)        
(LST)
Coil (LSTC/LSC)        
Present value (LSTN/        
LSN)
Link special relay (SB)        
Link special register (SW)        
Step relay (S)        *1
Direct input (DX)        
Direct output (DY)        
Accumulator (A)        
Index register (Z)        *1
(V)        *1
Long index register (LZ)        

10 ACCESSIBLE RANGES
10.6 For CC-Link Communication 303
 Device (device name) Access target
RCPU RCCPU LHCPU QCPU QCCPU LCPU QSCPU FXCPU
(Q mode)
File register (R)    *3    
*3
(ZR)        
Refresh device for modules (RD)        
Extended file register (ER*\R)        
Direct link Link input (J*\X)        
Link output (J*\Y)        
Link relay (J*\B)        
Link special relay (J*\SB)        
Link register (J*\W)        
Link special register        
(J*\SW)
Special direct buffer memory (U*\G)    *4    *5

*1 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.

*2 Q12DCCPU-V (Basic mode) cannot be accessed.
*3 Q00JCPU and Q00UJCPU cannot be accessed.
*4 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.
*5 Only FX3U(C)CPU can be accessed.

For own board access

The following devices are usable only for own board access.
Device Device Name Remarks
Link special relay (for CC-Link) SB Link special relay of own board
Link special register (for CC-Link) SW Link special register of own board
Remote input X RX
Remote output Y RY
Remote register (write area for CC-Link) WW RWw
Remote register (read area for CC-Link) WR RWr
Buffer memory ML Buffer memory of own station CC-Link module
Random access buffer MC Random access buffer in buffer memory of own station CC-Link module

10 ACCESSIBLE RANGES
304 10.6 For CC-Link Communication
Accessible ranges
This section indicates the accessible ranges for CC-Link communication.

Configuration
10
Connected station
Connected module Relayed module
CPU

Relayed network
CC-Link

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs and own board (CC-Link Ver.2 board) are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
RCPU CC IE TSN      
*3
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode), Q CC IE TSN     
motion CPU*1*4
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
10.6 For CC-Link Communication 305
 Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCPU (Q mode), Q CC IE TSN      
motion CPU*1*4 *2 *3 *2 *2
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU*5 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
QCCPU*5 CC IE TSN      
*2 *2 *2
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LCPU CC IE TSN      
CC IE Field      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Relayed station CPUs cannot be accessed via Q motion CPU.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode), QSCPU, and Q motion CPU relayed by CC-Link IE Field
Network cannot be accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*5 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.

10 ACCESSIBLE RANGES
306 10.6 For CC-Link Communication
10.7 For CC-Link G4 Communication
This section provides the accessible devices and accessible ranges for CC-Link G4 communication.

Accessible devices
10
The following table indicates the accessible devices for CC-Link G4 communication.

When access target is programmable controller CPU

Device (device name) Access target
RCPU RCCPU LHCPU QCPU QCCPU LCPU QSCPU FXCPU
(Q mode)
Function input (FX)        
Function output (FY)        
Function register (FD)        
Special relay (SM)        
Special register (SD)        
Input relay (X)        
Output relay (Y)        
Internal relay (M)        
Latch relay (L)        
Annunciator (F)        
Edge relay (V)        
Link relay (B)     *1   
Data register (D)        
Link register (W)     *1   
Timer (T) Contact (TS)        
Coil (TC)        
Present value (TN)        
Counter (C) Contact (CS)        
Coil (CC)        
Present value (CN)        
Retentive timer (ST) Contact (STS/SS)        
Coil (STC/SC)        
Present value (STN/SN)        
Long timer (LT) Contact (LTS)        
Coil (LTC)        
Present value (LTN)        
Long counter (LC) Contact (LCS)        
Coil (LCC)        
Present value (LCN)        
Long retentive timer Contact (LSTS/LSS)        
(LST)
Coil (LSTC/LSC)        
Present value (LSTN/LSN)        
Link special relay (SB)        
Link special register (SW)        
Step relay (S)        
Direct input (DX)        
Direct output (DY)        
Accumulator (A)        
Index register (Z)        
(V)        
Long index register (LZ)        

10 ACCESSIBLE RANGES
10.7 For CC-Link G4 Communication 307
 Device (device name) Access target
RCPU RCCPU LHCPU QCPU QCCPU LCPU QSCPU FXCPU
(Q mode)
File register (R)    *2    
*2
(ZR)        
Refresh device for modules (RD)        
Extended file register (ER*\R)        
Direct link Link input (J*\X)        
Link output (J*\Y)        
Link relay (J*\B)        
Link special relay (J*\SB)        
Link register (J*\W)        
Link special register        
(J*\SW)
Special direct buffer memory (U*\G)        

*1 Q12DCCPU-V (Basic mode) cannot be accessed.

*2 Q00JCPU and Q00UJCPU cannot be accessed.

When access target is Motion CPU

For accessible device list of Motion CPU, refer to the following section.
Page 269 When access target is Motion CPU

10 ACCESSIBLE RANGES
308 10.7 For CC-Link G4 Communication
Accessible ranges
This section indicates the accessible ranges for CC-Link G4 communication.

Configuration
10
Connected station CC-Link Relayed module
CPU module

CC-Link G4
Relayed network
module

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode), Q CC IE TSN     
motion CPU*1*5
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCPU (Q mode), Q CC IE TSN      
motion CPU*1*5
CC IE Control  *2 *3 *2 *2 
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU*4 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
10.7 For CC-Link G4 Communication 309
 Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCCPU*4 CC IE TSN      
*2 *3 *2 *2
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LCPU CC IE TSN      
CC IE Field      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Relayed station CPUs cannot be accessed via Q motion CPU.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode), QSCPU, and Q motion CPU relayed by CC-Link IE Field
Network cannot be accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

10 ACCESSIBLE RANGES
310 10.7 For CC-Link G4 Communication
10.8 For MELSECNET/H Communication
This section provides the accessible devices and accessible ranges for MELSECNET/H communication.

Accessible devices
10
The following table indicates the accessible devices for MELSECNET/H communication.

When access target is programmable controller CPU

Device (device name) Access target
RCPU RCCP LHCPU QCPU QCCPU LCPU QSCPU*1 FXCP
U (Q mode) U
Function input (FX)        
Function output (FY)        
Function register (FD)        
Special relay (SM)        
Special register (SD)        
Input relay (X)        
Output relay (Y)        
Internal relay (M)        
Latch relay (L)        
Annunciator (F)        
Edge relay (V)        
Link relay (B)     *2   
Data register (D)        
Link register (W)     *2   
Timer (T) Contact (TS)        
Coil (TC)        
Present value (TN)        
Counter (C) Contact (CS)        
Coil (CC)        
Present value (CN)        
Retentive timer (ST) Contact (STS/SS)        
Coil (STC/SC)        
Present value (STN/SN)        
Long timer (LT) Contact (LTS)        
Coil (LTC)        
Present value (LTN)        
Long counter (LC) Contact (LCS)        
Coil (LCC)        
Present value (LCN)        
Long retentive timer (LST) Contact (LSTS/LSS)        
Coil (LSTC/LSC)        
Present value (LSTN/LSN)        
Link special relay (SB)        
Link special register (SW)        
Step relay (S)        
Direct input (DX)        
Direct output (DY)        
Accumulator (A)        
Index register (Z)        
(V)        
Long index register (LZ)        

10 ACCESSIBLE RANGES
10.8 For MELSECNET/H Communication 311
 Device (device name) Access target
RCPU RCCP LHCPU QCPU QCCPU LCPU QSCPU*1 FXCP
U (Q mode) U
File register (R)    *3    
*3
(ZR)        
Refresh device for modules (RD)        
Extended file register (ER*\R)        
Direct link Link input (J*\X)        
Link output (J*\Y)        
Link relay (J*\B)        
Link special relay (J*\SB)        
Link register (J*\W)        
Link special register (J*\SW)        
Special direct buffer memory (U*\G)    *4    

*1 Writing to device data cannot be performed.

*2 Q12DCCPU-V (Basic mode) cannot be accessed.
*3 Q00JCPU and Q00UJCPU cannot be accessed.
*4 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.

For own board access

The following devices are usable only for own board access.
Device Device Name Remarks
Link relay B Link relay of own board
Link register W Link register of own board
Link special relay SB Link special relay of own board
Link special register SW Link special register of own board
Remote input X LX
Remote output Y LY

When access target is Motion CPU

For accessible device list of Motion CPU, refer to the following section.
Page 269 When access target is Motion CPU

10 ACCESSIBLE RANGES
312 10.8 For MELSECNET/H Communication
Accessible ranges
This section indicates the accessible ranges for MELSECNET/H communication.

Configuration
10
Connected station
Connected module Relayed module
CPU

MELSECNET/H Relayed network

Relayed station Relayed module

Personal computer
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs and own board (MELSECNET/H board) are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode), CC IE TSN     
QSCPU*1*6, Q motion
CC IE Control     
CPU*1*6 CC IE Field
MELSECNET/H*4     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
QCPU (Q mode), CC IE TSN      
QSCPU*1*6, Q motion
CC IE Control  *2 *3 *2  
CPU*1*6
CC IE Field
MELSECNET/H*4      
Ethernet      
Serial communication *5     
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU*7 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H*4     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
10.8 For MELSECNET/H Communication 313
 Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCCPU*7 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H*4      
Ethernet      
Serial communication      
CC-Link      

*1 Relayed station CPUs cannot be accessed via QSCPU or Q motion CPU.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and QSCPU relayed by CC-Link IE Field Network cannot
be accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 The modules can be accessed when the MELSECNET/H module of the connected station is in the MELSECNET/H mode.
*5 For redundant CPU, serial communication modules on the main base cannot be accessed.
*6 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*7 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.

10 ACCESSIBLE RANGES
314 10.8 For MELSECNET/H Communication
10.9 For CC-Link IE Controller Network Communication
This section provides the accessible devices and accessible ranges for CC-Link IE Controller Network communication.

Accessible devices
10
The following table indicates the accessible devices for CC-Link IE Controller Network communication.

When access target is programmable controller CPU

Device (device name) Access target
RCPU RCCPU LHCPU QCPU QCCP LCP QSCPU* FXCPU
1
(Q mode) U U
Function input (FX)        
Function output (FY)        
Function register (FD)        
Special relay (SM)        
Special register (SD)        
Input relay (X)        
Output relay (Y)        
Internal relay (M)        
Latch relay (L)        
Annunciator (F)        
Edge relay (V)        
Link relay (B)     *2   
Data register (D)        
Link register (W)     *2   
Timer (T) Contact (TS)        
Coil (TC)        
Present value (TN)        
Counter (C) Contact (CS)        
Coil (CC)        
Present value (CN)        
Retentive timer (ST) Contact (STS/SS)        
Coil (STC/SC)        
Present value (STN/SN)        
Long timer (LT) Contact (LTS)        
Coil (LTC)        
Present value (LTN)        
Long counter (LC) Contact (LCS)        
Coil (LCC)        
Present value (LCN)        
Long retentive timer (LST) Contact (LSTS/LSS)        
Coil (LSTC/LSC)        
Present value (LSTN/LSN)        
Link special relay (SB)        
Link special register (SW)        
Step relay (S)        
Direct input (DX)        
Direct output (DY)        
Accumulator (A)        
Index register (Z)        
(V)        
Long index register (LZ)        

10 ACCESSIBLE RANGES
10.9 For CC-Link IE Controller Network Communication 315
 Device (device name) Access target
RCPU RCCPU LHCPU QCPU QCCP LCP QSCPU* FXCPU
1
(Q mode) U U
File register (R)    *3    
*3
(ZR)        
Refresh device for modules (RD)        
Extended file register (ER*\R)        
Direct link Link input (J*\X)        
Link output (J*\Y)        
Link relay (J*\B)        
Link special relay (J*\SB)        
Link register (J*\W)        
Link special register (J*\SW)        
Special direct buffer memory (U*\G)    *4    

*1 Writing to device data cannot be performed.

*2 Q12DCCPU-V (Basic mode) cannot be accessed.
*3 Q00JCPU and Q00UJCPU cannot be accessed.
*4 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.

For own board access

The following devices are usable only for own board access.
Device Device Name Remarks
Link relay B Link relay of own board
Link register W Link register of own board
Link special relay SB Link special relay of own board
Link special register SW Link special register of own board
Remote input X LX
Remote output Y LY
Buffer memory ML Buffer memory of own board

When access target is Motion CPU

For accessible device list of Motion CPU, refer to the following section.
Page 269 When access target is Motion CPU

10 ACCESSIBLE RANGES
316 10.9 For CC-Link IE Controller Network Communication
Accessible ranges
This section indicates the accessible ranges for CC-Link IE Controller Network communication.

Configuration
10
Connected station
Connected module Relayed module
CPU

CC-Link IE Controller Relayed network

network

Relayed station Relayed module

Personal computer
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs and own board (CC-Link IE Controller Network board) are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication *8    
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU*6 FXCPU
mode)
RCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication *8  *8   
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode), CC IE TSN     
QSCPU*1*6, Q motion
CC IE Control     
CPU*1*6
CC IE Field
MELSECNET/H*4     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
10.9 For CC-Link IE Controller Network Communication 317
 Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCPU (Q mode), CC IE TSN      
QSCPU*1*6, Q motion *2 *3 *2
CC IE Control      
CPU*1*6
CC IE Field
MELSECNET/H*4      
Ethernet      
Serial communication *5     
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU*7 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H*4     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
QCCPU*7 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H*4      
Ethernet      
Serial communication      
CC-Link      

*1 Relayed station CPUs cannot be accessed via QSCPU or Q motion CPU.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and QSCPU relayed by CC-Link IE Field Network cannot
be accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 The modules can be accessed when the MELSECNET/H module of the connected station is in the MELSECNET/H mode.
*5 For redundant CPU, serial communication modules on the main base cannot be accessed.
*6 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*7 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.
*8 For redundant CPU, serial communication modules on the main base cannot be accessed because the multi-drop connection cannot be
performed.

10 ACCESSIBLE RANGES
318 10.9 For CC-Link IE Controller Network Communication
Accessible ranges (for transferring logging files)
This section indicates the accessible ranges for transferring logging files in CC-Link IE Controller Network communication.

Configuration
10
Connected station
Connected module
CPU

CC-Link IE Controller
network

Personal computer

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs described in this section are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
RnCPU, RnENCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
RnCPU, RnENCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

10 ACCESSIBLE RANGES
10.9 For CC-Link IE Controller Network Communication 319
 10.10 For CC-Link IE Field Network Communication
This section provides the accessible devices and accessible ranges for CC-Link IE Field Network communication.

Accessible devices
The following table indicates the accessible devices for CC-Link IE Field Network communication.

When access target is programmable controller CPU

Device (device name) Access target
RCPU RCCPU LHCPU QCPU (Q QCCPU LCP QSCPU* FXCPU
1
mode) U
Function input (FX)        
Function output (FY)        
Function register (FD)        
Special relay (SM)        
Special register (SD)        
Input relay (X)        
Output relay (Y)        
Internal relay (M)        
Latch relay (L)        
Annunciator (F)        
Edge relay (V)        
Link relay (B)     *2   
Data register (D)        
Link register (W)     *2   
Timer (T) Contact (TS)        
Coil (TC)        
Present value (TN)        
Counter (C) Contact (CS)        
Coil (CC)        
Present value (CN)        
Retentive timer (ST) Contact (STS/SS)        
Coil (STC/SC)        
Present value (STN/SN)        
Long timer (LT) Contact (LTS)        
Coil (LTC)        
Present value (LTN)        
Long counter (LC) Contact (LCS)        
Coil (LCC)        
Present value (LCN)        
Long retentive timer (LST) Contact (LSTS/LSS)        
Coil (LSTC/LSC)        
Present value (LSTN/LSN)        
Link special relay (SB)        
Link special register (SW)        
Step relay (S)        
Direct input (DX)        
Direct output (DY)        
Accumulator (A)        
Index register (Z)        
(V)        
Long index register (LZ)        

10 ACCESSIBLE RANGES
320 10.10 For CC-Link IE Field Network Communication
 Device (device name) Access target
RCPU RCCPU LHCPU QCPU (Q QCCPU LCP QSCPU* FXCPU
1
mode) U
File register (R)    *3    
*3
(ZR)        
Refresh device for modules (RD)
Extended file register (ER*\R)
















10
Direct link Link input (J*\X)        
Link output (J*\Y)        
Link relay (J*\B)        
Link special relay (J*\SB)        
Link register (J*\W)        
Link special register (J*\SW)        
Special direct buffer memory (U*\G)    *4    

*1 Writing to device data cannot be performed.

*2 Q12DCCPU-V (Basic mode) cannot be accessed.
*3 Q00JCPU and Q00UJCPU cannot be accessed.
*4 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.

For own board access

The following devices are usable only for own board access.
Device Device Remarks
Name
Remote register W W0000 to W1FFF = RWw0 to RWw1FFF Remote register of own board for sending
W2000 to W3FFF = RWr0 to RWr1FFF Remote register of own board for receiving
Link special relay SB Link special relay of own board
Link special register SW Link special register of own board
Remote input X RX
Remote output Y RY
Buffer memory ML Buffer memory of own board

When access target is Motion CPU

For accessible device list of Motion CPU, refer to the following section.
Page 269 When access target is Motion CPU

10 ACCESSIBLE RANGES
10.10 For CC-Link IE Field Network Communication 321
 Accessible ranges
This section indicates the accessible ranges for CC-Link IE Field Network communication.

Configuration

Connected station
Connected module Relayed module
CPU

CC-Link IE Field Relayed network

network

Relayed station Relayed module

Personal computer
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs and own board (CC-Link IE Field Network board) are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication *3    
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
RCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication *3  *3   
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
322 10.10 For CC-Link IE Field Network Communication
Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCPU (Q mode) CC IE TSN      
*1 *2
CC IE Control      
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LCPU CC IE TSN      
CC IE Field      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed because the multi-drop connection cannot be
performed.

10 ACCESSIBLE RANGES
10.10 For CC-Link IE Field Network Communication 323
 10.11 For Q Series Bus Communication
This section provides the accessible devices and accessible ranges for Q series bus communication.

Accessible devices
The following table indicates the accessible devices for Q series bus communication.
Device (device name) Access target
Q02(H), Q06H, Q12H, Q25H, Q02PH, Q06PH, Q12PH, Q25PH
Function input (FX) 
Function output (FY) 
Function register (FD) 
Special relay (SM) 
Special register (SD) 
Input relay (X) 
Output relay (Y) 
Internal relay (M) 
Latch relay (L) 
Annunciator (F) 
Edge relay (V) 
Link relay (B) 
Data register (D) 
Link register (W) 
Timer (T) Contact (TS) 
Coil (TC) 
Present value (TN) 
Counter (C) Contact (CS) 
Coil (CC) 
Present value (CN) 
Retentive timer (ST) Contact (STS) 
Coil (STC) 
Present value (STN) 
Link special relay (SB) 
Link special register (SW) 
Step relay (S) 
Direct input (DX) 
Direct output (DY) 
Accumulator (A) 
Index register (Z) 
(V) 
File register (R) 
(ZR) 
Extended file register (ER*\R) 
Direct link Link input (J*\X) 
Link output (J*\Y) 
Link relay (J*\B) 
Link special relay (J*\SB) 
Link register (J*\W) 
Link special register (J*\SW) 
Special direct buffer memory (U*\G) *1

*1 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.

10 ACCESSIBLE RANGES
324 10.11 For Q Series Bus Communication
Accessible ranges
This section indicates the accessible ranges for Q series bus communication.

Accessible ranges
■Another CPU on the same base can be accessed. 10
However, another CPU cannot be accessed via the network of another CPU.

■Another CPU can be accessed via the MELSECNET/H module controlled by the PC CPU
module.
In this case, the accessible ranges are the same as in MELSECNET/H communication. (Page 313 Accessible ranges)
The personal computer used for MELSECNET/H communication corresponds to the PC CPU module, and the MELSECNET/
H board to the MELSECNET/H module.

■Another CPU can be accessed via the CC-Link module controlled by the PC CPU module.
In this case, the accessible ranges are as in CC-Link communication. (Page 305 Accessible ranges)
The personal computer used for CC-Link communication corresponds to the PC CPU module, and the CC-Link Ver.2 board to
the CC-Link module.

10 ACCESSIBLE RANGES
10.11 For Q Series Bus Communication 325
 10.12 For Modem Communication
This section explains the accessible devices and accessible ranges for modem communication.

Accessible devices
The following table indicates the accessible devices for modem communication.
Device (device name) Access target
RCPU RCCPU LHCPU QCPU QCCPU LCPU QSCPU FXCPU
(Q mode)
Function input (FX)        
Function output (FY)        
Function register (FD)        
Special relay (SM)        
Special register (SD)        
Input relay (X)        *1
Output relay (Y)        *1
Internal relay (M)        *1
Latch relay (L)        
Annunciator (F)        
Edge relay (V)        
*2
Link relay (B)        
Data register (D)        *1
Link register (W)     *2   
Timer (T) Contact (TS)        *1
Coil (TC)        *1
Present value (TN)        *1
Counter (C) Contact (CS)        *1
Coil (CC)        *1
Present value (CN)        *1
Retentive timer (ST) Contact (STS/SS)        
Coil (STC/SC)        
Present value (STN/SN)        
Long timer (LT) Contact (LTS)        
Coil (LTC)        
Present value (LTN)        
Long counter (LC) Contact (LCS)        
Coil (LCC)        
Present value (LCN)        
Long retentive timer Contact (LSTS/LSS)        
(LST)
Coil (LSTC/LSC)        
Present value (LSTN/LSN)        
Link special relay (SB)        
Link special register (SW)        
Step relay (S)        *1
Direct input (DX)        
Direct output (DY)        
Accumulator (A)        
Index register (Z)        *1
(V)        *1
Long index register (LZ)        
File register (R)    *3    *4
(ZR)    *3    

10 ACCESSIBLE RANGES
326 10.12 For Modem Communication
Device (device name) Access target
RCPU RCCPU LHCPU QCPU QCCPU LCPU QSCPU FXCPU
(Q mode)
Refresh device for modules (RD)        
Extended file register (ER*\R)        
Direct link Link input (J*\X)
Link output (J*\Y)
















10
Link relay (J*\B)        
Link special relay (J*\SB)        
Link register (J*\W)        
Link special register        
(J*\SW)
Special direct buffer memory (U*\G)    *5    *6

*1 FX0CPU, FX0SCPU, FX0NCPU, FX1CPU, FXUCPU, and FX2CCPU cannot be accessed.

*2 Q12DCCPU-V (Basic mode) cannot be accessed.
*3 Q00JCPU and Q00UJCPU cannot be accessed.
*4 When specifying a file register in FX series CPU other than FX3G(C)CPU and FX3U(C)CPU, specify the data register (D). The extended
register (R) can be specified only in FX3G(C)CPU or FX3U(C)CPU.
*5 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.
*6 Only FX3U(C)CPU can be accessed.

10 ACCESSIBLE RANGES
10.12 For Modem Communication 327
 Accessible ranges (When using Q series-compatible C24 and L
series-compatible C24)
This section indicates the accessible ranges for Modem communication.

Configuration

Connected station Connected module Relayed module

CPU

Subscrib
Modem er's line Modem Relayed network

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Connected Relayed network Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode) Q series-compatible CC IE TSN     
C24
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*4

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
QCPU (Q mode) Q series-compatible CC IE TSN      
C24
CC IE Control  *1 *2 *1  
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication *3     
CC-Link      
*3
Multi-drop connection      
(Independent mode)*4

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU L series-compatible CC IE TSN     
C24
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*4

10 ACCESSIBLE RANGES
328 10.12 For Modem Communication
Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
LCPU L series-compatible CC IE TSN      
C24 *1
CC IE Field      
MELSECNET/H
Ethernet












10
Serial communication *3     
CC-Link      
*3
Multi-drop connection      
(Independent mode)*4

*1 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and QSCPU relayed by CC-Link IE Field Network cannot
be accessed.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.
*4 Indicates the CH2 side setting. (The CH1 side is fixed to the independent mode.)

10 ACCESSIBLE RANGES
10.12 For Modem Communication 329
 Accessible ranges (When using FXCPU)

Configuration

Connected station Relayed module

CPU

Subscrib
Modem er's line Modem Relayed network

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed Network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FXCPU*1 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 FX0CPU, FX0SCPU, FX0NCPU, FX1CPU, FXUCPU, and FX2CCPU cannot be accessed.

10 ACCESSIBLE RANGES
330 10.12 For Modem Communication
10.13 For Gateway Function Communication
This section describes the accessible devices and accessible ranges for gateway function communication.

Accessible devices
10
This section indicates the accessible devices for gateway function communication.
Only the following device is accessible for gateway function communication.
Device: Gateway device
Device name: EG

Accessible ranges
This section indicates the accessible ranges for gateway function communication.

Configuration

Programmable
controller CPU

GOT
Ethernet

Personal computer

Accessible ranges
Only the connected GOT can be accessed.

10 ACCESSIBLE RANGES
10.13 For Gateway Function Communication 331
 10.14 For GX Simulator Communication
This section describes the accessible devices and accessible ranges for GX Simulator communication.

Accessible devices
The accessible devices of other station during GX Simulator communication depends on the other station device settings set
on the device manager of GX Simulator.
For other station device setting, refer to the following manual.
GX Simulator Version 7 Operating Manual

Accessible ranges
The following table indicates the accessible ranges for GX Simulator communication.
Whether the target CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Target Target CPU
Station RCPU RCCPU R motion LHCPU FX5CP QCPU QCCPU LCPU QSCP Q motion FXCPU
CPU U (Q mode) U CPU
Host station           
Other station           

10 ACCESSIBLE RANGES
332 10.14 For GX Simulator Communication
10.15 For GX Simulator2 Communication
This section describes the accessible devices and accessible ranges for GX Simulator2 communication.

Accessible devices
10
The accessible devices during GX Simulator2 communication depend on the device supported by GX Simulator2.
For details, refer to the following manual.
GX Works2 Version 1 Operating Manual (Common)

Accessible ranges
The following table indicates the accessible ranges for GX Simulator2 communication.
Whether the target CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Target Target CPU
Station RCPU RCCP R motion LHCPU FX5CP QCPU QCCP LCPU QSCP Q motion FXCPU
U CPU U (Q mode) U U CPU
Other           
station

10 ACCESSIBLE RANGES
10.15 For GX Simulator2 Communication 333
 10.16 For GX Simulator3 Communication
This section describes the accessible devices and accessible ranges for GX Simulator3 communication.

Accessible devices
The accessible devices during GX Simulator3 communication depend on the device supported by GX Simulator3.
For details, refer to the following manual.
GX Works3 Operating Manual

Accessible ranges
The following table indicates the accessible ranges for GX Simulator3 communication.
Whether the target CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Target Target CPU
Station RCPU RCCPU R motion LHCPU FX5CPU QCPU QCCPU LCPU QSCP Q motion FXCP
CPU (Q mode) U CPU U
Other *1    *1      
station

*1 The supported CPU types are as follows.

Target CPU CPU type

RCPU R00, R01, R02, R04, R04EN, R08, R08EN, R08P, R08PSF, R08SF, R16, R16EN, R16P, R16PSF, R16SF, R32, R32EN, R32P, R32PSF,
R32SF, R120, R120EN, R120P, R120PSF, R120SF
FX5CPU FX5U, FX5UJ

10 ACCESSIBLE RANGES
334 10.16 For GX Simulator3 Communication
10.17 For MT Simulator2 Communication
This section describes the accessible devices and accessible ranges for MT Simulator2 communication.

Accessible devices
10
The accessible devices during MT Simulator2 communication depend on the device supported by MT Simulator2.
For accessible device list of Q motion CPU, refer to the following section.
Page 269 When access target is Motion CPU

Accessible ranges
The following table indicates the accessible ranges for MT Simulator2 communication.
Whether the target CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Target Target CPU
Station RCPU RCCPU R motion LHCPU FX5CP QCPU QCCPU LCPU QSCP Q motion FXCP
CPU U (Q mode) U CPU U
Other           
station

10 ACCESSIBLE RANGES
10.17 For MT Simulator2 Communication 335
 10.18 For GOT Transparent Communication
This section provides the accessible devices and accessible ranges for GOT transparent communication.

Accessible devices
The following table indicates the accessible devices for GOT transparent communication.

When access target is programmable controller CPU

Device (device name) Access target
RCPU RCCP LHCPU FX5CP QCPU QCCPU LCPU QSCP FXCPU
U U (Q mode) U
Function input (FX)         
Function output (FY)         
Function register (FD)         
Special relay (SM)         
Special register (SD)         
Input relay (X)         
Output relay (Y)         
Internal relay (M)         
Latch relay (L)         
Annunciator (F)         
Edge relay (V)         
Link relay (B)      *1   
Data register (D)         
Link register (W)      *1   
Timer (T) Contact (TS)         
Coil (TC)         
Present value (TN)         
Counter (C) Contact (CS)         
Coil (CC)         
Present value (CN)         
Retentive timer (ST) Contact (STS/SS)         
Coil (STC/SC)         
Present value (STN/SN)         
Long timer (LT) Contact (LTS)         
Coil (LTC)         
Present value (LTN)         
Long counter (LC) Contact (LCS)         
Coil (LCC)         
Present value (LCN)         
Long retentive timer Contact (LSTS/LSS)         
(LST)
Coil (LSTC/LSC)         
Present value (LSTN/         
LSN)
Link special relay (SB)         
Link special register (SW)         
Step relay (S)         
Direct input (DX)         
Direct output (DY)         
Accumulator (A)         
Index register (Z)         
(V)         
Long index register (LZ)         

10 ACCESSIBLE RANGES
336 10.18 For GOT Transparent Communication
 Device (device name) Access target
RCPU RCCP LHCPU FX5CP QCPU QCCPU LCPU QSCP FXCPU
U U (Q mode) U
File register (R)     *2    *3
*2
(ZR)         
Refresh device for modules (RD)
Extended file register (ER*\R)


















10
Direct link Link input (J*\X)         
Link output (J*\Y)         
Link relay (J*\B)         
Link special relay (J*\SB)         
Link register (J*\W)         
Link special register         
(J*\SW)
Special direct buffer memory (U*\G)     *4    *5

*1 Q12DCCPU-V (Basic mode) cannot be accessed.

*2 Q00JCPU and Q00UJCPU cannot be accessed.
*3 When specifying a file register in FX series CPU other than FX3G(C)CPU and FX3U(C)CPU, specify the data register (D). The extended
register (R) can be specified only in FX3G(C)CPU or FX3U(C)CPU.
*4 In a multi-CPU configuration, reading from the shared memory of the host CPU cannot be performed.
Writing to the shared memory cannot be performed regardless of the host or other CPU.
*5 Only FX3U(C)CPU can be accessed.

When access target is Motion CPU

For accessible device list of Motion CPU, refer to the following section.
Page 269 When access target is Motion CPU

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 337
 Accessible ranges (Personal computer side port: Serial,
GOT1000 side port: Serial, CPU side port: Direct connection)
This section indicates the accessible ranges for GOT transparent communication.

For usable system configuration, refer to GOT series connection manual.

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Serial Serial

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Relayed network Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FX5CPU CC IE TSN     
CC IE Control     *7
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
FX5CPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Relayed network Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
QCPU (Q mode) , Q CC IE TSN     
motion CPU*2,
CC IE Control     
QCCPU*5
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
338 10.18 For GOT Transparent Communication
Connected Relayed network Relayed station CPU
station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
QCPU (Q mode)*1, Q CC IE TSN      
motion CPU*2, *3 *4 *3
CC IE Control      
QCCPU*5
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

Connected Relayed network Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
LCPU CC IE TSN      
CC IE Field  *3    
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Relayed network Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
FXCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      *6

*1 Redundant CPU cannot be accessed.

*2 Relayed station CPUs cannot be accessed via Q motion CPU.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE Field Network
cannot be accessed.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*6 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.
*7 Only CC-Link IE Field Network can be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 339
 Accessible ranges (Personal computer side port: USB, GOT2000/
1000 side port: USB, CPU side port: Direct connection)

Configuration

Connected station Relayed module

CPU

GOT Relayed network

USB Serial

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Relayed network Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FX5CPU CC IE TSN     
CC IE Control     *7
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
FX5CPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Relayed network Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
QCPU (Q mode) , Q CC IE TSN     
motion CPU*4*6,
CC IE Control     
QCCPU*6 CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
340 10.18 For GOT Transparent Communication
Connected Relayed network Relayed station CPU
station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
QCPU (Q mode)*1, Q CC IE TSN      
motion CPU*4*6, *2 *3 *2
CC IE Control      
QCCPU*6
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

Connected Relayed network Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
LCPU CC IE TSN      
CC IE Field  *2    
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Relayed network Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
FXCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      *5

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE Field Network
cannot be accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Relayed station CPUs cannot be accessed via Q motion CPU.
*5 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.
*6 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*7 Only CC-Link IE Field Network can be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 341
 Accessible ranges (Personal computer side port: Serial,
GOT1000 side port: Serial, CPU side port: Bus connection)

Configuration

Connected Relayed module

station CPU

GOT Relayed network

Serial Bus

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Relayed network Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode)*1, Q CC IE TSN     
motion CPU*2*5
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
QCPU (Q mode)*1, Q CC IE TSN      
motion CPU*2*5 *3 *4 *3
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Relayed network Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU*6 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
342 10.18 For GOT Transparent Communication
Connected Relayed network Relayed station CPU
station CPU QCPU (Q mode)*1 QCCPU LCPU QSCPU Q motion CPU FXCPU
*6
QCCPU CC IE TSN      
CC IE Control  *3 *4  *3 
CC IE Field
MELSECNET/H      
Ethernet      
10
Serial communication      
CC-Link      

*1 Redundant CPU cannot be accessed.

*2 Relayed station CPUs cannot be accessed via Q motion CPU.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE Field Network
cannot be accessed.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*6 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 343
 Accessible ranges (Personal computer side port: USB, GOT2000/
1000 side port: USB, CPU side port: Bus connection)

Configuration

Connected Relayed module

station CPU

GOT Relayed network

USB Bus

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Relayed network Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode)*1, Q CC IE TSN     
motion CPU*4*5
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
QCPU (Q mode)*1, Q CC IE TSN      
motion CPU*4*5
CC IE Control  *2 *3  *2 
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Relayed network Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
344 10.18 For GOT Transparent Communication
Connected Relayed network Relayed station CPU
station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
QCCPU CC IE TSN      
*2 *3
CC IE Control      
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE Field Network
cannot be accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Relayed station CPUs cannot be accessed via Q motion CPU.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 345
 Accessible ranges (Personal computer side port: Serial,
GOT1000 side port: Serial, CPU side port: Serial communication
module)

Configuration

Connected station Relayed module

Connected module
CPU

GOT Relayed network

Serial

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Connected Relayed network Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU R series-compatible CC IE TSN     
C24
CC IE Control *4    
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*5

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
RCPU R series-compatible CC IE TSN      
C24 *4
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)*5

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCCPU*7 R series-compatible CC IE TSN     
C24 CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*5

10 ACCESSIBLE RANGES
346 10.18 For GOT Transparent Communication
Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
RCCPU*7 R series-compatible CC IE TSN      
C24
CC IE Control      
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)*5

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
R motion R series-compatible CC IE TSN     
CPU*6*7 C24
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*5

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
R motion R series-compatible CC IE TSN      
CPU*6*7 C24
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)*5

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q Q series-compatible CC IE TSN     
mode)*1, Q C24
CC IE Control     
motion CPU*2*7 CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*5

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 347
 Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
QCPU (Q Q series-compatible CC IE TSN      
mode)*1, Q C24 *3 *4 *3
CC IE Control      
motion CPU*2*7
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)*5

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU L series-compatible CC IE TSN     
C24
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*5

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
LCPU L series-compatible CC IE TSN      
C24 *3
CC IE Field      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)*5

*1 Redundant CPU cannot be accessed.

*2 Relayed station CPUs cannot be accessed via Q motion CPU.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE Field Network
cannot be accessed.
*4 Since CC-Link IE Controller Network is not supported, RCPU and LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Indicates the CH2 side setting. (The CH1 side is fixed to the independent mode.)
*6 Relayed station CPUs cannot be accessed via R motion CPU.
*7 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

10 ACCESSIBLE RANGES
348 10.18 For GOT Transparent Communication
Accessible ranges (Personal computer side port: USB, GOT2000/
1000 side port: USB, CPU side port: Serial communication
module)

Configuration 10

Connected station Relayed module

Connected module
CPU

GOT Relayed network

USB

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Connected Relayed network Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU R series-compatible CC IE TSN     
C24
CC IE Control *3    
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*4

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
RCPU R series-compatible CC IE TSN      
C24
CC IE Control   *3   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)*4

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCCPU*7 R series-compatible CC IE TSN     
C24
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*4

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 349
 Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
RCCPU*7 R series-compatible CC IE TSN      
C24
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)*4

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
R motion R series-compatible CC IE TSN     
CPU*5*7 C24
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*4

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
R motion R series-compatible CC IE TSN      
CPU*5*7 C24
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)*4

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q Q series-compatible CC IE TSN     
mode)*1, Q C24
CC IE Control     
motion CPU*6*7 CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*4

10 ACCESSIBLE RANGES
350 10.18 For GOT Transparent Communication
Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
QCPU (Q Q series-compatible CC IE TSN      
mode)*1, Q C24 *2 *3 *2
CC IE Control      
motion CPU*6*7
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)*4

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU L series-compatible CC IE TSN     
C24
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)*4

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
LCPU L series-compatible CC IE TSN      
C24 *2
CC IE Field      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)*4

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE Field Network
cannot be accessed.
*3 Since CC-Link IE Controller Network is not supported, RCPU and LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Indicates the CH2 side setting. (The CH1 side is fixed to the independent mode.)
*5 Relayed station CPUs cannot be accessed via R motion CPU.
*6 Relayed station CPUs cannot be accessed via Q motion CPU.
*7 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 351
 Accessible ranges (Personal computer side port: Serial,
GOT1000 side port: Serial, CPU side port: Ethernet module)

Configuration

Connected station Relayed module

Connected module
CPU

GOT Relayed network

Serial Ethernet

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Connected Relayed network Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU R series-compatible CC IE TSN     
E71*2
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
RCPU R series-compatible CC IE TSN      
E71*2
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCCPU*5 R series-compatible CC IE TSN     
E71*2
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
352 10.18 For GOT Transparent Communication
Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
RCCPU*5 R series-compatible CC IE TSN      
E71*2
CC IE Control      
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode)*1 Q series-compatible CC IE TSN     
E71*2
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
QCPU (Q mode)*1 Q series-compatible CC IE TSN      
E71*2 *3 *4
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU*1 L series-compatible CC IE TSN     
E71*2
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
LCPU*1 L series-compatible CC IE TSN      
E71*2
CC IE Control  *3 *4   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication *6 *6 *6   
CC-Link      

*1 Redundant CPU cannot be accessed.

*2 The communication cannot be established when a remote password is set to the connected station side R series-compatible E71, Q
series-compatible E71 and L series-compatible E71.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 353
 *6 For redundant CPU, serial communication modules on the main base cannot be accessed because the multi-drop connection cannot be
performed.

10 ACCESSIBLE RANGES
354 10.18 For GOT Transparent Communication
Accessible ranges (Personal computer side port: USB, GOT2000/
1000 side port: USB, CPU side port: Ethernet module)

Configuration
10
Connected station Relayed module
Connected module
CPU

GOT Relayed network

USB Ethernet

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Connected Relayed network Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU R series-compatible CC IE TSN     
E71*2
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
RCPU R series-compatible CC IE TSN      
E71*2
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCCPU*5 R series-compatible CC IE TSN     
E71*2
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 355
 Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
RCCPU*5 R series-compatible CC IE TSN      
E71*2
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q Q series-compatible CC IE TSN     
mode)*1, E71*2
CC IE Control     
QCCPU*5 CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
QCPU (Q Q series-compatible CC IE TSN      
mode)*1, E71*2 *3 *4
CC IE Control      
QCCPU*5
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU*1 L series-compatible CC IE TSN     
E71*2
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCP LCPU QSCP Q motion FXCP
mode) U U CPU U
LCPU*1 L series-compatible CC IE TSN      
E71*2
CC IE Control  *3 *4   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication *6 *6 *6   
CC-Link      

10 ACCESSIBLE RANGES
356 10.18 For GOT Transparent Communication
*1 Redundant CPU cannot be accessed.
*2 The communication cannot be established when a remote password is set to the connected station side R series-compatible E71, Q
series-compatible E71 and L series-compatible E71.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*6 For redundant CPU, serial communication modules on the main base cannot be accessed because the multi-drop connection cannot be 10
performed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 357
 Accessible ranges (Personal computer side port: Serial,
GOT1000 side port: Serial, CPU side port: Ethernet port)

Configuration

Connected station Relayed module

Connected module
CPU

GOT Relayed network

Serial Ethernet

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station CPU Relayed network Relayed station CPU
RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU, R motion CPU*5*7 CC IE TSN     
*4
CC IE Control     *8
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q mode)*2 QCCPU LCPU QSCPU Q motion CPU FXCP
U
RCPU, R motion CPU*5*7 CC IE TSN      
CC IE Control   *4   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

RCPU RCCPU R motion CPU LHCPU FX5CPU
RCCPU*5 CC IE TSN     
CC IE Control *4    
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
358 10.18 For GOT Transparent Communication
Connected station CPU Relayed network Relayed station CPU
QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*2
RCCPU*5 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

RCPU RCCPU R motion CPU LHCPU FX5CPU
FX5CPU CC IE TSN     
CC IE Control     *9
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q QCCP LCPU QSCPU Q motion CPU FXCPU
mode)*2 U
FX5CPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

RCPU RCCPU R motion CPU LHCPU FX5CPU
QnUDE(H)CPU*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q mode)*2 QCCP LCPU QSCPU Q motion CPU FXCPU
U
QnUDE(H)CPU*1 CC IE TSN      
CC IE Control  *3 *4   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 359
 Connected station CPU Relayed network Relayed station CPU
RCPU RCCPU R motion CPU LHCPU FX5CPU
*6
QCCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*2
QCCPU*6 CC IE TSN      
*3 *4
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU*1 CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q mode)*2 QCCP LCPU QSCPU Q motion CPU FXCPU
U
LCPU*1 CC IE TSN      
CC IE Field  *3    
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 The communication cannot be established when a remote password is set to the connected station CPU.
*2 Redundant CPU cannot be accessed.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*4 Since CC-Link IE Controller Network is not supported, RCPU and LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*6 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.
*7 Relayed station CPUs cannot be accessed via R motion CPU.
*8 Only CC-Link IE Field Network on which connected station CPU is RCPU can be accessed.
*9 Only CC-Link IE Field Network can be accessed.

10 ACCESSIBLE RANGES
360 10.18 For GOT Transparent Communication
Accessible ranges (Personal computer side port: USB, GOT2000/
1000 side port: USB, CPU side port: Ethernet port)

Configuration
10
Connected station Relayed module
CPU

GOT Relayed network

USB Ethernet

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station CPU Relayed network Relayed station CPU
RCPU RCCPU R motion CPU LHCPU FX5CPU
*5*6
RCPU, R motion CPU CC IE TSN     
CC IE Control *4    *7
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*2
RCPU, R motion CPU*5*6 CC IE TSN      
*4
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

RCPU RCCPU R motion CPU LHCPU FX5CPU
RCCPU*6 CC IE TSN     
*4
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 361
 Connected station CPU Relayed network Relayed station CPU
QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*2
RCCPU*6 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

RCPU RCCPU R motion CPU LHCPU FX5CPU
FX5CPU CC IE TSN     
CC IE Control     *8
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*2
FX5CPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

RCPU RCCPU R motion CPU LHCPU FX5CPU
QnUDE(H)CPU*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q mode)*2 QCCPU LCPU QSCPU Q motion CPU FXCPU
QnUDE(H)CPU*1 CC IE TSN      
CC IE Control  *3 *4   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

10 ACCESSIBLE RANGES
362 10.18 For GOT Transparent Communication
Connected station CPU Relayed network Relayed station CPU
RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
QCCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
10
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*2
QCCPU*1 CC IE TSN      
*3 *4
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU*1 CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*2
LCPU*1 CC IE TSN      
CC IE Field  *3    
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 The communication cannot be established when a remote password is set to the connected station CPU.
*2 Redundant CPU cannot be accessed.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*4 Since CC-Link IE Controller Network is not supported, RCPU and LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Relayed station CPUs cannot be accessed via R motion CPU.
*6 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*7 Only CC-Link IE Field Network on which connected station CPU is RCPU can be accessed.
*8 Only CC-Link IE Field Network can be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 363
 Accessible ranges (Personal computer side port: Serial,
GOT1000 side port: Serial, CPU side port: Ethernet adapter
module)

Configuration

Connected station CC-Link IE Field Relayed module

CPU Network module

Ethernet Adapter
GOT Relayed network
module

Serial Ethernet
Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QnUDE(H)CPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
QnUDE(H)CPU CC IE TSN      
CC IE Control  *2 *3   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
364 10.18 For GOT Transparent Communication
Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
LCPU CC IE TSN      
*2
CC IE Field      
MELSECNET/H
Ethernet












10
Serial communication      
CC-Link      

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 365
 Accessible ranges (Personal computer side port :USB, GOT2000/
1000 side port: USB, CPU side port: Ethernet adapter module)

Configuration

Connected station CC-Link IE Field Relayed module

CPU Network module

Ethernet Adapter
GOT Relayed network
module

USB Ethernet Relayed station

Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QnUDE(H)CPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
QnUDE(H)CPU CC IE TSN      
CC IE Control  *2 *3   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
366 10.18 For GOT Transparent Communication
Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
LCPU CC IE TSN      
*2
CC IE Field      
MELSECNET/H
Ethernet












10
Serial communication      
CC-Link      

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 367
 Accessible ranges (Personal computer side port: Serial,
GOT1000 side port: Serial, CPU side port: Ethernet adapter/
module)

Configuration
Ethernet adapter: FX3U-ENET-ADP

Ethernet adapter Connected station Relayed module

CPU

GOT Relayed network

Serial Ethernet

Relayed station
Personal computer Relayed module
CPU

Ethernet module: FX3U-ENET(-L)

Ethernet module Connected station Relayed module

CPU

GOT Relayed network

Serial Ethernet

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
FXCPU*1 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Only FX3SCPU (FX3U-ENET-ADP), FX3G(C)CPU, and FX3U(C)CPU can be accessed.

10 ACCESSIBLE RANGES
368 10.18 For GOT Transparent Communication
Accessible ranges (Personal computer side port: USB, GOT2000/
1000 side port: USB, CPU side port: Ethernet adapter/module)

Configuration
Ethernet adapter: FX3U-ENET-ADP 10

Ethernet adapter Connected station Relayed module

CPU

GOT Relayed network

USB Ethernet

Relayed station
Personal computer Relayed module
CPU

Ethernet module: FX3U-ENET(-L)

Ethernet module Connected station Relayed module

CPU

GOT Relayed network

USB Ethernet

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
FXCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FXCPU*1 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Only FX3SCPU (FX3U-ENET-ADP), FX3G(C)CPU, and FX3U(C)CPU can be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 369
 Accessible ranges (Personal computer side port: Ethernet board,
GOT2000/1000 side port: Ethernet port, CPU side port: Serial)

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Ethernet Serial

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FX5CPU CC IE TSN     
CC IE Control     *5
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q mode)*1 QCCPU LCPU QSCPU Q motion CPU FXCPU
FX5CPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode)*1, QCCPU*4 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
370 10.18 For GOT Transparent Communication
Connected station CPU Relayed network Relayed station CPU
QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCP
mode)*1 U
QCPU (Q mode)*1, QCCPU*4 CC IE TSN      
*2 *3
CC IE Control      
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
LCPU CC IE TSN      
CC IE Field  *2    
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
FXCPU CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 For Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS, only CPU No.2 or later in a multiple CPU configuration
can be accessed.
*5 Only CC-Link IE Field Network can be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 371
 Accessible ranges (Personal computer side port: Ethernet board,
GOT2000/1000 side port: Ethernet port, CPU side port: Serial
communication module)

Configuration

Connected station Connected module Relayed module

CPU

GOT Relayed network

Ethernet Serial

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Connected Relayed network Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU, R motion R series-compatible CC IE TSN     
CPU*4*5 C24
CC IE Control *3    
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
RCPU, R motion R series-compatible CC IE TSN      
CPU*4*5 C24 CC IE Control   *3   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
QCPU (Q mode) , Q series-compatible CC IE TSN     
QCCPU C24
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
372 10.18 For GOT Transparent Communication
Connected Connected Relayed network Relayed station CPU
station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
QCPU (Q Q series-compatible CC IE TSN      
mode)*1, QCCPU C24
CC IE Control   *2
 *3
  
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

Connected Connected Relayed network Relayed station CPU

station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU L series-compatible CC IE TSN     
C24
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
LCPU L series-compatible CC IE TSN      
C24
CC IE Field  *2    
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, RCPU and LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Relayed station CPUs cannot be accessed via R motion CPU.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 373
 Accessible ranges (Personal computer side port: Ethernet board,
GOT2000/1000 side port: Ethernet port, CPU side port: Bus
connection)

Configuration

Connected Relayed module

station CPU

GOT Relayed network

Ethernet Bus

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
QCPU (Q mode)*1 CC IE TSN      
CC IE Control  *2 *3   
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

Connected station Relayed network Relayed station CPU

CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

10 ACCESSIBLE RANGES
374 10.18 For GOT Transparent Communication
Connected station Relayed network Relayed station CPU
CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
QCCPU CC IE TSN      
*2 *3
CC IE Control      
CC IE Field
MELSECNET/H       10
Ethernet      
Serial communication      
CC-Link      

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 375
 Accessible ranges (Personal computer side port: Ethernet board,
GOT2000/1000 side port: Ethernet port, CPU side port: Ethernet
port)

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Ethernet Ethernet

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected station Relayed network Relayed station CPU
CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCPU (Q mode)*1 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Qn(U)(J)(P)(D)(E)(V)(H) only operate. QnPRHCPU cannot be accessed.

10 ACCESSIBLE RANGES
376 10.18 For GOT Transparent Communication
Accessible ranges (Personal computer side port: Ethernet board,
GOT2000/1000 side port: Ethernet port, CPU side port: Q series-
compatible E71)

Configuration 10

Connected station Relayed module

Connected module
CPU

GOT Relayed network

Ethernet Ethernet

Relayed station
Personal computer Relayed module
CPU

Accessibility list
The following table indicates whether the CPUs can be accessed.
The connected station CPUs are all accessible.
Whether the relayed station CPU is accessible or not is indicated by  (accessible) or  (inaccessible).
Connected Connected Relayed network Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode)*1 Q series-compatible CC IE TSN     
E71
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Connected Relayed network Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
QCPU (Q mode)*1 Q series-compatible CC IE TSN      
E71
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

*1 Qn(U)(J)(P)(D)(E)(V)(H) only operate. QnPRHCPU cannot be accessed.

10 ACCESSIBLE RANGES
10.18 For GOT Transparent Communication 377
 10.19 For Inverter Communication
This section provides the accessible monitor types during inverter communication.

Accessible monitor type

The following table indicates the accessible monitor type during inverter communication.
Monitor type (Decimal) Name
1 Output frequency/speed
2 Output current
3 Output voltage
5 Frequency setting value/speed setting
6 Running speed
7 Motor torque
8 Converter output voltage
9 Regenerative brake duty
10 Electronic thermal O/L relay load factor
11 Output current peak value
12 Converter output voltage peak value
13 Input power
14 Output power
17 Load meter
18 Motor excitation current
19 Position pulse
20 Cumulative energization time
22 Orientation status
23 Actual operation time
24 Motor load factor
25 Cumulative power
32 Torque command
33 Torque current command
34 Motor output
35 Feedback pulse
40 PLC function user monitor 1
41 PLC function user monitor 2
42 PLC function user monitor 3
50 Energy saving effect
51 Cumulative energy saving
52 PID set point
53 PID measured value
61 Motor thermal load factor
62 Inverter thermal load factor
64 PTC thermistor resistance
67 PID measured value 2
87 Remote output value 1
88 Remote output value 2
89 Remote output value 3
90 Remote output value 4
91 PID manipulated variable
92 Second PID set point
93 Second PID measured value
94 Second PID deviation
95 Second PID measured value 2

10 ACCESSIBLE RANGES
378 10.19 For Inverter Communication
Monitor type (Decimal) Name
96 Second PID manipulated variable
97 Dancer main speed setting

10

10 ACCESSIBLE RANGES
10.19 For Inverter Communication 379
 10.20 For Robot Controller Communication
The following table indicates the accessible monitor type during robot controller communication.

Accessible monitor type

The following table indicates the accessible monitor type during robot controller communication.
Specify the monitor type with the following format: (Request ID).(Data type).(Argument).
Monitor type Acquired value
Request ID Data type Argument
231 1 (1) Input signal read start number Input signal information (16 points)
2 (1) Output signal read start number Output signal information (16 points)
237 1 (1) Register number Input register description
238 1 (1) Register number Output register description

10 ACCESSIBLE RANGES
380 10.20 For Robot Controller Communication
APPENDIX
Appendix 1 Concept of Routing Parameters
The routing function is used by the station of the programmable controller CPU in a multi-level system to perform the transient
transmission to the station of another network number.
To perform the routing function, the "Routing parameters" must be set to associate the network numbers and stations acting
as bridges.

Routing parameter settings

■The routing parameters must be set to the request source and relayed station of the
programmable controller CPU.
• The request source must be set to access the request target.
• The relayed station must be set to access from the request source to the request target and vice versa.
• The request target is not required to be set.
For example, to perform the transient transmission from 1Ns3 to 3Ns4 in the following diagram, the routing parameters must
be set to the programmable controller 1Ns3 which performs transient transmission, to the programmable controllers 1Ns4 and
2Mp1 which serve as bridges, and to the programmable controllers 2Ns4 and 3Ns5.

Routing parameter setting Routing parameter setting

Transfer target Relay target Relay target Transfer target Relay target Relay target
Network number Network number station number Network number Network number station number
3 1 4 1 2 1
Only transfer target network number 3 must be set. Transfer target network number 2 and 3 need not be set as they
are connected.

A
Request
source
1Mp1 1N2 1Ns3 3Mp1 3Ns2

Network No.1 Network No.3

1N6 1Ns5 1Ns4 2Mp1 2Ns4 3Ns5 3Ns4 3N3

Request
target
Network No.2

2Ns2 2N3

Routing parameter setting Mp: Control station

Transfer target Relay target Relay target Ns: Normal station (station that can be control station)
Network number Network number station number N: Normal station

3 2 4 Routing parameter setting areas

Transfer target network number 1 and 2 need not be set as they
are connected.

■Up to 16 "transfer target network numbers" can be set to the programmable controller CPU.
16 different network numbers allow the host station to be a request source or other stations to be accessed via the host
station.

APPX
Appendix 1 Concept of Routing Parameters 381
 Routing parameter setting areas and data
For transient transmission, the routing parameter setting areas differ according to the system.

■Two-level system
The routing parameters are not required to be set because transient transmission is performed to within the same network.

Request
source

Network No.1

Request
target

■Multi-level 1 (two networks)

Set the routing parameters only to the station of the request source. *1
To the request source, set the data to access the request target (network No.2).

Request
source
Relay station
Network No.1 Network No.2

Request
target

■Multi-level 2 (three networks)

Set the routing parameters to the request source and relayed stations. *1
To the request source, set the data to access the request target (network No.3).
To the relayed station 1, set the data to access the request target (network No.3).
To the relayed station 2, set the data to access the request source (network No.1).

Request
source
Relay station 1 Relay station 2
Network No.1 Network No.2 Network No.3

Request
target

APPX
382 Appendix 1 Concept of Routing Parameters
■Multi-level 3 (four or more networks)
Set the routing parameters to the request source and relayed stations. *1
To the request source, set the data to access the request target (network No.4).
To the relayed station 1 (the nearest relayed station to the request source), set the data to access the request target (network
No.4).
To the relayed station 2 (the nearest relayed station to the request target), set the data to access the request source (network
No.1).
To the relayed station 3 (relayed station other than 1 and 2), set the data to access the request target (network number No.4)
and request source (network No.1).

Request
source
Relay station 1 Relay station 3 Relay station 2
Network No.1 Network No.2 Network No.3 Network No.4

Request
target

*1 The following explains the case when the request source is the personal computer connected to Ethernet.
The routing parameter settings are not necessary for the request source.
The routing parameter settings are necessary for relay stations so that they can access the request source.
For settings, refer to the following manual.
 Q Corresponding Ethernet Interface Module User's Manual (Application)

APPX
Appendix 1 Concept of Routing Parameters 383
 Appendix 2 How to Configure Internet/Intranet
Environment
This section describes an example of configuring a system that uses MX Component to create a home page (HTML, ASP) for
communication with the programmable controller CPU and display it using the browser (Internet Explorer) via the Internet/
intranet.

Operating procedure
The following is the procedure to configure the Internet/intranet environment.

Start

Prepare the personal computer. (1)

Install the Web server. (2)

Set the Internet access account. (3)

Restart the personal computer.

Set the settings to release Web pages. (4)

Abnormal Conduct a
test using the sample (5)
page.

Normal

Set the settings to release any Web

(6)
page.

(1)Page 385 Conditions of usable personal computers

(2)Page 386 How to install Web server
(3)Page 387 Setting the Internet access account
(4)Page 393 Releasing Web pages
(5)Page 398 Checking whether Web server can be accessed properly
(6)Page 393 Releasing Web pages

Web pages using MX Component will not perform in the environment where a test using the sample page is
not conducted properly.
Check the traffic, noise and others of the communication line to operate the sample page properly.

APPX
384 Appendix 2 How to Configure Internet/Intranet Environment
Conditions of usable personal computers
The following are the conditions of the personal computers that can be used as a Web server and a Web client.

Personal computer that can be used as Web server (factory side)

When using the personal computer as a Web server, use the personal computer that satisfies all of the following conditions 1
to 4.
Condition Description
No.
Condition 1 Any of the following Operating Systems is operating on the personal computer.
• Microsoft Windows XP Professional Operating System
• Microsoft Windows Vista Home Premium Operating System
• Microsoft Windows Vista Business Operating System
• Microsoft Windows Vista Ultimate Operating System
• Microsoft Windows Vista Enterprise Operating System
• Microsoft Windows 7 Home Premium Operating System
• Microsoft Windows 7 Professional Operating System
• Microsoft Windows 7 Ultimate Operating System
• Microsoft Windows 7 Enterprise Operating System
• Microsoft Windows 8 Operating System
• Microsoft Windows 8 Pro Operating System
• Microsoft Windows 8 Enterprise Operating System
• Microsoft Windows 8.1 Operating System
• Microsoft Windows 8.1 Pro Operating System
• Microsoft Windows 8.1 Enterprise Operating System
• Microsoft Windows 10 Home Operating System
• Microsoft Windows 10 Pro Operating System
• Microsoft Windows 10 Education Operating System
• Microsoft Windows 10 Enterprise Operating System
Condition 2 The personal computer can be connected to the Internet or intranet.
Condition 3 When Web pages are released on the Internet, external access must not be inhibited by a firewall or the like.
Condition 4 MX Component is installed and settings are set for communication with the programmable controller CPU.
A
Personal computer that can be used as Web client (office side)
When using the personal computer as a Web client, use the personal computer that satisfies both of the following conditions
1 and 2.
Condition Description
No.
Condition 1 Any of the following Operating Systems is operating on the personal computer.
• Microsoft Windows XP Professional Operating System
• Microsoft Windows XP Home Edition Operating System
• Microsoft Windows Vista Home Basic Operating System
• Microsoft Windows Vista Home Premium Operating System
• Microsoft Windows Vista Business Operating System
• Microsoft Windows Vista Ultimate Operating System
• Microsoft Windows Vista Enterprise Operating System
• Microsoft Windows 7 Starter Operating System
• Microsoft Windows 7 Home Premium Operating System
• Microsoft Windows 7 Professional Operating System
• Microsoft Windows 7 Ultimate Operating System
• Microsoft Windows 7 Enterprise Operating System
• Microsoft Windows 8 Operating System
• Microsoft Windows 8 Pro Operating System
• Microsoft Windows 8 Enterprise Operating System
• Microsoft Windows 8.1 Operating System
• Microsoft Windows 8.1 Pro Operating System
• Microsoft Windows 8.1 Enterprise Operating System
• Microsoft Windows 10 Home Operating System
• Microsoft Windows 10 Pro Operating System
• Microsoft Windows 10 Education Operating System
• Microsoft Windows 10 Enterprise Operating System
Condition 2 The personal computer can be connected to the Internet or intranet.

APPX
Appendix 2 How to Configure Internet/Intranet Environment 385
 How to install Web server
Install the Web server in the following method.

When using Windows XP Professional

Operating procedure
1. Select [Start]  [Control Panel]  [Add/Remove Programs].

2. Install the Windows component "Internet Information Service (IIS)".

The Windows XP Professional setup CD is required for installation.

When using Windows Vista or later

Operating procedure
1. Select [Start]  [Control Panel]  [Program]  [Turn Windows features on or off].

2. Install "Internet Information Services".

For details of Web server installation method corresponding to the operating system, refer to the installation
procedure attached to the corresponding operating system.

APPX
386 Appendix 2 How to Configure Internet/Intranet Environment
Setting the Internet access account
Set the authorities to Internet access accounts.

When using Windows XP Professional

When the Active Server Pages (ASP) pages using MX Component are released, the IUSR_Name (Internet Server
Anonymous Access) must be given the "Debug programs" right.
Set the settings in the following procedure.

Operating procedure
1. Select [Start]  [Control Panel]  [Administrative Tools]
 [Local Security Policy].

2. Select [Local Policies]  [User Rights Assignment] in

the tree structure and double-click "Debug programs". A

APPX
Appendix 2 How to Configure Internet/Intranet Environment 387
 3. Click the [Add User or Group] button.

4. If the computer name (name of the computer where

Internet Information Service is set) is not displayed in
"Locations", select the computer name.
After confirming the above setting, click the [Advanced]
button.

5. Click the [Find Now] button, and select the

"IUSR_Name (Internet Server Anonymous Access)"
account from the "Name" list box, and click the [OK]
button.

APPX
388 Appendix 2 How to Configure Internet/Intranet Environment
 6. After checking that the account is added, restart the
personal computer.

Setting complete

APPX
Appendix 2 How to Configure Internet/Intranet Environment 389
 When using Windows Vista or later
When the Active Server Pages (ASP) pages using MX Component are released, the IUSR must be given the "Debug
programs" right.
Set the settings in the following procedure.

Operating procedure
1. Select [Start]  [Control Panel]  [Administrative Tools]
 [Local Security Policy].
When user account control is enabled, the following
screen is displayed.
Click the [Continue] button or [Yes] button.
<Windows Vista>

<Windows 7 or later>

2. Select [Local Policies]  [User Rights Assignment] in

the tree structure and double-click "Debug programs".

APPX
390 Appendix 2 How to Configure Internet/Intranet Environment
3. Click the [Add User or Group] button.

4. If the computer name (name of the computer where

Internet Information Service is set) is not displayed in
"Locations", select the computer name.
After confirming the above setting, click the [Advanced]
button.

A
5. Click the [Find Now] button, and select the "IUSR"
account from the "Name" list box, and click the [OK]
button.

APPX
Appendix 2 How to Configure Internet/Intranet Environment 391
 6. After checking that the account is added, restart the
personal computer.

Setting complete

APPX
392 Appendix 2 How to Configure Internet/Intranet Environment
Releasing Web pages
To release Web pages on the Internet/intranet, the folder must be Web shared.
The following is the procedure to share the folders on the Web.
Though the screen slightly varies according to the Web server operating system, the setting procedure is the same.

When using Microsoft Windows XP Professional

Operating procedure
1. Start Explorer and right-click a desired folder that
contains the Web file (*.html, *.asp) to be released, and
select [Properties].

2. Select the [Web Sharing] tab and select "Share this

folder".

APPX
Appendix 2 How to Configure Internet/Intranet Environment 393
 3. For changing the alias, change the settings on the Edit
Alias window.
The alias is the underlined part of the URL to be
specified on the Web browser.
http://**.**.**.**/Mxcomponent/NetTest.asp

Setting complete

APPX
394 Appendix 2 How to Configure Internet/Intranet Environment
When using Windows Vista or later
Operating procedure
1. Select [Start]  [Control Panel]  [Programs]  [Turn
Windows features on or off].

2. Select "Internet Information Services".

A
3. Expand the tree at [Application Development Features]
under [Internet Information Services]  [World Wide
Web Services], select "ASP" and click the [OK] button.

APPX
Appendix 2 How to Configure Internet/Intranet Environment 395
 Only when using Windows 7 (64-bit version)/Windows 8 (64-
bit version)/Windows 8.1 (64-bit version)/Windows 10 (64-bit
version), go to steps 4 and 5.

4. Select [Start]  [Administrative Tools]  [Internet

Information Services (IIS) Manager] and select
[Application Pools] from the left pane. Select an
application pool to be changed and select [Advanced
Settings] from the right pane.

5. Set "True" for [Enable 32-Bit Applications] and click the

[OK] button.

6. Select [Start]  [Control Panel]  [Classic View] 

[Administrative Tools], and double-click [IIS Manager].
When user account control is enabled, the following
screen is displayed.
Click the [Continue] button.

APPX
396 Appendix 2 How to Configure Internet/Intranet Environment
 7. Expand the tree on the [Connections] window, right-click
on [Default Web Site], and select [Add Virtual Directory].

8. Specify the desired name for "Alias:" and a folder path

name to be released for "Physical path:", and click the
[OK] button.
The alias is the underlined part of the URL to be
specified on the Web browser.
http://**.**.**.**/Mxcomponent/NetTest.asp

Setting complete

APPX
Appendix 2 How to Configure Internet/Intranet Environment 397
 Checking whether Web server can be accessed properly
When checking the accessibility via the Internet, the personal computer where the Web server is installed must be connected
to the Internet.
After confirming that the Web server is connected to the Internet/intranet, start the Web browser (Internet Explorer) on the
Web client side personal computer, enter the URL as indicated below, and check that the Web page is displayed properly.

(URL input example) http://192.168.0.1/Mxcomponent/NetTest.asp

Alias set in Appendix 2.5

IP address of Web server

NetTest.asp is the Web server operation checking test page offered by MX Component.
Check that the system date and system time of the server are displayed on the Web browser.

• If NetTest.asp cannot be accessed properly, the Web pages using MX Component cannot be accessed
either.
In such a case, reconfirm the Web server settings and Web client browser setting.
Even if the settings are correct, the Web pages may not be displayed because communication cannot be
performed properly due to dense traffic or the like of the communication line.
In this case, check the status of the communication line.
• NetTest.asp is stored in the following folder.
[user-specified folder] - [Act] - [Sample] - [VBScript] - [SampleASP]

APPX
398 Appendix 2 How to Configure Internet/Intranet Environment
Appendix 3 RS-232 Cable Wiring Examples for Serial
Communication
Q Series
The connector specifications are indicated below.
Pin number Signal Name Signal Direction
Q series-compatible C24  personal
computer
1 CD Receive carrier detection 
2 RD(RXD) Receive data 
3 SD(TXD) Send data 
4 DTR(ER) Data terminal ready 
5 SG Send ground 
6 DSR(DR) Data set ready 
7 RS(RTS) Request to send 
8 CS(CTS) Clear to send 
9 RI(CI) Call indication 

Connection example which can turn ON/OFF CD signal (No. 1 pin)

Q series-compatible C24 Personal Computer Side
Cable Connection and Signal Direction
Signal Name Pin number (Connection example for full duplex/half duplex communication) Signal Name

CD 1 CD
RD(RXD) 2 RD(RXD)

SD(TXD) 3 SD(TXD)

DTR(ER) 4 DTR(ER) A
SG 5 SG

DSR(DR) 6 DSR(DR)

RS(RTS) 7 RS(RTS)

CS(CTS) 8 CS(CTS)

RI(CI) 9

Connection example which cannot turn ON/OFF CD signal (No. 1 pin)

Connection example for performing DC code control or DTR/DSR control

Q series-compatible C24 Personal Computer Side

Cable Connection and Signal Direction
Signal Name Pin number (Connection example for full duplex communication) Signal Name

CD 1 CD
RD(RXD) 2 RD(RXD)

SD(TXD) 3 SD(TXD)

DTR(ER) 4 DTR(ER)

SG 5 SG

DSR(DR) 6 DSR(DR)

RS(RTS) 7 RS(RTS)

CS(CTS) 8 CS(CTS)

RI(CI) 9

APPX
Appendix 3 RS-232 Cable Wiring Examples for Serial Communication 399
 FX Series
The following shows the example of wiring a personal computer and the FX extended port.

Connection example of a personal computer and FX-485PC-IF converter with the RS-
232 cable

Personal Computer Side FX-485PC-IF side

Cable Connection and Signal Direction
Signal Name (Connection example for full duplex/half duplex communication) Signal Name Pin number

SD(TXD) SD(TXD) 2

RD(RXD) RD(RXD) 3

RS(RTS) RS(RTS) 4

CS(CTS) CS(CTS) 5

DR(DSR) DR(DSR) 6

SG(GND) SG(GND) 7

ER(DTR) ER(DTR) 20

Connection example of the FX-485PC-IF converter and the FX extended port (2-pair
wiring)
FX1N-485-BD
FX2N-485-BD
FX3G-485-BD
FX3U-485-BD
FX2NC-485ADP
FX-485PC-IF FX3U-485ADP FX0N-485ADP FX0N-485ADP

SDA SDA SDA SDA

R R
SDB SDB SDB SDB

RDA RDA RDA RDA

R R
RDB RDB RDB RDB
LINK SG SG LINK SG LINK SG

FG FG

Grounding

*1
R indicates a terminal resistance.
The terminal resistances must be installed at both ends of the circuit.
(For 2-pair wiring, use the terminal resistance of 330, 1/4W.)
For FX3G-485-BD, FX3U-485-BD and FX3U-485ADP, terminal resistances are built in.
Set the terminal resistance by the setting switch.
For FX0N-485ADP, FX1N-485-BD, FX2N-485-BD, and FX2NC-485ADP, use the provided terminal resistances.
*2 Ground the shields connected to FX1N-485-BD, FX2N-485-BD, FX2NC-485ADP, FX3G-485-BD, FX3U-485-BD, FX3U- 485ADP.
*3 Connect the FG terminal to the ground terminal of the grounded programmable controller.

APPX
400 Appendix 3 RS-232 Cable Wiring Examples for Serial Communication
Appendix 4 Multi-CPU System
The valid CPU number specified for a multi-CPU system is that of the last accessed station only.
When accessing the non-controlled CPU of the relayed module on the accessed station, use the modules of function version
B as the relayed modules and QCPUs (Q mode) on the host station, all relayed stations and accessed station.

CPU COM communication

Ex.
When the programmable controller CPU number 3 (0x3E2) is specified for access, the CPU  can be accessed.

Last access target

Personal
computer
Ò: QCPU (Q mode) No. 1
Ò Ó Ô Õ Ó: QCPU (Q mode) No. 2
Ô: QCPU (Q mode) No. 3
Õ: QCPU (Q mode) No. 4

CPU COM communication (via MELSECNET/H)

Ex.
When the programmable controller CPU No. 3 (0x3E2), network number 2 and station number 2 are specified for access, the
CPU ' can be accessed.
The CPU number cannot be specified for the relayed station.
Therefore, if the network number 1 is accessed in the following case, an error will occur because the network number
controlled by the CPU  is only "2".

Relayed station Last access target Ò: QCPU (Q mode) No. 1

Personal
computer Ó: QCPU (Q mode) No. 2
Ô: QCPU (Q mode) No. 3
Ò Ó Ô Õ 1 2 Ò’ Ó’ Ô’ Õ’ 2’ Õ: QCPU (Q mode) No. 4 A
1 MELSECNET/H module controlled by Ò
(Network number: 1, station number: 1)
MELSECNET/H 2 MELSECNET/H module controlled by Ó
(Network number: 2, station number: 1)
2’ MELSECNET/H module controlled by Ó’
(Network number: 2, station number: 2)

APPX
Appendix 4 Multi-CPU System 401
 Appendix 5 Number of Mountable Network Modules
for Q00JCPU, Q00UJCPU, Q00CPU,
Q00UCPU, Q01CPU or Q01UCPU
The following indicates the number of mountable network modules that can be connected when Q00JCPU, Q00UJCPU,
Q00CPU, Q00UCPU, Q01CPU, or Q01UCPU is used.
Network Module Number of Mountable Modules
MELSECNET/H module 1 module
Ethernet module 1 module
CC-Link module (Function version B or later) 2 modules
CC-Link IE Controller Network module 1 module

Therefore, the following systems cannot be configured.

Ex.
Since the number of applicable Ethernet modules is 1, the part of the system indicated by the dotted line cannot be
configured.

MX Component

Ethernet

QCPU QJ71 QJ71

(Q mode) E71 E71

Ethernet

QCPU QJ71 QCPU QJ71

Q QCPU QJ71
(Q mode) E71 (Q mode) E71
1 (Q mode) E71

Ex.
Since the number of applicable MELSECNET/H modules is one, the part of the system indicated by the dotted line cannot be
configured.

MX Component

MELSECNET/H

QCPU QJ71 QJ71 QCPU QJ71

MELSECNET/H
(Q mode) LP2 LP2 (Q mode) LP2

QCPU QJ71
QJ
(Q mode) LP2
P2

APPX
402 Appendix 5 Number of Mountable Network Modules for Q00JCPU, Q00UJCPU, Q00CPU, Q00UCPU, Q01CPU or Q01UCPU
Appendix 6 Flowchart for When Access cannot be
Performed during Modem
Communication
If the programmable controller CPU cannot be accessed using modem communication, refer to the following flowchart and
take corrective action.

Start

Can normal modem communication be No Reexamine the wiring, switch settings,

executed using GX Developer? parameter settings, etc.

Yes

Did the communication No 1. Reexamine the setting of the logical

test of Communication Setup Utility station number.
complete normally? 2. Take corrective action for the error
that occurred.
Yes

Yes
Did an error occur in the user program Reexamine the user program.
that was executed?

No A
Complete

APPX
Appendix 6 Flowchart for When Access cannot be Performed during Modem Communication 403
 Appendix 7 Compatibility with Redundant CPU
This section explains the compatibility of MX Component with a redundant CPU.

RnPCPU (redundant mode) and RnPSFCPU

Redundant CPU specification

In redundant CPU specification in iQ-R series, only "Not specified" can be selected.
Redundant CPU specification setting can either be set on the utility setting type Communication Setting Wizard screen or on
the program setting type control property.
• Not specified : Connect to the connection target programmable controller CPU as before.
To judge which system in the redundant CPU system is being accessed by MX Component, monitor the following special
relays.
• When checking which system is being accessed, System A or System B
Indicate system A/system B of a redundant system.
Remain ON/OFF even if the tracking cable is disconnected while the redundant system is running.
 System A System B System not determined.
SM1632 (System A identification flag) ON OFF OFF
SM1633 (System B identification flag) OFF ON OFF

• When checking the control/standby system status

Indicate the CPU module control/standby status
Remain ON/OFF even if the tracking cable is disconnected while the redundant system is running.
 Control system Standby system System not determined.
SM1634 (Control system status) ON OFF OFF
SM1635 (Standby system status) OFF ON OFF

Operation at occurrence of system switching

System switching is not supported by iQ-R series.

APPX
404 Appendix 7 Compatibility with Redundant CPU
QnPRH

Redundant CPU specification

In redundant CPU specification, select either "Control system" or "Not specified" to access the compatible Redundant CPU.
Redundant CPU specification setting can either be set on the utility setting type Communication Setting Wizard screen or on
the program setting type control property.
• Control system: Connect to the control system and continue to access the control system in response to system switching.
• Not specified : Connect to the connection target programmable controller CPU as before.
To judge which system in the redundant CPU system is being accessed by MX Component, monitor the following special
relays.
• When checking which system is being accessed, System A or System B
Indicate system A/system B of a redundant system.
Remain ON/OFF even if the tracking cable is disconnected while the redundant system is running.
 System A System B System not determined.(At the
time of TRK.CABLE
ERR.(Error code: 6120)
occurrence)
SM1511 (System A identification flag) ON OFF OFF
SM1512 (System B identification flag) OFF ON OFF

• When checking the control/standby system status

Indicate the CPU module control/standby status
Remain ON/OFF even if the tracking cable is disconnected while the redundant system is running.
 Control system Standby system System not determined.(At the
time of TRK.CABLE
ERR.(Error code: 6120)
occurrence)
SM1515 (Control system status) ON OFF OFF A
SM1516 (Standby system status) OFF ON OFF

Operation at occurrence of system switching

When system switching occurs during access to the redundant CPU after selection of "Control system", access is continued
as described below.

■Connection via other than MELSECNET/H, Ethernet or CC-Link IE Controller Network

Access to the control system after system switching is continued.
The following shows an example of CPU direct connection.

APPX
Appendix 7 Compatibility with Redundant CPU 405
 MX Component

Connection to control system

Control system Standby system

Tracking cable

MX Component

Connection to control system

Connection to control system via standby system

Standby system Control system

Tracking cable

APPX
406 Appendix 7 Compatibility with Redundant CPU
■Connection to MELSECNET/H, Ethernet or CC-Link IE Controller Network
Access to the control system after system switching is continued as shown below, depending on communication error
occurrence.
The following shows an example of Ethernet connection.

Ex.
When communication is normal

MX Component

Connection to control system

Ethernet

Control system Standby system

Tracking cable

MX Component

Connection to control system

Connection to control system via standby system

Standby system Control system

Tracking cable
A
Ex.
When communication error occurs

MX Component

Connection to control system

Ethernet

Communication
error
Control system Standby system

Tracking cable

MX Component

Connection to control system

Connection to control system via network

Standby system Control system

Tracking cable

APPX
Appendix 7 Compatibility with Redundant CPU 407
 In the case of Ethernet connection, it may take time from when a communication error occurs until
communication starts after connection to the control system.

Automatic switching of communication route

If a communication error occurs during access to the redundant CPU connected to MELSECNET/H, Ethernet or CC-Link IE
Controller Network in Control system specification, the communication route is automatically switched to continue access to
the control system.
Hereinafter, this automatic switching of the communication route is referred to as route switch.
The following describes the route switch conditions, how to check for route switch occurrence, and examples of access by
route switch.

■Route switch conditions

When a CPU is accessed under the following conditions, access to the redundant CPU is continued by route switch if a
communication error occurs.
 Conditions for continued access
Operation mode Backup mode, separate mode*1
Target system Control system

*1 In the separate mode, a system switching by the system does not occur at power OFF/RESET of the control system.
However, if a tracking error occurred at a start of communication, access to the control system is not continued by route
switch even if tracking is recovered after that.
Includes the status in which either redundant CPU is shut off or reset.

■How to check whether route switch occurred or not

When communication is performed with the redundant system specified, whether communication is continued by route switch
due to communication error can be estimated.
Special relay and special registers to be monitored as well as the estimated possibility of route switch are shown below.
SM1600*1 SD1590*2 SD1690*2 Possibility of route switch Reference
OFF Either one is other than 0 Since a system switching request from the network Page 409 Examples of access by route switch
module was detected, route switch may be executed. When system switching occurs at communication
error
ON 0 0 Since another system error occurred, route switch may be Page 409 Examples of access by route switch
executed. When standby system error occurs
ON Either one is other than 0 Since another system error occurred or a system Page 409 Examples of access by route switch
switching request from the network module was detected, When system switching occurs at communication
route switch may be executed. error, When standby system error occurs

*1 Even if SM1600 is ON, route switch does not occur when the CPU is not accessed via the tracking cable.
*2 When using SM1600, SD1590 and SD1690 to estimate whether route switch has occurred or not for the redundant CPU connected to
Ethernet, select the following items in the redundant setting of the network parameter of GX Works2.
Issue a system switching request at disconnection detection.
Issue a system switching request at communication error.
Check the following based on the status of the above special relay and special registers, and remove the error cause.
• Check the redundant CPU for an error.
• Check the tracking cable status and whether the tracking cable is correctly connected.
• Check the relevant network module for an error and the network where the relevant network module is connected for an
error.

APPX
408 Appendix 7 Compatibility with Redundant CPU
■Examples of access by route switch
The following shows examples of route switch during access to the control system by Ethernet connection.

Ex.
When system switching occurs at communication error

MX Component

Connection to control system

Ethernet

Communication
error
Control system Standby system

Tracking cable

MX Component

Connection to control system

Standby system Control system

Tracking cable

Ex. A
When standby system error occurs

MX Component

Connection to control system

Ethernet

Control system Standby system

Standby
system fault

Tracking cable

MX Component

Connection to control system

Ethernet

Control system Standby system

Tracking cable

APPX
Appendix 7 Compatibility with Redundant CPU 409
 • Route switch is not executed if a communication error occurs at a communication start for the redundant
CPU specified as the target. (A communication error occurs.)
• In the case of Ethernet connection, it may take time from when a communication error occurs until
communication starts after connection to the control system.
• If a communication error occurs, refer to the following sections and remove the communication disturbance.
Page 408 How to check whether route switch occurred or not
Page 409 Examples of access by route switch

Special relay and special registers to monitor when estimating the occurrence of route
switch
The following indicates details of the special relay and special registers to be monitored when estimating whether route switch
occurred or not.
Number Name Description Explanation
SM1600 Other system error flag OFF : No error • Turn on when an error occurs during redundant system error check. (Turn on when
ON : Error either of bits for SD1600 is ON.)
• Remain off when no errors are present.
SD1590 Module number for Module number for • Any of the following bits turns on corresponding to module number for network module
network module network module requesting path switch in host system.
requesting path switch in requesting path switch in • Turn off by the system after recovery from error of the relevant module by user.
host system host system Bit status
b15 to b11 to b1 b0 0: OFF
SD1590 0 0/1 0/1 0 1: ON

Module No. 0: Invalid, as CPU module uses

2 slots
Module No. 1: Indicates the module to
the right of CPU module
to
Module No.11: Indicates the module at the
right end of a 12-I/O slot
base (Q312B)

• Refer to SD1690 for module number for network module requesting path switch in other
system.
SD1690 Module number for Module number for • Any of the following bits turns on corresponding to module number for network module
network module network module requesting path switch in other systems.
requesting path switch in requesting path switch in • Turns off by the system after recovery from error of the relevant module by user.
other system other system Bit status
b15 to b11 to b1 b0 0: OFF
SD1690 0 0/1 0/1 0 1: ON

Module No. 0: Invalid, as CPU module uses

2 slots
Module No. 1: Indicates the module to
the right of CPU module
to
Module No.11: Indicates the module at the
right end of a 12-I/O slot
base (Q312B)

• Refer to SD1590 for module number for network module requesting path switch in host
system.

APPX
410 Appendix 7 Compatibility with Redundant CPU
Combination table
Communications via Q series redundant type extension base unit (Q65WRB) are supported.
The following table shows the supported/unsupported combinations.
: Can be used. : Cannot be used.
Product name Model Function Combination
version When mounted to the When mounted to the
main base extension base
MELSECNET/H module QJ71LP21-25 D or later  
QJ71LP21S-25 D or later  
QJ71LP21G D or later  
QJ71BR11 D or later  
QJ72LP25-25   
QJ72LP25G   
QJ72BR15   
QJ71LP21   
Ethernet module QJ71E71   
QJ71E71(N1)-B2 D or later  
QJ71E71(N1)-B5 D or later  
QJ71E71-100 D or later  
Serial communication module QJ71C24N   
QJ71C24N-R2   
QJ71C24N-R4   
CC-Link module QJ61BT11   
QJ61BT11N  *1 
CC-Link IE Controller Network module QJ71GP21-SX D or later  
QJ71GP21S-SX D or later  

*1 Cannot be used when the first five digits of the serial number is 06051 or lower. A

APPX
Appendix 7 Compatibility with Redundant CPU 411
 Appendix 8 Differences with previous version of MX
Component
Comparison with MX Component Version 3
This section explains the differences between MX Component Version 3 and Version 4.00A.
For the functions added or changed in version 4.00A and later, refer to the following section.
Page 445 Functions Added Since Previous Versions

Controls
The following are the modifications on controls.
• ACT control names are changed. (The program setting type controls are unified. Controls for transferring logging files are
added.)
• .NET controls are added. (Labels can be used.)
Type of control Control name
Version 3 Version 4.00A
ACT control Program setting type ActCCBD ActMLCCBD ActProgType ActMLProgType
ActCCG4A ActMLCCG4A
ActCCG4Q ActMLCCG4Q
ActCCG4QnA ActMLCCG4QnA
ActCCIEFADPTCP ActMLCCIEFADPTCP
ActCCIEFADPUDP ActMLCCIEFADPUDP
ActCCIEFBD ActMLCCIEFBD
ActFX485BD ActMLFX485BD
ActFXCPU ActMLFXCPU
ActFXCPUUSB ActMLFXCPUUSB
ActFXENETTCP ActMLFXENETTCP
ActGOT ActMLGOT
ActGOTTRSP ActMLGOTTRSP
ActLCPU ActMLLCPU
ActLCPUTCP ActMLLCPUTCP
ActLCPUUDP ActMLLCPUUDP
ActLCPUUSB ActMLLCPUUSB
ActLJ71C24 ActMLLJ71C24
ActLLT ActMLLLT
ActMnet10BD ActMLMnet10BD
ActMnet2BD ActMLMnet2BD
ActMnetGBD ActMLMnetGBD
ActMnetHBD ActMLMnetHBD
ActQCPUA ActMLQCPUA
ActQCPUQ ActMLQCPUQ
ActQCPUQBus ActMLQCPUQBus
ActQCPUQUSB ActMLQCPUQUSB
ActQJ71C24 ActMLQJ71C24
ActQJ71E71TCP ActMLQJ71E71TCP
ActQJ71E71UDP ActMLQJ71E71UDP
ActQnACPU ActMLQnACPU
ActQNUDECPUTCP ActMLQNUDECPUTCP
ActQNUDECPUUDP ActMLQNUDECPUUDP
ActSIM ActMLSIM

APPX
412 Appendix 8 Differences with previous version of MX Component
Type of control Control name
Version 3 Version 4.00A
ACT control Program setting type ActFXCPUTEL   
ActLJ71C24TEL
ActQ6TEL
ActQJ71C24TEL
ActSupport ActMLSupport ActSupportMsg ActMLSupportMsg
ActACPU ActMLACPU  
ActAFBD ActMLAFBD
ActAJ71C24 ActMLAJ71C24
ActAJ71E71TCP ActMLAJ71E71TCP
ActAJ71E71UDP ActMLAJ71E71UDP
ActAJ71QC24 ActMLAJ71QC24
ActAJ71QE71TCP ActMLAJ71QE71TCP
ActAJ71QE71UDP ActMLAJ71QE71UDP
ActAJ71UC24 ActMLAJ71UC24
ActAnUBD ActMLAnUBD
ActA6TEL 
ActAJ71QC24TEL
  ActProgDataLogging 
Utility setting type ActEasyIF ActMLEasyIF ActUtlType ActMLUtlType
  ActUtlDataLogging 
.NET control Utility setting type   DotUtlType 
DotSupportMsg

• Controls of MX Component Version 3

Controls of MX Component Version 3 can also be used by installing MX Component Version 4.
Page 415 Compatibility
• Using unsupported communication routes
Use the controls of MX Component Version 3 when using communication routes, such as the access to a
MELSEC-A series programmable controller, which are not supported by MX Component Version 4.
A
• Details of controls and communication routes
Refer to the following manuals.
MX Component Version 4 Programming Manual
MX Component Version 3 Programming Manual
These manuals are included on the CD-ROM of MX Component Version 4 in a PDF file format.

APPX
Appendix 8 Differences with previous version of MX Component 413
 Engineering environment
The following table shows the engineering environment supported by MX Component Version 4.00A as compared to MX
Component Version 3.
: Supported, : Not supported
Item Software supported by Version 3 Version 4.00A
OS Microsoft Windows 95 
Microsoft Windows 98
Microsoft Windows Millennium Edition
Microsoft Windows NT
Microsoft Windows 2000
Microsoft Windows XP *1
Microsoft Windows Vista
Microsoft Windows 7 
Programming language Visual Basic Microsoft Visual Basic 6.0 
Microsoft Visual Basic .NET 2003

Microsoft Visual Studio 2005 Visual Basic 

Microsoft Visual Studio 2008 Visual Basic
Microsoft Visual Studio 2010 Visual Basic
Visual C++ Microsoft Visual C++ 6.0 
Microsoft Visual C++ .NET 2003
Microsoft Visual Studio 2005 Visual C++ 
Microsoft Visual Studio 2008 Visual C++
Microsoft Visual Studio 2010 Visual C++
VBScript Text editor and commercially available HTML tool 
VBA Microsoft Excel 2000 
Microsoft Excel 2002
Microsoft Excel 2003 
Microsoft Excel 2007
Microsoft Excel 2010 (32-bit version)
Microsoft Access 2000 
Microsoft Access 2002
Microsoft Access 2003 
Microsoft Access 2007
Microsoft Access 2010 (32-bit version)

*1 Limitations on the supported Service Pack.

• Using the unsupported engineering environment

Use MX Component Version 3 when using the engineering environment which is not supported by MX
Component
Version 4. MX Component Version 3 is included on the CD-ROM of MX Component Version 4.
• Details of engineering environment
Refer to the following section and manual.
Page 49 Operating Environment
MX Component Version 3 Operating Manual
The manual is included on the CD-ROM of MX Component Version 4 in a PDF file format.

Communication Setup Utility

Changes regarding Communication Setup Utility are not necessary; however, the settings of communication routes supported
by MX Component Version 3 and MX Component Version 4 can be set.

APPX
414 Appendix 8 Differences with previous version of MX Component
Compatibility
Programs and communication settings of MX Component Version 3 can be utilized in MX Component Version 4.

Installation
MX Component Version 4 cannot be installed with MX Component Version 3.
Install MX Component Version 4 after uninstalling MX Component Version 3.

Utilizing programs
Controls of MX Component Version 3 are included in MX Component Version 4.
Therefore, programs with the controls of MX Component Version 3 can be used in MX Component Version 4 without
modifications.

Utilizing communication settings

Import the setting file (.ACT file) of MX Component Version 3 using Communication Setup Utility of MX Component Version 4.
(Page 96 Importing communication settings)
The settings can be used for controls of both MX Component Version 3 and MX Component Version 4.

APPX
Appendix 8 Differences with previous version of MX Component 415
 Appendix 9 Version Compatibility

Installation of ACT version

When do not use labels, the installation of .NET Framework and label functions can be avoided by using another installer
stored on the CD-ROM.
Run the SETUP.EXE stored in the VerACT folder.
The communication route that can be used for ACT version is as follows:
• When the connected station is a programmable controller or motion controller

APPX
416 Appendix 9 Version Compatibility
Appendix 10 Character Strings that cannot be Used
for Label Names
Reserved word
The reserved words cannot be used for label names.
The following tables shows character strings that cannot be used for label names.
Category Character string
Class identifier VAR, VAR_RETAIN, VAR_ACCESS, VAR_CONSTANT, VAR_CONSTANT_RETAIN, VAR_INPUT, VAR_INPUT_RETAIN,
VAR_OUTPUT, VAR_OUTPUT_RETAIN, VAR_IN_OUT, VAR_IN_EXT, VAR_EXTERNAL, VAR_EXTERNAL_CONSTANT,
VAR_EXTERNAL_CONSTANT_RETAIN, VAR_EXTERNAL_RETAIN, VAR_GLOBAL, VAR_GLOBAL_CONSTANT,
VAR_GLOBAL_CONSTANT_RETAIN, VAR_GLOBAL_RETAIN
Data type BOOL, BYTE, INT, SINT, DINT, LINT, UINT, USINT, UDINT, ULINT, WORD, DWORD, LWORD, ARRAY, REAL, LREAL, TIME,
STRING, TIMER, COUNTER, RETENTIVETIMER, POINTER, Bit, Word [Unsigned]/Bit String [16-bit], Double Word [Unsigned]/Bit
String [32-bit], Word [Signed], Double Word [Signed], FLOAT (Single Precision), FLOAT (Double Precision), String, Time, Timer,
Counter, Retentive Timer, Pointer
Data type hierarchy ANY, ANY_NUM, ANY_BIT, ANY_REAL, ANY_INT, ANY_DATE
ANY_SIMPLE, ANY16, ANY32
Device name X, Y, D, M, T, B, C, F, L, P, V, Z, W, I, N, U, J, K, H, E, A, SD, SM, SW, SB, FX, FY, DX, DY, FD, TR, BL, SG, VD, ZR, ZZ
Character string X0 or the like
recognized as device
(Device name +
numeral)
ST operator NOT, MOD
(, ), -
IL operator LD, LDN, ST, STN, S, S1, R, R1, AND, ANDN, OR, ORN, XOR, XORN, ADD, SUB, MUL, DIV, GT, GE, EQ, NE, LE, LT, JMP, JMPC,
JMPCN, CAL, CALC, CALCN, RET, RETC, RETCN
LDI, LDP, LDF, ANI, ANDP, ANDF, ANB, ORI, ORP, ORF, ORB, MPS, MRD, MPP, INV, MEP, MEF, EGP, EGF, OUT(H), SET, RST,
PLS, PLF, FF, DELTA(P), SFT(P), MC, MCR, STOP, PAGE, NOP, NOPLF
SFC instruction SFCP, SFCPEND, BLOCK, BEND, TRANL, TRANO, TRANA, TRANC, TRANCA, TRANOA, SEND, TRANOC, TRANOCA,
TRANCO, TRANCOC, STEPN, STEPD, STEPSC, STEPSE, STEPST, STEPR, STEPC, STEPG, STEPI, STEPID, STEPISC,
A
STEPISE, STEPIST, STEPIR, TRANJ, TRANOJ, TRANOCJ, TRANCJ, TRANCOJ, TRANCOCJ
ST code body RETURN, IF, THEN, ELSE, ELSIF, END_IF, CASE, OF, END_CASE, FOR, TO, BY, DO, END_FOR, WHILE, END_WHILE,
REPEAT, UNTIL, END_REPEAT, EXIT, TYPE, END_TYPE, STRUCT, END_STRUCT, RETAIN, VAR_ACCESS, END_VAR,
FUNCTION, END_FUNCTION, FUNCTION_BLOCK, END_FUNCTION_BLOCK, STEP, INITIAL_STEP, END_STEP, TRANSITION,
END_TRANSITION, FROM, UNTILWHILE
Function name in Function names in application functions AND_E, NOT_E or the like
application function
Function block name in Function block names in application functions CTD, CTU or the like
application function
Symbol /, \, *, ?, <, >, |, ", :, [, ], ,, =, +, %, ', ~, @, {, }, &, ^, ., tab character
;
!, #, $, `
Date and time literal DATE, DATE_AND_TIME, DT, TIME, TIME_OF_DAY, TOD
Others ACTION, END_ACTION, CONFIGURATION, END_CONFIGURATION, CONSTANT, F_EDGE, R_EDGE, AT, PROGRAM, WITH,
END_PROGRAM, TRUE, FALSE, READ_ONLY, READ_WRITE, RESOURCE, END_RESOURCE, ON, TASK, EN, ENO,
BODY_CCE, BODY_FBD, BODY_IL, BODY_LD, BODY_SFC, BODY_ST, END_BODY, END_PARAMETER_SECTION,
PARAM_FILE_PATH, PARAMETER_SECTION, SINGLE, RETAIN, INTERVAL
String that starts with K1AAA or the like
K1 to K8
Statement in ladder ;FB BLK START, ;FB START, ;FB END, ;FB BLK END, ;FB IN, ;FB OUT, ;FB_NAME, ;INSTANCE_NAME, ;FB, ;INSTANCE
language
Common instruction MOV or the like
Windows reserved word COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9,
AUX, CON, PRN, NUL
Surrogate pair 0xD800 to 0xDBFF, 0xDC00 to 0xDFFF
Control code U+0000 to U+001F, U+0080 to U+009F, U+00A0 to U+00BF, U+FFFE, U+FFFF
Environment dependent character

APPX
Appendix 10 Character Strings that cannot be Used for Label Names 417
 Considerations on using labels
• More than 32 characters cannot be used for system label Ver.1.
• More than 256 characters cannot be used for system label Ver.2.
(More than 32 characters cannot be used for a system label list name, and more than 246 characters cannot be used for a
structure name.)
• A space cannot be used.
• A numeral cannot be used at the beginning of label name.
• A label name is not case-sensitive.
• An underscore (_) cannot be used at the beginning or end of label name.
Consecutive underscores (_) cannot be used for a data name or a label name.
• The digit-specified bit devices cannot be used.
• The indexing cannot be used.
• The buffer memory cannot be specified.
• The device check cannot be executed when registering labels.

APPX
418 Appendix 10 Character Strings that cannot be Used for Label Names
Appendix 11 Performance
This section explains the performances in the following system configuration.

R
OS : Windows Vista
CPU : Intel Core 2Duo (2GHz)
R08CPU Memory : 2.00GB
Target CPU : R08CPU
(Connecting personal computer and target CPU on 1:1 basis)
Communication route : TCP/IP
Ethernet Number of system label registration : 1000

Performance of MX Component (Control)

Time performance
This explains read/write performance of the device and label.
Processing/Number of label registration Processing time (ms)
device system label Ver.1 system label Ver.2
first time second time first time second time
Batch read 1 word (1 label) 5.9 230.5 10.7 174.4 12.5
960 word (1 label) 12.3 227.3 17.3 182.0 19.8
12288 word (1 label) 157.9 353.5 164.5 330.3 166.9
Batch write 1 word (1 label) 5.6 218.1 11.0 177.5 12.0
960 word (1 label) 17.6 232.0 22.6 189.9 24.6
12288 word (1 label) 161.4 367.7 170.1 327.3 171.6
Random read 1 word (1 label) 5.6 31.0 4.5 40.8 5.0
128 word (128 label) 24.1 1802.7 38.2 2381.9 45.3
256 word (256 label) 42.3 3550.2 136.3 4866.6 169.8
Random write 1 word (1 label) 5.0 26.2 4.3 38.5 5.0 A
128 word (128 label) 30.5 1817.0 41.8 2334.5 47.0
256 word (256 label) 52.6 3550.1 140.2 4799.8 166.1

Memory performance
The following shows the amount of cache memory used for DotUtlType control.
Processing the amount of memory usage (KB)
system label Ver.1 system label Ver.2
Batch read 1000 label (160)*1 (160)*1
Batch write
Random read
Random write

*1 Value in the parentheses is a theoretical value.

Cache size (byte) = 160  Number of system labels used
160 (byte) = Cache data size per one system label
Number of system labels = Specify a total number of 1000 different system labels

APPX
Appendix 11 Performance 419
 Performance of the Label Service

Time performance
This explains time performance of the Label Service.
Processing Type of system label Processing time (ms)
Memory load processing at startup of personal computer by System label of structure type 4101
Label service
System label other than structure type 6161
Update of system label data System label of structure type 5064
System label other than structure type 7081

Memory performance
The following shows the amount of memory usage (working set) of the Label Service.
• Measurement condition: A number of registered system labels: 1000
Type of system label the amount of memory usage (KB)
system label Ver.1 system label Ver.2
System label of structure type 30256 30268
System label other than structure type 31604 32156

A number of registered system labels written above as measurement condition differ depending on whether
the data type is structure type or other than structure type.
• Other than structure type: Number of registered system labels = Number of system labels registered in
Label Utility
• Structure type: Number of registered system labels = (1+ Number of structure elements)  Number of
system labels registered in Label Utility
As for "A number of registered system labels: 1000" in the table above, 100 system labels of which data types
are structure, and which have nine structure elements are defined. The formula is as follows: (1 + 9)  100 =
1000.

APPX
420 Appendix 11 Performance
Performance of the Label Utility

Time performance
This explains time performance of the Label Utility.
Processing Type of system label Processing time (s)
system label Ver.1 system label Ver.2
Change of label space System label of structure type 7.2 6.2
System label other than structure type 7.7 8.0
Save of label space System label of structure type 8.7 6.8
System label other than structure type 9.2 9.1
Import System label of structure type 0.9 0.6
System label other than structure type 0.8 0.9
Export System label of structure type 0.8 0.9
System label other than structure type 0.8 0.9

The processing time of "Save of label space" in the table above will be increased as the number of registered system labels is
increased because the check processing before the save takes longer time for its processing.
Therefore, the processing time is increased more than the increase rate of a number of registered system labels.

Memory performance
The following shows the amount of memory usage (working set) of the Label Utility.
• Measurement condition: A number of registered system labels: 1000
Type of system label the amount of memory usage (KB)
system label Ver.1 system label Ver.2
System label undefined 4108 4316
System label of structure type 8608 7500
System label other than structure type 12872 12256
A

APPX
Appendix 11 Performance 421
 DISK occupied size
The following table shows the DISK occupied size of the system label database.
Type of system label DISK occupied size (KB)
system label Ver.1 system label Ver.2
System label undefined (A number of registered system labels: 0) 1756 24
System label of structure type (A number of registered system labels: 2310 89
1000)
System label other than structure type (A number of registered system 2370 246
labels: 1000)

A number of registered system labels written above as measurement condition differ depending on whether
the data type is structure type or other than structure type.
• Other than structure type: Number of registered system labels = Number of system labels registered in
Label Utility
• Structure type: Number of registered system labels = (1+ Number of structure elements)  Number of
system labels registered in Label Utility
As for "A number of registered system labels: 1000" in the table above, 100 system labels of which data types
are structure, and which have nine structure elements are defined. The formula is as follows: (1 + 9)  100 =
1000.

APPX
422 Appendix 11 Performance
Appendix 12 USB Driver Installation
In order to communicate with a programmable controller CPU via USB, a USB driver is required to be installed.
The following explains the USB driver installation procedure.

When more than one MELSOFT product is installed, the USB driver is installed in the folder to which the first
MELSOFT product is installed.
This section explains using the USB driver installation destination folder:
C:\Program Files\MELSOFT\Easysocket\USBDrivers, as an example.

Windows XP
The following explains the procedure of USB driver installation for Windows XP.

Operating procedure
1. Connect the personal computer and the programmable
controller CPU with USB cable, and turn on the
programmable controller CPU.
The screen shown on the left is displayed.
2. Select "Install from a list or specific location [Advanced]"
and click the [Next] button.

3. Select "Search for the best driver in these locations",

and select "Include this location in the search".
4. Click the [Browse] button.

APPX
Appendix 12 USB Driver Installation 423
 5. Select the USB driver installation destination folder,
select [Easysocket]  [USBDrivers], and click the [OK]
button.

6. Select "MITSUBISHI Easysocket Driver", and click the

[Next] button.

7. Click the [Continue Anyway] button.

APPX
424 Appendix 12 USB Driver Installation
 The screen shown on the left is displayed, and the USB
driver installation is complete.

8. Click the [Finish] button to close the window.

Installation complete

If the USB driver cannot be installed, confirm the following settings.

If "Block - Never install unsigned driver software" is selected under [Control Panel] - [System] - [Hardware] -
[Driver Signing], the USB driver may not be installed.
Select "Ignore - Install the software anyway and don't ask for my approval", or "Warn - Prompt me each time to
choose an action" in [Driver Signing], and execute the USB driver installation.

APPX
Appendix 12 USB Driver Installation 425
 Windows Vista
The following explains the procedure of USB driver installation for Windows Vista.

Operating procedure
1. Connect the personal computer and the programmable
controller CPU with USB cable, and then turn on the
programmable controller CPU.
The screen shown on the left is displayed.

2. Select "Locate and install driver software

(recommended)" and wait for a search to finish.

3. When User Account Control is turned ON, the screen

shown on the left is displayed.
Click the [Continue] button.

4. Select "Browse my computer for driver software

(advanced)".

APPX
426 Appendix 12 USB Driver Installation
 5. Specify "Easysocket\USBDrivers", and click the [Next]
button.

6. Select "Install this driver software anyway".

The screen shown on the left is displayed, and the USB

A
driver installation is complete.

7. Click the [Close] button.

Installation complete

APPX
Appendix 12 USB Driver Installation 427
 Windows 7 or later
The following explains the procedure of USB driver installation for Windows 7 or later.

Operating procedure
1. Connect the personal computer and the programmable
controller CPU with USB cable, and then turn on the
programmable controller CPU.
<When using Windows 7>
The screen shown on the left is displayed.
<When using Windows 8 or Windows 8.1>
The screen is not displayed.
2. Select "System and Security" from the Control Panel.
(To display the Control Panel, select [Start]  [Control
Panel].)

3. Select [Administrative Tools].

4. Select "Computer Management" and double-click it.

APPX
428 Appendix 12 USB Driver Installation
5. Right-click "Unknown device" in Device Manager, and
select "Update Driver Software".
When the USB driver cannot be specified because more
than one "Unknown device" exists, right-click "Unknown
device" and select "Properties". The "Unknown device",
whose "Hardware Ids" is "USB\VID_06D3&PID_1800"
on the [Details] tab of the properties screen, is the
update target.

6. Select "Browse my computer for driver software".

7. Specify "Easysocket\USBDrivers", and click the [Next]

button.
The left screen is an example when C:\Program
Files\MELSEC\Easysocket\USBDrivers is set.
If more than one MELSOFT product is installed, browse
for the installation destination of the first product.

APPX
Appendix 12 USB Driver Installation 429
 8. Click the [Install] button.

9. Click the [Close] button.

10. "MITSUBISHI Easysocket Driver" is registered under

"Universal Serial Bus controllers".

Installation complete

APPX
430 Appendix 12 USB Driver Installation
Appendix 13 Updating USB Driver
In Windows Vista or later, when upgrading the MELSOFT version that is incompatible with each operating system to
compatible, updating the USB drivers is also required.
The USB driver has the following two types:
• USB driver for programmable controller connection
• USB driver for GOT connection (Used for the GOT transparent mode.)

Procedure for updating the USB driver for programmable controller connection
■Checking method
Whether an update of the USB driver is required or not can be checked by its version.
Start the Windows Device Manager while the personal computer is connected to the programmable controller with USB, right-
click "MITSUBISHI Easysocket Driver", and select "Properties".
Update is required if the version shown on the [Driver] tab of the properties screen is the following.
• Windows Vista: "2.0.0.0" or earlier
• Windows 7 : "3.0.0.0" or earlier
• Windows 8 or Windows 8.1: "4.0.0.0" or earlier

■Procedure for update

1. Connect the personal computer and the programmable
controller CPU with USB cable.
2. Start the Device Manager, right-click "MITSUBISHI
Easysocket Driver", and select "Uninstall".

APPX
Appendix 13 Updating USB Driver 431
 3. Select the "Delete the driver software for this device"
check box, and click the [OK] button.

4. Disconnect the USB cable and reconnect it to the same

USB port after 5 seconds.
When using Windows Vista, the following screen is
displayed. Select "Ask me again later".

5. Right-click "Unknown device" in Device Manager, and

select "Update Driver Software".
When the USB driver cannot be specified because more
than one "Unknown device" exists, right-click "Unknown
device" and select "Properties". The "Unknown device",
whose "Hardware Ids" is "USB\VID_06D3&PID_1800"
on the [Details] tab of the properties screen, is the
update target.

APPX
432 Appendix 13 Updating USB Driver
 6. Select "Browse my computer for driver software".

7. Specify "Easysocket\USBDrivers", and click the [Next]

button.
The left screen is an example when C:\Program
Files\MELSEC\Easysocket\USBDrivers is set.
If more than one MELSOFT product is installed, browse
for the installation destination of the first product.

A
8. Click the [Install] button.

9. Click the [Close] button.

Complete

APPX
Appendix 13 Updating USB Driver 433
 Procedure for updating the USB driver for GOT connection
■Checking method
Restart the GOT while the personal computer is connected to the GOT with USB and start the Windows Device Manager.
If "MITSUBISHI GOT2000 USB Controller" or "MITSUBISHI GOT1000 USB Controller" is not displayed under "Universal
Serial Bus controllers", but "Unknown device" is displayed under "Other devices", the device is required to be updated.
The "Unknown device", whose "Hardware Ids" is "USB\VID_06D3&PID_01E0" on the [Details] tab of the properties screen, is
the update target.

■Procedure for update

1. Connect the personal computer and the GOT with USB
cable.

2. Start the Device Manager, right-click "Unknown device",

and select [Update Driver Software].

3. Select "Browse my computer for driver software".

APPX
434 Appendix 13 Updating USB Driver
 4. Specify "Easysocket\USBDrivers", and click the [Next]
button.
The left screen is an example when C:\Program
Files\MELSEC\Easysocket\USBDrivers is set.
If more than one MELSOFT product is installed, browse
the installation destination of the first product.

5. Click the [Close] button.

A
Complete

APPX
Appendix 13 Updating USB Driver 435
 Appendix 14 Warning Messages on Windows
Overview of warning messages
The user account control function is added to Windows Vista or later.
By this function, a warning message is displayed when executing utilities with the administrator authority. (Page 88
Starting Utilities)
<Windows Vista> <Windows 7 or later>

APPX
436 Appendix 14 Warning Messages on Windows
Methods for disabling warning messages

• The user account control (UAC) function prevents a crash (e.g. prevention of startup of a program which
executes unintended operation). Before setting this function, grasp that the security function offered by UAC
will be disabled and fully understand the risk.
• The method of allowing the setting without displaying the warning message cannot be attempted for
Windows 8 or later.

The following two methods are available for preventing a warning message.

Disabling the user account control function

The following shows a procedure for disabling the user account control function.

■When using Windows Vista

Operating procedure
1. Select [Start]  [Control Panel].

2. Select [User Accounts].

APPX
Appendix 14 Warning Messages on Windows 437
 3. Select [User Accounts].

4. Select [Turn User Account Control on or off].

5. Clear [Use User Account Control (UAC) to help protect

your computer] and click the [OK] button.

Setting complete

APPX
438 Appendix 14 Warning Messages on Windows
■When using Windows 7

Operating procedure
1. Select [Start]  [Control Panel].

2. Select [System and Security].

3. Select [Change User Account Control settings].

APPX
Appendix 14 Warning Messages on Windows 439
 4. Set the slide bar "Never notify" and click the [OK] button.

Continued on next page

APPX
440 Appendix 14 Warning Messages on Windows
Allowing the setting without displaying the warning message
The following shows a procedure for allowing the setting without displaying the warning message.

Operating procedure
1. Select [Start]  [Control Panel].

2. Select [System and Security].

When using Windows Vista, select [Classic View].

3. Select [Administrative Tools].

APPX
Appendix 14 Warning Messages on Windows 441
 4. Select [Local Security Policy].
When user account control is enabled, the following
screen is displayed.
Click the [Continue] button or [Yes] button.
<Windows Vista>

<Windows 7 or later>

5. Select [Local Policies].

6. Select [Security Options].

APPX
442 Appendix 14 Warning Messages on Windows
7. Select [User Account Control: Behavior of the elevation
prompt for administrators in Admin Approval Mode
Prompt for consent].

8. Select [Elevate without prompting] on the [Local

Security Setting] tab, and click the [OK] button.

APPX
Appendix 14 Warning Messages on Windows 443
 Appendix 15 Troubleshooting
This section explains the errors which may occur when using MX Component and the troubleshooting.

When self-registration is not performed at the time of executing the installer

On Windows Vista or later, some particular settings may cause an installation failure.
For the corrective actions, refer to the following section.
Page 60 When self-registration is not performed at the time of executing the installer

APPX
444 Appendix 15 Troubleshooting
Appendix 16 Functions Added Since Previous
Versions
This section shows major functions added/changed with upgrade.
Version Major function added/ Description Reference
changed
Version 4.00A Programmable controller type The following modules are supported. Page 52 Applicable
• Q172CPU, Q173CPU, Q172HCPU, Q173HCPU, Q172DCPU, Programmable Controller
Q173DCPU, Q172DSCPU, Q173DSCPU CPUs
Label The system label is supported. Page 71 SYSTEM
LABELS
Version 4.02C Programmable controller type The following modules are supported. Page 52 Applicable
• Q03UDVCPU, Q04UDVCPU, Q06UDVCPU, Q13UDVCPU, Programmable Controller
Q26UDVCPU CPUs
• Q24DHCCPU-V
• FX3GCCPU
Version 4.04E Programmable controller type L02SCPU, L06CPU, and L26CPU are supported. 
Operation Environment Windows 8 is supported. Page 49 Operating
Environment
Programming language Visual C# .NET is supported. Page 67 When using
Visual C# .NET
Development software Visual Studio 2012 is supported. Page 49 Operating
Environment
Comminication route The following connections are supported. Page 266 ACCESSIBLE
• The CPU COM communication (via another station on CC-Link) RANGES
whose connected station is FXCPU
• The USB communication (via another station on CC-Link)
whose connected station is FXCPU
• The Ethernet communication whose connected station is
Ethernet adapter
• MT Simulator2 Communication
• The GOT transparent communication (via another station on
CC-Link) with serial connection whose connected station is
A
FXCPU
• The GOT transparent communication (via another station on
CC-Link) with USB connection whose connected station is
FXCPU
• The GOT transparent communication whose connected station
is Ethernet adapter/module
• The GOT transparent communication with Ethernet connection
whose connected station is FXCPU
Version 4.05F Programmable controller type The following modules are supported. Page 52 Applicable
• Q12DCCPU-V (Extended mode), Q24DHCCPU-LS Programmable Controller
• FX3SCPU CPUs
• GOT2000
• Inverter
Development software The following pieces of software are supported. Page 49 Operating
• Microsoft Excel 2013 (32-bit version) Environment
• Microsoft Access 2013 (32-bit version)
Comminication route The following connections are supported. Page 266 ACCESSIBLE
• The inverter communication whose connected station is an RANGES
inverter
Version 4.06G Programmable controller type The following modules are supported. Page 52 Applicable
• R04CPU, R08CPU, R16CPU, R32CPU, R120CPU Programmable Controller
• R16MTCPU, R32MTCPU CPUs
Operation Environment Windows 8.1 is supported. Page 49 Operating
Environment

APPX
Appendix 16 Functions Added Since Previous Versions 445
 Version Major function added/ Description Reference
changed
Version 4.07H Programmable controller type The following modules are supported. Page 36 System
• Robot controller configurations
Development software Visual Studio 2013 is supported. Page 49 Operating
Environment
Label The system label Ver.2 is supported. Page 71 SYSTEM
LABELS
Comminication route The following connections are supported. Page 266 ACCESSIBLE
• The robot controller communication whose connected station is RANGES
a robot controller
Version 4.09K Programmable controller type The following modules are supported. Page 52 Applicable
• FX5UCPU, FX5UCCPU Programmable Controller
CPUs
Comminication route The following connections are supported. Page 266 ACCESSIBLE
• The Ethernet communication whose connected station is RANGES
FX5CPU
• The CPU COM communication whose connected station is
FX5CPU
Version 4.10L Programmable controller type The following modules are supported. Page 52 Applicable
• R08PCPU, R16PCPU, R32PCPU, R120PCPU Programmable Controller
• R08SFCPU, R16SFCPU, R32SFCPU, R120SFCPU CPUs
Comminication route The following connections are supported. Page 266 ACCESSIBLE
• The Ethernet communication whose connected station are RANGES
RnPCPU and RnSFCPU
• The CPU USB communication whose connected station are
RnPCPU and RnSFCPU
Version 4.11M Programmable controller type The following modules are supported. Page 52 Applicable
• R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, Programmable Controller
R120ENCPU CPUs
• Q24DHCCPU-VG, Q26DHCCPU-LS, R12CCPU-V
Label Up to five-level structures are supported by System label Ver.2. Page 71 SYSTEM
LABELS
Comminication route The following connections are supported. Page 266 ACCESSIBLE
• GX Simulator3 Communication RANGES
• The GOT transparent communication whose connected
stations are RnPCPU, RnSFCPU, and FX5CPU
Version 4.12N Programmable controller type The redundant mode of RnPCPU is supported. Page 52 Applicable
Programmable Controller
CPUs
Operation Environment Windows 10 is supported. Page 49 Operating
Environment
Development software The following pieces of software are supported. Page 49 Operating
• Microsoft Excel 2016 (32-bit version) Environment
• Microsoft Access 2016 (32-bit version)
• Visual Studio 2015
Comminication route The connection to FX5CPU using CC-Link IE Field Network by Page 266 ACCESSIBLE
specifying other station on the following communication route is RANGES
added.
• The Ethernet communication whose connected station are
FX5CPU and RCPU
• The CPU COM communication whose connected station is
FX5CPU
• The USB COM communication whose connected station is
RCPU
• The GOT transparent communication whose connected
stations are FX5CPU and RCPU
Version 4.13P Comminication route The following connections are supported. Page 266 ACCESSIBLE
• GX Simulator3 Communication (FX5CPU) RANGES
• The Ethernet communication whose connected station is LCPU
• The CC-Link communication, CC-Link IE Controller Network
communication, and CC-Link IE Field Network communication
using a personal computer board whose connected station is
RCPU

APPX
446 Appendix 16 Functions Added Since Previous Versions
Version Major function added/ Description Reference
changed
Version 4.14Q Programmable controller type The following boards are supported in Windows 10. Page 35 When using
• CC-Link Ver.2 board Windows 10 Operating
• MELSECNET/H board System
• CC-Link IE Controller Network board
• CC-Link IE Field Network board
Comminication route The following connections are supported. Page 266 ACCESSIBLE
• The serial communication/USB communication/Ethernet RANGES
communication/GOT transparent communication (via another
station on CC-Link) whose connected station is FX5CPU
• GOT transparent communication with Ethernet connection
whose connected station is QCPU/QJ71E71
Version 4.16S Development software Visual Studio 2017 is supported. Page 49 Operating
Environment
Property The default port number of FX5CPU simulator is changed to 5511. 
Programmable controller type The following modules are supported. Page 52 Applicable
• R00CPU, R01CPU, R02CPU Programmable Controller
• R08PSFCPU, R16PSFCPU, R32PSFCPU, R120PSFCPU CPUs
Comminication route The communication route to an RnPCPU is supported by using Page 266 ACCESSIBLE
any of the following boards: RANGES
• CC-Link IE Controller Network board
• CC-Link IE Field Network board
• CC-Link Ver.2 board
Version 4.17T Comminication route The following connections are supported. Page 334 For GX
• GX Simulator3 Communication (for RCPUs (R00, R01, R02), Simulator3
RnENCPUs, RnSFCPUs, and RnPSFCPUs) Communication
The communication using a CC-Link IE Controller network 
interface board (NZ81BD-GP21-SX) is supported.
Control Controls for transferring logging files are added. MX Component
Version 4 Programming
Manual
Operation Environment Windows 10 IoT Enterprise 2016 LTSB is supported. Page 49 Operating
Environment
A
Version 4.18U Comminication route The following connections are supported. Page 266 ACCESSIBLE
• The Ethernet communication whose connected station is RCPU RANGES
(using a CC-Link IE TSN module)
• The CC-Link IE Field Network communication whose
connected station is RCPU (using a CC-Link IE TSN module)
• The USB communication whose connected station is RCPU
(via CC IE TSN)
• The serial communication whose connected station is RCPU
(via CC IE TSN)
Version 4.19V Development software • Microsoft Excel 2019 (32-bit version) Page 49 Operating
• Microsoft Access 2019 (32-bit version) Environment
Programmable controller type The following modules are supported. Page 52 Applicable
• L04HCPU, L08HCPU, L16HCPU Programmable Controller
CPUs
Comminication route • The Ethernet communication whose connected station is Page 266 ACCESSIBLE
LHCPU RANGES
• The CPU USB communication whose connected station is
LHCPU
Version 4.21X Programmable controller type The following module is supported. Page 52 Applicable
• FX5UJCPU Programmable Controller
CPUs
Comminication route The following connections are supported. Page 266 ACCESSIBLE
• The Ethernet communication whose connected station is RANGES
FX5UJCPU
• The CPU COM communication whose connected station is
FX5UJCPU
• The CPU USB communication whose connected station is
FX5UJCPU
• The GOT transparent communication whose connected station
is FX5UJCPU

APPX
Appendix 16 Functions Added Since Previous Versions 447
 MEMO

APPX
448 Appendix 16 Functions Added Since Previous Versions
REVISIONS
*The manual number is given on the bottom left of the back cover.
Revision date *Manual number Description
July 2012 SH(NA)-081084ENG-A Due to the transition to the e-Manual, the details on revision have been deleted.
to to
April 2019 SH(NA)-081084ENG-Q
January 2020 SH(NA)-081084ENG-R Complete revision (layout change)
■Added or modified parts
TERMS, Section 2.2, Section 3.1, Section 5.1, Section 10.2, Section 10.3, Section 10.5, Section
10.6, Section 10.10, Appendix 16
November 2020 SH(NA)-081084ENG-S ■Added or modified parts
SAFETY PRECAUTIONS, CONDITIONS OF USE FOR THE PRODUCT, TERMS, Section 2.2,
Section 2.3, Section 2.4, Section 10.4, Section 10.5, Section 10.16, Section 10.18, Appendix 10,
Appendix 16
November 2021 SH(NA)-081084ENG-T ■Added or modified parts
TRADEMARKS

Japanese manual number: SH-081082-T

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.

 2012 MITSUBISHI ELECTRIC CORPORATION

449
 TRADEMARKS
Intel is either registered trademarks or trademarks of Intel Corporation in the United States and/or other countries.
Java is registered trademarks of Oracle and/or its affiliates.
Microsoft, Microsoft Access, Excel, Visual Basic, Visual C++, Visual C#, Visual Studio, Windows, Windows Vista, and
Windows XP are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.
The company names, system names and product names mentioned in this manual are either registered trademarks or
trademarks of their respective companies.
In some cases, trademark symbols such as '' or '' are not specified in this manual.
SPREAD
Copyright  2004 FarPoint Technologies, Inc.
VSFlexGrid8 Pro
Copyright  2008 ComponentOne LLC.

450
SH(NA)-081084ENG-T(2111)KWIX
MODEL: SW4DNC-ACT-O-E
MODEL CODE: 13JU75

HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN
NAGOYA WORKS : 1-14 , YADA-MINAMI 5-CHOME , HIGASHI-KU, NAGOYA , JAPAN

When exported from Japan, this manual does not require application to the
Ministry of Economy, Trade and Industry for service transaction permission.

Specifications subject to change without notice.