SH 082395 Engc

MX Component Version 5
Reference Manual
-SW5DND-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 module used and MELSEC iQ-R Module Configuration Manual.
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
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.
3
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
GENERIC TERMS AND ABBREVIATIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
PART 1 FUNDAMENTALS AND CREATING PROCEDURE
CHAPTER 1 FUNDAMENTALS OF MX Component 16

1.1 Before Using this Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Using MX Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2 Types of Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Control list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.3 Types of Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
CHAPTER 2 SYSTEM CONFIGURATIONS 24

2.1 Operating Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2 Supported Communication Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3 System Configuration List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
System configuration examples of each communication route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4 Available Module List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Programmable controller CPU list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Module list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.5 Details on the Communication Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
CHAPTER 3 USER APPLICATION CREATING PROCEDURES 37

3.1 Installing MX Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Checking the Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Opening the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2 Grasping a Control to be Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3 Selecting a Communication Setting Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.4 Adding a Control to a User Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.5 Creating a New User Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.6 Communication Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.7 Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
CHAPTER 4 ADDING CONTROLS TO USER PROGRAM 40

4.1 When using VBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.2 When using Visual Basic .NET, Visual C# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.3 When using Visual C++. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
CHAPTER 5 COMMUNICATION SETTING 52

5.1 Setting with Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Starting Communication Settings Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
[Target setting] tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
[List view] tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
[Communication test] tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4
Exporting/importing the communication settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Specifying a created logical number in a program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.2 Setting in Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Checking a property with Communication Settings Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Setting a required property in a user program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
CHAPTER 6 COMMUNICATION SETTING EXAMPLES (UTILITY SETTING TYPE) 66

6.1 Serial Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
CONTENTS
Logical station number setting example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Settings of serial communication modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.2 Ethernet Communication (When Using Ethernet Modules) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Settings of modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.3 Ethernet Communication (When Using Built-in Ethernet CPUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.4 Ethernet Communication (When Using Ethernet Adapter Modules) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.5 Ethernet Communication (When Using Ethernet Adapter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.6 CPU COM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.7 CPU USB Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.8 CC-Link Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.9 CC-Link system RS-232 interface Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.10 GX Simulator2 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
6.11 GX Simulator3 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.12 MT Simulator2 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.13 MELSECNET/H Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5
6.14 CC-Link IE Controller Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6.15 CC-Link IE Field Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.16 GOT Gateway Device Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Logical station number setting example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
6.17 GOT Transparent Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.18 Inverter COM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
6.19 Inverter USB Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
6.20 Robot controller COM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.21 Robot controller USB Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6.22 Robot controller Ethernet Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
CHAPTER 7 PROGRAMMING 111

7.1 Creating a Label With Label Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Starting Label Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Label screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Registering/deleting a logical station number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
System label list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Structure setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Referring and registering/canceling Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Change notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Updating system label data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Exporting/Importing LabelSpace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
System label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
7.2 Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
7.3 Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Checking a value using PLC Monitor Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
PART 2 DETAILED SPECIFICATIONS OF PROGRAMS
CHAPTER 8 ACCESSIBLE DEVICES AND DEVICE TYPES 149

8.1 Accessible Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
For serial communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
For Ethernet communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
6
For CPU COM communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
For CPU USB communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
For CC-Link communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
For CC-Link system RS-232 interface communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
For MELSECNET/H communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
For CC-Link IE Controller Network communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
For CC-Link IE Field Network communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
For GX Simulator2 communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
For GX Simulator3 communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
CONTENTS
For MT Simulator2 communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
For GOT gateway device communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
For GOT Transparent communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
For inverter communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
For robot controller communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
8.2 Device Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
CHAPTER 9 PROPERTIES OF CONTROLS 181

9.1 Property List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
9.2 Details of Control Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
CHAPTER 10 PROPERTY SETTINGS OF COMMUNICATION ROUTES 192

10.1 Serial Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Serial communication when the connected station is R series-compatible C24 (1) . . . . . . . . . . . . . . . . . . . . . 192
Serial communication when the connected station is R series-compatible C24 (2) . . . . . . . . . . . . . . . . . . . . . 195
Serial communication when the connected station is Q series-compatible C24 (1) . . . . . . . . . . . . . . . . . . . . . 198
Serial communication when the connected station is Q series-compatible C24 (2) . . . . . . . . . . . . . . . . . . . . . 201
Serial communication when the connected station is L series-compatible C24 (1). . . . . . . . . . . . . . . . . . . . . . 203
Serial communication when the connected station is L series-compatible C24 (2). . . . . . . . . . . . . . . . . . . . . . 206
Serial communication when the connected station is FX extended port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
10.2 Ethernet Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Ethernet communication when the connected station is R series-compatible E71 (TCP). . . . . . . . . . . . . . . . . 210
Ethernet communication when the connected station is R series-compatible E71 (UDP) . . . . . . . . . . . . . . . . 213
Ethernet communication when the connected station is Q series-compatible E71 (TCP) . . . . . . . . . . . . . . . . 216
Ethernet communication when the connected station is Q series-compatible E71 (UDP) . . . . . . . . . . . . . . . . 219
Ethernet communication when the connected station is L series-compatible E71 (TCP) . . . . . . . . . . . . . . . . . 222
Ethernet communication when the connected station is L series-compatible E71 (UDP) . . . . . . . . . . . . . . . . . 225
Ethernet communication when the connected station is an RCPU (TCP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Ethernet communication when the connected station is an RCPU (UDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Ethernet communication when the connected station is an LHCPU (TCP). . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Ethernet communication when the connected station is an LHCPU (UDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Ethernet communication when the connected station is an FX5CPU (TCP). . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Ethernet communication when the connected station is an FX5CPU (UDP) . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Ethernet communication when the connected station is a built-in Ethernet port QCPU (TCP) . . . . . . . . . . . . . 242
Ethernet communication when the connected station is a built-in Ethernet port QCPU (UDP). . . . . . . . . . . . . 246
Ethernet communication when the connected station is a built-in Ethernet port LCPU (TCP) . . . . . . . . . . . . . 250
Ethernet communication when the connected station is a built-in Ethernet port LCPU (UDP) . . . . . . . . . . . . . 253
Ethernet communication when the connected station is a Ethernet adapter module (TCP) . . . . . . . . . . . . . . . 256
Ethernet communication when the connected station is a Ethernet adapter module (UDP). . . . . . . . . . . . . . . 260
Ethernet communication when the connected station is an Ethernet adapter (TCP) (1). . . . . . . . . . . . . . . . . . 264
Ethernet communication when the connected station is an Ethernet adapter (TCP) (2). . . . . . . . . . . . . . . . . . 265
7
Ethernet communication when the connected station is an Ethernet adapter (UDP) (1) . . . . . . . . . . . . . . . . . 267
Ethernet communication when the connected station is a robot controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Ethernet communication when the connected station is a CC-Link IE TSN module (TCP) . . . . . . . . . . . . . . . 273
Ethernet communication when the connected station is a CC-Link IE TSN module (UDP) . . . . . . . . . . . . . . . 276
10.3 CPU COM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
CPU COM communication when the connected station is an FX5CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
CPU COM communication when the connected station is a QCPU (Q mode) . . . . . . . . . . . . . . . . . . . . . . . . . 281
CPU COM communication when the connected station is an LCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
CPU COM communication when the connected station is a Q motion CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . 287
CPU COM communication when the connected station is an FXCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
CPU COM communication when the connected station is an inverter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
CPU COM communication when the connected station is a robot controller . . . . . . . . . . . . . . . . . . . . . . . . . . 292
10.4 CPU USB Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
CPU USB communication when the connected station is an RCPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
CPU USB communication when the connected station is an R motion CPU . . . . . . . . . . . . . . . . . . . . . . . . . . 296
CPU USB communication when the connected station is an LHCPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
CPU USB communication when the connected station is an FX5CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
CPU USB communication when the connected station is a QCPU (Q mode) . . . . . . . . . . . . . . . . . . . . . . . . . 302
CPU USB communication when the connected station is an LCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
CPU USB communication when the connected station is a QSCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
CPU USB communication when the connected station is a Q motion CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
CPU USB communication when the connected station is an FXCPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
CPU USB communication when the connected station is an inverter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
CPU USB communication when the connected station is a robot controller . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
10.5 MELSECNET/H Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
10.6 CC-Link IE Controller Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
CC-Link IE Controller Network communication when the connected station is an RCPU. . . . . . . . . . . . . . . . . 318
CC-Link IE Controller Network communication when the connected station is a module supporting Q series. 320
10.7 CC-Link IE Field Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
CC-Link IE Field Network communication when the connected station is an RCPU . . . . . . . . . . . . . . . . . . . . 323
CC-Link IE Field Network communication when the connected station is a module supporting QCPU (Q mode) or
LCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
10.8 CC-Link Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
CC-Link communication when the connected station is an RCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
CC-Link communication when the connected station is an LCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
CC-Link communication when the connected station is a module supporting Q series . . . . . . . . . . . . . . . . . . 332
10.9 CC-Link System RS-232 Interface Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
10.10 GX Simulator2 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
10.11 GX Simulator3 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
10.12 MT Simulator2 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
10.13 GOT Gateway Device Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
10.14 GOT Transparent Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Personal computer side port: USB, GOT2000 side port: USB, CPU side port: Direct connection (1). . . . . . . . 340
Personal computer side port: USB, GOT2000 side port: USB, CPU side port: Bus connection . . . . . . . . . . . . 349
Personal computer side port: USB, GOT2000 side port: USB, CPU side port: Serial communication module (1) .
352
8
355
357
359
361
CONTENTS
364
Personal computer side port: Serial, GOT2000 side port: Serial, CPU side port: R series-compatible E71 . . . 366
Personal computer side port: USB, GOT2000 side port: USB, CPU side port: R series-compatible E71. . . . . 369
Personal computer side port: USB, GOT2000 side port: USB, CPU side port: Q series-compatible E71 . . . . 372
Personal computer side port: USB, GOT2000 side port: USB, CPU side port: L series-compatible E71 . . . . . 375
Personal computer side port: USB, GOT2000 side port: USB, CPU side port: Ethernet port (1) . . . . . . . . . . . 378
Personal computer side port: USB, GOT2000 side port: USB, CPU side port: Ethernet adapter module . . . . 390
Personal computer side port: USB, GOT2000 side port: USB, CPU side port: Ethernet adapter/module . . . . 394
Personal computer side port: USB, GOT2000 side port: USB, CPU side port: Ethernet adapter . . . . . . . . . . . 396
Personal computer side port: Ethernet board, GOT2000 port: Ethernet port, CPU side port: Serial (1) . . . . . . 398
Personal computer side port: Ethernet board, GOT2000 side port: Ethernet port, CPU side port: Serial communi-
cation module (1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
cation module (2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
cation module (3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Personal computer side port: Ethernet board, GOT2000 side port: Ethernet port, CPU side port: Bus connection
416
Personal computer side port: Ethernet board, GOT2000 port: Ethernet port, CPU side port: Ethernet port. . . 419
Personal computer side port: Ethernet board, GOT2000 port: Ethernet port, CPU side port: Q series-compatible
E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
CHAPTER 11 FUNCTIONS 423

11.1 Programming Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
11.2 Function List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
11.3 Details of Functions (For Act Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Open (Opening communication line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Close (Closing communication line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
ReadDeviceBlock (Reading devices in batch). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
WriteDeviceBlock (Writing devices in batch) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
ReadDeviceRandom (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
WriteDeviceRandom (Writing devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
SetDevice (Setting device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
GetDevice (Acquiring device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
ReadBuffer (Reading data from buffer memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
9
WriteBuffer (Writing data to buffer memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
GetClockData (Reading clock data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
SetClockData (Writing clock data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
GetCpuType (Reading programmable controller CPU model) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
SetCpuStatus (Remote control). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
EntryDeviceStatus (Registering devices for status monitoring). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
FreeDeviceStatus (Deregistering devices for status monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
OnDeviceStatus (Event notification) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
ReadDeviceBlock2 (Reading devices in batch). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
WriteDeviceBlock2 (Writing devices in batch) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
ReadDeviceRandom2 (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
WriteDeviceRandom2 (Writing devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
SetDevice2 (Setting device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
GetDevice2 (Acquiring device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
GetErrorMessage(Acquiring error description and corrective action) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
11.4 Details of Functions (For Act Control (Logging File Transfer)). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
ReadFirstFile (Searching for a file/directory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
ReadNextFile (Searching for a file/directory). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
ReadClose (Ending the search) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
GetFile (Transferring logging files) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
11.5 Details of Functions (For .Net Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
ReadDeviceBlock (Reading devices in batch). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
WriteDeviceBlock (Writing devices in batch) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
ReadDeviceRandom (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
WriteDeviceRandom (Writing devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
SetDevice (Setting device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
GetDevice (Acquiring device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
ReadBuffer (Reading data from buffer memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
WriteBuffer (Writing data to buffer memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
GetClockData (Reading clock data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
SetClockData (Writing clock data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
GetCpuType (Reading programmable controller CPU model) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
SetCpuStatus (Remote control). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
EntryDeviceStatus (Registering devices for status monitoring). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
FreeDeviceStatus (Deregistering devices for status monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
OnDeviceStatus (Event notification) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
ReadDeviceBlock2 (Reading devices in batch). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
WriteDeviceBlock2 (Writing devices in batch) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
ReadDeviceRandom2 (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
WriteDeviceRandom2 (Writing devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
SetDevice2 (Setting device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
GetDevice2 (Acquiring device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
Dispose (release memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
CHAPTER 12 SAMPLE PROGRAMS 576

12.1 Visual Basic.NET, Visual C#, Visual C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
10
Act_2019.sln, Dot_2019.sln. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
ActDatalogging_2019.sln. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
12.2 VBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
For Access (ActTest.accdb,ActTest64.accdb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
For Excel (ActUtlType.xlsm, ActUtlType64.xlsm, ActProgType.xlsm, and ActProgType64.xlsm) . . . . . . . . . . . 586
CHAPTER 13 ERROR CODES 588

13.1 Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
13.2 Error Codes Returned by CPUs, Modules, and Network Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
CONTENTS
13.3 HRESULT Type Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
13.4 Error Codes Displayed on Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
APPENDIX 618
Appendix 1 Changes from Previous Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Appendix 2 Concept of Routing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Appendix 3 RS-232 Cable Wiring Examples for Serial Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
For Q Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
For FX Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Appendix 4 Multi-CPU System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Appendix 5 The Number of Mountable Network Modules for Q00UJCPU, Q00UCPU, and Q01UCPU. . . . . . . . 625
Appendix 6 Compatibility with Redundant CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
For RnPCPU (redundant mode) and RnPSFCPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
For QnPRH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Appendix 7 Character Strings that cannot be Used for Label Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Appendix 8 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Performance of MX Component (Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Performance of the Label Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
Performance of the Label Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Appendix 9 Installing a USB Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Installing a USB driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Appendix 10Programing Examples for Monitoring Word Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Appendix 11 Time-Out Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Communication retries at time-out error occurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Communication retries at receive data error occurrence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Time-out errors at fixed time in the Act control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Appendix 12Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
When a header file is not created properly at the time of pasting a control to a form with Visual C++ . . . . . . . 649
When an error occurs in the setting for using controls in Visual Studio .NET . . . . . . . . . . . . . . . . . . . . . . . . . . 650
When a link error occurs in creating a user program in Visual C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
When an unstart error occurs during communication with GX Simulator3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Appendix 13Differences with previous version of MX Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Comparison with MX Component Version 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
FUNCTION INDEX 658
REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .660
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .661
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .662
11
RELEVANT MANUALS
Manual name [manual number] Description Available
form
MX Component Version 5 Reference Manual Operation method, programming procedures, and error codes of MX e-Manual
[SH-082395ENG] (this manual) Component Version 5 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.
12
GENERIC TERMS AND ABBREVIATIONS
Unless otherwise specified, this manual uses the following generic terms and abbreviations.
Term Description
AJ65BT-R2N module An abbreviation for AJ65BT-R2N CC-Link system RS-232 interface module
CC-Link IE TSN module Another term for RJ71GN11-T2
CC-Link IE Controller Network A generic term for Q80BD-J71GP21-SX, Q80BD-J71GP21S-SX, and NZ81GP21-SX
board An abbreviation for CC-Link IE Controller Network interface board
CC-Link IE Field Network board An abbreviation for Q81BD-J71GF11-T2 CC-Link IE Field Network interface board
CC-Link Ver.2 board A generic term for Q80BD-J61BT11N and Q81BD-J61BT11
An abbreviation for CC-Link system master/local interface board
C Controller module A generic term for R12CCPU-V, Q12DCCPU-V (Basic mode), Q12DCCPU-V (Extended mode), Q24DHCCPU-V,
Q24DHCCPU-LS, Q24DHCCPU-VG, and Q26DHCCPU-LS
Ethernet adapter/module A generic term for FX3U-ENET-ADP, FX3U-ENET(-L), FX5-ENET, and FX5-ENET/IP
Ethernet adapter module An abbreviation for NZ2GF-ETB CC-Link IE Field Network Ethernet adapter module
Built-in Ethernet port QCPU A generic term for Q03UDE, Q03UDV, Q04UDEH, Q04UDV, Q04UDPV, Q06UDEH, Q06UDV, Q06UDPV, Q10UDEH,
Q13UDEH, Q13UDV, Q13UDPV, Q20UDEH, Q26UDEH, Q26UDV, Q26UDPV, Q50UDEH, and Q100UDEH
Ethernet module A generic term for R series-compatible E71, Q series-compatible E71, and L series-compatible E71
Built-in Ethernet CPU A generic term for RCPU, LHCPU, built-in Ethernet port QCPU, LCPU and FX5CPU
FX5CPU A generic term for FX5U, FX5UC, and FX5UJ
FXCPU A generic term for FX3S, FX3G, FX3GC, FX3U, and FX3UC
FX extended port A generic term for FX3G-485-BD and FX3U-485-BD
GOT An abbreviation for Graphic Operation Terminal
GOT2000 An abbreviation for Graphic Operation Terminal GOT2000 series
GT SoftGOT A generic term for GT SoftGOT2000 Version1, GT SoftGOT1000 Version2, and GT SoftGOT1000 Version3
LCPU A generic term for L02S, L02, L06, L26, and L26-BT
LHCPU A generic term for L04H, L08H, and L16H
L series-compatible C24 A generic term for LJ71C24 and LJ71C24-R2
L series-compatible E71 Another term for LJ71E71
MELSECNET/H board A generic term for Q80BD-J71LP21-25, Q80BD-J71LP21S-25, Q81BD-J71LP21-25, Q80BD-J71LP21G, and Q80BD-
J71BR11
An abbreviation for MELSECNET/H interface board
Q12DCCPU-V (Extended mode) Status that Q12DCCPU-V is initialized with the extended mode
For Q12DCCPU-V (Extended mode), refer to the following:
MELSEC-Q C Controller Module User's Manual
Q12DCCPU-V (Basic mode) Status that Q12DCCPU-V is initialized with the basic mode
For Q12DCCPU-V (Basic mode), refer to the following:
C Controller Module User's Manual (Hardware Design, Function Explanation)
QCCPU A generic term for Q12DCCPU-V (Basic mode), Q12DCCPU-V (Extended mode), Q24DHCCPU-V, Q24DHCCPU-LS,
Q24DHCCPU-VG, and Q26DHCCPU-LS
QCPU (Q mode) A generic term for Q00UJ, Q00U, Q01U, Q02U, Q03UD, Q03UDE, Q03UDV, Q04UDH, Q04UDEH, Q04UDV, Q04UDPV,
Q06UDH, Q06UDEH, Q06UDV, Q06UDPV, Q10UDH, Q10UDEH, Q12PRH, Q13UDH, Q13UDEH, Q13UDV, Q13UDPV,
Q20UDH, Q20UDEH, Q25PRH, Q26UDH, Q26UDEH, Q26UDV, Q26UDPV, Q50UDEH, and Q100UDEH
QnPRH A generic term for Q12PRH and Q25PRH
QSCPU An abbreviation for a safety CPU module (QS001CPU)
Q series-compatible C24 A generic term for QJ71C24, QJ71C24N, QJ71C24N-R2, and QJ71C24N-R4
Q series-compatible E71 A generic term for QJ71E71, QJ71E71-B2, QJ71E71-B5, and QJ71E71-100
Q motion CPU A generic term for Q172D, Q173D, Q172DS, and Q173DS
RCCPU Another term for R12CCPU-V
RCPU A generic term for RnCPU, RnENCPU, RnPCPU, RnPSFCPU, RnSFCPU
RnCPU A generic term for R00, R01, R02, R04, R08, R16, R32, and R120
RnENCPU A generic term for R04EN, R08EN, R16EN, R32EN and R120EN
RnPCPU A generic term for R08P, R16P, R32P and R120P
RnPSFCPU A generic term for R08PSF, R16PSF, R32PSF, and R120PSF
RnSFCPU A generic term for R08SF, R16SF, R32SF and R120SF
R series-compatible C24 A generic term for RJ71C24, RJ71C24-R2, and RJ71C24-R4
13
Term Description
R series-compatible E71 Another term for RJ71EN71
R motion CPU A generic term for R16MT and R32MT
Inverter An abbreviation for FREQROL-A800 series
Programmable controller CPU A generic term for RCPU, LHCPU, QCPU (Q mode), LCPU, FX5CPU, FXCPU, R motion CPU, Q motion CPU, QSCPU,
and C Controller module
Serial communication module A generic term for R series-compatible C24, Q series-compatible C24, L series-compatible C24, and FX extended port
Redundant CPU A generic term for QnPRH, RnPCPU, and RnPSFCPU
Redundant type extension base An abbreviation for Q65WRB extension base unit for redundant system
unit
Robot controller A abbreviation for CR750-D/CRnD-700 series
14
PART 2
PART 1 FUNDAMENTALS AND
CREATING PROCEDURE
This part explains the fundamentals of MX Component and creating procedure.
1 FUNDAMENTALS OF MX Component
2 SYSTEM CONFIGURATIONS
3 USER APPLICATION CREATING PROCEDURES
4 ADDING CONTROLS TO USER PROGRAM
5 COMMUNICATION SETTING
6 COMMUNICATION SETTING EXAMPLES (UTILITY SETTING TYPE)
7 PROGRAMMING
15
1.1 Before Using this Product

MX Component is a library that realizes easy communication from a personal computer to a programmable controller.
By using the controls provided by MX Component, device information can be acquired from a programmable controller and an
application can be developed.
In addition, a communication route to a programmable controller can be set in detail by using the utilities.
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.
Using MX Component
Support of a wide range of communication routes for programmable controller

A wide range of communication routes to a programmable controller are supported to enable the user to configure a system
as desired.
Substantial improvement in user's development efficiency

When creating a user program, select either the utility setting type or program setting type. (Page 38 Selecting a
Communication Setting Method)
In case of utility settings type, the wizard type communication settings utility is provided.
By simply setting dialog-based communication settings on the screen, communication settings to access a programmable
controller CPU to communicate with can be realized.
Once the communication settings are set, stations can be accessed by merely specifying the logical station number of the
programmable controller CPU stored in Communication Settings Utility.
Save and read of communication settings

MX Component features the functions to save and read the communication settings set in Communication Settings Utility.
The set data can easily be moved from a personal computer used for development to that used for operation.
MX Component must be installed in both of the computers.
Communication setting
Personal computer Personal computer
data is 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
16 1.1 Before Using this Product
Create programs with labels
Programs can be created without considering device numbers by using the label function.
1
Devices can be read/written by using the label 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.
Monitor devices and change their data

By utilizing PLC Monitor Utility, the status of a specified device can be monitored and its data can 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 connected intelligent or

special function module can be read/written!
MX
Component
Access to buffer memory
1.1 Before Using this Product 17
Read/write of programmable controller CPU clock data
The clock data of a programmable controller CPU connected to a personal computer can be read/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

Communication with various simulators (GX Simulator2, GX Simulator3, and MT Simulator2) can be performed.
By using the simulation function, debugging can be performed on a single personal computer without connecting with a
programmable controller.
This function is not supported by QSCPU.
MX
Component
Personal computer Programmable controller
Programmable controller is
not required to be connected.
A wide variety of programming languages supported
MX Component supports Visual Basic .NET, Visual C++, Visual C#, and VBA.
1
■ 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.
Device data of a programmable controller can be logged and device data can be sampled/saved in real time.
<Excel> <Access>
Support multi-CPU system of QCPU (Q mode)

Setting Communication Settings Utility or control properties enables access to the multi-CPU system of QCPU (Q mode).
Transfer logging files to a personal computer

A logging file in an SD memory card inserted in an RCPU can be transferred to a personal computer.
For controls for transferring logging files, refer to the following:
Page 21 Act Control (logging file transfer)
1.1 Before Using this Product 19
Accessibility to gateway devices of GOT
The device data of a 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

is read/written with GOT.
Mitsubishi Company A Company B

programmable programmable programmable
controller controller controller
Support GOT transparent communication

Using the GOT transparent function, a programmable controller CPU can be accessed via GOT.
MX
Component
GOT
Reduction of error description search time

By using the 'ActSupportMsg' which is a control for the troubleshooting function, the error description and corrective action
can be displayed within a user program by only specifying the error code.
Therefore, checking error description or corrective action on a 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.2 Types of Control
This section explains controls provided by MX Component.
1
Controls shown in this section are used to create user programs to communicate with a CPU module. By using these controls,
communication with a CPU module can be realized without being aware of the hardware and the communication protocol.
There are the following three types of controls provided by MX Component.
• Act Control
• Act Control (logging file transfer)
• .Net Control
The following table shows each control.
Control list
Act control
The following table shows the ActiveX Controls provided by MX Component.
Data can be accessed using devices.
Control name Application Supported
language
32-bit ActUtlType A utility setting type control. Visual C#
64-bit ActUtlType64 It is used to create a user program by using Communication Settings Utility. Visual Basic
.NET
32-bit ActProgType A program setting type control.*1 Visual C++
It is used to create a user program without using Communication Settings Utility. VBA
64-bit ActProgType64
32-bit ActSupportMsg Common control for a utility setting type and program setting type.
Used for the troubleshooting function.
64-bit ActSupportMsg64
*1 Not applicable to inverter communication/robot controller communication.
Act Control (logging file transfer)

The following table shows the ActiveX Controls for transferring logging files provided by MX Component.
Do not use the controls while the logging function of a CPU module is in operation.
language
32-bit ActUtlDataLogging A utility setting type control. Visual C#
64-bit ActUtlDataLogging64 It is used to transfer a logging file. Visual Basic
It operates with a logical station number created by using Communication Settings Utility. .NET
Visual C++
32-bit ActProgDataLogging A program setting type control.
It is used to transfer a logging file.
64-bit ActProgDataLogging64
It operates with the property of the control.
.Net control
The following table shows the .Net Controls provided by MX Component.
Data can be accessed using labels.
language
32-bit DotUtlType A utility setting type control. Visual C#
It is used to create a user program by using Communication Settings Utility. Visual Basic
64-bit DotUtlType64
.NET
1.2 Types of Control 21
1.3 Types of Utility
The following are the utilities used in MX Component.
Item Description Reference
Communication Settings Utility Sets the communication settings in the wizard format. Page 52 Setting with Utilities
Label Utility Registers/utilizes the system labels. Page 111 Creating a Label
With Label Utility
PLC Monitor Utility Sets a connection destination by using a logical station number, and monitors the Page 139 Checking a value
devices and buffer memories of a programmable controller. using PLC Monitor Utility
Administrator authority
When Label Utility is executed, the status is switched to the administrator authority automatically.
When executing Communication Settings 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 operate as "standard user" in the default setting.
To execute programs with administrator authority, specify "Run as administrator."
■ When user account control (UAC) is disabled

Programs can be executed by login user.
■ Warning messages in Windows

When executing a utility as an administrator, a warning message appears.
To execute a utility as an administrator at all times, select the checkbox of "Run this program as an
administrator" in the [Compatibility] tab of [Property].
22 1.3 Types of Utility
■ When MX Component is operated by a user without Administrator's authority.
Note that the following restrictions are applied when MX Component is operated by a user without Administrator's authority.
Item Restrictions 1
Communication Settings 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
*1 If the following error message appears, start up or close the utility as a user with Administrator's authority.
This operation enables a user without Administrator's authority to start up the utility.
1.3 Types of Utility 23
This chapter explains the system configuration of MX Component such as the operating environment, communication routes,
and available devices.
2.1 Operating Environment

Item Description
Personal computer Personal computer where Microsoft Windows operates
• CPU: Processor 1.6 GHz and 2 core or more
• Required memory: 2 GB or more recommended
Available hard disk capacity • For installation: 1.4 GB or more free hard disk capacity
• For operation: 512 MB or more free virtual memory capacity
Monitor Resolution 1024  768 pixels or higher
OS • Windows 10 (Home, Pro, Enterprise, Education, IoT Enterprise 2016 LTSB*1)
(English version)
(32-bit version/64-bit version)
Programming language *2*3 • Visual Basic.Net: Microsoft Visual Studio 2019
(English version) • Visual C#: Microsoft Visual Studio 2019
(32-bit version/64-bit version) • Visual C++: Microsoft Visual Studio 2019
• VBA: Microsoft Excel 2019, Microsoft Excel for Microsoft 365*1*5, Microsoft Access 2019, Microsoft Access for
Microsoft 365*1*5
Framework*4 .NET Framework 3.5/4.5.2/4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2/4.8
*1 64-bit version only

*2 User programs created in the English environment are applicable to the English environment only, cannot be used in the other
environment.
*3 Visual C++ and VBA do not support access with labels.
*4 .Net Core and .Net 5 are not supported.
*5 The operation of this product has been confirmed with the version 2201 (Build 14827.20192). This product does not run with a version
earlier than this version.
For Windows 10, if .NET Framework 3.5 (including .NET 2.0 and 3.0) or .NET Framework 4.6 Advanced Services is invalid, it needs to be valid. Refer to
TECHNICAL BULLETIN No. FA-D-0207.
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 Touch or Touch
• Modern UI
• Client Hyper-V
• Tablet mode
• Virtual Desktops
• Windows hibernate or standby
• Unified Write Filter
In the following cases, 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.).
• The resolution of the screen is changed in operation.
• Windows theme is changed in operation.
• The multi-display is set.
If the Windows firewall setting is enabled, the "Find Module function" and "Direct connection function" may not operate correctly. Disable the Windows firewall
setting.
In this product, the period (.) is used as the symbol of the decimal point. Regardless of the setting of "Decimal symbol" on the control panel, use the period when
enter the decimal point.
Precautions
• A communication error may occur when communicating with a programmable controller CPU after setting the resume
function, suspend setting, power-saving function, and/or standby mode of a personal computer.
Therefore, when communicating with the programmable controller CPU, do not set the above functions.
• Surrogate pair characters and environment dependent characters are not available in MX Component utilities.
• MX Component cannot be used from a Windows service application.
24 2.1 Operating Environment
2.2 Supported Communication Routes
This section shows the supported communication routes by MX Component.
Communication route Description Reference
Serial communication To perform communication with a programmable controller CPU using a
serial communication module.
Page 31 Serial communication
2
Ethernet communication To perform communication by connecting a personal computer to an Page 32 Ethernet communication
Ethernet module or a built-in Ethernet CPU.
CPU COM communication To perform communication by connecting a personal computer to an RS- Page 32 CPU COM
232 or RS-422 connector of a programmable controller CPU. communication
CPU USB communication To perform communication by connecting a personal computer to a USB Page 35 CPU USB communication
connector of a programmable controller CPU.
MELSECNET/H communication*1*2 To perform communication with a programmable controller CPU using a Page 35 MELSECNET/H
MELSECNET/H board. communication
CC-Link IE Controller Network To perform communication with a programmable controller CPU using a Page 35 CC-Link IE Controller
communication*1*2 CC-Link IE Controller Network board. Network communication
CC-Link IE Field Network communication*1*2 To perform communication with a programmable controller CPU using a Page 35 CC-Link IE Field Network
CC-Link IE Field Network board. communication
CC-Link communication*1*2 To perform communication with a programmable controller CPU using a Page 35 CC-Link communication
CC-Link Ver.2 board.
CC-Link system RS-232 interface To perform communication with a programmable controller CPU using Page 36 CC-Link system RS-232
communication an AJ65BT-R2N module. interface communication
GX Simulator2 communication To perform communication using the simulation function of GX Works2. Page 36 GX Simulator2
communication
GX Simulator3 communication To perform communication using the simulation function of GX Works3. Page 36 GX Simulator3
communication
MT Simulator2 communication To perform communication using the simulation function of MT Page 36 MT Simulator2
Developer2. communication
GOT gateway device communication To perform communication with a programmable controller CPU and a Page 36 GOT gateway device
third-party programmable controller using the gateway functions of GOT. communication
GOT transparent communication To perform communication with a programmable controller CPU using Page 36 GOT transparent
the GOT transparent function. communication
Inverter COM communication To perform communication by connecting an inverter to a COM port of a Page 36 Inverter (COM/USB)
personal computer. communication
Inverter USB communication To perform communication by connecting an inverter to a USB port of a
personal computer.
Robot controller COM communication*2 To perform communication by connecting a robot controller to a COM Page 36 Robot controller(COM/
port of a personal computer. USB/Ethernet) communication
Robot controller USB communication*2 To perform communication by connecting a robot controller to a USB
port of a personal computer.
Robot controller Ethernet Communication*2 To perform communication by connecting a robot controller and a
personal computer to Ethernet.
*1 Not supported when using Windows 10 Education.

*2 Not supported when using Windows 10 IoT Enterprise 2016 LTSB.
2.2 Supported Communication Routes 25
2.3 System Configuration List
For details on the available cables and considerations for communication, refer to the manual of each module.
System configuration examples of each communication route

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)
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
(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
communication CC-Link CC-Link module
CC-Link Ver.2 board
CC-Link system
RS-232 AJ65BT-R2N
RS-232 interface CC-Link
module CC-Link module
Communication
26 2.3 System Configuration List
Personal computer
GX Simulator2
communication
Simulation function of GX Works2
(GX Simulator2) 2
GX Simulator3 Simulation function of GX Works3
communication (GX Simulator3)
MT Simulator2 Simulation function of MT Developer2

communication (MT Simulator2)
GOT Gateway Device Ethernet GOT

communication
Ethernet board
GOT transparent USB, RS-232 RS-232 RCPU, QCPU (Q mode),

communication LCPU, C Controller module,
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
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
2.3 System Configuration List 27
2.4 Available Module List
The following shows available models in MX Component.
Programmable controller CPU list

The following table shows available programmable controller CPUs.
Series Module model
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) Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU, Q03UDCPU, Q03UDECPU, Q03UDVCPU, Q04UDHCPU, Q04UDEHCPU,
Q04UDVCPU, Q04UDPVCPU, Q06UDHCPU, Q06UDEHCPU, Q06UDVCPU, Q06UDPVCPU, Q10UDHCPU, Q10UDEHCPU,
Q12PRHCPU, Q13UDHCPU, Q13UDEHCPU, Q13UDVCPU, Q13UDPVCPU, Q20UDHCPU, Q20UDEHCPU, Q25PRHCPU,
Q26UDHCPU, Q26UDEHCPU, Q26UDVCPU, Q26UDPVCPU, 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 Q172DCPU, Q173DCPU, Q172DSCPU, Q173DSCPU
FXCPU FX3SCPU, FX3GCPU, FX3GCCPU, FX3UCPU, FX3UCCPU
*1 The first five digits of the serial number is 12042 or higher are supported.
28 2.4 Available Module List
Considerations
■ RnSFCPU
In order to protect the safety programmable controller system, a function to write data to the buffer memory or safety devices
in safety mode cannot be executed.
■ FX5CPU 2
• 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.
■ Q00UJ/Q00U/Q01U/Q02UCPU
"Serial communication function compatible CPU" indicates Q00UJ/Q00U/Q01U/Q02UCPU.
When the following conditions are all satisfied, communication between a personal computer and a 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 the personal computer with that of the serial
communication function compatible CPU.
■ QSCPU
In order to protect the safety programmable controller system, a function to write data to the buffer memory or safety devices
in safety mode cannot be executed.
■ Built-in Ethernet CPU

• When resetting a 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.
■ 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 programmable controller CPUs, an error is returned when 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.)
2.4 Available Module List 29
Module list
The following table shows the modules and boards that are available for communication with a programmable controller CPU
in each communication type.
Communication type Category Module model
Serial communication R series-compatible C24 RJ71C24, RJ71C24-R2, RJ71C24-R4
Q series-compatible C24 QJ71C24, QJ71C24N, Q71C24N-R2, QJ71C24N-R4
L series-compatible C24 LJ71C24, LJ71C24-R2
FX extended port FX3G-485-BD, FX3U-485-BD
Ethernet communication R series-compatible E71 RJ71EN71
Q series-compatible E71 QJ71E71, QJ71E71-B2, QJ71E71-B5, QJ71E71-100
L series-compatible E71 LJ71E71
Ethernet adapter module NZ2GF-ETB
Ethernet adapter/module FX3U-ENET-ADP, FX3U-ENET(-L), FX5-ENET, FX5-ENET/IP
MELSECNET/H communication MELSECNET/H module RJ71LP21
QJ71LP21
MELSECNET/H board*1 Q80BD-J71LP21-25, Q80BD-J71LP21S-25, Q81BD-J71LP21-25,
Q80BD-J71LP21G, Q80BD-J71BR11
CC-Link communication CC-Link module RJ61BT11
QJ61BT11N
LJ61BT11
FX3U-64CCL
*2
CC-Link Ver.2 board Q80BD-J61BT11N, Q81BD-J61BT11
CC-Link system RS-232 interface AJ65BT-R2N module AJ65BT-R2N
communication
CC-Link IE Controller Network CC-Link IE Controller Network module RJ71GP21-SX
communication
QJ71GP21S-SX, QJ71GP21-SX
LJ71GP21-SX
CC-Link IE Controller Network board*3 Q80BD-J71GP21-SX, Q80BD-J71GP21S-SX, NZ81GP21-SX
CC-Link IE Field Network CC-Link IE Field Network module RJ71GF11-T2
communication
QJ71GF11-T2
LJ71GF11-T2
CC-Link IE Field Network board*4 Q81BD-J71GF11-T2
CC-Link IE TSN communication CC-Link IE TSN module RJ71GN11-T2
GOT transparent communication GOT2000 GT27, GT25
Inverter communication A800 
Robot controller communication CR750 CR750-DCR751-D
CRnD-700 CR1DA-7xx, CR2DA-7xx, CR3DA-7xx
*1 Applicable driver: SW0DNC-MNETH-B (Version 30G) or later

*2 Applicable driver: SW1DNC-CCBD2-B (Version 1.19V) or later
*3 Applicable driver: SW1DNC-MNETG-B (Version 1.22Y) or later
*4 Applicable driver: SW1DNC-CCIEF-B (Version 1.10L) or later
30 2.4 Available Module List
2.5 Details on the Communication Routes
This section explains details and the considerations for each communication route.
For the method for connecting to a serial communication module, refer to the manual of the serial communication module.
2
■ Serial communication
• On any serial communication modules, remote "PAUSE" operation will result in an error for all connections.
• An FX extended port is required when performing the serial communication using FX3S, FX3G(C), or FX3U(C)CPU.
■ About connection of applicable modules

When accessing a programmable controller CPU from a personal computer via serial communication modules, note that
modules that can be connected to the personal computer directly 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
Module 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)   
QJ71C24N-R2 RS-232(CH1)   
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)   
FX3G-485-BD RS-422/485   
FX3U-485-BD
2.5 Details on the Communication Routes 31
Ethernet communication
• For the method for connecting to an Ethernet module, refer to the manual of the Ethernet communication module.
• For the FX series Ethernet module, refer to the user's manuals for the FX series.
• For the method for connecting to an Ethernet Built-in CPU, refer to the manual of the Ethernet Built-in CPU.
• For the method for connecting to an Ethernet adapter module, refer to the manual of the Ethernet adapter module.
• For the method for connecting to an Ethernet adapter, refer to the manual of the Ethernet adapter.
• For the method for connecting to a CC-Link IE TSN module, refer to the manual of the CC-Link IE TSN module.
CPU COM communication

■ Cable for connection of an QCPU (Q mode) and LCPU
The following cable is required for communications between the personal computer and of QCPU (Q mode).
RS-232 cable
QC30R2 (Personal computer connector: 9-pin D-sub connector)
RS-232 adaptor (L6ADP-R2) is required when connecting to the LCPU.
■ Cable for connection of an 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 an FXCPU

The following cable is required for communications between the personal computer and of FXCPU.
Personal computer side (RS-232 cable) RS-232/RS-422 converter Programmable controller CPU side (RS-
422 cable)
• F2-232CAB (25-pin D-sub  25-pin D-sub) • FX-232AW FX-422CAB0 (1.5m)
• F2-232CAB-1 (9-pin D-sub  25-pin D-sub) • FX-232AWC
• F2-232CAB-2 (Half pitch  25-pin D-sub) • FX-232AWC-H
• AC30N2A (25-pin  25-pin)
■ Cables for connection of Q motion CPU

For communications between the personal computer and Q motion CPU, use the cables as indicated below.
Page 32 Cable for connection of an QCPU (Q mode) and LCPU
■ Converter/Cable (FXCPU compatible) for connecting to a USB on personal computer

System configuration
• 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.
32 2.5 Details on the Communication Routes
■ USB cables and function expansion boards (compatible with FX3U, FX3UCCPU)
System configuration
• FX3U-USB-BD
• USB cable (included)
• Using a USB cable for the first time 2

Install the driver from the CD-ROM included with FX-USB-AW and FX3U-USB-BD.
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:
GX Works2 Version 1 Operating Manual (Common)
■ USB cables (compatible with FX3S, FX3G, and FX3GCCPU)

For details on 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

Install the USB driver. (Page 641 Installing a USB Driver)
■ RS-422 function expansion board for FXCPUs

Series Function expansion board
FX3U, FX3UC (FX3UC-32MT-LT and FX3UC-32MT-LT-2 only) FX3U-422-BD
FX3S, FX3G FX3G-422-BD
• PLC parameter
■ RS-232 cable and function expansion board (special adaptor) for FXCPUs
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
FX3G-CNV-ADP*4 + FX3U-232ADP
FX3S FX3G-232-BD FX-232CAB-1
FX3S-CNV-ADP + FX3U-232ADP
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
FX3S FX3G-232-BD FX-232CAB-2
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
FX3S FX3G-232-BD F2-232CAB-1
*1 For FX3UC series, only FX3UC-32MT-LT and FX3UC-32MT-LT-2 can be used.

*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:
Page 70 FX extended port
*3 FX3GC series cannot be used.
*4 ADP (FX3G-CNV-ADP) for FX3U adapter connection is not required for FX3GC series.
• PLC parameter
CPU USB communication
The following table shows the available USB cables.
Product name Module model
USB cable (USB A type  USB B type) AU230
USB cable (USB A type  USB miniB type) KU-AMB530 2
U2C-M30BK
MR-J3USBCBL3M
GT09-C30USB-5P

Install a USB driver. For the installation method, refer to the following:
Page 641 Installing a USB Driver
For the considerations and restrictions when accessing a programmable controller CPU, refer to the
following:
Page 646 For programmable controller CPU
MELSECNET/H communication
• A MELSECNET/H board can be used.
• Use the communication driver SW0DNC-MNETH-B or later.
The other communication drivers cannot be used.
• For details on 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

• A CC-Link IE Controller Network board can be used.
• Use the communication driver SW1DNC-MNETG-B or later.
each network board.
CC-Link IE Field Network communication

• A CC-Link IE Field Network board can be used.
• Use the communication driver SW1DNC-CCIEF-B or later.
each network board.
CC-Link communication
• A CC-Link Ver.2 board can be used.
• Use the communication driver SW1DNC-CCBD2-B or later.
each network board.
• Use the CC-Link master station module the software version of which is "N" or later.
Modules of software version "M" or earlier do not operate normally.
CC-Link system RS-232 interface communication
• Use the CC-Link master station module the software version of which is "N" or later.
Modules of software version "M" or earlier do not operate normally.
• For details on the communication with an AJ65BT-R2N module, refer to the manual of a CC-Link system RS-232 interface
module.
GX Simulator2 communication
When performing GX Simulator2 communication, use GX Works2.
GX Simulator3 communication
When performing GX Simulator3 communication, use GX Works3.
MT Simulator2 communication
When performing MT Simulator2 communication, use MT Developer2.
This function is supported by a Q motion CPU only.
■ Considerations for performing MT Simulator2 communication

After installing MX Component, install MT Developer2.
GOT gateway device communication

For details on the GOTs which support the gateway function and the settings, refer to the manual of the gateway function for
GOT 2000 series used.
GOT transparent communication

For details on the connection and settings, refer to the connection manuals for GOT 2000 series.
(Mitsubishi Products), (Non-Mitsubishi Products 1), (Non-Mitsubishi Products 2), (Microcomputer, MODBUS/Fieldbus
Products, Peripherals)
Inverter (COM/USB) communication

For the connection cables, refer to the manual of inverter used.
Robot controller(COM/USB/Ethernet) communication

For the connection cables, refer to the following:
 CR750/700/500 series RT ToolBox2 / RT ToolBox2 mini User's Manual
■ Considerations when connecting a robot controller with a USB

For the considerations when connecting a robot controller with a USB, refer to the following manual.
 CR750/700/500 series RT ToolBox2 / RT ToolBox2 mini User's Manual
When connecting a robot controller with a 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.
3 USER APPLICATION CREATING
PROCEDURES
This chapter shows the procedure for creating a user program.
1. Install MX Component
2. Grasp a control to be used.
3. Select the communication setting method

3
4. Create a new user program
5. Add the controls to a user program
6. Set the communication settings
7. Create a program (creating a label, coding, and debugging)
3.1 Installing MX Component

Install MX Component on a personal computer. For the installation method, refer to the following:
 MX Component Version 5 Installation Instructions
Precautions
• When performing overwrite installation, install the software in the same folder where it is installed previously.
• When downloading the installer, save the installer to a directory which does not include any space and execute it.
• When uninstalling MX Component, the item may remain in the start menu. In this case, restart the personal computer.
Checking the Version

The version of MX Component can be checked by using the [Help] menu of each utility.
Operating procedure
Select [Help]  [About].
Opening the manual

e-Manual can be opened by using the [Help] menu of each utility.
Operating procedure
Select [Help]  [Help].

3.1 Installing MX Component 37
3.2 Grasping a Control to be Used
When developing a user program by using MX Component, controls to be used differs depending on the content of the
processing and communication setting method.
Check if the controls are suitable for the contents of development.
Contents of processing Supporte Communication setting Types of control Control name
d (Upper: for 32-bit, lower: for 64-
language bit)
Reading/writing device data VB.Net Set in Communication Settings Utility. Act control ActUtlType
C# ActUtlType64
VC++
Set in a program. ActProgType
VBA ActProgType64
Troubleshooting Use the same control regardless of the ActSupportMsg
communication setting method. ActSupportMsg64
Transferring a logging file Set in Communication Settings Utility. Act Control (logging ActUtlDataLogging
file transfer) ActUtlDataLogging64
Set in a program. ActProgDataLogging
ActProgDataLogging64
Reading/writing label data VB.Net Set in Communication Settings Utility only. .Net control DotUtlType
C# DotUtlType64
For the difference between using Communication Settings Utility and the program as the "communication setting," refer to the
following:
Page 38 Selecting a Communication Setting Method
For the method to incorporate the Act control and .Net control into the development environment, refer to the following:
Page 40 ADDING CONTROLS TO USER PROGRAM
3.3 Selecting a Communication Setting Method

Select either type for the communication setting method (development type), a method to use Communication Settings Utility
(utility setting type) or to use a program (program setting type).
The following table shows the differences between the utility setting type and program setting type.
Development type Feature Specification method in a user Applicable control
program
Utility setting type A user program can be created with Specify the logical station number set • ActUtlType
Communication Settings Utility with Communication Setting Wizard • ActUtlDataLogging
without being aware of the in the property of the Act control and • ActSupportMsg
complicated parameters of each .Net control, or within the user • DotUtlType
communication. Set the program. • ActUtlType64
communication settings using • ActUtlDataLogging64
Communication Setting Wizard. • ActSupportMsg64
Each communication setting is saved • DotUtlType64
in a personal computer by adding a
logical station number.
Program setting type A user program can be created Set this type by entering the • ActProgType
without using Communication properties on the property window of • ActProgDataLogging
Settings Utility. the Act control directly or within the • ActSupportMsg
Communication settings can be user program. • ActProgType64
changed flexibly in the user program. The required settings for the • ActProgDataLogging64
properties differ depending on the Act • ActSupportMsg64
control.

38 3.2 Grasping a Control to be Used
3.4 Adding a Control to a User Program
To develop a user program that uses MX Component, a control of MX Component needs to be added to the user program.
The method to add a control differs depending on the development language and types of control to be used. For details, refer
to the following:
3.5 Creating a New User Program 3

Create a user program according to the development language to be used.
• VBA: Create a file in Excel or Access, and start Visual Basic Editor.
• Visual Basic .NET, Visual C#, or Visual C++: Start Visual Studio, and create a project file.
3.6 Communication Setting

For setting with the utility setting type, refer to the following:
Page 52 Setting with Utilities
For setting with the program setting type, refer to the following:
Page 63 Setting in Programs
3.7 Programming
Create a program to communicate with a program controller by using a property and function of a control.
In addition, create a label used in the program by using a label utility.
When debugging the created user program, a device and buffer memory can be checked easily by using PLC Monitor Utility.
For details, refer to the following:
Page 111 PROGRAMMING

3.4 Adding a Control to a User Program 39
When using the functions and properties of MX Component in a user program, controls need to be added to the user program.
The method to add controls differs depending on the development language and type of the controls.
Development Type of control Using control Details
language
VBA Act control (for 32-bit, for 64-bit) Use a control by creating an object. Page 40 When using a control by
creating an object
Act control (for 32-bit) Use a control by pasting the control to a form. Page 41 When using a control by
pasting a control to a form
Visual Basic .NET Act control (for 32-bit, for 64-bit) Use a control by creating an object. Page 44 When using a control by
Visual C# creating an object
.Net control (for 32-bit, for 64-bit) Use a control by creating an object. Page 44 When using a control by
creating an object
Visual C++ Act control (for 32-bit, for 64-bit) Use a control by creating an object. Page 47 When using a control by
creating an object
4.1 When using VBA

The following shows the setting operation when using VBA.
When using a control by creating an object

Operating procedure
1. Start Visual Basic Editor.
• When using Microsoft Excel 2019: Select [Visual Basic] on the [Developer] tab.
• When using Microsoft Access 2019: Select [Visual Basic] on the [Database Tools] tab.
2. Select "References" on the [Tools] tab of Visual Basic Editor.
3. Select a control of "Development type" to be used (Page 41 Applicable Controls (When using a control by creating
an object)) in the "Available References" screen, and click the [OK] button.

40 4.1 When using VBA
■ Applicable Controls (When using a control by creating an object)
The following table shows applicable controls by the development type.
Development type Applicable control
Utility setting type (for 32-bit) MITSUBISHI ActUtlType Controls Ver1.0
MITSUBISHI ActSupportMsg Controls Ver1.0
Utility setting type (for 64-bit) ActUtlType64 Control
ActSupportMsg64 Control
Program setting type (for 32-bit) MITSUBISHI ActProgType Controls Ver1.0
Program setting type (for 64-bit) ActProgType64 Control
When using a control by pasting a control to a form 4

Operating procedure
1. Add ActiveX control to the screen.
• When using Microsoft Excel 2019: Select in [Insert] on the [Developer] tab.
• When using Microsoft Access 2019: Select [Controls] on the [Form Design] tab  [ActiveX Controls].

4.1 When using VBA 41
2. Select a control of "Development type" to be used (Page 42 Applicable Controls (When pasting a control to a form))
in the "More Controls" screen, and click the [OK] button.
3. Paste the selected Act control to the sheet.
4. Start Visual Basic Editor.

• When using Microsoft Excel 2019: Select [Visual Basic] on the [Developer] tab.
• When using Microsoft Access 2019: Select [View Code] on the [Design] tab.
■ Applicable Controls (When pasting a control to a form)

Utility setting type (for 32-bit) MITSUBISHI ActUtlType Control
MITSUBISHI ActSupportMsg Control
Program setting type (for 32-bit) MITSUBISHI ActProgType Control
MITSUBISHI ActSupportMsg Control

42 4.1 When using VBA
Considerations for using Microsoft Excel
■ When controls cannot be 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 Excel 8.0 folder of the temp folders.

• The location of the 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. 4
3. Restart Excel.
■ Resizing of Act control

Act control can be resized in Excel, however this 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 a following error message appears after pasting the Act control to an Access form and
double-clicking the Act control or selecting the custom control
The following error message appears. 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."

4.1 When using VBA 43
4.2 When using Visual Basic .NET, Visual C#
The following shows the setting operation when using Visual Basic .NET, Visual C#.

Operating procedure
1. Start Visual Studio.
2. Select [Project]  [Add Reference].
3. Add a control of "Development type" to be used (Page 45 Applicable Controls (When using a control by creating an
object)).
• When using Act control: Select a control from "COM" in the "Reference Manager" screen.
• When using .Net control: Select a control from "Extensions" in "Assemblies" in the "Reference Manager" screen.
4. When developing a program by using the program setting type, select [Project]  [Add Existing Item], and add include
files (Page 45 Include file (When using Visual Basic .NET, Visual C# )). The include files are stored in the following
folder at the time of installation.
(User-specified folder)\Act\Include
5. Create an instance of class for each control to be used. (Page 45 Class created for each control)

44 4.2 When using Visual Basic .NET, Visual C#
■ Applicable Controls (When using a control by creating an object)
Development type Type of control Applicable control
Utility setting type (for 32-bit) Act control MITSUBISHI ActUtlType Controls Ver1.0
MITSUBISHI ActUtlDataLogging Controls Ver1.0
.Net control MITSUBISHI DotUtlType Component
Utility setting type (for 64-bit) Act control ActUtlType64 Control
ActUtlDataLogging64 Control
.Net control DotUtlType64 Control
Program setting type (for 32-bit) Act control MITSUBISHI ActProgType Controls Ver1.0
MITSUBISHI ActProgDataLogging Controls Ver1.0
MITSUBISHI ActSupportMsg Controls Ver1.0 4
Program setting type (for 64-bit) Act control ActProgType64 Control
ActProgDataLogging64 Control
■ Class created for each control

Control Class
ActUtlType Control ActUtlTypeLib.ActUtlTypeClass
ActUtlDataLogging Control ActUtlDataLoggingLib.ActUtlDataLoggingClass
ActSupportMsg Control ActSupportMsgLib.ActSupportMsgClass
MITSUBISHI DotUtlType Component MITSUBISHI.Component.DotUtlType
ActUtlType64 Control ActUtlType64Lib.ActUtlType64Class
ActUtlDataLogging64 Control ActUtlDataLogging64Lib.ActUtlDataLogging64Class
ActSupportMsg64 Control ActSupportMsg64Lib.ActSupportMsg64Class
DotUtlType64 Control DotUtlType64.DotUtlType64
ActProgType Control ActProgTypeLib.ActProgTypeClass
ActProgDataLogging Control ActProgDataLoggingLib.ActProgDataLoggingClass
ActSupportMsg Control ActSupportMsgLib.ActSupportMsgClass
ActProgType64 ActProgType64Lib.ActProgType64Class
ActProgDataLogging64 ActProgDataLogging64Lib.ActProgDataLogging64Class
ActSupportMsg64 ActSupportMsg64Lib.ActSupportMsg64Class
■ Include file (When using Visual Basic .NET, Visual C# )

Development language Include file
Visual Basic .NET ActDefine.vb
Visual C# ActDefine.cs

4.2 When using Visual Basic .NET, Visual C# 45
When using a control by pasting a control to a form
This function only supports Window Form. WPF and UWP are not supported.
Operating procedure
2. Right-click in "Toolbox" and select [Choose Items].
3. Select a control of "Development type" to be used (Page 46 Applicable Controls (When pasting a control to a form))
from the [COM Components] tab in the "Choose Toolbox Items" screen, click the [OK] button.
4. Paste the control added to the toolbox to a form.
5. Select [Project]  [Add Existing Item], and add included files (Page 45 Include file (When using Visual Basic .NET,
Visual C# )). The include files are stored in the following folder at the time of installation.

Utility setting type (for 32-bit) MITSUBISHI ActUtlType Controls
MITSUBISHI ActUtlDataLogging Controls
MITSUBISHI ActSupportMsg Controls
Program setting type (for 32-bit) MITSUBISHI ActProgType Controls
MITSUBISHI ActProgDataLogging Controls

46 4.2 When using Visual Basic .NET, Visual C#
4.3 When using Visual C++
When using a control with Visual C++, MFC must be installed in advance.
The following shows the setting operation when using Visual C++.

Operating procedure
2. Set required include files for "Development type" to be used by referring the following table. (Page 48 Setting the
include file (for Visual C++)) The include files are stored in the following folder at the time of installation.
4
Development type Required include file
Utility setting type (for 32-bit) ActUtlType_i.c
ActUtlType_i.h
ActUtlDataLogging_i.c
ActUtlDataLogging_i.h
ActSupportMsg_i.c
ActSupportMsg_i.h
Utility setting type (for 64-bit) ActUtlType64_i.c
ActUtlType64_i.h
ActUtlDataLogging64_i.c
ActUtlDataLogging64_i.h
ActSupportMsg64_i.c
ActSupportMsg64_i.h
Program setting type (for 32-bit) ActProgType_i.c
ActProgType_i.h
ActProgDataLogging_i.h
ActProgDataLogging_i.c
ActSupportMsg_i.c
ActSupportMsg_i.h
ActDefine.h
Program setting type (for 64-bit) ActProgType64_i.c
ActProgType64_i.h
ActProgDataLogging64_i.h
ActProgDataLogging64_i.c
ActSupportMsg64_i.c
ActSupportMsg64_i.h
ActDefine.h
3. Create instances for each control to be used. For the creation method of instance, refer to the sample program for Visual
C++.

4.3 When using Visual C++ 47
■ Setting the include file (for Visual C++)
Operating procedure
1. Start Visual Studio and select [Project]  [Properties].
2. Select [Configuration Properties]  [VC++ Directories] on the navigation pane displayed on the left side of the screen.
3. Select "Include Directories" displayed on the right side of the screen and click the [] button, then select <Edit...>.
4. Click the [New Line] button.
5. Click the [...] button.
6. On the "Select Directory" screen, select the folder in which the include files are stored.
The include files are stored in the following folder at the time of installation.
When using a control by pasting a control to a form

Operating procedure
2. Right-click the form and select "Insert ActiveX Control."

3. Select a control of "Development type" to be used (Page 51 Applicable Controls (When pasting a control to a form)),
and click the [OK] button.

48 4.3 When using Visual C++
4. Right-click the form and select "Add Variable."
5. Enter "Name" and "Variable type" (Page 51 Variable type) in "General settings" of the "Add Control Variable" screen,
and click the [Next] button.
For "Name," enter the name of an object to be used in the program.
6. Enter ".h file" and ".cpp file" (Page 51 .h file and .cpp file) in "Other settings" of the "Add Control Variable " screen,
and click the [Finish] button.

7. Make sure that ".h file" and ".cpp file" set in the step 6 are crated in Solution Explorer.
8. When using ActProgType or ActProgDataLogging, select [Project]  [Add Existing Item], and add an include file
"ActDefine.h." The include file is stored in the following folder at the time of installation.
".h file" created in the step 6 from 'When pasting a control to the form (Page 48 When using a control by
pasting a control to a form)' may not be created properly. (Page 649 When a header file is not created
properly at the time of pasting a control to a form with Visual C++)

50 4.3 When using Visual C++
Utility setting type (for 32-bit) MITSUBISHI ActUtlType Controls
MITSUBISHI ActUtlDataLogging Controls
Program setting type (for 32-bit) MITSUBISHI ActProgType Controls
MITSUBISHI ActProgDataLogging Controls
■ Variable type
The following list shows "Variable type" for each control to be entered in the "Add Control Variable" screen.
Control Variable type
ActUtlType CActUtlType
4
ActUtlDataLogging CActUtlDataLogging
ActSupportMsg CActSupportMsg
ActProgType CActProgType
ActProgDataLogging CActProgDataLogging
■ .h file and .cpp file

The following table shows ".hfile" and ".cpp file" for each control to be entered in the "Add Control Variable" screen.
Control .h file .cpp file
ActUtlType actutltype.h actutltype.cpp
ActUtlDataLogging actutldatalogging.h actutldatalogging.cpp
ActSupportMsg actsupportmsg.h actsupportmsg.cpp
ActProgType actprogtype.h actprogtype.cpp
ActProgDataLogging actprogdatalogging.h actprogdatalogging.cpp

5.1 Setting with Utilities

This section explains the procedure for communication by using the Communication Settings Utility, and how to operate and
set Communication Settings Utility.
Operation procedure
1. Create settings for each logical station number by using Communication Settings Utility.
2. Specify the logical number to the ActLogicalStationNumber property in a user program.
Logical station number

The logical station number is the logical number assigned to the data that is the compilation of the connection-destination
information necessary for opening a communication line into a single data by using Communication Settings Utility.
Ex.
For CPU COM communication
Personal computer CPU Module

(Communication target CPU)
CPU Module
Ethernet
(Network No. 1)
Ethernet Module
CPU COM communication (Station number: 3)
(COM 1) Ethernet Module
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.
Starting Communication Settings Utility

Operating procedure
Select [Start]  [MELSOFT]  [Communication Settings Utility].
52 5.1 Setting with Utilities
[Target setting] tab
This tab is used to display the setting details of the logical station number set in Communication Setting Wizard and to edit it.
Window
Connection image
diagram
Item Description
Logical station number Select a logical station number to display and edit the setting details set in Communication Setting Wizard.
[Wizard] button Click this to start Communication Setting Wizard and set the logical station number.
[Delete] button Click this to delete the preset logical station number.
Connection image diagram Displays the connection image diagram of the selected logical station number.
By clicking any sketch (personal computer, programmable controller CPU) in the connection image diagram, Communication
Setting Wizard starts and the settings can be changed.
For details on Communication Setting Wizard, refer to the following:

Page 54 Operations on Communication Setting Wizard screens
5.1 Setting with Utilities 53
Operations on Communication Setting Wizard screens
Set a logical station number which is required to perform communication with the utility setting type.
■ Outline of Communication Setting Wizard

The logical station number which is required to perform communication with the utility setting type is set in the wizard format.
Wizard (1), (6) Wizard (3) Wizard (5)
Connected station Relayed station
Personal computer
MX
Component
Connected network Relayed network
Wizard (2) Wizard (4)
The following are the descriptions of the settings set in Communication Setting Wizard screens.
Communication Screen Name Description
Setting Wizard
Wizard (1) Introduction Set the logical station number.
Wizard (2) PC side Set the connected network between the personal computer and connected station (programmable controller
CPU and module).
Wizard (3) PLC side Set the connected station (programmable controller CPU and module).
Wizard (4) Network Set the relayed network between the connected station (programmable controller CPU and module) and
relayed station (programmable controller CPU and module).
Wizard (5) Other station Set the relayed station programmable controller CPU.
Wizard (6) Finished Add a comment to the logical station number.
■ Display method of Communication Setting Wizard screens.
Window
• Select [Menu]  [Wizard].
• Click the [Wizard] button on the utility screen.
■ Display procedure of Communication Setting Wizard screens.
Communication Setting Wizard screens are displayed 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
settings.
Set all the available setting items being displayed.
• Some of Communication Setting Wizard screens may not be displayed depending on the settings.
Operating procedure
Wizard (1) - Introduction
1. Enter or select a logical station number.

The logical station number can be registered from 0 to 1023.
5
Wizard (2) - PC side
2. Select the personal computer side interface.

Items corresponding to the communications in "PC side I/F"
(Page 57 Items corresponding to the communications in "PC
side I/F")
Wizard (3) - PLC side

3. Select the PLC side interface.
Communication via GOT (Page 56 Communication via GOT)
Wizard (4) - Network
4. Select a communication route.
Wizard (5) - Other station
5. Select other station.
Wizard (6) - Finished
6. Enter a comment and click the [Finish] button.

Up to 32 alphanumeric characters can be entered in 'Comment.'
When the registration of the logical station number is completed
in Communication Setting Wizard, the settings are displayed on
the [Target setting] tab.
■ Communication via GOT

The following screen appears.
■ 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 system RS-232 interface communication
Serial (via GOT) GOT transparent communication
Ethernet board Ethernet communication, GOT gateway device communication
Ethernet board (via GOT) GOT transparent 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
GX Simulator3 GX Simulator3 communication
GX Simulator2 GX Simulator2 communication
MT Simulator2 MT Simulator2 communication
5
[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 Displays the settings of the registered logical station number.
By double-clicking the logical station number, Communication Setting Wizard starts.
[Wizard] button Click this to start Communication Setting Wizard and set the logical station number.
[Delete] button Click this to delete the preset logical station number.
Display Utility: Displays the settings set for the logical station number in the property list.
Program: Displays the property list required for setting with the program setting type.
[Save text] button Click this to save the settings of property list to a file in the .txt format.
• For details on Communication Setting Wizard, refer to the following:

• For a communication route for selecting PC side adapter, the ActHostAddress property on the [List view] tab
is displayed as follow:
'Connection target IP address' + tab character + 'Personal computer side IP address.'
To set the value of the ActHostAddress property by using the program setting type, use a tab character after
replacing it to the character code of the correct tab.
[Communication test] tab
This tab is used to perform the communication test of a registered logical station number.
Window
Item Description
Logical station number Select a logical station number to perform a communication test.
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) Click this to start (stop) the communication test.
Result Diagnosis count Displays the number of connections during the communication test.
Result Displays 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 Displays the connected CPU type.
Mean time of Displays the average time taken until one communication test is established. (Unit: ms)
communication
Operating procedure
1. Select a logical station number.
2. Click the [Test] button.

• The error code is displayed in 'Result.' (At normal termination, "0x00000000" is displayed in 'Result.')
• If an error occurs, check the error code and remove the error. (Page 588 ERROR CODES)
Create a user program and correct device date with PLC Monitor Utility by using a logical station number
whose communication is conformed as normal.
Exporting/importing the communication settings
Exporting
Save the communication settings set to a personal computer in a file. (The file where data is saved is called the ACT
registered file.)
This file is used to apply the communication settings to another personal computer.
• Uninstalling deletes all the settings within "Communication Settings Utility."

• To avoid this, export the file storing the settings.
• When importing the file using Communication Settings 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
Importing
Apply the exported communication settings saved to the file (Page 60 Exporting) 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.
Specifying a created logical number in a program
Communication can be established by specifying the logical station number set with Communication Settings Utility to the
ActLogicalStationNumber(LONG) which is the open function property, and executing the open function.
5.2 Setting in Programs
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 on the properties which must be set for the corresponding Act controls, refer to the following:
Page 183 Details of Control Properties
For module settings when using MX Component, refer to the following:
Item Reference
Serial communication Page 24 SYSTEM CONFIGURATIONS
Ethernet communication (when using Ethernet modules)
CC-Link system RS-232 interface communication
5
Operation procedure
1. Check the required property by using Communication Settings Utility.
2. Set the required property in a user program.
Checking a property with Communication Settings Utility

Check a property by the following procedure.
Operating procedure
1. Specify a communication route in "Communication
Setting Wizard" on Communication Settings Utility.
For details on Communication Setting Wizard, refer to
the following:
Page 54 Operations on Communication Setting
Wizard screens
5.2 Setting in Programs 63
2. Click the [List view] tab.
For details on the [List view] tab, refer to the following:
Page 58 [List view] tab
3. Select "Program" from "Display".
4. Control the scroll bar to confirm the property.

Control names to be used and properties to be set are displayed.
The file can be saved in the .txt format by clicking the [Save
text] button.
Saved into file in .txt format.
64 5.2 Setting in Programs
Setting a required property in a user program
Check the property values with the text file output from Communication Settings Utility, and enter the values into Properties of
the property window.
Example) Visual Basic .NET
The settings of the property can be changed with the source code.
5.2 Setting in Programs 65
6 COMMUNICATION SETTING EXAMPLES
(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 easily with the utility setting type in MX
Component.
• For the settings other than "As set by user," set the value shown in the table.
• When checking the communication settings in MX Component for the first time, make sure that
communication of each communication route can be established properly in each engineering tool in
advance so that the cause of the communication failure can be identified easily.
• For details on the settings of modules, refer to the manual of each module.
6.1 Serial Communication

This section provides the serial communication procedure and its setting example using the utility setting type.
(For 1:1 communication) (For 1:n communication)
Module Ò
CPU C24 Module CPU C24 Module
Module (Sta. No.1) Module (Sta. No.1)
(Multi-drop)
COM1 COM1
Module Ó
CPU C24 Module
Module (Sta. No.3)
Access procedure
The following shows the procedure before accessing a programmable controller CPU.
Operating procedure
1. Set a module.
Page 68 Settings of serial communication modules
2. Connect the module and a personal computer.

Page 24 SYSTEM CONFIGURATIONS
3. Set a logical station number with Communication Settings Utility.
Page 67 Logical station number setting example
4. Perform a communication test to check the communication.

Page 59 [Communication test] tab

66 6.1 Serial Communication
Logical station number setting example
For the operating procedure of Communication Setting Wizard screens, refer to the following:
Setting data
■ For 1:n communication
Communication Setting Item Setting example
Wizard
Introduction Logical station number 0 to 1023
PC side PC side I/F Serial
Connect port COM1
Time out 10000
PLC side PLC side I/F C24 module
Module type Select a C24 module to be used.
Station No. 1
Transmission speed 19200
Parity Odd
6
Control DTR or RTS Control
Network Station type Other station
Network C24
Network type Multidrop(combine)
Other station CPU type Select a CPU module to be used.
Station No. 3
Finished Comment (Optional)

6.1 Serial Communication 67
Settings of serial communication modules
The following 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
R series-compatible C24
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 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: 6
Q Corresponding Serial Communication Module User's Manual (Basic)
MELSEC-L Serial Communication Module User's Manual (Basic)
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
■ For 1:n communication

0 Station
b15 to b8 b7 to b0 Synchronous operation
Switch 1 CH1 communication speed CH1 transmission setting 07E6H
Switch 5 Module station number 0000H (As set by user)
1 Station
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 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 19200 bps
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 70 Settings with PLC parameters)
• To write values to special data registers (D8120, D8121, D8129) in a sequence program (Page 71 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
Stop Bit*1 1bit/2bit
Transmission Speed*1 300 bps/600 bps/1200 bps/2400 bps/4800 bps/9600 bps/19200 bps
H/W Type*1 Select the cable type used in the communication.
Sum Check*1 Select/clear
Transmission Control Procedure*1 Select the transmission control procedure.
Station Number Setting*1 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. 6
■ 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

b0 Data length 0: 7 bits
1: 8 bits
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 bits
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
300 bps 0 0 1 1
600 bps 0 1 0 0
1200 bps 0 1 0 1
2400 bps 0 1 1 0
4800 bps 0 1 1 1
9600 bps 1 0 0 0
19200 bps 1 0 0 1
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 10 ms units.
The setting range is as follows:
For FX3S, FX3G, FX3GC, FX3U, FX3UC, 1 to 255 (10 to 2550 ms).
If "0" is stored, 100 ms is set.
b15 to b0
D8129 FX3S, FX3G(C), FX3U(C): 1 to 255
• 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.
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: 9600 bps
Stop bit: 1 bit
Parity: NONE
Data length: 7 bit
• D8121
Station number : 12
• D8129
Time out time : 200 ms

6.2 Ethernet Communication (When Using Ethernet
Modules)
This section provides the procedure for Ethernet communication with an Ethernet module and its setting example using the
utility setting type.
Network No.1 Station Number: 2
Ethernet Module (192.168.0.2)

Station number: 2
CPU1
CPU Module Ethernet Module (192.168.0.1)
Station number: 1
CPU2
CPU Module
6
Network No.2
Ethernet Module (192.168.0.3)

Station number: 3
Access procedure
Operating procedure
1. Set the module parameters.
Page 75 Settings of modules
2. Connect the module and a personal computer.

3. Edit a HOSTS file.
The HOSTS file is not required to be edited when entering an IP address in a host name (IP Address) of Communication
Settings Utility and the ActHostAddress property.

6.2 Ethernet Communication (When Using Ethernet Modules) 73
Setting data
Wizard
PC side PC side I/F Ethernet board
Connect module Select an Ethernet board to be used.
Protocol TCP
Network No. 1
Station No. 2
Time out 60000
PLC side PLC side I/F Ethernet module
Module type Select an Ethernet module to be used.
Host (IP Address) 192.168.0.1
Station No. 1
Network Ethernet
Network No. 2
Station No. 3
Multiple CPU None

74 6.2 Ethernet Communication (When Using Ethernet Modules)
Settings of modules
The following shows the settings of a module when using MX Component.
Settings of parameters
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 Operation setting
CPU 2 Ethernet parameters Operation setting
Set the parameters in GX Works3 for an RCPU.

For details on parameter settings, refer to the following:
MELSEC iQ-R Ethernet User's Manual (Application)

6.2 Ethernet Communication (When Using Ethernet Modules) 75
Settings of routing parameters
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:
Page 619 Concept of Routing Parameters
CPU to be set Setting screen example
CPU 1
CPU 2
Set the routing parameters in GX Works3 for an RCPU.

For details on routing parameter settings, refer to the following:
Checking the communication

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 a cable and module connections and Windows side IP address and other settings.

76 6.2 Ethernet Communication (When Using Ethernet Modules)
6.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.
IP address (192.168.0.1)
Built-in Ethernet CPU
Access procedure
The following shows the procedure before accessing a programmable controller CPU. 6
Operating procedure
■ When directly connecting to an Ethernet port
1. Connect a module and personal computer.

Page 78 When directly connecting to an Ethernet port
■ When specifying a host name (IP address)

2. Set the module parameters.
Page 79 Setting of parameters (Only when specifying a host name (IP address)),Page 79 Checking the
communication

Page 78 When specifying a host name (IP address)

6.3 Ethernet Communication (When Using Built-in Ethernet CPUs) 77
Setting data
Wizard
Connect module CPU module
Protocol UDP
Time out 60000
PLC side PLC side I/F CPU module
Ethernet port direct connection Select the checkbox
Network Station type Host station
CPU type Select a CPU module to be used.
Multiple CPU None

Wizard
Protocol TCP
Time out 60000
Multiple CPU None
When using the built-in Ethernet CPU search, click the [Find CPU (Built-in Ethernet port) on network] button.
Built-in Ethernet CPUs on the same network is the target of the search.
Choose the target CPU from the list and clicking the [OK] button.
An IP address can be applied to the "Communication Setting Wizard - PLC side" setting.

78 6.3 Ethernet Communication (When Using Built-in Ethernet CPUs)
Settings of modules
The following shows the settings of a module when using MX Component.
Setting of parameters (Only when specifying a host name (IP address))

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 RCPUs and LHCPUs, set the parameters in GX Works3.

For details on parameter settings, refer to the following:

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.

6.3 Ethernet Communication (When Using Built-in Ethernet CPUs) 79
Adapter Modules)
This section explains the procedure for the Ethernet communication using Ethernet adapter module and its setting example
using the utility setting type.
CC-Link IE Field Network module
Ethernet adapter module
Access procedure
Operating procedure
2. Connect an Ethernet adapter module to CC-Link IE Field Network.


Setting data
Wizard
Connect module CC IE Field Ethernet adapter
Protocol TCP
Time out 60000
PLC side PLC side I/F CC IE Field Ethernet adapter
Network Station type Other station (Single)
Network No. 1
Station No. 0
Multiple CPU None

80 6.4 Ethernet Communication (When Using Ethernet Adapter Modules)
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.
<Direct connection>
FX3U(C)/FX3G(C)/FX3S
Ethernet
FX3U-ENET-ADP
<IP address specified communication>
FX3U(C)/FX3G(C)/FX3S 6
Hub
Ethernet Ethernet
FX3U-ENET-ADP
Access procedure
Operating procedure
1. Connect an Ethernet adapter and a personal computer.
Page 82 Direct connection


1. Connect an Ethernet adapter and a personal computer.

Page 82 IP address specified communication


6.5 Ethernet Communication (When Using Ethernet Adapter) 81
Setting data
■ Direct connection
Communication Setting Item Setting example (direct connection)
Wizard
Connect module FX3U-ENET-ADP
Time out 60000
PLC side PLC side I/F FX3U-ENET-ADP
Ethernet port direct connection Select the checkbox
CPU type Select an FXCPU to be used.
■ IP address specified communication

Communication Setting Item Setting example (IP address specified communication)
Wizard
Connect module FX3U-ENET-ADP
Time out 60000
PLC side PLC side I/F FX3U-ENET-ADP
When using the built-in Ethernet CPU search, click the [Find CPU (Built-in Ethernet port) on network] button.
Built-in Ethernet CPUs on the same network is the target of the search.
Choose the target CPU from the list and clicking the [OK] button.
An IP address can be applied to the "Communication Setting Wizard - PLC side" setting.

82 6.5 Ethernet Communication (When Using Ethernet Adapter)
6.6 CPU COM Communication
This section provides the CPU COM communication procedure and its setting example using the utility setting type.
CPU Normal station

Module (Sta. No.2)
MELSECNET/H
(Network No. 5)
COM1
CPU Normal station
Module (Sta. No.5)
Access procedure
6
Operating procedure


Setting data
Wizard
Connect port COM1
Time out 10000
Network MELSECNET/10(H)
Mode MELSECNET/H
Network No. 5
Station No. 5
Multiple CPU None

6.6 CPU COM Communication 83
6.7 CPU USB Communication
This section provides the CPU USB communication procedure and its setting example using the utility setting type.
CPU Normal station

Module (Sta. No.2)
MELSECNET/H
(Network No.1)
USB port
CPU Normal station
Module (Sta. No.8)
Access procedure
Operating procedure
2. Install a USB driver.


Setting data
Wizard
PC side PC side I/F USB
Time out 10000
Mode MELSECNET/H
Network No. 1
Station No. 8
Multiple CPU None

84 6.7 CPU USB Communication
6.8 CC-Link Communication
This section provides the CC-Link communication procedure and its setting example using the utility setting type.
Master station
(Station number 1)
Number of occupied
stations 1 Transmission speed: 10Mbps
CC-Link
CPU Local station

Module (Sta. No.5)
First CC-Link Ver.2 board
Supported CPU and module in CC-Link communication via a personal computer board to an RCPU are as follows.
CC-Link module Compatible CPU Station No.
RJ61BT11 RCPU 0 to 64
6
Supported CPUs and module in CC-Link communication to an FXCPU are as follows.
FX3U-64CCL FX3G, FX3GC, FX3U, FX3UC 1 to 63
• Accessible to an FXCPU with CC-Link communication only via the serial/USB connection of QCPU or via Q series-
compatible C24.
Access procedure
The following shows the procedure before accessing a programmable controller CPU by using CC-Link communication.
Operating procedure
1. Set a CC-Link Ver.2 board.
2. Connect a personal computer to CC-Link.

Page 24 SYSTEM CONFIGURATIONS, Page 87 Checking the CC-Link Ver.2 board


Setting data
Wizard
PC side PC side I/F CC-Link board
Board No. 1st module

6.8 CC-Link Communication 85
Wizard
Station No. 5
Multiple CPU None

86 6.8 CC-Link Communication
Settings of modules
Checking the CC-Link Ver.2 board

Check whether a 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
6
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.
5. Click the [Exit] button to exit from the utility.

6.9 CC-Link system RS-232 interface Communication
This section provides the CC-Link system RS-232 interface communication procedure and its setting example using the utility
setting type.
Transemission speed: 19200bps
Transemission speed: 10Mbps
AJ65BT-R2N(Q) CC-Link
Station number: 1
COM1 CPU Master station

Module (Sta. No.0)
Access procedure
The following shows the procedure before accessing a programmable controller CPU by CC-Link system RS-232 interface
communication.
Operating procedure
1. Set the operation setting DIP switches of an AJ65BT-R2N module.
CC-Link System RS-232 Interface Module User's Manual
2. Connect the AJ65BT-R2N module to a CC-Link module.

3. Connect a personal computer to the AJ65BT-R2N module.
4. Set the network parameters.


Setting data
Wizard
Connect port COM1
Time out 10000
PLC side PLC side I/F AJ65BT-R2N
Mode Q
CC-Link module No. 0

88 6.9 CC-Link system RS-232 interface Communication
Wizard

6.9 CC-Link system RS-232 interface Communication 89
6.10 GX Simulator2 Communication
This section provides GX Simulator2 communication procedure and its setting example using the utility setting type.
Starting!
GX Works2
The simulation
function
MX
Component CPU Module
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 shows the procedure before accessing the simulation function of GX Works2 by using GX Simulator2
communication.
Operating procedure
1. Start GX Works2 and the simulation function.


Setting data
Wizard
PC side PC side I/F GX Simulator2
Target Simulator Simulator A
CPU Series Select a CPU series to be used.

90 6.10 GX Simulator2 Communication
This section provides GX Simulator3 communication procedure and its setting example using the utility setting type.
Starting!
GX Works3
The simulation
function
MX
Component CPU Module
• 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 6
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 shows the procedure before accessing the simulation function of GX Works3 by using GX Simulator3
communication.
Operating procedure
1. Start GX Works3 and the simulation function.


Setting data
Wizard
PC side PC side I/F GX Simulator3
Set Port No.*1 Unselected
System No. 1
PLC No*2 1
Time out 10000

6.11 GX Simulator3 Communication 91
*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+ PLC No
<Example> For System No. = 1, PLC No = 1
5511=5500+110+1
*2 For the system number and PLC number, refer to the following:
GX Works3 Operating Manual

6.12 MT Simulator2 Communication
This section provides MT Simulator2 communication procedure and its setting example using the utility setting type.
Starting!
MT Developer2
The simulation
function
MX
Component simulater
The communication will be disconnected when the simulation function is stopped by MT Developer2 while
communicating to MX Component.
Access procedure 6
The following shows the procedure before accessing the simulation function of MT Developer2 by using MT Simulator2
communication.
Operating procedure
1. Start MT Developer2 and the simulation function.


Setting data
Wizard
PC side PC side I/F MT Simulator2
Target Simulator Select a target simulator to be used.

6.12 MT Simulator2 Communication 93
6.13 MELSECNET/H Communication
This section provides the MELSECNET/H communication procedure and its setting example using the utility setting type.
Normal station
(Sta. No. 1)
First MELSECNET/H board
Numeral within indicates station number.
1
CPU Module (No. 2) at normal station
(station number: 2) on network number 2
4 Network No. 1 2 3 Network No. 2 2 is accessed.
Access procedure
The following shows the procedure before accessing a programmable controller CPU by using MELSECNET/H
communication
Operating procedure
1. Set an MELSECNET/H board.
2. Connect a personal computer to MELSECNET/H.

Page 24 SYSTEM CONFIGURATIONS, Page 95 Checking the MELSECNET/H board



Setting data
Wizard
PC side PC side I/F MELSECNET/H board
Network No. 2
Station No. 2
Multiple CPU No. 2

94 6.13 MELSECNET/H Communication
Checking the MELSECNET/H board
Check whether a 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 Set] button.
Channel: 51: MELSECNET/H (1 slot)
Mode: Online (auto.reconnection)
Baudrate: Any (10Mbps is set for this example.)
NET mode: MNET/H mode
Then, click the [Routing Param.Setting] button.
6
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.
5. Click the [Loop monitor] tab.

Check that the loop is normal.
6. Click the [Exit] button to exit from the utility.

6.13 MELSECNET/H Communication 95
6.14 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.
Normal station
(Sta. No. 2)
First CC-Link IE Controller Network board
CPU Module at normal station (station number: 1)

on network number 1 is accessed.
Network No. 1 1
Supported CPUs and modules in CC-Link IE Controller Network communication via a personal computer board to RCPU are
as follows.
RJ71GP21-SX RCPU 1 to 63
RJ71EN71*1 RCPU 1 to 120
*1 CCIEC setting or CCIEC + Ether setting only
Access procedure
The following shows the procedure before accessing a programmable controller CPU by using CC-Link IE Controller Network
communication.
Operating procedure
1. Set a CC-Link IE Controller Network board.
2. Connect a personal computer to CC-Link IE Controller Network.

Page 24 SYSTEM CONFIGURATIONS, Page 97 Checking the CC-Link IE Controller Network board


Setting data
Wizard
PC side PC side I/F CC IE Control board

96 6.14 CC-Link IE Controller Network Communication
Checking the CC-Link IE Controller Network board
Check whether a 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)
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.

6.14 CC-Link IE Controller Network Communication 97
5. Click the [Diagnostics] button on the CC IE Control utility
screen.
6. Click the [Close] button to exit from the utility.

6.15 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.
Master station
(Sta. No. 0)
First CC-Link IE Field Network board
CPU Module at local station (station number: 1)

on network number 1 is accessed.
Network No. 1 1
Supported CPUs and modules in CC-Link IE Field Network communication via a personal computer board to RCPU are as
follows. 6
RJ71GF11-T2 RCPU 1 to 63
RJ71EN71*1 RCPU 1 to 120
*1 CCIEF setting or CCIEF + Ether setting only
Access procedure
The following shows the procedure before accessing a programmable controller CPU by using CC-Link IE Field Network
communication.
Operating procedure
1. Set a CC-Link IE Field Network board.
2. Connect a personal computer to CC-Link IE Field Network.

Page 24 SYSTEM CONFIGURATIONS, Page 101 Checking the CC-Link IE Field Network board

Setting data
Wizard
PC side PC side I/F CC IE Field board

6.15 CC-Link IE Field Network Communication 99
Wizard
Network No. 1
Station No. 1
Multiple CPU None

100 6.15 CC-Link IE Field Network Communication
Checking the CC-Link IE Field Network board
Check whether a 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].
6
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].
6. Click the [Close] button to exit from the utility.

6.16 GOT Gateway Device Communication
This section explains the procedure for the GOT gateway device communication and its setting example using the utility
setting type.
Ethernet
GOT (192.168.0.1)
Access procedure
The following shows the procedure before accessing a GOT by using GOT gateway device communication.
Operating procedure
1. Set a GOT.
GOT operating manual to be used
2. Connect the GOT to Ethernet.

3. Connect a personal computer to Ethernet.


102 6.16 GOT Gateway Device Communication
Setting data
Wizard
Connect module GOT
Port No. 5011
Time out 60000
PLC side PLC side I/F Ethernet module
Module type GOT
6
After completion of preparations for GOT gateway device 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<10ms TTL=32
• When abnormal
C:\>ping 192.168.0.1
Request timed out.

6.16 GOT Gateway Device Communication 103
6.17 GOT Transparent Communication
This section provides the GOT transparent communication procedure and its setting example using the utility setting type.
CPU Normal station

Module (Sta. No.2)
GOT MELSECNET/H
(Network No. 1)
USB port
CPU Normal station
Module (Sta. No.8)
For applicable system configuration, refer to the following:

 Connection manuals for GOT2000 series
(Mitsubishi Products), (Non-Mitsubishi Products 1), (Non-Mitsubishi Products 2), (Microcomputer, MODBUS/
Fieldbus Products, Peripherals)
Access procedure
The following shows the procedure before accessing a GOT by using the GOT transparent function.
Operating procedure
1. Set a GOT.
2. Connect the GOT to personal computer.
3. Connect the GOT to programmable controller CPU.

104 6.17 GOT Transparent Communication
Setting data
Wizard
PC side PC side I/F USB (via GOT)
Time out 10000
GOT side GOT - PLC I/F Serial
Other station
Mode
CPU type
MELSECNET/H
Select a CPU module to be used.
6
Network No. 1
Station No. 8
Multiple CPU None

6.17 GOT Transparent Communication 105
6.18 Inverter COM Communication
This section provides the inverter COM communication procedure and its setting example using the utility setting type.
Inverter
COM1
Access procedure
The following shows the procedure before accessing an inverter by using inverter COM communication.
Operating procedure
1. Connect an inverter and personal computer.


Setting data
Wizard
Connect port COM1
Time out 10000
PLC side PLC side I/F Inverter
Inverter A800
Station No. 0
Parity Even
Data bit 8
Stop bit 1
Delimiter CR
Transmission wait time 0

106 6.18 Inverter COM Communication
6.19 Inverter USB Communication
This section provides the inverter USB communication procedure and its setting example using the utility setting type.
Inverter
USB port
Access procedure
The following shows the procedure before accessing an inverter by using inverter USB communication.
Operating procedure
6
1. Connect an inverter and personal computer.


Setting data
Wizard
Time out 10000
PLC side PLC side I/F Inverter
Inverter A800
Station No. 0
Transmission wait time 0

6.19 Inverter USB Communication 107
6.20 Robot controller COM Communication
This section provides the robot controller COM communication procedure and its setting example using the utility setting type.
Robot controller
COM1
Access procedure
The following shows the procedure before accessing a robot controller by using robot controller COM communication.
Operating procedure
1. Connect a robot controller and personal computer.


Setting data
Wizard
Connect port COM1
Time out 10000
PLC side PLC side I/F Robot controller
R/C type CRnD-7xx/CR75x-D
Parity Even
Character Size 8
Stop bit 1
Send timeout 5000
Receive timeout 30000
Retries 3
Usage protocol Procedural

108 6.20 Robot controller COM Communication
6.21 Robot controller USB Communication
This section provides the robot controller USB communication procedure and its setting example using the utility setting type.
Robot controller
USB port
Access procedure
The following shows the procedure before accessing a robot controller by using robot controller USB communication.
Operating procedure
6
1. Connect a robot controller and personal computer.



Setting data
Wizard
Time out 10000
Send timeout 5000
Retries 3

6.21 Robot controller USB Communication 109
6.22 Robot controller Ethernet Communication
This section provides the robot controller Ethernet communication procedure and its setting example using the utility setting
type.
Robot
controller
Access procedure
The following shows the procedure before accessing a robot controller by using robot controller Ethernet communication.
Operating procedure
1. Connect a robot controller to Ethernet.
Robot controller Manual to use
2. Connect a personal computer to Ethernet.



Setting data
Wizard
Connect module Robot controller
Port No. 10001
Send timeout 5000
Retries 3

110 6.22 Robot controller Ethernet Communication
7 PROGRAMMING
This chapter explains the method for creating labels used in a program, coding, debugging by utilizing PLC Monitor Utility.
Process Overview Reference
Creating labels Explains Label Utility used when creating a label. Page 111 Creating a Label With Label Utility
Coding Explains the method for coding by using the functions and properties provided Page 138 Coding
by a control.
Debugging Explains PLC Monitor Utility used for debugging. Page 139 Debugging
7.1 Creating a Label With Label Utility

When using a label in a program, create a label with Label Utility firstly.
This section explains the operation and setting method of Label Utility.
Starting Label Utility

Operating procedure
Select [Start]  [MELSOFT]  [Label Utility].
Label screen 7
Window
LabelSpace
window
Work window
Navigation
window
Task window
Status bar

LabelSpace window Displays the list of LabelSpace. 
The LabelSpace names are displayed on the list in ascending order based on the
date of creation.
Navigation window Displays the logical station number, structured data type and system label list of 
LabelSpace in tree format.
Work window Displays the system label list and the Structure Setting screen. Page 114 System label list
Page 119 Structure setting
Task window Displays the processing result in list format. 
Status bar Displays the current status. Page 121 Change notification
7 PROGRAMMING
7.1 Creating a Label With Label Utility 111
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 32 characters can be used in the LabelSpace name.
■ 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 PROGRAMMING
112 7.1 Creating a Label With Label Utility
Registering/deleting a logical station number
Registration
Register a logical station number to LabelSpace.
Operating procedure
• Select a LabelSpace name on the LabelSpace window, and select [Menu]  [Logical Station Number]  [Register].
• Select a LabelSpace name on the LabelSpace window, right-click "Logical Station Number" on the Navigation window, and
select [Logical Station Number]  [Register].
Window
Item Description
Logical station number Select the logical station number defined in Communication Settings Utility from the list box.
The logical station number which has already been registered to other LabelSpace is not displayed.
[Communication setting]
button
Click this to start Communication Settings Utility. 7
[Register] button Click this to register the logical station number, and close the screen.
[Cancel] button Click this to 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] 
[Deregister].
• Right-click the station number to be deleted from the Navigation window, and select [Logical Station Number] 
[Deregister].
• After registering the logical station number, save the LabelSpace.

• The logical station number and LabelSpace will be registered on a 1:1 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 PROGRAMMING
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 635 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 115 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. 32 characters 
The bit-specified word device (D0.1) can be specified.
When the structure is set for data type, "Details setting" is displayed.
Set the items on the "Structured Data Device Setting" screen displayed by clicking "Details setting."
(Page 117 Assigning devices to structured data type labels, Page 118 Assigning devices to structure
array type labels)
Label Name Enter the label name to be managed by system label Ver.2.  1763
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].
7 PROGRAMMING
• 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 MELSOFT Navigator MX Component

System label Ver.2 System label Ver.1 LabelSpace Ver.2*4 LabelSpace Ver.1
Simple Types/Array Simple Types/Array
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    
7
*1
String[Unicode]    
Time    
Timer*1    
Timer[Unsigned]*1*3    
Long timer*1*3    
Counter*1    
Counter[Unsigned]*1*3    
Long counter*1*3    
*1
Retentive timer    
Retentive Timer[Unsigned]*1*3    
Retentive long timer*1*3    
Structure*2    
*1 Select "Simple type" when arraying.

An error occurs during usage, when "Structure" is selected.
*2 For a label to which devices are not assigned in system label Ver.2, a five-level structure can be used.
For other types, only one-level structure can be used.
*3 To perform reading in system label Ver.2, a target to be read needs to be specified expressly.
Registered by connecting a target to be read (contact ".S"/Coil ".C"/ Current value ".N") to the end of a label name.
Example) When connecting current value ".N": (label name).N
*4 For a label to which devices are not assigned (labels that uses a label memory), the operation is same as when devices are assigned
regardless of the data types.
For bit type, the operation same as bit-specified word device.
7 PROGRAMMING
Window
Click [...] on the data type input 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 such as 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 input 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 PROGRAMMING
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.
Item Description
Label Name Displays label names defined as structure.
7
Data Type Displays data types set to data names.
Device Set device names to be assigned.
7 PROGRAMMING
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
the array of structure Displays 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 Displays label names defined as structure.
Data Type Displays data types set to data names.
Device Set device names to be assigned.
Device names can be entered for the start array element only.
7 PROGRAMMING
Structure setting
Register, edit, and browse each data (element) that is configured in the structure managed in the LabelSpace.
Window

Label Name Displays a label name. 
Data Type Displays a data type of the label. Page 115 Selecting data types
Specify a data type from the "Type Selection" screen displayed by clicking [...]. 7
Basic operations
Operating procedure
■ Adding system label list
• 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 system label list 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].
• 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 PROGRAMMING
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 Displays 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 PROGRAMMING
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 PROGRAMMING
Updating system label data
Update the system label data.
Operating procedure
Select [Menu]  [Refresh system label data for Control].
7 PROGRAMMING
Exporting/Importing LabelSpace
Exporting
Save the information used in Label Utility to a file.
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.
Importing
Import the saved information saved in a file by exporting LabelSpace (Page 123 Exporting/Importing LabelSpace) to
Label Utility.
To import LabelSpace of MX Component Version 4 to MX Component Version 5, change the number of characters used in the
LabelSpace name to less than 32 characters.
Operating procedure
Select [Menu]  [Import].
Window
7 PROGRAMMING
System label
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.
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
Act.Close();
Visual Basic.NET Visual C# VBA
MX Component
Label Utility
Syetem label
Data base
• System labels
Define labels on a 1:1 basis 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.
7 PROGRAMMING
Registering system labels in MX Component
Register a system label with Label Utility.
■ Registering system labels
Operating procedure
1. Start Label Utility.
2. Right-click "Undefined_Name" on the LabelSpace

window, and select [Rename LabelSpace].
Change the LabelSpace name.
3. Right-click "System Label List" on the Navigation

window, and select [System Label List]  [New].
Set the system label list name.
Select the set system label list name to display the system
label list.
4. Set system label names, data types, and devices.
(Page 114 System label list)
7 PROGRAMMING
5. Right-click "Logical Station Number" on the Navigation
window, and select [Logical Station Number] 
[Register].
6. Select a logical station number, and click the [Register]

button.
For setting the communication settings, click the
[Communication setting] button, and set the settings in
Communication Setting Wizard.
(Page 54 Operations on Communication Setting
Wizard screens)
The logical station number is displayed on the Navigation
window.
7. Select [Menu]  [Save LabelSpace].
The system label is registered.
8. Select [Menu]  [Refresh system label data for Control].

The labels referred from controls are updated.
7 PROGRAMMING
■ Deleting system labels
Operating procedure
1. Select "Delete" for a system label to be deleted.

The system label is deleted.
7

7 PROGRAMMING
■ Registering system labels (structured data type)
Operating procedure

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

window, and select [Structured Data Types]  [New].
Set the structure name.
Select the set structure name to display the structure setting

list.
4. Set label names and data types for structure member.
(Page 119 Structure setting)
7 PROGRAMMING
5. Right-click "System Label List" on the Navigation
window, and select [System Label List]  [New].
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 114 System label list)
Click "Detail Setting" on the "Device" column of the
system label list.
7
7. Specify a device.

7 PROGRAMMING
7 PROGRAMMING
Utilizing labels used in MELSOFT Navigator
Refer a system label from existing Workspace, and register it with Label Utility.
Operating procedure

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

window, and select [Workspace]  [Reference
Registration].
4. Select a Workspace that is to be referred and

registered. (Page 120 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.
7 PROGRAMMING
For referring more than one Workspace, add
LabelSpace first, and operate the procedure 2 to 4.

7 PROGRAMMING
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
The system label notification icon is displayed on the status
bar of Label Utility.
2. Select the LabelSpace name.
System label notification icon

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

[Change Contents of System Label Database].
(Page 121 Change notification)
4. Click the [Yes] button in the window asking whether to

reflect the changes.
Select the system label list name to display the system label
list.

For referring more than one Workspace, select
LabelSpace from the LabelSpace window first, and
operate the procedure 2 to 4.
7 PROGRAMMING
The system label notification icon is displayed while referring
more than one Workspace.

The system label notification icon is not displayed when the system labels are used without referring and
registering the Workspace.
7 PROGRAMMING
Using System Labels on another personal computer
Export a LabelSpace, and import it to another personal computer to use a system label.
■ Exporting LabelSpace
Export a LabelSpace, and create a file.
Operating procedure
1. Start Communication Settings Utility.
2. Select [Menu]  [COM setup export].
3. Enter the file name to be saved.

7
5. Select [Menu]  [Export].
6. Enter the file name to be saved.
7 PROGRAMMING
■ Importing LabelSpace
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. Start Communication Settings Utility.
2. Select [Menu]  [COM setup import].
3. Specify the file name of communication setting to be

imported.
5. Select [Menu]  [Import].
6. Specify the file name of LabelSpace to be imported.
7 PROGRAMMING
7 PROGRAMMING
7.2 Coding
Create the processing for reading/writing the target devices, devices, and labels by using the properties and functions
provided by a control.
For accessible devices, properties of controls, and functions, refer to the following:
Page 149 Accessible Devices
Page 181 PROPERTIES OF CONTROLS
Page 423 FUNCTIONS
7 PROGRAMMING
138 7.2 Coding
7.3 Debugging
Debugging can be performed efficiently by using PLC Monitor Utility when checking the device value.
The following explains the operation and setting method of PLC Monitor Utility.
Checking a value using PLC Monitor Utility

The following explains how to operate and set PLC Monitor Utility.
Start
Operating procedure
Select [Start]  [MELSOFT]  [PLC Monitor Utility].
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.)
7
Window
Item Description
Connection using logical Select this when using a logical station number.
station number
Logical station number Select the logical station number set in Communication Settings Utility.
Connection without logical Select this when not using a logical station number.
station number
[Wizard] button Click this to start Communication Setting Wizard and set the transfer setting.
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 PROGRAMMING
7.3 Debugging 139
• 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 in Communication Settings 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.
7 PROGRAMMING
140 7.3 Debugging
Device Batch tab
This tab is used to monitor the specified device.
Window
(1)
(2) (3) (4)

7
Item Description
Device Enter the device name to be monitored in batch.
For the X and Y devices of FXCPUs and FX5CPUs, enter the device number in octal.
[Start monitor] button ([Stop Click this to 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.
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 Displays 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 146 Write to Device screen)
"*" flickers under the scroll button during monitoring.
(2) Target CPU name Displays the communication target CPU name specified in Communication Setting Wizard.
(3) Communication route Displays such information as the network type, network number, start I/O address and station number.
information
(4) Logical station number Displays the logical station number set for the utility setting type.
This number is not displayed when the program setting type is used.
7 PROGRAMMING
7.3 Debugging 141
• 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.
• Device data of QSCPU cannot be changed.
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 an 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 Click this to 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
Real number (single precision): Set to the real number (single precision) 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 Displays the buffer memory status.
For the bit device status, 1 indicates an ON status and 0 an OFF status.
7 PROGRAMMING
142 7.3 Debugging
Item Description
information
(4) Logical station number Displays the logical station number set for the utility setting type.
This number is not displayed when the program setting type is used.

• Monitoring for an FX5CPU are not supported.
• The devices cannot be monitored during GOT gateway device communication.
7 PROGRAMMING
7.3 Debugging 143
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 Click this to register the device to be monitored.
The following screen is displayed by clicking the [Register device] button.
Page 145 The "Register device" screen
[Delete device] button Click this to delete the device to be monitored.
[Clear device] button Click this to delete all devices registered in device entry monitor from the monitor screen.
[Start monitor] button Click this to start (stop) monitor.
([Stop monitor] button)
(1) Monitor screen Displays the device status.
The "Write to Device" screen is displayed by clicking the device name. (Page 146 Write to Device screen)
information
(4) Logical station Displays the logical station number set for the utility setting type.
number This number is not displayed when the program setting type is used.
7 PROGRAMMING
144 7.3 Debugging
■ 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
Real number (single precision): Set to the real number (single precision) display. 7
[Register] button Click this to register the device.
[Close] button Click this to close the dialog box.
• When monitoring the setting values of the timers and counters, indirectly specify the data registers.
7 PROGRAMMING
7.3 Debugging 145
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].
• Double-click the monitor screen of the corresponding tab.
Window
Item Description
Bit device Device Enter the device name.
[Force ON] button Click this to forcibly change the specified device to the ON status.
[Force OFF] button Click this to forcibly change the specified device to the OFF status.
[Toggle force] button Click this to 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 Click this to write the set data.
• When using an RnSFCPU, writing to the safety device cannot be performed in the safety mode. Page
154 When access target is an RnSFCPU and RnPSFCPU
• When using a QSCPU, [Device write] cannot be selected.
• When using a QSCPU, buffer memory cannot be written.
7 PROGRAMMING
146 7.3 Debugging
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
Item Description
PC Time Displays the time of the personal computer. (Write disabled)
PLC Time Displays the time of the programmable controller CPU.
[Set] button Click this to write the "PLC Time" information to the programmable controller CPU.
[Close] button Click this to close the "Time setting" screen.
7
Time setting is not available when either of the following communications is selected.
• GOT gateway device communication (An error occurs.)
For a QSCPU, the clock data cannot be changed.
7 PROGRAMMING
7.3 Debugging 147
PART 2 DETAILED
SPECIFICATIONS OF
PROGRAMS
This part explains the details of the properties and functions used in a program.
8 ACCESSIBLE DEVICES AND DEVICE TYPES
9 PROPERTIES OF CONTROLS
10 PROPERTY SETTINGS OF COMMUNICATION ROUTES
11 FUNCTIONS
12 SAMPLE PROGRAMS
13 ERROR CODES
148
This chapter explains the accessible devices in each communication route and device types that can be specified with the
functions.
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(Page
192 PROPERTY SETTINGS OF COMMUNICATION ROUTES)
8.1 Accessible Devices

This section shows accessible devices in each communication route in a list.
Accessibility list
For the accessibility list using relayed network in each communication route, refer to the following:
Page 192 PROPERTY SETTINGS OF COMMUNICATION ROUTES
For serial communication

The following table shows the accessible devices for serial communication.
When access target is a programmable controller CPU 8

: Accessible, : Inaccessible
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)        

8.1 Accessible Devices 149
(Q mode)
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)        
*2
File register (R)        *3
(ZR)    *2    
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 Q12DCCPU-V (Basic mode) cannot be accessed.

*2 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.

150 8.1 Accessible Devices
When access target is a Motion CPU

R16MT/R32MT Q172D/Q173D Q172DS/Q173DS
Input relay (X)   
Output relay (Y)   
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)   
CPU buffer Multiple CPU area device  *1 *1
memory access (U3En\G)
device
CPU buffer memory   
(U3En\G)
CPU buffer memory fixed   
scan communication area
(U3En\HG) 8
Module access device (U*\G)   

For Ethernet communication
The following table shows the accessible devices for Ethernet communication.
When access target is a programmable controller CPU


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)         
*3
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/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)         
File register (R)     *4    
(ZR)     *4    
Refresh device for modules (RD)         

RCPU RCCPU LHCPU FX5CP QCPU (Q QCCP LCPU QSCPU FXCP
*1
U mode) U U*2
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)
Module access device (U*\G)     *5    
*1 Writing to device data cannot be performed.

*2 For the supported FXCPUs and devices, refer to the manuals of Ethernet module and setting software.

When access target is an RnSFCPU and RnPSFCPU
The safety devices described in the following table can be used when access target is an RnSFCPU and RnPSFCPU.
The safety mode is read-only. An attempt to write into the safety device will cause an error.

RnSFCPU, RnPSFCPU
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) 

For an accessible device list of a Motion CPU, refer to the following:
Page 151 When access target is a Motion CPU

For CPU COM communication
The following table shows the accessible devices CPU COM communication.


RCPU RCCPU LHCPU FX5CP QCPU QCCPU LCPU QSCP FXCP
U (Q mode) U U
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)         
*1
Link register (W)         
Timer (T) Contact (TS)         
Coil (TC)          8
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)         
Coil (LTC)         
Coil (LCC)         
(LST)
Coil (LSTC/LSC)         
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)     *2    *3
(ZR)     *2    

RCPU RCCPU LHCPU FX5CP QCPU QCCPU LCPU QSCP FXCP
U (Q mode) U U
Link output (J*\Y)         
Link relay (J*\B)         
Link register (J*\W)         
(J*\SW)
Module access device (U*\G)     *4    *5

*5 Only FX3U(C)CPU can be accessed.


For CPU USB communication
The following table shows the accessible devices for CPU USB communication.


RCP RCCP LHCP FX5CP QCPU QCCP LCPU QSCPU* FXCPU
1
U U U U(FX5U (Q mode) U
J)
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)         
Link relay (B)      *3   
Data register (D)         *2
Link register (W)      *3   
Timer (T) Contact (TS)         *2 8
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)         
Coil (LTC)         
Coil (LCC)         
(LST) Coil (LSTC/LSC)         
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
File register (R)     *4    *2
(ZR)     *4    

RCP RCCP LHCP FX5CP QCPU QCCP LCPU QSCPU* FXCPU
1
U U U U(FX5U (Q mode) U
J)
Link output (J*\Y)         
Link relay (J*\B)         
Link register (J*\W)         
(J*\SW)
Special direct buffer memory (U*\G)     *5    

When access target is an RnSFCPU and RnPSFCPU

For an accessible device list of an RnSFCPU and RnPSFCPU, refer to the following:
Page 154 When access target is an RnSFCPU and RnPSFCPU


For CC-Link communication
The following table shows the accessible devices for CC-Link communication.
For another station access


(Q mode)
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
*2
Link register (W)        
Timer (T) Contact (TS)        *1
Coil (TC)        *1 8
Present value (TN)        *1
Counter (C) Contact (CS)        *1
Coil (CC)        *1
Present value (CN)        *1
Coil (STC/SC)        
Coil (LTC)        
Coil (LCC)        
(LST)
Coil (LSTC/LSC)        
Present value (LSTN/        
LSN)
Step relay (S)        *1
Direct input (DX)        
Accumulator (A)        
Index register (Z)        *1
(V)        *1
File register (R)    *3    
(ZR)    *3    

(Q mode)
Link output (J*\Y)        
Link relay (J*\B)        
Link register (J*\W)        
(J*\SW)
Special direct buffer memory (U*\G)    *4    *5
*1 Only FX3G(C)CPU and 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 (Data write area for CC-Link) WW RWw
Remote register (Data 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

For CC-Link system RS-232 interface communication
The following table shows the accessible devices for CC-Link system RS-232 interface communication.


(Q mode)
Input relay (X)        
Output relay (Y)        
Internal relay (M)        
Latch relay (L)        
Annunciator (F)        
Edge relay (V)        
Link relay (B)     *1   
Data register (D)        
*1
Link register (W)        
Timer (T) Contact (TS)        
Coil (TC)         8
Present value (TN)        
Counter (C) Contact (CS)        
Coil (CC)        
Present value (CN)        
Coil (STC/SC)        
Coil (LTC)        
Coil (LCC)        
(LST)
Coil (LSTC/LSC)        
Present value (LSTN/LSN)        
Step relay (S)        
Direct input (DX)        
Accumulator (A)        
Index register (Z)        
(V)        
File register (R)    *2    
(ZR)    *2    

(Q mode)
Link output (J*\Y)        
Link relay (J*\B)        
Link register (J*\W)        
(J*\SW)
Special direct buffer memory (U*\G)        



For MELSECNET/H communication
The following table shows the accessible devices for MELSECNET/H communication.


RCPU RCCP LHCPU QCPU QCCPU LCPU QSCPU*1 FXCP
U (Q mode) U
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)        
*2
Link register (W)        
Timer (T) Contact (TS)        
Coil (TC)         8
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)        
Coil (LTC)        
Coil (LCC)        
Long retentive timer (LST) Contact (LSTS/LSS)        
Coil (LSTC/LSC)        
Link special relay (SB)        
Link special register (SW)        
Step relay (S)        
Direct input (DX)        
Accumulator (A)        
(V)        
File register (R)    *3    
(ZR)    *3    

RCPU RCCP LHCPU QCPU QCCPU LCPU QSCPU*1 FXCP
U (Q mode) U
Link output (J*\Y)        
Link relay (J*\B)        
Link register (J*\W)        
Link special register (J*\SW)        
Special direct buffer memory (U*\G)    *4    


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


For CC-Link IE Controller Network communication
The following table shows the accessible devices for CC-Link IE Controller Network communication.


RCPU RCCPU LHCPU QCPU QCCP LCP QSCPU* FXCPU
1
(Q mode) U U
Input relay (X)        
Output relay (Y)        
Latch relay (L)        
Annunciator (F)        
Edge relay (V)        
Link relay (B)     *2   
Data register (D)        
*2
Link register (W)        
Coil (TC)         8
Coil (CC)        
Coil (STC/SC)        
Coil (LTC)        
Coil (LCC)        
Coil (LSTC/LSC)        
Step relay (S)        
Direct input (DX)        
Accumulator (A)        
(V)        
File register (R)    *3    
(ZR)    *3    

RCPU RCCPU LHCPU QCPU QCCP LCP QSCPU* FXCPU
1
(Q mode) U U
Link output (J*\Y)        
Link relay (J*\B)        
Link register (J*\W)        


Link relay B Link relay of own board
Link register W Link register of own board
Remote input X LX
Remote output Y LY
Buffer memory ML Buffer memory of own board


For CC-Link IE Field Network communication
The following table shows the accessible devices for CC-Link IE Field Network communication.


RCPU RCCPU LHCPU QCPU (Q QCCPU LCP QSCPU* FXCPU
1
mode) U
Input relay (X)        
Output relay (Y)        
Latch relay (L)        
Annunciator (F)        
Edge relay (V)        
Link relay (B)     *2   
Data register (D)        
*2
Link register (W)        
Coil (TC)         8
Coil (CC)        
Coil (STC/SC)        
Coil (LTC)        
Coil (LCC)        
Coil (LSTC/LSC)        
Step relay (S)        
Direct input (DX)        
Accumulator (A)        
(V)        
File register (R)    *3    
(ZR)    *3    

RCPU RCCPU LHCPU QCPU (Q QCCPU LCP QSCPU* FXCPU
1
mode) U
Link output (J*\Y)        
Link relay (J*\B)        
Link register (J*\W)        


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
Remote input X RX
Remote output Y RY
Buffer memory ML Buffer memory of own board


For GX Simulator2 communication
The accessible devices during GX Simulator2 communication depend on the device supported by GX Simulator2.
For details, refer to the following manual.
For GX Simulator3 communication

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
For MT Simulator2 communication

The accessible devices during MT Simulator2 communication depend on the device supported by MT Simulator2.
For an accessible device list of a Q motion CPU, refer to the following:
For GOT gateway device communication

Only the following device is accessible for GOT gateway device communication.
Device: Gateway device
Device name: EG

For GOT Transparent communication
The following table shows the accessible devices for GOT transparent communication.


RCPU RCCP LHCPU FX5CP QCPU QCCPU LCPU QSCP FXCPU
U U (Q mode) U
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)         
*1
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/SS)         
Coil (STC/SC)         
Present value (STN/SN)         
Long timer (LT) Contact (LTS)         
Coil (LTC)         
Present value (LTN)         
Coil (LCC)         
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)         
File register (R)     *2    *3
(ZR)     *2    

RCPU RCCP LHCPU FX5CP QCPU QCCPU LCPU QSCP FXCPU
U U (Q mode) U
Link output (J*\Y)         
Link relay (J*\B)         
Link register (J*\W)         
(J*\SW)
Special direct buffer memory (U*\G)     *4    *5



For inverter communication
The following table shows the accessible monitor types during inverter communication.
Monitor type (Decimal) Description
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
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
91 PID manipulated variable
92 Second PID set point
93 Second PID measured value
94 Second PID deviation
95 Second PID measured value 2
96 Second PID manipulated variable
97 Dancer main speed setting

For robot controller communication
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

8.2 Device Types
This section explains the devices that can be specified for functions.
• Specify devices with "device name + device number" for any of the following functions.
For the device numbers, note the differences between octal, decimal, and hexadecimal numbers.
Target functions: ReadDeviceBlock, ReadDeviceBlock2, WriteDeviceBlock, WriteDeviceBlock2,
ReadDeviceRandom, ReadDeviceRandom2, WriteDeviceRandom, WriteDeviceRandom2,
SetDevice, SetDevice2, GetDevice, GetDevice2
• When specifying bit devices for ReadDeviceBlock, ReadDeviceBlock2, WriteDeviceBlock, or
WriteDeviceBlock2, specify the device number with a multiple of 16.
• Local devices and file registers per program of programmable controller CPU cannot be accessed by
specifying a program name.
• Only the devices indicated in this section are supported. Do not use unsupported devices.
Common device types

The following device types are common to all communication routes except for the communication to an FX5CPU, GOT
gateway device communication, inverter communication, and robot controller communication.
Device Device name Device type Device number
Function input FX Bit device Decimal
Function output FY Bit device Decimal
Function register FD Word device*1 Decimal
Special relay SM Bit device Decimal
Special register SD Word device Decimal
Input relay X Bit device Hexadecimal*2
Output relay Y Bit device Hexadecimal*2
Internal relay M Bit device Decimal
Latch relay L Bit device Decimal
Annunciator F Bit device Decimal
Edge relay V Bit device Decimal
Link relay B Bit device Hexadecimal
Data register D Word device Decimal
Link register W Word device Hexadecimal
Timer*11 Contact TS Bit device Decimal
Coil TC Bit device Decimal
Present value TN Word device Decimal
Counter*11 Contact CS Bit device Decimal
Coil CC Bit device Decimal
Present value*3 CN Word device Decimal
Retentive timer*11 Contact STS/SS Bit device Decimal
Coil STC/SC Bit device Decimal
Present value STN/SN Word device Decimal
Link special relay SB Bit device Hexadecimal
Link special register SW Word device Hexadecimal
Accumulator A*4 Word device Decimal
Index register Z*4 Word device Decimal
*4
V Word device Decimal
File register R*5 Word device Decimal
ZR Word device Decimal

174 8.2 Device Types
Direct link*7*12 Link input J*\X*6 Bit device Hexadecimal
Link output J*\Y*6 Bit device Hexadecimal
*6
Link relay J*\B Bit device Hexadecimal
Link special relay J*\SB*6 Bit device Hexadecimal
*6
Link register J*\W Word device Hexadecimal
Link special register J*\SW*6 Word device Hexadecimal
Special direct buffer memory*8*9 U*\G***6*10 Word device Hexadecimal/Decimal
*1 4 words/1 point. For a bulk operation, the operation is performed continuously in units of one word. For a random operation, only the first
one word is read.
*2 For FXCPU, the device number is octal.
*3 For FXCPU, the value higher than or equal to 200 is 32-bit data.
*4 These devices cannot be used when E71 is relayed.
*5 When accessing FX series CPU other than FX3G(C)CPU and FX3U(C)CPU, specify the data register (D). The extended file register (R)
can be specified only when accessing FX3G(C)CPU or FX3U(C)CPU.
*6 For a direct specification, enter "\" between the direct specification and the device specification.
*7 J* specifies a network number.
*8 U* specifies a special module I/O number (hexadecimal), and G** specifies a buffer memory address (decimal).
(Example: When the special module I/O number is 200H and the buffer memory address is 100, the device name will be "U20\G100.")
*9 In a QCPU multiple CPU configuration, an error occurs if the shared memory of the host QCPU is specified.
Regardless of whether the CPU is a host CPU or other CPU, an error occurs if data is written to the shared memory.
*10 For FXCPU, this device name can be used on FX3U(C)CPU only.
*11 When accessing the device using a label of system label Ver.2, the label of system label Ver.2 which is corresponding to a device for
contact/coil/present value is required to be defined.
*12 The device is not available in LHCPU.

8.2 Device Types 175
When access target is an RCPU or LHCPU
The devices described in the following table can be used when access target is an RCPU or LHCPU.
Long timer*1 Contact LTS Bit device Decimal
Coil LTC Bit device Decimal
Present value LTN Double word device Decimal
*1
Long counter Contact LCS Bit device Decimal
Coil LCC Bit device Decimal
Present value LCN Double word device Decimal
Retentive long timer*1 Contact LSTS/LSS Bit device Decimal
Coil LSTC/LSC Bit device Decimal
Present value LSTN/LSN Double word device Decimal
Long index register LZ Double word device Decimal
Refresh device for modules RD Word device Decimal
When access target is an RnSFCPU and RnPSFCPU (Safety devices)

The safety devices described in the following table can be used when access target is an RnSFCPU and RnPSFCPU.
The safety mode is read-only. An attempt to write into the safety device will cause an error.
Safety input SA\X Bit device Hexadecimal
Safety output SA\Y Bit device Hexadecimal
Safety internal relay SA\M Bit device Decimal
Safety link relay SA\B Bit device Hexadecimal
Safety timer SA\T Bit device/Word device Decimal
Safety retentive timer SA\ST Bit device/Word device Decimal
Safety counter SA\C Bit device/Word device Decimal
Safety data register SA\D Word device Decimal
Safety link register SA\W Word device Hexadecimal
Safety special relay SA\SM Bit device Decimal
Safety special register SA\SD Word device Decimal
When access target is an R motion CPU or Q motion CPU

The devices described in the following table can be used only when the access target is an R motion CPU or a Q motion CPU.
Motion registers # Word device Decimal

When access target is an FX5CPU
The devices described in the following table can be used when access target is an FX5CPU.
Special relay SM Bit device Decimal
Special register SD Word device Decimal
Input relay X Bit device Octal
Output relay Y Bit device Octal
Internal relay M Bit device Decimal
Latch relay L Bit device Decimal
Annunciator F Bit device Decimal
Link relay B Bit device Hexadecimal
Data register D Word device Decimal
Link register W Word device Hexadecimal
Timer Contact TS Bit device Decimal
Coil TC Bit device Decimal
Present value TN Word device Decimal
Counter Contact CS Bit device Decimal
Coil CC Bit device Decimal
Present value CN Word device Decimal
Retentive timer Contact STS/SS Bit device Decimal
Coil STC/SC Bit device Decimal
Present value STN/SN Word device Decimal
Long counter Contact LCS Bit device Decimal
Coil LCC Bit device Decimal 8
Present value LCN Bit device Decimal
Link special relay SB Bit device Hexadecimal
Link special register SW Word device Hexadecimal
Step relay S Bit device Decimal
Index register Z Word device Decimal
File register R Word device Decimal
Long index register LZ Double word device Decimal
Module access device U*\G Word device Decimal

For CC-Link communication
The devices described in the following table can be used when accessing to the own board with CC-Link communication.
These devices cannot be used for other communication routes.
Device Device name Device type Device number Remarks
Link special relay (for CC-Link) SB Bit device Hexadecimal Link special relay of own board
Link special register (for CC-Link) SW Word device Hexadecimal Link special register of own board
Remote input X Bit device Hexadecimal RX
Remote output Y Bit device Hexadecimal RY
Remote register (Data write area for CC- WW Word device Hexadecimal RWw
Link)
Remote register (Data read area for CC- WR Word device Hexadecimal RWr
Link)
Buffer memory ML Word device Hexadecimal Buffer memory of own station CC-Link module
Random access buffer MC Word device Hexadecimal Random access buffer in buffer memory of own
station CC-Link module
For MELSECNET/H communication

The devices described in the following table can be used when accessing to the own board with MELSECNET/H
communication.
Link relay B Bit device Hexadecimal Link relay of own board
Link register W Word device Hexadecimal Link register of own board
Link special relay SB Bit device Hexadecimal Link special relay of own board
Link special register SW Word device Hexadecimal Link special register of own board
Link input X Bit device Hexadecimal LX
Link output Y Bit device Hexadecimal LY
For CC-Link IE Controller Network communication

The devices described in the following table can be used when accessing to the own board with CC-Link IE Controller
Network communication.
Link relay B Bit device Hexadecimal Link relay of own board
Link register W Word device Hexadecimal Link register of own board
Link input X Bit device Hexadecimal LX
Link output Y Bit device Hexadecimal LY
Buffer memory ML Word device Hexadecimal Buffer memory of own board

For CC-Link IE Field Network communication
The devices described in the following table can be used when accessing to the own board with CC-Link IE Field Network
communication.
Remote register W Word device Hexadecimal 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)
Remote input X Bit device Hexadecimal RX
Remote output Y Bit device Hexadecimal RY
Buffer memory ML Word device Hexadecimal Buffer memory of own board
For GOT gateway device communication

The following list shows how to specify the device name used for GOT gateway device communication
Gateway device*1 EG Word device Decimal
*1 If a gateway device to which a programmable controller CPU device is not assigned is read, the read data becomes 0.
For inverter communication/robot controller communication

For the monitor types used for inverter communication/robot controller communication, refer to the following:
Page 172 For inverter communication
8
Page 173 For robot controller communication

Device extension representations
The following table shows applicability of device extension representation.
These representations cannot be used for ReadDeviceBlock and WriteDeviceBlock.
: Applicable : Not applicable
Device extension Target CPU
representation RCPU RCCPU R motion CPU LHCPU FX5CPU
Digit specification *1 *6  *1 
(Example: K4M0)
Bit specification *2   *2 
(Example: D0.1)
Index setting (Example: *3   *3 
M100Z0)
Device extension Target CPU GOT Inverter Robot

representation QCPU (Q QCCPU LCPU QSCP FXCP Q motion controller
mode) U U CPU
Digit specification  *6       
(Example: K4M0)*4
Bit specification *7  *7 *7 *7    
(Example: D0.1)
Index setting (Example:         
M100Z0)*5
*1 FX/FY, FD/SD, V, T/C/ST, LT/LC/LST, W/SW, G, Z, R/ZR and LZ cannot be specified.

*2 Z, T/C/ST, LT/LC/LST and LZ cannot be specified.
*3 FX/F, Z and LZ cannot be specified.
*4 FX/FY, DX/DY, and T/C/ST (contact, coil) cannot be specified.
*5 FX/FY, DX/DY, T/C/ST (contact, coil), Z, and S cannot be specified.
*6 The bit devices whose device numbers are multiple of 16 can only be used for digit specification.
(For link direct devices, the digit specification only for K4 and K8 is supported.)
*7 Z, V, and T/C/ST (present value) cannot be specified.

9
This chapter explains the property list of controls and details of the respective controls.
9.1 Property List

The following table shows the properties of each control.
Control name Property name
ACT Control ActUtlType ActLogicalStationNumber
ActUtlType64
ActPassword
ActUtlDataLogging*1
ActUtlDataLogging64*1
ActProgType ActBaudRate
ActProgType64
ActConnectUnitNumber
ActProgDataLogging*1
ActProgDataLogging64*1 ActControl
ActCpuTimeOut
ActCpuType
ActDataBits
ActDestinationIONumber
ActDestinationPortNumber
ActDidPropertyBit
ActDsidPropertyBit
ActHostAddress
ActIntelligentPreferenceBit
ActIONumber
ActMultiDropChannelNumber
ActMxUnitSeries*2
ActNetworkNumber
ActParity
ActPacketType
ActPassword
ActPortNumber
ActProtocolType
ActSourceNetworkNumber
ActSourceStationNumber
ActStationNumber
ActStopBits
ActSumCheck
ActTargetSimulator
ActThroughNetworkType
ActTimeOut
ActUnitNumber
ActUnitType
ActSupportMsg 
ActSupportMsg64
9.1 Property List 181
Control name Property name
ACT Control ActProgType ActATCommand*3
ActProgType64
ActConnectWay*3
ActProgDataLogging*1
ActProgDataLogging64*1 ActATCommandPasswordCancelRetryTimes*3
ActATCommandResponseWaitTime*3
ActCallbackCancelWaitTime*3
ActCallbackDelayTime*3
ActCallbackNumber*3
ActCallbackReceptionWaitingTimeOut*3
ActConnectionCDWaitTime*3
ActConnectionModemReportWaitTime*3
ActDialNumber*3
ActDisconnectionCDWaitTime*3
ActDisconnectionDelayTime*3
ActLineType*3
ActOutsideLineNumber*3
ActPasswordCancelResponseWaitTime*3
ActTransmissionDelayTime*3
.NET Control DotUtlType ActLogicalStationNumber
DotUtlType64
ActPassword
DotSupportMsg 
DotSupportMsg64
*1 Only supported by RCPUs.

*2 The property value is set automatically, and it cannot be changed.
*3 Properties for modem communication. They can be used in only MX Component Version 4, and cannot be used in MX Component
Version 5 or later.
182 9.1 Property List
9.2 Details of Control Properties
This section explains the details of properties set when creating a user program.
9
Properties of utility setting type controls

The following table shows the properties of the ActUtlType control and DotUtlType control.
Property name (Type) Description Default value
ActLogicalStationNumber(LONG) A logical station number set in Communication Settings Utility. (Applicable setting range: 0 to 0 (0x00)
1023)
ActPassword(BSTR) Specify a password to disable the password set to the password protected modules.*1 Empty
This setting is ignored when a password protected module is not used.
*1 Characters exceeded the maximum number of characters for the password are ignored.
If a character other than alphanumeric is specified, a character code conversion error (0xF1000001) occurs at the execution of the Open
function.
Properties of program setting type controls

The following table shows the properties of the ActProgType control.
ActMxUnitSeries(LONG) Specify the series of connection target module. 0 (0x00)
The property value is set automatically, and it cannot be changed.
■Property value
0 (0x00): Specify programmable controller/motion controller/GOT.
1 (0x01): Specify inverter.
2 (0x02): Specify robot controller.
ActNetworkNumber(LONG) Specify the network number for MELSECNET/H. (Specify "0" (0x00) when specifying the host 0 (0x00)
station.)
Specify a network number for accessing other station with GX Simulator.
Specify the following value for the multi-drop connection (via Q series-compatible C24).
■Property value of ActIntelligentPreferenceBit
0 (0x00): Specify the own network.
1 (0x01): Specify another network of multi-drop destination.
ActStationNumber(LONG) Specify the station number for MELSECNET/H or CC-Link. (Specify "255" (0xFF) when specifying 255 (0xFF)
the host station.)
Specify the station number for accessing other station with GX Simulator. For GX Simulator3,
specify a system number.
Specify the following value for the multi-drop connection (via Q series-compatible C24).
■Property value of ActIntelligentPreferenceBit
0 (0x00): Specify the own network.
1 (0x01): Specify another network of multi-drop destination.
For inverter communication, specify the inverter station number (0 to 31) to be connected.
ActUnitNumber(LONG) Specify the module number of the serial communication module or the station number when the 0 (0x00)
target is the Q series-compatible intelligent function module.
This setting is invalid when the target is not a serial communication or Q series-compatible
intelligent function module.
For multi-drop link, specify the module number of the target serial communication module.
ActConnectUnitNumber(LONG) Specify the module number of serial communication module, QE71, or Q series-compatible E71. 0 (0x00)
For multi-drop link, specify the module number of the requesting serial communication module.
For multi-drop link via CPU COM communication, however, the module number of the requesting
station is not required. (Specify "0" (0x00))
Specify "0" (0x00) for other than multi-drop link.
For QE71 and Q series-compatible E71, specify the relay target station number. (Fixed to "0"
(0x00) for access within the own network)
For access to another network via MELSECNET/10, specify the station number set in the
parameter of the connected Ethernet module.
ActIONumber(LONG) Specify the module I/O number. 1023 (0x3FF)
For multi-drop link or intelligent function module access, specify the actual I/O number (start I/O
number divided by 16) of the target serial communication module or intelligent function module.
(For multi-drop link, specify the I/O number of the relayed or requesting station)
Specify "992" (0x3E0) to "1023" (0x3FF) when making access to another station via the host
station CPU or network.
9.2 Details of Control Properties 183
ActCpuType(LONG) When the ActMxUnitSeries property is set to '0' (programmable controller/motion controller) 34
Specify the target CPU to communicate with. (CPU_Q02CPU)
In the parameter, specify the CPU type in the following table.
Page 187 ActCpuType(LONG): When the ActMxUnitSeries property is set to '0'
(programmable controller/motion controller)
When the ActMxUnitSeries property is set to '1' (inverter)
Specify the target Inverter to communicate with.
Page 188 ActCpuType(LONG): When the ActMxUnitSeries property is set to '1' (inverter)
When the ActMxUnitSeries property is set to '2' (robot)
Specify the target robot to communicate with.
Page 188 ActCpuType(LONG): When the ActMxUnitSeries property is set to '2' (robot)
ActPortNumber(LONG) Specify the connection port number of personal computer. 1 (PORT_1)
When an Ethernet module is connected, set any value as a port number of the requesting source
(personal computer).
When "=0" was specified as a port number, the Station No.  IP information system should be
the automatic response system. (When the system other than the automatic response system via
QE71 is selected, set the fixed value "5001.")
When the network board is used, specify the first board as PORT_1, and the second and
subsequent boards as PORT_2, PORT_3, and so on.
Page 189 ActPortNumber(LONG)
ActBaudRate(LONG) Specify the baud rate for serial communication. 19200
■Property value (Property window input value) (BAUDRATE_19
BAUDRATE_300 (300): 300 bps 200)
BAUDRATE_600 (600): 600 bps
BAUDRATE_1200 (1200): 1200 bps
BAUDRATE_2400 (2400): 2400 bps
BAUDRATE_4800 (4800): 4800 bps
BAUDRATE_9600 (9600): 9600 bps
BAUDRATE_19200 (19200): 19200 bps
BAUDRATE_38400 (38400): 38400 bps
BAUDRATE_57600 (57600): 57600 bps
BAUDRATE_115200 (115200): 115200 bps
For inverter communication, specify the property value greater than BAUDRATE_4800 (4800).
ActDataBits(LONG) Specify the number of bits of the byte data sent and received for serial communication. 8 (DATABIT_8)
■Property value (Property window input value)
DATABIT_7 (7): 7 bits
DATABIT_8 (8): 8 bits
For robot controller, specify the character size.
ActParity(LONG) Specify the parity system used for serial communication. 1
■Property value (Property window input value) (ODD_PARITY)
NO_PARITY (0): No parity
ODD_PARITY (1): Odd
EVEN_PARITY (2): Even
ActStopBits(LONG) Specify the number of stop bits used for serial communication. 0
■Property value (Property window input value) (STOPBIT_ONE
STOPBIT_ONE (0): 1 stop bit )
STOPBITS_TWO (2): 2 stop bits
For robot controller, specify the following setting.
ONESTOPBIT (0): 1 stop bit
ONE5STOPBITS (1): 1.5 stop bits
TWOSTOPBITS (2): 2 stop bits
ActControl(LONG) Specify the control setting of the signal line. 8
Page 189 ActControl(LONG) (TRC_DTR_OR
_RTS)
ActHostAddress(BSTR) Pointer which indicates the connection host name (IP address) for Ethernet communication. 1.1.1.1
When setting the first character of each octet to '0,' the value is processed as octal number.
ActCpuTimeOut(LONG) Specify the CPU watchdog timer for Ethernet communication. (Unit: Multiplied by 250 ms) 0 (0x00)
For FXCPU/inverter, specify the transmission waiting time for serial communication of FXCPU/
inverter. (Unit: Multiplied by 10 ms)
For robot controller, specify the transmission timeout time. (1000 to 30000 ms)
184 9.2 Details of Control Properties
ActTimeOut(LONG) Set the time-out value of communication between the personal computer and programmable 10000
controller/inverter. (Unit: ms)
For robot controller, specify the transmission timeout time. (5000 to 120000 ms) 9
A time-out processing may be performed internally depending on the communication route in MX
Component.
Page 645 Time-Out Periods
ActSumCheck(LONG) Specify whether sum check is applied or not. 0
This setting is valid for serial communication module only. (NO_SUM_CHE
■Property value (Property window input value) CK)
NO_SUM_CHECK (0): Without sum check
SUM_CHECK (1): With sum check
ActSourceNetworkNumber(LONG) Specify the requesting network number when the QE71 or Q series-compatible E71 is specified. 0 (0x00)
Specify the same network number (which is specified in the network parameter) as that of the
connected QE71 or Q series-compatible E71.
ActSourceStationNumber(LONG) Specify the requesting station number (personal computer side station number) when the QE71 0 (0x00)
or Q series-compatible E71 is specified.
Set the setting to avoid setting the same station number as that of the QE71 set within the same
Ethernet loop.
ActDestinationPortNumber(LONG) Specify the port number of the target when Ethernet communication is specified. 0 (0x00)
When accessing another network, specify the relay destination port number.
For the system other than the automatic response system, set the following setting.
■Setting
R series-compatible E71 (TCP/IP) - MELSOFT connection: Fixed to "5002"
R series-compatible E71 (TCP/IP) - OPS connection: Depending on network parameter
R series-compatible E71(UDP/IP): Fixed to "5001"
QE71(UDP/IP): Fixed to "5001"
Q series-compatible E71 (TCP/IP) - Other than redundant CPU: Fixed to "5002"
Q series-compatible E71 (TCP/IP) - MELSOFT connection*1: Fixed to "5002"
Q series-compatible E71 (TCP/IP) - OPS connection*1: Depending on network parameter
Q series-compatible E71(UDP/IP): Fixed to "5001"
ActDestinationIONumber(LONG) For multi-drop connection (via R series-compatible C24/Q series-compatible C24/L series- 0 (0x00)
compatible C24/CC-Link), specify the actual I/O number (start I/O number divided by 16) of the
last access target station. (When the target is an intelligent function module)
Specify "992" (0x3E0) to "1023" (0x3FF) when making access to another station via the host
station CPU or network.
ActMultiDropChannelNumber(LONG) For multi-drop connection (via R series-compatible C24/Q series-compatible C24/L series- 0 (0x00)
compatible C24/CC-Link), specify the multi-drop connection channel number (CH1/CH2).
For robot controller, specify the retry count at communication error. (0 to 10 times)
This setting is invalid for other connections.
ActThroughNetworkType(LONG) Specify whether MELSECNET/10 is included in the relayed network when accessing other station 0 (0x00)
via network.
■Property value
0 (0x00): MELSECNET/10 is not included.
1 (0x01): MELSECNET/10 is included.
For robot controller, specify the protocol to be used (communication method). (Procedural (0)/
Nonprocedural (1))
ActIntelligentPreferenceBit(LONG) For multi-drop connection (via R series-compatible C24/Q series-compatible C24/L series- 0 (0x00)
compatible C24/CC-Link), specify whether to relay the network of the multi-drop link destination.
(To differentiate the own network module.)
■Property value
0 (0x00): Another network of multi-drop link destination is not accessed.
1 (0x01): Another network of multi-drop link destination is accessed.
ActDidPropertyBit(LONG) For accessing the Q series-compatible host station intelligent function module (intelligent function 1 (0x01)
module mounted on the host station CPU), the setting of "ActUnitNumber" is not necessary by
invalidating the following setting. (Specify the property with the setting of "ActIONumber" only.)
■Property value
0 (0x00): Module number is validated.
1 (0x01): Module number is invalidated.
ActDsidPropertyBit(LONG) For multi-drop connection (via R series-compatible C24/Q series-compatible C24/L series- 1 (0x01)
compatible C24/CC-Link), the setting of "ActDestinationIONumber" is not necessary by
invalidating the following setting.
However, when the following setting is invalidated, validate the setting of "ActDidPropertyBit."
(Specify the property with the setting of "ActUnitNumber.")
■Property value
0 (0x00): I/O number of the last access target station is validated.
1 (0x01): I/O number of the last access target station is invalidated.
ActPacketType(LONG) Specify whether CR/LF exists or not. 1(CRLF_CR)
CRLF_NONE (0): Without CR/LF
CRLF_CR (1): With CR
CRLF_CRLF (2): With CR/LF
ActPassword(BSTR)*2 Specify a password to disable the password set to the password protected modules.*3*4*5 Empty
This setting is ignored when a password protected module is not used.
ActTargetSimulator(LONG) Specify the connection destination GX Simulator2 in start status. 0 (0x00)
When connecting to FXCPU, specify "0" (0x00).
■Property value
0 (0x00): None
(When only one simulator is in start status, connects to the simulator in start status. When
multiple simulators are in start status, search for the simulators in start status and connect them in
alphabetical order.)
1 (0x01): Simulator A
2 (0x02): Simulator B
3 (0x03): Simulator C
4 (0x04): Simulator D
Specify the PLC number of the connection destination GX Simulator3 in start status.
Specify the connection destination MT Simulator2 in start status.
■Property value
2 (0x02): Simulator No.2
ActUnitType(LONG) Specify the module type connected to the physical port. 0x13
Page 189 ActUnitType(LONG) (UNIT_QNCPU)
ActProtocolType(LONG) Specify the communication protocol type of the module (board) to be connected. 0x04
Page 191 ActProtocolType(LONG) (PROTOCOL_S
ERIAL)
ActATCommand They can be used in only MX Component Version 4, and cannot be used in MX Component 
ActATCommandPasswordCancelRetry Version 5 or later.
Times
ActATCommandResponseWaitTime
ActCallbackCancelWaitTime
ActCallbackDelayTime
ActCallbackNumber
ActCallbackReceptionWaitingTimeOut
ActConnectionCDWaitTime
ActConnectionModemReportWaitTime
ActConnectWay
ActDialNumber
ActDisconnectionCDWaitTime
ActDisconnectionDelayTime
ActLineType
ActOutsideLineNumber
ActPasswordCancelResponseWaitTim
e
ActTransmissionDelayTime
*1 For details, refer to the following:

Q Corresponding Ethernet Interface Module User's Manual (Basic)
*2 This property can be used for Ethernet communication.
*3 The setting of ActPassword is not necessary if a password is not set.
*4 Characters exceeded the maximum number of characters for the password are ignored.
*5 If characters other than alphanumeric are specified, a character code conversion error (0xF1000001) occurs at the execution of the
Open function.
■ ActCpuType(LONG): When the ActMxUnitSeries property is set to '0' (programmable
controller/motion controller)
Property value (Property window input value) Target CPU 9
CPU type Dec. Hex.
CPU_R00CPU 4609 0x1201 R00CPU
CPU_R04ENCPU 4104 0x1008 R04ENCPU
CPU_R08ENCPU 4105 0x1009 R08ENCPU
CPU_R08PCPU 4354 0x1102 R08PCPU
CPU_R08PSFCPU 4369 0x1111 R08PSFCPU
CPU_R08SFCPU 4386 0x1122 R08SFCPU
CPU_R16ENCPU 4106 0x100A R16ENCPU
CPU_R32ENCPU 4107 0x100B R32ENCPU
CPU_R120CPU 4101 0x1005 R120CPU
CPU_R120ENCPU 4108 0x100C R120ENCPU
CPU_R16MTCPU 4113 0x1011 R16MTCPU
CPU_R32MTCPU 4114 0x1012 R32MTCPU
CPU_R12CCPU_V 4129 0x1021 R12CCPU-V
CPU_L04HCPU 4625 0x1211 L04HCPU
CPU_Q00UJCPU 128 0x80 Q00UJCPU
CPU_Q00UCPU 129 0x81 Q00UCPU
CPU_Q03UDCPU 112 0x70 Q03UDCPU
CPU_Q03UDECPU 144 0x90 Q03UDECPU
CPU_Q03UDVCPU 209 0xD1 Q03UDVCPU
CPU_Q04UDHCPU 113 0x71 Q04UDHCPU
CPU_Q04UDEHCPU 145 0x91 Q04UDEHCPU
CPU_Q04UDPVCPU 71 0x47 Q04UDPVCPU
CPU_Q12PRHCPU 67 0x43 Q12PRHCPU
Property value (Property window input value) Target CPU
CPU type Dec. Hex.
CPU_Q25PRHCPU 68 0x44 Q25PRHCPU
CPU_Q26UDPVCPU 74 0x4A Q26UDPVCPU
CPU_Q100UDEHCPU 154 0x9A Q100UDEHCPU
CPU_L02SCPU 163 0xA3 L02SCPU
CPU_L02CPU 161 0xA1 L02CPU
CPU_L26CPUBT 162 0xA2 L26CPU-BT
CPU_Q12DC_V 88 0x58 Q12DCCPU-V
CPU_Q24DHC_V 89 0x59 Q24DHCCPU-V
CPU_Q24DHC_LS 91 0x5B Q24DHCCPU-LS
CPU_Q24DHC_VG 92 0x5C Q24DHCCPU-VG
CPU_Q26DHC_LS 93 0x5D Q26DHCCPU-LS
CPU_QS001CPU 96 0x60 QS001CPU
CPU_Q172DCPU 1573 0x625 Q172DCPU
CPU_Q173DCPU 1574 0x626 Q173DCPU
CPU_Q172DSCPU 1578 0x62A Q172DSCPU
CPU_Q173DSCPU 1579 0x62B Q173DSCPU
CPU_FX3SCPU 522 0x20A FX3SCPU
CPU_FX3GCPU 521 0x209 FX3G(C)CPU
CPU_FX3UCCPU 520 0x208 FX3U(C)CPU
CPU_FX5UCPU 528 0x0210 FX5UCPU
CPU_FX5UJCPU 529 0x0211 FX5UJCPU
CPU_BOARD 1025 0x401 For own board access*1
*1 Except for CPU boards and AF boards.
■ ActCpuType(LONG): When the ActMxUnitSeries property is set to '1' (inverter)

Property value (Property window input value) Target inverter
CPU type Dec. Hex.
INV_A800 7776 0x1E60 A800
■ ActCpuType(LONG): When the ActMxUnitSeries property is set to '2' (robot)

Property value (Property window input value) Target robot
CPU type Dec. Hex.
UCPU_CRD700 77825 0x13001 CRnD-7xx/CR75x-D
■ ActPortNumber(LONG)
Property value (Property window input value) Description
Port number Dec. Hex. 9
PORT_1 1 0x01 Communication port 1
PORT_10 10 0x0A Communication port 10
■ ActControl(LONG)
Property value (Property window input value) Description
Control setting Dec. Hex.
TRC_DTR 1 0x01 DTR control
TRC_RTS 2 0x02 RTS control
TRC_DRT_AND_RTS 7 0x07 DTR control and RTS control
TRC_DTR_OR_RTS 8 0x08 DTR control or RTS control
■ ActUnitType(LONG)
Module type Connection system Value
UNIT_RJ71C24 R series-compatible C24 module direct connection 0x1000
R series-compatible C24 connection via GOT2000 series
UNIT_QJ71C24 Q series-compatible C24 module direct connection 0x19
Q series-compatible C24 connection via GOT2000 series
UNIT_LJ71C24 L series-compatible C24 module direct connection 0x54
L series-compatible C24 connection via GOT2000 series
UNIT_FX485BD FX extended port (RS-485) connection 0x24
UNIT_RJ71EN71 Via R series-compatible E71 connection (IP specification) 0x1001
UNIT_RJ71EN71_DIRECT Via R series-compatible E71 connection (Direct connection) 0x1005
UNIT_QJ71E71 Q series-compatible E71 Ethernet port connection/direct connection 0x1A
UNIT_LJ71E71 L series-compatible E71 module connection 0x5C
UNIT_RETHER RCPU Ethernet port connection (IP specification) 0x1002
UNIT_LHETHER LHCPU Ethernet port connection (IP specification)
UNIT_RETHER_DIRECT RCPU Ethernet port direct connection 0x1003
UNIT_LHETHER_DIRECT LHCPU Ethernet port direct connection
UNIT_FXVETHER FX5CPU Ethernet port connection 0x2001
UNIT_FXVETHER_DIRECT FX5CPU Ethernet port direct connection 0x2002
UNIT_LNETHER LCPU Ethernet port connection 0x52
UNIT_LNETHER_DIRECT LCPU Ethernet port direct connection 0x53
UNIT_QNETHER QCPU Ethernet port connection 0x2C
UNIT_QNETHER_DIRECT QCPU Ethernet port direct connection 0x2D
UNIT_RJ71GN11 RJ71GN11-T2 module for RCPU IP specified connection 0x1006
UNIT_RJ71GN11_DIRECT RJ71GN11-T2 module for RCPU direct connection 0x1007
UNIT_NZ2GF_ETB Ethernet adapter module (NZ2GF-ETB) connection 0x59
UNIT_NZ2GF_ETB_DIRECT Ethernet adapter module (NZ2GF-ETB) direct connection 0x5A
UNIT_FXETHER FXCPU Ethernet adapter (FX3U-ENET-ADP) via hub 0x4A
UNIT_FXETHER_DIRECT FXCPU Ethernet adapter (FX3U-ENET-ADP) direct connection 0x4B
UNIT_FXVENET FX5CPU Ethernet module (FX5-ENET, FX5-ENET/IP) IP specified 0x2004
connection
UNIT_FXVENET_DIRECT FX5CPU Ethernet module (FX5-ENET, FX5-ENET/IP) direct connection 0x200E
Module type Connection system Value
UNIT_FXVCPU FX5CPU Serial port connection 0x2000
UNIT_QNCPU QCPU (Q mode) RS232C port direct connection 0x13
GOT2000 series QCPU (Q mode) direct connection
UNIT_LNCPU LCPU-RS232C port direct connection 0x50
GOT2000 series LCPU direct connection
UNIT_QNMOTION Q motion CPU-RS232C port direct connection 0x1C
UNIT_FXCPU FXCPU-RS422 port direct connection 0x0F
FXCPU USB direct connection
GOT2000 series FXCPU direct connection
UNIT_RUSB RCPU USB port direct connection 0x1004
UNIT_LHUSB LHCPU USB port direct connection
UNIT_FXVUSB FX5CPU USB port direct connection 0x200C
UNIT_QNUSB QCPU (Q mode) USB port direct connection 0x16
UNIT_LNUSB LCPU USB port direct connection 0x51
UNIT_QSUSB QSCPU (Safety programmable controller) USB port connection 0x29
UNIT_QNMOTIONUSB Q motion CPU USB port direct connection 0x1D
UNIT_MNETHBOARD MELSECNET/H board connection 0x1E
UNIT_MNETGBOARD CC-Link IE Controller Network board connection 0x2B
UNIT_CCIEFBOARD CC-Link IE Field Network board connection 0x2F
UNIT_CCLINKBOARD CC-Link Ver.2 board connection 0x0C
UNIT_G4QNCPU Q series-compatible AJ65BT-G4-S3 module direct connection 0x1B
UNIT_SIMULATOR2*1 Simulator (GX Simulator2) connection 0x30
Simulator (MT Simulator2) connection
UNIT_SIMULATOR3 Simulator (GX Simulator3) connection 0x31
UNIT_A900GOT GOT2000 series connection 0x21
UNIT_GOT_RJ71EN71 R series-compatible E71 connection via GOT2000 series 0x1051
UNIT_GOT_QJ71E71 Q series-compatible E71 connection via GOT2000 series 0x40
UNIT_GOT_LJ71E71 L series-compatible E71 connection via GOT2000 series 0x5D
UNIT_GOT_RETHER RCPU Ethernet port connection via GOT2000 series 0x1052
UNIT_GOT_QNETHER QCPU Ethernet port connection via GOT2000 series 0x41
UNIT_GOT_LNETHER LCPU Ethernet port connection via GOT2000 series 0x55
UNIT_GOT_NZ2GF_ETB Ethernet adapter module (NZ2GF-ETB) connection via GOT2000 series 0x5B
UNIT_GOT_FXETHER FXCPU Ethernet adapter (FX3U-ENET-ADP) connection via GOT2000 0x61
series
UNIT_GOT_FXENET FXCPU Ethernet module (FX3U-ENET(-L)) connection via GOT2000 0x62
series
UNIT_GOT_FXVENET FX5CPU Ethernet module (FX5-ENET, FX5-ENET/IP) connection via 0x2008
GOT2000 series
UNIT_GOT_FXVCPU FX5CPU Serial port connection via GOT2000/1000 series 0x2005
UNIT_GOTETHER_FXVCPU FX5CPU Ethernet port connection via GOT2000/1000 series 0x2006
UNIT_GOT_FXVETHER Built-in Ethernet port FX5CPU connection via GOT2000/1000 series 0x2007
UNIT_GOTETHER_RJ71C24 RCPU Ethernet port (RS422) connection via GOT2000 series 0x1061
UNIT_GOTETHER_QNCPU QCPU (Q mode) Ethernet port (RS422) connection via GOT2000 series 0x56
UNIT_GOTETHER_LNCPU LCPU Ethernet port (RS232C) connection via GOT2000 series 0x57
UNIT_GOTETHER_FXCPU FXCPU Ethernet port connection via GOT2000 series 0x60
UNIT_GOTETHER_QN_ETHER GOT Ethernet transparent (Ethernet-GOT-Ethernet-QnCPU) 0x6F
connection
*1 When the CPU type is Q motion CPU, connected to MT Simulator2. Other than that, connected to GX Simulator2.
■ ActProtocolType(LONG)
Communication protocol type Connection system Value
PROTOCOL_SERIAL Via serial port 0x04(4) 9
PROTOCOL_USB Via USB port 0x0D(13)
PROTOCOL_TCPIP Via TCP/IP 0x05(5)
PROTOCOL_UDPIP Via UDP/IP 0x08(8)
PROTOCOL_MNETH Via MELSECNET/H board 0x0F(15)
PROTOCOL_MNETG Via CC-Link IE Controller Network board 0x14(20)
PROTOCOL_CCIEF Via CC-Link IE Field Network board 0x15(21)
PROTOCOL_CCLINK Via CC-Link 0x07(7)
PROTOCOL_USBGOT Via USB port and GOT 0x13(19)
PROTOCOL_SHAREDMEMORY Via shared memory server (Simulator) 0x06(6)
COMM_RS232C*1 Inverter RS-232C communication 0x00(0)
COMM_USB *1 Inverter USB communication 0x01(1)
RC_PROTOCOL_SERIAL Robot controller RS-232C communication 0x01(1)
RC_PROTOCOL_USB Robot controller USB communication 0x04(4)
RC_PROTOCOL_TCPIP Robot controller Ethernet (TCP/IP) communication 0x02(2)
*1 The communication protocol type can be used when ActMxUnitSeries is 1 (0x01).
10 PROPERTY SETTINGS OF COMMUNICATION
ROUTES
This chapter explains the details of accessible communication routes and property settings.
10.1 Serial Communication

Serial communication when the connected station is R series-
compatible C24 (1)
When a relayed module other than the connected station side R series-compatible C24 exists
Configuration
Connected station R Series -

Relayed module
CPU compatible C24
Relayed network
Relayed station
Personal computer Relayed module
CPU
Accessibility and property patterns

(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station CPU

RCPU R motion CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1*3
(1) (1) CC IE TSN (2)    
CC IE Control (2)*2 (2)   
CC IE Field
MELSECNET/H     
Ethernet (2)  (2)  
Serial communication (3)  (3)  
CC-Link (4) (4) (4)  

RCPU R motion CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1) (1)*1*3 CC IE TSN      
CC IE Control (2)  (2)*2   
CC IE Field
MELSECNET/H (2)     
Ethernet (2)  (2)   
Serial communication (3)*4  (3)   
CC-Link (4)  (4)   
*1 Relayed station CPUs cannot be accessed via R motion CPU.

*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 unit cannot be accessed.

Property list
The following table shows the property settings of communication routes.
The setting is not necessary for those properties without description.
Property Default value Property patterns
(1) (2)*1 (3) (4) 10
ActBaudRate 19200 Match to the setting of R series-compatible C24.
(BAUDRATE_19200)
ActConnectUnitNumber 0 (0x00) Connected station side module station number
ActControl 8 Depending on the used cable.
(TRC_DTR_OR_RTS
)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station side Target station side
■For single CPU ■For single CPU
• Fixed to 1023 • Fixed to 1023
(0x3FF) (0x3FF)
■For multiple CPUs ■For multiple CPUs
• Connected CPU: • Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
■For redundant CPU
• No specification:
1023 (0x3FF)
ActDidPropertyBit 1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
ActDsidPropertyBit 1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0 (0x00) Fixed to 0 (0x00)
ActIONumber*2 1023 (0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU relayed module I/O relayed module I/O
(0x3FF) • Fixed to 1023 address address
■For multiple CPUs (0x3FF)
• Connected CPU: ■For multiple CPUs
1023 (0x3FF) • Connected CPU:
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
■For redundant CPU • No. 4: 995 (0x3E3)
• No specification: ■For redundant CPU
1023 (0x3FF) • No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*3 number
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActParity 1 (ODD_PARITY) Fixed to ODD_PARITY
ActPortNumber 1 (PORT_1) Personal computer side COM port number
ActProtocolType 0x04 PROTOCOL_SERIAL
(PROTOCOL_SERIA
L)
ActPacketType 0x01 PACKET_PLC1
(PACKET_PLC1)
ActHostAddress 1.1.1.1 Fixed to NULL
ActCpuTimeOut 0 (0x00) Fixed to 0 (0x00)
ActDataBits 8 (DATABIT_8) Fixed to 8 (0x08)
ActStopBits 0 (STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0 (NO_SUM_CHECK) Fixed to 0 (0x00)
ActSourceNetworkNumber 0 (0x00) Fixed to 0 (0x00)
ActSourceStationNumber 0 (0x00) Fixed to 0 (0x00)

(1) (2)*1 (3) (4)
ActDestinationPortNumber 0 (0x00) Fixed to 0 (0x00)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Target station side Fixed to 255 (0xFF) Fixed to 255 (0xFF)
module station number
ActThroughNetworkType 0 (0x00) • MELSECNET/10 is not included.: 0 (0x00)
• MELSECNET/10 is included.: 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station side Target station side
module station number module station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_RJ71C24
*1 Note the following considerations when accessing via Ethernet module (R series-compatible E71).
 For ActNetworkNumber and ActStationNumber, specify the value set in the parameter setting of the target station side R series-
compatible E71.
 Set "Station No.  IP information" in the parameter setting of R series-compatible E71. When setting the parameter, specify the setting
other than the automatic response system (any of the IP address calculation system, table conversion system, and combined system)
for "Station No.  IP information system."
*2 For the I/O address, specify the value obtained by dividing the actual start I/O number by 16.
*3 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

Serial communication when the connected station is R series-
compatible C24 (2)
When performing multi-drop link on the connected station side R series-compatible C24 with the relayed module
Configuration 10

CPU compatible C24
Multi-drop link
Relayed network
Relayed station
CPU

Connected station Relayed network Relayed station CPU

CPU
RCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
Independent (1) Serial communication (2)    
mode*1
Synchronous  (3)    
mode*2

CPU
RCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
Independent (1) Serial communication (2)*3  (2)   
mode*1
Synchronous  (3)*3  (3)   
mode*2
*1 For the Independent mode, set the following parameters.

CH1 side: Operation setting of Transmission setting = Independent (0), Communication protocol setting = 0
CH2 side: Operation setting of Transmission setting = Independent (0)
*2 For the Synchronous mode, set the following parameters.
CH2 side: Operation setting of Transmission setting = Synchronous (1), Communication protocol setting = 0
When the connected station side R series-compatible C24 is set to the synchronous mode, always validate
(turn ON) "sum check (SW06)" for the transmission specification software switch setting of the R series-
compatible C24 parameter.
If it is invalidated (OFF), a communication error occurs and the communication is disabled.

Property list
(1) (2) (3)
ActBaudRate 19200 Match to the setting of R series-compatible C24.
(BAUDRATE_19200)
ActConnectUnitNumber 0 (0x00) Connected station side module station number Target station side module
station number
(TRC_DTR_OR_RTS
)
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00)
■For single CPU
• Fixed to 1023 (0x3FF)
■For multiple CPUs
• Connected CPU: 1023
(0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActDidPropertyBit 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActIONumber*1 1023 (0x3FF) ■For single CPU Connected station side relayed Target station side
• Fixed to 1023 (0x3FF) module I/O address ■For single CPU
■For multiple CPUs • Fixed to 1023 (0x3FF)
• Connected CPU: 1023 ■For multiple CPUs
(0x3FF) • Connected CPU: 1023
• No. 1: 992 (0x3E0) (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0 (0x00) Fixed to 0 (0x00) Multi-drop channel number Fixed to 0 (0x00)
*2
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00)

ActParity 1 (ODD_PARITY) Fixed to ODD_PARITY
(PROTOCOL_SERIA
L)
(PACKET_PLC1)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Target station side module Fixed to 0 (0x00)
station number

(1) (2) (3)
1: Channel 1 10
2: Channel 2

Serial communication when the connected station is Q series-
compatible C24 (1)
When a relayed module other than the connected station side Q series-compatible C24 exists
Configuration
Connected station Q Series - Relayed module

CPU compatible C24
Relayed network
Relayed station Relayed module

Personal computer
CPU


QCPU (Q QCCP Q motion RCPU RCCPU R motion CPU LHCPU FX5CPU
mode) U CPU
(1) (1)*6 (1)*1 CC IE TSN     
CC IE Control     
CC IE Field
Ethernet     
Serial communication     
CC-Link     

QCPU (Q QCCP Q motion QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) U CPU mode) CPU
(1) (1)*6 (1)*1 CC IE TSN      
CC IE Control (2) (2)*2 (2)*3 (2)*2 (2)*2 
CC IE Field
MELSECNET/H (2) (2)  (2) (2) 
Ethernet (2)   (2) (2) 
Serial communication (3)*4  (3)  (3) 
CC-Link (4) (4) (4)  (4) (4)*5
*1 Relayed station CPUs cannot be accessed via Q motion CPU.

*2 Since CC-Link IE Field Network is not supported, R motion CPU, 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.
*5 Supported by FX3G(C)CPU and FX3U(C)CPU within the own network only.

Property list
(1) (2)*1 (3) (4) 10
ActBaudRate 19200 Match to the setting of Q series-compatible C24.
(BAUDRATE_19200)
(TRC_DTR_OR_RTS
)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
• Control system: 976
(0x3D0)
1023 (0x3FF)
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
1023 (0x3FF)
*3 number
module network
number
ActParity 1 (ODD_PARITY) Match to the setting of Q series-compatible C24.
ActProtocolType 0x04 PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIA
L)

(1) (2)*1 (3) (4)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_QJ71C24 (0x19)
*1 Note the following considerations when accessing via Ethernet module (Q series-compatible E71).
 For ActNetworkNumber and ActStationNumber, specify the value set in the parameter setting of the target station side Q series-
compatible E71.
 Set "Station No.  IP information" in the parameter setting of Q series-compatible E71. When setting the parameter, specify the setting
*2 For the I/O address, specify the value of the actual start I/O number divided by 16.
1: Channel 1
2: Channel 2

Serial communication when the connected station is Q series-
compatible C24 (2)
When performing multi-drop link on the connected station side Q series-compatible C24 with the relayed module
Configuration 10
Connected station Q Series -

CPU compatible C24
Multi-drop link
Relayed network

Personal computer
CPU


CPU
QCPU (Q mode), RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU*3
Independent (1)*2 Serial communication     
mode*1
Synchronous      
mode*1

CPU
QCPU (Q mode), QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
QCCPU*3 mode)
Independent (1)*2 Serial communication (2)*2  (2)   
mode*1
Synchronous  (3)*2  (3)   
mode*1
*1 Indicates the CH2 side setting. (The CH1 side is fixed to the independent mode.)
When the connected station side Q series-compatible C24 is set to the synchronous mode, always validate
(turn ON) "sum check (SW06)" for the transmission specification software switch setting of the Q series-

Property list
(1) (2) (3)
ActBaudRate 19200 (BAUDRATE_19200) Match to the setting of Q series-compatible C24.
ActControl 8 (TRC_DTR_OR_RTS) Depending on the used cable.
■For single CPU
Fixed to 1023 (0x3FF)
(0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
• No specification: 1023
(0x3FF)
ActIONumber*1 1023 (0x3FF) ■For single CPU Connected station side Target station side
• Fixed to 1023 (0x3FF) relayed module I/O address ■For single CPU
• No. 1: 992 (0x3E0) (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber*2 0 (0x00) Fixed to 0 (0x00) Multi-drop channel number Fixed to 0 (0x00)
ActParity 1 (ODD_PARITY) Match to the setting of Q series-compatible C24.
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_SERIAL (0x04)
station number
1: Channel 1
2: Channel 2

Serial communication when the connected station is L series-
compatible C24 (1)
When a relayed module other than the connected station side L series-compatible C24 exists
Configuration 10
Connected station L Series -

Relayed module
CPU compatible C24
Relayed network

Personal computer
CPU

Connected Relayed network Relayed station CPU

station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*1     
CC-Link     

station CPU
LCPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
(1) CC IE TSN      
CC IE Field*1 (4) (4)*2 (4)   
MELSECNET/H      
Ethernet (4)  (4)   
CC-Link (3) (3) (3)   
*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.

Property list
(1) (2) (3) (4)
ActBaudRate 19200 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
(BAUDRATE_19200) BAUDRATE_115200
ActDataBits 8 (DATABIT_8) Fixed to 8 (DATABIT_8)
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
ActIONumber*1 1023 (0x3FF) Fixed to 1023 (0x3FF) Connected station Connected station Target station side
side relayed module I/ side relayed module I/ ■For single CPU
O address O address • Fixed to 1023
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
ActMultiDropChannelNumber 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00) Fixed to 0 (0x00)
*2 number
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station side
module network
number
ActPacketType 0x01 (PACKET_PLC1) Fixed to 0x01 (PACKET_PLC1)
ActParity 1 (ODD_PARITY) Fixed to 1 (ODD_PARITY)
(PROTOCOL_SERIAL)

(1) (2) (3) (4)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
module station
number
ActStopBits 0 (STOPBIT_ONE) Fixed to 0 (STOPBIT_ONE)
ActSumCheck 0 (NO_SUM_CHECK) Fixed to 0 (NO_SUM_CHECK) 10
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
module station module station
number number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_LJ71C24 (0x54)
1: Channel 1
2: Channel 2

Serial communication when the connected station is L series-
compatible C24 (2)
When performing multi-drop link on the connected station side L series-compatible C24 with the relayed module
Configuration

CPU compatible C24
Multi-drop link
Relayed network
Relayed station
CPU


CPU
Independent (1)*3 Serial communication     
mode*1
Synchronous      
mode*2

CPU
LCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
Independent (1)*3 Serial communication (2)*3  (2)   
mode*1
Synchronous  (3)*3  (3)   
mode*2
*1 For the Independent mode, set the following parameters.

CH2 side: Operation setting of Transmission setting = Independent (0)
*2 For the Synchronous mode, set the following parameters.
CH2 side: Operation setting of Transmission setting = Synchronous (1), Communication protocol setting = 0
When the connected station side L series-compatible C24 is set to the synchronous mode, always validate
(turn ON) "sum check (SW06)" for the transmission specification software switch setting of the L series-

Property list
(1) (2) (3) 10
ActBaudRate 19200 (BAUDRATE_19200) Match to the setting of L series-compatible C24.
■For single CPU
(0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActIONumber*1 1023 (0x3FF) Fixed to 1023 (0x3FF) Connected station side Target station side
relayed module I/O address ■For single CPU
(0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*2

ActParity 1 (ODD_PARITY) Match to the setting of L series-compatible C24.
station number
1: Channel 1
2: Channel 2

Serial communication when the connected station is FX extended
port
Configuration
Connected station FX extended port

CPU
Relayed network
Relayed station
Personal computer FX extended port Relayed module
CPU


station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
FXCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1) CC IE TSN      
CC IE Control      
CC IE Field
Ethernet      
Serial communication      (1)*1
CC-Link      
*1 FX0CPU, FX0SCPU, FX1CPU, FXUCPU, and FX2CCPU cannot be accessed.

Property list
(1) 10
ActBaudRate 19200 (BAUDRATE_19200) Match to the setting of FX extended port
ActCpuTimeOut 0 (0x00) Any value specified by user in 10ms units
ActDataBits 8 (DATABIT_8) Match to the setting of FX extended port
ActParity 1 (ODD_PARITY) Match to the setting of FX extended port
ActStopBits 0 (STOPBIT_ONE) Match to the setting of FX extended port
ActSumCheck 0 (NO_SUM_CHECK) Match to the setting of FX extended port
ActUnitNumber 0 (0x00) Target station side module station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FX485BD (0x24)

10.2 Ethernet Communication
Ethernet communication when the connected station is R series-
compatible E71 (TCP)
Configuration

Relayed module
CPU compatible E71
Relayed network

Personal computer
CPU


(1) (1)*1*2 CC IE TSN     
CC IE Field
Ethernet (2)  (2)  
CC-Link (4) (4) (4)  

mode)
(1) (1)*1*2 CC IE TSN      
CC IE Field
Ethernet (2)  (2)   
Serial communication (3)  (3)   
CC-Link (4)  (4)   


210 10.2 Ethernet Communication
Property list
(1) (2)*1 (3) (4) 10
ActConnectUnitNumber 0 (0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
ActDestinationIONumber*3 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station side Target station side
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
1023 (0x3FF)
ActDestinationPortNumber 0 (0x00) 5002 for MELSOFT connection
Any port number for OPS connection.*2
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
*4 number
ActNetworkNumber*5 0 (0x00) Target station side Target station side Connected station side Connected station side
module network module network R series-compatible R series-compatible
number number E71 network number E71 network number
ActPassword Empty Password set to R series-compatible E71 on the connected station side
ActProtocolType 0x04 PROTOCOL_TCPIP (0x05)
(PROTOCOL_SERIA
L)
(PACKET_PLC1)
ActPortNumber 1 (PORT_1) Personal computer side port number
ActBaudRate 19200 Fixed to 0 (0x00)
(BAUDRATE_19200)
ActControl 8 Fixed to 0 (0x00)
(TRC_DTR_OR_RTS
)
ActParity 1 (ODD_PARITY) Fixed to 0 (0x00)

10.2 Ethernet Communication 211
(1) (2)*1 (3) (4)
ActSourceNetworkNumber 0 (0x00) Personal computer side network number
ActSourceStationNumber*6 0 (0x00) Personal computer side station number
ActStationNumber*5 255 (0xFF) Target station side Target station side Connected station side Connected station side
module station number module station number R series-compatible R series-compatible
E71 station number E71 station number
ActThroughNetworkType 0 (0x00) Fixed to 0 (0x00)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_RJ71EN71 (0x1001)
compatible E71.
*2 When using the OPS connection function for Redundant CPU, specify any port number that was set to the network parameter of the
CPU. (The setting range is 1025  port number  4999 or 5003  port number  65534)
1: Channel 1
2: Channel 2
*5 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.
*6 Specify the personal computer side station number to avoid the same station number set for R series-compatible E71 within the same
Ethernet loop.

Ethernet communication when the connected station is R series-
compatible E71 (UDP)
Configuration
10
Relayed module
CPU compatible E71
Relayed network

Personal computer
CPU


*1 *2*3
(1) (1) CC IE TSN     
CC IE Field
Ethernet (2)  (2)  
CC-Link (4) (4) (4)  

mode)
(1)*1 (1)*2*3 CC IE TSN      
CC IE Field
Ethernet (2)  (2)   
CC-Link (4)  (4)   
*1 Relayed station CPUs cannot be accessed when directly connecting to an R series-compatible E71.

Property list
(1) (2)*1 (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
1023 (0x3FF)
ActDestinationPortNumber 0 (0x00) For communication with IP address specified: 5001
For direct communication without IP address specified: 5003
ActHostAddress 1.1.1.1 For communication with IP address specified: Host name or IP address of the connected station side
For direct communication without IP address specified: 255.255.255.255
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
*3
number
ActPassword Empty Password set to R series-compatible E71 on the connected station side
ActPortNumber 1 (PORT_1) For communication with IP address specified: Personal computer side COM port number
For direct communication without IP address specified: Unused
ActProtocolType 0x04 PROTOCOL_UDPIP (0x08)
(PROTOCOL_SERIA
L)
(PACKET_PLC1)
(BAUDRATE_19200)
(TRC_DTR_OR_RTS
)

(1) (2)*1 (3) (4)
10
ActUnitType 0x13 (UNIT_QNCPU) • For communication with IP address specified: UNIT_RJ71EN71 (0x1001)
• For direst communication without IP address specified: UNIT_RJ71EN71_DIRECT (0x1005)
compatible E71.
1: Channel 1
2: Channel 2
*4 When the property pattern is (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.
*5 Specify the personal computer side station number to avoid the same station number set for R series-compatible E71 within the same
Ethernet loop.

Ethernet communication when the connected station is Q series-
Configuration

CPU compatible E71
Relayed network
Personal computer Relayed station Relayed module

CPU


QCPU (Q QCCP QSCP Q motion RCPU RCCPU R motion CPU LHCPU FX5CP
mode) U U CPU U
(1) (1)*6 (1)*2 (1)*1*2 CC IE TSN     
CC IE Field
CC-Link     

QCPU (Q QCCP QSCP Q motion QCPU (Q QCCP LCP QSCP Q motion FXCP
mode) U U CPU mode) U U U CPU U
(1) (1)*6 (1)*2 (1)*1*2 CC IE TSN      
CC IE Control (2) (2)*3 (2)*4 (2)*2*3 (2)*3 
CC IE Field
MELSECNET/H (2) (2)  (2)*2 (2) 
Ethernet (2)   (2)*2 (2) 
Serial communication (3)*5  (3)*5  (3) 
CC-Link (4) (4) (4)  (4) 
*1 Only Q172D, Q173D, Q172DS and Q173DS can be accessed.

*2 Relayed station CPUs cannot be accessed via QSCPU or Q motion CPU.

Property list
(1) (2) (3) (4) 10
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
Any port number for OPS connection*1
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
*3
number
module network module network Q series-compatible Q series-compatible
ActPassword Empty Password set to Q series-compatible E71 on the connected station side
(PROTOCOL_SERIA
L)
module station number module station number Q series-compatible Q series-compatible
E71 network number E71 network number

(1) (2) (3) (4)
ActUnitType 0x13 UNIT_QJ71E71 (0x1A)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2
ActStationNumber.
*5 Specify the personal computer side station number to avoid the same station number set for Q series-compatible E71 within the same
Ethernet loop.

Ethernet communication when the connected station is Q series-
Configuration
10
CPU compatible E71
Relayed network

CPU


QCPU (Q QCCP QSCP Q motion RCPU RCCPU R motion CPU LHCPU FX5CP
mode) U U CPU U
(1) (1)*6*7 (1)*2 (1)*1*2 CC IE TSN     
CC IE Field
CC-Link     

QCPU (Q QCCP QSCP Q motion QCPU (Q QCCP LCPU QSCP Q motion FXCP
mode) U U CPU mode) U U CPU U
(1) (1)*6*7 (1)*2 (1)*1*2 CC IE TSN      
CC IE Control (2) (2)*3 (2) *4
(2) *2*3
(2)*3

CC IE Field
MELSECNET/H (2) (2)  (2)*2 (2) 
Ethernet (2)   (2)*2 (2) 
CC-Link (4) (4) (4)  (4) 

*7 Since QCCPU is not supported by MELSOFT direct connection, Ethernet port direct connection is not applicable.

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
ActDestinationPortNumber 0 (0x00) 5001
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
*2 number
ActPassword Empty Password set to Q series-compatible E71 on the connected station side
ActPortNumber*4 1 (PORT_1) Personal computer side port number
(PROTOCOL_SERI
AL)

(1) (2) (3) (4)
ActUnitType 0x13 UNIT_QJ71E71 (0x1A)
(UNIT_QNCPU)
*1 For the I/O address, specify the value of the actual start I/O number divided by 16. 10
1: Channel 1
2: Channel 2
ActStationNumber.
*4 Do not use 1 to 1024 of ActPortNumber.
*5 Specify the personal computer side station number to avoid the same station number set for Q series-compatible E71 within the same
Ethernet loop.

Ethernet communication when the connected station is L series-
Configuration

Relayed module
CPU compatible E71
Relayed network
Relayed station
CPU

Connect Relayed network Relayed station CPU

ed
station
CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

ed
station
CPU
LCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU*1 FXCPU
mode)
(1) CC IE TSN      
CC IE Field
Ethernet (2)  (2)   
Serial communication (3)*2  (3)*2   
CC-Link (4)  (4)   


Property list
(1) (2) (3) (4) 10
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
Any port number for OPS connection*1
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
*3 number
module network module network L series-compatible L series-compatible
ActPassword Empty Password set to L series-compatible E71 on the connected station side
ActPortNumber 1 (PORT_1) Personal computer side port number
(PROTOCOL_SERIA
L)

(1) (2) (3) (4)
*5
ActSourceStationNumber 0 (0x00) Personal computer side station number
module station number module station number L series-compatible L series-compatible
ActUnitType 0x13 UNIT_LJ71E71 (0x5C)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2
ActStationNumber.
*5 Specify the personal computer side station number to avoid the same station number set for L series-compatible E71 within the same
Ethernet loop.

Ethernet communication when the connected station is L series-
Configuration
10
Relayed module
CPU compatible E71
Relayed network
Relayed station
CPU


ed
station
CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

ed
station
CPU
LCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU*1 FXCPU
mode)
(1) CC IE TSN      
CC IE Field
Ethernet (2)  (2)   
CC-Link (4)  (4)   


Property list
(1) (2) (3) (4)
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
ActMultiDropChannelNumb 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
er*2 number
ActPassword Empty Password set to L series-compatible E71 on the connected station side
(PROTOCOL_SERIA
L)

(1) (2) (3) (4)
*3
ActStationNumber 255 (0xFF) Target station side Target station side Connected station side Connected station side
• MELSECNET/10 is included.: 1 (0x01) 10
ActUnitType 0x13 UNIT_LJ71E71 (0x5C)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2
ActStationNumber.
*4 Do not use 1 to 1024 of ActPortNumber.
*5 Specify the personal computer side station number to avoid the same station number set for L series-compatible E71 within the same
Ethernet loop.

Ethernet communication when the connected station is an RCPU
(TCP)
Configuration
Connected station Relayed module

CPU
Relayed network

Personal computer
CPU


RCPU RCCPU R motion RCPU RCCPU R motion LHCPU FX5CPU
CPU CPU
(1) (1)*3 (1)*1*3 CC IE TSN (2)    
*2
CC IE Control (2) (2)   (2)*5
CC IE Field
Ethernet (2)*4  (2)*4  
Serial communication (3)*4  (3)*4  
CC-Link (4) (4) (4)  (4)

RCPU RCCPU R motion QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
CPU mode) CPU
(1) (1)*3 (1)*1*3 CC IE TSN      
CC IE Control (2)*4  (2)*2*4   
CC IE Field
MELSECNET/H (2)*4     
Ethernet (2)*4  (2)   
CC-Link (4)*4  (4)*4   

*4 RCCPU cannot be accessed because the communication route is not supported.
*5 Only CC-Link IE Field Network on which connected station CPU is RCPU can be accessed.

Property list
(1) (2)*1 (3) (4) 10
ActPortNumber 1 (PORT_1) Fixed to 0 (0x00)
(BAUDRATE_19200)
(TRC_DTR_OR_RTS
)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
1023 (0x3FF)
ActIntelligentPreferenceBit 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
• RCPU, R motion • RCPU, R motion
CPU, QCPU (Q CPU, QCPU (Q
mode), LCPU: 1 mode), LCPU: 1
(0x01) (0x01)
• Other than the • Other than the
above: 0 (0x00) above: 0 (0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
1023 (0x3FF)
*3 number
ActNetworkNumber*4 0 (0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActPassword Empty Password set to the connected station side
(PROTOCOL_SERIA
L)

(1) (2)*1 (3) (4)
*4
ActThroughNetworkType 0 (0x00) • MELSECNET/10 is not included.: 0 (0x00) MELSECNET/10 is not
• MELSECNET/10 is included.: 1 (0x01) included.: 0 (0x00)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_RETHER (0x1002)
*1 Note the following considerations when accessing via Ethernet module (Q series-compatible E71 or R series-compatible E71).
For ActNetworkNumber and ActStationNumber, specify the value set in the parameter setting of the target station side Q series-
compatible E71 or R series-compatible E71.
 Set "Station No.  IP information" in the parameter setting of Q series-compatible E71 or R series-compatible E71. When setting the
parameter, specify the setting other than the automatic response system (any of the IP address calculation system, table conversion
system, and combined system) for "Station No.  IP information system."
1: Channel 1
2: Channel 2
ActStationNumber.

Ethernet communication when the connected station is an RCPU
(UDP)
Configuration
10
CPU
Relayed network

Personal computer
CPU


RCPU RCCPU R motion RCPU RCCPU R motion LHCPU FX5CPU
CPU CPU
(1) (1)*3 (1)*1*3 CC IE TSN (2)    
CC IE Control (2)*2 (2)   (2)*5
CC IE Field
Ethernet (2)*4  (2)*4  
Serial communication (3)*4  (3)*4  
CC-Link (4) (4) (4)  (4)

RCPU RCCPU R motion QCPU QCCPU LCPU QSCPU Q motion FXCPU
CPU (Q CPU
mode)
(1) (1)*3 (1)*1*3 CC IE TSN      
CC IE Control (2)*4  (2)*2*4   
CC IE Field
MELSECNET/H (2)*4     
*4 *4
Ethernet (2)  (2)   
CC-Link (4)*4  (4)*4   

*4 RCCPU cannot be accessed because the communication route is not supported.

Property list
(1) (2)*1 (3) (4)
(BAUDRATE_19200)
(TRC_DTR_OR_RTS
)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
1023 (0x3FF)
• RCPU, R motion • RCPU, R motion
CPU, QCPU (Q CPU, QCPU (Q
(0x01) (0x01)
above: 0 (0x00) above: 0 (0x00)
ActHostAddress 1.1.1.1 • For communication with IP address specified: Host name or IP address of the connected station
side
• For direct communication without IP address specified: 255.255.255.255
ActDestinationPortNumber 0 (0x00) • For communication with IP address specified: 5006
• For direct communication without IP address specified: 5008
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
1023 (0x3FF)
*3 number
module network
number
(PACKET_PLC1)

(1) (2)*1 (3) (4)
(PROTOCOL_SERIA
L)
ActStationNumber*4 255 (0xFF) Fixed to 255 (0xFF) Target station side Fixed to 255 (0xFF) Fixed to 255 (0xFF) 10
ActUnitType 0x13 (UNIT_QNCPU) • For communication with IP address specified: UNIT_RETHER (0x1002)
• For direst communication without IP address specified: UNIT_RETHER_DIRECT (0x1003)
compatible E71.
1: Channel 1
2: Channel 2
ActStationNumber.

Ethernet communication when the connected station is an
LHCPU (TCP)
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
LHCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
LHCPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
(1) CC IE TSN      
CC IE Field
Serial communication      
CC-Link      

Property list
(1) 10
ActBaudRate 19200 (BAUDRATE_19200) Fixed to 0 (0x00)
ActControl 8 (TRC_DTR_OR_RTS) Fixed to 0 (0x00)
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00)
ActDidPropertyBit 1 (0x01) Fixed to 1 (0x01)
ActDsidPropertyBit 1 (0x01) Fixed to 1 (0x01)
ActIONumber 1023 (0x3FF) ■For single CPU
ActMultiDropChannelNumber 0 (0x00) Fixed to 0 (0x00)
ActPacketType 0x01 (PACKET_PLC1) PACKET_PLC1
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_TCPIP (0x05)
ActUnitNumber 0 (0x00) Fixed to 0 (0x00)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_LHETHER (0x1002)

LHCPU (UDP)
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
LHCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1) CC IE TSN      
CC IE Field
CC-Link      

Property list
(1) 10
ActHostAddress 1.1.1.1 • For communication with IP address specified: Host name or IP address of
the connected station side
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_UDPIP (0x08)
ActUnitType 0x13 (UNIT_QNCPU) • For communication with IP address specified: UNIT_LHETHER (0x1002)
• For direst communication without IP address specified:
UNIT_LHETHER_DIRECT (0x1003)

FX5CPU (TCP)
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
FX5CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
CC-Link     (3)

station CPU
FX5CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
(1) CC IE TSN      
CC IE Field
CC-Link      
*1 Only CC-Link IE Field Network can be accessed.

Property list
(1) (2) (3) 10
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) 1023 (0x3FF)
ActDidPropertyBit 1 (0x01) 1 (0x01) 0 (0x00)
ActDsidPropertyBit 1 (0x01) 1 (0x01) 0 (0x00)
ActIntelligentPreferenceBit 0 (0x00) 0 (0x00) 1 (0x01)
ActIONumber 1023 (0x3FF) 1023 (0x3FF) Module number of the
connected station
ActNetworkNumber 0 (0x00) 0 (0x00) Target station side module 0 (0x00)
network number
ActPortNumber 1 (PORT_1) 0 (0x00)
ActStationNumber 255 (0xFF) 255 (0xFF) Target station side module 255 (0xFF)
station number
ActStopBits 0 (STOPBIT_ONE) 0 (0x00)
ActSumCheck 0 (NO_SUM_CHECK) 0 (0x00)
ActThroughNetworkType 0 (0x00) 1 (0x01) 0 (0x00)
ActUnitNumber 0 (0x00) 0 (0x00) Target station side module
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXVETHER (0x2001)

FX5CPU (UDP)
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
CC-Link     (3)

station CPU
FX5CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1) CC IE TSN      
CC IE Field
CC-Link      

Property list
(1) (2) (3) 10
ActHostAddress 1.1.1.1 255.255.255.255
To select a PC side adapter, assign a tab character and the personal computer side IP
address after the connection target IP address.
ActIntelligentPreferenceBit 0 (0x00) Fixed to 0 (0x00) 1 (0x01)
connected station
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Target station side module Fixed to 0 (0x00)
network number
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_UDPIP (0x08)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Target station side module Fixed to 255 (0xFF)
station number
ActThroughNetworkType 0 (0x00) 1 (0x01) Fixed to 0 (0x00)
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Target station side module
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXVETHER_DIRECT (0x2002)

Ethernet communication when the connected station is a built-in
Ethernet port QCPU (TCP)
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
QnUDE(H)CPU RCPU RCCPU R motion CPU*4 LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
QnUDE(H)CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
(1) CC IE TSN      
*1 *2 *1 *1
CC IE Control (2) (2) (2) (2) (2) 
CC IE Field
MELSECNET/H (2) (2)  (2) (2) 
Ethernet (2)   (2) (2) 
CC-Link (4) (4) (4)  (4) 

station CPU
QCCPU RCPU RCCPU R motion CPU*4 LHCPU FX5CPU
(1)*4*5*6 CC IE TSN     
CC IE Field
CC-Link     

station CPU
QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1)*4*5*6 CC IE TSN      
CC IE Control (2) (2)*1 (2)*2 (2)*1 (2)*1 
CC IE Field 10
MELSECNET/H (2) (2)  (2) (2) 
CC-Link (4) (4) (4)  (4) 

station CPU
Q motion CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*7 CC IE TSN     
CC IE Field
CC-Link     

station CPU
Q motion CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1)*7 CC IE TSN      
CC IE Field
CC-Link      
*5 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.
*7 For Q172D, Q173D, Q172DS, and Q173DS, only CPU No.2 or later in a multiple CPU configuration can be accessed.

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
QCPU (Q mode), QCPU (Q mode),
LCPU: 1 (0x01) QCCPU, LCPU: 1
Other than the above: 0 (0x01)
(0x00) Other than the above: 0
(0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2
number
module network
number
(PROTOCOL_SERI
AL)
ActStationNumber*3 255 (0xFF) Fixed to 255 (0xFF) Target station side Fixed to 255 (0xFF) Fixed to 255 (0xFF)

(1) (2) (3) (4)
ActUnitType 0x13 UNIT_QNETHER (0x2C)
(UNIT_QNCPU)
0: Default channel of module 10
1: Channel 1
2: Channel 2
ActStationNumber.

Ethernet port QCPU (UDP)
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
QnUDE(H)CPU RCPU RCCPU R motion CPU*4 LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
QnUDE(H)CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1) CC IE TSN      
*1 *2 *1 *1
CC IE Control (2) (2) (2) (2) (2) 
CC IE Field
MELSECNET/H (2) (2)  (2) (2) 
Ethernet (2)   (2) (2) 
CC-Link (4) (4) (4)  (4) 

station CPU
QCCPU RCPU RCCPU R motion CPU*4 LHCPU FX5CPU
*4*5*6
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
QCCPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
(1)*4*5*6 CC IE TSN      
*1 *2 *1 *1
CC IE Control (2) (2) (2) (2) (2) 
CC IE Field
MELSECNET/H (2) (2)  (2) (2)  10
CC-Link (4) (4) (4)  (4) 

station CPU
Q motion CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*7 CC IE TSN     
CC IE Field
CC-Link     

station CPU
Q motion CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
*7
(1) CC IE TSN      
CC IE Field
CC-Link      
not supported.
*7 For Q172D, Q173D, Q172DS, and Q173DS, only CPU No.2 or later in a multiple CPU configuration can be accessed.

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
• For direct communication without IP address specified: Unused
ActHostAddress 1.1.1.1 For communication with IP address specified: Host name or IP address of the connected station side
For direct communication without specified IP address: The specification is invalid.
• QCPU (Q mode), • QCPU (Q mode),
• Other than the (0x01)
above: 0 (0x00) • Other than the
above: 0 (0x00)
ActIONumber*1 1023 (0x3FF) Target station side Target station side Connected station side Connected station side
■For single CPU ■For single CPU relayed module I/O relayed module I/O
• Fixed to 1023 • Fixed to 1023 address address
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2 number
module network
number
(PROTOCOL_SERI
AL)

(1) (2) (3) (4)
ActUnitType 0x13 • For communication with specified IP address: UNIT_QNETHER (0x2C)
(UNIT_QNCPU) • For direct communication without specified IP address: UNIT_QNETHER_DIRECT (0x2D)
*1 For the I/O address, specify the value of the actual start I/O number divided by 16. 10
1: Channel 1
2: Channel 2
ActStationNumber.

Ethernet port LCPU (TCP)
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN     
*1
CC IE Field     
CC-Link     

station CPU
(1) CC IE TSN      
CC IE Field*1 (4) (4)*2 (4)   
Ethernet (4)  (4)   
CC-Link (3) (3) (3)   
accessed.

Property list
(1) (2) (3) (4) 10
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
ActIntelligentPreferenceBit 0 (0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
(0x00)
ActIONumber*1 1023 (0x3FF) ■For single CPU Connected station side Connected station side Target station side
Fixed to 1023 (0x3FF) relayed module I/O relayed module I/O ■For single CPU
address address • Fixed to 1023
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2 number
ActNetworkNumber*3 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station side
module network
number

(1) (2) (3) (4)
(PROTOCOL_SERI
AL)
ActStationNumber*3 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
ActUnitType 0x13 UNIT_LNETHER (0x52)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2
ActStationNumber.

Ethernet port LCPU (UDP)
Configuration
10
CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN     
*1
CC-Link     

station CPU
mode)
(1) CC IE TSN      
CC IE Field*1 (4) (4)*2 (4)   
Ethernet (4)  (4)   
CC-Link (3) (3) (3)   
accessed.

Property list
(1) (2) (3) (4)
(BAUDRATE_19200)
(TRC_DTR_OR_RTS
)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
ActHostAddress 1.1.1.1 • For communication with IP address specified: Host name or IP address of the connected station side
above: 0 (0x00)
ActIONumber*1 1023 (0x3FF) ■For single CPU Connected station side Connected station side Target station side
Fixed to 1023 (0x3FF) relayed module I/O relayed module I/O ■For single CPU
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
ActMultiDropChannelNumbe 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00) Fixed to 0 (0x00)
r*2 number
ActNetworkNumber*3 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station side
module network
number

(1) (2) (3) (4)
(PROTOCOL_SERIA
L)
ActStationNumber*3 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
module station number 10
ActUnitType 0x13 (UNIT_QNCPU) • For communication with specified IP address: UNIT_LNETHER (0x52)
• For direct communication without specified IP address: UNIT_LNETHER_DIRECT (0x53)
1: Channel 1
2: Channel 2
ActStationNumber.

Ethernet communication when the connected station is a
Ethernet adapter module (TCP)
Configuration
Connected station CC-Link IE Field

Relayed module
CPU Network module
Ethernet adapter
Relayed network
module
Relayed station
CPU


station CPU
QnUDE(H)CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
mode)
(1) CC IE TSN      
CC IE Control (2) (2)*1 (2)*2   
CC IE Field
MELSECNET/H (2) (2)    
Ethernet (2)     
CC-Link (4) (4) (4)   

station CPU
(1) CC IE TSN     
CC IE Field*2     
CC-Link     

station CPU
(1) CC IE TSN      
*2 *1
CC IE Field (2) (2) (2)   
MELSECNET/H
Ethernet












10
CC-Link (4) (4) (4)   
accessed.

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
ActHostAddress 1.1.1.1 Host name or IP address of the Ethernet adapter module
*1
ActIONumber 1023 (0x3FF) ■For single CPU Target station side Connected station side Connected station side
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2
number
ActNetworkNumber*3 0 (0x00) Connected station side Target station side Connected station side Connected station side
CC-Link IE Field module network CC-Link IE Field CC-Link IE Field
Network module station number Network module station Network module station
number number number
(PROTOCOL_SERI
AL)
ActStationNumber*3 255 (0xFF) Connected station side Target station side Connected station side Connected station side
CC-Link IE Field module station number CC-Link IE Field CC-Link IE Field
Network module station Network module station Network module station
ActUnitType 0x13 UNIT_NZ2GF_ETB (0x59)
(UNIT_QNCPU)

1: Channel 1
2: Channel 2
*3 When the property pattern is (1), (3), or (4), specify the parameter value set for the CC-Link IE Field Network module on the
connected station side for ActNetworkNumber and ActStationNumber.
When the property pattern is (2), specify the value set in the target station side parameter for ActNetworkNumber and 10
ActStationNumber.

Ethernet communication when the connected station is a
Ethernet adapter module (UDP)
Configuration

Relayed module
CPU Network module
Ethernet adapter
Relayed network
module
Relayed station
CPU


station CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
mode)
(1) CC IE TSN      
CC IE Control (2) (2)*1 (2)*2   
CC IE Field
MELSECNET/H (2) (2)    
Ethernet (2)     
CC-Link (4) (4) (4)   

station CPU
(1) CC IE TSN     
CC IE Field*2     
CC-Link     

station CPU
(1) CC IE TSN      
*2 *1
CC IE Field (2) (2) (2)   
MELSECNET/H
Ethernet












10
CC-Link (4) (4) (4)   
accessed.

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
ActHostAddress 1.1.1.1 • For communication with specified IP address: Host name or IP address of the Ethernet adapter
module
• For direct communication without specified IP address: The specification is invalid.
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2 number
(PROTOCOL_SERI
AL)
ActUnitType 0x13 • For communication with specified IP address: UNIT_NZ2GF_ETB (0x59)
(UNIT_QNCPU) • For direct communication without specified IP address: UNIT_NZ2GF_ETB_DIRECT (0x5A)

1: Channel 1
2: Channel 2
*3 When the property pattern is (1), (3), or (4), specify the parameter value set for the CC-Link IE Field Network module on the
When the property pattern is (2), specify the value set in the target station side parameter for ActNetworkNumber and 10
ActStationNumber.

Ethernet adapter (TCP) (1)
When a connection target CPU is an FXCPU
Configuration
Connected station
Ethernet adapter Relayed module
CPU
Relayed network
Relayed station
CPU


station CPU
(1)*1 CC IE TSN     
CC IE Field
CC-Link     

station CPU
FXCPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
(1)*1 CC IE TSN      
CC IE Field
CC-Link      
*1 Only FX3SCPU, FX3G(C)CPU and FX3U(C)CPU can be accessed.
Property list
(1)
ActProtocolType 0x04 PROTOCOL_TCPIP
(PROTOCOL_SERIAL)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXETHER

Ethernet adapter (TCP) (2)
When a connection target CPU is an FX5CPU
Configuration 10
Connected station
CPU
Relayed network
Relayed station
CPU


station CPU
 CC IE TSN     
CC IE Field
Ethernet     (1)*1
CC-Link     

station CPU
 CC IE TSN      
CC IE Field
CC-Link      
*1 Only FX5UCPU and FX5UJCPU can be accessed.
Property list
(1)
ActConnectUnitNumber 0 (0x00) Fixed to 0 (0x00)
ActDestinationPortNumber 0 (0x00) Fixed to 5554
ActIONumber 1023 (0x3FF) Fixed to 1023 (0x3FF)

(1)
(PROTOCOL_SERIAL)
ActPacketType 0x01 (PACKET_PLC1) Fixed to PACKET_PLC1
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXVENET

Ethernet adapter (UDP) (1)
When a connection target CPU is an FXCPU
Configuration 10
Connected station
CPU
Relayed network
Relayed station
CPU


station CPU
(1)*1 CC IE TSN     
CC IE Field
CC-Link     

station CPU
*1
(1) CC IE TSN      
CC IE Field
CC-Link      
*1 Only FX3SCPU, FX3G(C)CPU and FX3U(C)CPU can be accessed.
Property list
(1)
ActProtocolType 0x04 PROTOCOL_UDPIP
(PROTOCOL_SERIAL)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXETHER_DIRECT

Configuration
Connected station
CPU
Relayed network
Relayed station
CPU


station CPU
 CC IE TSN     
CC IE Field
Ethernet     (1)*1
CC-Link     

station CPU
 CC IE TSN      
CC IE Field
CC-Link      
Property list
(1)

(1)
ActProtocolType 0x04 PROTOCOL_UDPIP
(PROTOCOL_SERIAL)
10
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXVENET

When a connection target CPU is an FX5CPU and connected directly
Configuration
Connected station
CPU
Relayed network
Relayed station
CPU


station CPU
 CC IE TSN     
CC IE Field
Ethernet     (1)*1
CC-Link     

station CPU
 CC IE TSN      
CC IE Field
CC-Link      
Property list
(1)
ActHostAddress 1.1.1.1 255.255.255.255
To select a PC side adapter, assign a tab character and the personal computer side IP
address after the connection target IP address.

(1)
ActProtocolType 0x04
(PROTOCOL_SERIAL)
PROTOCOL_UDPIP
10
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXVENET_DIRECT

Ethernet communication when the connected station is a robot
controller
Configuration
Robot controller
Personal computer
Property list
ActProtocolType 0x04 RC_PROTOCOL_TCPIP (0x02)
(PROTOCOL_SERIAL)
ActCpuType 34 (CPU_Q02CPU) Robot controller type (0x013001)
ActPortNumber 1 (PORT_1) Port number to be connected (specify 10001 normally)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side robot controller
ActMultiDropChannelNumber 8 (TRC_DTR_OR_RTS) Retry count
ActMxUnitSeries 0 (0x00) 2 (0x02)
When robot controller communication, the program setting type control cannot be used.
Use the utility setting type control.

Ethernet communication when the connected station is a CC-Link
IE TSN module (TCP)
Configuration
10
Connected station CC-Link IE TSN
Relayed module
CPU module
Relayed network
Relayed station
CPU


station CPU
(1) CC IE TSN (2)    
CC IE Field
Serial communication (3)    
CC-Link (4)    

station CPU
mode)
(1) CC IE TSN      
CC IE Field
CC-Link      

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*4 number
ActNetworkNumber*1*6 0 (0x00) Target station side Target station side Connected station side Connected station side
module network module network CC-Link IE TSN CC-Link IE TSN
number number module network module network
number number
ActPassword Empty Password set to CC-Link IE TSN module on the connected station side
(PROTOCOL_SERIA
L)
(PACKET_PLC1)
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
ActSumCheck 0 Fixed to 0 (0x00)
(NO_SUM_CHECK)

(1) (2) (3) (4)
*1*6
module station number module station number CC-Link IE TSN CC-Link IE TSN
ActTimeOut 10000 Any value specified by user in ms units 10
ActUnitType 0x13 UNIT_RJ71GN11 (0x1006)
(UNIT_QNCPU)
ActStationNumber.
*2 Specify the following value.
0: An empty slot number in a personal computer is automatically assigned.
*3 Specify the personal computer side station number to avoid the same station number set for CC-Link IE TSN module within the same
Ethernet loop.
1: Channel 1
2: Channel 2
*5 When the target station is a motion controller or a robot controller, set the value for multiple CPUs.
Example: When a robot controller is set as the CPU No.2, specify '0x3E1'.
*6 Note the following considerations when accessing via CC-Link IE TSN module.
For ActNetworkNumber and ActStationNumber, specify the value set in the parameter setting of the target station side CC-Link IE TSN
module.
 Set "Station No.  IP information" in the parameter setting of CC-Link IE TSN module. When setting the parameter, specify the setting

Ethernet communication when the connected station is a CC-Link
IE TSN module (UDP)
Configuration
Connected station CC-Link IE TSN

Relayed module
CPU module
Relayed network
Relayed station
CPU


station CPU
*1
(1) CC IE TSN (2)    
CC IE Field
CC-Link (4)    

station CPU
mode)
(1)*1 CC IE TSN      
CC IE Field
CC-Link      
*1 Access to a CC-Link IE TSN module with a direct connection is not supported.

Property list
(1) (2) (3) (4) 10
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*4 number
ActNetworkNumber*1*6 0 (0x00) Target station side Target station side Connected station side Connected station side
module network module network CC-Link IE TSN CC-Link IE TSN
number number module network module network
number number
ActPassword Empty Password set to CC-Link IE TSN module on the connected station side
(PROTOCOL_SERIA
L)
(PACKET_PLC1)
ActPortNumber*2 1 (PORT_1) For communication with IP address specified: Personal computer side COM port number
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(NO_SUM_CHECK)

(1) (2) (3) (4)
*1*6
module station number module station number CC-Link IE TSN CC-Link IE TSN
ActUnitType 0x13 UNIT_RJ71GN11 (0x1006)
(UNIT_QNCPU)
ActStationNumber.
*2 When other than the 'automatic response system' is set in the Ethernet parameter of the connected station side CC-Link IE TSN
module, fix the value to '5001'.
When the 'automatic response system' is set in the Ethernet parameter of the connected station side CC-Link IE TSN module, specify
the following value.
0: An empty slot number in a personal computer is automatically assigned.
Other than '0': a UDP socket is generated with the specified port number.
*3 Specify the personal computer side station number to avoid the same station number set for CC-Link IE TSN module within the same
Ethernet loop.
1: Channel 1
2: Channel 2
*5 When the target station is a motion controller or a robot controller, set the value for multiple CPUs.
Example: When a robot controller is set as the CPU No.2, specify '0x3E1'.
*6 Note the following considerations when accessing via CC-Link IE TSN module.
For ActNetworkNumber and ActStationNumber, specify the value set in the parameter setting of the target station side CC-Link IE TSN
module.
 Set "Station No.  IP information" in the parameter setting of CC-Link IE TSN module. When setting the parameter, specify the setting

10.3 CPU COM Communication
CPU COM communication when the connected station is an
FX5CPU
10
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
CC-Link     (3)

station CPU
FX5CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1) CC IE TSN      
CC IE Field
CC-Link      

Property list
(1) (2) (3)
ActBaudRate 19200 (BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
BAUDRATE_115200
ActIntelligentPreferenceBit 0 (0x00) Fixed to 0 (0x00) 1 (0x01)
ActIONumber 1023 (0x3FF) Fixed to 1023 (0x3FF) Module number of the
connected station
network number
ActPassword Empty NULL
station number
ActSumCheck 0 (NO_SUM_CHECK) Fixed to 0 (NO_SUM_CHECK)
ActHostAddress 1.1.1.1 NULL
ActTargetSimulator 0 (0x00) Fixed to 0 (0x00)
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Target station side module
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXVCPU (0x2000)

280 10.3 CPU COM Communication
CPU COM communication when the connected station is a QCPU
(Q mode)
Configuration
10
CPU
Relayed network

Personal computer
CPU


CPU
QCPU (Q QCCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
mode)
(1) (1)*4 CC IE TSN     
CC IE Field
CC-Link     

CPU
QCPU (Q QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) mode) CPU
(1) (1)*4 CC IE TSN      
CC IE Control (2) (2)*1 (2)*2 (2)*1 (2)*1 
CC IE Field
MELSECNET/H (2) (2)  (2) (2) 
Ethernet (2)   (2) (2) 
CC-Link (4) (4) (4)  (4) (4)*3

Property list
(1) (2)*1 (3) (4)
(TRC_DTR_OR_RT
S)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
above: 0 (0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
*3
number
module network
number
(PROTOCOL_SERI
AL)

(1) (2)*1 (3) (4)
ActUnitType 0x13 UNIT_QNCPU (0x13)
(UNIT_QNCPU) 10
compatible E71.
1: Channel 1
2: Channel 2

LCPU
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN     
CC IE Field*1     
CC-Link     

station CPU
mode)
(1) CC IE TSN      
CC IE Field*1 (4) (4)*2 (4)   
Ethernet (4)  (4)   
CC-Link (3) (3) (3)   
accessed.

Property list
(1) (2) (3) (4) 10
(TRC_DTR_OR_RT
S)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
■For redundant CPU ■For redundant CPU
• Control system: 976 • Control system: 976
(0x3D0) (0x3D0)
• No specification: • No specification:
1023 (0x3FF) 1023 (0x3FF)
above: 0 (0x00)
ActIONumber*1 1023 (0x3FF) Fixed to 1023 (0x3FF) Connected station side Connected station side Target station side
module I/O address module I/O address ■For single CPU
• Fixed to 1023
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2 number
module network
number
ActPacketType 0x01 Fixed to 0x01 (PACKET_PLC1)
(PACKET_PLC1)

(1) (2) (3) (4)
(PROTOCOL_SERIA
L)
ActSumCheck 0 Fixed to 0 (NO_SUM_CHECK)
(NO_SUM_CHECK)
ActUnitType 0x13 UNIT_LNCPU (0x50)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

CPU COM communication when the connected station is a Q
motion CPU
Configuration
10
CPU
Relayed network

Personal computer
CPU


station CPU
Q motion RCPU RCCPU R motion CPU LHCPU FX5CPU
CPU
(1)*1 CC IE TSN     
CC IE Field
CC-Link     

station CPU
Q motion QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
CPU mode)
(1)*1 CC IE TSN      
CC IE Field
CC-Link      

Property list
(1)
BAUDRATE_115200
ActIONumber 1023 (0x3FF) ■For multiple CPUs
• Control CPU: 1023 (0x3FF)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_QNMOTION (0x1C)

FXCPU
Configuration
10
CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
(1) CC IE TSN      
CC IE Field
CC-Link      (2)*1

Property list
(1) (2)
ActBaudRate 19200 (BAUDRATE_19200) • FX3S, FX3UC, FX3G(C), FX5U, FX5UJ: (BAUDRATE_9600, BAUDRATE_19200,
BAUDRATE_38400, BAUDRATE_57600, BAUDRATE_115200)
ActDidPropertyBit 1 (0x01) 0 (0x00)
ActDsidPropertyBit 1 (0x01) 0 (0x00)
ActIONumber 1023 (0x3FF) Fixed to 0 (0x00) Module number of the connected station
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Target station side module station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXCPU (0x0F)

inverter
Configuration
10
Inverter
Personal computer
Property list
ActProtocolType 0x04 COMM_RS232C (0x00)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) Inverter station number (0 to 31)
ActCpuType 34 (CPU_Q02CPU) INV_A800 (0x1E60)
BAUDRATE_57600, BAUDRATE_115200
ActPacketType 0x01 (PACKET_PLC1) • CRLF_NONE (0): Without CR/LF
• CRLF_CR (1): With CR
• CRLF_CRLF (2): With CR/LF
ActDataBits 8 (DATABIT_8) • DATABIT_7
• DATABIT_8
ActParity 1 (ODD_PARITY) • NO_PARRITY
• ODD_PARITY
• EVEN_PARITY
ActStopBits 0 (STOPBIT_ONE) • STOPBIT_ONE
• STOPBIT_TWO
When performing inverter communication, the program setting type control cannot be used.

CPU COM communication when the connected station is a robot
controller
Configuration
Robot controller
Personal computer
Property list
ActProtocolType 0x04 RC_PROTOCOL_SERIAL (0x01)
(PROTOCOL_SERIAL)
ActBaudRate 19200 (BAUDRATE_19200) Transmission speed
ActTimeOut 10000 Receive timeout time (msec)
ActCpuTimeOut 0 (0x00) Send timeout time (msec)
ActDataBits 8 (DATABIT_8) • DATABIT_7
• DATABIT_8
ActParity 1 (ODD_PARITY) • NO_PARRITY
• ODD_PARITY
• EVEN_PARITY
ActStopBits 0 (STOPBIT_ONE) • ONESTOPBIT(0)
• ONE5STOPBITS(1)
• TWOSTOPBITS(2)
ActMultiDropChannelNumber 0 (0x00) Retry count
ActThroughNetworkType 0 (0x00) Procedural/Nonprocedural (0/1)

10.4 CPU USB Communication
CPU USB communication when the connected station is an RCPU
Configuration
10

CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN (2)    
CC IE Control (2)*1 (2)   (2)*2
CC IE Field
Ethernet (2)  (2)  
CC-Link (4) (4) (4)  (4)

station CPU
mode)
(1) CC IE TSN      
*1
CC IE Control (2)  (2)   
CC IE Field
Ethernet (2)  (2)   
CC-Link (4)  (4)   

10.4 CPU USB Communication 293
Property list
(1) (2)*1 (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
1023 (0x3FF)
ActDidPropertyBit 1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) 0 (0x00) 0 (0x00)
ActDsidPropertyBit 1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) 0 (0x00) 0 (0x00)
• RCPU, QCPU (Q • RCPU, QCPU (Q
(0x01) (0x01)
above: 0 (0x00) above: 0 (0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
*3 number
module network
number
ActProtocolType 0x04 PROTOCOL_USB
(PROTOCOL_SERI
AL)
(PACKET_PLC1)
ActPortNumber 1 (PORT_1) Fixed to 1 (PORT_1)
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)

(1) (2)*1 (3) (4)
ActSumCheck 0
(NO_SUM_CHECK)
Fixed to 0 (0x00)
10
ActUnitType 0x13 UNIT_RUSB
(UNIT_QNCPU)
compatible E71.
1: Channel 1
2: Channel 2

CPU USB communication when the connected station is an R
motion CPU
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
R motion RCPU RCCPU R motion CPU LHCPU FX5CPU
CPU
(1)*1*2 CC IE TSN     
CC IE Field
CC-Link     

station CPU
R motion QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
CPU
(1)*1*2 CC IE TSN      
CC IE Field
CC-Link      


Property list
(1) 10
Act DestinationIONumber 0 (0x00) Fixed to 0 (0x00)
Act IntelligentPreference Bit 0 (0x00) Fixed to 0 (0x00)
• Connected CPU: 1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
• No specification: 1023 (0x3FF)
ActMultiDropChannelNumber*1 0 (0x00) Fixed to 0 (0x00)
ActProtocolType 0x04 PROTOCOL_USB
(PROTOCOL_SERIAL)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_RUSB
1: Channel 1
2: Channel 2

CPU USB communication when the connected station is an
LHCPU
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
LHCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1) CC IE TSN      
CC IE Field
CC-Link      

Property list
(1) 10
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_USB
ActUnitType 0x13 (UNIT_QNCPU) UNIT_LHUSB

FX5CPU
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
(1)*1 CC IE TSN     
CC IE Control     (2)*2
CC IE Field
CC-Link     (3)

station CPU
(1)*1 CC IE TSN      
CC IE Field
CC-Link      
*1 Only FX5UJCPU can be accessed.


Property list
(1) (2) (3) 10
ActBaudRate 19200 (BAUDRATE_19200) 0 (0x00)
ActControl 8 (TRC_DTR_OR_RTS) 0 (0x00)
ActDataBits 8 (DATABIT_8) 0 (0x00)
ActDidPropertyBit 1 (0x01) 0 (0x00) 1 (0x01) 0 (0x00)
ActDsidPropertyBit 1 (0x01) 0 (0x00) 1 (0x01) 0 (0x00)
ActHostAddress 1.1.1.1 0 (0x00)
connected station
network number
ActPacketType 0x01 (PACKET_PLC1) Fixed to 0x01 (PACKET_PLC1)
ActPassword Empty NULL
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_USB
ActSourceNetworkNumber 0 (0x00) 0 (0x00)
ActSourceStationNumber 0 (0x00) 0 (0x00)
station number
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXVUSB

CPU USB communication when the connected station is a QCPU
(Q mode)
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
QCPU (Q RCPU RCCPU R motion CPU LHCPU FX5CPU
mode)
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
QCPU (Q QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1) CC IE TSN      
CC IE Control (2) (2)*1 (2)*2 (2)*1 (2)*1 
CC IE Field
MELSECNET/H (2) (2)  (2) (2) 
Ethernet (2)   (2) (2) 
CC-Link (4) (4) (4)  (4) (4)*4

station CPU
QCCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
mode)
(1) CC IE TSN      
CC IE Control (2) (2)*1 (2)*2 (2)*1 (2)*1 
CC IE Field 10
MELSECNET/H (2) (2)  (2) (2) 
CC-Link (4) (4) (4)  (4) 

Property list
(1) (2)*1 (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0) (0x3D0)
1023 (0x3FF) 1023 (0x3FF)
above: 0 (0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
*3
number
module network
number
ActProtocolType 0x04 PROTOCOL_USB (0x0D)
(PROTOCOL_SERIA
L)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_QNUSB (0x16)

compatible E71.
*3 Specify the following value for the channel number to be multi-drop linked. 10
1: Channel 1
2: Channel 2

CPU USB communication when the connected station is an LCPU
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN     
CC IE Field*1     
CC-Link     

station CPU
mode)
(1) CC IE TSN      
CC IE Field*1 (4) (4)*2 (4)   
Ethernet (4)  (4)   
CC-Link (3) (3) (3)   
accessed.

Property list
(1) (2) (3) (4) 10
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0) (0x3D0)
1023 (0x3FF) 1023 (0x3FF)
(0x00)
• Fixed to 1023
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2 number
module network
number
ActPacketType 0x01 Fixed to 0x01 (PACKET_PLC1)
(PACKET_PLC1)

(1) (2) (3) (4)
(PROTOCOL_SERI
AL)
ActSumCheck 0 Fixed to 0 (NO_SUM_CHECK)
(NO_SUM_CHECK)
ActUnitType 0x13 UNIT_LNUSB (0x51)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

CPU USB communication when the connected station is a
QSCPU
Configuration
10
CPU
Relayed network

Personal computer
CPU


station CPU
QSCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*1 CC IE TSN     
CC IE Field
CC-Link     

station CPU
QSCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1)*1 CC IE TSN      
CC IE Field
CC-Link      
*1 Relayed station CPUs cannot be accessed via QSCPU.
Property list
(1)
(PROTOCOL_SERIAL)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_QSUSB (0x29)

CPU USB communication when the connected station is a Q
motion CPU
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
Q motion RCPU RCCPU R motion CPU LHCPU FX5CPU
CPU
(1)*1 CC IE TSN     
CC IE Field
CC-Link     

station CPU
Q motion QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
CPU mode)
(1)*1 CC IE TSN      
CC IE Field
CC-Link      
Property list
(1)
ActIONumber 1023 (0x3FF) ■For multiple CPUs
• Control CPU: 1023 (0x3FF)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(PROTOCOL_SERIAL)

(1)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_QNMOTIONUSB (0x1D)
10

FXCPU
Configuration

CPU
Relayed network

Personal computer
CPU


station CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
FXCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1) CC IE TSN      
CC IE Field
CC-Link      (2)*1
Property list
(1) (2)
ActIONumber 1023 (0x3FF) Fixed to 0 (0x00) Module number of the connected station
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_USB (0x0D)

inverter
Configuration
10
Inverter
Personal computer
Property list
ActProtocolType 0x04 COMM_USB (0x01)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) Inverter station number (0 to 31)
ActCpuType 34 (CPU_Q02CPU) Fixed to INV_A800 (0x1E60)
When performing inverter communication, the program setting type control cannot be used.

CPU USB communication when the connected station is a robot
controller
Configuration
Robot controller
Personal computer
Property list
ActProtocolType 0x04 RC_PROTOCOL_USB (0x04)
(PROTOCOL_SERIAL)
ActTimeOut 10000 Receive timeout time (msec)
ActCpuTimeOut 0 (0x00) Send timeout time (msec)
ActMultiDropChannelNumber 0 (0x00) Retry count

10.5 MELSECNET/H Communication
Configuration
10
Connected station MELSECNET/H
Relayed module
CPU module
Relayed network

CPU

Own Connected station CPU Relayed network Relayed station CPU

board QCPU QSCPU Q motion RCPU RCCPU R motion LHCPU FX5CPU
(Q CPU CPU
mode)
(1) (2) (2)*1*5 (2)*1*5 CC IE TSN     
CC IE Field
CC-Link     

board QCPU QSCPU Q motion QCPU QCCPU LCPU QSCPU Q motion FXCPU
(Q CPU (Q CPU*5
mode) mode)
(1) (2) (2)*1*5 (2)*1*5 CC IE TSN      
CC IE Control (2) (2)*2 (2)*3 (2)*1*2  
CC IE Field
MELSECNET/H (2) (2)  (2)*1  
*1
Ethernet (2)   (2)  
CC-Link (4) (4) (4)  (4) 

board QCCPU RCPU RCCPU R motion LHCPU FX5CPU
CPU
(1) (2)*6 CC IE TSN     
CC IE Field
CC-Link     

board QCCPU QCPU QCCPU LCPU QSCPU Q motion FXCPU
(Q CPU*5
mode)
(1) (2)*6 CC IE TSN      
CC IE Field
CC-Link (4) (4) (4)  (4) 

*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.
not supported.

316 10.5 MELSECNET/H Communication
Property list
(1) (2) (3) (4) 10
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0) (0x3D0)
1023 (0x3FF) 1023 (0x3FF)
ActIONumber*1 1023 (0x3FF) Fixed to 0 (0x00) Target station side Connected station side Connected station side
■For single CPU relayed module I/O relayed module I/O
• Fixed to 1023 address address
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2
number
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Target station side Connected station side Connected station side
module network module network module network
ActPortNumber 1 (PORT_1) Port number of personal computer side MELSECNET/H board, PORT 1 to PORT 4 (first to fourth
boards)
ActProtocolType 0x04 PROTOCOL_MNETH (0x0F)
(PROTOCOL_SERI
AL)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Target station side Connected station side Connected station side
module station number module station number module station number
ActUnitType 0x13 UNIT_MNETHBOARD (0x1E)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

10.6 CC-Link IE Controller Network Communication
CC-Link IE Controller Network communication when the
connected station is an RCPU
Configuration
Connected station CC-Link IE Controller Relayed module

CPU Network module
Relayed network

CPU

Own Connected Relayed network Relayed station CPU

board station CPU
 (2) CC IE TSN     
CC IE Field
Serial communication (3)*1    
CC-Link (4)    

board station CPU
RCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU*2
 (2) CC IE TSN      
CC IE Field
CC-Link (4)  (4)   
*1 For redundant CPU, serial communication modules on the main base unit cannot be accessed because the multi-drop connection
cannot be performed.

Property list
(1) (2) (3) (4) 10
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
1023 (0x3FF)
ActIONumber*1 1023 (0x3FF) Fixed to 0 (0x00) Target station side Connected station side Connected station side
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
1023 (0x3FF)
*2 number
ActPortNumber 1 (PORT_1) Port number of personal computer side CC-Link IE Controller Network board, PORT 1 to PORT 4 (first
to fourth boards)
ActProtocolType 0x04 PROTOCOL_MNETG (0x14)
(PROTOCOL_SERI
AL)
ActUnitType 0x13 UNIT_MNETGBOARD (0x2B)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

CC-Link IE Controller Network communication when the
connected station is a module supporting Q series
Configuration
Connected station CC-Link IE Controller Relayed module

CPU Network module
Relayed network

CPU


board QCPU (Q QSCPU Q motion RCPU RCCPU R motion LHCPU FX5CPU
mode) CPU CPU
(1) (2) (2)*1*5 (2)*1*5 CC IE TSN     
CC IE Field
CC-Link     

board QCPU (Q QSCPU Q motion QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU mode) CPU*5
(1) (2) (2)*1*5 (2)*1*5 CC IE TSN      
CC IE Control (2) (2)*2 (2)*3 (2)*1*2  
CC IE Field
MELSECNET/H (2) (2)  (2)*1  
*1
Ethernet (2)   (2)  
CC-Link (4) (4) (4)  (4) 

CPU
(1) (2)*6 CC IE TSN     
CC IE Field
CC-Link     

board QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU*5
(1) (2)*6 CC IE TSN      
CC IE Field
MELSECNET/H       10
CC-Link (4) (4) (4)  (4) 

*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.
not supported.

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0) (0x3D0)
1023 (0x3FF) 1023 (0x3FF)
*1
ActIONumber 1023 (0x3FF) Fixed to 0 (0x00) Target station side Connected station side Connected station side
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2
number
ActPortNumber 1 (PORT_1) Port number of personal computer side CC-Link IE Controller Network board, PORT 1 to PORT 4 (first
to fourth boards)
ActProtocolType 0x04 PROTOCOL_MNETG (0x14)
(PROTOCOL_SERI
AL)
ActUnitType 0x13 UNIT_MNETGBOARD (0x2B)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

10.7 CC-Link IE Field Network Communication
CC-Link IE Field Network communication when the connected
station is an RCPU
10
Configuration

Relayed module
CPU Network module
Relayed network
Relayed station
CPU


board station CPU
 (1) CC IE TSN     
Serial communication (2)*1    
CC-Link (3)    

board station CPU
mode) CPU
 (1) CC IE TSN      
CC IE Field      
CC-Link (3)  (3)   

Property list
(1) (2) (3)
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Target station side Target station side
• Fixed to 1023 (0x3FF) • Fixed to 1023 (0x3FF)
• Connected CPU: 1023 • Connected CPU: 1023
(0x3FF) (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3FF)
ActIONumber*1 1023 (0x3FF) ■For single CPU Connected station side relayed Connected station side relayed
• Fixed to 1023 (0x3FF) module I/O address module I/O address
(0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3FF)
*2
ActNetworkNumber 0 (0x00) Target station side module Connected station side module Connected station side module
network number network number network number
ActPortNumber 1 (PORT_1) Port number of personal computer side CC-Link IE Field Network board, PORT 1 to PORT 4 (first to
fourth boards)
ActProtocolType 0x04 PROTOCOL_CCIEF (0x15)
(PROTOCOL_SERI
AL)
ActStationNumber 255 (0xFF) Target station side module Connected station side module Connected station side module
station number station number station number
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Target station side module Target station side module
station number station number
ActUnitType 0x13 UNIT_CCIEFBOARD (0x2F)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

CC-Link IE Field Network communication when the connected
station is a module supporting QCPU (Q mode) or LCPU
Configuration
10
Relayed module
CPU Network module
Relayed network
Relayed station
CPU


board station CPU
QCPU (Q RCPU RCCPU R motion CPU LHCPU FX5CPU
mode)
(1) (2) CC IE TSN     
CC IE Field
CC-Link     

board station CPU
QCPU (Q QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) mode) CPU
(1) (2) CC IE TSN      
CC IE Control (2) (2)*1 (2)*2   
CC IE Field
MELSECNET/H (2) (2)    
Ethernet (2)     
CC-Link (4) (4) (4)   

board station CPU
(1) (2) CC IE TSN     
CC IE Field*2     
CC-Link     

board station CPU
LCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
(1) (2) CC IE TSN      
CC IE Field*2 (2)  (2)   
CC-Link (4) (4) (4)   
accessed.

Property list
(1) (2) (3) (4) 10
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
ActIONumber*1 1023 (0x3FF) Fixed to 1023 (0x3FF) Target station side Connected station side Connected station side
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*2 number
ActPortNumber 1 (PORT_1) Port number of personal computer side CC-Link IE Field Network board, PORT 1 to PORT 4 (first to
fourth boards)
ActProtocolType 0x04 PROTOCOL_CCIEF (0x15)
(PROTOCOL_SERI
AL)
ActUnitType 0x13 UNIT_CCIEFBOARD (0x2F)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

10.8 CC-Link Communication
CC-Link communication when the connected station is an RCPU
Configuration
Connected station CC-Link Relayed module

CPU module
Relayed network
Relayed station
CPU


board station CPU
 (1) CC IE TSN (2)    
CC IE Control (2)    
CC IE Field
Ethernet (2)    
CC-Link     

board station CPU
mode) CPU
 (1) CC IE TSN      
CC IE Control (2)  (2)*1   
CC IE Field
Ethernet (2)  (2)   
CC-Link      

Property list
(1) (2) 10
ActDestinationIONumber 0 (0x00) ■For single CPU Target station side
• Fixed to 1023 (0x3FF) ■For single CPU
• Connected CPU: 1023 (0x3FF) ■For multiple CPUs
• No. 1: 992 (0x3E0) Connected CPU: 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No specification: 1023 (0x3FF) ■For redundant CPU
• No specification: 1023 (0x3FF)
ActIONumber 1023 (0x3FF) Fixed to 1023 (0x3FF) Fixed to 1023 (0x3FF)
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Target station side module network number
ActPortNumber 1 (PORT_1) Port number of personal computer side CC-Link Ver.2 board, PORT 1 to PORT 4 (first to fourth
boards)
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_CCLINK (0x07)
ActStationNumber 255 (0xFF) Target station side CC-Link module station Target station side module station number
number
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Connected station side CC-Link module
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_CCLINKBOARD (0x0C)

CC-Link communication when the connected station is an LCPU
Configuration

CPU module
Relayed network
Relayed station
CPU


board station CPU
(1) (2) CC IE TSN     
CC IE Field
CC-Link     

board station CPU
mode) CPU
(1) (2) CC IE TSN      
CC IE Field
CC-Link      

Property list
(1) (2) 10
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Target station side
■For single CPU
ActIONumber 1023 (0x3FF) Fixed to 0 (0x00) Fixed to 1023 (0x3FF)
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
boards)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Target station side CC-Link module station
number
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)

CC-Link communication when the connected station is a module
supporting Q series
Configuration

CPU module
Relayed network
Relayed station
CPU


board QCPU (Q Q motion RCPU RCCPU R motion LHCPU FX5CPU
mode) CPU CPU
(1) (2) (2)*1*4 CC IE TSN     
CC IE Field
CC-Link     

board QCPU (Q Q motion QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU mode) CPU
(1) (2) (2)*1*4 CC IE TSN      
CC IE Control (3) (3)*2 (3)*3 (3)*2 (3)*2 
CC IE Field
MELSECNET/H (3) (3)  (3) (3) 
Ethernet (3)   (3) (3) 
CC-Link      

CPU
(1) (2)*5 CC IE TSN     
CC IE Field
CC-Link     

Own Connected station Relayed network Relayed station CPU
board CPU
QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
(1) (2)*5 CC IE TSN      
CC IE Control (3) (3)*2  (3)*2 (3)*2 
CC IE Field 10
MELSECNET/H (3) (3)  (3) (3) 
CC-Link      

*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.
not supported.

Property list
(1) (2) (3)
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Target station side Target station side
• Connected CPU: 1023 • Connected CPU: 1023
(0x3FF) (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0) (0x3D0)
• No specification: 1023 • No specification: 1023
(0x3FF) (0x3FF)
ActIONumber 1023 (0x3FF) Fixed to 0 (0x00) Fixed to 1023 (0x3FF) Fixed to 1023 (0x3FF)
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station side module
network number
boards)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Target station side CC-Link Target station side module
module station number station number
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected station side CC-
Link module station number

10.9 CC-Link System RS-232 Interface Communication
Configuration
10
CPU module
AJ65BT-R2N
Relayed network
module(Q mode)
Relayed station
CPU


QCPU (Q Q motion CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
mode)
(1) (2)*1*5 CC IE TSN     
CC IE Field
CC-Link     

QCPU (Q Q motion CPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) mode) CPU
(1) (2)*1*5 CC IE TSN      
CC IE Control (2) (2)*2 (2)*3 (2)*2 (2)*2 
CC IE Field
MELSECNET/H (2) (2)  (2) (2) 
Ethernet (2)   (2) (2) 
CC-Link      

(1)*4 CC IE TSN     
CC IE Field
CC-Link     

10.9 CC-Link System RS-232 Interface Communication 335
mode) CPU
(1)*4 CC IE TSN      
*2 *3 *2 *2
CC IE Control (2) (2) (2) (2) (2) 
CC IE Field
MELSECNET/H (2) (2)  (2) (2) 
CC-Link      

(1) CC IE TSN     
CC IE Field
CC-Link     

mode) CPU
(1) CC IE TSN      
CC IE Field
CC-Link      

not supported.

336 10.9 CC-Link System RS-232 Interface Communication
Property list
(1) (2) (3) 10
BAUDRATE_115200
ActIONumber*1 1023 (0x3FF) ■For single CPU Target station side Connected station side
• Fixed to 1023 (0x3FF) ■For single CPU relayed module I/O address
• No. 1: 992 (0x3E0) (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No specification: 1023 (0x3D0)
(0x3FF) • No specification: 1023
(0x3FF)
network number
station number
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station side module
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_G4QNCPU (0x1B)

10.9 CC-Link System RS-232 Interface Communication 337
Accessibility
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
Property list
ActTargetSimulator 0 (0x00) Refer to the property [ActTargetSimulator].
ActUnitType 0x13 (UNIT_QNCPU) UNIT_SIMULATOR2 (0x30)

Accessibility
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
Property list
ActHostAddress 1.1.1.1 Loopback address(127.0.0.1)
ActIONumber 1023 (0x3FF) 0 (0x00)
ActParity 1 (ODD_PARITY) 0 (0x00)
ActPassword Empty 0 (0x00)

ActStationNumber 255 (0xFF) System number corresponding to target station
ActThroughNetworkType
ActTimeOut
0 (0x00)
10000
Fixed to 0 (0x00)
Any value specified by user in ms units
10
ActTargetSimulator 0 (0x00) PLC number corresponding to target station
10.12 MT Simulator2 Communication

Accessibility
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
Property list
ActTargetSimulator 0 (0x00) Refer to the property [ActTargetSimulator].
ActCpuType CPU_Q02CPU CPU type corresponding to the target station (Q motion CPU)
10.13 GOT Gateway Device Communication

Configuration
GOT
Personal computer
Property list
ActHostAddress 1.1.1.1 Host name or IP address of connected GOT
(PROTOCOL_SERIAL)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_A900GOT (0x21)

10.12 MT Simulator2 Communication 339
10.14 GOT Transparent Communication
For the 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)
Personal computer side port: USB, GOT2000 side port: USB, CPU
side port: Direct connection (1)
When the connected station is an FX5CPU
Configuration

CPU
GOT Relayed network

USB Serial
Relayed station
CPU


station CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
CC-Link     (3)

station CPU
FX5CPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
(1) CC IE TSN      
CC IE Field
CC-Link      

Property list
(1) (2) (3) 10
ActConnectUnitNumber 0 (0x00) 0 (0x00)
ActCpuTimeOut 0 (0x00) 0 (0x00)
ActDestinationIONumber 0 (0x00) 0 (0x00) 1023 (0x3FF)
ActDestinationPortNumber 0 (0x00) 0 (0x00)
ActHostAddress 1.1.1.1 NULL
connected station
ActMultiDropChannelNumber 0 (0x00) 0 (0x00)
network number
ActPacketType 0x01 (PACKET_PLC1) PACKET_PLC1 (0x01)
ActPassword Null Null
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_USBGOT (0x13)
station number
ActTargetSimulator 0 (0x00) 0 (0x00)
ActThroughNetworkType 0 (0x00) 0 (0x00)
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXVCPU (0x2005)

When the connected station is a QCPU (Q mode)
Configuration

CPU
GOT Relayed network

USB Serial
Relayed station
CPU


QCPU (Q Q motion QCCPU RCPU RCCPU R motion LHCPU FX5CPU
mode) CPU CPU
(1)*1 (1)*2 (1)*5 CC IE TSN     
CC IE Field
CC-Link     

QCPU (Q Q motion QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU mode)*1 CPU
(1)*1 (1)*2 (1)*5 CC IE TSN      
CC IE Control (2) (2)*3 (2)*4  (2)*3 
CC IE Field
MELSECNET/H (2) (2)   (2) 
Ethernet (2)    (2) 
Serial communication (3)  (3)  (3) 
CC-Link (4) (4) (4)  (4) 
*1 Redundant CPU cannot be accessed.

*3 Since CC-Link IE Field Network is not supported, R motion CPU, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE
Field Network cannot be accessed.

Property list
(1) (2) (3) (4) 10
ActCpuType 34 CPU type corresponding to the target station
(CPU_Q02CPU)
• Connected CPU: • Connected CPU: 1023
1023 (0x3FF) (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
QCCPU, LCPU: 1 QCCPU, LCPU: 1 (0x01)
(0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*2 number
module network
number
ActProtocolType 0x04 PROTOCOL_USBGOT (0x13)
(PROTOCOL_SE
RIAL)
ActUnitType 0x13 UNIT_QNCPU (0x13)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

When the connected station is an LCPU
Configuration

CPU
GOT Relayed network

USB Serial
Relayed station
CPU


station CPU
(1) CC IE TSN     
*2
CC-Link     

station CPU
mode)*1 CPU
(1) CC IE TSN      
CC IE Field*2 (4) (4)*3 (4)   
Ethernet (4)  (4)   
CC-Link (3) (3) (3)  (3) 

accessed.

Property list
(1) (2) (3) (4) 10
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
(0x00)
• Fixed to 1023
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2
number
module network
number
(PROTOCOL_SERI
AL)

(1) (2) (3) (4)
ActUnitType 0x13 UNIT_LNCPU (0x50)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

When the connected station is an FXCPU
Configuration 10

CPU
GOT Relayed network

USB Serial
Relayed station
CPU


station CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
FXCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
(1) CC IE TSN      
CC IE Field
CC-Link      (2)*1

Property list
(1) (2)
ActDestinationIONumber 0 (0x00) 0 (0x00) Fixed to 1023 (0x3FF)
ActDidPropertyBit 1 (0x01) 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1 (0x01) 0 (0x00) Fixed to 1 (0x01)
ActIONumber 1023 (0x3FF) 0 (0x00) Module number of the connected station
(PROTOCOL_SERIAL)
ActUnitNumber 0 (0x00) 0 (0x00) Target station side module station number

side port: Bus connection
Configuration
10
Connected Relayed module
station CPU
GOT Relayed network

USB Bus
Relayed station
CPU


QCPU (Q Q motion RCPU RCCPU R motion LHCPU FX5CPU
mode) CPU CPU
(1)*1 (1)*2*5 CC IE TSN     
CC IE Field
CC-Link     

QCPU (Q Q motion QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU mode)*1 CPU
(1)*1 (1)*2*5 CC IE TSN      
CC IE Control (2) (2)*3 (2)*4  (2)*3 
CC IE Field
MELSECNET/H (2) (2)   (2) 
Ethernet (2)    (2) 
CC-Link (4) (4) (4)  (4) 

QCCPU RCPU RCCPU R motion LHCPU FX5CPU
CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

mode)*1 CPU
(1) CC IE TSN      
*3 *4 *3
CC IE Control (2) (2) (2)  (2) 
CC IE Field
MELSECNET/H (2) (2)    
CC-Link (4) (4) (4)   

*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.

Property list
(1) (2) (3) (4) 10
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*2 number
module network
number
(PROTOCOL_SERI
AL)
ActTimeOut*3 10000 Any value specified by user in ms units
ActUnitType 0x13 UNIT_A900GOT (0x21)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2
*3 When a value from 0 to 5000 [ms] is specified, the value is rounded to 5000 ms. Note that the value is rounded to 255000 ms when a
value greater than 255000 ms is specified.

side port: Serial communication module (1)
When a relayed module other than the connected station side R series-compatible C24 exists
Configuration
Connected station R series-compatible Relayed module

CPU C24
GOT Relayed network

USB
Relayed station
CPU


RCPU R motion RCPU RCCPU R motion CPU LHCPU FX5CPU
CPU
(1) (1)*1*3 CC IE TSN     
CC IE Control (2)*2 (2)   
CC IE Field
Ethernet (2)  (2)  
CC-Link (4) (4) (4)  

RCPU R motion QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
CPU mode) CPU
(1) (1)*1*3 CC IE TSN      
CC IE Control (2)  (2)*2   
CC IE Field
MELSECNET/H (2)     
Ethernet (2)  (2)   
CC-Link (4)  (4)   


Property list
(1) (2)*1 (3) (4) 10
*2
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
ActIntelligentPreferenceBit 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*3 number
module network
number
ActProtocolType 0x04 PROTOCOL_USBGOT
(PROTOCOL_SERI
AL)
(PACKET_PLC1)
(BAUDRATE_19200
)
(TRC_DTR_OR_RT
S)
(NO_SUM_CHECK)

(1) (2)*1 (3) (4)
ActUnitType 0x13 UNIT_RJ71C24
(UNIT_QNCPU)
compatible E71.
 Set "MNET/10 routing information" to R series-compatible E71 parameter setting. When setting parameters, specify other than
Automatic Response System (any of IP address calculation system, table conversion system, or combined system) for "MNET/10
routing method."
1: Channel 1
2: Channel 2

When performing multi-drop link on the connected station side R series-compatible C24 with the relayed module
Configuration 10
Connected station R series-compatible

CPU C24
GOT Multi-drop link

USB
Relayed station
CPU


CPU
RCPU, R motion RCPU RCCPU R motion CPU LHCPU FX5CPU
CPU*1*4
Independent (1) Serial communication (2)    
mode*3

CPU
RCPU, R motion QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
CPU*1*4 mode)*2
Independent (1) Serial communication (2)  (2)   
mode*3

*3 The independent mode indicates that the parameters are set as follows.
 CH1 side: Operation setting for transmission setting = independent (0), communication protocol setting = 0
 CH2 side: Operation setting for transmission setting = independent (0)

Property list
(1) (2)
ActDestinationIONumber*1 0 (0x00) Fixed to 0 (0x00) Target station side
■For single CPU
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActDidPropertyBit 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActDsidPropertyBit 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActIONumber*1 1023 (0x3FF) ■For single CPU Connected station side relayed module I/O
• Fixed to 1023 (0x3FF) address
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber*2 0 (0x00) Fixed to 0 (0x00) Multi-drop channel number
(PROTOCOL_SERIAL)
(BAUDRATE_19200)
1: Channel 1
2: Channel 2

When a relayed module other than the connected station side Q series-compatible C24 exists
Configuration 10
Connected station Q series-compatible Relayed module

CPU C24
GOT Relayed network

USB
Relayed station
CPU


QCPU (Q Q motion CPU RCPU RCCPU R motion LHCPU FX5CPU
mode) CPU
(1)*1 (1)*2*5 CC IE TSN     
CC IE Field
CC-Link     

QCPU (Q Q motion CPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) mode)*1 CPU
(1)*1 (1)*2*5 CC IE TSN      
CC IE Control (2) (2)*3 (2)*4  (2)*3 
CC IE Field
MELSECNET/H (2) (2)   (2) 
Ethernet (2)    (2) 
CC-Link (4) (4) (4)  (4) 

*3 Since CC-Link IE Field Network is not supported, R motion CPU, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE
Field Network cannot be accessed.

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*2 number
module network
number
(PROTOCOL_SERI
AL)
ActThrough 0 (0x00) • MELSECNET/10 is not included.: 0 (0x00)
NetworkType • MELSECNET/10 is included.: 1 (0x01)
ActUnitType 0x13 UNIT_QJ71C24 (0x19)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

When performing multi-drop link on the connected station side Q series-compatible C24 with the relayed module
Configuration 10
Connected station Q series-compatible

CPU C24
GOT Multi-drop link

USB
Relayed station
CPU


CPU
QCPU (Q mode)*1 RCPU RCCPU R motion CPU LHCPU FX5CPU
Independent (1) Serial communication     
mode*2

CPU
QCPU (Q mode)*1 QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
mode*2


Property list
(1) (2)
■For single CPU
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActIONumber*1 1023 (0x3FF) ■For single CPU Connected station side relayed module I/
• Fixed to 1023 (0x3FF) O address
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Target station side module station
number
1: Channel 1
2: Channel 2

When a relayed module other than the connected station side L series-compatible C24 exists
Configuration 10
Connected station L series-compatible Relayed module

CPU C24
GOT Relayed network

USB
Relayed station
CPU


station CPU
(1) CC IE TSN     
*2
CC-Link     

station CPU
LCPU QCPU (Q mode)*1 QCCPU LCPU QSCPU Q motion CPU FXCPU
(1) CC IE TSN      
CC IE Field*2 (4) (4)*3 (4)   
Ethernet (4)  (4)   
CC-Link (3) (3) (3)  (3) 

accessed.

Property list
(1) (2) (3) (4)
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
relayed module I/O relayed module I/O ■For single CPU
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*2 number
module network
number
(PROTOCOL_SERI
AL)
ActUnitType 0x13 UNIT_LJ71C24 (0x54)
(UNIT_QNCPU)

1: Channel 1
2: Channel 2
10

When performing multi-drop link on the connected station side L series-compatible C24 with the relayed module
Configuration
Connected station L series-compatible

CPU C24
GOT Multi-drop link

USB
Relayed station
CPU


CPU
Independent (1) Serial communication     
mode*2

CPU
mode)*1
mode*2


Property list
(1) (2) 10
■For single CPU
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActIONumber*1 1023 (0x3FF) Fixed to 1023 (0x3FF) Connected station side relayed module I/
O address
(PROTOCOL_SERIAL)
1: Channel 1
2: Channel 2

Personal computer side port: Serial, GOT2000 side port: Serial,
CPU side port: R series-compatible E71
Configuration

CPU E71
GOT Relayed network

Serial Ethernet
Relayed station
CPU


station CPU
(1)*1 CC IE TSN     
CC IE Field
Ethernet (2)    
CC-Link (4) (4)   

station CPU
RCPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
(1)*1 CC IE TSN      
CC IE Field
Ethernet (2)  (2)   
CC-Link (4)  (4)   

Property list
(1) (2) (3) (4) 10
ActConnectUnitNumber*1 0 (0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
Host station port number for OPS connection*3
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*4 number
(PROTOCOL_SERI
AL)
(PACKET_PLC1)
(TRC_DTR_OR_RT
S)
(NO_SUM_CHECK)
ActSourceNetworkNumber*6 0 (0x00) GOT side network number
ActSourceStationNumber*7 0 (0x00) GOT side station number

(1) (2) (3) (4)
*5
ActUnitType 0x13 UNIT_GOT_RJ71EN71
(UNIT_QNCPU)
*1 When the property pattern is (2), specify the connected station side R series-compatible E71 station number set to the connected
station side R series-compatible E71 Ethernet parameter.
*3 When using OPS connection function at redundant CPU connection, set the port No. specified to "Host Station Port No." in Network
parameter.
1: Channel 1
2: Channel 2
ActStationNumber.
*6 Specify the same network No. as MELSECNET/10 network No. set to R series-compatible E71 in the Ethernet parameter settings of
target station side R series-compatible E71.
*7 Specify the station number on the GOT side to avoid setting the same station number as set to the R series-compatible E71 on the same
Ethernet loop.

side port: R series-compatible E71
Configuration
10
CPU E71
GOT Relayed network

USB Ethernet
Relayed station
CPU


RCPU RCCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1 *1 *2
(1) (1) , CC IE TSN     
CC IE Field
Ethernet (2)    
CC-Link (4) (4)   

RCPU RCCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
(1)*1 (1)*1,*2 CC IE TSN      
CC IE Field
Ethernet (2)  (2)   
CC-Link (4)  (4)   

*2 A communication with a relayed station via network cannot be established.

Property list
(1) (2) (3) (4)
*1
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
Host station port number for OPS connection*3
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*4 number
(PROTOCOL_SERI
AL)
(PACKET_PLC1)
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(NO_SUM_CHECK)

(1) (2) (3) (4)
*5
ActUnitType 0x13 UNIT_GOT_RJ71EN71
(UNIT_QNCPU)
*1 When the property pattern is (2), specify the connected station side R series-compatible E71 station number set to the connected
station side R series-compatible E71 Ethernet parameter.
parameter.
1: Channel 1
2: Channel 2
ActStationNumber.
*6 Specify the same network No. as MELSECNET/10 network No. set to R series-compatible E71 in the Ethernet parameter settings of
target station side R series-compatible E71.
*7 Specify the station number on the GOT side to avoid setting the same station number as set to the R series-compatible E71 on the same
Ethernet loop.

side port: Q series-compatible E71
Configuration

CPU E71
GOT Relayed network

USB Ethernet
Relayed station
CPU
The communication cannot be established when a remote password is set to the connected station side Q series-compatible
E71.


mode)
(1)*1 (1)*4 CC IE TSN     
CC IE Field
CC-Link     

mode) mode)*1 CPU
(1)*1 (1)*4 CC IE TSN      
CC IE Control (2) (2)*2 (2)*3   
CC IE Field
MELSECNET/H (2) (2)    
Ethernet (2)     
CC-Link (4) (4) (4)   

accessed.

Property list
(1) (2) (3) (4) 10
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
*2 number
(PROTOCOL_SERI
AL)
ActSourceNetworkNumber 0 (0x00) GOT side network number

(1) (2) (3) (4)
ActUnitType 0x13 UNIT_GOT_QJ71E71 (0x40)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2
ActStationNumber.
*4 Specify the station number on the GOT side to avoid setting the same station number as set to the Q series-compatible E71 on the same
Ethernet loop.

side port: L series-compatible E71
Configuration
10
CPU E71
GOT Relayed network

USB Ethernet
Relayed station
CPU
The communication cannot be established when a remote password is set to the connected station side L series-compatible
E71.


station CPU
*1
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
LCPU QCPU (Q mode)*1 QCCPU LCPU QSCPU Q motion CPU FXCPU
(1)*1 CC IE TSN      
CC IE Control (2) (2)*2 (2)*3
  
CC IE Field
MELSECNET/H (2) (2)    
Ethernet (2) (2) (2)   
Serial communication (3)*4 (3)*4 (3)*4   
CC-Link (4) (4) (4)   

accessed.

Property list
(1) (2) (3) (4)
(BAUDRATE_19200)
ActConnectUnitNumber*1 0 (0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
(TRC_DTR_OR_RT
S)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
ActDestinationPortNumber*2 0 (0x00) 5001
Host station port number for OPS connection
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
1023 (0x3FF)
*4 number
(PROTOCOL_SERI
AL)

(1) (2) (3) (4)
*5
ActUnitType 0x13 UNIT_GOT_LJ71E71 (0x5D)
(UNIT_QNCPU)
*1 When the property pattern is (2), specify the connected station side L series-compatible E71 station number set to the connected
station side L series-compatible E71 Ethernet parameter.
parameter.
1: Channel 1
2: Channel 2
ActStationNumber.
*6 Specify the same network No. as MELSECNET/10 network No. set to L series-compatible E71 in the Ethernet parameter settings of
target station side L series-compatible E71.
*7 Specify the station number on the GOT side to avoid setting the same station number as set to the L series-compatible E71 on the same
Ethernet loop.

side port: Ethernet port (1)
When the connected station is an RCPU
Configuration

CPU
GOT Relayed network

USB Ethernet
Relayed station
CPU


RCPU RCCPU R motion CPU RCPU RCCPU R motion LHCPU FX5CPU
CPU
(1) (1)*3 (1)*1,*3 CC IE TSN     
CC IE Control (2)*2 (2)   (2)*4
CC IE Field
Ethernet (2)    
CC-Link (4) (4)   (4)

RCPU RCCPU R motion CPU QCPU (Q QCCPU LCPU QSCP Q motion FXCP
mode) U CPU U
(1) (1)*3 (1)*1,*3 CC IE TSN      
CC IE Field
Ethernet   (2)   
CC-Link      


Property list
(1) (2)*1 (3) (4) 10
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
RCPU, QCPU (Q RCPU, QCPU (Q
mode), LCPU: 1 (0x01) mode), LCPU: 1 (0x01)
Other than the above: 0 Other than the above: 0
(0x00) (0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*3
number
module network
number
(PROTOCOL_SERI
AL)
(PACKET_PLC1)
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(NO_SUM_CHECK)

(1) (2)*1 (3) (4)
*4
ActUnitType 0x13 UNIT_GOT_RETHER
(UNIT_QNCPU)
compatible E71.
 Set "MNET/10 routing information" to R series-compatible E71 parameter setting. When setting parameters, specify other than
Automatic Response System (any of IP address calculation system, table conversion system, or combined system) for "MNET/10
routing method."
1: Channel 1
2: Channel 2
ActStationNumber.

Configuration 10

CPU
GOT Relayed network

USB Ethernet
Relayed station
CPU


station CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
CC-Link     (3)

station CPU
mode) CPU
(1) CC IE TSN      
CC IE Field
CC-Link      

Property list
(1) (2) (3)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side IP address of a connected
module station CPU
connected station
network number
station number
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOT_FXVETHER (0x2007)

When the connected station is a QCPU (Q mode) or QCCPU
Configuration 10

CPU
GOT Relayed network

USB Ethernet
Relayed station
CPU


station CPU*1
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU*1
QnUDE(H)CPU QCPU (Q mode)*2 QCCPU LCPU QSCPU Q motion CPU FXCPU
(1) CC IE TSN      
CC IE Control (2) (2)*3 (2)*4   
CC IE Field
MELSECNET/H (2) (2)    
Ethernet (2)     
CC-Link (4) (4) (4)   

station CPU*1
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU*1
mode)*2
(1) CC IE TSN      
CC IE Control (2) (2)*3 (2)*4   
CC IE Field
MELSECNET/H (2) (2)    
CC-Link (4) (4) (4)   
*1 The communication cannot be established when a remote password is set to the connected station CPU.
accessed.

Property list
(1) (2)*1 (3) (4) 10
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
Other than the above: (0x01)
0 (0x00) Other than the above:
0 (0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*3 number
module network
number
(PROTOCOL_SERI
AL)
ActUnitType 0x13 UNIT_GOT_QNETHER (0x41)
(UNIT_QNCPU)

compatible E71.
1: Channel 1
2: Channel 2
ActStationNumber.

Configuration 10

CPU
GOT Relayed network

USB Ethernet
Relayed station
CPU


station CPU*1
(1) CC IE TSN     
CC IE Field*3     
CC-Link     

station CPU*1
mode)*2 CPU
(1) CC IE TSN      
CC IE Field*3 (4) (4)*4 (4)   
Ethernet (4)  (4)   
CC-Link (3) (3) (3)   
*1 The communication cannot be established when a remote password is set to the connected station CPU.
accessed.

Property list
(1) (2) (3) (4)
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
0 (0x00) Other than the above:
0 (0x00)
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2 number
module network
number
(PROTOCOL_SERI
AL)

(1) (2) (3) (4)
ActTimeOut 10000 Any value specified by user in ms units 10
ActUnitType 0x13 UNIT_GOT_LNETHER (0x55)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

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
CPU


station CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
QnUDE(H)CPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
(1) CC IE TSN      
CC IE Control (2) (2)*2 (2)*3   
CC IE Field
MELSECNET/H (2) (2)    
Ethernet (2)     
CC-Link (4) (4) (4)   

station CPU
(1) CC IE TSN     
CC IE Field*3     
CC-Link     

station CPU
mode)*1 CPU
(1) CC IE TSN      
CC IE Field*3 (2)  (2)   
10
CC-Link (4) (4) (4)   

accessed.

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
ActHostAddress 1.1.1.1 Host name or IP address of the Ethernet adapter module
*1
ActIONumber 1023 (0x3FF) ■For single CPU Target station side Connected station side Connected station side
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2
number
(PROTOCOL_SERI
AL)
ActUnitType 0x13 UNIT_GOT_NZ2GF_ETB (0x5B)
(UNIT_QNCPU)

1: Channel 1
2: Channel 2
*3 For the property pattern of (1), (3), or (4), specify the parameter value set on the CC-Link IE Field Network module on the
For the property pattern of (2), specify the value set in the target station side parameter for ActNetworkNumber and 10
ActStationNumber.

side port: Ethernet adapter/module
Configuration
Ethernet adapter: FX3U-ENET-ADP
Ethernet adapter Connected station Relayed module

CPU
Ethernet
GOT Relayed network
USB
Relayed station
CPU
Ethernet module: FX3U-ENET (-L)
Ethernet module Connected station Relayed module

CPU
Ethernet
GOT Relayed network
USB
Relayed station
CPU


station CPU
(1)*1 CC IE TSN     
CC IE Field
CC-Link     

station CPU
mode) CPU
(1)*1 CC IE TSN      
CC IE Field
CC-Link      
*1 Only FX3SCPU(FX3U-ENET-ADP), FX3G(C)CPU and FX3U(C)CPU can be accessed.

Property list
(1) 10
ActHostAddress 1.1.1.1 Host name or IP address of FX3U-ENET-ADP module
Host name or IP address of FX3U-ENET (-L) module
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_USBGOT
ActUnitType 0x13 (UNIT_QNCPU) FX3U-ENET-ADP: UNIT_GOT_FXETHER
FX3U-ENET(-L): UNIT_GOT_FXENET

side port: Ethernet adapter
Configuration
Ethernet adapter Connected station Relayed module

CPU
Ethernet
GOT Relayed network
USB
Relayed station
CPU


station CPU
 CC IE TSN     
CC IE Field
Ethernet     (1)*1
CC-Link     

station CPU
mode) CPU
 CC IE TSN      
CC IE Field
CC-Link      
Property list
(1)
ActDidPropertyBit 1 (0x01) 1 (0x01) (invalid)
ActDsidPropertyBit 1 (0x01) 1 (0x01) (invalid)
ActHostAddress 1.1.1.1 Host name or IP address of a connection target CPU

(1)
(PROTOCOL_SERIAL)
10
ActPortNumber 1 (PORT_1) PORT_1
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOT_FXVENET

Personal computer side port: Ethernet board, GOT2000 port:
Ethernet port, CPU side port: Serial (1)
Configuration

CPU
GOT Relayed network

Ethernet Serial
Relayed station
CPU


station CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
CC-Link     (3)

station CPU
mode) CPU
(1) CC IE TSN      
CC IE Field
CC-Link      

Property list
(1) (2) (3) 10
ActDestinationPortNumber 0 (0x00) GOT port number
ActHostAddress 1.1.1.1 Host name or IP address of GOT
connected station
network number
station number
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOTETHER_FXVCPU (0x2006)

When the connected station is a QCPU (Q mode) or QCCPU
Configuration

CPU
GOT Relayed network

Ethernet Serial
Relayed station
CPU


mode)
(1)*1 (1)*4 CC IE TSN     
CC IE Field
CC-Link     

mode) mode)*1 CPU
(1)*1 (1)*4 CC IE TSN      
CC IE Control (2) (2)*2 (2)*3   
CC IE Field
MELSECNET/H (2) (2)    
CC-Link (4) (4) (4)   

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.

Property list
(1) (2) (3) (4) 10
• Fixed to 1023 • Fixed to 1023 (0x3FF)
(0x3FF) ■For multiple CPUs
■For multiple CPUs • Connected CPU:
1023 (0x3FF) • No. 1: 992 (0x3E0)
• No. 1: 992 (0x3E0) • No. 2: 993 (0x3E1)
• No. 2: 993 (0x3E1) • No. 3: 994 (0x3E2)
• No. 3: 994 (0x3E2) • No. 4: 995 (0x3E3)
• No. 4: 995 (0x3E3) ■For redundant CPU
(0x3D0)
(0x3FF)
0 (0x00) Other than the above: 0
(0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2 number
module network
number
(PROTOCOL_SERI
AL)
ActUnitType 0x13 UNIT_GOTETHER_QNCPU (0x56)
(UNIT_QNCPU)

1: Channel 1
2: Channel 2

Configuration 10

CPU
GOT Relayed network

Ethernet Serial
Relayed station
CPU


station CPU
(1) CC IE TSN     
CC IE Field*2     
CC-Link     

station CPU
mode)*1 CPU
(1) CC IE TSN      
CC IE Field*2 (4) (4)*3 (4)   
CC-Link (3) (3) (3)   

accessed.

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
(0x00)
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2
number
module network
number
(PROTOCOL_SERI
AL)

(1) (2) (3) (4)
ActUnitType 0x13 UNIT_GOTETHER_LNCPU (0x57)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

Configuration

CPU
GOT Relayed network

Ethernet Serial
Relayed station
CPU


station CPU
(1) CC IE TSN     
CC IE Field
CC-Link     

station CPU
mode) CPU
(1) CC IE TSN      
CC IE Field
CC-Link      
Property list
(1)
*1
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_TCPIP
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOTETHER_FXCPU
*1 For ActPortNumber, specify the value set to GOT side.

Personal computer side port: Ethernet board, GOT2000 side port:
Ethernet port, CPU side port: Serial communication module (1)
When the connected station is R series-compatible C24
Configuration 10

CPU C24
GOT Relayed network

Ethernet Serial
Relayed station
CPU


RCP R motion CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
U
(1) (1)*1*3 CC IE TSN     
CC IE Control (4)*2 (4)   
CC IE Field
CC-Link (3) (3)   

RCP R motion CPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
U mode) CPU
(1) (1)*1,*3 CC IE TSN      
CC IE Control (4)  (4)*2   
CC IE Field
MELSECNET/H (4)     
CC-Link (3)  (3)   


Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
ActDestinationPortNumber*2 0 (0x00) GOT port number
RCPU, QCPU (Q RCPU, QCPU (Q
mode), LCPU: 1 (0x01) mode), QCCPU,
Other than the above: 0 LCPU: 1 (0x01)
(0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*3 number
module network
number
(PROTOCOL_SERI
AL)
(PACKET_PLC1)
(BAUDRATE_19200)
(TRC_DTR_OR_RT
S)
(NO_SUM_CHECK)

(1) (2) (3) (4)
ActUnitType 0x13 UNIT_GOTETHER_RJ71C24
(UNIT_QNCPU)
*2 Specify the value set to GOT side for ActDestinationPortNumber.
1: Channel 1
2: Channel 2
ActStationNumber.

When the connected station is Q series-compatible C24
Configuration

CPU C24
GOT Relayed network

Ethernet Serial
Relayed station
CPU


mode)
(1)*1 (1) CC IE TSN     
CC IE Field
CC-Link     

mode) mode)*1 CPU
(1)*1 (1) CC IE TSN      
CC IE Control (2) (2)*2 (2)*3   
CC IE Field
MELSECNET/H (2) (2)    
CC-Link (4) (4) (4)   

accessed.

Property list
(1) (2) (3) (4) 10
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
(0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2
number
module network
number
(PROTOCOL_SERI
AL)

(1) (2) (3) (4)
ActUnitType 0x13 UNIT_GOTETHER_QNCPU (0x56)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

When the connected station is L series-compatible C24
Configuration 10

CPU C24
GOT Relayed network

Ethernet Serial
Relayed station
CPU


station CPU
(1) CC IE TSN     
CC IE Field*2     
CC-Link     

station CPU
mode)*1 CPU
(1) CC IE TSN      
*2 *3
CC IE Field (4) (4) (4)   
CC-Link (3) (3) (3)   

accessed.

Property list
(1) (2) (3) (4)
(0x3FF) (0x3FF)
1023 (0x3FF) 1023 (0x3FF)
• No. 1: 992 (0x3E0) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1) • No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3) • No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
(0x00)
(0x3FF)
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x3D0)
1023 (0x3FF)
*2
number
module network
number
(PROTOCOL_SERI
AL)

(1) (2) (3) (4)
ActUnitType 0x13 UNIT_GOTETHER_LNCPU (0x57)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

Ethernet port, CPU side port: Bus connection
Configuration
Connected Relayed module

station CPU
GOT Relayed network

Ethernet Bus
Relayed station
CPU


QCPU (Q mode) RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
(1) CC IE TSN     
CC IE Field
CC-Link     

QCPU (Q mode) QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
(1)*1 CC IE TSN      
CC IE Control (2) (2)*2 (2)*3   
CC IE Field
MELSECNET/H (2) (2)    
CC-Link (4) (4) (4)   

(1) CC IE TSN     
CC IE Field
CC-Link     

mode)*1 CPU
(1) CC IE TSN      
*2 *3
CC IE Control (2) (2) (2)   
CC IE Field
MELSECNET/H (2) (2)     10
CC-Link (4) (4) (4)   

accessed.

Property list
(1) (2) (3) (4)
Fixed to 1023 (0x3FF) • Fixed to 1023
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
(0x00)
• No. 1: 992 (0x3E0) 1023 (0x3FF)
• No. 2: 993 (0x3E1) • No. 1: 992 (0x3E0)
• No. 3: 994 (0x3E2) • No. 2: 993 (0x3E1)
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
*2 number
module network
number
(PROTOCOL_SERI
AL)
ActUnitType 0x13 UNIT_GOTETHER_QBUS (0x58)
(UNIT_QNCPU)
1: Channel 1
2: Channel 2

Ethernet port, CPU side port: Ethernet port
Configuration
10
CPU
GOT Relayed network

Ethernet Ethernet
Relayed station
CPU


*1
(1) CC IE TSN     
CC IE Field
CC-Link     

mode) CPU
(1)*1 CC IE TSN      
CC IE Field
CC-Link      
*1 Only operates for Qn(U)(J)(P)(D)(E)(V)(H). QnPRHCPU cannot be accessed because it is not supported.

Property list
(1)
ActIONumber*2 1023 (0x3FF) ■For single CPU
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActNetworkNumber*4 0 (0x00) Fixed to 0 (0x00)
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_TCPIP (0x05)/PROTOCOL_UDPIP (0x08)
ActSourceNetworkNumber*5 0 (0x00) Fixed to 0 (0x00)
ActSourceStationNumber*6 0 (0x00) Fixed to 0 (0x00)
ActStationNumber*4 255 (0xFF) Fixed to 255 (0xFF)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOTETHER_QN_ETHER (0x6F)
*1 Specify the value set on the GOT side.

1: Channel 1
2: Channel 2
*4 Specify the value set in the parameter setting on the target station side.
*5 When the connected station includes an Ethernet port and the extension setting (network No. station number setting), specify the same
network No. as that set for the Ethernet port.
When the connected station does not include an Ethernet port and extension setting (network No. station number setting), specify the
same network No. as that of the connected station set in the Ethernet setting of a GOT. For the setting addressing to the own station
(1NetworkNumber: 0x00, 1StationNumber: 0xFF), set '0x00' same as '1NetworkNumber'.
*6 Specify the personal computer side station number to avoid the same station number set for QJ71E71 in the same Ethernet network.

Ethernet port, CPU side port: Q series-compatible E71
Configuration
10
CPU E71
GOT Relayed network

Ethernet Ethernet
Relayed station
CPU


(1)*1 CC IE TSN     
CC IE Field
CC-Link     

mode) CPU
(1)*1 CC IE TSN      
CC IE Field
CC-Link      
*1 Only operates for Qn(U)(J)(P)(D)(E)(V)(H). QnPRHCPU cannot be accessed because it is not supported.

Property list
(1)
ActIONumber*2 1023 (0x3FF) ■For single CPU
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActNetworkNumber*4 0 (0x00) Target station side module network number
ActProtocolType 0x04 (PROTOCOL_SERIAL) PROTOCOL_TCPIP (0x05)/PROTOCOL_UDPIP (0x08)
ActStationNumber*4 255 (0xFF) Target station side module station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOTETHER_QN_ETHER (0x6F)
*1 Specify the value set on the GOT side.

1: Channel 1
2: Channel 2
*4 Specify the value set in the parameter setting on the target station side.
*5 Specify the same network No. as the one set for QJ71E71 in the parameter setting of the QJ71E71.
*6 Specify the personal computer side station number to avoid the same station number set for QJ71E71 in the same Ethernet network.

11 FUNCTIONS
This chapter explains the programming considerations, function list, and details of functions.
11.1 Programming Considerations

This section explains the considerations for creating a program using the function.
Read these precautions before starting creating a program. 11
Open function (opening communication line)
The processing may take long time due to the Open function processes: establishment of communication routes, obtaining
programmable controller internal information, or the like.
Efficient programs need to be created in order to improve the speed performance of user programs.
The following figures are flows for creating efficient and inefficient user programs.
<Efficient user program> <Inefficient user program>
Start Start
Open the communication line. (Open) Open the communication line. (Open)
Access the programmable controller CPU or module Access the programmable controller CPU or module
using the function (such as GetDevice). using the function (such as GetDevice).
Close the communication line. (Close)

No
Close the user program?
No
Yes Close the user program?
Close the communication line. (Close)
Yes
Complete Complete
Differences between LONG type functions and SHORT type/INT type functions
LONG type functions and SHORT type/INT type functions are the functions of MX Component to 'read devices in batch,' 'write
devices in batch,' 'read devices randomly,' 'write devices randomly,' 'set device data,' and 'acquire device data.'
The following describes the differences between the LONG type functions and SHORT type/INT type functions.
■ LONG type function

When writing/reading a negative device value using the LONG type function, the LONG type data needs to be converted to
the SHORT type/INT type data in the user program.
When writing/reading negative device values, use the SHORT type/INT type functions.
Page 424 SHORT type/INT type function
Target function Reference
ReadDeviceBlock Page 431 ReadDeviceBlock (Reading devices in batch)
WriteDeviceBlock Page 434 WriteDeviceBlock (Writing devices in batch)
ReadDeviceRandom Page 437 ReadDeviceRandom (Reading devices randomly)
WriteDeviceRandom Page 437 ReadDeviceRandom (Reading devices randomly)
SetDevice Page 443 SetDevice (Setting device data)
11 FUNCTIONS
11.1 Programming Considerations 423
GetDevice Page 445 GetDevice (Acquiring device data)
Ex.
When reading a device data with a negative value using the ReadDeviceBlock function
lplData = 65535 (0x0000FFFF)
The data is stored as LONG type

data (4-byte data) in the user
application.
Conversion
D0 = -1 (0xFFFF)
lpsData = (SHORT)lplData;
lpsData = -1 (0xFFFF)
Data needs to be converted

to SHORT type/INT type
data (2-byte data) in the
Read D0 data using Convert to user application.
the ReadDeviceBlock function. SHORT type/INT type.
■ SHORT type/INT type function

When reading/writing a negative device value using the SHORT type/INT type function, the device value can be used as it is
without converting it.
When reading/writing double word devices, use any of the LONG type functions.
Page 423 LONG type function
ReadDeviceBlock2 Page 477 ReadDeviceBlock2 (Reading devices in batch)
WriteDeviceBlock2 Page 480 WriteDeviceBlock2 (Writing devices in batch)
ReadDeviceRandom2 Page 483 ReadDeviceRandom2 (Reading devices randomly)
WriteDeviceRandom2 Page 486 WriteDeviceRandom2 (Writing devices randomly)
SetDevice2 Page 489 SetDevice2 (Setting device data)
GetDevice2 Page 491 GetDevice2 (Acquiring device data)
Ex.
When reading a device data with a negative value using the ReadDeviceBlock2 function
lpsData = -1 (0xFFFF)
The data is stored as SHORT

type/INT type data (2-byte
data) in the user application.
D0 = -1 (0xFFFF)
Read D0 data using

the ReadDeviceBlock2 function.
Considerations of multi-thread programming

When performing multi-thread programming, follow the rules of COM and ActiveX controls.
For details, refer to the rules and reference books of COM and ActiveX controls.
• The ActiveX controls used on MX Component are those of the STA model.
• When passing the interface pointer to another apartment, the interface pointer needs to be marshaled.
Synchronize programs using CoMarshalInterThreadInterfaceInStream or
CoGetInterfaceAndReleaseStream of the COM function.
Considerations for using RnSFCPU
11 FUNCTIONS
424 11.1 Programming Considerations
In case of safety mode, the following functions cannot be used for the RnSFCPU safety device.
Function name Feature
WriteDeviceBlock To write devices in batch.
WriteDeviceRandom To write devices randomly.
SetDevice To set device data.
WriteDeviceBlock2 To write devices in batch.
WriteDeviceRandom2 To write devices randomly.
SetDevice2 To set device data.
WriteBuffer To write data to buffer memory.
11
If any of these functions is used, the error code "0x010A42A5" (Operation that can not be carried out in safety
mode)will be returned.
Considerations for using QSCPU

The following functions cannot be used for QSCPU.
Function name Feature
WriteDeviceBlock To write devices in batch.
WriteDeviceRandom To write devices randomly.
SetDevice To set device data.
WriteBuffer To write data to buffer memory.
SetClockData To write clock data.
SetCpuStatus To perform a remote operation.
WriteDeviceBlock2 To write devices in batch.
WriteDeviceRandom2 To write devices randomly.
SetDevice2 To set device data.
If any of these functions is used, the error code "0x010A42A0" (mismatched CPU access password) will be
returned.
Consideration for using inverter/robot controller

The functions of .Net control and controls set in a program (Page 38 Grasping a Control to be Used) cannot be used
during performing inverter communication/robot controller communication.
If any of these functions is used, the error code "0xF0000007" (function non-support error) will be returned.
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)
11 FUNCTIONS
11.1 Programming Considerations 425
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.
Control
■ 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.
11 FUNCTIONS
426 11.1 Programming Considerations
11.2 Function List
The following table shows the features of the functions and the functions that can be used for the controls.
Function name Feature Refer*1
Open To open a communication line. Act: Page 429 Open (Opening communication line)
DataLogging: Page 494 Open (Opening communication line)
Dot: Page 502 Open (Opening communication line)
Close To close a communication line. Act: Page 430 Close (Closing communication line)
DataLogging: Page 495 Close (Closing communication line)
Dot: Page 503 Close (Closing communication line)
11
ReadDeviceBlock To read devices in batch (in 4-byte data unit). Act: Page 431 ReadDeviceBlock (Reading devices in batch)
Dot: Page 504 ReadDeviceBlock (Reading devices in batch)
WriteDeviceBlock To write devices in batch (in 4-byte data unit). Act: Page 434 WriteDeviceBlock (Writing devices in batch)
Dot: Page 508 WriteDeviceBlock (Writing devices in batch)
ReadDeviceRandom To read devices randomly (in 4-byte data unit). Act: Page 437 ReadDeviceRandom (Reading devices randomly)
Dot: Page 512 ReadDeviceRandom (Reading devices randomly)
WriteDeviceRandom To write devices randomly (in 4-byte data unit). Act: Page 440 WriteDeviceRandom (Writing devices randomly)
Dot: Page 519 WriteDeviceRandom (Writing devices randomly)
SetDevice To set one point of device (in 4-byte data unit). Act: Page 443 SetDevice (Setting device data)
Dot: Page 526 SetDevice (Setting device data)
GetDevice To acquire data of one point of device (in 4-byte data Act: Page 445 GetDevice (Acquiring device data)
unit). Dot: Page 529 GetDevice (Acquiring device data)
ReadBuffer To read data from buffer memory. Act: Page 447 ReadBuffer (Reading data from buffer memory)
Dot: Page 532 ReadBuffer (Reading data from buffer memory)
WriteBuffer To write data to buffer memory. Act: Page 451 WriteBuffer (Writing data to buffer memory)
Dot: Page 534 WriteBuffer (Writing data to buffer memory)
GetClockData To read clock data from programmable controller Act: Page 455 GetClockData (Reading clock data)
CPU. Dot: Page 536 GetClockData (Reading clock data)
SetClockData To write clock data to programmable controller CPU. Act: Page 459 SetClockData (Writing clock data)
Dot: Page 538 SetClockData (Writing clock data)
GetCpuType To read programmable controller CPU model. Act: Page 463 GetCpuType (Reading programmable controller CPU model)
Dot: Page 540 GetCpuType (Reading programmable controller CPU model)
SetCpuStatus To perform remote RUN/STOP/PAUSE of Act: Page 466 SetCpuStatus (Remote control)
programmable controller CPU. Dot: Page 541 SetCpuStatus (Remote control)
EntryDeviceStatus*2 To register devices for status monitoring. Act: Page 469 EntryDeviceStatus (Registering devices for status monitoring)
Dot: Page 542 EntryDeviceStatus (Registering devices for status monitoring)
FreeDeviceStatus*2 To deregister devices for status monitoring. Act: Page 473 FreeDeviceStatus (Deregistering devices for status monitoring)
Dot: Page 545 FreeDeviceStatus (Deregistering devices for status monitoring)
OnDeviceStatus*2 To notify event. Act: Page 474 OnDeviceStatus (Event notification)
Dot: Page 546 OnDeviceStatus (Event notification)
ReadDeviceBlock2 To read devices in batch (in 2-byte data unit). Act: Page 477 ReadDeviceBlock2 (Reading devices in batch)
Dot: Page 548 ReadDeviceBlock2 (Reading devices in batch)
WriteDeviceBlock2 To write devices in batch (in 2-byte data unit). Act: Page 480 WriteDeviceBlock2 (Writing devices in batch)
Dot: Page 552 WriteDeviceBlock2 (Writing devices in batch)
ReadDeviceRandom2 To read devices randomly (in 2-byte data unit). Act: Page 483 ReadDeviceRandom2 (Reading devices randomly)
Dot: Page 557 ReadDeviceRandom2 (Reading devices randomly)
WriteDeviceRandom2 To write devices randomly (in 2-byte data unit). Act: Page 486 WriteDeviceRandom2 (Writing devices randomly)
Dot: Page 564 WriteDeviceRandom2 (Writing devices randomly)
SetDevice2 To set one point of device (in 2-byte data unit). Act: Page 489 SetDevice2 (Setting device data)
Dot: Page 570 SetDevice2 (Setting device data)
GetDevice2 To acquire data of one point of device (in 2-byte data Act: Page 491 GetDevice2 (Acquiring device data)
unit). Dot: Page 573 GetDevice2 (Acquiring device data)
GetErrorMessage To acquire error description and corrective action. Msg: Page 493 GetErrorMessage(Acquiring error description and corrective
action)
ReadFirstFile To search for a directly name/file name. DataLogging: Page 496 ReadFirstFile (Searching for a file/directory)
ReadNextFile To search for a directly name/file name. DataLogging: Page 498 ReadNextFile (Searching for a file/directory)
ReadClose To end the search. DataLogging: Page 500 ReadClose (Ending the search)
GetFile To transfer a logging file. DataLogging: Page 501 GetFile (Transferring logging files)
Dispose To release memory. Dot: Page 575 Dispose (release memory)
11 FUNCTIONS
11.2 Function List 427
*1 Act: ActUtlType, ActUtlType64, ActProgType, ActProgType64,
DataLogging: ActDataLogging, ActDataLogging64, ActProgDataLogging, ActProgDataLogging64,
Dot: DotUtilType, DotUtilType64,
Msg: ActSupportMsg, ActSupportMsg64
*2 Can be used only by pasting a control to a form for VC++. Cannot be used by creating an object.
Controls for 64-bit cannot be used in any development languages.
For the differences of each control, refer to the following:
• Considerations for using RnSFCPU

In order to protect the safety programmable controller system, an error code is returned when a function to
write data to the buffer memory or safety devices in safety mode is executed.
• Considerations for using QSCPU
In order to protect the safety programmable controller system, an error code is returned when a function to
write data to the buffer memory, write/set devices, or write clock data is executed.
11 FUNCTIONS
428 11.2 Function List
11.3 Details of Functions (For Act Control)
Open (Opening communication line)
Applicable controls
This function can be used for the following controls.
• 32-bit: ActProgType, ActUtlType
11
• 64-bit: ActProgType64, ActUtlType64
Feature
To open a communication line.
Format
■ VBA
lRet = object.Open()
Long lRet Returned value Output
■ Visual C++
■ Visual Basic .NET

IRet = object.Open()
Integer IRet Returned value Output
■ Visual C#
iRet = object.Open()
int iRet Returned value Output
Format (when creating an object)

■ Visual C++
hResult = object.Open( *lplRetCode )
HRESULT hResult Returned value of COM Output
LONG *lplRetCode Returned value of communication function Output
Returned value
Normal termination: '0' is returned.
Abnormal termination: Any value other than '0' is returned. (Page 588 ERROR CODES)
Description
The communication line is opened.
Lines are connected according to the set value of the Open function property.
• If the Open function property is changed after the completion of the Open function, the setting of
communication target is not changed.
To change the communication setting, close the communication line, set the setting of communication
target, and open the communication line again.
• Even when a CPU type which is different from the CPU used for the communication is set to the
ActCpuType property, the Open function may be completed normally.
In such a case, the connection range, usable method, or device range may be narrowed.
When executing the Open function, set the correct CPU type to the ActCpuType property.
11 FUNCTIONS
11.3 Details of Functions (For Act Control) 429
Close (Closing communication line)
Applicable controls
Feature
To close a communication line.
Format
■ VBA
lRet = object.Close()
■ Visual C++

IRet = object.Close()
■ Visual C#
iRet = object.Close()

■ Visual C++
hResult = object.Close( *lplRetCode )
Returned value
Description
The line connected using the Open function is closed.
11 FUNCTIONS
430 11.3 Details of Functions (For Act Control)
ReadDeviceBlock (Reading devices in batch)
Applicable controls
Feature 11
To read devices in batch.
Format
■ VBA
lRet = object.ReadDeviceBlock(szDevice, lSize, lData(0))
String szDevice Device name Input
Long lSize Number of read points Input
Long lData(n) Read device value Output
■ Visual C++
lRet = object.ReadDeviceBlock(szDevice, lSize, *lplData)
CString szDevice Device name Input
Long *lplData Read device value Output

IRet = object.ReadDeviceBlock(szDevice, iSize, iData(0))
Integer iSize Number of read points Input
Integer iData(n) Read device value Output
■ Visual C#
iRet = object.ReadDeviceBlock(szDevice, iSize, out iData[0])
int iSize Number of read points Input
int[n] iData Read device value Output

■ Visual C++
hResult = object.ReadDeviceBlock( szDevice, lSize, *lplData, *lplRetCode )
BSTR szDevice Device name Input
LONG lSize Number of read points Input
LONG *lplData Read device value Output
Returned value
Description
• The device values of lSize (iSize) are read in batch starting from the device specified for szDevice.
• The read device values are stored in IData (lplData or iData).
• For IData (lplData or iData), reserve arrays for more than the amount specified for ISize (iSize).
11 FUNCTIONS
• The maximum number of read points for lSize (iSize) should be the value which satisfies the following
condition:
Start read device number + Number of read points  Last device number
• When specifying bit devices, a multiple of 16 can be specified as a device number.
• Not applicable to inverter communication/robot controller communication.
• For IData (lplData or iData), reserve a memory area for the number of points specified for lSize (iSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• Devices of long timer contact (LTS), long timer coil (LTC), long retentive timer contact (LSTS), long retentive
timer coil (LSTC) cannot be read. Use the ReadDeviceRandom or GetDevice function.
How to specify devices

The following describes how to specify devices.
■ When specifying bit devices

Example: Read 3 points (3 words) of data in 16-point unit from the devices starting from M0.
Upper 2-byte Lower 2-byte
Not used ('0' is stored.) M0 to M15*1
M16 to M31*1
M32 to M47*1
*1 Devices are stored from the lower bit in the order of device number.
■ When specifying word devices

Example: Read 3 points of data from the devices starting from D0.
Not used ('0' is stored.) D0
D1
D2
■ When specifying CN200 and later devices of FXCPU

Example: Read 6 points of data from the devices starting from CN200.
For CN200 and later devices of FXCPU, 2 words are read for each 2 points. Reading only 1 point of data will result in an error.
Not used ('0' is stored.) L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202
■ When specifying FD devices (4-word devices)

Example: Read 6 points of data from the devices starting from FD0.
Not used ('0' is stored.) LL of FD0
LH of FD0
HL of FD0
HH of FD0
LL of FD1
LH of FD1
■ 8-bit devices assigned to gateway devices

Example: Read 4 points of data from the devices starting from EG0.
11 FUNCTIONS
(When 8-bit devices (from E0000 to E0007 of SHARP programmable controller) are assigned from EG0 to EG3.)
Not used ('0' is stored.) EG0
(E0001) (E0000)
EG1
(E0003) (E0002)
EG2
(E0005) (E0004)
EG3
(E0007) (E0006)
11
■ When specifying double word devices
Example: Read 3 points of data from the devices starting from LTN0.
H of LTN0 L of LTN0
H of LTN1 L of LTN1
H of LTN2 L of LTN2
11 FUNCTIONS
WriteDeviceBlock (Writing devices in batch)
Applicable controls
Feature
To write devices in batch.
Format
■ VBA
lRet = object.WriteDeviceBlock(szDevice, lSize, lData(0))
Long lSize Number of write points Input
Long lData(n) Device value to be written Input
■ Visual C++
lRet = object.WriteDeviceBlock(szDevice, lSize, *lplData)
Long *lplData Device value to be written Input

IRet = object.WriteDeviceBlock(szDevice, iSize, iData(0))
Integer iSize Number of write points Input
Integer iData(n) Device value to be written Input
■ Visual C#
iRet = object.WriteDeviceBlock(szDevice, iSize, ref iData[0])
int iSize Number of write points Input
int[n] iData Device value to be written Input

■ Visual C++
hResult = object.WriteDeviceBlock( szDevice, lSize, *lplData, *lplRetCode )
LONG lSize Number of write points Input
LONG *lplData Device value to be written Input
Returned value
Description
• The device values of lSize (iSize) are written in batch starting from the device specified for szDevice.
• The device values to be written are stored in lData (lplData or iData).
11 FUNCTIONS
• The maximum number of write points for lSize (iSize) should be the value which satisfies the following
condition:
Start write device number + Number of write points  Last device number
timer coil (LSTC) cannot be written. Use the WriteDeviceRandom or SetDevice function. 11
• If the function is run against the safety device in the RnSFCPU safety mode, an error code 0x010A42A5"
(an operation that can not be carried out in safety mode was performed) is returned.


Example: Write 3 points (3 words) of data in 16-point unit to the devices starting from M0.
Not used ('0' is stored.) M0 to M15*1
M16 to M31*1
M32 to M47*1

Example: Write 3 points of data to the devices starting from D0.
D1
D2

Example: Write 6 points of data to the devices starting from CN200.
For CN200 and later devices of FXCPU, 2 words are written for each 2 points. Writing only 1 point of data will result in an
error.
Not used ('0' is stored.) L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

Example: Write 6 points of data to the devices starting from FD0.
Not used ('0' is stored.) LL of FD0
LH of FD0
HL of FD0
HH of FD0
LL of FD1
LH of FD1
11 FUNCTIONS
Example: Write 4 points of data to the devices starting from EG0.
(E0001) (E0000)
EG1
(E0003) (E0002)
EG2
(E0005) (E0004)
EG3
(E0007) (E0006)

Example: Write 3 points of data to the devices starting from LTN0.
H of LTN0 L of LTN0
H of LTN1 L of LTN1
H of LTN2 L of LTN2
11 FUNCTIONS
ReadDeviceRandom (Reading devices randomly)
Applicable controls
Feature 11
To read devices randomly.
Read monitor types of inverters/robot controllers randomly.
Format
■ VBA
lRet = object.ReadDeviceRandom(szDeviceList, lSize, lData(0))
String szDeviceList Device name/monitor type Input
Long lData(n) Read device value Output
■ Visual C++
lRet = object.ReadDeviceRandom(szDeviceList, lSize,*lplData)
CString szDeviceList Device name/monitor type Input
Long *lplData Read device value Output

IRet = object.ReadDeviceRandom(szDeviceList, iSize, iData(0))
String szDeviceList Device name/monitor type Input
■ Visual C#
iRet = object.ReadDeviceRandom(szDevice, iSize, out iData[0])
String szDevice Device name/monitor type Input

■ Visual C++
hResult = object.ReadDeviceRandom( szDevice, lSize, *lplData, *lplRetCode )
BSTR szDevice Device name/monitor type Input
LONG *lplData Read device value Output
Returned value
Description
• Data of a device group/monitor type group specified for szDeviceList (szDevice) is written for the size of ISize (iSize).
• The read device values are stored in IData (lplData or iData).
11 FUNCTIONS
• Use the line feed symbol to separate the character string specified for the device list. The line feed symbol is not necessary
to be suffixed to the last device.
Example:
When using Visual Basic .NET, VBA: "D0" & vbLf & "D1" & vbLf & "D2"
When using Visual C++: D0\nD1\nD2
When using Visual C#: D0\nD1\nD2
• For the items that can be monitored (monitor types), refer to the following:
Page 149 ACCESSIBLE DEVICES AND DEVICE TYPES
• The maximum number of read points for lSize (iSize) is 0x7FFFFFFF.


■ When devices are specified as follows (number of points: 3 points)

When using Visual Basic .NET, VBA: "M0" & vbLf & "D0" & vbLf & "K8M0"
When using Visual C++: M0\nD0\nK8M0
When using Visual C#: M0\nD0\nK8M0

Not used ('0' is stored.) M0
D0
M16 to M31*1 M0 to M15*1
■ When devices including CN200 and later of FXCPU are specified (total number of points: 3
points)
For CN200 and later devices of FXCPU, 2 words are read for each point when reading devices randomly.
When using Visual Basic .NET, VBA: "D0" & vbLf & "CN200" & vbLf & "D1"
When using Visual C++: D0\nCN200\nD1
When using Visual C#: D0\nCN200\nD1

H of CN200 L of CN200
■ When devices including FD are specified (total number of points: 3 points)

When using Visual Basic .NET, VBA: "D0" & vbLf & "FD0" & vbLf & "D1"
When using Visual C++: D0\nFD0\nD1
When using Visual C#: D0\nFD0\nD1

LL of FD0
D1
■ When devices including EG are specified (total number of points: 3 points)

The following is the example when 8-bit devices (E0000 and E0001 of SHARP programmable controller) are assigned to
EG0.
When using Visual Basic .NET, VBA: "D0" & vbLf & "EG0" & vbLf & "D1"
When using Visual C++: D0\nEG0\nD1
When using Visual C#: D0\nEG0\nD1
11 FUNCTIONS
EG0
(E0001)
D1
■ When double word devices are specified

When using Visual Basic .NET, VBA: "LTN0" & vbLf & "LTN1" & vbLf & "LTN2"
When using Visual C++: LTN0\nLTN1\nLTN2
When using Visual C#: LTN0\nLTN1\nLTN2

11
H of LTN0 L of LTN0
H of LTN1 L of LTN1
H of LTN2 L of LTN2
■ When monitor types (1, 2, and 5) of inverter are specified (total number of points: 3 points)
When using Visual Basic .NET, VBA: "1" & vbLf &"2" & vbLf &"5"
When using Visual C++: 1\n2\n5
When using Visual C#: 1\n2\n5

H of 1 L of 1
H of 2 L of 2
H of 5 L of 5
■ When monitor types (223.102.A, and 223.103.B) of robot controller are specified (total number
of points: 2 points)
Format: (Request ID).(Data type).(Argument)
When using Visual Basic .NET, VBA: "223.102.A" & vbLf &"223.103.B"
When using Visual C++: 223.102.A\n223.103.B
When using Visual C#: 223.102.A\n223.103.B

H of 223.102.A L of 223.102.A
H of 223.103.B L of 223.103.B
11 FUNCTIONS
WriteDeviceRandom (Writing devices randomly)
Applicable controls
Feature
To write devices randomly.
Format
■ VBA
lRet = object.WriteDeviceRandom(szDeviceList, lSize,lData(0))
String szDeviceList Device name Input
Long lData(n) Device value to be written Input
■ Visual C++
lRet = object.WriteDeviceRandom(szDeviceList, lSize,*lplData)
CString szDeviceList Device name Input
Long *lplData Device value to be written Input

IRet = object.WriteDeviceRandom(szDeviceList, iSize, iData(0))
■ Visual C#
iRet = object.WriteDeviceRandom(szDevice, iSize, ref iData[0])

■ Visual C++
hResult = object.WriteDeviceRandom( szDeviceList, lSize, *lplData,*lplRetCode )
BSTR szDeviceList Device name Input
LONG *lplData Device value to be written Input
Returned value
11 FUNCTIONS
Description
• Data of a device group specified for szDeviceList (szDevice) is written for the size of ISize (iSize).
• The device values to be written are stored in lData (lplData or iData).
Example:
When using Visual C#: D0\nD1\nD2 11
• The maximum number of write points for lSize (iSize) is 0x7FFFFFFF.

• An error is returned when a Q motion CPU is accessed.



D0
*1
M16 to M31 M0 to M15*1
points)
For CN200 or later of FXCPU, 2 words are written for each point when writing devices randomly.


LL of FD0
D1
11 FUNCTIONS
EG0.

EG0
(E0001) (E0000)
D1


H of LTN0 L of LTN0
H of LTN1 L of LTN1
H of LTN2 L of LTN2
11 FUNCTIONS
SetDevice (Setting device data)
Applicable controls
Feature 11
To set one point of device.
Format
■ VBA
lRet = object.SetDevice(szDevice, lData)
Long lData Set data Input
■ Visual C++
lRet = object.SetDevice(szDevice, lData)
Long lData Set data Input

IRet = object.SetDevice(szDevice, iData)
Integer iData Set data Input
■ Visual C#
iRet = object.SetDevice(szDevice, iData)
int iData Set data Input

■ Visual C++
hResult = object.SetDevice( szDevice, lData, *lplRetCode )
LONG lData Set data Input
Returned value
Description
• One point of device specified for szDevice is specified using lData (iData).
• When specifying bit devices, the least significant bit of the lData value (varData value or iData value) is valid.
11 FUNCTIONS

Example: M0

Example: D0

Example: LTN0
H of LTN0 L of LTN0
■ When specifying double word devices (digit specification)

Example: K8M0
M16 to M31*1 M0 to M15*1

Example: CN200
■ When specifying gateway devices

Example: When 8-bit devices (E0000 and E0001 of SHARP programmable controller) are assigned to EG0
(E0001) (E0000)
11 FUNCTIONS
GetDevice (Acquiring device data)
Applicable controls
Feature 11
To acquire one point of device.
Acquire one point monitor type data of inverter/robot controller.
Format
■ VBA
lRet = object.GetDevice(szDevice, lData)
Long lData Acquired data Output
■ Visual C++
lRet = object.GetDevice(szDevice, *lplData)
CString szDevice Device name/monitor type Input
Long *lplData Acquired data Output

IRet = object.GetDevice(szDevice, iData)
Integer iData Acquired data Output
■ Visual C#
iRet = object.GetDevice(szDevice, out iData)
int iData Acquired data Output

■ Visual C++
hResult = object.GetDevice( szDevice, *lplData, *lplRetCode )
BSTR szDevice Device name/monitor type Input
LONG *lplData Acquired data Output
Returned value
Description
One point of device data specified for szDevice is stored in lData (lplData or iData).
For the items that can be monitored (monitor types), refer to the following:
Page 149 ACCESSIBLE DEVICES AND DEVICE TYPES
11 FUNCTIONS
The following describes how to specify devices/monitor type.

Example: M0

Example: D0

Example: LTN0
H of LTN0 L of LTN0

Example: K8M0
M16 to M31*1 M0 to M15*1

Example: CN200

(E0001) (E0000)
■ When specifying monitor types of inverter

Example: 2
H of 1 L of 1
■ When specifying monitor types of robot controller

Format: (Request ID).(Data type).(Argument)
Example: 223.102.A
H of 223.102.A L of 223.102.A
11 FUNCTIONS
ReadBuffer (Reading data from buffer memory)
Applicable controls
Feature 11
To read data from the buffer memory of special function module.
Format
■ VBA
lRet = object.ReadBuffer(lStartIO,lAddress,lReadSize, iData(0))
Long lStartIO Start I/O number of module from which values are Input
read
Long lAddress Buffer memory address Input
Long lReadSize Read size Input
Integer iData(n) Values read from buffer memory Output
■ Visual C++
lRet = object.ReadBuffer(lStartIO, lAddress, lReadSize, *lpsData)
Long lStartIO Start I/O number of module from which values are Input
read
Long lReadSize Read size Input
Short *lpsData Values read from buffer memory Output

IRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, iData(0))
Integer iStartIO Start I/O number of module from which values are Input
read
Integer iAddress Buffer memory address Input
Integer iReadSize Read size Input
short iData(n) Values read from buffer memory Output
■ Visual C#
iRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, out sData[0])
int iStartIO Start I/O number of module from which values are Input
read
int iAddress Buffer memory address Input
int iReadSize Read size Input
short[n] sData Values read from buffer memory Output

■ Visual C++
hResult = object.ReadBuffer( lStartIO, lAddress, lReadSize, *lpsData, *lplRetCode )
LONG lStartIO Start I/O number of module from which values are Input
read
LONG lAddress Buffer memory address Input
LONG lReadSize Read size Input
SHORT *lpsData Values read from buffer memory Output
11 FUNCTIONS
Returned value
Description
• For the start I/O number of the module specified for IStartIO (iStartIO), specify the value of the actual start I/O number
divided by 16.
For an FX5CPU, specify the module number on the target station side.
• Buffer values of buffer memory address specified for IAddress (iAddress) of the special function module of the start I/O
number specified for IStartIO (iStartIO) are read for the size of IReadSize (iReadSize).
• When performing CPU COM communication with FXCPU as a connected station or GX Simulator2 communication, specify
the block number (0 to 7) of a special expansion device for the start I/O number of a module and 0 to 32767 for the buffer
memory address.
• For iData (lpsData or sData), reserve arrays for more than the amount specified for lReadSize (iReadSize).
• An error is returned when an R motion CPU or a Q motion CPU is accessed.

• For iData (lpsData or sData), reserve a memory area for the number of points specified for lReadSize
(iReadSize).
• When reading data from buffer memory (ReadBuffer) on QCPU (Q mode), the read operation can only be
performed on the Q series-dedicated modules.
Furthermore, data cannot be read from the shared memory of QCPU (Q mode).
Applicable communication routes

The following table shows the applicable communication routes.
Communication route Property setting Applic
ActUnitType ActProtocolType ability
Serial Connected module: R series-compatible UNIT_RJ71C24 PROTOCOL_SERIAL 

communication C24
Connected module: Q series-compatible UNIT_QJ71C24 
C24
Connected module: L series-compatible UNIT_LJ71C24 
C24
Connected module: FX extended port UNIT_FX485BD 
11 FUNCTIONS
Ethernet communication UNIT_RJ71EN71 PROTOCOL_TCPIP, 

PROTOCOL_UDPIP
UNIT_RJ71EN71_DIRECT PROTOCOL_UDPIP
UNIT_QJ71E71 PROTOCOL_TCPIP,
PROTOCOL_UDPIP
UNIT_LJ71E71 PROTOCOL_TCPIP,
PROTOCOL_UDPIP
UNIT_RETHER PROTOCOL_TCPIP,
PROTOCOL_UDPIP
11
UNIT_RETHER_DIRECT PROTOCOL_UDPIP
UNIT_FXVETHER PROTOCOL_TCPIP 
UNIT_FXVETHER_DIRECT PROTOCOL_UDPIP
UNIT_LNETHER PROTOCOL_TCPIP 
UNIT_LNETHER, PROTOCOL_UDPIP
UNIT_LNETHER_DIRECT
UNIT_QNETHER PROTOCOL_TCPIP
UNIT_QNETHER, PROTOCOL_UDPIP
UNIT_QNETHER_DIRECT
UNIT_RJ71GN11 PROTOCOL_TCPIP,
PROTOCOL_UDPIP
UNIT_NZ2GF_ETB PROTOCOL_TCPIP
UNIT_NZ2GF_ETB, PROTOCOL_UDPIP
UNIT_NZ2GF_ETB_DIRECT
UNIT_FXETHER PROTOCOL_TCPIP
UNIT_FXETHER_DIRECT PROTOCOL_UDPIP
CPU COM Connection target CPU: FX5CPU UNIT_FXVCPU PROTOCOL_SERIAL 
communication
Connection target CPU: QCPU (Q mode) UNIT_QNCPU 
Connection target CPU: LCPU UNIT_LNCPU 
Connection target CPU: Q motion CPU UNIT_QNMOTION 
Connection target CPU: FXCPU UNIT_FXCPU *1
USB Connection target CPU: RCPU UNIT_RUSB PROTOCOL_USB 
communication
Connection target CPU: LHCPU UNIT_LHUSB 
Connection target CPU: FX5CPU UNIT_FXVUSB 
Connection target CPU: QCPU (Q mode) UNIT_QNUSB 
Connection target CPU: LCPU UNIT_LNUSB 
Connection target CPU: QSCPU UNIT_QSUSB 
Connection target CPU: Q motion CPU UNIT_QNMOTIONUSB 
Connection target CPU: FXCPU UNIT_FXCPU 
MELSECNET/H communication UNIT_MNETHBOARD PROTOCOL_MNETH *2
CC-Link IE Controller Network communication UNIT_MNETGBOARD PROTOCOL_MNETG
CC-Link IE Field Network communication UNIT_CCIEFBOARD PROTOCOL_CCIEF
CC-Link communication UNIT_CCLINKBOARD PROTOCOL_CCLINK
CC-Link system RS-232 interface communication UNIT_G4QCPU PROTOCOL_SERIAL 
GX Simulator2 communication UNIT_SIMULATOR2  
GX Simulator3 communication (RCPU) UNIT_SIMULATOR3 
GX Simulator3 communication (FX5CPU)
MT Simulator2 communication UNIT_SIMULATOR2  
GOT gateway device communication UNIT_A900GOT PROTOCOL_UDPIP 
11 FUNCTIONS
GOT transparent function communication UNIT_RJ71C24, UNIT_FXVCPU, PROTOCOL_SERIAL, 

UNIT_QNCPU, UNIT_LNCPU PROTOCOL_USBGOT
UNIT_FXCPU *1
UNIT_QJ71C24, UNIT_LJ71C24, 
UNIT_GOT_RJ71EN71,
UNIT_GOT_QJ71E71,
UNIT_GOT_LJ71E71,
UNIT_GOT_RETHER,
UNIT_GOT_QNETHER,
UNIT_GOT_LNETHER,
UNIT_A900GOT,
UNIT_GOT_NZ2GF_ETB,
UNIT_GOT_FXETHER,
UNIT_GOT_FXENET
UNIT_GOTETHER_RJ71C24, PROTOCOL_TCPIP 
UNIT_GOTETHER_FXVCPU,
UNIT_GOTETHER_QNCPU,
UNIT_GOTETHER_LNCPU
UNIT_GOTETHER_FXCPU *1
UNIT_GOTETHER_QBUS 
UNIT_GOTETHER_QN_ETHER 
Inverter communication - COMM_RS232C, COMM_USB 
*1 An error is returned when the CPU is other than FX3U, FX3UC, FX3G and FX3GC.
*2 An error is returned when the own board is accessed.
11 FUNCTIONS
WriteBuffer (Writing data to buffer memory)
Applicable controls
Feature 11
To write data to the buffer memory of special function module.
Format
■ VBA
lRet = object.WriteBuffer(lStartIO, lAddress, lWriteSize, iData(0))
Long lStartIO Start I/O number of module to which values are Input
written
Long lWriteSize Write size Input
Integer iData(n) Values written from buffer memory Input
■ Visual C++
lRet = object.WriteBuffer(lStartIO, lAddress, lWriteSize, *lpsData)
Long lStartIO Start I/O number of module to which values are Input
written
Long lWriteSize Write size Input
Short *lpsData Values written from buffer memory Input
11 FUNCTIONS
IRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, iData(0))
Integer iStartIO Start I/O number of module to which values are Input
written
Integer iWriteSize Write size Input
short iData(n) Values written from buffer memory Input
■ Visual C#
iRet = object. WriteBuffer (iStartIO, iAddress, iWriteSize, ref sData[0])
int iStartIO Start I/O number of module to which values are Input
written
int iWriteSize Write size Input
short[n] sData Values written from buffer memory Input

■ Visual C++
hResult = object.WriteBuffer( lStartIO, lAddress, lWriteSize, *lpsData, *lplRetCode )
LONG lStartIO Start I/O number of module to which values are Input
written
LONG lAddress Buffer memory address Input
LONG lWriteSize Write size Input
SHORT *lpsData Values written from buffer memory Input
Returned value
Description
• For the start I/O number of the module specified for IStartIO (iStartIO), specify the value of the actual start I/O number
divided by 16.
• Buffer values of buffer memory address specified for IAddress (iAddress) of the special function module of the start I/O
number specified for IStartIO (iStartIO) are written for the size of IWriteSize (iWriteSize).
memory address.
• For iData (lpsData or sData), reserve arrays for more than the amount specified for lWriteSize (iWriteSize).

• For iData (lpsData, varData, or sData), reserve a memory area for the number of points specified for
lWriteSize (varWriteSize or iWriteSize).
• When buffer memory write (WriteBuffer) is performed for QCPU (Q mode), write operation may be
performed for only the Q series-dedicated module.
Furthermore, data cannot be written to the shared memory of QCPU (Q mode).
11 FUNCTIONS

communication C24
Connected module: Q series-compatible
C24
UNIT_QJ71C24 
11
C24
Connected module: FX extended port UNIT_FX485BD 
PROTOCOL_UDPIP
PROTOCOL_UDPIP
PROTOCOL_UDPIP
PROTOCOL_UDPIP
UNIT_FXVETHER PROTOCOL_TCPIP 
UNIT_LNETHER_DIRECT
UNIT_QNETHER_DIRECT
PROTOCOL_UDPIP
communication Connection target CPU: QCPU (Q mode) UNIT_QNCPU 
communication
Connection target CPU: QSCPU UNIT_QSUSB *2
11 FUNCTIONS
GX Simulator2 communication UNIT_SIMULATOR2 - 

GX Simulator3 communication (RCPU) UNIT_SIMULATOR3 
MT Simulator2 communication UNIT_SIMULATOR2 - 
UNIT_QNCPU, UNIT_LNCPU PROTOCOL_USBGOT
UNIT_FXCPU *1
UNIT_GOT_RJ71EN71,
UNIT_GOT_QJ71E71,
UNIT_GOT_LJ71E71,
UNIT_GOT_RETHER,
UNIT_GOT_QNETHER,
UNIT_GOT_LNETHER,
UNIT_A900GOT,
UNIT_GOT_NZ2GF_ETB,
UNIT_GOT_FXETHER,
UNIT_GOT_FXENET
UNIT_GOTETHER_LNCPU
UNIT_GOTETHER_FXCPU *1
*1 An error is returned when the CPU is other than FX3U, FX3UC, FX3G and FX3GC.
*2 The error code "0x010A42A0" (the access password mismatch) is returned when accessing QSCPU.
11 FUNCTIONS
GetClockData (Reading clock data)
Applicable controls
Feature 11
To read clock data from a programmable controller CPU.
Format
■ VBA
lRet = object.GetClockData(iYear, iMonth, iDay, iDayOfWeek, iHour, iMinute, iSecond)
Integer iYear Read year value Output
Integer iMonth Read month value Output
Integer iDay Read day value Output
Integer iDayOfWeek Read day-of-week value Output
Integer iHour Read hour value Output
Integer iMinute Read minute value Output
Integer iSecond Read second value Output
■ Visual C++
lRet = object.GetClockData(*lpsYear, *lpsMonth, *lpsDay, *lpsDayOfWeek, *lpsHour, *lpsMinute, *lpsSecond)
Short *lpsYear Read year value Output
Short *lpsMonth Read month value Output
Short *lpsDay Read day value Output
Short *lpsDayOfWeek Read day-of-week value Output
Short *lpsHour Read hour value Output
Short *lpsMinute Read minute value Output
Short *lpsSecond Read second value Output

IRet = object.GetClockData(iYear, iMonth, iDay, iDayOfWeek,iHour, iMinute,iSecond)
short iYear Read year value Output
short iMonth Read month value Output
short iDay Read day value Output
short iDayOfWeek Read day-of-week value Output
short iHour Read hour value Output
short iMinute Read minute value Output
short iSecond Read second value Output
■ Visual C#
hResult = object.GetClockData(out sYear, out sMonth, out sDay, out sDayOfWeek,out sHour, out sMinute, out sSecond)
short sYear Read year value Output
short sMonth Read month value Output
short sDay Read day value Output
short sDayOfWeek Read day-of-week value Output
short sHour Read hour value Output
short sMinute Read minute value Output
short sSecond Read second value Output
11 FUNCTIONS
■ Visual C++
hResult = object.GetClockData( *lpsYear, *lpsMonth, *lpsDay, *lpsDayOfWeek, *lpsHour, *lpsMinute, *lpsSecond, *lplRetCode
)
SHORT *lpsYear Read year value Output
SHORT *lpsMonth Read month value Output
SHORT *lpsDay Read day value Output
SHORT *lpsDayOfWeek Read day-of-week value Output
SHORT *lpsHour Read hour value Output
SHORT *lpsMinute Read minute value Output
SHORT *lpsSecond Read second value Output
Returned value
Description
• An error is returned when the correct clock data is not set to the programmable controller CPU.
• The values stored in iYear (lpsYear or sYear) are: the four digits of year for RCPU and QCPU (Q mode) and the last two
digits of year for any other CPUs.
Note that the applicable years for RCPU and QCPU (Q mode) are from 1980 to 2079.
• The values to be stored in iDayOfWeek (lpsDayOfWeek or sDayOfWeek) are as follows:
Value Day of Week
0 Sunday
1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5 Friday
6 Saturday

• The clock data can be read on FXCPUs with the built-in clock.
For FXCPUs without the built-in clock, an error is returned.
• Note that an error of transfer time may occur in clock setting.


communication C24
C24
C24
Connected module: FX extended port UNIT_FX485BD 
11 FUNCTIONS

PROTOCOL_UDPIP
PROTOCOL_UDPIP
PROTOCOL_UDPIP
PROTOCOL_UDPIP
11
UNIT_FXVETHER PROTOCOL_TCPIP
UNIT_LNETHER PROTOCOL_TCPIP
UNIT_LNETHER_DIRECT
UNIT_QNETHER_DIRECT
PROTOCOL_UDPIP
communication
communication Connection target CPU: LHCPU UNIT_LHUSB 
Connection target CPU: QSCPU UNIT_QSUSB 
GX Simulator3 communication (RCPU) UNIT_SIMULATOR3
11 FUNCTIONS

UNIT_QNCPU, UNIT_LNCPU, PROTOCOL_USBGOT
UNIT_FXCPU, UNIT_QJ71C24,
UNIT_LJ71C24,
UNIT_GOT_RJ71EN71,
UNIT_GOT_QJ71E71,
UNIT_GOT_LJ71E71,
UNIT_GOT_RETHER,
UNIT_GOT_QNETHER,
UNIT_GOT_LNETHER,
UNIT_A900GOT,
UNIT_GOT_NZ2GF_ETB,
UNIT_GOT_FXETHER,
UNIT_GOT_FXENET
UNIT_GOTETHER_RJ71C24, PROTOCOL_TCPIP
UNIT_GOTETHER_LNCPU,
UNIT_GOTETHER_FXCPU,
UNIT_GOTETHER_QBUS,
UNIT_GOTETHER_QN_ETHER
11 FUNCTIONS
SetClockData (Writing clock data)
Applicable controls
Feature 11
To write clock data to a programmable controller CPU.
Format
■ VBA
object.SetClockData(iYear, iMonth, iDay, iDayOfWeek, iHour, iMinute, iSecond)
Integer iYear Year value to be written Input
Integer iMonth Month value to be written Input
Integer iDay Day value to be written Input
Integer iDayOfWeek Day-of-week value to be written Input
Integer iHour Hour value to be written Input
Integer iMinute Minute value to be written Input
Integer iSecond Second value to be written Input
■ Visual C++
lRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
Short sYear Year value to be written Input
Short sMonth Month value to be written Input
Short sDay Day value to be written Input
Short sDayOfWeek Day-of-week value to be written Input
Short sHour Hour value to be written Input
Short sMinute Minute value to be written Input
Short sSecond Second value to be written Input

IRet = object.SetClockData(iYear, iMonth, iDay, iDayOfWeek, iHour, iMinute,iSecond)
short iYear Year value to be written Input
short iMonth Month value to be written Input
short iDay Day value to be written Input
short iDayOfWeek Day-of-week value to be written Input
short iHour Hour value to be written Input
short iMinute Minute value to be written Input
short iSecond Second value to be written Input
■ Visual C#
short sYear Year value to be written Input
short sMonth Month value to be written Input
short sDay Day value to be written Input
short sDayOfWeek Day-of-week value to be written Input
short sHour Hour value to be written Input
short sMinute Minute value to be written Input
short sSecond Second value to be written Input
11 FUNCTIONS
■ Visual C++
hResult = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond, *lplRetCode )
SHORT sYear Year value to be written Input
SHORT sMonth Month value to be written Input
SHORT sDay Day value to be written Input
SHORT sDayOfWeek Day-of-week value to be written Input
SHORT sHour Hour value to be written Input
SHORT sMinute Minute value to be written Input
SHORT sSecond Second value to be written Input
Returned value
Description
• An error is returned when the clock data to be set is not the correct value.
• The applicable values to be specified for iYear (sYear) are: the four digits of year for RCPU and QCPU (Q mode) and the
last two digits of year for any other CPUs.
An error occurs when four digits are set to a CPU other than RCPU and QCPU (Q mode).
• The values to be specified in iDayOfWeek (sDayOfWeek) are as follows:
Value Day of Week
0 Sunday
1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5 Friday
6 Saturday



communication C24
C24
C24
Connected module: FX extended port UNIT_FX485BD 
11 FUNCTIONS

PROTOCOL_UDPIP
PROTOCOL_UDPIP
PROTOCOL_UDPIP
PROTOCOL_UDPIP
11
UNIT_FXVETHER PROTOCOL_TCPIP
UNIT_LNETHER PROTOCOL_TCPIP
UNIT_LNETHER_DIRECT
UNIT_QNETHER_DIRECT
PROTOCOL_UDPIP
communication
communication Connection target CPU: LHCPU UNIT_LHUSB 
GX Simulator2 communication UNIT_SIMULATOR2 - 
11 FUNCTIONS

UNIT_QNCPU, UNIT_LNCPU, PROTOCOL_USBGOT
UNIT_FXCPU, UNIT_QJ71C24,
UNIT_LJ71C24,
UNIT_GOT_RJ71EN71,
UNIT_GOT_QJ71E71,
UNIT_GOT_LJ71E71,
UNIT_GOT_RETHER,
UNIT_GOT_QNETHER,
UNIT_GOT_LNETHER,
UNIT_A900GOT,
UNIT_GOT_NZ2GF_ETB,
UNIT_GOT_FXETHER,
UNIT_GOT_FXENET
UNIT_GOTETHER_RJ71C24, PROTOCOL_TCPIP
UNIT_GOTETHER_LNCPU,
UNIT_GOTETHER_FXCPU,
UNIT_GOTETHER_QBUS,
UNIT_GOTETHER_QN_ETHER
11 FUNCTIONS
GetCpuType (Reading programmable controller CPU model)
Applicable controls
Feature 11
To read the model character string and the model code of programmable controller CPU in communication, network board,
and GOT.
Format
■ VBA
lRet = object.GetCpuType(szCpuName, lCpuType)
String szCpuName Programmable controller CPU model character string Output
Long lCpuType Programmable controller CPU model code Output
■ Visual C++
lRet = object.GetCpuType(*szCpuName, *lplCpuType)
BSTR *szCpuName Programmable controller CPU model character string Output
Long *lplCpuType Programmable controller CPU model code Output

IRet = object.GetCpuType(szCpuName, ICpuType)
Integer ICpuType Programmable controller CPU model code Output
■ Visual C#
iRet = object.GetCpuType (out szCpuName, out iCpuType)
int iCpuType Programmable controller CPU model code Output

■ Visual C++
hResult = object.GetCpuType( *szCpuName, *lplCpuType, *lplRetCode )
BSTR *szCpuName Programmable controller CPU model character string Output
LONG *lplCpuType Programmable controller CPU model code Output
Returned value
Description
• The model and the model code of the communication target programmable controller CPU are stored in szCpuName and
ICpuType (lplCpuType or iCpuType) respectively.
• The model character string of the programmable controller CPU is returned in UNICODE.
11 FUNCTIONS
Model character string and model code
The following tables show the model character strings and the model codes of programmable controller CPU, network board,
and GOT, which are read by the GetCpuType function.
CPU type When connecting to CPU/own board When connecting to GX Simulator2 or GX
Network board/GOT Simulator3
Model character string Model code Model character string Model code
CPU_R00CPU R00CPU 48A0H -
CPU_R01CPU R01CPU 48A1H
CPU_R02CPU R02CPU 48A2H
CPU_R04CPU R04CPU 4800H
CPU_R04ENCPU R04ENCPU 4805H
CPU_R08PCPU R08PCPU 4841H
CPU_R08PSFCPU R08PSFCPU 4851H
CPU_R08SFCPU R08SFCPU 4891H
CPU_R16MTCPU R16MTCPU 4C00H
CPU_R32MTCPU R32MTCPU 4C01H
CPU_R12CCPU-V R12CCPU-V 4820H
CPU_L04HCPU L04HCPU 48C0H
CPU_Q00JCPU Q00JCPU 250H Q00JCPU 250H
CPU_Q00UJCPU Q00UJCPU 260H Q00UJCPU 260H
CPU_Q00CPU Q00CPU 251H Q00CPU 251H
CPU_Q00UCPU Q00UCPU 261H Q00UCPU 261H
CPU_Q01CPU Q01CPU 252H Q01CPU 252H
CPU_Q03UDCPU Q03UDCPU 268H Q03UDCPU 268H
CPU_Q03UDECPU Q03UDECPU Q03UDECPU
CPU_Q03UDVCPU Q03UDVCPU 366H -
CPU_Q04UDHCPU Q04UDHCPU 269H Q04UDHCPU 269H
CPU_Q04UDEHCPU Q04UDEHCPU Q04UDEHCPU
CPU_Q04UDPVCPU Q04UDPVCPU
CPU_Q06UDHCPU Q06UDHCPU 26AH Q06UDHCPU 26AH
11 FUNCTIONS
CPU type When connecting to CPU/own board When connecting to GX Simulator2 or GX
Network board/GOT Simulator3
Model character string Model code Model character string Model code
CPU_Q12PRHCPU Q12PRHCPU 4BH Q12PRHCPU 4BH
CPU_Q13UDHCPU Q13UDHCPU 26BH Q13UDHCPU 26BH
11
CPU_Q13UDVCPU Q13UDVCPU 36AH -
CPU_Q25PRHCPU Q25PRHCPU 4CH Q25PRHCPU 4CH
CPU_Q26UDHCPU Q26UDHCPU 26CH Q26UDHCPU 26CH
CPU_Q26UDVCPU Q26UDVCPU 36CH -
CPU_Q50UDEHCPU Q50UDEHCPU 26DH
CPU_Q100UDEHCPU Q100UDEHCPU 26EH
CPU_L02SCPU L02SCPU 543H -
CPU_L02CPU L02CPU 541H
CPU_L26CPU-BT L26CPU-BT 542H
CPU_Q12DCCPU-V Q12DCCPU-V 2043H -
CPU_Q24DHCCPU-V Q24DHCCPU-V 2044H
CPU_Q24DHCCPU-LS Q24DHCCPU-LS 2045H
CPU_Q24DHCCPU-VG Q24DHCCPU-VG 2046H
CPU_Q26DHCCPU-LS Q26DHCCPU-LS 2047H
CPU_QS001CPU QS001CPU 230H
CPU_Q172DCPU Q172DCPU 2014H
CPU_Q173DCPU Q173DCPU 2015H
CPU_Q172DSCPU Q172DSCPU 2018H
CPU_Q173DSCPU Q173DSCPU 2019H
CPU_FX3S FX3S F5H -
CPU_FX3G FX3G F4H FX3G F4H
CPU_FX3GC
CPU_FX3U FX3UC F3H FX3UC F3H
CPU_FX3UC
CPU_FX5UCPU FX5UCPU 4A00H -
CPU_FX5UJCPU FX5UJCPU 4B00H
Q80BD-J71LP21-25 Q80BD-J71LP21-25 90H
Q80BD-J71LP21G Q80BD-J71LP21G
Q80BD-J71BR11 Q80BD-J71BR11
Q81BD-J71GF11-T2 Q81BD-J71GF11-T2
GOT *1 E340H
A800 0xA8 A8H
CRnD-7xx/CR75x-D CRnD-7xx 03H
*1 A product model number of GOT is displayed.
11 FUNCTIONS
SetCpuStatus (Remote control)
Applicable controls
Feature
To perform a remote operation of programmable controller CPU.
Format
■ VBA
lRet = object.SetCpuStatus(lOperation)
Long lOperation Remote RUN/STOP/PAUSE Input
■ Visual C++
lRet = object.SetCpuStatus(lOperation)
Long lOperation Remote RUN/STOP/PAUSE Input

IRet = object.SetCpuStatus(IOperation)
Integer IOperation Remote RUN/STOP/PAUSE Input
■ Visual C#
iRet = object.SetCpuStatus (iOperation)
int iOperation Remote RUN/STOP/PAUSE Input

■ Visual C++
hResult = object.SetCpuStatus(lOperation, *lplRetCode )
LONG lOperation Remote RUN/STOP/PAUSE Input
Returned value
Description
The operation specified for IOperation (iOperation) is performed.
An error occurs when a value other than the following values is specified.
Value Operation
0 Remote RUN
1 Remote STOP
2 Remote PAUSE
11 FUNCTIONS
• Since FXCPUs do not feature the PAUSE switch as programmable controller CPUs, an error is returned
when remote pause is specified in SetCpuStatus.
• An error is returned when a Q motion CPU is accessed and PAUSE is specified.
• An error is returned when an R motion CPU is accessed.

11
Communication route Property setting Appli
ActUnitType ActProtocolType cabilit
y
communication C24
C24
C24
Connected module: FX extended port UNIT_FX485BD *1,*2
PROTOCOL_UDPIP
PROTOCOL_UDPIP
PROTOCOL_UDPIP
PROTOCOL_UDPIP
UNIT_FXVETHER PROTOCOL_TCPIP *1
UNIT_LNETHER_DIRECT
UNIT_QNETHER_DIRECT
PROTOCOL_UDPIP
UNIT_FXETHER PROTOCOL_TCPIP *1
CPU COM Connection target CPU: FX5CPU UNIT_FXVCPU PROTOCOL_SERIAL *1
communication
Connection target CPU: Q motion CPU UNIT_QNMOTION 
11 FUNCTIONS
Communication route Property setting Appli
ActUnitType ActProtocolType cabilit
y
communication
Connection target CPU: Q motion CPU UNIT_QNMOTIONUSB 
GX Simulator3 communication (FX5CPU) *1
MT Simulator2 communication UNIT_SIMULATOR2 - 
GOT transparent function communication UNIT_RJ71C24, UNIT_QNCPU, PROTOCOL_SERIAL, 
UNIT_LNCPU PROTOCOL_USBGOT
UNIT_FXVCPU, UNIT_FXCPU *1
UNIT_GOT_RJ71EN71,
UNIT_GOT_QJ71E71,
UNIT_GOT_LJ71E71,
UNIT_GOT_RETHER,
UNIT_GOT_QNETHER,
UNIT_GOT_LNETHER,
UNIT_A900GOT,
UNIT_GOT_NZ2GF_ETB
UNIT_GOT_FXETHER, *1
UNIT_GOT_FXENET
UNIT_GOTETHER_LNCPU
UNIT_GOTETHER_FXVCPU, *1
UNIT_GOTETHER_FXCPU
*1 An error is returned when PAUSE is specified.

*2 An error is returned when the CPU is other than FX3S, FX3U, FX3UC, FX3G and FX3GC.
11 FUNCTIONS
EntryDeviceStatus (Registering devices for status monitoring)
Applicable controls
Feature
To register devices whose status to be monitored. 11
Format
■ VBA
lRet = object.EntryDeviceStatus(szDeviceList, lSize, lMonitorCycle, lData(0))
String szDeviceList Registered device name list Input
Long lSize Number of registered device points Input
Long lMonitorCycle Status monitoring time interval Input
Long lData(n) Registered device value list Input
■ Visual C++
lRet = object.EntryDeviceStatus (szDeviceList, lSize, lMonitorCycle, *lplData)
CString szDeviceList Registered device name list Input
Long lSize Number of registered device points Input
Long lMonitorCycle Status monitoring time interval Input
Long *lplData Registered device value list Input

IRet = object.EntryDeviceStatus(szDeviceList, ISize,IMonitorCycle, IData(0))
Integer ISize Number of registered device points Input
Integer IMonitorCycle Status monitoring time interval Input
Integer IData(n) Registered device value list Input
■ Visual C#
iRet = object. EntryDeviceStatus(szDeviceList, iSize, iMonitorCycle, ref iData[0])
int iSize Number of registered device points Input
int iMonitorCycle Status monitoring time interval Input
int[n] iData Registered device value list Input
Returned value
Description
• A device group for the size of ISize (iSize) specified for szDeviceList is checked whether it is in the status specified for
IData (lplData or iData).
Specify the check time for IMonitorCycle (iMonitorCycle).
When the status is established, the OnDeviceStatus function of the user program is executed.
Example:
11 FUNCTIONS
• The maximum number of device points for lSize (iSize) is 20.
• Specify a value within the range from 1 second to 1 hour (set between 1 and 3600 in seconds) for IMonitorCycle
(iMonitorCycle).
An error occurs when any other value outside the above range is specified.
• The registered device value list is stored in lData (lplData or iData).
• Device status monitoring may not be performed at the specified status monitoring time intervals depending
on the conditions: personal computer performance, currently executed application load, time required for
communication with the programmable controller, or the like.
Simultaneous use of any other control functions would also be the cause of disabling device status
monitoring at the specified status monitoring time ntervals.
• An error occurs when the EntryDeviceStatus function is executed during a status monitoring.
When changing any status monitor condition, execute the FreeDeviceStatus function and then execute the
EntryDeviceStatus function.
• When the status of multiple devices changes at the same time, the OnDeviceStatus event is executed every
time the status changes.
(Example: When M0 is monitored)
Application MX Component Programmable controller
M0, M1 read request

Content of M0, M1
M0, M1 read request

Content of M0, M1 M0 ON !
Event notification
OnDeviceStatus (M0)
Event execution M0 OFF
M0, M1 read request
Content of M0, M1 M0, M1 ON !
Event notification
OnDeviceStatus (M0)
Event execution
Event notification
OnDeviceStatus (M1)
Event execution
• This function is a function to check the status establishment under the constant execution of random device
read by the control.
This function is not a function for a programmable controller CPU to notify the device status establishment
to MX Component.
Therefore, the control may not be able to check the device status establishment of programmable controller
CPU depending on the specified status monitoring time interval.
11 FUNCTIONS
Considerations for checking word device status
When checking the word device status for negative values of -1 to -32768 (FFFFH to 8000H), set the monitor device value of
the EntryDeviceStatus function to any of 65535 to 32768 (0000FFFFH to 00008000H) where '0' is stored in the upper 2-byte.
Example: When checking the D0 status for "-10"
Set the value "65526 (0000FFF6H)" where '0' is stored in the upper 2-byte of "-10 (FFFFFFF6H)" for the monitor device value.
While the type of word devices of the programmable controller CPU is WORD type, the type of monitor device value of the
EntryDeviceStatus function is LONG type.
Therefore, when current values of programmable controller CPU are compared with monitor device values of the
11
EntryDeviceStatus function, the values do not match and the above setting is required. (When bit devices or double word
devices are used, this consideration does not apply.)
For the programming examples regarding this consideration, refer to the following:
Page 642 Programing Examples for Monitoring Word Device Status

11 FUNCTIONS

D0
M16 to M31*1 M0 to M15*1
points)
For CN200 and later devices of FXCPU, 2 words are read for each point when reading devices randomly.



LL of FD0
D1

EG0.

EG0
(E0001) (E0000)
D1


H of LTN0 L of LTN0
H of LTN1 L of LTN1
H of LTN2 L of LTN2
11 FUNCTIONS
FreeDeviceStatus (Deregistering devices for status monitoring)
Applicable controls
Feature
To deregister devices registered by using the EntryDeviceStatus function to monitor their status. 11
Format
■ VBA
lRet = object.FreeDeviceStatus()
■ Visual C++
iRet = object. FreeDeviceStatus()

IRet = object.FreeDeviceStatus()
■ Visual C#
Returned value
Description
The devices that are set using the EntryDeviceStatus function to monitor their status are deregistered.
Not applicable to inverter communication/robot controller communication.
11 FUNCTIONS
OnDeviceStatus (Event notification)
Applicable controls
Feature
To execute the event notification when the device condition registered using the EntryDeviceStatus function is satisfied.

■ VBA
• Adding an event handler
Private WithEvents object As objectLib.object
• Event handler
Private Sub object_OnDeviceStatus(szDevice, lData, lReturnCode)
String szDevice Name of device whose condition is satisfied Input
Long lData Name of device whose condition is satisfied Input
Long lReturnCode Returned value of condition check processing Input

AddHandler object.OnDeviceStatus, AddressOf object_OnDeviceStatus
• Event handler
Private Sub object_OnDeviceStatus(szDevice, iData, iReturnCode)
Integer iData Name of device whose condition is satisfied Input
Integer iReturnCode Returned value of condition check processing Input
• Removing an event handler

RemoveHandler object.OnDeviceStatus, AddressOf object_OnDeviceStatus
■ Visual C#
object.OnDeviceStatus += new objectLib._IobjectEvents_OnDeviceStatusEventHandler(object_OnDeviceStatus);
• Event handler
private void object_OnDeviceStatus(szDevice, iData, iReturnCode)
int iData Name of device whose condition is satisfied Input
int iReturnCode Returned value of condition check processing Input

object.OnDeviceStatus -= new objectLib._IobjectEvents_OnDeviceStatusEventHandler(object_OnDeviceStatus);
Format (when pasting a control to a form)

■ VBA
Private Sub object.OnDeviceStatus(szDevice, lData, lReturnCode)
Long lData Value of device whose condition is satisfied Input
11 FUNCTIONS
■ Visual C++
Add "OnDeviceStatus" event from "Properties" of a control pasted to a form  [Control Events] tab.
OnDeviceStatus event name: object_OnDeviceStatus
• Event handler
void object.OnDeviceStatus(szDevice, lData, lReturnCode)
LPCTSTR szDevice Name of device whose condition is satisfied Input
Long lData Value of device whose condition is satisfied Input
11
Private Sub object_OnDeviceStatus(ByVal sender As System.Object,
ByVal e As objectLib. _objectIEvents_OnDeviceStatusEvent)
sender Event occurrence source Output
e Event data Output
The members of e are as follows:
e.szDevice Name of device whose condition is satisfied
e.lReturnCode Value of device whose condition is satisfied
e.lData Returned value of condition check processing
■ Visual C#
private void object_OnDeviceStatus
(object sender,object._IActUtlTypeEvents_OnDeviceStatusEvent e)
sender Event occurrence source Output
e Event data Output
e->szDevice Name of device whose condition is satisfied
e->lReturnCode Returned value of condition check processing
e->lData Value of device whose condition is satisfied
Returned value
None
Description
• The event is notified to the application when the device condition registered using the EntryDeviceStatus function is
satisfied.
Programming this function in the user program allows the application to receive the event when the registered device
condition is satisfied.
• Device values registered using the EntryDeviceStatus function are input to lData.
Example: When the word device is monitored for the value of "-1"
Set 65535 (0000FFFFH) as a registered device value using the EntryDeviceStatus function.
When the value of the target word device of the programmable controller CPU becomes
"-1" (FFFFH), the OnDeviceStatus function is executed and (0000FFFFH) is input to lData.
11 FUNCTIONS
• When any of the following settings is set in the user program, the event of the OnDeviceStatus function
does not occur even if the condition of the device registered to the EntryDeviceStatus function is satisfied.
Note that when the event occurrence becomes in wait status, the control function is not returned to the
control and device management processing stops until the following setting is terminated:
(1) For user programs created by using Visual Basic .NET or VBA (Excel):
The message box is being displayed in the user program.
The InputBox/OutputBox is being displayed in the user program.
(2) For user programs created by using Visual Basic .NET, Visual C++, Visual C#, or VBA (Excel, Access):
The Sleep processing, WaitForSingleObject function, or similar standby function is being used in the user
program.
• For installing "References," refer to the sample programs.
• The method to paste a control to a form cannot be used for 64-bit.
11 FUNCTIONS
ReadDeviceBlock2 (Reading devices in batch)
Applicable controls
Feature 11
To read devices in 2-byte data unit in batch.
Format
■ VBA
lRet = object.ReadDeviceBlock2(szDevice, lSize, iData(0))
■ Visual C++
lRet = object.ReadDeviceBlock2(szDevice, lSize, *lpsData)
Short *lpsData Read device value Output

IRet = object.ReadDeviceBlock2(szDevice, ISize, sData(0))
Integer ISize Number of read points Input
short sData(n) Read device value Output
■ Visual C#
iRet = object.ReadDeviceBlock2(szDevice, iSize, out sData[0])
short[n] sData Read device value Output

■ Visual C++
hResult = object.ReadDeviceBlock2( szDevice, lSize, *lpsData, *lplRetCode )
SHORT *lpsData Read device value Output
Returned value
Description
• The device values of lSize (iSize) are read in batch starting from the device specified for szDevice as SHORT type data.
• The read device values are stored in iData (lplData or sData).
• For iData (lpsData or sData), reserve arrays for more than the amount specified for ISize (iSize).
11 FUNCTIONS
• The maximum number of read points for lSize should be the value which satisfies the following condition:
• For iData (lpsData or sData), reserve a memory area for the number of points specified for lSize (iSize).
timer coil (LSTC) cannot be read. Use the ReadDeviceRandom2 or GetDevice2 function.


Example: Read 3 points (3 words) of data in 16-point unit from the devices starting from M0.
2-byte
M0 to M15*1
M16 to M31*1
M32 to M47*1

2-byte
D0
D1
D2

Example: Read 6 points of data from the devices starting from CN200.
For CN200 and later devices of FXCPU, 2 words are read for each 2 points. Reading only 1 point of data will result in an error.
2-byte
L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

2-byte
LL of FD0
LH of FD0
HL of FD0
HH of FD0
LL of FD1
LH of FD1

Example: Read 4 points of data from the devices starting from EG0.
11 FUNCTIONS
2-byte
EG0
(E0001) (E0000)
EG1
(E0003) (E0002)
EG2
(E0005) (E0004)
EG3
(E0007) (E0006)
11
Example: Read 3 points of data from the devices starting from LTN0.
2-byte
L of LTN0
L of LTN1
L of LTN2
11 FUNCTIONS
WriteDeviceBlock2 (Writing devices in batch)
Applicable controls
Feature
To write devices in 2-byte data unit in batch.
Format
■ VBA
lRet = object.WriteDeviceBlock2(szDevice, lSize, iData(0))
■ Visual C++
lRet = object.WriteDeviceBlock2(szDevice, lSize, *lpsData)
Short *lpsData Device value to be written Input

IRet = object.WriteDeviceBlock2(szDevice, ISize, sData(0))
Integer ISize Number of write points Input
short sData(n) Device value to be written Input
■ Visual C#
iRet = object.WriteDeviceBlock2(szDevice, iSize, ref sData[0])
short[n] sData Device value to be written Input

■ Visual C++
hResult = object.WriteDeviceBlock2(szDevice, lSize, *lpsData, *lplRetCode )
SHORT *lpsData Device value to be written Input
Returned value
Description
• The device values of lSize (iSize) are written in batch starting from the device specified for szDevice.
• The device values to be written are stored in iData (lpsData or sData).
11 FUNCTIONS
• The maximum number of write points for lSize (iSize) should be the value which satisfies the following
condition:
timer coil (LSTC) cannot be written. Use the WriteDeviceRandom2 or SetDevice2 function. 11


Example: Write 3 points (3 words) of data in 16-point unit to the devices starting from M0.
2-byte
M0 to M15*1
M16 to M31*1
M32 to M47*1

2-byte
D0
D1
D2

Example: Write 6 points of data to the devices starting from CN200.
For CN200 and later devices of FXCPU, 2 words are written for each 2 points. Writing only 1 point of data will result in an
error.
2-byte
L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

Example: Write 6 points of data to the devices starting from FD0.
2-byte
LL of FD0
LH of FD0
HL of FD0
HH of FD0
LL of FD1
LH of FD1
11 FUNCTIONS
Example: Write 4 points of data to the devices starting from EG0.
2-byte
EG0
(E0001) (E0000)
EG1
(E0003) (E0002)
EG2
(E0005) (E0004)
EG3
(E0007) (E0006)

Example: Write 3 points of data to the devices starting from LTN0.
2-byte
L of LTN0
L of LTN1
L of LTN2
11 FUNCTIONS
ReadDeviceRandom2 (Reading devices randomly)
Applicable controls
Feature 11
To read devices in 2-byte data unit randomly.
Format
■ VBA
lRet = object.ReadDeviceRandom2(szDeviceList, lSize, iData(0))
■ Visual C++
lRet = object.ReadDeviceRandom2(szDeviceList, lSize, *lpsData)
Short *lpsData Read device value Output

IRet = object.ReadDeviceRandom2(szDeviceList, ISize, sData(0))
Integer ISize Number of read points Input
short sData(n) Read device value Output
■ Visual C#
iRet = object.ReadDeviceRandom2(szDevice, iSize, out sData[0])

■ Visual C++
hResult = object.ReadDeviceRandom2( szDeviceList, lSize, *lpsData, *lplRetCode )
SHORT *lpsData Read device value Output
Returned value
11 FUNCTIONS
Description
• Data of a device group specified for szDeviceList (szDevice) is read for the size of ISize (iSize).
• The read device values are stored in iData (lplData or sData).
Example:
• The maximum number of read points for lSize (iSize) is 0x7FFFFFFF.

• When specifying a double word device, the ReadDeviceRandom2 function stores only the data of lower 1
word (2-byte). (An error does not occur.)
Use the ReadDeviceRandom or GetDevice function to read data from double word devices.


2-byte
M0*1
D0
M0 to M15*2
*1 The target device from which data is read is only one point of "M0," and '0' or '1' is stored as the device value.
Data is not read from the upper 2-byte of M16 to M31.
points)
2-byte
D0
L of CN200*1
D1
*1 For CN200 and later devices of FXCPU, the L (lower 2-byte) of specified devices is read for each point when the ReadDeviceRandom2
function is executed.
The H (upper 2-byte) of specified devices is not read.
11 FUNCTIONS
2-byte
D0
LL of FD0
D1
■ When devices including EG are specified (total number of points: 3 points) 11

EG0.
2-byte
D0
EG0
(E0001) (E0000)
D1

2-byte
L of LTN0
L of LTN1
L of LTN2
11 FUNCTIONS
WriteDeviceRandom2 (Writing devices randomly)
Applicable controls
Feature
To write devices in 2-byte data unit randomly.
Format
■ VBA
lRet = object.WriteDeviceRandom2(szDeviceList, lSize,iData(0))
■ Visual C++
lRet = object.WriteDeviceRandom2(szDeviceList, lSize,*lpsData)
Short *lpsData Device value to be written Input

IRet = object.WriteDeviceRandom2(szDeviceList, ISize, sData(0))
Integer ISize Number of write points Input
short sData(n) Device value to be written Input
■ Visual C#
iRet = object.WriteDeviceRandom2(szDevice, iSize, ref sData[0])

■ Visual C++
hResult = object.WriteDeviceRandom2( szDeviceList, lSize, *lpsData, *lplRetCode )
SHORT *lpsData Device value to be written Input
Returned value
11 FUNCTIONS
Description
• Data of a device group specified for szDeviceList (szDevice) is written for the size of ISize (iSize).
• The device values to be written are stored in iData (lpsData or sData).
Example:
When using Visual C#: D0\nD1\nD2 11
• The maximum number of write points for lSize (iSize) is 0x7FFFFFFF.

• When specifying a double word device, the WriteDeviceRandom2 function writes to the data area of lower 1
word (2-byte), and '0' is written to the data area of upper 1 word (2-byte).
When writing a double word device, use the WriteDeviceRandom function or the SetDevice function.


2-byte
M0*1
D0
M0 to M15*2
*1 The target device to which data is written is only one point of "M0," and the least significant bit of the set 2-byte data is written as the
device value.
'0' is written to the upper 2-byte of M16 to M31.
points)
2-byte
D0
L of CN200*1
D1
*1 For CN200 or later device of FXCPU, data is written to the L (lower 2-byte) of specified devices for each point when the
WriteDeviceRandom2 function is executed.
'0' is written to the H (upper 2-byte) of specified devices.
11 FUNCTIONS
2-byte
D0
LL of FD0
D1

EG0.
2-byte
D0
EG0
(E0001) (E0000)
D1

2-byte
L of LTN0
L of LTN1
L of LTN2
11 FUNCTIONS
SetDevice2 (Setting device data)
Applicable controls
Feature 11
To set one point of device in 2-byte data unit.
Format
■ VBA
lRet = object.SetDevice2(szDevice, iData)
Integer iData Set data Input
■ Visual C++
lRet = object.SetDevice2(szDevice, sData)
Short sData Set data Input

IRet = object.SetDevice2(szDevice, sData)
Short sData Set data Input
■ Visual C#
iRet = object.SetDevice2(szDevice, sData)
short sData Set data Input

■ Visual C++
hResult = object.SetDevice2( szDevice, sData, *lplRetCode )
LONG lData Set data Input
Returned value
Description
• One point of device specified for szDevice is specified using iData (sData).
• When specifying bit devices, the least significant bit of the iData value (sData value) is valid.
11 FUNCTIONS
• When specifying a double word device, the SetDevice2data function writes to the data area of lower 1 word
(2-byte), and '0' is written to the data area of upper 1 word (2-byte).
Use the WriteDeviceRandom or SetDevice function to write a double word device.


Example: M0
2-byte
M0*1
device value.

Example: D0
2-byte
D0

Example: LTN0
2-byte
L of LTN0

Example: K8M0
2-byte
M0 to M15*1
'0' is written to the upper 2-byte of M16 to M31.

Example: CN200
2-byte
L of CN200*1
*1 For CN200 and later devices of FXCPU, data is written to the L (lower 2-byte) of specified devices for each point when the SetDevice2
function is executed.

2-byte
EG0
(E0001) (E0000)
11 FUNCTIONS
GetDevice2 (Acquiring device data)
Applicable controls
Feature 11
To acquire one point of device in 2-byte data unit.
Format
■ VBA
lRet = object.GetDevice2(szDevice, iData)
Integer iData Acquired data Output
■ Visual C++
lRet = object.GetDevice2(szDevice, *lpsData)
Short *lpsData Acquired data Output

IRet = object.GetDevice2(szDevice, sData)
short sData Acquired data Output
■ Visual C#
iRet = object.GetDevice2(szDevice, out sData)
short sData Acquired data Output

■ Visual C++
hResult = object.GetDevice2( szDevice, *lpsData, *lplRetCode )
SHORT *lpsData Acquired data Output
Returned value
Description
One point of device data specified for szDevice is stored in iData (lpsData or sData).
11 FUNCTIONS
• When a double word device is specified, only the data of lower 1 word (2-byte) is stored using the
GetDevice2 function. (An error does not occur.)
• When reading data from a double word device, use the ReadDeviceRandom or GetDevice function.


Example: M0
2-byte
M0*1

Example: D0
2-byte
D0

Example: LTN0
2-byte
L of LTN0

Example: K8M0
2-byte
M0 to M15*1
Data is not read from the upper 2-byte of M16 to M31.

Example: CN200
2-byte
L of CN200*1
*1 For CN200 and later devices of FXCPU, the L (lower 2-byte) of specified devices is read for each point when the GetDevice2 function is
executed.
The H (upper 2-byte) of specified devices is not read.

2-byte
EG0
(E0001) (E0000)
11 FUNCTIONS
GetErrorMessage(Acquiring error description and corrective
action)
Applicable controls
• 32-bit: ActSupportMsg
• 64-bit: ActSupportMsg64
11
Feature
To acquire the error description and its corrective action corresponding to the error code.
Format
■ VBA
lRet = object.GetErrorMessage(lErrorCode, szErrorMessage)
Long lErrorCode Error code Input
String szErrorMessage Error message Output
■ Visual C++
lRet = object.GetErrorMessage(lErrorCode, *lpszErrorMessage)
Long lErrorCode Error code Input
BSTR *lpszErrorMessage Error message Output

IRet = object.GetErrorMessage(IErrorCode, szErrorMessage)
Integer IErrorCode Error code Input
■ Visual C#
iRet = object.GetErrorMessage(iErrorCode, out szErrorMessage)
int iErrorCode Error code Input

■ Visual C++
hResult = object.GetErrorMessage( lErrorCode, *lpszErrorMessage, *lplRetCode )
LONG lErrorCode Error code Input
BSTR *lpszErrorMessage Error message Output
Returned value
Description
• The error description and its corrective action of the error code specified for lErrorCode (iErrorCode) are read.
• The read error description and corrective action are stored in szErrorMessage (lpszErrorMessage or lpvarErrorMessage).
Not applicable to inverter communication.
11 FUNCTIONS
11.4 Details of Functions (For Act Control (Logging File
Transfer))
Applicable controls
• 32-bit: ActProgDataLogging, ActUtlDataLogging
• 64-bit: ActProgDataLogging64, ActUtlDataLogging64
Feature
Format
■ Visual C++

■ Visual C#

■ Visual C++
hResult = object.Open( *lplReturnCode )
LONG *lplReturnCode Returned value of communication function Output
Returned value
Description
• Even when a CPU type which is different from the one used for the communication is set to the ActCpuType
property, the Open function may be completed normally.
11 FUNCTIONS
494 11.4 Details of Functions (For Act Control (Logging File Transfer))
Applicable controls
Feature 11
Format
■ Visual C++

■ Visual C#

■ Visual C++
hResult = object.Close( *lplReturnCode )
Returned value
Description
• Call this function when an error occurred after calling the Open function or when exit the program.
11 FUNCTIONS
11.4 Details of Functions (For Act Control (Logging File Transfer)) 495
ReadFirstFile (Searching for a file/directory)
Applicable controls
Feature
To search a file or directly in the specified directory.
Format
■ Visual C++
Ret = object.ReadFirstFile(srcDir, *srcFilename, *srcType)
Long Ret Returned value Output
CString srcDir Directory name Input
BSTR *srcFileName File name or directory name Output
Long *srcType Type Output

Ret = object.ReadFirstFile(srcDir, srcFilename, srcType)
Integer Ret Returned value Output
String srcDir Directory name Input
String srcFileName File name or directory name Output
Integer srcType Type Output
■ Visual C#
Ret = object.ReadFirstFile(srcDir, out srcFilename, out srcType)
int Ret Returned value Output
String srcDir Directory name Input
int srcType Type Output

■ Visual C++
hResult = object.ReadFirstFile(srcDir, *srcFilename, *srcType, *lplReturnCode)
BSTR srcDir Directory name Input
LONG *srcType Type Output
Returned value
11 FUNCTIONS
Description
Search a file or directly in the specified directory.
• A read file name or directory name is stored in srcFileName.
• A value that identifies if the name set for srcFileName indicates a directory or file is stored in srcType.
For a directory, '1' is stored in the 4th bit counted from the lowest-order position.
As for a file, '0' is stored.
Example: When srcType is 24 (0x18), it indicates that the target is a directory.
Upper 3 byte Lower 1 byte

11
0 0 0 0 1 1 0 0 0
Example: When srcType is 16 (0x10), it indicates that the target is a file.
0 0 0 0 1 0 0 0 0
Do not use the bits which are not described in the figure above.
• Files or directories under a sub directory are not searched.
• The control does not return until the processing is completed.

• If two or more controls are called at the same time, the search result will be overwritten.
To search multiple directories, generate controls for each directory.
• This function is available while logging is stopped.
• For srcDir, specify the length of a character string within 188 bytes.
• The search result is displayed randomly.
11 FUNCTIONS
ReadNextFile (Searching for a file/directory)
Applicable controls
Feature
To continue searching other files from the last search result of ReadFirstFile.
Format
■ Visual C++
Ret = object.ReadNextFile(*srcFilename, *srcType)
Long *srcType Type Output

Ret = object.ReadNextFile(srcFilename, srcType)
Integer srcType Type Output
■ Visual C#
Ret = object.ReadNextFile(out srcFilename, out srcType)
int srcType Type Output

■ Visual C++
hResult = object.ReadNextFile(*srcFilename, *srcType, *lplReturnCode)
LONG *srcType Type Output
Returned value
11 FUNCTIONS
Description
After searching for a file or directory using ReadFirstFile, search for the next file or directory in the specified directory.
• A read file name or directory name is stored in srcFileName.
• A value that identifies if the name set for srcFileName indicates a directory or file is stored in srcType.
For a directory, '1' is stored in the 4th bit counted from the lowest-order position.
As for a file, '0' is stored.
Do not use the bits which are not described in the figure above.
Example: When srcType is 24 (0x18), it indicates that the target is a directory. 11

0 0 0 0 1 1 0 0 0
Example: When srcType is 16 (0x10), it indicates that the target is a file.
0 0 0 0 1 0 0 0 0

• The search result is displayed randomly.
11 FUNCTIONS
ReadClose (Ending the search)
Applicable controls
Feature
To end the search.
Format
■ Visual C++
Ret = object.ReadClose()

■ Visual C#

■ Visual C++
hResult = object.ReadClose(*lplReturnCode)
Returned value
Description
End the search.
• The result for searching for a directory or file name is deleted.

11 FUNCTIONS
GetFile (Transferring logging files)
Applicable controls
Feature 11
To transfer a logging file.
Format
■ Visual C++
Ret = object.GetFile(srcFileName , dstFileName)
CString srcFileName Transfer source file name Input
CString dstFileName Transfer destination file name Input

String srcFileName Transfer source file name Input
String dstFileName Transfer destination file name Input
■ Visual C#
String srcFileName Transfer source file name Input
String dstFileName Transfer destination file name Input

■ Visual C++
hResult = object.GetFile(srcFileName , dstFileName, *lplReturnCode)
BSTR srcFileName Transfer source file name Input
BSTR dstFileName Transfer destination file name Input
Returned value
Description
Transfer a logging file.
• The file specified for srcFileName is transferred to the file specified for dstFileName.

• Specify a character string for srcFileName within 318 bytes.
• Specify a character string for dstFileName within 259 bytes.
11 FUNCTIONS
11.5 Details of Functions (For .Net Control)
Applicable controls
• 32-bit: DotUtlType
• 64-bit: DotUtlType64
Feature
Format
■ Visual C#
Returned value
Description
• Even when a CPU type which is different from the CPU used for the communication is set to the
ActCpuType property, the Open function may be completed normally.
In such a case, the connection range, usable method, or device range may be narrowed.
11 FUNCTIONS
502 11.5 Details of Functions (For .Net Control)
Applicable controls
Feature 11
Format
■ Visual C#
Returned value
Description
11 FUNCTIONS
11.5 Details of Functions (For .Net Control) 503
ReadDeviceBlock (Reading devices in batch)
Applicable controls
Feature
To read devices in batch.
Format
IRet = object.ReadDeviceBlock(szLabel, iSize, iData)
String szLabel Label name Input
■ Visual C#
iRet = object.ReadDeviceBlock(ref szLabel, iSize, ref iData)
Int iRet Returned value Output
Returned value
Description
• Data of devices specified for iSize (number of read points) is read in batch starting from the device specified for szLabel
(label name).
• The read device values are stored in iData.
• For iData, reserve arrays for more than the amount specified for iSize.
11 FUNCTIONS
• The maximum number of read points is 0x7FFFFFFF, which satisfies the following condition:
• When specifying bit type array labels, 0 or a multiple of 16 can be specified as a device number.
• For the number of read points, specify the number of words which applies to the data type specified for the
label name.
For the read device values, reserve a memory area for the number of points specified for the number of
read points.
If the memory area is not reserved, a critical error (an application error or the like) may occur. 11
• When a device which corresponds to the label name does not exist, an error occurs and data cannot be
read.
When any one of devices which correspond to multiple label names does not exist, an error occurs and data
cannot be read.
• Digit specified bit device and index setting cannot be used.
timer coil (LSTC) cannot be read. Use the ReadDeviceRandom or GetDevice function.
• When using system label Ver.2, the data type defined in the Label Utility of MX Component and the data
type managed by MELSOFT Navigator is required to match.
If the data type does not match, the read data length may wrong, or when multiple labels are specified, the
correspondence of the array of the read device value and label name may not match.
How to specify labels

The following describes how to specify labels.
■ Data type
The following data type can be specified for label name.
Type class Label data type Label name format Device data type
Array Label name Integer/int
Array member Bit*2, (32-bit value)
Word, Double Word, Float (Single Precision), Float (Double Label name [number of
Precision), String*1, String (Unicode)*1, Time, Timer*2, Long timer*2, elements]
Counter*2, Long counter*2, Retentive Timer*2, Long retentive timer*2 Label name [n1] [n2] [n3]
*1 Can be specified up to 32 characters + NULL.

*2 Cannot be used for system label Ver.2.
■ Number of read points

For the number of read points, specify the following values according to the label data type.
Label (array) data type Number of Number of read points to be
applicable words specified
Bit 1 Number of label array elements  16
(rounded up)
Word 1 Number of label array elements
Double Word, Float (Single Precision) 2*1 Number of label array elements  2*1
Float (Double Precision) 4 Number of label array elements  4
String 17 Number of label array elements  17
String (Unicode) 33 Number of label array elements  33
Time 2*1 Number of label array elements  2*1
Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer 1 Number of label array elements
*1 When specifying a double word device for a label, the number of devices (elements) is 1.
11 FUNCTIONS
The read device values are stored as follows:

Example: Read 3 points (3 words = 48 bits) of data from the devices starting from M0.
 Label setting (Data type: Bit, Number of array elements: 48)
szLabel Label name Data type Device
[0] to [2] LABEL Bit (0..47) M0 to M47
 Number of read points: 3

 Read device values
Upper 2-byte Lower 2-byte Applicable label
Not used ('0' is stored.) M0 to M15*1 LABEL[0] to LABEL[15]
*1
M16 to M31 LABEL[16] to LABEL[31]
M32 to M47*1 LABEL[30] to LABEL[47]

Example: Read 3 points (3 words) of data from the devices starting from D0.
 Label setting (Data type: Word, Number of array elements: 3)
[0] to [2] LABEL Word (0..2) D0 to D2

Not used ('0' is stored.) D0 LABEL[0]
D1 LABEL[1]
D2 LABEL[2]
■ When specifying double word devices (CN200 and later devices of FXCPU)
Example: Read 6 points (6 words = 3 double words) of data from the devices starting from CN200.
For CN200 and later devices of FXCPU, 2 points of data are read from each 1 point of device (upper (H) and lower (L) data).
Reading only 1 point of data will result in an error.
 Label setting
[0] to [5] LABEL Double Word (0..2) CN200 to CN202

Not used ('0' is stored.) L of CN200 LABEL[0]
H of CN200
L of CN201 LABEL[1]
H of CN201
L of CN202 LABEL[2]
H of CN202
11 FUNCTIONS
Example: Read 8 points (8 words) of data from the devices starting from FD0.
 Label setting (Data type: Double Word, Number of array elements: 2)
[0] to [7] LABEL Double Word (0..1) FD0, FD1

Upper 2-byte
Not used ('0' is stored.)
Lower 2-byte
LL of FD0
Applicable label
LABEL[0]
11
LH of FD0
HL of FD0
HH of FD0
LL of FD1 LABEL[1]
LH of FD1
HL of FD1
HH of FD1
■ When specifying word devices for double word array type labels
Example: Read 6 points (6 words = 3 double words) of data from the devices starting from D100.
[0] to [5] LABEL Double Word (0..2) D100 to D105

D101
D102 LABEL[1]
D103
D104 LABEL[2]
D105
■ When specifying double word devices to be acquired for 1 point in Double Word type
Example: Read 3 points (3 words) of data from the devices starting from LZ0.
[0] to [2] LABEL Double Word (0..2) LZ0 to LZ2

H of LZ0 L of LZ0 LABEL[0]
11 FUNCTIONS
WriteDeviceBlock (Writing devices in batch)
Applicable controls
Feature
To write devices in batch.
Format
IRet = object.WriteDeviceBlock(szLabel, iSize, iData)
■ Visual C#
iRet = object.WriteDeviceBlock(ref szLabel, iSize, iData)
Returned value
Description
• Data of devices specified for iSize (number of write points) is written in batch starting from the device specified for szLabel
(label name).
• The device values to be written are stored in iData.
11 FUNCTIONS
• The maximum number of write points should be the value which satisfies the following condition:
• For the number of write points, specify the number of words which applies to the data type specified for the
label name.
For the device values to be written, reserve a memory area for the number of points specified for the
number of write points.
written.
cannot be written.
timer coil (LSTC) cannot be written. Use the WriteDeviceRandom or SetDevice function.

■ Data type
Type class Label data type Label name format Device data
type
Array Label name Integer/int
Array member Bit*2, Word, Double Word, Float (Single Precision), Float (Double Precision), (32-bit value)
Label name [number of
String*1, String (Unicode)*1, Time, Timer*2, Long timer*2, Counter*2, Long counter*2, elements]
Retentive Timer*2, Long retentive timer*2 Label name [n1] [n2]
[n3]

■ Number of write points

For the number of write points, specify the following values according to the label data type.
Label (array) data type Number of Number of write points to be
(rounded up)
11 FUNCTIONS
Specify the device values to be written as follows:

Example: Write 3 points (3 words = 48 bits) of data to the devices starting from M0.
[0] to [2] LABEL Bit (0..47) M0 to M47
 Number of write points: 3

 Device values to be written
Not used ('0' is stored.) M0 to M15*1 LABEL[0] to LABEL[15]
*1

Example: Write 3 points (3 words) of data to the devices starting from D0.

D1 LABEL[1]
D2 LABEL[2]
■ When specifying double word devices (CN200 and later devices of FXCPU)
Example: Write 6 points (6 words = 3 double words) of data to the devices starting from CN200.
For CN200 and later devices of FXCPU, 2 points of data are written to each 1 point of device (upper (H) and lower (L) data).
Writing only 1 point of data will result in an error.

Not used ('0' is stored.) L of CN200 LABEL[0]
H of CN200
L of CN201 LABEL[1]
H of CN201
L of CN202 LABEL[2]
H of CN202
11 FUNCTIONS
Example: Write 8 points (8 words) of data to the devices starting from FD0.

Upper 2-byte
Lower 2-byte
LL of FD0
Applicable label
LABEL[0]
11
LH of FD0
HL of FD0
HH of FD0
LL of FD1 LABEL[1]
LH of FD1
HL of FD1
HH of FD1
Example: Write 6 points (6 words = 3 double words) of data to the devices starting from D100.

D101
D102 LABEL[1]
D103
D104 LABEL[2]
D105
Example: Write 3 points (3 words) of data to the devices starting from LZ0.

11 FUNCTIONS
ReadDeviceRandom (Reading devices randomly)
Applicable controls
Feature
To read devices randomly.
Format
IRet = object.ReadDeviceRandom(szLabel, iSize, iData)
IRet = object.ReadDeviceRandom(szLabelList, iSize, iData)

String szLabelList(n) Label list Input
■ Visual C#
iRet = object.ReadDeviceRandom(ref szLabel, iSize, ref iData)
iRet = object.ReadDeviceRandom(ref szLabelList, iSize, ref iData)

System.String[n] szLabelList Label list Input
Returned value
Description
• Data of a device group specified for the label name szLabel (szLabelList) is read for the size of iSize.
• The read device values are stored in iData.
11 FUNCTIONS
• The maximum number of read points is 0x7FFFFFFF.
label name.
read points.
read. 11
cannot be read.
• Up to five levels of a structure can be defined. Note that only one-level structure can be used for a static
system label.

■ Data type
Basic type Bit, Word, Double Word, Float (Single Precision), Float Label name Integer/int
(Double Precision), String*1, String (Unicode)*1, Time, (32-bit value)
Timer*2, Long timer*2, Counter*2, Long counter*2, Retentive
Timer*2, Long retentive timer*2
Array Label name
Array member (The label data type can be specified in the same manner as Label name [number of
the basic type.) elements]
Label name [n1] [n2] [n3]
Structure Label name
Structure member (The label data type can be specified in the same manner as Label name.Member name
the basic type.)
Structured array Label name [number of
elements]
Structured array member (The label data type can be specified in the same manner as Label name [number of
the basic type.) elements].Member name
Label name [n1] [n2]
[n3].Element

11 FUNCTIONS
For the number of read points, specify the sum of the following values correspond to the elements according to the label data
type.
Label data type Number of Number of read points to be
Bit 1 Number of label elements  16 (rounded
up)
Word 1 Number of label elements
Double Word, Float (Single Precision) 2*1 Number of label elements  2*1
Float (Double Precision) 4 Number of label elements  4
String 17 Number of label elements  17
Time 2*1 Number of label elements  2*1
Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer 1 Number of label elements

■ When specifying bit devices, word devices, and double word devices acquired for one point
Example: Read a total of 6 points of data from M0, D0, D4, CN200, and D10.
 Label setting
szLabelList Label name Data type Device
[0] LABEL1 Bit M0
[1] LABEL2 Word D0
[2] LABEL3 Word D4
[3], [4] LABEL4 Double Word CN200
[5] LABEL5 Double Word D10

Not used ('0' is stored.) M0 LABEL1
D0 LABEL2
D4 LABEL3
H of CN200 L of CN200 LABEL4
Not used ('0' is stored.) D10 LABEL5
■ When specifying bit devices and word devices (FD devices including 4-word devices)
Example: Read a total of 5 points of data from FD0 and D0.
 Label setting
[0] to [3] LABEL1 Word FD0
[4] LABEL2 Bit D0.1

Not used ('0' is stored.) LL of FD0 LABEL1
LH of FD0
HL of FD0
HH of FD0
D0.1 LABEL2
11 FUNCTIONS
■ When specifying character strings
 Label setting
[0] to [15] LABEL Word D0 to D16

Upper 2-byte
Lower 2-byte
D0
Applicable label
LABEL[0]
11
D1 LABEL[1]
 
 
D16 LABEL[16]
Example: Read 3 points of data from the devices starting from LZ0.

■ When specifying data types equivalent to 2 words or more for labels

Example: Read a total of 6 points of data by specifying labels of Double Word, Float (Single Precision), and Time types.
 Label setting
[0], [1] LABEL1 Double Word D0, D1
[2], [3] LABEL2 Float (Single Precision) D100, D101
[4], [5] LABEL3 Time D200, D201

D1
D100 LABEL2
D101
D200 LABEL3
D201
11 FUNCTIONS
■ When specifying Float (Double Precision) and word devices
Example: Read a total of 5 points of data by specifying labels of Float (Double Precision) and Word types.
 Label setting
[0] to [3] LABEL1 Float (Double Precision) D0 to D3
[4] LABEL2 Word D200

D1
D2
D3
D200 LABEL2
■ When specifying array type labels

Example 1: Read 3 points of data from the bit devices (M0 to M2) by specifying array type labels.
 Label setting
[0] to [2] LABEL Bit M0 to M2

Not used ('0' is stored.) M0 LABEL[0]
M1 LABEL[1]
M2 LABEL[2]
Example 2: Read 3 points of data from the word devices (D0 to D2) by specifying array type labels.
 Label setting

D1 LABEL[1]
D2 LABEL[2]
Example 3: Read 3 points of data from the word devices (CN200 to CN202) by specifying array type labels.
 Label setting
[0] to [2] LABEL Word CN200 to CN202

H of CN200 L of CN200 LABEL[0]
11 FUNCTIONS
Example 4: Read 3 points of data from the word devices (FD0 to FD2) by specifying array type labels.
 Label setting
[0] to [2] LABEL Word FD0 to FD2

Not used ('0' is stored.) LL of FD0*1 LABEL[0]
LL of FD1*1 LABEL[1] 11
LL of FD2*1 LABEL[2]
*1 Only the lower 2-byte is read. Data is not read from the HH, HL, and LH (upper 6-byte) of specified devices.
Example 5: Read 6 points (6 words = 3 double words) of data by specifying array type labels.
 Label setting
[0] to [5] LABEL Double Word D0 to D5

D1
D2 LABEL[1]
D3
D4 LABEL[2]
D5
Example 6: Read 51 points (D0 to D50) of string type data by specifying array type labels.
 Label setting
[0] to [50] LABEL String D0 to D50


D16
D17 LABEL[1]

D33
D34 LABEL[2]

D50
11 FUNCTIONS
■ When specifying structure type labels
Example: Read data by specifying structure type labels.
 Structure setting
Structure name Label name Data type
STRUCT L1 Bit
L2 Double Word
 Label setting
szLabelList Data type Label name Device
[0] LABEL1 STRUCT L1 D0.0
L2 D0
[1] LABEL2 STRUCT L1 M10
L2 CN200

Not used ('0' is stored.) D0.0 LABEL1.L1
D0 LABEL1.L2
D1
M0 LABEL2.L1
H of CN200 L of CN200 LABEL2.L2
H of CN201 L of CN201*1
*1 Data of two devices are read when the device of CN200 and later is specified for the Double Word type label.
■ When specifying labels in combination with structure and array

Example: Read data by specifying structure type array and structure array type labels.
STRUCT1 L1 Bit
L2 Word
STRUCT2 L1 Bit (0..2)
L2 Double Word
 Label setting
[0] LABEL1 STRUCT1(0..1) L1 X0
L2 D0
[1] LABEL2 STRUCT2 L1 M0
L2 D100

Not used ('0' is stored.) X0 LABEL1[0].L1
D0 LABEL1[0].L2
X1 LABEL1[1].L1
D1 LABEL1[1].L2
M0 LABEL2.L1[0]
M1 LABEL2.L1[1]
M2 LABEL2.L1[2]
D100 LABEL2.L2
D101
11 FUNCTIONS
WriteDeviceRandom (Writing devices randomly)
Applicable controls
Feature 11
To write devices randomly.
Format
IRet = object.WriteDeviceRandom(szLabel, iSize, iData)
IRet = object.WriteDeviceRandom(szLabelList, iSize, iData)

■ Visual C#
iRet = object.WriteDeviceRandom(ref szLabel, iSize, ref iData)
iRet = object. WriteDeviceRandom(ref szLabelList, iSize, ref iData)

Returned value
Description
• Data of a device group specified for the label name szLabel (szLabelList) is written for the size of iSize.
• The device values to be written are stored in iData.
11 FUNCTIONS
• The maximum number of write points is 0x7FFFFFFF.
label name.
written.
cannot be written.
system label.

■ Data type
Type class Label data type Label name format
Basic type String*1,
Bit, Word, Double Word, Float (Single Precision), Float (Double Precision), String Label name
(Unicode)*1, Time, Timer*2, Long timer*2, Counter*2, Long counter*2, Retentive Timer*2, Long
retentive timer*2
Array Label name
Array member (The label data type can be specified in the same manner as the basic type.) Label name [number of
elements]
Structure member (The label data type can be specified in the same manner as the basic type.) Label name.Member name
elements]
Structured array member (The label data type can be specified in the same manner as the basic type.) Label name [number of
elements].Member name
[n3].Element

11 FUNCTIONS
For the number of write points, specify the sum of the following values correspond to the elements according to the label data
type.
Label data type Number of Number of write points to be
up)
11

■ When specifying bit devices, word devices, and double word devices acquired for one point
Example: Write 1 point of data to M0, D0, D4, CN200 and D10.
 Label setting
[0] LABEL1 Bit M0
[1] LABEL2 Word D0
[2] LABEL3 Word D4
[3], [4] LABEL4 Double Word CN200, CN201

D0 LABEL2
D4 LABEL3
H of CN200 L of CN200 LABEL4
■ When specifying bit devices and word devices (FD devices including 4-word devices)
Example: Write a total of 5 points of data to FD0 and D0.
 Label setting
[0] to [3] LABEL1 Word FD0
[4] LABEL2 Bit D0.1

Not used ('0' is stored.) LL of FD0 LABEL1
LH of FD0
HL of FD0
HH of FD0
D0.1 LABEL2
11 FUNCTIONS
 Label setting

Not used ('0' is stored.) D0 LABEL
D1


D16
Example: Write 3 points of data to the devices starting from LZ0.


Example: Write data by specifying labels of Double Word, Float (Single Precision), and Time types.
 Label setting
[4], [5] LABEL3 Time D200, D201

D1
D100 LABEL2
D101
D200 LABEL3
D201
11 FUNCTIONS
Example: Write a total of 5 points of data by specifying Float (Double Precision) and a word device.
 Label setting

11
D1
D2
D3
D200 LABEL2

Example 1: Write 3 points of data to the bit devices (M0 to M2) by specifying array type labels.
 Label setting

Not used ('0' is stored.) M0 LABEL[0]
M1 LABEL[1]
M2 LABEL[2]
Example 2: Write 3 points of data to the word devices (D0 to D2) by specifying array type labels.
 Label setting

D1 LABEL[1]
D2 LABEL[2]
Example 3: Write 3 points of data to the word devices (CN200 to CN202) by specifying array type labels.
 Label setting

11 FUNCTIONS
 Label setting

Not used ('0' is stored.) LL of FD0*1 LABEL[0]
*1 Only the lower 2-byte is written.

Example 5: Write 6 points (6 words = 3 double words) of data by specifying array type labels.
 Label setting

D1
D2 LABEL[1]
D3
D4 LABEL[2]
D5
 Label setting


D16
D17 LABEL[1]

D33
D34 LABEL[2]

D50
11 FUNCTIONS
Example: Write data by specifying structure type labels.
STRUCT L1 Bit
L2 Double Word
 Label setting
szLabelList
[0] LABEL1
Data type
STRUCT
Label name
L1
Device
D0.0
11
L2 D0
L2 CN200

Not used ('0' is stored.) D0.0 LABEL1.L1
D0 LABEL1.L2
D1
M0 LABEL2.L1
H of CN200 L of CN200 LABEL2.L2

Example: Write data by specifying structure type array and structure array type labels.
STRUCT1 L1 Bit
L2 Word
L2 Double Word
 Label setting
L2 D0
L2 D100

Not used ('0' is stored.) X0 LABEL1[0].L1
D0 LABEL1[0].L2
X1 LABEL1[1].L1
D1 LABEL1[1].L2
M0 LABEL2.L1[0]
M1 LABEL2.L1[1]
M2 LABEL2.L1[2]
D100 LABEL2.L2
D101
11 FUNCTIONS
SetDevice (Setting device data)
Applicable controls
Feature
To set one point of device.
Format
IRet = object.SetDevice(szLabel, iData)
Integer iData Device value to be written Input
■ Visual C#
iRet = object.SetDevice(ref szLabel, iData)
int iData Device value to be written Input
Returned value
Description
• The values of iData (device values to be written) are written to 1 point of device specified for szLabel (label name).
• When specifying bit devices, the least significant bit of the iData (device values to be written) is valid.
written.
• When specifying a double word device, 2-byte is written in Double Word type.
When specifying other than a double word device for a data type equivalent to 2 words or more, this
function writes to the data area of lower 1 word (2-byte). (The values of upper 2-byte is indefinite.)
Use the WriteDeviceRandom function to write devices equivalent to 2 words or more.
• When using a label memory without specifying a device in system label Ver.2, the data is handled as 2
points of word.
11 FUNCTIONS
■ Data type
Basic type Bit, Word, Double Word*1, Float (Single Precision)*1, Float (Double Precision)*1, String*1, String Label name
(Unicode), Time*1, Timer*2, Long timer*2, Counter*2, Long counter*2, Retentive Timer*2, Long retentive
timer*2
11
*1 Only the lower 2-byte of start device can be written. Use the WriteDeviceRandom function to write devices equivalent to 2 words or
more.


Example: Write data to M0.
 Label setting
[0] LABEL Bit M0

Not used ('0' is stored.) M0 LABEL

Example: Write data to D0.
 Label setting
[0] LABEL Word D0

■ When specifying double word devices (ones to which data of 2 words can be written for 1
point)
Example: Write data to CN200.
For CN200 and later devices of FXCPU, 4-byte is written.
 Label setting
[0] LABEL Double Word CN200

H of CN200 L of CN200 LABEL
11 FUNCTIONS
■ When specifying double word devices (ones to which data of 2 words cannot be written for 1
point)
Example: Write data by specifying D0.
 Label setting
[0] LABELW Double Word D0

Not used. D0*1 LABELW
*1 Data is written in order from the lower 2-byte. For system label Ver.2, an indefinite value is written to the upper 2-byte.

Example: Write data by specifying a string type label.
 Label setting
[0] LABEL String D0

Not used. D0*1 LABEL
*1 Data is written in order from the lower 2-byte. For system label Ver.2, an indefinite value is written to the upper 2-byte.
11 FUNCTIONS
GetDevice (Acquiring device data)
Applicable controls
Feature 11
To acquire one point of device.
Format
IRet = object.GetDevice(szLabel, lData)
Integer iData Read device value Output
■ Visual C#
iRet = object.GetDevice(ref szLabel, ref iData)
int iData Read device value Output
Returned value
Description
• One point of device data specified for szLabel (label name) is stored in iData (read device values).
read.
• For the read device values, reserve 4 bytes of memory area.

■ Data type
Basic type Bit, Word, Double Word*1, Float (Single Precision)*1,Float (Double Precision)*1, String*1,
String Label name
(Unicode)*1, Time*1, Timer*2, Long timer*2, Counter*2, Long counter*2, Retentive Timer*2, Long retentive
timer*2
*1 Only the lower 2-byte of start device can be read.

Use the ReadDeviceRandom function to read 2 words or more of devices.
However, the upper 2-byte is also read in Double Word type when specifying a double word device that can be acquired for 1 point.
11 FUNCTIONS

Example: Read data from M0.
 Label setting
[0] LABEL Bit M0

Not used ('0' is stored.) M0*1 LABEL

Example: Read data from D0.
 Label setting
[0] LABEL Word D0

■ When specifying double word devices (ones from which data of 2 words can be read for 1
point)
Example: Read data from CN200.
 Label setting

H of CN200 L of CN200*1 LABEL
*1 For CN200 and later devices of FXCPU, 4-byte is read.
■ When specifying double word devices (ones from which data of 2 words cannot be read for 1
point)
Example: Read data by specifying D0.
 Label setting

Not used ('0' is stored.) D0*1 LABELW
*1 Data is read in order from the lower 2 bytes.
11 FUNCTIONS
Example: Read data by specifying a string type label.
 Label setting
[0] LABEL String D0

Upper 2-byte
Lower 2-byte
D0*1
Applicable label
LABEL
11
*1 Data is read in order from the lower 2 bytes.
11 FUNCTIONS
ReadBuffer (Reading data from buffer memory)
Applicable controls
Feature
To read data from the buffer memory of special function module.
Format
IRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, sData)
Integer iStartIO Start I/O number of module from which values Input
are read
Integer iReadSize Read size Input
Short sData(n) Values read from buffer memory Output
■ Visual C#
iRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, sData)
int iStartIO Start I/O number of module from which values Input
are read
int iReadSize Read size Input
short[n] sData Values read from buffer memory Output
Returned value
Description
• For the start I/O number of the module specified for iStartIO, specify the value of the actual start I/O number divided by 16.
• Buffer values of buffer memory address specified for iAddress of the special function module of the start I/O number
specified for iStartIO are read for the size of iReadSize.
memory address.
• For sData, reserve arrays for more than the amount specified for iReadSize.

• For iData, reserve a memory area for the number of points specified for iReadSize. If the memory area is
not reserved, a critical error (an application error or the like) may occur.
11 FUNCTIONS
Refer to the following:
Page 448 Applicable communication routes
11
11 FUNCTIONS
WriteBuffer (Writing data to buffer memory)
Applicable controls
Feature
To write data to the buffer memory of special function module.
Format
IRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, sData)
Integer iStartIO Start I/O number of module to which values Input
are written
Integer iWriteSize Write size Input
Short sData(n) Values written from buffer memory Input
■ Visual C#
iRet = object. WriteBuffer (iStartIO, iAddress, iWriteSize, sData)
int iStartIO Start I/O number of module to which values Input
are written
int iWriteSize Write size Input
short[n] sData Values written from buffer memory Input
Returned value
Description
• For the start I/O number of the module specified for iStartIO, specify the value of the actual start I/O number divided by 16.
• Buffer values of buffer memory address specified for iAddress of the special function module of the start I/O number
specified for iStartIO are written for the size of iWriteSize.
memory address.
• For sData, reserve arrays for more than the amount specified for iWriteSize.

• For sData, reserve a memory area for the number of points specified for iReadSize. If the memory area is
not reserved, a critical error (an application error or the like) may occur.
11 FUNCTIONS
11
11 FUNCTIONS
GetClockData (Reading clock data)
Applicable controls
Feature
To read clock data from a programmable controller CPU.
Format
IRet = object.GetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
Short sYear Read year value Output
Short sMonth Read month value Output
Short sDay Read day value Output
Short sDayOfWeek Read day-of-week value Output
Short sHour Read hour value Output
Short sMinute Read minute value Output
Short sSecond Read second value Output
■ Visual C#
hResult = object.GetClockData
(ref sYear, ref sMonth, ref sDay, ref sDayOfWeek,ref sHour, ref sMinute, ref sSecond)
short sYear Read year value Output
short sMonth Read month value Output
short sDay Read day value Output
short sDayOfWeek Read day-of-week value Output
short sHour Read hour value Output
short sMinute Read minute value Output
short sSecond Read second value Output
Returned value
Description
• An error is returned when the correct clock data is not set to the programmable controller CPU.
• The values stored in sYear are: the four digits of year for RCPU and QCPU (Q mode) and the last two digits of year for any
other CPUs.
• The values to be stored in sDayOfWeek are as follows:
Value Day of Week
0 Sunday
1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5 Friday
6 Saturday
11 FUNCTIONS
• For the availability of communication routes, refer to the table in Page 455 GetClockData (Reading
clock data).
Applicable communication routes 11

11 FUNCTIONS
SetClockData (Writing clock data)
Applicable controls
Feature
To write clock data to a programmable controller CPU.
Format
IRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
Short sYear Year value to be written Input
Short sMonth Month value to be written Input
Short sDay Day value to be written Input
Short sDayOfWeek Day-of-week value to be written Input
Short sHour Hour value to be written Input
Short sMinute Minute value to be written Input
Short sSecond Second value to be written Input
■ Visual C#
short sYear Year value to be written Input
short sMonth Month value to be written Input
short sDay Day value to be written Input
short sDayOfWeek Day-of-week value to be written Input
short sHour Hour value to be written Input
short sMinute Minute value to be written Input
short sSecond Second value to be written Input
Returned value
11 FUNCTIONS
Description
• An error is returned when the clock data to be set is not the correct value.
• The applicable values to be specified for sYear are: the four digits of year for RCPU and QCPU (Q mode) and the last two
digits of year for any other CPUs.
An error occurs when four digits are set to a CPU other than RCPU and QCPU (Q mode).
• The values to be specified for sDayOfWeek are as follows:
Value Day of Week 11
0 Sunday
1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5 Friday
6 Saturday

• For the availability of communication routes, refer to the table in Page 459 SetClockData (Writing clock
data).
• An error is returned when the own board is accessed.

11 FUNCTIONS
GetCpuType (Reading programmable controller CPU model)
Applicable controls
Feature
To read the model character string and the model code of programmable controller CPU, network board, and GOT.
Format
IRet = object.GetCpuType(szCpuName, ICpuType)
String szCpuName Programmable controller CPU model Output
character string
Integer ICpuType Programmable controller CPU model Output
code
■ Visual C#
iRet = object.GetCpuType (ref szCpuName, ref iCpuType)
String szCpuName Programmable controller CPU model Output
character string
int iCpuType Programmable controller CPU model Output
code
Returned value
Description
• The model and the model code of the communication target programmable controller CPU are stored in szCpuName and
iCpuType respectively.
• The model character string of the programmable controller CPU is returned in UNICODE.
Model character string and model code of CPU

For details, refer to the table in Page 463 GetCpuType (Reading programmable controller CPU model).
11 FUNCTIONS
SetCpuStatus (Remote control)
Applicable controls
Feature 11
To perform a remote operation of programmable controller CPU.
Format
IRet = object.SetCpuStatus(IOperation)
Integer IOperation Remote RUN/STOP/PAUSE Input
■ Visual C#
iRet = object.SetCpuStatus (iOperation)
int iOperation Remote RUN/STOP/PAUSE Input
Returned value
Description
The operation specified for iOperation is performed.
An error occurs when a value other than the following values is specified.
Value Operation
0 Remote RUN
1 Remote STOP
2 Remote PAUSE
• Since FXCPUs do not feature the PAUSE switch as programmable controller CPUs, an error is returned
when remote pause is specified in SetCpuStatus.
• An error is returned when a Q motion CPU is accessed and PAUSE is specified.
• An error is returned when an R motion CPU is accessed.
• For the availability of communication routes, refer to the table in Page 466 SetCpuStatus (Remote
control).

11 FUNCTIONS
EntryDeviceStatus (Registering devices for status monitoring)
Applicable controls
Feature
To register devices whose status to be monitored.
Format
IRet = object.EntryDeviceStatus(szLabelList, iSize, iMonitorCycle, iData)
String szLabelList(n) Registered label name list Input
Integer iSize Number of registered device points Input
Integer iMonitorCycle Status monitoring time interval Input
Integer iData(n) Registered device value list Input
■ Visual C#
iRet = object. EntryDeviceStatus(szLabelList, iSize, iMonitorCycle, iData)
System.String[n] szLabelList Registered label name list Input
int iSize Number of registered device points Input
int iMonitorCycle Status monitoring time interval Input
int[n] iData Registered device value list Input
Returned value
Description
• A device group for the size of iSize specified for szLabelList is checked whether it is in the status specified for iData.
Specify the check time for iMonitorCycle.
When the status is established, the OnDeviceStatus function of the user program is executed.
• The maximum number of device points for iSize is 20.
• Specify a value within the range from 1 second to 1 hour (set between 1 and 3600 in seconds) for iMonitorCycle.
An error occurs when any other value outside the above range is specified.
• The registered device value list is stored in iData.
11 FUNCTIONS
• Device status monitoring may not be performed at the specified status monitoring time intervals depending
on the conditions: personal computer performance, currently executed application load, time required for
communication with the programmable controller, or the like.
Simultaneous use of any other control functions would also be the cause of disabling device status
monitoring at the specified status monitoring time intervals.
• For iData, reserve a memory area for the number of points specified for iSize.
• An error occurs when the EntryDeviceStatus function is executed during a status monitoring. 11
When changing any status monitor condition, execute the FreeDeviceStatus function and then execute the
EntryDeviceStatus function.
• When the status of multiple devices changes at the same time, the OnDeviceStatus event is executed every
time the status changes.
(Example: When M0 is monitored)
Application MX Component Programmable controller
M0, M1 read request

Content of M0, M1
M0, M1 read request

Content of M0, M1 M0 ON !
Event notification
OnDeviceStatus (M0)
Event execution M0 OFF
M0, M1 read request
Content of M0, M1 M0, M1 ON !
Event notification
OnDeviceStatus (M0)
Event execution
Event notification
OnDeviceStatus (M1)
Event execution
• This function is a function to check the status establishment under the constant execution of random device
read by the control.
This function is not a function for a programmable controller CPU to notify the device status establishment
to MX Component.
Therefore, the control may not be able to check the device status establishment of programmable controller
CPU depending on the specified status monitoring time interval.
Considerations for checking word device status

When checking the word device status for negative values of -1 to -32768 (FFFFH to 8000H), set the monitor device value of
the EntryDeviceStatus function to any of 65535 to 32768 (0000FFFFH to 00008000H) where '0' is stored in the upper 2-byte.
(Example) When checking the D0 status for "-10"
Set the value "65526 (0000FFF6H)" where '0' is stored in the upper 2-byte of "-10 (FFFFFFF6H)" for the monitor device value.
While the type of word devices of the programmable controller CPU is WORD type, the type of monitor device value of the
EntryDeviceStatus function is LONG type. Therefore, when current values of programmable
controller CPU are compared with monitor device values of the EntryDeviceStatus function, the values do not match and the
above setting is required. (When bit devices or Double Word devices are used, this consideration does not apply.)
For the programming examples regarding this consideration, refer to the following:
Page 642 Programing Examples for Monitoring Word Device Status

11 FUNCTIONS
■ Data type
Basic type Bit, Word Label name Integer/int
(32-bit value)

Specify the device values to be registered as follows:
■ When specifying bit devices and word devices

Example: Register 1 point of M0 and D0.
 Label setting
[0] LABEL1 Bit M0
[1] LABEL2 Word D0
 umber of registered device points: 2

 Registered device values
D0 LABEL2

Example: Register 3 points of devices including CN200.
 Label setting
[0] LABEL1 Word D0
[1] LABEL2 Word CN200
[2] LABEL3 Word D1
 Number of registered device points: 3

H of CN200 L of CN200*1 LABEL2
*1 For CN200 and later devices of FXCPU, 4-byte can be registered.

Example: Register 3 points of data from FD0.
 Label setting
[0] LABEL1 Word D0
[1] LABEL2 Word FD0
[2] LABEL3 Word D1
 Number of registered device points: 3

LL of FD0*1 LABEL2
D1 LABEL3
*1 Only the lower 2-byte can be registered. The HH, HL, and LH (upper 6-byte) of specified devices cannot be registered.
11 FUNCTIONS
FreeDeviceStatus (Deregistering devices for status monitoring)
Applicable controls
Feature
To deregister devices registered by using the EntryDeviceStatus function to monitor their status. 11
Format
IRet = object.FreeDeviceStatus()
■ Visual C#
Returned value
Description
The devices that are set using the EntryDeviceStatus function to monitor their status are deregistered.
11 FUNCTIONS
OnDeviceStatus (Event notification)
Applicable controls
Feature
To execute the event notification when the device condition registered using the EntryDeviceStatus function is satisfied.
Format
AddHandler object.OnDeviceStatus, AddressOf object_OnDeviceStatus
• Event handler
Private Sub object_OnDeviceStatus(ByVal sender As System.Object,
ByVal e As MITSUBISHI.Component.DeviceStatusEventArgs)
sender Event occurrence Output
source
e Event data Output
e.szDevice Name of label whose condition is satisfied
e.lData Value of device whose condition is satisfied
e.lReturnCode Returned value of condition check processing

RemoveHandler object.OnDeviceStatus, AddressOf object_OnDeviceStatus
■ Visual C#
object.OnDeviceStatus += new MITSUBISHI.Component.DotUtlType.DeviceStatusEventHandler (object_OnDeviceStatus);
• Event handler
private void object_OnDeviceStatus(object sender, MITSUBISHI.Component.DeviceStatusEventArgs e)
sender Event occurrence Output
source
e Event data Output
e.szDevice Name of label whose condition is satisfied
e.lData Value of device whose condition is satisfied
e.lReturnCode Returned value of condition check processing

object.OnDeviceStatus -= new MITSUBISHI.Component.DotUtlType.DeviceStatusEventHandler(object_OnDeviceStatus);
Returned value
None
Description
• The event is notified to the application when the device condition registered using the EntryDeviceStatus function is
satisfied.
Programming this function in the user program allows the application to receive the event when the registered device
condition is satisfied.
• Device values registered using the EntryDeviceStatus function are input to lData.
Example: When the word device is monitored for the value of "-1"
Set 65535 (0000FFFFH) as a registered device value using the EntryDeviceStatus function.
When the value of the target word device of the programmable controller CPU becomes
"-1" (FFFFH), the OnDeviceStatus function is executed and (0000FFFFH) is input to lData.
11 FUNCTIONS
When any of the following settings is set in the user program, the event of the OnDeviceStatus function does
not occur even if the condition of the device registered to the EntryDeviceStatus function is satisfied.
Note that when the event occurrence becomes in wait status, the control function is not returned to the .Net
control and device management processing stops until the following setting is terminated.
• For user applications created by using Visual Basic .NET:
The message box is being displayed in the user program.
The InputBox/OutputBox is being displayed in the user program.
• For user programs created by using Visual Basic .NET or Visual C#: 11
The Sleep processing, WaitForSingleObject function, or similar standby function is being used in the user
program.
11 FUNCTIONS
ReadDeviceBlock2 (Reading devices in batch)
Applicable controls
Feature
To read devices in 2-byte data unit in batch.
Format
IRet = object.ReadDeviceBlock2(szLabel, iSize, sData)
Short sData(n) Read device value Output
■ Visual C#
iRet = object.ReadDeviceBlock2(ref szLabel, iSize, ref sData)
Returned value
Description
• Data of devices specified for iSize (number of read points) is read in batch starting from the device specified for szLabel
(label name).
• The read device values are stored in sData.
• For sData, reserve arrays for more than the amount specified for iSize.
• The maximum number of read points should be the value which satisfies the following condition:
label name.
read points.
read.
cannot be read.
timer coil (LSTC) cannot be read. Use the ReadDeviceRandom2 or GetDevice2 function.
11 FUNCTIONS
■ Data type
Array Label name Short/short
(16-bit value)
Array member Bit*2, Word, Double Word, Float (Single Precision), Float (Double Label name [number of
Precision), String*1, String (Unicode)*1, Time, Timer*2, Long timer*2,
Counter*2, Long counter*2, Retentive Timer*2, Long retentive timer*2
elements]
11
[n3]


For the number of read points, specify the following values according to the label data type.
Label (array) data type Number of Number of read points to be
(rounded up)
11 FUNCTIONS

Example: Read 3 points of data (3 words = 48 bits) from the devices starting from M0.
[0] to [2] LABEL Bit (0..47) M0 to M47

2-byte Applicable label
*1


D0 LABEL[0]
D1 LABEL[1]
D2 LABEL[2]

Example: Read 6 points (6 words = 3 double words) of data from the devices starting from CN200.
For CN200 and later devices of FXCPU, 2 points of data are read from each 1 point of device (upper (H) and lower (L) data).
Reading only 1 point of data will result in an error.

L of CN200 LABEL[0]
H of CN200
L of CN201 LABEL[1]
H of CN201
L of CN202 LABEL[2]
H of CN202
11 FUNCTIONS

2-byte
LL of FD0
Applicable label
LABEL[0]
11
LH of FD0
HL of FD0
HH of FD0
LL of FD1 LABEL[1]
LH of FD1
HL of FD1
HH of FD1
■ When specifying double word devices in Double Word type

Example: Read 2 points of data from the devices starting from LZ0.

L of LZ0 LABEL[0]
L of LZ1 LABEL[1]
11 FUNCTIONS
WriteDeviceBlock2 (Writing devices in batch)
Applicable controls
Feature
To write devices in 2-byte data unit in batch.
Format
IRet = object.WriteDeviceBlock2(szLabel, iSize, sData)
Short sData(n) Device value to be written Input
■ Visual C#
iRet = object.WriteDeviceBlock2(ref szLabel, iSize, sData)
Returned value
Description
• Data of devices specified for iSize (number of write points) is written in batch starting from the device specified for szLabel
(label name).
• Store the device values to be written in sData.
11 FUNCTIONS
• The maximum number of write points should be the value which satisfies the following condition:
label name.
written.
cannot be written.
timer coil (LSTC) cannot be read. Use the WriteDeviceRandom2 or SetDevice2 function.
11 FUNCTIONS
■ Data type
Array Label name Short/short
(16-bit value)
Array member Bit*2, Word, Double Word, Float (Single Precision), Float (Double Label name [number of
Precision), String*1, String (Unicode)*1, Time, Timer*2, Long timer*2, elements]
Counter*2, Long counter*2, Retentive Timer*2, Long retentive timer*2 Label name [n1] [n2] [n3]


For the number of write points, specify the following values according to the label data type.
Label (array) data type Number of Number of write points to be
(rounded up)
*1
Time 2 Number of label array elements  2*1
11 FUNCTIONS

Example: Write 3 points (3 words = 48 bits) of data to the devices starting from M0.
[0] to [2] LABEL Bit (0..47) M0 to M47

11
M0 to M15*1 LABEL[0]
*1
M16 to M31 LABEL[1]
M32 to M47*1 LABEL[2]


D0 LABEL[0]
D1 LABEL[1]
D2 LABEL[2]

Example: Write 6 points (6 words = 3 double words) of data to the devices starting from CN200.
For CN200 and later devices of FXCPU, 2 points of data are written to each 1 point of device (upper (H) and lower (L) data).
Writing only 1 point of data will result in an error.

L of CN200 LABEL[0]
H of CN200
L of CN201 LABEL[1]
H of CN201
L of CN202 LABEL[2]
H of CN202
11 FUNCTIONS
Example: Read 8 points (8 words) of data from the devices starting from FD0.

LL of FD0 LABEL[0]
LH of FD0
HL of FD0
HH of FD0
LL of FD1 LABEL[1]
LH of FD1
HL of FD1
HH of FD1
Example: Write 6 points (6 words = 3 double words) of data to the devices starting from D0.

D0 LABEL[0]
D1
D2 LABEL[1]
D3
D4 LABEL[2]
D5
11 FUNCTIONS
ReadDeviceRandom2 (Reading devices randomly)
Applicable controls
Feature 11
To read devices in 2-byte data unit randomly.
Format
IRet = object.ReadDeviceRandom2(szLabel, iSize, sData)
IRet = object.ReadDeviceRandom2(szLabelList, iSize, sData)

■ Visual C#
iRet = object.ReadDeviceRandom2(ref szLabel, iSize, ref sData)
iRet = object.ReadDeviceRandom2(ref szLabelList, iSize, ref sData)

Returned value
Description
• Data of a device group specified for the label name szLabel (szLabelList) is read for the size of iSize.
• The read device values are stored in sData.
11 FUNCTIONS
• The maximum number of read points is 0x7FFFFFFF.
label name.
read points.
read.
cannot be read.
• When specifying a double word device, this function stores only the data of lower 1 word (2-byte). (An error
does not occur.)
Use the ReadDeviceRandom or ReadDeviceBlock function to read data from double word devices.
system label.

■ Data type
Basic type Bit, Word, Double Word, Float (Single Precision), Float (Double Label name Short/short
Precision), String*1, String (Unicode)*1, Time, Timer*2, Long (16-bit value)
timer*2, Counter*2, Long counter*2, Retentive Timer*2, Long
retentive timer*2
Array Label name
Array member (The label data type can be specified in the same manner as the Label name [number of
basic type.) elements]
Structure member (The label data type can be specified in the same manner as the Label name.Member name
basic type.)
elements]
Structured array member (The label data type can be specified in the same manner as the Label name [number of
basic type.) elements].Member name
[n3].Element


For the number of read points, specify the sum of the following values correspond to the elements according to the label data
type.
up)
11 FUNCTIONS
*1 When specifying a double word device for a label, the number of devices (elements) is 1. Only the lower 2-byte can be read.

11
■ When specifying CN200 and later devices of FXCPU or double word devices
Example: Read 3 points of data from the devices including CN200.
 Label setting
[0] LABEL1 Word D0
[1] LABEL2 Double Word CN200
[2] LABEL3 Word D1

D0 LABEL1
L of CN200*1 LABEL2
D1 LABEL3
*1 Only the lower 2-byte is read. Data is not read from the H (upper 2-byte) of specified device.

Example: Read 3 points of data from the devices including FD0.
 Label setting
[0] LABEL1 Word D0
[1] LABEL2 Word FD0
[2] LABEL3 Word D1

D0 LABEL1
LL of FD0*1 LABEL2
D1 LABEL3
11 FUNCTIONS
Example: Read data by specifying labels of Double Word, Float (Single Precision), Float (Double Precision), String*1, and
Time types.
 Label setting
szLabelList Data type Device
[1] LABEL2 Float (Single Precision) D100
[2] LABEL3 Float (Double Precision) D200
[3] LABEL4 String D300
[4] LABEL5 Time D400

D0 LABEL1
D1
D100 LABEL2
D101
D200 LABEL3
D201
D202
D203
D300 LABEL4


D316*1
D400 LABEL5
D401
*1 The number of points of characters to be read is 17 (32 characters + NULL).

The characters need to be converted in a user program because the characters of String type are not converted.

Example 1: Read 3 points of data from the bit devices (M0 to M2) by specifying array type labels.
 Label setting

M0 LABEL[0]
M1 LABEL[1]
M2 LABEL[2]
Example 2: Read 3 points of data from the word devices (D0 to D2) by specifying array type labels.
 Label setting

D0 LABEL[0]
D1 LABEL[1]
D2 LABEL[2]
11 FUNCTIONS
Example 3: Read 3 points of data from the word devices (CN200 to CN202) by specifying array type labels.
 Label setting

L of CN200 LABEL[0]
L of CN201 LABEL[1] 11
L of CN202 LABEL[2]
Example 4: Read 3 points of data from the word devices (FD0 to FD2) by specifying array type labels.
 Label setting

Example 5: Read 6 points (6 words = 3 double words) of data by specifying array type labels.
 Label setting

D0 LABEL[0]
D1
D2 LABEL[1]
D3
D4 LABEL[2]
D5
11 FUNCTIONS
 Label setting

D0 LABEL[0]

D16
D17 LABEL[1]

D33
D34 LABEL[2]

D50

Example: Read data by specifying structure type labels.
STRUCT L1 Bit
L2 Double Word
 Label setting
[0] LABEL1 STRUCT L1 D0.0
L2 D0
L2 CN200

D0.0 LABEL1.L1
D0 LABEL1.L2
D1
M0 LABEL2.L1
L of CN200 LABEL2.L2
L of CN201*1
*1 Data of two devices are read when the device of CN200 and later is specified for the Double Word type label.
11 FUNCTIONS
Example: Read data by specifying structure type array and structure array type labels.
STRUCT1 L1 Bit
L2 Word
L2 Double Word
 Label setting 11
L2 D0
L2 D100

X0 LABEL1[0].L1
D0 LABEL1[0].L2
X1 LABEL1[1].L1
D1 LABEL1[1].L2
M0 LABEL2.L1[0]
M1 LABEL2.L1[1]
M2 LABEL2.L1[2]
D100 LABEL2.L2
D101
11 FUNCTIONS
WriteDeviceRandom2 (Writing devices randomly)
Applicable controls
Feature
To write devices in 2-byte data unit randomly.
Format
Ret = object.WriteDeviceRandom2(szLabel, iSize, sData)
Ret = object.WriteDeviceRandom2(szLabelList, iSize, sData)

■ Visual C#
iRet = object.WriteDeviceRandom2(szLabel, iSize, sData)
iRet = object. WriteDeviceRandom2(szLabelList, iSize, sData)

Returned value
Description
• Data of a device group specified for the label name szLabel is written for the size of iSize.
• The device values to be written are stored in sData.
11 FUNCTIONS
• The maximum number of write points is 0x7FFFFFFF.
label name.
written. 11
cannot be written.
• When specifying a double word device, this function writes to the data area of lower 1 word (2-byte), and '0'
is written to the data area of upper 1 word (2-byte).
Use the WriteDeviceRandom or WriteDeviceBlock function to write double word devices.
system label.

■ Data type
Basic type Bit, Word, Double Word, Float (Single Precision), Float Label name Short/short
(Double Precision), String*1, String (Unicode)*1, Time, (16-bit value)
Timer*2, Long timer*2, Counter*2, Long counter*2,
Retentive Timer*2, Long retentive timer*2
Array Label name
Array member (The label data type can be specified in the same Label name [number of
manner as the basic type.) elements]
Structure member (The label data type can be specified in the same Label name.Member name
manner as the basic type.)
elements]
Structured array member (The label data type can be specified in the same Label name [number of
manner as the basic type.) elements].Member name
[n3].Element

11 FUNCTIONS
For the number of write points, specify the sum of the following values correspond to the elements according to the label data
type.
Label data type Number of Number of write points to be
up)
*1 When specifying a double word device for a label, the number of devices (elements) is 1. Only the lower 2-byte is written. Use the
WriteDeviceRandom function to write devices equivalent to 2 words or more.

■ When specifying CN200 and later devices of FXCPU or double word devices
Example: Write 3 points of data to the devices including CN200.
 Label setting
[0] LABEL1 Word D0
[1] LABEL2 Double Word CN200
[2] LABEL3 Word D1

D0 LABEL1
L of CN200*1 LABEL2
D1 LABEL3
*1 Only the lower 2-byte is written. Data is not written to the H (upper 2-byte) of specified devices.

Example: Write 2 points of data to the devices including FD0.
 Label setting
[0] LABEL2 Word FD0
[1] LABEL3 Word D1

LL of FD0*1 LABEL2
D1 LABEL3
*1 Only the lower 2-byte is written. Data is not written to the HH, HL, and LH (upper 6-byte) of specified devices.
11 FUNCTIONS
 Label setting

2-byte
D0
Applicable label
LABEL[0]
11
D1 LABEL[1]
 
 
D16 LABEL[16]

Example: Write a total of 6 points of data by specifying labels of Double Word, Float (Single Precision), and Time types.
 Label setting
[4], [5] LABEL3 Time D200, D201

D0 LABEL1
D1
D100 LABEL2
D101
D200 LABEL3
D201

Example: Write a total of 5 points of data by specifying Float (Double Precision) and a word device.
 Label setting

D0 LABEL1
D1
D2
D3
D200 LABEL2
11 FUNCTIONS
Example 1: Write 3 points of data to the bit devices (M0 to M2) by specifying array type labels.
 Label setting

M0 LABEL[0]
M1 LABEL[1]
M2 LABEL[2]
Example 2: Write 3 points of data to the word devices (D0 to D2) by specifying array type labels.
 Label setting

D0 LABEL[0]
D1 LABEL[1]
D2 LABEL[2]
Example 3: Write 6 points (6 words = 3 double words) of data by specifying array type labels.
 Label setting

D0 LABEL[0]
D1
D2 LABEL[1]
D3
D4 LABEL[2]
D5
Example 4: Write 34 points (D0 to D33) of string type data by specifying array type labels.
 Label setting

D0 LABEL[0]

D16
D17 LABEL[1]

D33
11 FUNCTIONS
Example: Write data by specifying structure type labels.
STRUCT L1 Bit
L2 Double Word
 Label setting
szLabelList
[0] LABEL1
Data type
STRUCT
Label name
L1
Device
D0.0
11
L2 D0
L2 CN200

D0.0 LABEL1.L1
D0 LABEL1.L2
D1
M0 LABEL2.L1
L of CN200 LABEL2.L2

Example: Write data by specifying structure type array and structure array type labels.
STRUCT1 L1 Bit
L2 Word
L2 Double Word
 Label setting
L2 D0
L2 D100

X0 LABEL1[0].L1
D0 LABEL1[0].L2
X1 LABEL1[1].L1
D1 LABEL1[1].L2
M0 LABEL2.L1[0]
M1 LABEL2.L1[1]
M2 LABEL2.L1[2]
D100 LABEL2.L2
D101
11 FUNCTIONS
SetDevice2 (Setting device data)
Applicable controls
Feature
To set one point of device in 2-byte data unit.
Format
IRet = object.SetDevice2(szLabel, sData)
Short sData Device value to be written Input
■ Visual C#
iRet = object.SetDevice2(ref szLabel, sData)
short sData Device value to be written Input
Returned value
Description
• The values of sData (device values to be written) are written to 1 point of device specified for szLabel (label name).
• When specifying bit devices, the least significant bit of the sData (device values to be written) is valid.
written.
• When specifying a double word device at the time other than specifying a double word device which can be
written for 1 point (such as CN200 and later devices of FXCPU), this function writes to the data area of
lower 1 word (2-byte). Use the WriteDeviceRandom or WriteDeviceBlock function to write double word
devices.
11 FUNCTIONS
■ Data type
Type class Label data type Label name Device data type
format
Basic type Bit, Word, Double Word*1, Float (Single Precision)*1, Float (Double Label name Short/short
Precision)*1, String*1, String (Unicode)*1, Time*1, Timer, Long timer,
Counter, Long counter, Retentive Timer, Long retentive timer
(16-bit value)
11
*1 Only the lower 2-byte of start device can be written.
Use the WriteDeviceRandom function to write 2 words or more of devices.


Example: Write data to M0.
 Label setting
[0] LABEL Bit M0

M0*1 LABEL
device value.

Example: Write data to D0.
 Label setting
[0] LABEL Word D0

D0 LABEL
■ When specifying CN200 and later devices of FXCPU (double word devices to which data of 2
words can be written for 1 point)
Example: Write data to CN200.
For CN200 and later devices of FXCPU, 4-byte is written.
Only the value of lower 2-byte can be set.
 Label setting

L of CN200 LABEL
11 FUNCTIONS
■ When specifying double word devices (ones to which data of 2 words cannot be written for 1
point)
Example: Write data by specifying D0.
 Label setting

D0*1 LABELW
*1 Data is written in order from the lower 2 bytes.

Example: Write data by specifying a string type label.
 Label setting
[0] LABELW String D0

D0*1 LABELW
*1 Data is written in order from the lower 2 bytes.
11 FUNCTIONS
GetDevice2 (Acquiring device data)
Applicable controls
Feature 11
To acquire one point of device in 2-byte data unit.
Format
IRet = object.GetDevice2(szLabel, sData)
Short sData Read device value Output
■ Visual C#
iRet = object.GetDevice2(ref szLabel, ref sData)
short sData Read device value Output
Returned value
Description
• One point of device data specified for szLabel (label name) is stored in sData (read device values).
read.
• For the read device values, reserve 2 bytes of memory area.
• When specifying a label equivalent to 2 words or more, this function stores only the data of lower 1 word (2-
byte). (An error does not occur.) Use the ReadDeviceRandom or ReadDeviceBlock function to read labels
equivalent to 2 words or more.

■ Data type
Type class Label data type Label name Device data type
format
Basic type Bit, Word, Double Word*1, Float (Single Precision)*1, Float (Double Label name Short/short
Precision)*1, String*1, String (Unicode), Time*1, Timer*2, Long timer*2, (16-bit value)
Counter*2, Long counter*2, Retentive Timer*2, Long retentive timer*2
*1 Only the lower 2-byte of start device can be read.

Use the ReadDeviceRandom function to read 2 words or more of devices.
11 FUNCTIONS

Example: Read data from M0.
 Label setting
[0] LABEL Bit M0

M0*1 LABEL

Example: Read data from D0.
 Label setting
[0] LABEL Word D0

D0 LABEL

Example: Read data by specifying a string type label.
 Label setting
[0] LABEL String D0

D0*1 LABEL
*1 Only the lower 2-byte is read to the start device.
11 FUNCTIONS
Dispose (release memory)
Applicable controls
Feature
To end the control for 64-bit (DotUtlType64_Server.exe). 11
Format
object.Dispose()
■ Visual C#
object.Dispose()
Returned value
None
Description
• The control used for 64-bit access (DotUtlType64_Server.exe) ends.
This function must be executed before discarding DotUtlType instances. Otherwise, DotUtlType64_Server.exe
cannot be ended.
11 FUNCTIONS
12 SAMPLE PROGRAMS
This chapter explains the sample programs registered at the installation of MX Component.
Precautions
• The sample programs are stored in (installation folder)\Samples at the installation. When executing the sample files, copy
them to any folder. When using the sample programs of VC++, also copy the include file.
• Sample programs are provided as a reference for creating user application programs. Use the programs with your
responsibility.
■ 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, use a control for 64-bit.
Sample program list

The following table shows the list of sample programs registered under (installation folder)\Samples when installing MX
Component.
■ Supported language: Visual Basic.NET

Folder name Sample program name Target Control Reference
Vb.Net\Act_2019 Act_2019.sln ActUtlType Page 578 Act_2019.sln,
ActProgType Dot_2019.sln
ActSupportMsg
ActUtlType64
ActProgType64
ActSupportMsg64
Vb.Net\ActDatalogging_2019 ActDatalogging_2019.sln ActUtlDataLogging Page 581
ActProgDataLoging ActDatalogging_2019.sln
ActUtlDataLogging64
ActProgDataLoging64
Vb.Net\Dot_2019 Dot_2019.sln DotUtlType Page 578 Act_2019.sln,
DotUtlType64 Dot_2019.sln
■ Supported language: Visual C#

Vcs.NET\Act_2019 Act_2019.sln ActUtlType Page 578 Act_2019.sln,
ActSupportMsg
ActUtlType64
ActProgType64
ActSupportMsg64
Vcs.NET\ActDatalogging_2019 ActDatalogging_2019.sln ActUtlDataLogging Page 581
ActUtlDataLogging64
ActProgDataLoging64
Vcs.NET\Dot_2019 Dot_2019.sln DotUtlType Page 578 Act_2019.sln,
DotUtlType64 Dot_2019.sln
12 SAMPLE PROGRAMS
576
■ Supported language: Visual C++
Vc\Act_2019 Act_2019sln ActUtlType Page 578 Act_2019.sln,
ActSupportMsg
ActUtlType64
ActProgType64
ActSupportMsg64
Vc\ActDatalogging_2019 ActDatalogging_2019.sln ActUtlDataLogging Page 581
ActUtlDataLogging64
ActProgDataLoging64
■ Supported language: VBA (Access)

12
VBA\Access ActTest.accdb ActUtlType Page 582 For Access
ActProgType (ActTest.accdb,ActTest64.ac
ActSupportMsg cdb)
ActTest64.accdb ActUtlType64 Page 582 For Access
ActProgType64 (ActTest.accdb,ActTest64.ac
ActSupportMsg64 cdb)
■ Supported language: VBA (Excel)

VBA\Excel ActUtlType.xlsm ActUtlType Page 586 For Excel
ActSupportMsg (ActUtlType.xlsm,
ActUtlType64.xlsm,
ActProgType.xlsm ActProgType
ActProgType.xlsm, and
ActProgType64.xlsm)
ActUtlType64.xlsm ActutlType64 Page 586 For Excel
ActSupportMsg64 (ActUtlType.xlsm,
ActUtlType64.xlsm,
ActProgType64.xlsm ActProgType64
ActProgType.xlsm, and
ActProgType64.xlsm)
12 SAMPLE PROGRAMS
577
12.1 Visual Basic.NET, Visual C#, Visual C++
Act_2019.sln, Dot_2019.sln
Window
Displayed items
Frame Select/Input item Description
Control ActUtlType, ActProgType*1 Select the control to be used.
LogicalStationNumber Enter the logical station number which was specified for the communication
setting in Communication Settings Utility.
Password Enter a password when using a CPU which requires a password.
[Open] button Click this to open a communication line.
[Close] button Click this to close a communication line.
Get/Set DeviceName/LabelName*2 Enter a device/label name for acquiring/setting devices or labels.
DeviceData Enter a device value for setting devices.
[GetDevice2] button Click this to acquire a device data from a programmable controller CPU by
executing the GetDevice2 with the data entered in the
"DeviceName"("LabelName") column in the same frame.*3
[SetDevice2] button Click this to set a device data to a programmable controller CPU by
executing the SetDevice2 with the data entered in the
"DeviceName"("LabelName") column and "DeviceData" column in the same
frame.
[GetDevice] button Click this to acquire a device data from a programmable controller CPU by
executing the GetDevice with the data entered in the
"DeviceName"("LabelName") column in the same frame..*3
[SetDevice] button Click this to set a device data to a programmable controller CPU by
executing SetDevice with the data the entered in the
"DeviceName"("LabelName") column and "DeviceData" column in the same
frame.
12 SAMPLE PROGRAMS
578 12.1 Visual Basic.NET, Visual C#, Visual C++
Random Read/Write DeviceName/LabelName*2 Enter a device/label name for reading/writing devices or labels randomly.
DeviceSize Enter the number of device points for reading/writing devices randomly.
DeviceData Enter the device value for writing devices randomly.
[ReadDeviceRandom2] button Click this to acquire a device data from a programmable controller CPU by
executing the ReadDeviceRandom2 with the data entered in the
"DeviceName"("LabelName") column and "DeviceSize" column in the same
frame.*3
[WriteDeviceRandom2] button Click this to set a device data to a programmable controller CPU by
executing the WriteDeviceRandom2 with the data entered in the
"DeviceName"("LabelName") column, "DeviceSize" column, and
"DeviceData" column in the same frame.
[ReadDeviceRandom] button Click this to acquire a device data from a programmable controller CPU by
executing the ReadDeviceRandom with the data entered in the
"DeviceName"("LabelName") column and "DeviceSize" column in the same 12
frame.*3
[WriteDeviceRandom] button Click this to set a device data to a programmable controller CPU by
executing WriteDeviceRandom with the data entered in the
"DeviceName"("LabelName") column and "DeviceSize" column, and
Block Read/Write DeviceName/LabelName*2 Enter a device/label name for reading/writing devices or labels in batch.
DeviceSize Enter the number of device points for reading/writing devices in batch.
DeviceData Enter a device value for writing devices in batch.
[ReadDeviceBlock2] button Click this to acquire a device data from a programmable controller CPU by
executing the ReadDeviceBlock2 with the data entered in the
frame.*3
[WriteDeviceBlock2] button Click this to set a device data to a programmable controller CPU by
executing the WriteDeviceBlock2 with the data entered in the
"DeviceName"("LabelName") column, "DeviceSize" column, and
[ReadDeviceBlock] button Click this to acquire a device data from a programmable controller CPU by
executing the ReadDeviceBlock with the data entered in the
frame.*3
[WriteDeviceBlock] button Click this to set a device data to a programmable controller CPU by
executing the WriteDeviceBlock with the data entered in the
"DeviceName"("LabelName") column and "DeviceSize" column, and
Status Entry/Free*4 DeviceName/LabelName*2 Enter a device/label name for monitoring device status.
DeviceSize Enter the number of devices for monitoring device status.
MonitorCycle Enter the device status monitoring interval.
DeviceData Enter a registered device value for monitoring devices.
[EntryDeviceStatus] button Click this to register device monitoring by executing the EntryDeviceStatus
with the data entered in the "DeviceName"("LabelName") column and
"DeviceSize" column, "MonitorCycle" column and "DeviceData" column in
the same frame.
[FreeDeviceStatus] button Click this to deregister a device that is registered using the
EntryDeviceStatus function to monitor its status.
Output ReturnCode Displays the execution result of each method (function).
Data Display the read device values.
Message Code Enter a message code.
[GetErrorMessage] button Click this to acquire a message by executing the GetErrorMessage with the
data entered in "the Code" column in the same frame.*3
CpuType [GetCpuType] button Click this to acquire the CPU type name and CPU type name code from a
programmable controller CPU by executing the GetCpuType.*3
Status Status Enter a remote control to be set.
[SetCpuStatus] button Click this to set a remote control to a programmable controller CPU by
executing the SetCpuStatus with the data entered in the "Status" column in
the same frame.
12 SAMPLE PROGRAMS
12.1 Visual Basic.NET, Visual C#, Visual C++ 579
Clock Year Enter a year to be set for a programmable controller CPU.
Month Enter a month to be set for a programmable controller CPU.
Day Enter a day to be set for a programmable controller CPU.
Week Enter a day of the week to be set for a programmable controller CPU.
Hour Enter an hour to be set for a programmable controller CPU.
Minute Enter a minute to be set for a programmable controller CPU.
Second Enter a second to be set for a programmable controller CPU.
[GetClockData] button Click this to acquire a clock data from a programmable controller CPU.*3
[SetClockData] button Click this to set a clock data to a programmable controller CPU with the data
entered in the "Year" column, "Month" column, "Day" column, "Week"
column, "Hour" column, "Minute" column, and "Second" column in the same
frame.
Buffer Read/Write I/OAdress Enter an I/O address for reading/writing buffer memories.
BufferAddress Enter an address for reading/writing buffer memories.
BufferSize Enter a size for reading/writing buffer memories.
BufferData Enter a data for reading/writing buffer memories.
[ReadBuffer] button Click this to acquire a device data from a programmable controller CPU by
executing the ReadBuffer with the data entered in the "I/OAdress" column,
"BufferAddress" column, and "BufferSize" column in the same frame..*3
[WriteBuffer] button Click this to set a device data to a programmable controller CPU by
executing the WriteBuffer with the data entered in "I/OAdress" column,
"BufferAddress" column, "BufferSize" column, and "BufferData" column in
the same frame.
Sample Using Timer DeviceName/LabelName*2 Enter a device/label name for reading devices or labels.
[Start] button Click this to acquire a device data from a programmable controller CPU by
executing the ReadDeviceRandom with the data entered in the
"DeviceName"("LabelName") column in the same
frame.*3ReadDeviceRandom is executed every five seconds until the [Stop]
button is clicked.
[Stop] button Click this to stop the processing started by clicking the [Start] button in the
same frame.
*1 Appears in Act_2019.sln only. Not appears in Dot_2019.sln.

*2 For Act_2019.sln, DeviceName is displayed, and for Dot_2019.sln, LabelName is displayed.
*3 The acquisition result is displayed in the "Data" column in the "Output" frame.
*4 Not be displayed in the sample programs of Visual C++.
Operating procedure
1. Select a control to be used (ActUtlType or ActProgType) in "Control."
2. Enter a logical number in the "LogicalStationNumber" column.
3. Click the [Open] button to open a communication line.
4. Click the button of a method (function) to execute the function after entering the data which is an argument of method
(function) in each item.
The read device value is displayed in the "Data" on "Output," and the execution result of each method (function) is
displayed in the "ReturnCode" column.
5. Click the [Close] button on "Control" to close the communication line.
12 SAMPLE PROGRAMS
580 12.1 Visual Basic.NET, Visual C#, Visual C++
ActDatalogging_2019.sln
Window
12
Displayed items
Item Description
ActUtlDataLogging /ActProgDataLogging Select the control to be used.
ReturnCode Displays the execution result of each method.
FolderName Enter a name of a folder to be accessed.
[Display] button Click this to update the content displayed in "File list" column.
[Select] button Click this to apply a folder name selected in the "File list" column to "FolderName." When a file name
has already selected, a logging file is saved in a personal computer.
[Save] button Click this to display "Save As" screen. Only a text file (*.txt) can be selected in "Save as type."
[Close] button Click this to exit the sample program.
File list Displays files or folders in the path specified for "Folder" in a list. For a folder name, a slash '/' is
prefixed.
12 SAMPLE PROGRAMS
12.1 Visual Basic.NET, Visual C#, Visual C++ 581
12.2 VBA
This section explains the VBA sample programs for Access and Excel.
For Access (ActTest.accdb,ActTest64.accdb)
Menu window
Window
Displayed items
Item name Description
[ActUtlType] button (When using ActTest.accdb) Click this to open the Method screen for the ActUtlType control (for ActUtlType64 control).
[ActUtlType64] button (When using ActTest64.accdb)
[ActProgType] button (When using ActTest.accdb) Click this to open the Method screen for the ActProgType control (for (ActProgType64 control).
[ActProgType64] button (When using ActTest64.accdb)
[ActSupportMsg] button (When using ActTest.accdb) Click this to open the Method screen for the ActSupportMsg control (for ActSupportMsg64control).
[ActSupportMsg] button (When using ActTest64.accdb)
12 SAMPLE PROGRAMS
582 12.2 VBA
Method window
Window
12
Displayed items
Tab name Item Description
 [Property] button Click this to set the properties.
 Result Displays the execution result of each method (function).
 [Execute] button Click this to execute a method (function) in the selected tab.
 Interval(S) Displays a time interval for monitoring.
 [Monitor Start] button Click this to start the monitoring of the ReadDeviceBlock/
ReadDeviceBlock2. A method (function) is executed in the time interval
displayed in the "Interval(S)," and data is acquired.
 [Monitor End] button Click this to stop the monitoring of the ReadDeviceBlock/
ReadDeviceBlock2.
 [Close] button Click this to return to the menu window.
Open  
Close  
GetDevice, GetDevice2 Device Name Enter a device name for acquiring devices.
Device Data Displays an acquired device value.
SetDevice, SetDevice2 Device Name Enter a device name for setting devices.
Device Data Enter a device value for setting devices.
ReadDeviceRandom, Device Name Enter a device name for reading devices randomly.
ReadDeviceRandom2
Device Points Enter the number of device points for reading devices randomly.
Data file name Specify a save destination binary file name when saving the read data.
Dump When this checkbox is selected, displays the read data.
WriteDeviceRandom, Device Name Enter a device name for writing devices randomly.
WriteDeviceRandom2
Device Points Enter the number of device points for writing devices randomly.
Written device value Enter the device value for writing devices randomly. Data can be entered
automatically by selecting a data not specified.
ReadDeviceBlock, Device Name Enter a device name for reading devices in batch.
ReadDeviceBlock2 Device Points Enter the number of device points for reading devices in batch.
12 SAMPLE PROGRAMS
12.2 VBA 583
Tab name Item Description
WriteDeviceBlock, Device Name Enter a device name for writing devices in batch.
WriteDeviceBlock2
Device Points Enter the number of device points for writing devices in batch.
Written device value Enter the device value for writing devices randomly. Data can be entered
EntryDeviceStatus*1 Device Name Enter a device name for monitoring device status.
Points Enter the number of devices for monitoring device status.
Interval Enter the device status monitoring interval.
Device value Enter a registered device value for monitoring devices.
FreeDeviceStatus*1  
GetCpuType PLC CPU type Displays an acquired CPU type name.
PLC CPU type code Displays an acquired CPU type code.
SetCpuStatus Operation Enter a remote control to be set.
GetClockData, SetClockData Year Enter/displays a year to be set for a programmable controller CPU.
Month Enter/displays a month to be set for a programmable controller CPU.
Day Enter/displays a day to be set for a programmable controller CPU.
WeekDay Enter/displays a day of the week to be set for a programmable controller
CPU.
Hour Enter/displays an hour to be set for a programmable controller CPU.
Minute Enter/displays a minute to be set for a programmable controller CPU.
Second Enter/displays a second to be set for a programmable controller CPU.
ReadBuffer First I/O address Enter an I/O address for reading buffer memories.
Buffer memory address Enter an address for reading buffer memories.
Read size Enter a size for reading buffer memories.
WriteBuffer First I/O address Enter an I/O address for writing buffer memories.
Buffer memory address Enter an address for writing buffer memories.
Write size Enter a size for writing buffer memories.
Values written to buffer memory Enter a device value for writing buffer memories. Data can be entered
*1 Displayed only when using ActTest.accdb.
Operating procedure
1. Click the [Property] button to set the properties.
2. Select [Open] tab, and click the [Execute] button to open a communication line.
3. Select the tab of a method (function) to be executed, and click the [Execute] button after entering the data which is an
argument.
When the checkbox of "Dump" is selected, the read device value is displayed at the bottom in the screen.
The execution result of each method (function) is displayed in the "Result" column.
4. Select [Close] tab, and click the [Execute] button to close the communication line.
12 SAMPLE PROGRAMS
584 12.2 VBA
GetErrorMessage screen
Window
12
Displayed items
Item name Description
Error code Enter a message code.
Trouble shooting Displays an acquired message.
Result Displays an execution result of the GetErrorMessage.
[Execute] button Click this to execute the GetErrorMessage with the data entered in "Error code" column.
[Close] button Click this to return to the menu window.
12 SAMPLE PROGRAMS
12.2 VBA 585
For Excel (ActUtlType.xlsm, ActUtlType64.xlsm,
ActProgType.xlsm, and ActProgType64.xlsm)
Window
Displayed items
Method (function) Item Description
Open [Open] button Click this to open a communication line.
Close [Close] button Click this to close a communication line.
 RESULT Displays the execution result of each method (function).
 Other method Select a method (function) to which the cell moves from the combo box.
 [Execute] button Click this to execute a method (function) selected in the combo box based
on the input data.
 [Property] button Click this to set a property value of the ActUtlType/ActProgType.
 Result Displays the execution result of each method (function).
GetDevice, GetDevice2 Device name Enter a device name for acquiring devices.
Device value Displays an acquired device value.
SetDevice, SetDevice2 Device name Enter a device name for setting devices.
Device value Enter a device value for setting devices.
ReadDeviceRandom, Device name Enter a device name for reading devices randomly.
ReadDeviceRandom2
Points Enter the number of device points for reading devices randomly.
WriteDeviceRandom, Device name Enter a device name for writing devices randomly.
WriteDeviceRandom2
Points Enter the number of device points for writing devices randomly.
Device value Enter the device value for writing devices randomly. Data can be entered
ReadDeviceBlock, Device name Enter a device name for reading devices in batch.
ReadDeviceBlock2 Points Enter the number of device points for reading devices in batch.
Interval(sec) Enter a time interval for monitoring (second).
Start monitor Click this to start monitoring of a method (function). The method (function) is
executed in the time interval displayed in "Interval(sec)," and the data is
acquired.
WriteDeviceBlock, Device name Enter a device name for writing devices in batch.
WriteDeviceBlock2
Points Enter the number of device points for writing devices in batch.
Device value Enter the device value for writing devices randomly. Data can be entered
12 SAMPLE PROGRAMS
586 12.2 VBA
Method (function) Item Description
EntryDeviceStatus Device name Enter a device name for monitoring device status.
Points Enter the number of devices for monitoring device status.
Interval(sec) Enter the device status monitoring interval (second).
Device value Enter a registered device value for monitoring devices.
OnDeviceStatus Device and value to which condition Displays a result of the OnDeviceStatus event.
consists.
FreeDeviceStatus  
GetCpuType CPU type Displays an acquired CPU type name.
CPU type code Displays an acquired CPU type code.
SetCpuStatus Operation Enter a remote control to be set.
GetClockData, SetClockData Year Enter/displays a year to be set for a programmable controller CPU.
Month Enter/displays a month to be set for a programmable controller CPU. 12
Day Enter/displays a day to be set for a programmable controller CPU.
Day-of-week Enter/displays a day of the week to be set for a programmable controller
CPU.
Hour Enter/displays an hour to be set for a programmable controller CPU.
Minute Enter/displays a minute to be set for a programmable controller CPU.
Second Enter/displays a second to be set for a programmable controller CPU.
ReadBuffer First I/O address Enter an I/O address for reading buffer memories.
Buffer memory address Enter an address for reading buffer memories.
Read size Enter a size for reading buffer memories.
WriteBuffer First I/O address Enter an I/O address for writing buffer memories.
Buffer memory address Enter an address for writing buffer memories.
Write size Enter a size for writing buffer memories.
Device value Enter a device value for writing buffer memories. Data can be entered
GetErrorMessage [GetErrorMessage] button Click this to execute the GetErrorMessage based on the data input in
"ErrorCode(Hex)." An acquired message is output to the text right to the
button.
ErrorCode(Hex) Enter a message code.
RESULT Displays an execution result of the GetErrorMessage.
Operating procedure
1. Click the [Property] button to set the properties.
2. Click the [Open] button to open a communication line.
3. Select a method (function) to be executed in "Other method" and click the [Execute] button after entering the data which
is an argument of method (function).
When the checkbox of "Dump" is selected, the read device value is displayed.
The execution result of each method (function) is displayed in the "RESULT" column.
12 SAMPLE PROGRAMS
12.2 VBA 587
13 ERROR CODES
This chapter explains the error codes returned by controls and the error codes returned by CPUs, modules, and network
boards.
13.1 Error Code List

The following table shows the error codes.
Error code Error description Corrective action
0x00000000 Normal end -
0x01010002 Time-out error • Check the property timeout value.
• Check the settings in the communication settings utility.
• Check the programmable controller, unit settings, state of the cable, etc.
• Close and Open again.
• Exit the program and restart the personal computer.
0x01010005 Message error • Check the system noise.
• Check the property timeout value.
0x01010010 Programmable controller No. error • Check the station number set on the communication settings utility.
Communication could not be made with the specified • Check the station number set to ActStationNumber.
station number.
0x01010011 Mode error • Check if the correct CPU type setting is done.
Command not supported. • Check the programmable controller, unit settings, status of the cable, etc.
• Reinstall MX Component.
0x01010012 Special Unit Specification error • Check the specified address of the special unit.
0x01010013 Other data error • Check that the system configuration is not an unsupported configuration.
Communication cannot be made for some cause. • Check if the correct CPU type setting is done.
0x01010018 Remote request error • Cancel the remote operation being performed in another route.
Remote operation is being performed in a route different
from the communicating route.
0x01010020 Link error • Check that reset operation is not performed for the other end of
Link communications could not be made. communication, the control station (master station) or the station passed
through by routing.
• Check that the network parameter setting is correct.
0x01010021 Special Unit Bus error • Repair or exchange the special unit under consideration.
There is no response from the special unit under • Exit the program and restart the personal computer.
consideration. • Reinstall MX Component.
0x01800001 No command error • The corresponding method does not support.
The method does not support.
0x01800002 Memory lock error • Exit the program and restart the personal computer.
• When using an interface board for personal computer, increase the
minimum working set size of the personal computer.*1
0x01800003 Memory securing error • Exit the program and restart the personal computer.
• Exit other programs and secure free memory area.
• When using an interface board for personal computer, increase the
minimum working set size of the personal computer.*1
0x01800004 DLL load error • Exit the program and restart the personal computer.
0x01800005 Resource securing error • Exit the program and restart the personal computer.
0x01801001 Resource Timeout error • Execute again after the other object completes the communication.
The resource could not be retrieved within the specified • Execute again after increasing the timeout value.
time. • Exit the program and restart the personal computer.
13 ERROR CODES
588 13.1 Error Code List
0x01801002 Multi-line open error • Exit the program and restart the personal computer.
0x01801003 Open not yet executed
0x01801004 Open Type error • Exit the program and restart the personal computer.
0x01801005 Specified port error • Exit the program and restart the personal computer.
0x01801006 Specified module error • Check that the actual system configuration matches to the settings in the
communication settings utility or the values of the properties.
0x01801007 Specified CPU error • Check the CPU type set to ActCpuType.
• Check that the system configuration is not an unsupported configuration.
• Check the packet type set to ActPacketType.
0x01801008 Target station access error • Review the target station.
0x01801009 Registry open failure
Failed while opening data key of the registry.
13
0x0180100A Packet Type error • Recheck the ActPacketType.
The packet type specified is incorrect. • Exit the program and restart the personal computer.
0x0180100B Protocol Type error • Exit the program and restart the personal computer.
The protocol specified is incorrect. • Reinstall MX Component.
0x0180100C Registry search failure • Exit the program and restart the personal computer.
0x0180100D GetProcAddress failure
0x0180100E DLL non-load error
0x0180100F Another Object in execution • Execute again after some time
Method cannot be executed because of exclusive control in
progress.
0x01802001 Device error • Review the device name.
The device character string specified in the method is an
unauthorized device character string.
0x01802002 Device number error • Review the device number.
The device character string number specified in the method
is an unauthorized device number.
0x01802003 Program Type error • Exit the program and restart the personal computer.
0x01802004 Sumcheck error • Check the module side sumcheck setting.
The sumcheck value of the received data is abnormal. • Check the sumcheck property of the control.
• Check the cable.
0x01802005 Size error • Check the number of points specified in the method.
The number of points specified in the method is • Review the system, e.g. programmable controller CPU, module setting
unauthorized. and cable status.
0x01802006 Block number error • Review the block specifying number in the device character string
The block specifying number in the device character string specified in the method.
specified in the method is unauthorized.
0x01802007 Receive data error • Review the system, e.g. programmable controller CPU, module setting
The data received is abnormal. and cable status.
• Check the cable.
0x01802008 Write Protect error • Exit the program and restart the personal computer.
0x01802009 Reading Parameters error
0x0180200A Writing Parameters error
0x0180200B Programmable controller type mismatch • Set the correct CPU type as the CPU type of the property.
The CPU type set to the property and the CPU type set on • Set the correct CPU type on the communication settings utility.
the communication settings utility do not match the CPU • Review the system, e.g. programmable controller CPU, module setting
type on the other end of communication. and cable status.
13 ERROR CODES
13.1 Error Code List 589
0x0180200C Request Cancel error • Exit the program and restart the personal computer.
The request was cancelled while being processed. • Reinstall MX Component.
0x0180200D Drive Name error
The specified drive name is incorrect.
0x0180200E Beginning Step error
The beginning step specified is incorrect.
0x0180200F Parameter Type error
The parameter type is incorrect.
0x01802010 File Name error
The file name is incorrect.
0x01802011 Status error
The status of Registration/Cancellation/Setting is incorrect.
0x01802012 Detailed Condition Field error
0x01802013 Step Condition error
0x01802014 Bit Device Condition error
0x01802015 Parameter Settings error
0x01802016 Error in specifying station number • Check the station number.
Method does not support the operations corresponding to • Check if the method being executed is supported or not.
the specified station number. • Check the system configuration such as programmable controller, unit,
etc.
0x01802017 Keyword error • Exit the program and restart the personal computer.
0x01802018 Read/Write Flag error • Reinstall MX Component.
0x01802019 Refresh Method error

0x0180201A Buffer Access Method error
0x0180201B Start Mode/Stop Mode error
0x0180201C Written clock data error • Review the clock data to be written.
Clock data specified for write cannot be written properly
since that data is in error.
0x0180201D Online clock data write error • Place the programmable controller CPU in the STOP status
Write of clock data failed.
Clock data cannot be written since the programmable
controller CPU is during RUN.
0x0180201E ROM drive error • Exit the program and restart the personal computer.
0x0180201F While Tracing error
Invalid operation was carried out during trace.
0x01802020 First I/O number error • Check the value of the first I/O number specified in the method.
The first I/O number specified in the method is an • Using the GPP function, check the programmable controller CPU
unauthorized value. parameters (I/O assignment).
0x01802021 First address error • Check the value of the buffer address specified in the method.
The buffer address specified in the method is an • Exit the program and restart the personal computer.
unauthorized value.
0x01802022 Pattern error • Exit the program and restart the personal computer.
0x01802023 SFC Block No. error
0x01802024 SFC Step No. error
0x01802025 Step No. error
0x01802026 Data error
0x01802027 System Data error
0x01802028 Error in number of TC settings Value
0x01802029 Clear Mode error
0x0180202A Signal Flow error
13 ERROR CODES
0x0180202B Version Control error • Exit the program and restart the personal computer.
0x0180202C Monitor Not Registered error
0x0180202D PI Type error
0x0180202E PI No error
0x0180202F Error in Number of PIs
0x01802030 Shift error
0x01802031 File Type error
0x01802032 Specified module error
0x01802033 Error check flag error
0x01802034 Step RUN operation error
0x01802035 Step RUN data error
0x01802036 During Step RUN error
0x01802037 Write error while running program corresponding to E2ROM
0x01802038 Clock data read/write error • Do not execute clock data read/write.
The clock data read/write method was executed for the 13
programmable controller CPU which does not have the
clock devices.
0x01802039 Trace not completed error • Exit the program and restart the personal computer.
0x0180203A Registration Clear Flag error
0x0180203B Operation error
0x0180203C Error in the number of exchanges
0x0180203D Error in number of loops specified
0x0180203E Retrieve data selection
0x0180203F Error in number of SFC cycles
0x01802040 Motion PLC Error
0x01802041 Motion PLC Communication error
0x01802042 Fixed execution time setting error
0x01802043 Error in number of functions
0x01802044 System information specification error
0x01802045 Registration Condition Not Formed error
0x01802046 Function No. error
0x01802047 RAM drive error
0x01802048 ROM drive error at the booting side
0x01802049 Transfer mode specification error at the booting side
0x0180204A Insufficient memory error
0x0180204B Back up drive ROM error
0x0180204C Block size error
0x0180204D Detached during RUN state error • Exit the program and restart the personal computer.
0x0180204E Unit Already Registered error
0x0180204F Password Registration Data Full error
0x01802050 Password Not Registered error
0x01802051 Remote Password error
0x01802052 IP Address error
0x01802053 Timeout value out of range error
0x01802054 Command not detected error
0x01802055 Trace execution type error
0x01802056 Version error
0x01802057 Tracking cable error • Reexamine the system such as the programmable controller CPU,
The tracking cable is faulty. module setting and cable status.
The programmable controller CPU status is error.
0x0180205C Keyword protection error • Disable the keyword and execute again.
Programmable controller CPU is protected by the key word.
0x0180205D Keyword disable error • Input a correct keyword.
The inputted keyword is wrong.
13 ERROR CODES
0x0180205E Keyword protecting error • Execute again or re-switch the power of the programmable controller.
Programmable controller CPU did not accept the protecting
command.
0x0180205F Keyword entry error • Input a correct keyword.
An illegal character is included in the inputted keyword.
0x01802060 Keyword deletion error
The inputted keyword is wrong.
0x01802062 Received packet CRC check error • Execute the communication process again.
An error occurred in CRC check for receive packet data.
0x01802063 Received packet CRC check error
An error occurred in CRC check for whole data file of
receive packet.
0x01802064 FX Series programmable controller connection error • Execute the communication process again.
0x01802070 Online change program error • Execute the online change after turning the programmable controller CPU
No target program for online change exists in the to STOP.
0x01802071 Ether direct communication multiple response receive error • Check that the personal computer and the programmable controller CPU
Multiple responses were received during Ether direct are in a one-to-on connection.
communication.
0x01802072 Ether direct communication error
Cannot communicate because the programmable controller
CPU is being accessed by another personal computer
during Ether direct communication.
0x01802073 Programmable controller CPU search response error • Reduce the number of programmable controllers on the network to 1024
The number of responses in the programmable controller or less.
CPU search exceeded the maximum number to be
searched.
0x01802074 Redundant system other system connection diagnostics • Disconnect the cable and connect it to the currently disconnected
error programmable controller CPU.
• Or, change the redundant CPU specification to the self system.
0x01808001 Multiple Open error • Exit the program and restart the personal computer.
Open method was executed while it was open. • Execute any method other than Open.
0x01808002 Channel number specifying error • Set the correct value to the port number of the property.
The port number set to the property and the port number • Make communication settings again on the communication settings utility.
set on the communication settings utility are unauthorized
values.
0x01808003 Driver not yet started • Start the driver.
The network board driver is not started.
0x01808004 Error in overlap event generation • Exit the program and restart the personal computer.
0x01808005 MUTEX generation error • Exit the program and restart the personal computer.
Creation of MUTEX to exercise exclusive control failed. • Reinstall MX Component.
0x01808006 Error in socket object generation • Exit the program and restart the personal computer.
Socket object could not be created • Reinstall MX Component.
0x01808007 Socket object generation error • Check for a running application which uses the same port number.
Creation of the Socket object failed. • Retry after changing the port number value of the property.
• Retry after changing the port number value on the communication settings
utility.
• Check whether the first character of IP address is not zero.
• Make Ethernet board and protocol settings on the control panel of the OS.
• Right-click and select "Run as administrator" when starting the
application.
0x01808008 Port connection error • Review the IP address and port number values of the properties.
Establishment of connection failed. • Review the port number value on the communication settings utility.
The other end does not respond. • Review the system, e.g. programmable controller CPU, module setting
and cable status
0x01808009 COM port handle error • Check for an application which uses the COM port.
The handle of the COM port cannot be acquired. • Exit the program and restart the personal computer.
The COM port object cannot be copied.
The SOCKET object cannot be copied.
13 ERROR CODES
0x0180800A Buffer size setting error • Check for an application which uses the COM port.
Setting of the COM port buffer size failed. • Make COM port setting on the control panel of the OS.
0x0180800B DCB value acquisition error
Acquisition of the COM port DCB value failed.
0x0180800C DCB setting error
Setting of the COM port DCB value failed.
0x0180800D Time-out value setting error • Check the property timeout value.
Setting of the COM port time-out value failed. • Review the time-out value on the communication settings utility.
• Check for an application which uses the COM port.
• Make COM port setting on the control panel of the OS.
0x0180800E Shared memory open error • Check whether the GX Simulator has started.
Open processing of shared memory failed. • Exit the program and restart the personal computer.
0x01808101 Duplex close error • Exit the program and restart the personal computer.
0x01808102 Handle close error
Closing of the COM port handle failed.
0x01808103 Driver close error
Closing of the driver handle failed.
13
0x01808104 Overlap Event Close error • Exit the program and restart the personal computer.
0x01808105 Mutex Handle Close error
0x01808106 COM Port Handle Close error
0x01808201 Send error • Review the system, e.g. programmable controller CPU, module setting
Data send failed. and cable status.
• Make COM port setting on the control panel of the OS.
• Make Ethernet board and protocol settings on the control panel.
• Retry the method.
0x01808202 Send data size error • Exit the program and restart the personal computer.
Data send failed.
0x01808203 Queue clear error • Exit the program and restart the personal computer.
Clearing of the COM port queue failed. • Close and Open again.
0x01808301 Receive error • Review the system, e.g. programmable controller CPU, module setting
Data receive failed. and cable status.
• Check the property timeout value.
• Review the time-out value on the communication settings utility.
0x01808302 Not Sent error • Exit the program and restart the personal computer.
0x01808303 Error in retrieving Overlap Event • Exit the program and restart the personal computer.
0x01808304 Receive buffer size shortage • Exit the program and restart the personal computer.
Receive data was larger than the receive buffer size
prepared for the system.
0x01808401 Control error
Changing of the COM port communication control failed.
0x01808402 Signal Line Control error • Exit the program and restart the personal computer.
0x01808403 Signal line specifying error • Exit the program and restart the personal computer.
Changing of the COM port communication control failed.
0x01808404 Open not yet executed • Execute Open.
0x01808405 Communication parameter error • Review the data bit and stop bit values of the properties.
The data bit and stop bit combination of the properties is • Set it again on the communication settings utility.
unauthorized.
0x01808406 Transmission speed value specifying error • Review the transmission speed value of the property.
The transmission speed of the property is unauthorized. • Set it again on the communication settings utility.
0x01808407 Data length error • Review the data bit value of the property.
The data bit value of the property is unauthorized. • Set it again on the communication settings utility.
0x01808408 Parity specifying error • Review the parity value of the property.
The parity value of the property is unauthorized. • Set it again on the communication settings utility.
13 ERROR CODES
0x01808409 Stop bit specifying error • Review the stop bit value of the property.
The stop bit value of the property is unauthorized. • Set it again on the communication settings utility.
0x0180840A Communication control setting error • Review the control value of the property.
The control value of the property is unauthorized. • Set it again on the communication settings utility.
0x0180840B Time-out error • Check the property timeout value.
Though the time-out period had elapsed, data could not be • Set it again on the communication settings utility.
received. • Review the system, e.g. programmable controller CPU, module setting
and cable status.
• Check if communication can be established with the Ping command.
0x0180840C Connect error • Exit the program and restart the personal computer.
0x0180840D Duplex connect error
0x0180840E Attach failure
Attaching of the socket object failed.
0x0180840F Signal line status acquisition failure
Acquisition of the COM port signal line status failed.
0x01808410 CD signal line OFF • Review the system, e.g. programmable controller CPU, module setting
The CD signal on the other end of communication is in the and cable status.
OFF status. • Exit the program and restart the personal computer.
0x01808411 Password mismatch error • Check the remote password of the property.
0x01808412 TEL Communication error • Exit the program and restart the personal computer.
0x01808501 USB driver load error • Exit the program and restart the personal computer.
Loading of the USB driver failed. • Reinstall MX Component.
• Check USB driver installation.
0x01808502 USB driver connect error
Connection of the USB driver failed.
0x01808503 USB driver send error • Review the system, e.g. programmable controller CPU, module setting
Data send failed. and cable status.
• Make USB setting on the control panel (device manger) of the OS.
0x01808504 USB driver receive error
Data receive failed.
0x01808505 USB Driver Timeout error • Recheck the timeout value.
0x01808506 USB driver initialization error • Make USB setting on the control panel (device manger) of the OS.
Initialization of the USB driver failed. • Exit the program and restart the personal computer.
0x01808507 Other USB error • Disconnect the cable once, then reconnect.
Error related to data send/receive occurred. • Exit the program and restart the personal computer.
0x01809000 GX Works2 uninstallation error • Install GX Works2.
The error occurred by retrieving the installation passing of
GX Simulator2.
0x01809001 GX Simulator2 unstart error • Start GX Simulator2.
GX Simulator2 did not start.
0x01809002 GX Simulator2 start error • Exit the program and restart the personal computer.
0x01809003 GX Simulator2 start time-out error
0x01809004 GX Simulator2 stop error
0x01809005 GX Simulator2 start error
0x01809007 GX Simulator2 stop error
Because it had reached upper bounds of the number of
simulations that was able to be started at the same time, it
was not possible to start.
The simulation of only one project that can be started has
started.
13 ERROR CODES
0x01809010 GX Simulator2 start information illegal error • Exit the program and restart the personal computer.
The error occurred because it was not able to secure the • Reinstall MX Component.
memory area to allocate GX Simulator2 start information.
0x01809022 GX Simulator2 start error • Exit the program and restart the personal computer.
The simulation of other CPU was not able to begin because • Reinstall MX Component.
the simulation of the project of FXCPU had already been
begun.
0x02000001 Points Exceeded error • Reduce the no. of points registered by the monitor.
The number of points registered in the monitoring server is • Exit the program and restart the personal computer.
very high. • Reinstall MX Component.
0x02000002 Shared memory creation error • Exit the program and restart the personal computer.
Failed in creating shared memory. • Reinstall MX Component.
0x02000003 Shared memory access error
0x02000004 Memory securing error • Close the other applications.
13
Failed in securing memory for the monitoring server. • Increase the system memory.
0x02000005 Device Not Registered error • Register the monitor in the monitoring server.
Monitor has not been registered. • Exit the program and restart the personal computer.
0x02000006 Monitoring Server Startup error • Start the Monitoring Server.
Monitoring Server is not started. • Exit the program and restart the personal computer.
0x02000010 Yet to retrieve Device Value error • Try to retrieve the value again after waiting for a fixed amount of time.
Monitoring is not yet completed. • Exit the program and restart the personal computer.
0x03000001 Command not Supported. • Exit the program and restart the personal computer.
Command is not supported. • Reinstall MX Component.
0x03000002 Memory lock error
Failed while locking memory.
0x03000003 Memory securing error
Failed in securing the memory.
0x03000004 DLL read error
Failed in reading DLL.
0x03000005 Resource securing error
Failed in securing the resources.
0x03010001 File Creation error • Check if there is enough space on the hard disk.
Failed in creating the file. • Exit the program and restart the personal computer.
• Reinstall MX Component
0x03010002 File Open error • Exit the program and restart the personal computer.
Failed to open the file. • Reinstall MX Component.
0x03010003 Buffer Size error
The buffer size specified is either incorrect or not enough.
0x03010004 SIL Sentence formation error
SIL sentence formation is incorrect.
0x03010005 File Name error • Specify a shorter filename.
The specified filename is too long. • Exit the program and restart the personal computer.
0x03010006 File does not exist error • Check the file name.
The specified file does not exist. • Check if the file exists or not.
0x03010007 File Structure error • Exit the program and restart the personal computer.
The data structure in the specified file is incorrect. • Reinstall MX Component.
0x03010008 File already exists error • Check the file name.
The specified file already exists. • Exit the program and restart the personal computer.
0x03010009 File does not exist error
The specified file does not exist.
13 ERROR CODES
0x0301000A File Deletion error • Exit the program and restart the personal computer.
The specified file could not be deleted. • Reinstall MX Component.
0x0301000B Multiple Open error
The specified project has been opened twice.
0x0301000C File Name error • Check the file name.
The specified filename is incorrect. • Exit the program and restart the personal computer.
0x0301000D File Read error • Exit the program and restart the personal computer.
Failed in reading the file. • Reinstall MX Component.
0x0301000E File Write error
Failed in writing the file.
0x0301000F File Seek error
File seek failed.
0x03010010 File Close error
Failed while closing the file.
0x03010011 Folder Creation error
Failed while creating the folder.
0x03010012 File Copy error • Exit the program and restart the personal computer.
Failed while copying the file. • Reinstall MX Component.
0x03010013 Project Path error
The length of the project path is incorrect.
0x03010014 Project Type error
The project type is incorrect.
The file type is incorrect.
0x03010016 Sub-File Type error
The sub-file type is incorrect.
0x03010017 Insufficient Disk space error
The disk space is insufficient.
0x03020002 Multiple Open error
Tried to open DBProduct more than once.
0x03020003 Not yet open error
DBProduct is not opened.
0x03020004 Extract error
DBProduct is not extracted.
0x03020010 Parameter error • Exit the program and restart the personal computer.
The parameters of DBProduct are incorrect. • Reinstall MX Component.
0x03020011 Language error
The language parameter is incorrect.
0x03020012 Error in specifying Maker
The maker parameter is incorrect.
0x03020013 Error in specifying Unit
The unit parameter is incorrect.
0x03020014 SQL Parameter error
SIL, SQL Parameter of DBProduct is incorrect.
0x03020015 SIL Sentence formation error
SIL sentence formation is incorrect.
0x03020016 Field Key Input Error
The entered field key is incorrect.
0x03020050 Record Data Construction error.
Failed in reconstructing the record data of DBProduct.
0x03020060 Error Retrieving Record Data
Failed while retrieving DBProduct record data.
0x03020061 Last Record error
Cannot retrieve the next record since the current record is
the last record.
13 ERROR CODES
0x03FF0000 Initialization error • Exit the program and restart the personal computer.
0x03FF0001 Not Initialized error
0x03FF0002 Multiple Initialization error
0x03FF0003 Workspace Initialization error
0x03FF0004 Database Initialization error
0x03FF0005 Recordset Initialization error
0x03FF0006 Error Closing Database
0x03FF0007 Error Closing Recordset
0x03FF0008 Database Not Opened error
Database is not opened.
0x03FF0009 Recordset Not Opened error
Recordset is not opened.
0x03FF000A Table Initialization error • Exit the program and restart the personal computer.
Failed in initializing TtableInformation table. • Reinstall MX Component.
0x03FF000B Table Initialization error
Failed in initializing TfieldInformation table. 13
0x03FF000C Table Initialization error
Failed in initializing TrelationInformation table.
0x03FF000D Table Initialization error
Failed in initializing Tlanguage table.
0x03FF000E Table Initialization error
Failed in initializing Tmaker table.
0x03FF000F Table Initialization error
Failed in initializing TOpenDatabase table.
0x03FF0010 Field Value error
0x03FF0011 Field Value error
0x03FF0012 Exit error
Failed to exit the database.
0x03FF0100 Moving Record error
Failed while moving the record.
0x03FF0101 Retrieving Record Count error
Failed to retrieve the record count.
0x03FF0110 Retrieving Field Value error
Failed in retrieving the field value.
0x03FF0111 Setting Field Value error
Failed in setting the field value.
0x03FFFFFF Other errors
0x04000001 No command error • Check the CPU type set to ActCpuType.
The specified CPU type cannot be used to perform • Check that the system configuration is not an unsupported configuration.
processing. • Exit the program and restart the personal computer.
0x04000002 Memory lock error • Exit the program and restart the personal computer.
Failed while locking memory. • Reinstall MX Component.
Failed in securing the memory.
0x04000004 Internal server DLL load error • Check for the deleted or moved installation file of MX Component.
Start of the internal server failed. • Exit the program and restart the personal computer.
13 ERROR CODES
0x04000005 Resource securing error • Exit the program and restart the personal computer.
Failed in securing the resources. • Reinstall MX Component.
0x04000006 Error Loading Main Object
Failed in reading the file.
0x04000007 Error Loading Conversion Table
Failed in reading table data.
0x04000100 Incorrect Intermediate Code Size error
0x04010001 Intermediate Code Not Converted error
The converted machine code for one command is more
than 256 bytes.
0x04010002 Intermediate Code Completion error
Intermediate code area of the code to be converted ended
abruptly.
0x04010003 Insufficient Intermediate Code error
The intermediate code of the code to be converted was
insufficient.
0x04010004 Intermediate Code Data error
The intermediate code to be converted is incorrect.
0x04010005 Intermediate Code Structure error • Exit the program and restart the personal computer.
The number of steps in the intermediate code is incorrect. • Reinstall MX Component.
0x04010006 Error in Number of Steps
The number of steps in comment intermediate code is
incorrect.
0x04010007 Insufficient Storage Space for Machine Code error
The storage space for machine code is insufficient.
0x04010008 Other errors (Other errors generated during the conversion
of Intermediate code to machine code.)
0x04011001 Machine Code Not Converted error
The converted intermediate code for one command is more
than 256 bytes.
0x04011002 Machine Code Completion error
The machine code area to be converted ended abruptly.
0x04011003 Could not convert since the machine code to be converted
was abnormal.
0x04011004 Insufficient Storage Space for Intermediate Code error
The storage area for intermediate code is insufficient.
0x04011005 Other errors (Other errors generated while converting
machine code to Intermediate code.)
0x04020001 Text Code Not Converted error
The converted intermediate code for one command is more
than 256 bytes.
0x04020002 No Input error
The input list code is insufficient.
0x04020003 Command error
The command name of list code to be converted is
incorrect.
0x04020004 Device error
The device name of list code to be converted is incorrect.
0x04020005 Device No. error
The device number of the list code to be converted is out of
range.
0x04020006 Conversion error
The list code to be converted conversion could not be
identified.
13 ERROR CODES
0x04020007 Text Data error • Exit the program and restart the personal computer.
The list code to be converted is incorrect. • Reinstall MX Component.
0x04020008 Error in SFC Operation Output
The output command of SFC operation is incorrect.
0x04020009 SFC Shift Condition error
SFC shift condition command is incorrect.
0x0402000A Error in Statements between lines
The statements entered between lines are incorrect.
0x0402000B P.I Statement error
The P.I statement entered is incorrect.
0x0402000C Note error
The Note entered is incorrect.
0x0402000D Comment error
The comment entered is incorrect.
0x0402000E Other errors (Other errors generated during the conversion
of list to Intermediate code)
0x04021001 Intermediate Code Not Converted error 13
The converted list code for one command has exceeded
256 bytes.
0x04021002 Intermediate Code Area Full error
Intermediate code area to be converted is full.
0x04021003 Command error
The command specified by the intermediate code to be
converted is incorrect.
0x04021004 Device error • Exit the program and restart the personal computer.
The device specified in the intermediate code to be • Reinstall MX Component.
converted is incorrect.
0x04021005 Intermediate Code error
The structure of intermediate code to be converted is
incorrect.
0x04021006 Insufficient List Storage Space error
The space for storing the converted list code is insufficient.
of intermediate code to list)
0x04030001 Not Converted error
The storage space for converted intermediate code is
insufficient.
0x04030002 Bad Circuit Creation error
The character memory circuit is not completed in a
sequence.
0x04030003 Specified Circuit Size Exceeded
Specified circuit size is too big.
0x04030004 Incorrect Return Circuit error
There is no consistency before and after the return circuit.
The setting for the return circuit is too high.
0x04030005 Other errors (Other errors generated while converting from
Character Memory to Intermediate Code)
0x04031001 Not Converted error
The size (vertical/horizontal) of the character memory
specified is incorrect.
0x04031002 Abnormal Command Code error
The command intermediate code to be converted is
incorrect.
0x04031003 Bad Circuit Creation error
Could not be converted to Sequence Circuit. There is no
END command.
13 ERROR CODES
0x04031004 Specified Circuit Size exceeded error • Exit the program and restart the personal computer.
Specified circuit size is too big. • Reinstall MX Component.
0x04031005 Fatal error
Fatal error has occurred.
0x04031006 Insufficient number of storage blocks error
The space to store the converted character memory circuit
blocks is not sufficient.
0x04031007 Circuit Block Search error
Data is broken off in the circuit block.
of intermediate code to character memory)
0x04040001 CAD Data error
The CAD data format is incorrect.
0x04040002 Output Data error
The input CAD data type and the output CAD data type are
not matching.
0x04040003 Library Load error
Failed to load the library.
0x04040004 Storage Space Secure error
The space secured to store the converted data is not
sufficient.
0x04040005 No END Command error
There is no END command in the data to be converted.
0x04040006 Abnormal Command Code
There is abnormal command code in the CAD data to be
converted.
The device number is out of range.
0x04040008 Step No. error • Exit the program and restart the personal computer.
The step number is out of range. • Reinstall MX Component.
0x04040009 Specified Circuit Size exceeded error
1 circuit block is too big.
0x0404000A Return Circuit Error
The return circuit is incorrect.
0x0404000B Bad Circuit Creation error
The circuit data is incorrect.
0x0404000C SFC Data error
The SFC data to be converted is incorrect.
0x0404000D List Data error
The list data to be converted is incorrect.
0x0404000E Comment Data error
The comment data to be converted is incorrect.
0x0404000F Statement error
The statement data to be converted is incorrect.
of CAD code to Intermediate code.)
0x04041001 Intermediate Code Data error
There is no intermediate code to be converted. The format
of the intermediate code is incorrect.
0x04041002 CAD Data Type error
The input CAD data type and the output CAD data type are
not matching.
13 ERROR CODES
0x04041003 Library error • Exit the program and restart the personal computer.
Failed to load the library. • Reinstall MX Component.
0x04041004 Insufficient Input Data error
Data to be converted is insufficient.
0x04041005 Insufficient Storage Space error
There is not enough space to store the CAD data to be
converted.
0x04041006 No END Command error
There is no END command in the data to be converted.
0x04041007 Abnormal Command Code error
There is abnormal command code in the CAD data to be
converted.
The device number is out of range.
0x04041009 Step No. error
The step number is out of range.
0x0404100A Specified Circuit Size exceeded error
1 circuit block is too big.
13
0x0404100B Return Circuit Error
The return circuit is incorrect.
0x0404100C Bad Circuit Creation error
The circuit data is incorrect.
0x0404100D SFC Data error
The SFC data to be converted is incorrect.
0x0404100E List Data error
The list data to be converted is incorrect.
0x0404100F Comment Data error
The comment data to be converted is incorrect.
0x04041010 Statement error • Exit the program and restart the personal computer.
The statement data to be converted is incorrect. • Reinstall MX Component.
of Intermediate code to CAD code.)
0x04050001 Abnormal Character String Specified error
Device character string specified is incorrect.
0x04050002 Device Points error
Device points are out of range.
0x04050003 Other errors (The errors generated during the conversion of
the Device Character String to Device Intermediate Code)
0x04051001 Device Name error
The classification specified for the device intermediate code
is incorrect.
0x04051002 Device Name error
The classification specified for the extended specification
device intermediate code is incorrect.
the Device Intermediate Code to Device Character String)
0x04052001 Abnormal Character String Specified error
Device character string specified is incorrect.
0x04052002 Device Points error
Device points are out of range.
the Device Character String to Device Representation
Code)
0x04053001 Device Representation error
is incorrect.
13 ERROR CODES
0x04053002 Device Representation error • Exit the program and restart the personal computer.
The classification specified for the extended specification • Reinstall MX Component.
The rectification part specified for the device is incorrect.
The rectification part specified for the extended device is
incorrect.
the Device Representation Code to Device Character
String)
0x04064001 Abnormal Device Intermediate Code error
The intermediate code for the device is incorrect.
of the Intermediate code for the Device to Device Name)
0x04065001 Abnormal Device Name error
is incorrect.
0x04065002 Abnormal Device Name error
The classification for the intermediate code of the extended
specification device is incorrect.
of the device name to Intermediate code)
0x04066001 Device Intermediate Code error
The intermediate code for the device is incorrect.
of the device intermediate code to device representation
code.)
0x04067001 Device Representation error • Exit the program and restart the personal computer.
The classification specified for the device intermediate code • Reinstall MX Component.
is incorrect.
The classification specified for the extended specification
The rectification part specified for the device is incorrect.
The rectification part specified for the extended device is
incorrect.
0x04067005 Other errors
(Other errors generated during the conversion of device
representation code to the device intermediate code)
0x04070001 Common Data Conversion error
The input data of the device comment conversion is
incorrect.
0x04070002 Insufficient Common Data
The data to be converted is insufficient.
0x04070003 Insufficient Storage Area
The area where the conversion data is stored is insufficient.
0x04071001 Error in CPU Data Conversion
The input data of the device comment conversion is
incorrect.
0x04071002 Insufficient CPU Data error
The data to be converted is insufficient.
0x04071003 Insufficient Storage Area
The area where the conversion data is stored is insufficient.
0x04072001 Open error
Failed in creating conversion object.
0x04072002 CPU Type error
The specified CPU type does not exist.
13 ERROR CODES
0x04072003 Not Converted error • Exit the program and restart the personal computer.
Converted object does not exist. • Reinstall MX Component.
0x04072004 Input Data error
The input data is incorrect.
0x04073001 Program Common Data Conversion error
0x04073002 Program Common Data Conversion error
0x04073101 Program CPU Data Conversion error
0x04074001 Common Data Parameter error
0x04074002 Network Parameter Common Data error
The parameter block exists, but the data inside is not set.
0x04074101 Parameter CPU Data error
0x04074102 Network Parameter CPU Data error
The parameter block exists, but the data inside is not set.
0x04074103 Offset error
0x04074201 Error in Specifying Network Type • Exit the program and restart the personal computer.
The CPU specified does not support the network type. • Reinstall MX Component. 13
0x04074202 Parameter Block Number error
The Block corresponding to the parameter block number
specified does not exist.
0x04074203 Parameter Block Content error
It is different from the content supported by the specified.
0x04074204 Parameter Block Information error
The specified block number does not exist.
0x04074205 Default Parameter Block is Abnormal
The specified block number does not exist.
0x04074301 Error in Conversion of the Common Parameter Block
0x04074302 Error in Common Parameter Block No. 1001
The value of the RUN-PAUSE settings existence flag is
incorrect.
The device intermediate code specified does not exist.
The settings for the annunciator display mode is incorrect.
0x0407430A Error in Common Parameter Block No. 4000
I/O Allotment Data is not created.
0x0407430B Error in Common Parameter Block No. 5000
The specified network is not supported.
0x0407430C Error in Common Parameter Block No. 5001
Valid unit No is not set while accessing other exchange.
0x0407430D Error in Common Parameter Block No. 5002
0x0407430E Error in Common Parameter Block No. 5003
0x0407430F Error in Common Parameter Block No. 5NM0
13 ERROR CODES
0x04074310 Error in Common Parameter Block No. 5NM1 • Exit the program and restart the personal computer.
0x04074311 Error in Common Parameter Block No. 5NM2
0x04074312 Error in Common Parameter Block No. 5NM3
0x04074314 Error in Common Parameter Block No. FF18
Link parameter Capacity is not set.
Calculation circuit check is not set.
Sampling Trace Data is not created.
Status latch data is not created.
0x04074318 Error in Common Parameter Block No. F42
Timer processing points are not set.
Setting value device for specified extended timer does not
exist.
0x0407431A Error in Common Parameter Block No. FF44
0x0407431B Error in Common Parameter Block No. FF45
0x0407431C Error in Common Parameter Block No. FF60
Terminal Settings are not set.
0x0407431D Error in Common Parameter Block No. FF70
User Release area is not set.
0x04074401 Error in Conversion of CPU Parameter Block • Exit the program and restart the personal computer.
0x04074402 Error in CPU Parameter Block No.1001 • Reinstall MX Component.
0x04074403 Error in CPU Parameter Block No.1003

0x04074406 Error in CPU Parameter Block No. 2001
0x0407440A Error in CPU Parameter Block No. 4000
0x0407440B Error in CPU Parameter Block No. 5000
The specified network type is not supported.
0x0407440C Error in CPU Parameter Block No. 5001
0x0407440D Error in CPU Parameter Block No. 5002
0x0407440E Error in CPU Parameter Block No. 5003
0x0407440F Error in CPU Parameter Block No. 5NM0
0x04074410 Error in CPU Parameter Block No. 5NM1 • Exit the program and restart the personal computer.
0x04074411 Error in CPU Parameter Block No. 5NM2
0x04074412 Error in CPU Parameter Block No. 5NM3
0x04074414 Error in CPU Parameter Block No. FF18
0x0407441A Error in CPU Parameter Block No. FF44
0x0407441B Error in CPU Parameter Block No. FF45
0x0407441C Error in CPU Parameter Block No. FF60
0x0407441D Error in CPU Parameter Block No. FF70
13 ERROR CODES
0x04075001 Common Data Conversion error • Exit the program and restart the personal computer.
Failed while converting the device memory settings portion. • Reinstall MX Component.
Failed while converting the device memory settings portion.
Device memory data portion did not exist.
Failed while converting the settings portion of the device
comments.
Failed while converting the data portion of the device
comments.
Failed while converting the settings portion of the device
13
comments.
Failed while converting the data portion of the device
comments.
0x04077001 Common Data Conversion error • Exit the program and restart the personal computer.
Failed during the conversion of sampling trace settings • Reinstall MX Component.
portion.
Failed during the conversion of sampling trace data portion.
Failed during the conversion of sampling trace settings
portion.
Failed during the conversion of sampling trace data portion.
Failed in the conversion of the status latch settings portion.
Failed in the conversion of the status latch data portion.
Failed in the conversion of the status latch settings portion.
Failed in the conversion of the status latch data portion.
0x04079101 Failure history CPU Data Conversion error • Exit the program and restart the personal computer.
0x0407A101 File List CPU Data Conversion error
0x0407B101 Error Information CPU Data Conversion error
0x0407C001 Error in Conversion of Indirect Address to Device Name
The device name storage area is not secured.
0x0407C002 Error in Conversion of Device Name to Indirect Address
Indirect Address storage area is not secured.
0x0407C003 Error in Conversion of Indirect Address to Device
Representation
The device representation storage area is not secured.
0x0407C004 Error in Conversion of Device Representation to Indirect
Address
0x0407C005 Error in Conversion of Indirect Address to Device Character
String
Device Character String storage area is not secured.
13 ERROR CODES
0x0407C006 Error in Conversion of Device Character String to Indirect • Exit the program and restart the personal computer.
Address • Reinstall MX Component.
0x0407C007 Error in Conversion of Intermediate Code to Device Name
The device name storage area is not secured.
0x0407C008 Error in Conversion of Device Name to Intermediate Code
Intermediate Code storage area is not secured.
0x0407C009 Error in Conversion of Intermediate Code to Device
representation
Device Representation storage area is not secured.
0x0407C00A Error in Conversion of Device Representation to
Intermediate Code
0x0407C00B Error in Conversion of Intermediate Code to Indirect
Address
0x0407C00C Error in Conversion of Indirect Address to Intermediate
Code
0x0407C00D CPU Type error
The specified CPU type is not supported.
0x0407C00E Device Character String error • Exit the program and restart the personal computer.
The specified device is not supported. • Reinstall MX Component.
0x0407C00F Device Character String error
The specified device character string, type is incorrect.
0x0407C010 Device error
The specified device is not supported by the specified CPU.
0x0407C011 CPU Type error
The specified CPU is not supported.
0x0407C012 Device out of Range error
0x0407D001 Common Data Conversion error
Error in Conversion of SFC trace condition settings portion.
0x0407D002 Common Data Conversion error
Error in Conversion of SFC trace condition data portion.
0x0407D101 Error in CPU Data Conversion
Error in Conversion of SFC trace condition settings portion.
0x0407D102 Error in CPU Data Conversion
Error in Conversion of SFC trace condition data portion.
0x04080001 Intermediate Code classification out of range error • Exit the program and restart the personal computer.
The intermediate code classification specified is out of • Reinstall MX Component.
range.
0x04080002 Extended specification Intermediate Code classification out
of range error
The extended specification intermediate code specified is
out of range.
0x04080003 Device Points check absent error
The device does not check the device points.
0x04090001 GPP Project error
The specified CPU type and GPP project type are not
matching.
The specified GPP project type and file type are not
matching.
0x04090010 Insufficient GPP Data to be converted
There is no data to be converted.
The data size specified is incorrect.
0x04090011 Insufficient Storage Space for Converted Data
The space for storing converted data is insufficient.
0x04090012 Error in GPP Data to be converted
The GPP data to be converted is incorrect.
13 ERROR CODES
0x04090110 Insufficient Data to be converted error • Exit the program and restart the personal computer.
There is no data to be converted. • Reinstall MX Component.
The data size specified is insufficient.
0x04090111 Insufficient Storage Space for Converted Data error.
The storage space for converted data is insufficient.
0x04090112 Error in data to be converted
The data to be converted is incorrect.
0x040A0001 Insufficient Intermediate Code Storage Space
The space secured to store the converted data is not
sufficient.
0x040A0002 The space to store addition SFC information is not
sufficient.
0x040A0003 Conversion error
0x040A0004 Non-SFC Program error
0x040A1001 Step Not Used / No Output error • Exit the program and restart the personal computer.
0x040A1002 Step No. out of range error
0x040A1003 Step Not Used / No Output error
13
0x040A1004 Transition No. out of range
0x040A1005 Maximum Number Exceeded error
0x040A1006 Microcontroller Program space error
0x040A1007 Non-SFC Program error
0x040B0001 Insufficient Intermediate Code Storage Space • Exit the program and restart the personal computer.
The space secured to store the converted data is not • Reinstall MX Component.
sufficient.
0x040B0002 Conversion error
0x040B1001 Failed in creating Step Start position table
0x040B1002 Error Reading Step Information
0x040B1003 Step No. Error
0x040B1004 Failed in reading the output of operation/Transition
condition intermediate code error
0x040B1005 Securing Internal Work Area Failed error
0x040B1006 Error in setting the maximum value of X direction for
character memory
0x040B1007 Insufficient Internal Work Area error
0x040B1008 Stack Overflow, Abnormal Character Memory
0x040B1009 Insufficient number of storage blocks error
0x040B100A Non-SFC Program error
0x04FFFFFF Other errors
0x10000001 No command error
0x10000002 Start of communication DLL of MX Component failed. • Exit the program and restart the personal computer.
0x10000003 Open failed. (DiskDrive) • Reinstall MX Component.
0x10000004 Duplex open error • Exit the program and restart the personal computer.
0x10000005 File Access error • Exit the program and restart the personal computer.
0x10000006 Incorrect Folder Name error
0x10000007 File Access Denied error
0x10000008 Disk Full error
0x10000009 File Deletion error
0x1000000A Incorrect File Name error
0x1000000C Execution failed since another application or thread is • Execute again after some time
making a request. • Perform programming according to the multithread rules of COM and
ActiveX.
0x1000000D Folder Creation error • Exit the program and restart the personal computer.
0x1000000E Folder/ File Type error
0x1000000F Offset Address error
0x10000010 Request Cancel
Cancel Process has occurred.
13 ERROR CODES
0x10000012 Open not yet executed • Exit the program and restart the personal computer.
0x10000013 Attach Not Executed error • Exit the program and restart the personal computer.
0x10000014 Object Invalid error
0x10000015 Request Cancel Failed error
0x10000016 Failed in Reading Status error
0x10000017 The specified size (number of devices) is unauthorized. • Check the number of points specified in the method.
0x10000018 There is no registered device. • Exit the program and restart the personal computer.
0x10000019 Data set Not Executed • Exit the program and restart the personal computer.
0x1000001A Read Not Executed error
0x1000001B Incorrect Create Flag error
0x1000001C Operation Over Access
0x1000001D Redundant Device error
0x1000001E Registry search failed. • Exit the program and restart the personal computer.
0x1000001F File Type error • Exit the program and restart the personal computer.
0x10000020 Device Memory Type error
0x10000021 Program Range error
0x10000022 TEL Type error
0x10000023 TEL Access error
0x10000024 Cancel Flag Type error • Exit the program and restart the personal computer.
0x10000030 Multiple Device Registration error
0x10000031 Device Not Registered error
0x10000032 Specified device error • Review the specified device data.
0x10000033 Specified device range error
0x10000034 File Write error • Exit the program and restart the personal computer.
0x10000040 Server start failed. • Reinstall MX Component.
0x10000041 Server Stop error

Failed while stopping the server.
0x10000042 Server Started Twice error
0x10000043 Server Not Started error
0x10000044 Resource Timeout error
0x10000045 Server Type error
0x10000046 Failed to Access Server error
0x10000047 Server Already Accessed error
0x10000048 Failed in Simulator Startup
0x10000049 Failed in exiting Simulator
0x1000004A Simulator Not Started error
0x1000004B Simulator Type error
0x1000004C Simulator Not Supported error
0x1000004D Simulator Started Twice error
0x1000004E Shared Memory Not Started error
0x10000055 GX Simulator3 did not start error • Start GX Simulator3.
0x1000005A System number error • Check the system number set on the communication settings utility.
0x8001000C Data out of the allowable setting range is specified. • Review the value of the property.
• Set it again on the communication settings utility.
0x80010016
13 ERROR CODES
• Check the unit settings, state of the cable, etc.
0x80020001 Type of data is invalid. • Review the value of the property.
0x80020002 Range of the data is incorrect.
0x80030001 The specification of the communication port is incorrect. • Review the communication port value of the property.
0x80030002 The specification of the Transmission speed is incorrect. • Review the transmission speed value of the property.
0x80030003 The specification of the Data bit length is incorrect. • Review the data bit value of the property.
0x80030004 The specification of the parity is incorrect. • Review the parity value of the property.
0x80030005 The specification of the stop bit length is incorrect. • Review the stop bit value of the property.
• Set it again on the communication settings utility. 13
0x80030006 The specification of the wait time is incorrect. • Review the wait time of the property.
0x80030007 The specification of the CR/LF is incorrect. • Review the CR/LF of the property.
0x80030008 The specification of the timeout is incorrect. • Check the property timeout value.
0x80030009 The specification of the station number is incorrect. • Review the station number of the property.
0x8003000A USB communication setting is invalid. • Review the value of the property.
0x8003000B USB model code is invalid.
0x8003000C Duplication was detected in station number of the USB • Review the station number of the property.
communication. • Set it again on the communication settings utility.
0x80200107 Communication error • Try the same method again.
0x80201101 Already open error • When changing the communication target CPU, execute the Open
The Open method was executed in the open status. method after performing Close.
0x80201104 DLL load error • Exit the program and restart the personal computer.
0x80201106 Error in Communication object generation • Exit the program and restart the personal computer.
0x80201201 Not yet open error • After executing the Open method, execute the corresponding method.
The Open method is not yet executed.
0x80209501 MT Simulator2 start error • Exit the program and restart the personal computer.
0x80209502 MT Simulator2 start error • Exit the program and restart the personal computer.
0x80209503 MT Simulator2 communication error • Exit the program and restart the personal computer.
0x80209504 MT Simulator2 start error • Retry after exiting MT Simulator2.
0x80209505 MT Simulator2 stop error • Exit the program and restart the personal computer.
0x80209506 MT Simulator2 stop error • Exit the program and restart the personal computer.
0x8020950F MT Simulator2 stop error • Retry after starting MT Simulator2.
MT Simulator2 is not started.
13 ERROR CODES
0x80209510 MT Simulator2 start error • Retry after starting MT Simulator2.
MT Simulator2 is not started.
0x80209516 MT Simulator2 start error • Install MT Works2.
MT Works2 uninstallation error.
0x80209518 MT Simulator2 start error • Execute after exiting the specified No. of MT Simulator2.
The specified number is already used.
0x80209519 Send data illegal error • Review the argument.
0x8020951C MT Simulator2 start error • Retry after exiting MT Simulator2.
MT Simulator2 is ending.
0x8020951D MT Simulator2 start error • Retry after performing Close.
Already executed Open.
0x8020951E MT Simulator2 non-Open error • Retry after performing Open.
0x8020951F MT Simulator2 start error • Retry after performing Close.
Already executed Open.
0x80206004 Remote request error • Change the switch on the module to RUN, exit the test mode, and try
again.
0x8020A104 DLL load error • Exit the program and restart the personal computer.
0x8020A203 Memory securing error • Exit the program and restart the personal computer.
0x80A00101 Not yet open error • After executing the Open method, execute the corresponding method.
0x80A00104 Already open error • When changing the communication target CPU, execute the Open
0x80A00105 Incorrect data type of the argument • Check the data type being used for the argument.
0x80A00106 Data range of the argument is invalid • Check the value being used for the argument.
0x80A00107 No command error • Not supported by the method.
0x80A00109 Data source cannot be opened. • Check the cable connection.
0x80A0010C The response format from the robot controller was • Take measures against noise
incorrect.
0xF0000001 No-license error • Using the license FD, give the license to the personal computer.
The license is not given to the personal computer.
0xF0000002 Set data read error • Specify the correct logical station number.
Reading of the set data of the logical station number failed. • Set the logical station number on the communication settings utility.
0xF0000003 Already open error • When changing the communication target CPU, execute the Open
0xF0000004 Not yet open error • After executing the Open method, execute the corresponding method.
0xF0000005 Initialization error • Exit the program and restart the personal computer.
Initialization of the object possessed internally in MX • Reinstall MX Component.
Component failed.
0xF0000006 Memory securing error • Exit the program and restart the personal computer.
Securing of MX Component internal memory failed. • Exit other programs and secure free memory area.
0xF0000007 Function non-support error • Can not use because the corresponding method is not supported.
The method does not support.
0xF1000001 Character code conversion error • Check the character string specified in the method.
Character code conversion (UNICODE to ASCII code or • The ASCII character string acquired from the programmable controller
ASCII code to UNICODE) failed. CPU is abnormal.
• Review the system, e.g. programmable controller CPU, module setting
and cable status.
• Retry the GetCpuType method.
0xF1000002 First I/O number error • Check the value of the first I/O number specified in the method.
The first I/O number specified is an unauthorized value. • Using the GPP function, check the programmable controller CPU
A matching first I/O number does not exist. parameters (I/O assignment).
0xF1000003 Buffer address error • Check the value of the buffer address specified in the method.
The buffer address specified is an unauthorized value.
The buffer address is outside the range.
13 ERROR CODES
0xF1000004 Buffer read size error • Perform reopen processing.
As a result of buffer read, the specified size could not be • Review the system, e.g. programmable controller CPU, module setting
acquired. and cable status.
• Retry.
• Exit the program.
0xF1000005 Size error • Check the size specified in the method.
The size specified in the read/write method is abnormal.
The read/write first number plus size exceeds the device or
buffer area.
0xF1000006 Operation error • Check the operation specifying value specified in the method.
The operation specified for remote operation is an
abnormal value.
0xF1000007 Clock data error • Check the clock data specified in the method.
The clock data is abnormal. • Set the correct clock data to the clock data of the programmable controller
CPU.
0xF1000008 Monitored device registration count excess • Register the device points between 1 and 20 in the EntryDeviceStatus
The number of device points registered in the method.
EntryDeviceStatus method was 0 or less.
The number of device points registered in the
13
EntryDeviceStatus method was more than 20.
0xF1000009 Monitored device data registration error • After making deregistration in the FreeDeviceStatus method, execute the
EntryDeviceStatus method again.
0xF1000010 Device status monitor processing failed to start. • Start/end the device status monitor processing again in the
Device status monitor processing failed to end. EntryDeviceStatus method.
0xF1000011 The VARIANT argument data type is wrong. • Reexamine the data type specified for the VARIANT argument.
• Check whether the array variable size is large enough.
• Check whether the data type specified in the corresponding method has
been set.
0xF1000012 The device status monitoring time interval is a value outside • Specify the device status monitoring time between 1 and 3600.
the range 1 second to 1 hour (1 to 3600).
0xF1000013 Already Connected error. • Execute the Connect method after executing the Disconnect method.
Connect was executed again after it was executed for the
same object.
0xF1000014 Invalid Telephone Number error. • Rectify the Telephone number and try to Connect again.
Characters other than "0123456789-*#" that are allowed for
telephone numbers are included.
0xF1000015 Exclusive Control Failure error. • In case if Connect/Disconnect method is being executed for any other
There was failure in the exclusive control process while object, execute the failed method (Connect/ Disconnect) again after the
executing the Connect and Disconnect method. completion of the Connect/ Disconnect method of that object.
• If the Connect/Disconnect process is in progress only for the self object,
perform the following.
 Exit the program.
 Restart the personal computer.
 Reinstall MX Component.
0xF1000016 While connecting to the telephone line error. • Try Connecting again after disconnecting the application that is using the
The telephone line is connected to some other application, telephone line.
other than the one using MX Component.
0xF1000017 Telephone line not connected error. • (When Connect method has failed)
Telephone line is not connected. Execute Connect again after executing Disconnect method.
Connect was executed and the telephone line was • (When method other than Connect has failed)
connected, but it got disconnected due to some reason. Execute Disconnect method, Execute Connect and connect to the
telephone line. After connecting, execute the method that failed once
again.
0xF1000018 No Telephone number error. • In case of program settings type, set the telephone No. to the property
The telephone No. is not set. ActDialNumber. (Set the telephone No. to the properties ActDialNumber
The telephone No. or call back No. is not set, if the and ActCallbackNumber, if the connection method is automatic (when
connection method is Automatic (when specifying the call specifying the call back No.), call back connection (when specifying the
back No.), call back connection (when specifying the telephone No.), or call back request (when specifying the number).)
number), or call back Request(when specifying the • In case of utility settings type, set the telephone No. using the wizard.
number). (Set the telephone No. and call back No. , if the connection method is
automatic (when specifying the call back No.), call back connection (when
specifying the telephone No.), or call back request (when specifying the
number).)
0xF1000019 Not Closed error. • Try Disconnect again after executing Close.
Disconnect was executed while in Open state.
13 ERROR CODES
0xF100001A Target telephone line connection mismatch error. • If you want to connect to a different telephone number, Execute
Connect was tried for a different telephone number using Disconnect with respect to the telephone line that is already connected
the port which is already connected to a telephone line. and executes Connect after it gets disconnected.
(When the method of connection is a callback reception, it • In case of connecting the telephone line with callback reception, use the
is considered that the telephone number is different from Connect of the connection method that is executed at the earliest in the
methods of connection in other than the callback reception.) same port as callback reception.
0xF100001B Control Type Mismatch error. • Execute Disconnect for the object currently connected to the telephone
An object, whose control type is different from that of the line and execute Connect once again after the telephone line gets
object already connected to the telephone line, tried to disconnected.
Connect.
0xF100001C Not Disconnected error. • Execute Disconnect for all the Connected objects. Try Disconnect again
When Disconnect method is executed for the object for the object that actually performed the telephone line connection.
connected to the telephone line, it is found that other
objects are in connected state.
0xF100001D Not Connected error. • Execute Open again after executing Connect.
Open was executed before Connect. Or, Disconnect was • Or execute Disconnect again after executing Connect.
executed.
0xF100001E Fatal error • Exit the program.
• Restart the personal computer.
0xF100001F Open time setting error • Check the telephone number and the port number.
There are some differences in telephone number and the • Check the Connect way.
port number settings used during Connect and Open.
There are some errors in Connect way.
0xF1000020 GX Simulator3 did not start error • Start GX Simulator3.
0xF1000021 No data error • Check the file.
The size of the specified file is '0'.
0xF1000022 File size error • Check the file.
The specified file size is too large.
0xF1000023 File input/output error • Check the file name.
An error occurred while saving a file.
0xF1000024 No file found error • End the search.
No more files not found.
0xF1000025 File name error • Check the file name.
The file name is too long.
Set a transfer source directory name within 188 bytes.
Set a transfer source file name within 318 bytes.
Set a transfer destination file name within 259 bytes.
0xF2000002 There is an error response from the target telephone. • Check the value of the properties set in case of program settings type.
Causes can be the following. • Check the contents of the detailed settings that were set using the wizard
Communication error has occurred. in case of utility settings type.
0xF2000003 Invalid data was received. • Retry.
Causes can be the following. • Check the communication device used at the other end.
Incorrect data packet is received due to noise.
0xF2000004 There is no response from the modem. • Check the status of the modem.
Causes can be the following. • Check the telephone number.
Abnormality in the modem • If the problem persists even after checking the above points, change the
Telephone number setting mistake value of the properties set (Properties such as
ActConnectionCDWaitTime etc. , which set the timing) in case of program
settings type and change the contents of the detailed settings that were
set using the wizard in case of utility settings type.
0xF2000005 There are chances that the line is not disconnected. • Check the telephone line.
0xF2000006 The PC modem did not receive the AT command. • Check the contents of the AT command.
Causes can be the following. • Check the status of the modem.
Invalid AT command was specified.
Abnormality in the modem.
0xF2000007 Modem did not respond properly to the standard escape • Check the modem.
command. • Confirm whether the value of the time-out is too small. ( 5000ms or more
is recommended. )
0xF2000009 Modem does not respond properly to the line Disconnect • Check the modem.
command.
13 ERROR CODES
0xF200000A Target did not receive the signal. • Check the Receive settings of the modem at the other end.
The Receive settings of the modem at the other end may be • Check if the other end is busy.
incorrect. • Check the telephone number.
The other end may be busy.
The telephone number may be incorrect.
0xF200000B Timeout reached for the call back receive waiting time. • Increase the call back receive waiting time
ActCallbackReceptionWaitingTimeOut and execute connect again.
0xF200000C Password of QJ71C24 units could not be resolved. • Set the password to ActPassword property and execute the failed method
again.
0xF2010001 The callback line disconnect wait time is other than 0 -180 • Check whether the callback line disconnect wait time is with in 0 - 180
Seconds. Seconds.
The callback execution delay time is other than 0 -1800 • Check whether the callback execution delay time is within 0 - 1800
Seconds. Seconds.
The telephone number is more than 62 characters. • Check whether the telephone number is less than or equal to 62
characters.
0xF2010002 QJ71C24 did not receive the specified connection method.
Causes can be the following.
• Check whether the settings of QJ71C24 and the MX Component are
matching.
13
Incorrect Connection method
Incorrect telephone number for Call back
0xF2010003 QJ71C24 does not permit the automatic connection (during • Check the settings of QJ71C24.
fixed Call back or when the number is specified.)
0xF2100005 There are chances that the line is not disconnected. • If there is no problem with the modem or the telephone line, change the
value of the properties set (Properties like ActConnectionCDWaitTime etc.
, which set the timing) in case of program settings type and change the
contents of the detailed settings that were set using the wizard in case of
utility settings type.
0xF2100006 Modem did not receive the startup command AT. • Change the settings of the property ActATCommand in case of program
settings type.
• Change the command AT that were set using the wizard in case of utility
settings type.
0xF2100007 The PC modem does not respond to the Escape command. • If there is no problem with the modem, change the value of the properties
set (Properties like ActConnectionCDWaitTime etc. , which set the timing)
in case of program settings type and change the contents of the detailed
settings that were set using the wizard in case of utility settings type.
0xF2100008 There was no response from the modem for the data sent • Change the value of the properties set (Properties such as
from the PC. ActConnectionCDWaitTime etc. , which set the timing) in case of program
0xF21000** There is no response from the modem. • Check the status of the modem.
Causes can be the following. • Check the telephone number.
Abnormality in the modem • If the problem persists even after checking the above points, change the
Telephone number setting mistake value of the properties set (Properties such as
ActConnectionCDWaitTime etc. , which set the timing) in case of program
0xF202**** There was a communication failure. • Check whether the cable is broken.
Following causes can be considered depending on the • Check whether the specified port is not supported.
status. • Check whether correct COM port is set.
Communication time over (Break in cable, the specified port • Check if the modem power is switched OFF.
not supported, mistake in specifying the COM port) • For detailed troubleshooting, please refer to the details of the error code
Modem's power is switched OFF. got after replacing the first four digits with "0x0180".
e.g. In case of "0xF202480B", please refer to the code "0x0180480B".
0xF3000001 Label error • Review the label name.
The label character string specified in the method is an • Start Label Utility, please check System label information.
unauthorized label character string.
0xF3000002 Label Service not started • Exit the program and restart the personal computer.
• Start Label Utility, please check System label information.
0xF3000003 MMS Service not started • Exit the program and restart the personal computer.
0xF3000004 The specified LabelSpace is currently being used and • Retry.
cannot be opened.
0xF3000005 Label data access timeout error • Retry.
• Reduce system label definition.
13 ERROR CODES
0xF3000006 MUTEX acquisition error • Exit the program and restart the personal computer.
Acquisition of MUTEX to exercise exclusive control failed.
0xF4000001 to 64-bit control error • Exit the program and restart the personal computer.
0xF400000F • Reinstall MX Component.
0xF4000010 to 64-bit control access error • Execute the Open method again after executing the Close method.
0xF4000012 • Check if 10 minutes or longer have passed since the DotUtlType64 control
was last accessed.
• Reduce the amount of data handled in a single process.
0xF4001001 Not yet open error After executing the Open method, execute the corresponding method.
0xF4001002 Already open error When changing the communication target CPU, execute the Open method
The Open method was executed in the open status. after performing Close.
0xF4001003 Registry search failed. • Exit the program and restart the personal computer.
0xFF000001 MX Component trial version error • Uninstall the trial version and install the commercial version, or reinstall
Expired MX Component trial version the trial version.
*1 For the method for increasing the minimum working set size of the personal computer, refer to the following:
MELSEC Data Link Library Reference Manual
• Error code for the robot controller
100 Number of ENQ retries is exceeded. • Take measures against noise
101
102 Number of NACK retries is exceeded.
103 The message is too long.
104 Reception time-out • Check the cable connection.
105 DSR signal was not detected.
106 The line was disconnected. • Check the cable connection.
• Open again.
107 Transmission time-out • Check the cable connection.
108 Sequence number is incorrect. • Take measures against noise
200 Included DLL was not found. • Reinstall MX Component.
13 ERROR CODES
13.2 Error Codes Returned by CPUs, Modules, and
Network Boards
This section explains the error codes returned by CPUs, modules, and network boards.
Error codes may not be returned as described in Page 615 Error code list.
Check Page 615 Considerations for confirming error codes firstly.
Error code list

If a CPU, module, or network board detected an error, any of the error codes indicated in the following table is returned.
The two upper bytes denote the error detection module, and the two lower bytes denote the error code returned by the error
detection module.
For error details, refer to the manual of CPU, module, or network board corresponds to the error code. 13
Error code Error detection module
0x01010000 to 0x0101FFFF *1,*2 Motion controller CPU
0x01070000 to 0x0107FFFF *1 CC-Link IE Controller Network board, MELSECNET/H board, CC-Link Ver.2 board
0x01090000 to 0x0109FFFF *1 FXCPU
0x010A0000 to 0x010AFFFF *1
QCPU (Q mode), QSCPU, RCPU, FX5CPU
0x010B0000 to 0x010BFFFF *1 Q series-compatible C24
0x010C0000 to 0x010CFFFF *1 Q series-compatible E71
0x010D0000 to 0x010DFFFF *1 PC CPU module
0x010F0000 to 0x010FFFFF *1 GOT
*1 Refer to "Point."
*2 The error codes are also described in the following section:
Page 588 Error Code List.
Considerations for confirming error codes

The following are the considerations for confirming the error codes returned by CPU, module, and network board.
■ Property setting error

If the used system configuration does not match the preset property values, the two upper bytes do not indicate the correct
error detection module.
For example, when the property values of FXCPU are set to ActCpuType for QCPU (Q mode), the two upper bytes may
indicate that the error detection module is FXCPU.
In such a case, perform the communication again after checking the system configuration and all preset property values.
When the ActUtlType control is used, check the settings of Communication Settings Utility.
■ When accessing another station

When accessing another station, the error code of the used relayed module (CC-Link IE Controller Network, MELSECNET/H,
CC-Link, Serial communication, Ethernet module) may be entered to the two lower bytes.
In such a case, the two upper bytes that indicate the error detection module may not always match the faulty module. Check
the system configuration, and check the manuals of the used CPU, relayed network module, and network board.
Label specification error

The following error code will be returned if an error related to labels in the CPU occurred such as; system label Ver.2 does not
exist, the information of system label Ver.2 is modified while reading/writing devices that are corresponding to the system label
Ver.2.
0x01802001 Label information error • When a system label is specified as a label, review the global label name assigned
to the system label name in Label Utility.
• Check if the global labels exist in the CPU.
13 ERROR CODES
13.2 Error Codes Returned by CPUs, Modules, and Network Boards 615
0x010A4000 to 0x010A4FFF For the errors and their corrective actions, refer to the following manual.

MELSEC iQ-R CPU Module User's Manual (Application)
13 ERROR CODES
616 13.2 Error Codes Returned by CPUs, Modules, and Network Boards
13.3 HRESULT Type Error Codes
Normally, the ActiveX control and the Act control return HRESULT type returned values.
When the custom interface is used, the returned value is equivalent to the returned value of method API.
When the dispatch interface is used, HRESULT type returned values can be acquired by performing the exception
processing.
The following table shows HRESULT type returned values of Act controls.
Returned value Terminatio Description
n status
S_OK Normal end The function processing is normally terminated.
S_FALSE Normal end The function processing (as ActiveX control) is normally terminated, but the operation (access to programmable
controller) failed.
E_POINTER Abnormal The pointer passed to the function is abnormal.
termination
E_OUTOFMEMORY Abnormal
termination
Memory reservation or object creation failed.
13
E_FAIL Abnormal An indefinite error occurred.
termination
If the exception processing to acquire the HRESULT type returned value is not performed, the dispatch
interface displays the error dialog box on the operating system level when E_POINTER (E_XXXXX defined
returned value) or the like is returned from the Act control.
13.4 Error Codes Displayed on Event Viewer

This section explains the error codes displayed on Windows Event Viewer by MX Component.
MX Component uses MMS (system label database) Service and Label Service to manage label information.
When an error occurs in Label Service, an error description is displayed on the system log in Event Viewer.
For errors regarding Label Service of MX Component, "MXLabelService" is displayed on the source field in Event Viewer.
The following table shows the errors and their corrective actions.
Event ID Error message Corrective action
3 MMS Service not started. • Wait for the completion of MMS (system label database) Service startup.
If MMS Service startup does not complete, exit the program and restart
the personal computer.
5 MXLabelService error.(%1,%2) • Exit the program and restart the personal computer.
please perform one of the followings. • Reinstall MX Component.
-Re-start Personal computer.
-Re-install the application and try again.
13 ERROR CODES
13.3 HRESULT Type Error Codes 617
APPENDIX
Appendix 1 Changes from Previous Version
This section shows the additions and changes with upgrade.
Version Item Description Reference
Version 5.000A Control • Controls for 64-bit are supported. 
• The DotSupportMsg control is integrated into the
ActSupportMsg control.
Function Functions for 64-bit are supported. Page 423 FUNCTIONS
Operating environment Only Windows 10 is supported.  MX Component
Version 5 Installation
Development software Only the following software is supported:
Instructions
• Visual Studio 2019
Page 24 Operating
• Microsoft Excel 2019
Environment
• Microsoft Access 2019
Product to be discontinued Products to be discontinued are no longer supported. 
Communication type The following Communication types are no longer supported. Page 25 Supported
• Q series bus communication Communication Routes
• GX Simulator communication
• Modem communication
Installation folder The default installation folder is changed from "C:\MELSEC" to 
"C:\Program Files\MELSOFT."
Manual Available for e-Manual Viewer 
Version 5.002C Module FX5-ENET and FX5-ENET/IP are supported. Page 30 Module list
Communication route The following communication routes are supported: Page 210 Ethernet
• Ethernet communication when a connection target CPU is an Communication, Page
FX5CPU (using an Ethernet adapter) 340 GOT Transparent
• GOT Transparent Communication when a connection target Communication
CPU is an FX5CPU (using an Ethernet adapter)
Development software The following software is supported:  MX Component
• Microsoft Excel for Microsoft 365 Version 5 Installation
• Microsoft Access for Microsoft 365 Instructions
Page 24 Operating
Environment
APPX
618 Appendix 1 Changes from Previous Version
Appendix 2 Concept of Routing Parameters
The routing function is used by a station of a programmable controller CPU in a multi-level system to perform the transient
transmission to a 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

■ Source and relayed station of a programmable controller CPU settings
The routing parameters must be set to the request source and relayed station of a 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 CPU 1Ns3 which performs transient transmission, to the programmable controller
CPUs 1Ns4 and 2Mp1 which serve as bridges, and to the programmable controller CPUs 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.
Request
source
1Mp1 1N2 1Ns3 3Mp1 3Ns2
Network No.1 Network No.3 A

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.
■ "Target network No." settings

Up to 16 "transfer target network numbers" can be set to a programmable controller CPU.
16 different network numbers allow a host station to be a request source or other stations to be accessed via the host station.
APPX
Appendix 2 Concept of Routing Parameters 619
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 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
620 Appendix 2 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 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 a 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.
Set the routing parameter by referring the following manual:
MELSEC-Q/L Ethernet Interface Module User's Manual (Application)
MELSEC iQ-R CPU Module User's Manual (Application)
APPX
Appendix 2 Concept of Routing Parameters 621
Appendix 3 RS-232 Cable Wiring Examples for Serial
Communication
For 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)
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

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
622 Appendix 3 RS-232 Cable Wiring Examples for Serial Communication
For FX Series
The following shows the example of wiring a personal computer and the FX extended port.
Connecting a personal computer and FX-485PC-IF converter with a RS-232 cable
Personal Computer Side FX-485PC-IF side

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
Connecting the FX-485PC-IF converter and the FX extended port (2-pair wiring)
FX3G-485-BD
FX-485PC-IF FX3U-485-BD FX-485PC-IF FX-485PC-IF
SDA SDA SDA SDA

Ò R R Ò
SDB SDB SDB SDB
RDA RDA RDA RDA

Ò R R Ò
RDB RDB RDB RDB A
LINK SG SG LINK SG LINK SG
FG Ô FG Ô
Ó
Grounding
No. Description
 It 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 and FX3U-485-BD, terminal resistances are built in.
Set the terminal resistance by the setting switch.
 Ground the shields connected to FX3G-485-BD and FX3U-485-BD.
 Connect the FG terminal to the ground terminal of the grounded programmable controller.
APPX
Appendix 3 RS-232 Cable Wiring Examples for Serial Communication 623
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
1 MELSECNET/H module controlled by Ò
(Network number: 1, station number: 1)
MELSECNET/H 2 MELSECNET/H module controlled by Ó
2’ MELSECNET/H module controlled by Ó’
APPX
624 Appendix 4 Multi-CPU System
Appendix 5 The Number of Mountable Network
Modules for Q00UJCPU, Q00UCPU, and
Q01UCPU
The following shows the number of mountable network modules when using Q00UJCPU, Q00UCPU, and Q01UCPU.
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
A
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
Appendix 5 The Number of Mountable Network Modules for Q00UJCPU, Q00UCPU, and Q01UCPU 625
Appendix 6 Compatibility with Redundant CPU
This section explains the compatibility of MX Component with a redundant CPU.
For RnPCPU (redundant mode) and RnPSFCPU
Redundant CPU specification

In redundant CPU specification in iQ-R series, only "Not specified" can be selected.
When selecting "Not specified," MX Component connects to the connection target programmable controller CPU as before.
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.
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.
Special relay 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.
Special relay 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
626 Appendix 6 Compatibility with Redundant CPU
For QnPRH
Redundant CPU specification

In redundant CPU specification, select either "Control system" or "Not specified" to access the compatible Redundant CPU.
When selecting "Control system," MX Component connects to the control system and continue to access the control system
in response to system switching.
When selecting "Not specified," MX Component connects to the connection target programmable controller CPU as before.
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.
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.
Special relay 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.
Special relay Control system Standby system System not determined.(At the
time of TRK.CABLE
ERR.(Error code: 6120)
occurrence)
A
SM1515 (Control system status) ON OFF OFF
SM1516 (Standby system status) OFF ON OFF
APPX
Appendix 6 Compatibility with Redundant CPU 627
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.
MX Component
Connection to control system
Control system Standby system
Tracking cable
MX Component
Connection to control system via standby system
Standby system Control system
Tracking cable
APPX
■ 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
Ethernet
Tracking cable
MX Component
Connection to control system via standby system
Tracking cable
A
Ex.
When communication error occurs
MX Component
Ethernet
Communication
error
Tracking cable
MX Component
Connection to control system via network
Tracking cable
APPX
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.
APPX
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 632 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 632 Examples of access by route switch A
executed. When standby system error occurs
ON Either one is other than 0 Since another system error occurred or a system Page 632 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
■ 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
Ethernet
Communication
error
Tracking cable
MX Component
Tracking cable
Ex.
When standby system error occurs
MX Component
Ethernet
Standby
system fault
Tracking cable
MX Component
Ethernet
Tracking cable
APPX
• 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 and remove the communication disturbance.
Page 631 How to check whether route switch occurred or not
Page 632 Examples of access by route switch
Special relays and special registers for estimating route switch occurrence
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.)
• Turn OFF after recovery from error.
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.
A
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 • Turn 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
Combination table
Communications via Q series redundant type extension base unit (Q65WRB) are supported.
The following table shows the supported/unsupported combinations.
Product name Module 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   
*1
CC-Link module QJ61BT11N   
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.
APPX
Appendix 7 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 7 Character Strings that cannot be Used for Label Names 635
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
636 Appendix 7 Character Strings that cannot be Used for Label Names
Appendix 8 Performance
This section explains the performances in the following system configuration.
OS : Windows 10 Enterprise (64-bit version)

CPU : Intel Core i5-4590(3.30GHz)
R08CPU Memory : 16GB
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 words (1 label) 12.3 227.3 17.3 182.0 19.8
12288 words (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 words (1 label) 17.6 232.0 22.6 189.9 24.6
12288 words (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 words (128 labels) 24.1 1802.7 38.2 2381.9 45.3
256 words (256 labels) 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 words (128 labels) 30.5 1817.0 41.8 2334.5 47.0
256 words (256 labels) 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 Memory usage amount [KB]
system label Ver.1 system label Ver.2
Batch read 1000 labels (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 8 Performance 637
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 Memory usage amount [KB]
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
638 Appendix 8 Performance
Performance of the Label Utility
Time performance
This explains time performance of the Label Utility.
Processing Type of system label Processing time (s)
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
Import System label of structure type 0.9 0.6
Export System label of 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 Memory usage amount [KB]
System label undefined 4108 4316
System label of structure type 8608 7500
System label other than structure type 12872 12256
A
APPX
Appendix 8 Performance 639
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 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
640 Appendix 8 Performance
Appendix 9 Installing a USB Driver
To communicate with a programmable controller CPU via USB, installing a USB driver is required.
When more than one MELSOFT product is installed, the USB driver is installed in the folder to which the first
MELSOFT product is installed.
Example: C:\Program Files\MELSOFT\Easysocket\USBDrivers
If 'Easysocket\USBDrivers' does not exist, search for 'USBDrivers' in the Windows explorer.
Installing a USB driver

The following explains the installation procedure of a USB driver.
Operating procedure
1. Connect a personal computer and a programmable controller CPU with a USB cable, and turn the power of the
programmable controller ON.
2. Select [Control Panel]  [System and Security]  [Administrative Tools]  [Computer Management]  [Device
Manager] from Windows Start. Right-click "Unknown device" and click "Update Driver Software."
3. Select "Browse my computer for driver software" on the "Update Driver Software" screen, and specify
'Easysocket\USBDrivers' in the folder where MX Component Version 5 is installed on the next screen.
The installation succeeded if "MITSUBISHI Easysocket Driver" is displayed on "Universal Serial Bus controllers."
APPX
Appendix 9 Installing a USB Driver 641
Appendix 10 Programing Examples for Monitoring
Word Device Status
This section explains the programming examples to monitor word devices for negative values using the EntryDeviceStatus
function.
When using Visual Basic .NET

The following is a programming example to monitor D0 for -10, D1 for 0, and D2 for 10 using Visual Basic .NET.
Dim szDevice As String 'Checked device list

Dim lInputData(2) As Long 'Set value
Dim lEntryData(2) As Long 'Value set to argument of EntryDeviceStatus
Dim lReturnCode As Long 'Returned value to EntryDeviceStatus
Dim lCount As Long 'Loop counter
'Sets D0, D1 and D2 to the checked device list.
szDevice = "D0" + vbLf + "D1" + vbLf + "D2"
'Sets the checked device value "-10" for D0.
lInputData(0) = -10
'Sets the checked device value "0" for D1.
lInputData(1) = 0
'Sets the checked device value "10" for D2.
lInputData(2) = 10
'If the set value is negative, stores "0"s into the upper 2 bytes
'for conversion into the value to be set to EntryDeviceStatus.
'Loops through the number of device points.
For lCount = 0 To 2
'If the set value is negative
If lInputData(lCount) < 0 Then
'Masks with 65535 (0000FFFF[hex]) to store "0"s into upper 2 bytes.
lEntryData(lCount) = lInputData(lCount) And 65535
Else
'If the set value is positive, assigns the value as-is to lEntryData.
lEntryData(lCount) = lInputData(lCount)
End If
Next
'Executes EntryDeviceStatus.
lReturnCode = AxActUtlType1.EntryDeviceStatus(szDevice, 3, 5, lEntryData(0))
■ When lData = -1
Private Sub AxActUtlType1_OnDeviceStatus(ByVal szDevice As String, ByVal lData As Long, ByVal lReturnCode As Long)
Dim lCheckData As Long 'Value set to EntryDeviceStatus (value before 0s are stored into the upper 2 bytes)
'If the device value whose condition was established is a WORD type negative value (greater than 32767 (7FFF[Hex])
If lData > 32767 Then
'Since "0"s are stored in the upper 2 bytes, the device value is ORed with FFFF0000[Hex] to convert it into a LONG
'type negative value.
lCheckData = lData Or &HFFFF0000
Else
'If the device value whose condition was established is positive, assigns the value as-is to lCheckData.
lCheckData = lData
End If
End Sub
APPX
642 Appendix 10 Programing Examples for Monitoring Word Device Status
When using Visual C++
The following is a programming example to monitor D0 for -10, D1 for 0, and D2 for 10 using Visual C++.
CString szDevice; //Checked device list

LONG lInputData[3]; //Set value
LONG lEntryData[3]; //Value set to argument of EntryDeviceStatus
LONG lReturnCode; //Returned value to EntryDeviceStatus
LONG lCount; //Loop counter
//Sets D0, D1 and D2 to the checked device list.
szDevice = "D0\nD1\nD2";
// Sets the checked device value "-10" for D0.
lInputData[0] = -10;
// Sets the checked device value "0" for D1.
lInputData[1] = 0;
lInputData[2] = 10;
//If the set value is negative, stores "0"s into the upper 2 bytes
//for conversion into the value to be set to EntryDeviceStatus.
//Loops through the number of device points.
for(lCount = 0;lCount<=2; lCount++) {
//If the set value is negative
if (lInputData[lCount] < 0 ){
//Masks with 65535 (0000FFFF[hex]) to store "0"s into upper 2 bytes.
lEntryData[lCount] = lInputData[lCount] & 0x0000FFFF;
}else{
//If the set value is positive, assigns the value as-is to lEntryData.
lEntryData[lCount] = lInputData[lCount];
}
}
//Executes EntryDeviceStatus.
lReturnCode = m_Actutltype.EntryDeviceStatus(szDevice,3,5,lEntryData);
■ When lData = -1
void CSampleDlg::OnDeviceStatusActutltype1(LPCTSTR szDevice, long lData, long lReturnCode)
{
LONG lCheckData; //Value set to EntryDeviceStatus
//If the device value whose condition was established is a WORD type negative value A
//greater than 32767 (7FFF[Hex])
if(lData > 0x7FFF){
//Since "0"s are stored in the upper 2 bytes, the device value is ORed
//with FFFF0000[Hex] to convert it into a LONG type negative value.
lCheckData = lData | 0xFFFF0000;
}else{
//If the device value whose condition was established is positive,
//assigns the value as-is to lCheckData.
lCheckData = lData;
}
}
APPX
Appendix 10 Programing Examples for Monitoring Word Device Status 643
When using Visual C#
The following is a programming example to monitor D0 for -10, D1 for 0, and D2 for 10 using Visual C#.
String szDevice; //Checked device list

int[] iInputData = new int[3]; //Set value
int[] iEntryData = new int[3]; //Value set to argument of EntryDeviceStatus
int iReturnCode; //Returned value to EntryDeviceStatus
int iCount; //Loop counter
//Sets D0, D1 and D2 to the checked device list.
szDevice = "D0\nD1\nD2";
// Sets the checked device value "-10" for D0.
iInputData[0] = -10;
iInputData[1] = 0;
iInputData[2] = 10;
//If the set value is negative, stores "0"s into the upper 2 bytes
//for conversion into the value to be set to EntryDeviceStatus.
//Loops through the number of device points.
for(iCount = 0;iCount<=2; iCount++) {
//If the set value is negative
if (iInputData[iCount] < 0 ){
//Masks with 65535 (0000FFFF[hex]) to store "0"s into upper 2 bytes.
iEntryData[iCount] = iInputData[iCount] & 0x0000FFFF;
}else{
//If the set value is positive, assigns the value as-is to lEntryData.
iEntryData[iCount] = iInputData[iCount];
}
}
axActUtlType1.ActLogicalStationNumber = 0;
iReturnCode = axActUtlType1.Open();
//Executes EntryDeviceStatus.
iReturnCode = axActUtlType1.EntryDeviceStatus(szDevice, 3, 5, ref iEntryData[0]);
APPX
644 Appendix 10 Programing Examples for Monitoring Word Device Status
Appendix 11 Time-Out Periods
In MX Component, a time-out may occur at the period different from the value set to the ActTimeOut property in the Act
control.
This section explains the time-out periods in various status.
Communication retries at time-out error occurrence

If a time-out error occurs during communication, the time-out processing may be repeated for a maximum of three times in the
Act control.
At that time, the process takes a maximum of three times longer period than the set time-out value which is a period until the
time-out occurrence.
Communication retries at receive data error occurrence

If a receive data error occurs during communication, send/receive retry processing may be repeated for a maximum of three
times in the Act control.
At that time, the process takes a maximum of three times longer period than the set time-out value which is a period until the
normal or abnormal termination of the function.
Time-out errors at fixed time in the Act control

MX Component performs communication to check whether a personal computer and a programmable controller system are
connected normally before executing the Open function.
When performing the above communication, the fixed time-out period (1000 ms to 4500 ms) in the Act control is used.
Note that if an error occurs during the above communication, an error other than the time-out error may occur.
APPX
Appendix 11 Time-Out Periods 645
Appendix 12 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 an installer

Some policies of [User Account Control] in the local security policy may not be installed properly.
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 an 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 an installer cannot start properly.
For programmable controller CPU

■ When performing USB communication
A communication error may occur and it may not be recovered if connecting and disconnecting a USB cable, resetting the a
programmable controller CPU, or turning the power ON or OFF is performed frequently during communication with a
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 communication.)
■ Clock data of a programmable controller CPU

• For QCPUs (Q mode), LCPUs, and FXCPUs, 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.
• Note that an error for transfer time occurs in the time setting.
For when using Ethernet modules

■ Resetting a programmable controller CPU during TCP/IP connection establishment
When resetting a 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.
■ Target existence check starting interval of an Ethernet module

If the close processing (Close) is executed from a personal computer, an 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 a 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.)
APPX
646 Appendix 12 Troubleshooting
■ Replacement of Ethernet modules
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.)
■ Simultaneous access when using a 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 an 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
Ö Without setting
mode) E71 E71
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.
A
APPX
Appendix 12 Troubleshooting 647
■ Ethernet communication
• The communication line is disconnected if a CPU becomes faulty or an 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.
APPX
For 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 an application.
2 When the error cannot be solved by the above • Set a port number different from one used for another application to a personal computer side.
No.1 • Check whether the first character of the specified IP address is not '0.'
When setting the first character to '0,' the value of the target octet is processed as octal number.
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 Settings Utility"
• Occurrence frequency and procedure for a symptom
For saving the setting of Communication Settings Utility

■ Errors which occur when saving the setting with Communication Settings Utility and
corrective actions
Error message Corrective action Considerations
Updating the system information data failed. Select [Communication Settings Utility] from the When Label Utility is executed, the status is
• There is a possibility without the operation start 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.
When a header file is not created properly at the time of pasting a A

control to a form with Visual C++
A header file may not be created properly when pasting a control to a form with Visual C++ depending on the version of Visual
Studio 2019.
In this case, overwrite the created file with the following header files stored in "[User-specified folder]\Act\Include."
Control to be used Header file
ActUtlType actutltype.h
ActUtlDataLogging actutldatalogging.h
ActSupportMsg actsupportmsg.h
ActProgType actprogtype.h
ActProgDataLogging actprogdatalogging.h
APPX
When an error occurs in the setting for using controls in Visual
Studio .NET
An error may occur in the setting for using controls.
For the corrective actions, refer to the following 'Point'.
When creating an application using .NET Framework 4, .NET Framework 4.5, or .NET Framework 4.6 (The
following is an example for .NET Framework 4.) Add an application configuration file with the following
elements (app.config) to the folder which contains the .exe file of the application.
For details, refer to Visual Studio Help.
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0"/>
</startup>
</configuration>
When pasting a control to a form
• When using Visual C++ .NET/Visual Basic .NET/Visual C# projects

The following library is added to "References":
For ActProgType: ActProgTypeLib
For ActUtlType: ActUtlTypeLib
For ActSupportMsg: ActSupportMsgLib
For DotUtlType: MITSUBISHI.Component.DotUtlType
For DotSupportMsg: MITSUBISHI.Component.DotSupportMsg
Set "False" for "Embed Interop Types" in the property of each library.
APPX
When a link error occurs in creating a user program in Visual C++
A link error occurs if both '.NET control' (DotUtlType) and 'Act control' (ActUtlType) are used at the same time by pasting them
in a single program.
The corrective actions are shown below.
Procedure for adding an application configuration file

1. Select [Project]  [Add New Item].
2. Select [Installed]  [Visual C++]  [Utility].
3. Select "Configuration file (app.config)" and click the [Add] button.
4. Write the following code to the application configuration file (app.config).
<?xml version="1.0" encoding="utf-8" ?>

<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0"/>
</startup>
</configuration>
5. Select [Project]  [Properties].
6. Select [Configuration Properties]  [Build Events]  [Post-Build Event].
7. Set "copy app.config"$(TargetPath).config"" for "Command Line."
Procedure for pasting a control

For the corrective actions, refer to the following 'Point'.
When using both .NET control (DotUtlType) and Act control (ActUtlType) by pasting them into a program,
perform the following operations by selecting [Project]  [Properties] from Solution Explorer. A
Select [Common Properties]  [Framework and references].
Select "ActUtlTypeLib" from "Name" in "References," and change the setting of "Reference Assembly
Output" under "Build Properties" to "False."
Select "Interop.ActUtlTypeLib.1.0" from "Name" in "References," and change the setting of "Reference
Assembly Output" under "Build Properties" to "False."
Click the [OK] button to reflect the change of the setting.
APPX
When an unstart error occurs during communication with GX
Simulator3
If GX Simulator3 communication is performed by importing the setting of MX Component Version 4.15R or earlier, GX
Simulator3 unstart error (0xF1000020) occurs.
The corrective actions are shown below.
When using a utility setting type control

Calculate the port number of the simulator using the average value '5500', and set the value using Communication Settings
Utility again.
• PortNumber=5500 + System No.  10 + Unit No. (For System No.=1 and Unit No.=1, 5511=5500+1  10+1)
When using a program setting type control

Calculate the port number of the simulator using the average value '5500', and change the setting to pass the value to the
property of the control.
• PortNumber=5500 + System No.  10 + Unit No. (For System No.=1 and Unit No.=1, 5511=5500+1  10+1)
APPX
Appendix 13 Differences with previous version of MX
Component
This section explains the differences between MX Component Version 4 and Version 5.
For the functions added or changed in version 5.000A and later, refer to the following:
Page 618 Changes from Previous Version
Comparison with MX Component Version 4
Engineering environment
The following table shows the differences of the development environment between MX Component Version 4 and Version 5.
Item MX Component Version 4 MX Component Version 5
OS Windows Microsoft Windows XP Microsoft Windows 10
Microsoft Windows Vista Microsoft Windows 10 IoT Enterprise 2016 LTSB
Microsoft Windows 7
Microsoft Windows 8
Microsoft Windows 8.1
Microsoft Windows 10
Programming language Visual Basic.Net Microsoft Visual Studio 2005 Visual Basic Microsoft Visual Studio 2019 Visual Basic
Microsoft Visual Studio 2008 Visual Basic
Visual C++ Microsoft Visual Studio 2005 Visual C++ Microsoft Visual Studio 2019 Visual C++
Microsoft Visual Studio 2008 Visual C++
Microsoft Visual Studio 2015 Visual C++ A
Visual C# Microsoft Visual Studio 2005 Visual C# Microsoft Visual Studio 2019 Visual C#
Microsoft Visual Studio 2008 Visual C#
Microsoft Visual Studio 2010Visual C#
VBA Microsoft Excel 2003 Microsoft Excel 2019 (32-bit version/64-bit version)
Microsoft Excel 2007 Microsoft Excel for Microsoft 365 (64-bit version)
Microsoft Excel 2010 (32-bit version)
Microsoft Access 2003 Microsoft Access 2019 (32-bit version/64-bit
Microsoft Access 2007 version)
Microsoft Access 2010 (32-bit version) Microsoft Access for Microsoft 365 (64-bit version)
Microsoft Access 2013 (32-bit version)
VBScript Text editor and commercially available HTML tool Not supported
APPX
Appendix 13 Differences with previous version of MX Component 653
Communication route
The following table shows the differences of the communication routes between MX Component Version 4 and Version 5.
Whether the communication can be established or not differs depending on the operating system to be used.
In addition, restrictions on versions may apply even for the applicable boards and drivers.
• Page 25 Supported Communication Routes
• Page 30 Module list
: Available, : Not available
Communication route MX Component Version 4*1 MX Component Version 5

Serial communication  
Ethernet communication  
CPU COM communication  
CPU USB communication  
MELSECNET/H communication  *2*3
CC-Link IE Controller Network communication  *2*3
CC-Link IE Field Network communication  *2*3
CC-Link communication  *2*3
CC-Link system RS-232 interface 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  
GOT gateway device communication  
GOT transparent communication  
Inverter COM communication  
Inverter USB communication  
Robot controller COM communication  *3
Robot controller USB communication  *3
Robot controller Ethernet communication  *3
*1 Whether the communication can be established or not differs depending on the operating system to be used. (MX Component
Version 4 Operating Manual)
*2 Not supported when using Windows 10 Education.
*3 64-bit version is not supported when using Windows 10 IoT Enterprise 2016 LTSB.
APPX
654 Appendix 13 Differences with previous version of MX Component
Applicable models
The following table shows the differences of the applicable models between MX Component Version 4 and Version 5.
Category Series MX Component Version 4 MX Component Version 5

CPU RCPU  
RCCPU  
R motion CPU  
LHCPU  
FX5CPU  
QCPU (Q mode)  *1
LCPU  
QCCPU  
QSCPU  
Q motion CPU  *2
FXCPU (FX3CPU)*3  
FXCPU (FX0CPU to FXUCPU)*4  
GOT GOT1000  
GOT2000  
Inverter A800  
Robot controller CR750  
CRnD-700  
Simulator GX Simulator  
GX Simulator2  
GX Simulator3  
MT Simulator2  
*1 Basic model QCPUs, high performance model QCPUs, and process CPUs are not supported.
*2 Q172CPU, Q173CPU, Q172HCPU, and Q173HCPU are not supported. A
*3 FX3SCPU, FX3GCPU, FX3GCCPU, FX3UCPU, FX3UCCPU
*4 FX0CPU, FX0SCPU, FX0NCPU, FX1CPU, FX1NCPU, FX1NCCPU, FX1SCPU, FXUCPU, FX2CCPU, FX2NCPU, FX2NCCPU
Controls
The following table shows differences of controls.
MX Component Version 4 MX Component Version 5
32-bit 64-bit*2
ActUtlType ActUtlType ActUtlType64
ActProgType ActProgType ActProgType64
ActSupportMsg ActSupportMsg ActSupportMsg64
ActUtlDataLogging ActUtlDataLogging ActUtlDataLogging64
ActProgDataLogging ActProgDataLogging ActProgDataLogging64
DotUtlType DotUtlType DotUtlType64
DotSupportMsg*1 ActSupportMsg ActSupportMsg64
ActMLUtlType Not supported because VBScript is not supported.
ActMLProgType
ActMLSupportMsg
*1 Controls of the DotSupportMsg are integrated into the ActSupportMsg in Version 5.000A.
*2 The method to paste this control to a form cannot be used.
APPX
Compatibility
The programs and communication settings of MX Component Version 4 can be utilized in MX Component Version 5.
For the programs and communication settings which are not supported in MX Component Version 5, use MX
Component Version 4.
Note that MX Component Version 4 and MX Component Version 5 cannot be installed on the same personal
computer.
Install MX Component Version 4 after uninstalling MX Component Version 5.
Utilizing programs
Controls of MX Component Version 4 are included in MX Component Version 5.
Therefore, programs created with the controls of MX Component Version 4 can be used in MX Component Version 5.
Utilizing communication settings

Import the setting file (.ACT file) of MX Component Version 4 using Communication Settings Utility of MX Component Version
5. (Page 60 Importing)
The settings can be used for controls of both MX Component Version 4 and MX Component Version 5.
■ Exporting/importing
The communication settings and system labels of MX Component Version 4 can be utilized in MX Component Version 5 by
using exporting/importing of communication settings.
The following is a correspondence table for the communication setting and system label.
Exporting Importing
MX Component Version 4 MX Component Version 5
MX Component Version 4  
MX Component Version 5  
Using a control
■ When using control in 32-bit
When using the DotSupportMsg control of MX Component Version 4 in MX Component Version 5, replace it with the
ActSupportMsg control.
Controls of MX Component Version 4 other than the above can be used as it is in MX Component Version 5.
■ When using control in 64-bit

• When using a control of MX Component Version 4 by creating an object
A control can be used in MX Component Version 5 by replacing it with a control for 64-bit version.
Ex.
DotSupportMsg  ActSupportMsg64
• When using a control of MX Component Version 4 by pasting it to a form
When using a control in VBA, the control can be used in MX Component Version 5 by replacing it with a control for 64-bit
version.
When using the control in a language other than VBA, the control cannot be used by pasting to a form in MX Component
Version 5.
Use the control by creating an object. (Page 44 When using a control by creating an object, Page 47 When using a
control by creating an object)
APPX
656 Appendix 13 Differences with previous version of MX Component
MEMO
APPX
FUNCTION INDEX
C 440,519
WriteDeviceRandom2(Writing devices randomly) . . . .
Close(Closing communication line) . . . 430,495,503 486,564
D
Dispose(release memory) . . . . . . . . . . . . . . . . 575
E
EntryDeviceStatus(Registering devices for status
monitoring) . . . . . . . . . . . . . . . . . . . . . . . . 469,542
F
FreeDeviceStatus(Deregistering devices for status
monitoring) . . . . . . . . . . . . . . . . . . . . . . . . 473,545
G
GetClockData(Reading clock data) . . . . . . . 455,536
GetCpuType(Reading programmable controller CPU
model) . . . . . . . . . . . . . . . . . . . . . . . . . . . 463,540
GetDevice(Acquiring device data) . . . . . . . . 445,529
GetDevice2(Acquiring device data) . . . . . . . 491,573
GetErrorMessage(Acquiring error description and
corrective action) . . . . . . . . . . . . . . . . . . . . . . 493
GetFile(Transferring logging files) . . . . . . . . . . . 501
O
OnDeviceStatus(Event notification) . . . . . . . 474,546
Open(Opening communication line) . . 429,494,502
R
ReadBuffer(Reading data from buffer memory) . . . .
447,532
ReadClose(Ending the search) . . . . . . . . . . . . . 500
ReadDeviceBlock(Reading devices in batch) 431,504
ReadDeviceBlock2(Reading devices in batch) . . . . .
477,548
ReadDeviceRandom(Reading devices randomly) . . .
437,512
ReadDeviceRandom2(Reading devices randomly) . .
483,557
ReadFirstFile(Searching for a file/directory) . . . . 496
ReadNextFile(Searching for a file/directory) . . . . 498
S
SetClockData(Writing clock data) . . . . . . . . 459,538
SetCpuStatus(Remote control) . . . . . . . . . . 466,541
SetDevice(Set device data) . . . . . . . . . . . . 443,526
SetDevice2(Set device data) . . . . . . . . . . . 489,570
W
WriteBuffer(Writing data to buffer memory) . 451,534
WriteDeviceBlock(Writing devices in batch) . 434,508
WriteDeviceBlock2(Writing devices in batch) 480,552
WriteDeviceRandom(Writing devices randomly) . . . .
658
MEMO
659
REVISIONS
*The manual number is given on the bottom left of the back cover.
Revision date *Manual number Description
April 2021 SH(NA)-082395ENG-A First edition
November 2021 SH(NA)-082395ENG-B ■Added or modified parts
GENERIC TERMS AND ABBREVIATIONS, Section 2.1, Section 2.4, Section 5.1, Section 9.1,
Section 9.2, Section 10.2, Section 10.14, Section 11.2, Chapter 12, Section 13.1, Appendix 1,
Appendix 12, Appendix 13, TRADEMARKS
March 2022 SH(NA)-082395ENG-C ■Added or modified parts
Section 2.1, Appendix 1, Appendix 13
Japanese manual number: SH-082394-C

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.
 2021 MITSUBISHI ELECTRIC CORPORATION
660
WARRANTY
Please confirm the following product warranty details before using this product.
1. Gratis Warranty Term and Gratis Warranty Range
If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product
within the gratis warranty term, the product shall be repaired at no cost via the sales representative or Mitsubishi Service
Company.
However, if repairs are required onsite at domestic or overseas location, expenses to send an engineer will be solely at
the customer's discretion. Mitsubishi shall not be held responsible for any re-commissioning, maintenance, or testing
on-site that involves replacement of the failed module.
[Gratis Warranty Term]
The gratis warranty term of the product shall be for one year after the date of purchase or delivery to a designated place.
Note that after manufacture and shipment from Mitsubishi, the maximum distribution period shall be six (6) months, and
the longest gratis warranty term after manufacturing shall be eighteen (18) months. The gratis warranty term of repair
parts shall not exceed the gratis warranty term before repairs.
[Gratis Warranty Range]
(1) The range shall be limited to normal use within the usage state, usage methods and usage environment, etc., which
follow the conditions and precautions, etc., given in the instruction manual, user's manual and caution labels on the
product.
(2) Even within the gratis warranty term, repairs shall be charged for in the following cases.
1. Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure caused
by the user's hardware or software design.
2. Failure caused by unapproved modifications, etc., to the product by the user.
3. When the Mitsubishi product is assembled into a user's device, Failure that could have been avoided if functions
or structures, judged as necessary in the legal safety measures the user's device is subject to or as necessary by
industry standards, had been provided.
4. Failure that could have been avoided if consumable parts (battery, backlight, fuse, etc.) designated in the
instruction manual had been correctly serviced or replaced.
5. Failure caused by external irresistible forces such as fires or abnormal voltages, and Failure caused by force
majeure such as earthquakes, lightning, wind and water damage.
6. Failure caused by reasons unpredictable by scientific technology standards at time of shipment from Mitsubishi.
7. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.
2. Onerous repair term after discontinuation of production
(1) Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is discontinued.
Discontinuation of production shall be notified with Mitsubishi Technical Bulletins, etc.
(2) Product supply (including repair parts) is not available after production is discontinued.
3. Overseas service
Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at each FA
Center may differ.
4. Exclusion of loss in opportunity and secondary loss from warranty liability
Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation to:
(1) Damages caused by any cause found not to be the responsibility of Mitsubishi.
(2) Loss in opportunity, lost profits incurred to the user by Failures of Mitsubishi products.
(3) Special damages and secondary damages whether foreseeable or not, compensation for accidents, and
compensation for damages to products other than Mitsubishi products.
(4) Replacement by the user, maintenance of on-site equipment, start-up test run and other tasks.
5. Changes in product specifications
The specifications given in the catalogs, manuals or technical documents are subject to change without prior notice.
661
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 .NET, 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.
662
SH(NA)-082395ENG-C(2203)
MODEL:MXCV5-R-E
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.

SH 082395 Engc

Uploaded by

Copyright:

Available Formats

SH 082395 Engc

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SH 082395 Engc

Uploaded by

Copyright:

Available Formats

MX Component Version 5

Indicates that incorrect handling may cause hazardous conditions, resulting in

Indicates that incorrect handling may cause hazardous conditions, resulting in

PART 1 FUNDAMENTALS AND CREATING PROCEDURE

CHAPTER 1 FUNDAMENTALS OF MX Component 16

CHAPTER 2 SYSTEM CONFIGURATIONS 24

CHAPTER 3 USER APPLICATION CREATING PROCEDURES 37

CHAPTER 4 ADDING CONTROLS TO USER PROGRAM 40

CHAPTER 5 COMMUNICATION SETTING 52

CHAPTER 6 COMMUNICATION SETTING EXAMPLES (UTILITY SETTING TYPE) 66

CHAPTER 7 PROGRAMMING 111

PART 2 DETAILED SPECIFICATIONS OF PROGRAMS

CHAPTER 8 ACCESSIBLE DEVICES AND DEVICE TYPES 149

CHAPTER 9 PROPERTIES OF CONTROLS 181

CHAPTER 10 PROPERTY SETTINGS OF COMMUNICATION ROUTES 192

CHAPTER 11 FUNCTIONS 423

CHAPTER 12 SAMPLE PROGRAMS 576

CHAPTER 13 ERROR CODES 588

FUNCTION INDEX 658

This part explains the fundamentals of MX Component and creating procedure.

3 USER APPLICATION CREATING PROCEDURES

4 ADDING CONTROLS TO USER PROGRAM

6 COMMUNICATION SETTING EXAMPLES (UTILITY SETTING TYPE)

1.1 Before Using this Product

Support of a wide range of communication routes for programmable controller

Substantial improvement in user's development efficiency

Save and read of communication settings

Enter and save Read communication setting data and

'Execute the processing of function "ReadDeviceRandom2".

Specify the label name.

'Execute the processing of function "ReadDeviceRandom2".

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

Monitor devices and change their data

Device status is checked.

Set and connect communication path on

Access to buffer memory of special function module

Buffer memory data of connected intelligent or

Clock data of connected programmable

The simulator function for offline debugging

Personal computer Programmable controller

Support multi-CPU system of QCPU (Q mode)

Transfer logging files to a personal computer

Gateway device data of GOT can be

GOT GOT GOT

Programmable controller CPU data

Mitsubishi Company A Company B

Support GOT transparent communication

Reduction of error description search time

<Example of displaying error description on message box>

Error description and corrective action

*1 Not applicable to inverter communication/robot controller communication.

Act Control (logging file transfer)

■ When user account control (UAC) is enabled

■ When user account control (UAC) is disabled

■ Warning messages in Windows

2.1 Operating Environment

*1 64-bit version only

*1 Not supported when using Windows 10 Education.

System configuration examples of each communication route