MX Component Version 4

Programming Manual

-SW4DNC-ACT-E
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using this product, please read this manual and the relevant manuals carefully and pay full attention to safety to handle
the product correctly.
In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".

Indicates that incorrect handling may cause hazardous conditions, resulting in

WARNING death or severe injury.

Indicates that incorrect handling may cause hazardous conditions, resulting in

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

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

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

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

1
 CONDITIONS OF USE FOR THE PRODUCT
(1) MELSEC programmable controller ("the PRODUCT") shall be used in conditions;
i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident;
and
ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the
case of any problem, fault or failure occurring in the PRODUCT.
(2) The PRODUCT has been designed and manufactured for the purpose of being used in general industries.
MITSUBISHI ELECTRIC SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED TO
ANY AND ALL RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT, PRODUCT
LIABILITY) FOR ANY INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO PROPERTY CAUSED BY the
PRODUCT THAT ARE OPERATED OR USED IN APPLICATION NOT INTENDED OR EXCLUDED BY
INSTRUCTIONS, PRECAUTIONS, OR WARNING CONTAINED IN MITSUBISHI ELECTRIC USER'S, INSTRUCTION
AND/OR SAFETY MANUALS, TECHNICAL BULLETINS AND GUIDELINES FOR the PRODUCT.
("Prohibited Application")
Prohibited Applications include, but not limited to, the use of the PRODUCT in;
• Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the
public could be affected if any problem or fault occurs in the PRODUCT.
• Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality
assurance system is required by the Purchaser or End User.
• Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator,
Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for Recreation and Amusement, and
Safety devices, handling of Nuclear or Hazardous Materials or Chemicals, Mining and Drilling, and/or other
applications where there is a significant risk of injury to the public or property.
Notwithstanding the above restrictions, Mitsubishi Electric may in its sole discretion, authorize use of the PRODUCT in
one or more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific
applications agreed to by Mitsubishi Electric and provided further that no special quality assurance or fail-safe,
redundant or other safety features which exceed the general specifications of the PRODUCTs are required. For details,
please contact the Mitsubishi Electric representative in your region.
(3) Mitsubishi Electric shall have no responsibility or liability for any problems involving programmable controller trouble and
system trouble caused by DoS attacks, unauthorized access, computer viruses, and other cyberattacks.

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

Considerations of operating system and personal computer to be used

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

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

■Resume and other functions of personal computer

A communication error may occur when communicating with the programmable controller CPU after setting the resume
function, suspend setting, power-saving function, and/or standby mode of the personal computer.
Therefore, do not set the above functions when communicating with the programmable controller CPU.

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

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

■When downloading the installer

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

Programmable controller CPU-related considerations

■Considerations for performing USB communication
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
programmable controller CPU.
If it is not recovered, completely disconnect the USB cable and then reconnect it after 5 or more seconds.
(If this error occurs at the initial communication after the above operation, the function will be performed properly in and after
the second communications.)

■Clock data of programmable controller CPU

• For 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 or FXU/FX2C/FX2NC with the RTC cassette.
• Note that an error for transfer time occurs in the time setting.

■Restrictions on using FXCPU

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

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

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

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

■Considerations for using RnSFCPU

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

■Considerations for using QSCPU

In order to protect the safety programmable controller system, functions to write data to buffer memory, to write/set devices,
and to write clock data cannot be executed.

■Considerations for using FX5CPU

• Since FX5CPUs do not feature the PAUSE switch as the programmable controller CPU, an error is returned if remote
pause is specified in SetCpuStatus.
• Multiple simultaneous communications cannot be established via the route specified by a different adapter when an adapter
to be used for Ethernet direct connection is specified to establish a communication.
• Personal computer-side adapter information of communication settings may need to reset depending on the change in
personal computer environment or other MELSOFT application settings.

Considerations for using other MELSOFT products

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

■Considerations for performing MT Simulator2 communication

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

5
 Considerations for using Ethernet modules
■Resetting programmable controller CPU during TCP/IP connection establishment
When resetting the programmable controller CPU during TCP/IP connection establishment (during opening) using MX
Component, a communication error or receive error occurs at 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 Ethernet module

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

■Replacement of Ethernet module

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

■Simultaneous access when using Q series-compatible Ethernet module

The following conditions should be satisfied when communication is performed simultaneously from multiple personal
computers to the same module using the TCP/IP protocol.
• Using Q series-compatible E71 module (except QJ71E71-100) whose first five digits of the serial number are "02122" or
higher and whose function version is B or later.
• Using GX Developer Version 6.05F or later, set "MELSOFT connection" in the Ethernet parameter [open system].

■Unlocking password when using QJ71E71

The range where the password can be unlocked by remote operation is up to the connection target station.
If the password is also set on the lower layer, communication cannot be performed with the programmable controller CPU on
the lower layer.

Starting Enter password to

source unlock.
AAAA

No. Remote Password

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

Ethernet
QCPU Ô QCPU Õ QCPU Ö
: Accessible
(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.

6
■Ethernet communication
• The communication line is disconnected if the CPU becomes faulty or the Ethernet module is reset during Ethernet
communication (when the protocol is TCP/IP).
In this case, perform the line close processing (Close) and then perform the reopen processing (Open).
• When two different communication systems (protocols) are used to access from one personal computer to one Q series-
compatible E71, two station numbers for 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.
Example: 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
(UDP/IP) station number for GX Developer : 3 (Station number: 1)

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.

Considerations for using CC-Link modules

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

Considerations for using serial communication modules

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

■Considerations for connecting personal computer and serial communication module

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

7
 Considerations of modem communication
■Simultaneous modem communications
The simultaneous modem communications using MX Component and other applications (GX Developer or the like) cannot be
performed.
Do not perform a modem communication using other applications during a modem communication using MX Component.
If modem communications are simultaneously performed using MX Component and other application, this will result in a
communication error, disconnection of telephone line or similar problem.

■Considerations for using telephone line

• Do not use the call-waiting phone line.
On the call-waiting phone line, data corruption, telephone line disconnection, or similar problem may occur due to interrupt
reading sounds.
• Do not connect the line to master/slave phones.
If the handset of the slave phone is lifted while the telephone line is connecting to the master/slave phones, the telephone
line may be disconnected.
• Use an analog 2 wire type telephone line.
When using a digital line, use a terminal adapter.
When the telephone line is 4 wire type, the line may not be connected depending on the wiring type of the modular jack.
For the 4 wire type, conduct connection tests in advance to check for connections.

■Considerations for using cellular phone

• Modem for radio communication using a cellular phone
Although the modem name is different according to the manufacturer, the modem is generically referred to as the cellular
phone communication unit in this manual.
Select the model of the cellular phone communication unit according to the cellular phone used.
For details, contact the company of your cellular phone.
• Cellular phone without auto answer function
For the cellular phone without auto answer function, use a cellular phone communication unit that features the ANS/ORG/
TEL select switch.
If the cellular phone communication unit does not have the ANS/ORG/TEL select switch, the line cannot be connected.
The line connection procedure is different according to the cellular phone company and cellular phone model.
For details, contact the manufacturer of your cellular phone.

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

■Forced termination of processes during communication

If communication is performed with the same type of control open for multiple processes, forcing one process to be terminated
by Task Manager or the like may stop the other processes at the communication function execution area.

■Error at communication start

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

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

■ActUMsg control and ActUWzd control

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

■Considerations for using Ethernet modules

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

■Considerations for executing the Disconnect function

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

■Error at building sample programs

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

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

Operating procedure
1. Close Excel.

2. Delete "*.exd" in the Excel 8.0 folder of the temp folders.

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

■Resizing of ACT control

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

■Considerations for using Excel VBA

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

Considerations for using Microsoft Access

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

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

■Resizing of ACT control

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

Considerations for using VBScript

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

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

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

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

12
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
OPERATING CONSIDERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

CONTENTS
CHAPTER 1 OVERVIEW 23
1.1 Outline of Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.2 Control and Function Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Control list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Function list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

CHAPTER 2 CONTROLS 28
2.1 Settings for Using Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
When using VBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
When using VBScript. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
When using Visual Studio .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.2 Programming Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
When using VBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
When using VBScript. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
When using Visual Basic .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
When using Visual C++ .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
When using Visual C# .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.3 Device Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.4 Accessible Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

CHAPTER 3 PROPERTIES OF CONTROLS 62

3.1 Property List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.2 Details of Control Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION ROUTES 75

4.1 Serial Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Serial communication when the connected station is R series-compatible C24 (1) . . . . . . . . . . . . . . . . . . . . . . 75
Serial communication when the connected station is R series-compatible C24 (2) . . . . . . . . . . . . . . . . . . . . . . 78
Serial communication when the connected station is Q series-compatible C24 (1) . . . . . . . . . . . . . . . . . . . . . . 81
Serial communication when the connected station is Q series-compatible C24 (2) . . . . . . . . . . . . . . . . . . . . . . 84
Serial communication when the connected station is L series-compatible C24 (1). . . . . . . . . . . . . . . . . . . . . . . 86
Serial communication when the connected station is L series-compatible C24 (2). . . . . . . . . . . . . . . . . . . . . . . 89
Serial communication when the connected station is FX extended port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.2 Ethernet Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Ethernet communication when the connected station is R series-compatible E71 (TCP). . . . . . . . . . . . . . . . . . 93
Ethernet communication when the connected station is R series-compatible E71 (UDP) . . . . . . . . . . . . . . . . . 96
Ethernet communication when the connected station is Q series-compatible E71 (TCP) . . . . . . . . . . . . . . . . . 99
Ethernet communication when the connected station is Q series-compatible E71 (UDP) . . . . . . . . . . . . . . . . 102
Ethernet communication when the connected station is L series-compatible E71 (TCP) . . . . . . . . . . . . . . . . . 105
Ethernet communication when the connected station is L series-compatible E71 (UDP) . . . . . . . . . . . . . . . . . 108
Ethernet communication when the connected station is RCPU (TCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

13
 Ethernet communication when the connected station is RCPU (UDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Ethernet communication when the connected station is LHCPU (TCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Ethernet communication when the connected station is LHCPU (UDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Ethernet communication when the connected station is FX5CPU (TCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Ethernet communication when the connected station is FX5CPU (UDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Ethernet communication when the connected station is built-in Ethernet port QCPU (TCP) . . . . . . . . . . . . . . 125
Ethernet communication when the connected station is built-in Ethernet port QCPU (UDP) . . . . . . . . . . . . . . 129
Ethernet communication when the connected station is built-in Ethernet port LCPU (TCP). . . . . . . . . . . . . . . 133
Ethernet communication when the connected station is built-in Ethernet port LCPU (UDP) . . . . . . . . . . . . . . 136
Ethernet communication when the connected station is Ethernet adapter module (TCP) . . . . . . . . . . . . . . . . 139
Ethernet communication when the connected station is Ethernet adapter module (UDP) . . . . . . . . . . . . . . . . 143
Ethernet communication when the connected station is Ethernet adapter (TCP) . . . . . . . . . . . . . . . . . . . . . . . 147
Ethernet communication when the connected station is Ethernet adapter (UDP). . . . . . . . . . . . . . . . . . . . . . . 148
Ethernet communication when the connected station is robot controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Ethernet communication when the connected station is CC-Link IE TSN module (TCP) . . . . . . . . . . . . . . . . . 150
Ethernet communication when the connected station is CC-Link IE TSN module (UDP) . . . . . . . . . . . . . . . . . 153
4.3 CPU COM communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
CPU COM communication when the connected station is FX5CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
CPU COM communication when the connected station is QCPU (Q mode) . . . . . . . . . . . . . . . . . . . . . . . . . . 158
CPU COM communication when the connected station is LCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
CPU COM communication when the connected station is Q motion CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
CPU COM communication when the connected station is FXCPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
CPU COM communication when the connected station is inverter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
CPU COM communication when the connected station is robot controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
4.4 CPU USB Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
CPU USB communication when the connected station is RCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
CPU USB communication when the connected station is R motion CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
CPU USB communication when the connected station is LHCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
CPU USB communication when the connected station is FX5CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
CPU USB communication when the connected station is QCPU (Q mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
CPU USB communication when the connected station is LCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
CPU USB communication when the connected station is QSCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
CPU USB communication when the connected station is Q motion CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
CPU USB communication when the connected station is FXCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
CPU USB communication when the connected station is inverter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
CPU USB communication when the connected station is robot controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
4.5 MELSECNET/H Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
4.6 CC-Link IE Controller Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
CC-Link IE Controller Network communication when the connected station is an RCPU. . . . . . . . . . . . . . . . . 194
CC-Link IE Controller Network communication when the connected station is a module supporting
Q series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
4.7 CC-Link IE Field Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
CC-Link IE Field Network communication when the connected station is an RCPU . . . . . . . . . . . . . . . . . . . . 199
CC-Link IE Field Network communication when the connected station is a module supporting QCPU
(Q mode) or LCPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
4.8 CC-Link Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
CC-Link communication when the connected station is an RCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
CC-Link communication when the connected station is an LCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
CC-Link communication when the connected station is a module supporting Q series . . . . . . . . . . . . . . . . . . 208
4.9 CC-Link G4 communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
4.10 GX Simulator Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

14
4.11 GX Simulator2 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
4.12 GX Simulator3 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
4.13 MT Simulator2 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
4.14 Modem Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Modem communication when the connected module is Q series-compatible C24 (1) . . . . . . . . . . . . . . . . . . . 216
Modem communication when the connected module is Q series-compatible C24 (2) . . . . . . . . . . . . . . . . . . . 219
Modem communication when the connected module is L series-compatible C24 (1). . . . . . . . . . . . . . . . . . . . 222
Modem communication when the connected module is L series-compatible C24 (2). . . . . . . . . . . . . . . . . . . . 225
Modem communication when the connected station is FXCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

CONTENTS
4.15 Gateway Function Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4.16 GOT Transparent Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Direct connection (1) . . . . . . 230
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Direct connection (2) . . . . . . 232
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Direct connection (3) . . . . . . 235
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Direct connection (4) . . . . . . 238
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Direct connection (1) . . . 240
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Direct connection (2) . . . 242
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Direct connection (3) . . . 244
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Direct connection (4) . . . 247
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Bus connection . . . . . . . . . . 249
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Bus connection . . . . . . . 252
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial communication
module (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial communication
module (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial communication
module (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial communication
module (4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial communication
module (5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial communication
module (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial communication
module (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial communication
module (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial communication
module (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial communication
module (4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial communication
module (5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial communication
module (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: R series-compatible E71 . . . 281
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Q series-compatible E71. . . 284
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: L series-compatible E71 . . . 287
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: R series-compatible
E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

15
 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Q series-compatible
E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: L series-compatible
E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet port (1) . . . . . . . . . 299
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet port (2) . . . . . . . . . 302
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet port (3) . . . . . . . . . 304
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet port (4) . . . . . . . . . 308
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet port (1). . . . . . . 311
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet port (2). . . . . . . 314
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet port (3). . . . . . . 316
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet port (4). . . . . . . 320
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet adapter module. . . 323
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet adapter
module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet adapter/
module (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet adapter/
module (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Personal computer side port: Ethernet board, GOT2000/1000 side port: Ethernet port, CPU side port:
Serial (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Personal computer side port: Ethernet board, GOT2000/1000 side port: Ethernet port, CPU side port:
Serial (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Personal computer side port: Ethernet board, GOT2000/1000 side port: Ethernet port, CPU side port:
Serial (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Personal computer side port: Ethernet board, GOT2000/1000 side port: Ethernet port, CPU side port:
Serial (4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Personal computer side port: Ethernet board, GOT2000/1000 side port: Ethernet port, CPU side port:
Serial communication module (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Personal computer side port: Ethernet board, GOT2000/1000 side port: Ethernet port, CPU side port:
Serial communication module (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Personal computer side port: Ethernet board, GOT2000/1000 side port: Ethernet port, CPU side port:
Serial communication module (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Personal computer side port: Ethernet board, GOT2000/1000 side port: Ethernet port, CPU side port:
Bus connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Personal computer side port: Ethernet board, GOT2000/1000 side port: Ethernet port, CPU side port:
Ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Personal computer side port: Ethernet board, GOT2000/1000 side port: Ethernet port, CPU side port:
Q series-compatible E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
4.17 Q Series Bus Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

CHAPTER 5 FUNCTIONS 361

5.1 Programming Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
5.2 Details of Functions (For ACT Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Open (Opening communication line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Close (Closing communication line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
ReadDeviceBlock (Reading devices in bulk). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
WriteDeviceBlock (Writing devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
ReadDeviceRandom (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
WriteDeviceRandom (Writing devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

16
 SetDevice (Set device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
GetDevice (Acquiring device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
ReadBuffer (Reading data from buffer memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
WriteBuffer (Writing data to buffer memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
GetClockData (Reading clock data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
SetClockData (Writing clock data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
GetCpuType (Reading programmable controller CPU model) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
SetCpuStatus (Remote control). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
EntryDeviceStatus (Registering devices for status monitoring). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

CONTENTS
FreeDeviceStatus (Deregistering devices for status monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
OnDeviceStatus (Event notification) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
ReadDeviceBlock2 (Reading devices in bulk). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
WriteDeviceBlock2 (Writing devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
ReadDeviceRandom2 (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
WriteDeviceRandom2 (Writing devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
SetDevice2 (Set device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
GetDevice2 (Acquiring device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Connect (Connecting telephone line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Disconnect (Disconnecting telephone line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
GetErrorMessage (Receiving error message). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
5.3 Details of Functions (For ACT Control (Logging File Transfer)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Open (Opening communication line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Close (Closing communication line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
ReadFirstFile (Searching for a file/directory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
ReadNextFile (Searching for a file/directory). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
ReadClose (Ending the search) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
GetFile (Transferring logging files) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
5.4 Details of Functions (For .NET Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Open (Opening communication line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Close (Closing communication line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
ReadDeviceBlock (Reading devices in bulk). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
WriteDeviceBlock (Writing devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
ReadDeviceRandom (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
WriteDeviceRandom (Writing devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
SetDevice (Set device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
GetDevice (Acquiring device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
ReadBuffer (Reading data from buffer memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
WriteBuffer (Write data to buffer memory.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
GetClockData (Reading clock data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
SetClockData (Writing clock data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
GetCpuType (Reading programmable controller CPU model) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
SetCpuStatus (Remote control). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
EntryDeviceStatus (Registering devices for status monitoring). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
FreeDeviceStatus (Deregistering devices for status monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
OnDeviceStatus (Event notification) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
ReadDeviceBlock2 (Reading devices in bulk). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
WriteDeviceBlock2 (Writing devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
ReadDeviceRandom2 (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
WriteDeviceRandom2 (Writing devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
SetDevice2 (Set device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
GetDevice2 (Acquiring device data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517

17
 Connect (Connecting telephone line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Disconnect (Disconnecting telephone line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
GetErrorMessage (Receiving error message). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524

CHAPTER 6 SAMPLE PROGRAMS 525

6.1 VBA Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Sample program for Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Sample program for Excel (Reading/writing devices) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Sample program for Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
6.2 VBScript Sample Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
6.3 ASP Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
6.4 Visual Basic .NET Sample Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Modem communication sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Read/Write sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Type conversion sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Logging file transfer sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
6.5 Visual C++ .NET Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Read/Write sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Troubleshooting function sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
6.6 Visual C# .NET Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Read/Write sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Logging file transfer sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
6.7 Visual C++ .NET (MFC) Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Dispatch interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Custom interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Troubleshooting function sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Logging file transfer sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554

CHAPTER 7 ERROR CODES 555

7.1 Error Codes Returned by Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
7.2 Error Codes Returned by CPUs, Modules, and Network Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
7.3 HRESULT Type Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
7.4 Error Codes Displayed on Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583

APPENDIX 584
Appendix 1 Connection System of Callback Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Appendix 2 Programming Examples for Monitoring Word Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Appendix 3 Time-Out Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Communication retries at time-out error occurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Communication retries at receive data error occurrence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Time-out errors at fixed time in ACT control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Appendix 4 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Error occurred in the setting for using controls in Visual Studio .NET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Link error occurred when creating a user application in Visual C++ .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
The unstart error occurred during communication with GX Simulator3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
A build error occurred when using a sample program created in Visual Studio 2017 . . . . . . . . . . . . . . . . . . . . 613
REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .614
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .616

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

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.

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

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

21
 Term Description
Robot controller COM Abbreviation for communication by connecting the robot controller to the COM port of personal computer.
communication
Robot controller Ethernet Abbreviation for communication by connecting the robot controller and personal computer to Ethernet.
communication
Robot controller USB Abbreviation for communication by connecting the robot controller to the USB port of personal computer.
communication
Serial communication Abbreviation for communication with programmable controller CPU using the serial communication module.
Serial communication module Generic term for R series-compatible C24, Q series-compatible C24, L series-compatible C24, and FX extended port.
Utility setting type A development type for creating user programs using Communication Setup Utility.

Visual Basic .NET Generic term for Visual Basic version Microsoft Visual Studio 2005, Microsoft Visual Studio 2008, Microsoft Visual Studio
2010, Microsoft Visual Studio 2012, Microsoft Visual Studio 2013, Microsoft Visual Studio 2015, and Microsoft Visual
Studio 2017.
Visual C#.NET Generic term for Visual C# version Microsoft Visual Studio 2005, Microsoft Visual Studio 2008, Microsoft Visual Studio
2010, Microsoft Visual Studio 2012, Microsoft Visual Studio 2013, Microsoft Visual Studio 2015, and Microsoft Visual
Studio 2017.
Visual C++.NET Abbreviation for creation of an application using .NET Framework.
Visual C++.NET(MFC) Abbreviation for creation of an application using MFC/ATL/Win32.

22
1 OVERVIEW
1
This manual explains the procedure and the error codes when creating programs with MX Component.

1.1 Outline of Controls

This section explains the outline of controls supported by MX Component.
These controls are used to create user programs to communicate with a programmable controller CPU. A user can
communicate with programmable controller CPUs without being aware of the hardware and the communication protocol on
the other end.
Personal computer

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

Ethernet
Ethernet communication Ethernet module

Ethernet board
Built-in Ethernet CPU

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

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
FXCPU
Converter/cable (FX0/FX0S/FXON/FX1S/FX1N/FX2N/FX1NC/
FX2NC/FX3S/FX3G/FX3GC/FX3U/FX3UC)

USB RCPU, R motion CPU, LHCPU, FX5CPU (FX5UJ),

CPU USB communication QCPU (Q mode), LCPU, C Controller module, QSCPU,
Q motion CPU, FXCPU (FX3S/FX3G/FX3GC)

MELSECNET/H MELSECNET/H module

MELSECNET/H communication

MELSECNET/H board

CC-Link IE Controller Network CC-Link IE Controller CC-Link IE Controller Network module

communication Network

CC-Link IE Controller
Network board

CC-Link IE Field Network CC-Link IE Field CC-Link IE Field Network module

communication Network

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

CC-Link G4 module
(Software version "D" or later)

1 OVERVIEW
1.1 Outline of Controls 23
 Personal computer

Perform communication with the specified

programmable controller easily without being
aware of communication protocol.

GX Developer GX Developer Version 5

+ GX Simulator (SW5D5C-GPPW-E) or later
GX Simulator communication GX Simulator
(offline debugging)
(SW5D5C-LLT-E 10B) or later
Sold separately

Simulation function of GX Works2 GX Works2 Version 1

GX Simulator2 communication (GX Simulator2) (SW1DNC-GXW2-E) or later
Sold separately

Simulation function of GX Works3 GX Works3

GX Simulator3 communication (SW1DND-GXW3-E)
(GX Simulator3)
Sold separately
MT Developer2 Version 1
Simulation function of MT Developer2 (SW1DNC-MTW2-E) or later
MT Simulator2 communication (MT Simulator2) Sold separately

Telephone line FXCPU, Q series-compatible C24,

Modem communication
L series-compatible C24
Modem Modem

Ethernet
Gateway function communication GOT
Ethernet board

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

GOT transparent 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

Bus connection QCPU (Q mode),

QCCPU,
Q motion CPU

Ethernet
Ethernet module

Ethernet
Built-in Ethernet CPU

Ethernet Adapter CC-Link IE Field

module Network CC-Link IE Field Network

Ethernet
Ethernet Adapter/module

Inverter COM RS-232/RS-485 conversion

communication Inverter

Inverter USB USB

communication Inverter

Robot controller RS-232

Robot controller
COM communication

Robot controller USB

Robot controller
USB communication

Robot controller Ethernet

Robot controller
Ethernet communication
Ethernet board

On the same base

Q series bus communication PC CPU module QCPU (Q mode)

1 OVERVIEW
24 1.1 Outline of Controls
1.2 Control and Function Lists
This section shows the lists of controls and functions.
1

Control list
The following tables show the controls included in each DLL supported by MX Component.

ACT control
The following table shows the ActiveX controls supported by MX Component.
Data can be accessed using devices.
DLL name Included control name Application
For VB, VC++, For VBScript
VC#, VBA
ActUtlType.dll ActUtlType ActMLUtlType*1 A utility setting type control.
It is used to create a user program using Communication Setup Utility.
ActProgType.dll*2 ActProgType ActMLProgType*1 A program setting type control.
It is used to create a user program without using Communication Setup
Utility.
ActSupportMsg.dll ActSupportMsg ActMLSupportMsg Used for the troubleshooting function.

*1 Communication is disabled if the communication route is a modem.

*2 Not applicable to inverter communication/robot controller communication.

ACT Control (logging file transfer)

The following table shows the ActiveX controls for transferring logging files supported by MX Component.
Do not use the controls while the logging function of a CPU module is in operation.
DLL name Included control name Application
For VB, VC++, VC#, For VBScript
VBA
ActUtlDataLogging.dll ActUtlDataLogging Not supported A utility setting type control.
It is used to transfer a logging file.
It operates with a logical station number which is created in
Communication Setup Utility.
ActProgDataLogging.dll ActProgDataLogging Not supported A program setting type control.
It is used to transfer a logging file.
It operates with the property of the control.

.NET control
The following table shows the .NET controls supported by MX Component.
Data can be accessed using labels.
DLL name Included control name Application
For VB, VC++, VC#
MITSUBISHI. DotUtlType A utility setting type control.
Component. It is used to create a user program using Communication Setup Utility.
DotUtlType.dll
MITSUBISHI. DotSupportMsg Used for the troubleshooting function.
Component.
DotSupportMsg.dll

1 OVERVIEW
1.2 Control and Function Lists 25
 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 Open a communication line. Act: Page 366 Open (Opening communication line)
DataLogging: Page 441 Open (Opening communication line)
Dot: Page 449 Open (Opening communication line)
Close Close a communication line. Act: Page 368 Close (Closing communication line)
DataLogging: Page 442 Close (Closing communication line)
Dot: Page 450 Close (Closing communication line)
ReadDeviceBlock Read devices in bulk. (4-byte data) Act: Page 369 ReadDeviceBlock (Reading devices in bulk)
Dot: Page 451 ReadDeviceBlock (Reading devices in bulk)
WriteDeviceBlock Write devices in bulk. (4-byte data) Act: Page 372 WriteDeviceBlock (Writing devices in bulk)
Dot: Page 455 WriteDeviceBlock (Writing devices in bulk)
ReadDeviceRandom Read devices randomly. (4-byte data) Act: Page 376 ReadDeviceRandom (Reading devices randomly)
Dot: Page 460 ReadDeviceRandom (Reading devices randomly)
WriteDeviceRandom Write devices randomly. (4-byte data) Act: Page 379 WriteDeviceRandom (Writing devices randomly)
Dot: Page 466 WriteDeviceRandom (Writing devices randomly)
SetDevice Set one point of device. (4-byte data) Act: Page 382 SetDevice (Set device data)
Dot: Page 472 SetDevice (Set device data)
GetDevice Acquire data of one point of device. (4-byte data) Act: Page 384 GetDevice (Acquiring device data)
Dot: Page 475 GetDevice (Acquiring device data)
ReadBuffer Read data from buffer memory. Act: Page 387 ReadBuffer (Reading data from buffer memory)
Dot: Page 478 ReadBuffer (Reading data from buffer memory)
WriteBuffer Write data to buffer memory. Act: Page 392 WriteBuffer (Writing data to buffer memory)
Dot: Page 480 WriteBuffer (Write data to buffer memory.)
GetClockData Read clock data from programmable controller CPU. Act: Page 396 GetClockData (Reading clock data)
Dot: Page 482 GetClockData (Reading clock data)
SetClockData Write clock data to programmable controller CPU. Act: Page 400 SetClockData (Writing clock data)
Dot: Page 484 SetClockData (Writing clock data)
GetCpuType Read programmable controller CPU model. Act: Page 404 GetCpuType (Reading programmable controller CPU model)
Dot: Page 486 GetCpuType (Reading programmable controller CPU model)
SetCpuStatus Remote RUN/STOP/PAUSE of programmable Act: Page 408 SetCpuStatus (Remote control)
controller CPU. Dot: Page 487 SetCpuStatus (Remote control)
EntryDeviceStatus Register device status monitor. Act: Page 411 EntryDeviceStatus (Registering devices for status monitoring)
Dot: Page 488 EntryDeviceStatus (Registering devices for status monitoring)
FreeDeviceStatus Deregister device status monitor. Act: Page 415 FreeDeviceStatus (Deregistering devices for status monitoring)
Dot: Page 491 FreeDeviceStatus (Deregistering devices for status monitoring)
OnDeviceStatus Announce event. Act: Page 416 OnDeviceStatus (Event notification)
Dot: Page 492 OnDeviceStatus (Event notification)
ReadDeviceBlock2 Read devices in bulk. (2-byte data) Act: Page 418 ReadDeviceBlock2 (Reading devices in bulk)
Dot: Page 498 WriteDeviceBlock2 (Writing devices in bulk)
WriteDeviceBlock2 Write devices in bulk. (2-byte data) Act: Page 421 WriteDeviceBlock2 (Writing devices in bulk)
Dot: Page 498 WriteDeviceBlock2 (Writing devices in bulk)
ReadDeviceRandom2 Read devices randomly. (2-byte data) Act: Page 424 ReadDeviceRandom2 (Reading devices randomly)
Dot: Page 502 ReadDeviceRandom2 (Reading devices randomly)
WriteDeviceRandom2 Write devices randomly. (2-byte data) Act: Page 427 WriteDeviceRandom2 (Writing devices randomly)
Dot: Page 508 WriteDeviceRandom2 (Writing devices randomly)
SetDevice2 Set one point of device. (2-byte data) Act: Page 430 SetDevice2 (Set device data)
Dot: Page 514 SetDevice2 (Set device data)
GetDevice2 Acquire data of one point of device. (2-byte data) Act: Page 433 GetDevice2 (Acquiring device data)
Dot: Page 517 GetDevice2 (Acquiring device data)
Connect Connect a telephone line. Act: Page 435 Connect (Connecting telephone line)
Dot: Page 520 Connect (Connecting telephone line)
Disconnect Disconnect a telephone line Act: Page 437 Disconnect (Disconnecting telephone line)
Dot: Page 522 Disconnect (Disconnecting telephone line)
GetErrorMessage Display error definition and corrective action. Act: Page 439 GetErrorMessage (Receiving error message)
Dot: Page 524 GetErrorMessage (Receiving error message)
ReadFirstFile Search for a directly name/file name. DataLogging: Page 443 ReadFirstFile (Searching for a file/directory)
ReadNextFile Search for a directly name/file name. DataLogging: Page 445 ReadNextFile (Searching for a file/directory)
ReadClose End the search. DataLogging: Page 447 ReadClose (Ending the search)

1 OVERVIEW
26 1.2 Control and Function Lists
Function name Feature Refer*1
GetFile Transfer a logging file. DataLogging: Page 448 GetFile (Transferring logging files)

*1 Act: For ACT controls, DataLogging: For ACT controls (logging file transfer), Dot: For .NET controls 1
• Considerations for using RnSFCPU
In order to protect the safety programmable controller system, the "write to buffer memory" and "write to
safety devices in safety mode" functions cannot be executed.
• Considerations for using QSCPU
In order to protect the safety programmable controller system, an error code is returned when a function to
write data to buffer memory, write/set devices, or write clock data is executed.

1 OVERVIEW
1.2 Control and Function Lists 27
 2 CONTROLS
This chapter explains settings for using controls, programming procedure, device types, and applicable access ranges.

2.1 Settings for Using Controls

This section explains the settings for using controls.

When using VBA

Perform the following setting operation when using VBA.

When using Microsoft Excel 2010

Operating procedure
1. Start Excel, select [Insert] on the [Developer] tab, and click the button.

2. Select the ACT control to be used, and click the [OK] button.

3. Paste the selected ACT control to the sheet.

2 CONTROLS
28 2.1 Settings for Using Controls
4. Select [Visual Basic] on the [Developer] tab to start Visual Basic Editor.

5. Create a program with Visual Basic Editor.

2 CONTROLS
2.1 Settings for Using Controls 29
 When using Microsoft Access 2010
1. Start Access and activate the database form.

2. Select [Controls]  [ActiveX Controls] on the [Design] tab.

3. Select the ACT control to be used, and click the [OK] button.

4. Paste the selected ACT control to the sheet.

2 CONTROLS
30 2.1 Settings for Using Controls
5. Select [View Code] on the [Design] tab to start Visual Basic Editor.

6. Create a program with Visual Basic Editor.

2 CONTROLS
2.1 Settings for Using Controls 31
 When using VBScript
Create HTML or ASP using a tool such as notepad, commercially available text editor, or HTML creation tool.
For the grammars of HTML and ASP, refer to the commercially available references.
The HTML and ASP sample programs installed with MX Component can also be referred.

2 CONTROLS
32 2.1 Settings for Using Controls
When using Visual Studio .NET
Perform the following setting operation when using Visual Studio .NET.

Setting the include file (for Visual Basic .NET)

Operating procedure
2
1. Start the project and select [Project]  [Add Existing Item].

2. Select the ActDefine.vb file and click the [Add] button.

The ActDefine.vb file is stored in the following folder at the time of installation.
[User-specified folder] - [Act] - [Include]

3. The ActDefine.vb file is displayed on the Solution Explorer window.

2 CONTROLS
2.1 Settings for Using Controls 33
 Setting the include file (for Visual C++ .NET)
Operating procedure
1. Start Visual Studio .NET and select [Project]  [Properties].

(For Visual Studio 2005 and Visual Studio 2008, select [Tools]  [Options].)

2. Select [Configuration Properties]  [VC++ Directories] on the navigation pane displayed on the left side of the screen.

(For Visual Studio 2005 and Visual Studio 2008, select [Projects and Solutions]  [VC++ Directories].)

3. Right-click on "Include Directories" displayed on the right side of the screen and select <Edit...>.

For Visual Studio 2005 and Visual Studio 2008, select "Include files" for "Show directories for:" on the top right of the screen.

2 CONTROLS
34 2.1 Settings for Using Controls
 2

4. Click (New line).

5. Click the [...] button.

6. Select the folder that contains the include files.

The include files are stored in the following folder at the time of installation.
[User-specified folder] - [Act] - [Include]

2 CONTROLS
2.1 Settings for Using Controls 35
 Setting the include file (for Visual C# .NET)
Operating procedure
1. Start Visual Studio .NET and select [PROJECT]  [Add Existing Item].

2. Select the ActDefine.cs file and click the [Add] button.

The ActDefine.cs file is stored in the following folder at the time of installation.
[User-specified folder] - [Act] - [Include]

3. The ActDefine.cs file is displayed on the Solution Explorer window.

2 CONTROLS
36 2.1 Settings for Using Controls
When pasting a control to the form
(Common setting for Visual C++ .NET, Visual Basic .NET, and Visual C# .NET projects)

Operating procedure
1. Select [Tools]  [Choose Toolbox Items]. 2

2. Select the [.NET Framework Components] tab (for pasting .NET control) or the [COM Components] tab (for pasting ACT
control), select the control to be used, and click the [OK] button.

3. The control is added to the bottom of the tab selected under "Toolbox".

2 CONTROLS
2.1 Settings for Using Controls 37
 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>

2 CONTROLS
38 2.1 Settings for Using Controls
When using control without pasting it to a form (Reference setting)
(Common setting for Visual C++ .NET, Visual Basic .NET, and Visual C# .NET projects)

Operating procedure
1. Select [View]  [Solution Explorer] to display "Solution Explorer". 2
2. Right-click the project and select "References".

(For Visual Studio 2010, Visual Studio 2012, Visual Studio 2015, and Visual Studio 2017, select "Add Reference". (To Step 4))
(For Visual Studio 2013, select "Add"  "References". (To Step 4))

3. Select the [Add New Reference] button on "Property Pages".

2 CONTROLS
2.1 Settings for Using Controls 39
 4. Select the [COM] tab (for pasting ACT control) or the [.NET] tab (for pasting .NET control), select the control to be used,
and click the [OK] button.

(For Visual Studio 2012, Visual Studio 2013, Visual Studio 2015, and Visual Studio 2017, select "COM"  "Type Libraries" (for
pasting ACT control) or "Assemblies"  "Extensions" (for pasting .NET control), select the control to be used, and click the
[OK] button.)

2 CONTROLS
40 2.1 Settings for Using Controls
5. The library of the component to be used is set to "References" as a reference.

The library of the component to be used can be checked with "References" on "Class View".

(For Visual Studio 2008 and Visual Studio 2010, enable "Show Project References" in "Class View Settings".)

2 CONTROLS
2.1 Settings for Using Controls 41
 6. For Visual Basic .NET of Visual Studio 2010/2012/2013/2015/2017, click the button on "Solution Explorer" to display
all files.
Right-click the library of the component to be used under "References" and select "Properties".

Set "False" for "Embed Interop Types".

• When using Visual C++ .NET/Visual Basic .NET/Visual C# .NET 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.
• When creating a program
Select "x86" (32 bits) for "Target CPU".
• When creating an application using .NET Framework 4, .NET Framework 4.5, or .NET Framework 4.6, add
an application configuration file with the following elements (app.config) to the folder which contains the .exe
file of the application. (The following is an example for .NET Framework 4.)
For details, refer to Visual Studio Help.

<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0"/>
</startup>
</configuration>

2 CONTROLS
42 2.1 Settings for Using Controls
When using ACT control on Visual C++ .NET(MFC)
Operating procedure
1. Right-click the form and select "Insert ActiveX Control".

2. Select the ACT control to be used and click the [OK] button.

3. The selected ACT control is pasted to the form.

2 CONTROLS
2.1 Settings for Using Controls 43
 4. Right-click the form and select "Add Variable".

5. After selecting "Control variable", select the ID of the ACT control for "Control ID", enter the variable name, and click the
[Finish] button.

2 CONTROLS
44 2.1 Settings for Using Controls
6. Check that the member variable set in Step 5 is created.
• In the form class of Class View

• In the header file of form class

2 CONTROLS
2.1 Settings for Using Controls 45
 When using a different version of Visual Studio
■When using a project which is created in the version of Visual Studio 2013 or earlier in Visual
Studio 2015
When opening and compiling the project which is created in Visual Studio 2013 or earlier in Visual Studio 2015, save the
project in UNICODE format.

Operating procedure
1. Select [Tools]  [Customize].

2. Select the [Commands] tab, and click the [Add Command] button.

3. Select "File"  "Advanced Save Options", and click the [OK] button.

2 CONTROLS
46 2.1 Settings for Using Controls
■When using a project which is created in Visual Studio 2015 or earlier in Visual Studio 2017
When opening a Visual C++ .NET(MFC) project which is created in Visual Studio 2015 or earlier in Visual Studio 2017, the
Windows SDK version must be changed to '10.0.15063.0'.

Operating procedure
1. Select [Project]  [Property] to open "Property Pages". 2
2. Check the version in "Windows SDK Version" by selecting [Configuration Properties]  [General], and change the
version to '10.0.15063.0'.

2 CONTROLS
2.1 Settings for Using Controls 47
 2.2 Programming Procedure
This section explains the procedure to create a user application.

When creating a user program, select "x86" (32 bits) for "Target CPU".

When using VBA

Create a user application with the following procedure when using VBA.

Power on the personal computer and start Windows.

Install MX Component Version 4. (1)

Program setting type

Select the setting type.

Utility setting type

Start Communication Setup Utility and set the communication

settings by following the instructions of wizard. (1) Start Excel or Access.
(2)
Start Visual Basic Editor and create
Start Excel or Access.
an application.
(2)
Start Visual Basic Editor and create Form the controls to be used
an application. in VBA. (ActProgType)

Form the controls to be used

in VBA. (ActUtlType)
Set the property of the formed controls. (1)

Set the property of the formed controls.

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

Create a program using the functions supported by (3)

corresponding controls.

Debug the program using PLC Monitor Utility. (1)

Completion of user application

(1) MX Component Version 4 Operating Manual

(2) Page 28 When using VBA
(3) Page 62 PROPERTIES OF CONTROLS, Page 75 PROPERTY SETTINGS OF COMMUNICATION ROUTES,
Page 361 FUNCTIONS

2 CONTROLS
48 2.2 Programming Procedure
When using VBScript
Create a user application with the following procedure when using VBScript.

Power on the personal computer and start Windows.

Install MX Component Version 4. (1) 2

Program setting type
Select the setting type.

Utility setting type

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

Create a website using the text editor

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

Set the property of the formed controls.

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

Create a program using the functions supported by

corresponding controls. (3)

Debug the program using PLC Monitor Utility. (1)

Completion of user application

(1) MX Component Version 4 Operating Manual

(2) Page 32 When using VBScript
(3) Page 62 PROPERTIES OF CONTROLS, Page 75 PROPERTY SETTINGS OF COMMUNICATION ROUTES,
Page 361 FUNCTIONS

2 CONTROLS
2.2 Programming Procedure 49
 When using Visual Basic .NET
Create a user application with the following procedure when using Visual Basic .NET.
Power on the personal computer and start Windows.

Install MX Component Version 4. (1)

Program setting type

Select the setting type.

Utility setting type

Yes Start Visual Basic.NET.

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

Start Visual Basic.NET. Start Visual Basic.NET.

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

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

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

Create a program using the functions supported by

corresponding controls.
(3)

Debug the program using PLC Monitor Utility. (1)

Completion of user application

(1) MX Component Version 4 Operating Manual

(2) Page 33 Setting the include file (for Visual Basic .NET)
(3) Page 62 PROPERTIES OF CONTROLS, Page 75 PROPERTY SETTINGS OF COMMUNICATION ROUTES,
Page 361 FUNCTIONS

2 CONTROLS
50 2.2 Programming Procedure
When using Visual C++ .NET
Create a user application with the following procedure when using Visual C++ .NET.

Power on the personal computer and start Windows.

Install MX Component Version 4. (1) 2

Program setting type
Select the setting type.

Utility setting type

Yes Start Visual C++.NET.

Use labels.

No Add controls to Visual C++.NET.

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

Add controls to Visual C++.NET. Add controls to Visual C++.NET. Set the property of the pasted controls. (1)
(2)
Create a form and paste the controls. (2) Create a form and paste the controls.
(ActUtlType) (DotUtlType)

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

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

Create a program using the functions supported by

corresponding controls. (3)

Debug the program using PLC Monitor Utility. (1)

Completion of user application

(1) MX Component Version 4 Operating Manual

(2) Page 34 Setting the include file (for Visual C++ .NET)
(3) Page 62 PROPERTIES OF CONTROLS, Page 75 PROPERTY SETTINGS OF COMMUNICATION ROUTES,
Page 361 FUNCTIONS

2 CONTROLS
2.2 Programming Procedure 51
 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.
• Visual Studio 2005/2008
1) Select [Common Properties]  [References].
2) Select "ActUtlTypeLib" from "Name" in "References", and change the setting of "Use" under "Build
Properties" to "False".
3) Select "ActInterop.ActUtlTypeLib.1.0" from "Name" in "References", and change the setting of "Use"
under "Build Properties" to "False".
4) Click the [OK] button to reflect the change of the setting.
• Visual Studio 2010/2012/2013/2015/2017
1) Select [Common Properties]  [Framework and references].
2) Select "ActUtlTypeLib" from "Name" in "References", and change the setting of "Reference Assembly
Output" under "Build Properties" to "False".
3) Select "Interop.ActUtlTypeLib.1.0" from "Name" in "References", and change the setting of "Reference
Assembly Output" under "Build Properties" to "False".
4) Click the [OK] button to reflect the change of the setting.

2 CONTROLS
52 2.2 Programming Procedure
When using Visual C# .NET
Create a user application with the following procedure when using Visual C# .NET.

Power on the personal computer and start Windows.

Install MX Component Version 4. (1) 2

Program setting type
Select the setting type.

Utility setting type

Yes Start Visual C#.NET.

Use labels.
(2)
No Add controls to Visual C#.NET.
Start Label Utility, and create and
register labels.
Create a form and paste the controls.
(1) (ActProgType)
Start Communication Setup Utility and set the communication Start Communication Setup Utility and set the communication
settings by following the instructions of wizard. (1) settings by following the instructions of wizard.
Set the property of the pasted controls. (1)
Start Visual C#.NET. Start Visual C#.NET.
(2) (2)
Add controls to Visual C#.NET. Add controls to Visual C#.NET.

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

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

Create a program using the functions supported by

corresponding controls. (3)

Debug the program using PLC Monitor Utility.*1 (1)

Completion of user application

(1) MX Component Version 4 Operating Manual

(2) Page 36 Setting the include file (for Visual C# .NET)
(3) Page 62 PROPERTIES OF CONTROLS, Page 75 PROPERTY SETTINGS OF COMMUNICATION ROUTES,
Page 361 FUNCTIONS

On Visual Studio 2010/2012/2013/2015/2017, when using both .NET control (DotUtlType) and Act control
(ActUtlType) by pasting them into a program, perform the following operations by selecting "References" from
Solution Explorer.
1) Select ActUtlTypeLib and delete it.
2) Select Interop.ActUtlTypeLib and delete it.

2 CONTROLS
2.2 Programming Procedure 53
 2.3 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 FX5CPU, gateway
function 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*12 Contact TS Bit device Decimal
Coil TC Bit device Decimal
Present value TN Word device Decimal
Counter*12 Contact CS Bit device Decimal
Coil CC Bit device Decimal
*3
Present value CN Word device Decimal
Retentive timer*12 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
Step relay S Bit device Decimal
Accumulator A*4 Word device Decimal
*4
Index register Z Word device Decimal
V *4 Word device Decimal
*5
File register R Word device Decimal
ZR Word device Decimal
Extended file register ER*\R*6 Word device Decimal

2 CONTROLS
54 2.3 Device Types
Device Device name Device type Device number
Direct link*8*13 Link input J*\X*7 Bit device Hexadecimal
Link output J*\Y*7 Bit device Hexadecimal
*7
Link relay J*\B Bit device Hexadecimal
Link special relay J*\SB*7 Bit device Hexadecimal

2
*7
Link register J*\W Word device Hexadecimal
Link special register J*\SW*7 Word device Hexadecimal
Special direct buffer memory*9*10 U*\G***7*11 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 specifying an extended file register, enter "\" between the block number and the file register.
When specifying R**, R of the block No. 0 becomes a target.
When specifying ER0\R**, an error is returned.
When specifying ER**\R**, the extension representation (indirect specification, digit specification) is not applicable.
*7 For a direct specification, enter "\" between the direct specification and the device specification.
*8 J* specifies a network number.
*9 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".)
*10 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.
*11 For FXCPU, this device name can be used on FX3U(C)CPU only.
*12 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.
*13 The device is not available in LHCPU.

2 CONTROLS
2.3 Device Types 55
 When access target is RCPU or LHCPU
The devices described in the following table can be used when access target is RCPU or LHCPU.
Device Device name Device type Device number
*1
Long timer Contact LTS Bit device Decimal
Coil LTC Bit device Decimal
Present value LTN Double word device Decimal
Long counter*1 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

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

When access target is RnSFCPU (Safety devices)

The safety devices described in the following table can be used when access target is RnSFCPU.
The safety mode is read-only. An attempt to write into the safety device will cause an error.
Device Device name Device type Device number
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 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.
Device Device name Device type Device number
Motion registers # Word device Decimal

2 CONTROLS
56 2.3 Device Types
When access target is FX5CPU
The devices described in the following table can be used when access target is FX5CPU.
Device Device name Device type Device number
Special relay SM Bit device Decimal
Special register SD Word device Decimal 2
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
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

2 CONTROLS
2.3 Device Types 57
 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.
These devices cannot be used for other communication routes.
Device Device name Device type Device number Remarks
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.
These devices cannot be used for other communication routes.
Device Device name Device type Device number Remarks
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
Buffer memory ML Word device Hexadecimal Buffer memory of own board

2 CONTROLS
58 2.3 Device Types
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.
These devices cannot be used for other communication routes.
Device Device name Device type Device number Remarks 2
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)
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
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 gateway function communication

This section explains how to specify the device name used for gateway function communication.
For specifying devices used for other communication, refer to the following manual.
MX Component Version 4 Operating Manual
Device Device name Device type Device number
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 monitor types used for inverter communication/robot controller communication, refer to the following manual.
MX Component Version 4 Operating Manual

2 CONTROLS
2.3 Device Types 59
 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.

2 CONTROLS
60 2.3 Device Types
2.4 Accessible Ranges
For the ranges that can be accessed in each communication, refer to the following manual.
MX Component Version 4 Operating Manual

2 CONTROLS
2.4 Accessible Ranges 61
 3 PROPERTIES OF CONTROLS
This chapter explains the property list of controls and details of the respective controls.

3.1 Property List

The following table shows the properties of each control.
Control name Property name
ACT Control ActUtlType ActLogicalStationNumber
ActMLUtlType
ActPassword
ActUtlDataLogging
ActProgType ActATCommand*1
ActMLProgType ActATCommandPasswordCancelRetryTimes*1
ActProgDataLogging
ActATCommandResponseWaitTime*1
ActBaudRate
ActCallbackCancelWaitTime*1
ActCallbackDelayTime*1
ActCallbackNumber*1
ActCallbackReceptionWaitingTimeOut*1
ActConnectionCDWaitTime*1
ActConnectionModemReportWaitTime*1
ActConnectUnitNumber
ActConnectWay*1
ActControl
ActCpuTimeOut
ActCpuType
ActDataBits
ActDestinationIONumber
ActDestinationPortNumber
ActDialNumber*1
ActDidPropertyBit
ActDisconnectionCDWaitTime*1
ActDisconnectionDelayTime*1
ActDsidPropertyBit
ActHostAddress
ActIntelligentPreferenceBit
ActIONumber
ActLineType*1
ActMultiDropChannelNumber
ActMxUnitSeries*2
ActNetworkNumber
ActOutsideLineNumber*1
ActPacketType
ActParity
ActPassword

3 PROPERTIES OF CONTROLS
62 3.1 Property List
Control name Property name
ACT Control ActProgType ActPasswordCancelResponseWaitTime*1
ActMLProgType ActPortNumber
ActProgDataLogging
ActProtocolType
ActSourceNetworkNumber
ActSourceStationNumber
ActStationNumber
ActStopBits
ActSumCheck
ActTargetSimulator
3
ActThroughNetworkType
ActTimeOut
ActTransmissionDelayTime*1
ActUnitNumber
ActUnitType
ActSupportMsg 
ActMLSupportMsg
.NET Control DotUtlType ActLogicalStationNumber
ActPassword
DotSupportMsg 

*1 A property for modem communication. It can only be used for ActProgType.

*2 The property value is set automatically, and it cannot be changed.

3 PROPERTIES OF CONTROLS
3.1 Property List 63
 3.2 Details of Control Properties
This section explains the details of properties set when creating a user application.

Properties of utility setting type controls

The following table shows the properties of the Act(ML)UtlType control and the DotUtlType control.
Property name (Type) Description Default value
ActLogicalStationNumber(LONG) A logical station number set in Communication Setup Utility. (Applicable setting range: 0 to 1023) 0(0x00)
ActPassword(BSTR) Specify a password to disable the password set to the password protected modules.*1*2*3 Empty
This setting is ignored when a password protected module is not used.

*1 The setting of ActPassword is not necessary if a password is not set.

*2 Characters exceeded the maximum number of characters for the password are ignored.
*3 If characters other than alphanumeric are 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 Act(ML)ProgType control.
Property name (Type) Description Default value
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,
QJ61BT11).
■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,
QJ61BT11).
■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.

3 PROPERTIES OF CONTROLS
64 3.2 Details of Control Properties
Property name (Type) Description Default value
ActCpuType(LONG) When the ActMxUnitSeries property is set to '0' (programmable controller/motion controller) 34(CPU_Q02CP
Specify the target CPU to communicate with. U)
In the parameter, specify the CPU type in the following table.
Page 68 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.
In the parameter, specify the CPU type in the following table.
Page 70 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.
3
In the parameter, specify the CPU type in the following table.
Page 70 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 71 ActPortNumber(LONG)
ActBaudRate(LONG) Specify the baud rate for serial communication. 19200(BAUDRA
■Property value (Property window input value) TE_19200)
BAUDRATE_300 (300): 300bps
BAUDRATE_600 (600): 600bps
BAUDRATE_1200 (1200): 1200bps
BAUDRATE_2400 (2400): 2400bps
BAUDRATE_4800 (4800): 4800bps
BAUDRATE_9600 (9600): 9600bps
BAUDRATE_19200 (19200): 19200bps
BAUDRATE_38400 (38400): 38400bps
BAUDRATE_57600 (57600): 57600bps
BAUDRATE_115200 (115200): 115200bps
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(ODD_PARITY)
■Property value (Property window input value)
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(STOPBIT_ON
■Property value (Property window input value) E)
STOPBIT_ONE (0): 1 stop bit
STOPBITS_TWO (2): 2 stop bits
For robot controller, specify the following setting.
■Property value (Property window input value)
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(TRC_DTR_O
Page 71 ActControl(LONG) R_RTS)
ActHostAddress(BSTR) Pointer which indicates the connection host name (IP address) for Ethernet communication. 1.1.1.1
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)

3 PROPERTIES OF CONTROLS
3.2 Details of Control Properties 65
 Property name (Type) Description Default value
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)
A time-out processing may be performed internally depending on the communication route in MX
Component.
For details, refer to the following section.
Page 588 Time-Out Periods
ActSumCheck(LONG) Specify whether sum check is applied or not. 0(NO_SUM_CH
This setting is valid for serial communication module only. ECK)
■Property value (Property window input value)
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.

3 PROPERTIES OF CONTROLS
66 3.2 Details of Control Properties
Property name (Type) Description Default value
ActPacketType(LONG)*2 Specify whether CR/LF exists or not. 1(CRLF_CR)
■Property value (Property window input value)
CRLF_NONE (0): Without CR/LF
CRLF_CR (1): With CR
CRLF_CRLF (2): With CR/LF
ActPassword(BSTR)*3 Specify a password to disable the password set to the password protected modules.*4*5*6 Empty
This setting is ignored when a password protected module is not used.
ActConnectWay(LONG)*7 Set the connection system. 0(TEL_AUTO_C
Page 71 ActConnectWay(LONG) ONNECT)
ActATCommand(BSTR)*7 Specify the AT command that initializes the modem. Empty 3
If no value (do not enter the property value) is set, the modem-standard AT command is used.
Up to 70 characters can be set.*8
ActDialNumber(BSTR)*7 Specify the telephone number. Up to 50 characters can be set.*8 Empty
(The characters that can be set are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, -, *, #)
ActOutsideLineNumber(BSTR)*7 Specify the number to access the outside line. Up to 10 characters can be set. Empty
(The characters that can be set are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, -, *, #)
ActCallbackNumber(BSTR)*7 Specify the callback telephone number.*8 Empty
Up to 62 characters can be set. (The characters that can be set are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, -, *,
#)
The setting of the connection system is not necessary when the connection system
(ActConnectWay) is other than auto line connect (callback number specification), callback
connect (number specification), or callback request (number specification).
ActLineType(LONG)*7 Recognize the line type. 1(LINETYPE_T
Page 71 ActLineType(LONG) ONE)
ActConnectionCDWaitTime(LONG)*7 Line connection CD signal confirmation time 90
Set the time for watching the ON/OFF of the CD signal line when the line is connected.
(Applicable setting range: 1 to 999, unit: seconds)
Increase the set time if the CD signal does not turn ON within the preset time depending on the
line-connected region (Example: overseas).
ActConnectionModemReportWaitTime Line connection modem waiting time 5
(LONG)*7 Set the waiting time for a result code response from the modem after line connection. (Applicable
setting range: 1 to 999, unit: seconds)
Increase the set time if the response speed of the modem is slow.
ActDisconnectionCDWaitTime(LONG)* Line disconnection CD signal confirmation time 5
7 Set the time for watching the ON/OFF of the CD signal line when the line is disconnected.
(Applicable setting range: 1 to 999, unit: seconds)
Increase the set time if the CD signal does not turn OFF within the preset time depending on the
line-connected region (Example: overseas).
ActDisconnectionDelayTime(LONG)*7 Line disconnection delay time 3
Set the guard time (no communication time) of the escape command sent to the modem.
(Applicable setting range: 1 to 999, unit: seconds)
Increase the set time if the response speed of the modem is slow.
ActTransmissionDelayTime(LONG)*7 Data send delay time 0
Set the time to be provided before the AT command is sent. (Applicable setting range: 0 to 999,
unit: seconds)
Increase the set time if the error code (0xF2100008) is returned even though the correct AT
command is set.
Increase the set time if the response speed of the modem is slow.
ActATCommandResponseWaitTime(L AT command send response waiting time (Applicable setting range: 1 to 999, unit: seconds) 1
ONG)*7 Increase the set time if the response speed of the modem is slow.
ActPasswordCancelResponseWaitTim Password cancel response waiting time (Applicable setting range: 1 to 999, unit: seconds) 5
e(LONG)*7 Increase the set time if the quality of the line with the other end is low.
ActATCommandPasswordCancelRetry AT command/password cancel send retry count 3
Times(LONG)*7 (Applicable setting range: 1 to 999, unit: number of times)
ActCallbackCancelWaitTime(LONG)*7 Callback line disconnection waiting time (Applicable setting range: 1 to 180, unit: seconds) 90
Increase the set time if the line at the other end (Q series-compatible C24) is not disconnected
within the preset time depending on the line-connected region (Example: overseas).
The setting is not necessary when the connection system (ActConnectWay) is other than callback
connect or callback request.
ActCallbackDelayTime(LONG)*7 Callback execution delay time (Applicable setting range: 1 to 999, unit: seconds) 20
Increase the set time if the device for relaying connection to the line (Example: modem or like)
requires the predetermined time for reconnection after line disconnection.
The setting is not necessary when the connection system (ActConnectWay) is other than callback
connect or callback request.

3 PROPERTIES OF CONTROLS
3.2 Details of Control Properties 67
 Property name (Type) Description Default value
ActCallbackReceptionWaitingTimeOut( Callback receive waiting time-out period (Applicable setting range: 1 to 3600, unit: seconds) 120
LONG)*7 Set the waiting time for a telephone line connection request from Q series-compatible C24 in a
callback receive waiting status.
If the set time elapsed, the callback reception waiting status is exited, and since the connection of
the telephone line was not completed, the Connect function is terminated abnormally.
The setting is not necessary when the connection system (ActConnectWay) is other than callback
reception waiting.
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
3 (0x03): Simulator No.3
4 (0x04): Simulator No.4
ActUnitType(LONG) Specify the module type connected to the physical port. 0x13(UNIT_QN
Page 72 ActUnitType(LONG) CPU)
ActProtocolType(LONG) Specify the communication protocol type of the module (board) to be connected. 0x04(PROTOCO
Page 74 ActProtocolType(LONG) L_SERIAL)

*1 For details, refer to the following manual.

Q Corresponding Ethernet Interface Module User's Manual (Basic)
*2 This property can be used for inverter communication.
*3 This property can be used for Ethernet communication.
*4 The setting of ActPassword is not necessary if a password is not set.
*5 Characters exceeded the maximum number of characters for the password are ignored.
*6 If a character other than alphanumeric is specified, a character code conversion error (0xF1000001) occurs at the execution of the Open
function.
*7 This property can be used for modem communication. It cannot be used for ActMLProgType control.
*8 If the characters entered exceed the limit of set characters, the characters outside the setting range are ignored.

■ActCpuType(LONG): When the ActMxUnitSeries property is set to '0' (programmable

controller/motion controller)
Property value (Property window input value) Target CPU
CPU type Dec. Hex.
CPU_R00CPU 4609 0x1201 R00CPU
CPU_R01CPU 4610 0x1202 R01CPU
CPU_R02CPU 4611 0x1203 R02CPU
CPU_R04CPU 4097 0x1001 R04CPU
CPU_R04ENCPU 4104 0x1008 R04ENCPU
CPU_R08CPU 4098 0x1002 R08CPU
CPU_R08ENCPU 4105 0x1009 R08ENCPU
CPU_R08PCPU 4354 0x1102 R08PCPU
CPU_R08PSFCPU 4369 0x1111 R08PSFCPU
CPU_R08SFCPU 4386 0x1122 R08SFCPU
CPU_R16CPU 4099 0x1003 R16CPU
CPU_R16ENCPU 4106 0x100A R16ENCPU
CPU_R16PCPU 4355 0x1103 R16PCPU
CPU_R16PSFCPU 4370 0x1112 R16PSFCPU
CPU_R16SFCPU 4387 0x1123 R16SFCPU
CPU_R32CPU 4100 0x1004 R32CPU
CPU_R32ENCPU 4107 0x100B R32ENCPU

3 PROPERTIES OF CONTROLS
68 3.2 Details of Control Properties
Property value (Property window input value) Target CPU
CPU type Dec. Hex.
CPU_R32PCPU 4356 0x1104 R32PCPU
CPU_R32PSFCPU 4371 0x1113 R32PSFCPU
CPU_R32SFCPU 4388 0x1124 R32SFCPU
CPU_R120CPU 4101 0x1005 R120CPU
CPU_R120ENCPU 4108 0x100C R120ENCPU
CPU_R120PCPU 4357 0x1105 R120PCPU
CPU_R120PSFCPU
CPU_R120SFCPU
4372
4389
0x1114
0x1125
R120PSFCPU
R120SFCPU
3
CPU_R16MTCPU 4113 0x1011 R16MTCPU
CPU_R32MTCPU 4114 0x1012 R32MTCPU
CPU_R12CCPU_V 4129 0x1021 R12CCPU-V
CPU_L04HCPU 4625 0x1211 L04HCPU
CPU_L08HCPU 4626 0x1212 L08HCPU
CPU_L16HCPU 4627 0x1213 L16HCPU
CPU_Q00JCPU 48 0x30 Q00JCPU
CPU_Q00UJCPU 128 0x80 Q00UJCPU
CPU_Q00CPU 49 0x31 Q00CPU
CPU_Q00UCPU 129 0x81 Q00UCPU
CPU_Q01CPU 50 0x32 Q01CPU
CPU_Q01UCPU 130 0x82 Q01UCPU
CPU_Q02CPU 34 0x22 Q02(H)CPU
CPU_Q02PHCPU 69 0x45 Q02PHCPU
CPU_Q02UCPU 131 0x83 Q02UCPU
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_Q04UDVCPU 210 0xD2 Q04UDVCPU
CPU_Q06CPU 35 0x23 Q06HCPU
CPU_Q06PHCPU 70 0x46 Q06PHCPU
CPU_Q06UDHCPU 114 0x72 Q06UDHCPU
CPU_Q06UDEHCPU 146 0x92 Q06UDEHCPU
CPU_Q06UDVCPU 211 0xD3 Q06UDVCPU
CPU_Q10UDHCPU 117 0x75 Q10UDHCPU
CPU_Q10UDEHCPU 149 0x95 Q10UDEHCPU
CPU_Q12CPU 39 0x24 Q12HCPU
CPU_Q12PHCPU 65 0x41 Q12PHCPU
CPU_Q12PRHCPU 67 0x43 Q12PRHCPU
CPU_Q13UDHCPU 115 0x73 Q13UDHCPU
CPU_Q13UDEHCPU 147 0x93 Q13UDEHCPU
CPU_Q13UDVCPU 212 0xD4 Q13UDVCPU
CPU_Q20UDHCPU 118 0x76 Q20UDHCPU
CPU_Q20UDEHCPU 150 0x96 Q20UDEHCPU
CPU_Q25CPU 37 0x25 Q25HCPU
CPU_Q25PHCPU 66 0x42 Q25PHCPU
CPU_Q25PRHCPU 68 0x44 Q25PRHCPU
CPU_Q26UDHCPU 116 0x74 Q26UDHCPU
CPU_Q26UDEHCPU 148 0x94 Q26UDEHCPU
CPU_Q26UDVCPU 213 0xD5 Q26UDVCPU
CPU_Q50UDEHCPU 152 0x98 Q50UDEHCPU
CPU_Q100UDEHCPU 154 0x9A Q100UDEHCPU

3 PROPERTIES OF CONTROLS
3.2 Details of Control Properties 69
 Property value (Property window input value) Target CPU
CPU type Dec. Hex.
CPU_Q02CPU_A 321 0x141 Q02(H)CPU-A
CPU_Q06CPU_A 322 0x142 Q06HCPU-A
CPU_L02SCPU 163 0xA3 L02SCPU
CPU_L02CPU 161 0xA1 L02CPU
CPU_L06CPU 165 0xA5 L06CPU
CPU_L26CPU 164 0xA4 L26CPU
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_Q172CPU 1569 0x621 Q172CPU
CPU_Q173CPU 1570 0x622 Q173CPU
CPU_Q172HCPU 1569 0x621 Q172HCPU
CPU_Q173HCPU 1570 0x622 Q173HCPU
CPU_Q172DCPU 1573 0x625 Q172DCPU
CPU_Q173DCPU 1574 0x626 Q173DCPU
CPU_Q172DSCPU 1578 0x62A Q172DSCPU
CPU_Q173DSCPU 1579 0x62B Q173DSCPU
CPU_FX0CPU 513 0x201 FX0(S)CPU
CPU_FX0NCPU 514 0x202 FX0NCPU
CPU_FX1CPU 515 0x203 FX1CPU
CPU_FX1SCPU 518 0x206 FX1SCPU
CPU_FX1NCPU 519 0x207 FX1N(C)CPU
CPU_FX2CPU 516 0x204 FXUCPU
FX2CCPU
CPU_FX2NCPU 517 0x205 FX2N(C)CPU
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

3 PROPERTIES OF CONTROLS
70 3.2 Details of Control Properties
■ActPortNumber(LONG)
Property value (Property window input value) Description
Port number Dec. Hex.
PORT_1 1 0x01 Communication port 1
PORT_2 2 0x02 Communication port 2
PORT_3 3 0x03 Communication port 3
PORT_4 4 0x04 Communication port 4
PORT_5 5 0x05 Communication port 5
PORT_6 6 0x06 Communication port 6 3
PORT_7 7 0x07 Communication port 7
PORT_8 8 0x08 Communication port 8
PORT_9 9 0x09 Communication port 9
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

■ActConnectWay(LONG)
Property value (Property window input value) Connection system
Connection system Dec. Hex.
TEL_AUTO_CONNECT 0 0x00 Auto line connect
TEL_AUTO_CALLBACK 1 0x01 Auto line connect (Callback fixation)
TEL_AUTO_CALLBACK_NUMBER 2 0x02 Auto line connect (Callback number
specification)
TEL_CALLBACK 3 0x03 Callback connect (Fixation)
TEL_CALLBACK_NUMBER 4 0x04 Callback connect (Number
specification)
TEL_CALLBACK_REQUEST 5 0x05 Callback request (Fixation)
TEL_CALLBACK_REQUEST_NUMB 6 0x06 Callback request (Number
ER specification)
TEL_CALLBACK_WAIT 7 0x07 Callback reception waiting

■ActLineType(LONG)
Property value (Property window input value) Description
Line type Dec. Hex.
LINETYPE_PULSE 0 0x00 Pulse (Dial line)
LINETYPE_TONE 1 0x01 Tone (Push button line)
LINETYPE_ISDN 2 0x02 ISDN (ISDN line)

3 PROPERTIES OF CONTROLS
3.2 Details of Control Properties 71
 ■ActUnitType(LONG)
Module type Connection system Value
UNIT_RJ71C24 R series-compatible C24 module direct connection 0x1000
R series-compatible C24 connection via GOT2000/1000 series
UNIT_QJ71C24 Q series-compatible C24 module direct connection 0x19
Q series-compatible C24 connection via modem
Q series-compatible C24 connection via GOT2000/1000 series
UNIT_LJ71C24 L series-compatible C24 module direct connection 0x54
L series-compatible C24 connection via modem
L series-compatible C24 connection via GOT2000/1000 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_FXVCPU FX5CPU Serial port connection 0x2000
UNIT_QNCPU QCPU (Q mode) RS232C port direct connection 0x13
GOT2000/1000 series QCPU (Q mode) direct connection
UNIT_LNCPU LCPU RS232C port direct connection 0x50
GOT2000/1000 series LCPU direct connection
UNIT_QNMOTION Q motion CPU-RS232C port direct connection 0x1C
UNIT_FXCPU FXCPU-RS422 port direct connection 0x0F
FXCPU direct connection via modem
FXCPU USB direct connection
GOT2000/1000 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

3 PROPERTIES OF CONTROLS
72 3.2 Details of Control Properties
Module type Connection system Value
UNIT_SIMULATOR Simulator (GX Simulator) connection 0x0B
UNIT_SIMULATOR2*1 Simulator (GX Simulator 2) connection 0x30
Simulator (MT Simulator 2) connection
UNIT_SIMULATOR3 Simulator (GX Simulator 3) connection 0x31
UNIT_A900GOT GOT2000/1000/900 series connection 0x21
UNIT_GOT_RJ71EN71 R series-compatible E71 connection via GOT2000/1000 series 0x1051
UNIT_GOT_QJ71E71 Q series-compatible E71 connection via GOT2000/1000 series 0x40
UNIT_GOT_LJ71E71
UNIT_GOT_RETHER
L series-compatible E71 connection via GOT2000/1000 series
RCPU Ethernet port connection via GOT2000/1000 series
0x5D
0x1052
3
UNIT_GOT_QNETHER QCPU Ethernet port connection via GOT2000/1000 series 0x41
UNIT_GOT_LNETHER LCPU Ethernet port connection via GOT2000/1000 series 0x55
UNIT_GOT_NZ2GF_ETB Ethernet adapter module (NZ2GF-ETB) connection via GOT2000/1000 0x5B
series
UNIT_GOT_FXETHER FXCPU Ethernet adapter (FX3U-ENET-ADP) connection via GOT2000/ 0x61
1000 series
UNIT_GOT_FXENET FXCPU Ethernet module (FX3U-ENET(-L)) connection via GOT2000/ 0x62
1000 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/1000 series 0x1061
UNIT_GOTETHER_QNCPU QCPU (Q mode) Ethernet port (RS422) connection via GOT2000/1000 0x56
series
UNIT_GOTETHER_LNCPU LCPU Ethernet port (RS232C) connection via GOT2000/1000 series 0x57
UNIT_GOTETHER_FXCPU FXCPU Ethernet port connection via GOT2000/1000 series 0x60
UNIT_GOTETHER_QBUS Q series bus Ethernet port connection via GOT2000/1000 series 0x58
UNIT_GOTETHER_QN_ETHER GOT Ethernet transparent (Ethernet-GOT-Ethernet-QnCPU) 0x6F
connection
UNIT_QBF Bus connection 0x1F

*1 When the CPU type is Q motion CPU, connected to MT Simulator2. Other than that, connected to GX Simulator2.

3 PROPERTIES OF CONTROLS
3.2 Details of Control Properties 73
 ■ActProtocolType(LONG)
Communication protocol type Connection system Value
PROTOCOL_SERIAL Via serial port 0x04(4)
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_SERIALMODEM Via serial port and modem 0x0E(14)
PROTOCOL_TEL Via TEL 0x0A(10)
PROTOCOL_QBF Via Q series bus 0x10(16)
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).

3 PROPERTIES OF CONTROLS
74 3.2 Details of Control Properties
4 PROPERTY SETTINGS OF COMMUNICATION
ROUTES
This chapter explains the details of accessible communication routes and property settings.

4.1 Serial Communication

Serial communication when the connected station is R series-
compatible C24 (1)
4
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

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) (1)*1*3 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)  

Connected station CPU Relayed network Relayed station CPU

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)  (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 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.1 Serial Communication 75
 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)
ActBaudRate 19200(BAUDRATE_1 Match to the setting of R series-compatible C24.
9200)
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RT Depending on the used cable.
S)
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 1(ODD_PARITY)
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL
ERIAL)
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)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

76 4.1 Serial Communication
Property Default value Property patterns
(1) (2)*1 (3) (4)
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 4
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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.1 Serial Communication 77
 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

Connected station R Series -

CPU compatible C24
Multi-drop link
Relayed network

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
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

Connected station Relayed network Relayed station CPU

CPU
RCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
Independent (1) Serial communication (2)*3  (2)*3   
mode*1
Synchronous  (3)*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.
⋅CH1 side: Operation setting of Transmission setting = Independent (0), Communication protocol setting = 8
⋅CH2 side: Operation setting of Transmission setting = Synchronous (1), Communication protocol setting = 0
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.

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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

78 4.1 Serial Communication
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) (3)
ActBaudRate 19200(BAUDRATE_1 Match to the setting of R series-compatible C24.
9200)
ActConnectUnitNumber 0(0x00) Connected station side module station number Target station side module
station number
ActControl 8(TRC_DTR_OR_RT Depending on the used cable.
S)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station 4
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)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
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 1(ODD_PARITY)
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL
ERIAL)
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)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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) Target station side module Fixed to 0 (0x00)
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_RJ71C24

*1 For the I/O address, specify the value obtained by dividing the actual start I/O number by 16.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.1 Serial Communication 79
 *2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

80 4.1 Serial Communication
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

4
Relayed station Relayed module
Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station 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
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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) 
*4
Serial communication (3)  (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.
*4 For redundant CPU, serial communication modules on the main base cannot be accessed.
*5 Supported by FX3G(C)CPU and FX3U(C)CPU within the own network only.
*6 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.1 Serial Communication 81
 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)
ActBaudRate 19200(BAUDRATE_1 Match to the setting of Q series-compatible C24.
9200)
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RT Depending on the used cable.
S)
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
• Control system: 976
(0x3D0)
• 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)
ActHostAddress 1.1.1.1 Fixed to NULL
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
*2 1023(0x3FF) ■For single CPU Target station side
ActIONumber Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
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) Match to the setting of Q series-compatible C24.
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

82 4.1 Serial Communication
Property Default value Property patterns
(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
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 of the actual start I/O number divided 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
4

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.1 Serial Communication 83
 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

Connected station Q Series -

CPU compatible C24
Multi-drop link
Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
QCPU (Q mode), RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU*3
Independent (1)*2 Serial communication     
mode*1
Synchronous      
mode*1

Connected station Relayed network Relayed station CPU

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

*1 Indicates the CH2 side setting. (The CH1 side is fixed to the independent mode.)
*2 For redundant CPU, serial communication modules on the main base cannot be accessed.
*3 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

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-
compatible C24 parameter.
If it is invalidated (OFF), a communication error occurs and the communication is disabled.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

84 4.1 Serial Communication
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) (3)
ActBaudRate 19200(BAUDRATE_19200) Match to the setting of Q series-compatible C24.
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00)
■For single CPU
Fixed to 1023 (0x3FF) 4
■For multiple CPUs
• Connected CPU: 1023
(0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification: 1023
(0x3FF)
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)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
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
■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*2 0(0x00) Fixed to 0 (0x00) Multi-drop channel number Fixed to 0 (0x00)
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Match to the setting of Q series-compatible C24.
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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) Target station side module Fixed to 0 (0x00)
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_QJ71C24(0x19)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.1 Serial Communication 85
 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

Connected station L Series -

Relayed module
CPU compatible C24

Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*1     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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)   
Serial communication (2)*3  (2)   
CC-Link (3) (3) (3)   

*1 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

86 4.1 Serial Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_192 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
00) BAUDRATE_115200
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 8 (DATABIT_8)
4
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
■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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Fixed to NULL
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
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)
■For multiple CPUs
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
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)
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERI PROTOCOL_SERIAL(0x04)
AL)
ActSourceNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActSourceStationNumber 0(0x00) Fixed to 0 (0x00)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.1 Serial Communication 87
 Property Default value Property patterns
(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)
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) Target station side Target station side Fixed to 0 (0x00)
module station module station
number number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LJ71C24(0x54)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

88 4.1 Serial Communication
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

Connected station L Series -

CPU compatible C24
Multi-drop link
Relayed network

4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
Independent (1)*3 Serial communication     
mode*1
Synchronous      
mode*2

Connected station Relayed network Relayed station CPU

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.

⋅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.
⋅CH1 side: Operation setting of Transmission setting = Independent (0), Communication protocol setting = 8
⋅CH2 side: Operation setting of Transmission setting = Synchronous (1), Communication protocol setting = 0
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.

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-
compatible C24 parameter.
If it is invalidated (OFF), a communication error occurs and the communication is disabled.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.1 Serial Communication 89
 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) (3)
ActBaudRate 19200(BAUDRATE_19200) Match to the setting of L series-compatible C24.
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
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)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*1 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side Target station side
relayed module I/O address ■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)
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) Match to the setting of L series-compatible C24.
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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) Target station side module Fixed to 0 (0x00)
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LJ71C24(0x54)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

90 4.1 Serial Communication
Serial communication when the connected station is FX extended
port

Configuration

Connected station FX extended port

CPU

Relayed network

Personal computer
Relayed station
CPU
FX extended port Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 FX0CPU, FX0SCPU, FX1CPU, FXUCPU, and FX2CCPU cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.1 Serial Communication 91
 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)
ActBaudRate 19200(BAUDRATE_19200) Match to the setting of FX extended port
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuTimeOut 0(0x00) Any value specified by user in 10ms units
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Match to the setting of FX extended port
ActParity 1(ODD_PARITY) Match to the setting of FX extended port
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
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
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Target station side module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FX485BD(0x24)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

92 4.1 Serial Communication
4.2 Ethernet Communication
Ethernet communication when the connected station is R series-
compatible E71 (TCP)

Configuration

Connected station R Series -

Relayed module
CPU compatible E71

Relayed network
4
Relayed station Relayed module
Personal computer
CPU

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) (1)*1*2 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet (2)  (2)  
Serial communication (3)  (3)  
CC-Link (4) (4) (4)  

Connected station CPU Relayed network Relayed station CPU

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

*1 Relayed station CPUs cannot be accessed via R motion CPU.

*2 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 93
 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)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*3 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)
ActDestinationPortNumber 0(0x00) 5002 for MELSOFT connection
Any port number for OPS connection.*2
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIONumber*3 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)
*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 Null Password set to R series-compatible E71 on the connected station side
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActPortNumber 1(PORT_1) Personal computer side port number
ActBaudRate 19200(BAUDRATE_1 Fixed to 0 (0x00)
9200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RT Fixed to 0 (0x00)
S)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

94 4.2 Ethernet Communication
Property Default value Property patterns
(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)
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_RJ71EN71(0x1001)

*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-
4
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 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)
*3 For the I/O address, specify the value obtained by dividing the actual start I/O number by 16.
*4 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
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 station number on the personal computer side to avoid the same station number set for R series-compatible E71 within the
same Ethernet loop.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 95
 Ethernet communication when the connected station is R series-
compatible E71 (UDP)

Configuration

Connected station R Series -

Relayed module
CPU compatible E71

Relayed network

Relayed station Relayed module

Personal computer
CPU

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)*1 (1)*2*3 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet (2)  (2)  
Serial communication (3)  (3)  
CC-Link (4) (4) (4)  

Connected station CPU Relayed network Relayed station CPU

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

*1 Relayed station CPUs cannot be accessed when directly connecting to an R series-compatible E71.
*2 Relayed station CPUs cannot be accessed via R motion CPU.
*3 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

96 4.2 Ethernet Communication
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)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*2 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)
■For multiple CPUs
(0x3FF)
■For multiple CPUs
4
• 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)
ActDestinationPortNumber 0(0x00) For communication with IP address specified: 5001
For direct communication without IP address specified: 5003
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)
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
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*4 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 Null 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_S PROTOCOL_UDPIP(0x08)
ERIAL)
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActBaudRate 19200(BAUDRATE_1 Fixed to 0 (0x00)
9200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RT Fixed to 0 (0x00)
S)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK) Fixed to 0 (0x00)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 97
 Property Default value Property patterns
(1) (2)*1 (3) (4)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActSourceNetworkNumber 0(0x00) Personal computer side network number
ActSourceStationNumber*5 0(0x00) Personal computer side station number
ActStationNumber*4 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)
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) • For communication with IP address specified: UNIT_RJ71EN71(0x1001)
• For direst communication without IP address specified: UNIT_RJ71EN71_DIRECT(0x1005)

*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
*4 When the property pattern is (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.
*5 Specify the station number on the personal computer side to avoid the same station number set for R series-compatible E71 within the
same Ethernet loop.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

98 4.2 Ethernet Communication
Ethernet communication when the connected station is Q series-
compatible E71 (TCP)

Configuration

Connected station Q Series - Relayed module

CPU compatible E71

Relayed network

Personal computer Relayed station

CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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      
*3 *4 *2*3 *3
CC IE Control (2) (2) (2) (2) (2) 
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 Relayed stations cannot be accessed when the Q motion CPU is Q172CPU, Q173CPU, Q172HCPU, or Q173HCPU.
*2 Relayed station CPUs cannot be accessed via QSCPU or Q motion CPU.
*3 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.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 For redundant CPU, serial communication modules on the main base cannot be accessed.
*6 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 99
 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) (3) (4)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) 5002 for MELSOFT connection
Any port number for OPS connection*1
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
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*4 0(0x00) Target station side Target station side Connected station side Connected station side
module network module network Q series-compatible Q series-compatible
number number E71 network number E71 network number
ActPassword Null Password set to Q series-compatible E71 on the connected station side
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
ActSourceNetworkNumber 0(0x00) Personal computer side network number
*5
ActSourceStationNumber 0(0x00) Personal computer side station number
ActStationNumber*4 255(0xFF) Target station side Target station side Connected station side Connected station side
module station number module station number Q series-compatible Q series-compatible
E71 network number E71 network 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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

100 4.2 Ethernet Communication
Property Default value Property patterns
(1) (2) (3) (4)
ActUnitType 0x13(UNIT_QNCPU) UNIT_QJ71E71(0x1A)

*1 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)
*2 For the I/O address, specify the value of the actual start I/O number divided 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
*4 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.
*5 Specify the station number on the personal computer side to avoid the same station number set for Q series-compatible E71 within the
same Ethernet loop.
4

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 101
 Ethernet communication when the connected station is Q series-
compatible E71 (UDP)

Configuration

Connected station Q Series - Relayed module

CPU compatible E71

Relayed network

Personal computer Relayed station Relayed module

CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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      
*3 *4 *2*3 *3
CC IE Control (2) (2) (2) (2) (2) 
CC IE Field
MELSECNET/H (2) (2)  (2)*2 (2) 
*2
Ethernet (2)   (2) (2) 
Serial communication (3)*5  (3)*5  (3) 
CC-Link (4) (4) (4)  (4) 

*1 Relayed stations cannot be accessed when the Q motion CPU is Q172CPU, Q173CPU, Q172HCPU, or Q173HCPU.
*2 Relayed station CPUs cannot be accessed via QSCPU or Q motion CPU.
*3 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.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 For redundant CPU, serial communication modules on the main base cannot be accessed.
*6 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*7 Since QCCPU is not supported by MELSOFT direct connection, Ethernet port direct connection is not applicable.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

102 4.2 Ethernet Communication
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) (3) (4)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
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)
■For multiple CPUs
(0x3FF)
■For multiple CPUs
4
• 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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) 5001
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIONumber*1 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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
1023 (0x3FF) • No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2 number
ActNetworkNumber*3 0(0x00) Target station side Target station side Connected station side Connected station side
module network module network Q series-compatible Q series-compatible
number number E71 network number E71 network number
ActPassword Null Password set to Q series-compatible E71 on the connected station side
ActPortNumber*4 1(PORT_1) Personal computer side port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_UDPIP(0x08)
ERIAL)
ActSourceNetworkNumber 0(0x00) Personal computer side network number
ActSourceStationNumber*5 0(0x00) Personal computer side station number
ActStationNumber*3 255(0xFF) Target station side Target station side Connected station side Connected station side
module station number module station number Q series-compatible Q series-compatible
E71 network number E71 network 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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 103
 Property Default value Property patterns
(1) (2) (3) (4)
ActUnitType 0x13(UNIT_QNCPU) UNIT_QJ71E71(0x1A)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*3 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.
*4 Do not use 1 to 1024 of ActPortNumber.
*5 Specify the station number on the personal computer side to avoid the same station number set for Q series-compatible E71 within the
same Ethernet loop.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

104 4.2 Ethernet Communication
Ethernet communication when the connected station is L series-
compatible E71 (TCP)

Configuration

Connected station L Series -

Relayed module
CPU compatible E71

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connect Relayed network Relayed station CPU
ed
station
CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connect Relayed network Relayed station CPU

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

*1 Only Q172D, Q173D, Q172DS and Q173DS can be accessed.

*2 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 105
 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) (3) (4)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActControl 8(TRC_DTR_OR_RT Fixed to 0 (0x00)
S)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) 5002 for MELSOFT connection
Any port number for OPS connection*1
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
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*4 0(0x00) Target station side Target station side Connected station side Connected station side
module network module network L series-compatible L series-compatible
number number E71 network number E71 network number
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActPassword Null Password set to L series-compatible E71 on the connected station side
ActPortNumber 1(PORT_1) Personal computer side port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
ActSourceNetworkNumber 0(0x00) Personal computer side network number
*5 0(0x00) Personal computer side station number
ActSourceStationNumber

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

106 4.2 Ethernet Communication
Property Default value Property patterns
(1) (2) (3) (4)
*4
ActStationNumber 255(0xFF) Target station side Target station side Connected station side Connected station side
module station number module station number L series-compatible L series-compatible
E71 station number E71 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_LJ71E71(0x5C)

*1 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)
*2 For the I/O address, specify the value of the actual start I/O number divided by 16. 4
*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
*4 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.
*5 Specify the station number on the personal computer side to avoid the same station number set for L series-compatible E71 within the
same Ethernet loop.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 107
 Ethernet communication when the connected station is L series-
compatible E71 (UDP)

Configuration

Connected station L Series -

Relayed module
CPU compatible E71

Relayed network

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connect Relayed network Relayed station CPU
ed
station
CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connect Relayed network Relayed station CPU

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

*1 Only Q172D, Q173D, Q172DS and Q173DS can be accessed.

*2 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

108 4.2 Ethernet Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActControl 8(TRC_DTR_OR_RT Fixed to 0 (0x00)
S)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station 4
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) 5001
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
*1
ActIONumber 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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
1023 (0x3FF) • No specification:
1023 (0x3FF)
ActMultiDropChannelNumb 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
er*2 number
ActNetworkNumber*3 0(0x00) Target station side Target station side Connected station side Connected station side
module network module network L series-compatible L series-compatible
number number E71 network number E71 network number
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActPassword Null Password set to L series-compatible E71 on the connected station side
*4
ActPortNumber 1(PORT_1) Personal computer side port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_UDPIP(0x08)
ERIAL)
ActSourceNetworkNumber 0(0x00) Personal computer side network number
ActSourceStationNumber*5 0(0x00) Personal computer side station number

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 109
 Property Default value Property patterns
(1) (2) (3) (4)
*3
ActStationNumber 255(0xFF) Target station side Target station side Connected station side Connected station side
module station number module station number L series-compatible L series-compatible
E71 station number E71 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_LJ71E71(0x5C)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*3 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.
*4 Do not use 1 to 1024 of ActPortNumber.
*5 Specify the station number on the personal computer side to avoid the same station number set for L series-compatible E71 within the
same Ethernet loop.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

110 4.2 Ethernet Communication
Ethernet communication when the connected station is RCPU
(TCP)

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station 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
MELSECNET/H     
Ethernet (2)*4  (2)*4  
Serial communication (3)*4  (3)*4  
CC-Link (4) (4) (4)  (4)

Connected station CPU Relayed network Relayed station CPU

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)   
Serial communication (3)*4  (3)*4   
CC-Link (4)*4  (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 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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 111
 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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActBaudRate 19200(BAUDRATE_1 Fixed to 0 (0x00)
9200)
ActControl 8(TRC_DTR_OR_RT Fixed to 0 (0x00)
S)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActDestinationIONumber*2 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)
ActDestinationPortNumber 0(0x00) 5007
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
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)
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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• 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*4 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActPassword Null Password set to the connected station side
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
ActStationNumber*4 255(0xFF) Fixed to 255 (0xFF) Target station side Fixed to 255 (0xFF) Fixed to 255 (0xFF)
module station number

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

112 4.2 Ethernet Communication
Property Default value Property patterns
(1) (2)*1 (3) (4)
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00) MELSECNET/10 is not
• MELSECNET/10 is included.: 1 (0x01) included.: 0 (0x00)
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_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". 4
*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
*4 When the property pattern is (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 113
 Ethernet communication when the connected station is RCPU
(UDP)

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station 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
MELSECNET/H     
Ethernet (2)*4  (2)*4  
Serial communication (3)*4  (3)*4  
CC-Link (4) (4) (4)  (4)

Connected station CPU Relayed network Relayed station CPU

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)   
Serial communication (3)*4  (3)*4   
CC-Link (4)*4  (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 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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

114 4.2 Ethernet Communication
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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActBaudRate 19200(BAUDRATE_1 Fixed to 0 (0x00)
9200)
ActControl 8(TRC_DTR_OR_RT Fixed to 0 (0x00)
S)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00) 4
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActDestinationIONumber*2 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) 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)
ActHostAddress 1.1.1.1 • For communication with IP address specified: Host name or IP address of the connected station
side
• For direst 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
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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• 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*4 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActPassword Null Password set to the connected station side

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 115
 Property Default value Property patterns
(1) (2)*1 (3) (4)
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_UDPIP(0x08)
ERIAL)
ActStationNumber*4 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 not
• MELSECNET/10 is included.: 1 (0x01) included.: 0 (0x00)
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) • For communication with IP address specified: UNIT_RETHER(0x1002)
• For direst communication without IP address specified: UNIT_RETHER_DIRECT(0x1003)

*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
*4 When the property pattern is (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

116 4.2 Ethernet Communication
Ethernet communication when the connected station is LHCPU
(TCP)

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LHCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 117
 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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActBaudRate 19200(BAUDRATE_19200) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RTS) Fixed to 0 (0x00)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00)
ActDestinationPortNumber 0(0x00) 5007
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber 1023(0x3FF) ■For single CPU
Fixed to 1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00)
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActPassword Null Remote password set to the connected station
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_TCPIP(0x05)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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)
ActUnitType 0x13(UNIT_QNCPU) UNIT_LHETHER(0x1002)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

118 4.2 Ethernet Communication
Ethernet communication when the connected station is LHCPU
(UDP)

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LHCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 119
 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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActBaudRate 19200(BAUDRATE_19200) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RTS) Fixed to 0 (0x00)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00)
ActDestinationPortNumber 0(0x00) • For communication with IP address specified: 5006
• For direct communication without IP address specified: 5008
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 • For communication with IP address specified: Host name or IP address of
the connected station side module
• For direct communication without IP address specified: 255.255.255.255
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber 1023(0x3FF) ■For single CPU
Fixed to 1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00)
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActPassword Null Remote password set to the connected station
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_UDPIP(0x08)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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)
ActUnitType 0x13(UNIT_QNCPU) • For communication with IP address specified: UNIT_LHETHER(0x1002)
• For direst communication without IP address specified:
UNIT_LHETHER_DIRECT(0x1003)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

120 4.2 Ethernet Communication
Ethernet communication when the connected station is FX5CPU
(TCP)

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FX5CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     (3)

Connected Relayed network Relayed station CPU

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

*1 Only CC-Link IE Field Network can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 121
 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) (3)
ActBaudRate 19200(BAUDRATE_19200) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RTS) Fixed to 0 (0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) 1023(0x3FF)
ActDestinationPortNumber 0(0x00) 5562
ActDidPropertyBit 1(0x01) 1(0x01) 0(0x00)
ActDsidPropertyBit 1(0x01) 1(0x01) 0(0x00)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
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
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActPassword Null Remote password set to the connected station
ActPortNumber 1(PORT_1) 0(0x00)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_TCPIP(0x05)
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)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) 0(0x00) Target station side module
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXVETHER(0x2001)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

122 4.2 Ethernet Communication
Ethernet communication when the connected station is FX5CPU
(UDP)

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FX5CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     (3)

Connected Relayed network Relayed station CPU

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

*1 Only CC-Link IE Field Network can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 123
 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) (3)
ActBaudRate 19200(BAUDRATE_19200) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RTS) Fixed to 0 (0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) 1023(0x3FF)
ActDestinationPortNumber 0(0x00) 5560
ActDidPropertyBit 1(0x01) 1(0x01) 0(0x00)
ActDsidPropertyBit 1(0x01) 1(0x01) 0(0x00)
ActHostAddress 1.1.1.1 255.255.255.255
To select an adapter of the PLC side, assign a tab and the IP address of the personal
computer-side after the IP address of the connection target.
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) 1(0x01)
ActIONumber 1023(0x3FF) 1023(0x3FF) Module number of the
connected station
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side module Fixed to 0 (0x00)
network number
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActPassword Null Remote password set to the connected station
ActPortNumber 1(PORT_1) 0(0x00)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_UDPIP(0x08)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Target station side module Fixed to 255 (0xFF)
station number
ActStopBits 0(STOPBIT_ONE) 0(0x00)
ActSumCheck 0(NO_SUM_CHECK) 0(0x00)
ActThroughNetworkType 0(0x00) 1(0x01) Fixed to 0 (0x00)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side module
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXVETHER_DIRECT(0x2002)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

124 4.2 Ethernet Communication
Ethernet communication when the connected station is built-in
Ethernet port QCPU (TCP)

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
QnUDE(H)CPU RCPU RCCPU R motion CPU*4 LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU
QnUDE(H)CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
(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) 
Serial communication (3)*3  (3)  (3) 
CC-Link (4) (4) (4)  (4) 

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 125
 Connected Relayed network Relayed station CPU
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
MELSECNET/H (2) (2)  (2) (2) 
Ethernet      
Serial communication      
CC-Link (4) (4) (4)  (4) 

Connected Relayed network Relayed station CPU

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

Connected Relayed network Relayed station CPU

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

*1 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.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.
*4 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*5 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.
*6 Since QCCPU is not supported by MELSOFT direct connection, Ethernet port direct connection is not applicable.
*7 For Q172D, Q173D, Q172DS, and Q173DS, only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

126 4.2 Ethernet Communication
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) (3) (4)
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) 4
• 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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) 5007
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
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)
ActIONumber*1 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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber*3 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActPassword Null Remote password set to the connected station
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
ActStationNumber*3 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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 127
 Property Default value Property patterns
(1) (2) (3) (4)
ActUnitType 0x13(UNIT_QNCPU) UNIT_QNETHER(0x2C)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*3 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

128 4.2 Ethernet Communication
Ethernet communication when the connected station is built-in
Ethernet port QCPU (UDP)

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
QnUDE(H)CPU RCPU RCCPU R motion CPU*4 LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU
QnUDE(H)CPU QCPU (Q 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) 
Serial communication (3)*3  (3)  (3) 
CC-Link (4) (4) (4)  (4) 

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 129
 Connected Relayed network Relayed station CPU
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) 
Ethernet      
Serial communication      
CC-Link (4) (4) (4)  (4) 

Connected Relayed network Relayed station CPU

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

Connected Relayed network Relayed station CPU

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

*1 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.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.
*4 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*5 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.
*6 Since QCCPU is not supported by MELSOFT direct connection, Ethernet port direct connection is not applicable.
*7 For Q172D, Q173D, Q172DS, and Q173DS, only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

130 4.2 Ethernet Communication
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) (3) (4)
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) 4
• 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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) • For communication with IP address specified: 5006
• For direct communication without IP address specified: Unused
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)
ActHostAddress 1.1.1.1 For communication with specified IP address: Host name or IP address of the connected station side
module
For direct communication without specified IP address: The specification is invalid.
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
• QCPU (Q mode), • QCPU (Q mode),
LCPU: 1 (0x01) QCCPU, LCPU: 1
• 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)
■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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber*3 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActPassword Null Remote password set to the connected station
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_UDPIP(0x08)
ERIAL)
ActStationNumber*3 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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 131
 Property Default value Property patterns
(1) (2) (3) (4)
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) • For communication with specified IP address: UNIT_QNETHER (0x2C)
• 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.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*3 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

132 4.2 Ethernet Communication
Ethernet communication when the connected station is built-in
Ethernet port LCPU (TCP)

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*1     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 133
 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) (3) (4)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
■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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) 5007
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
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)
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)
■For multiple CPUs
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00) Fixed to 0 (0x00)
*2 number
ActNetworkNumber*3 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station side
module network
number
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActPassword Null Password set to the connected station side
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

134 4.2 Ethernet Communication
Property Default value Property patterns
(1) (2) (3) (4)
*3
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
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) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LNETHER(0x52)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1 4
2: Channel 2
*3 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 135
 Ethernet communication when the connected station is built-in
Ethernet port LCPU (UDP)

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
*1
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

136 4.2 Ethernet Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_1 Fixed to 0 (0x00)
9200)
ActControl 8(TRC_DTR_OR_RT Fixed to 0 (0x00)
S)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00) 4
■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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) • For communication with IP address specified: 5006
• For direct communication without IP address specified: 5008
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 • For communication with specified IP address: Host name or IP address of the connected station side
module
• For direct communication without IP address specified: 255.255.255.255
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
• QCPU (Q mode), • QCPU (Q mode),
LCPU: 1 (0x01) QCCPU, LCPU: 1
• Other than the (0x01)
above: 0 (0x00) • Other than the
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
address address • 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)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
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
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActPassword Null Remote password set to the connected station
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 137
 Property Default value Property patterns
(1) (2) (3) (4)
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_UDPIP(0x08)
ERIAL)
ActStationNumber*3 255(0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
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) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
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 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*3 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

138 4.2 Ethernet Communication
Ethernet communication when the connected station is Ethernet
adapter module (TCP)

Configuration

Connected station CC-Link IE Field

Relayed module
CPU Network module

Ethernet adapter
Relayed network
module

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
QnUDE(H)CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

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

*1 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

140 4.2 Ethernet Communication
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) (3) (4)
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) 4
• 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
• Control system: 976
(0x3D0)
• 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)
ActHostAddress 1.1.1.1 Host name or IP address of the Ethernet adapter module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
*1
ActIONumber 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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*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
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
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
number number 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_NZ2GF_ETB(0x59)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 141
 *1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
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
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

142 4.2 Ethernet Communication
Ethernet communication when the connected station is Ethernet
adapter module (UDP)

Configuration

Connected station CC-Link IE Field

Relayed module
CPU Network module

Ethernet adapter
Relayed network
module

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
QnUDE(H)CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

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

*1 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

144 4.2 Ethernet Communication
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) (3) (4)
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) 4
• 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
• Control system: 976
(0x3D0)
• 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)
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.
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
*1 1023(0x3FF) ■For single CPU Target station side
ActIONumber 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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*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
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_UDPIP(0x08)
ERIAL)
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
number number 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) • For communication with specified IP address: UNIT_NZ2GF_ETB (0x59)
• For direct communication without specified IP address: UNIT_NZ2GF_ETB_DIRECT (0x5A)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 145
 *1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
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
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

146 4.2 Ethernet Communication
Ethernet communication when the connected station is Ethernet
adapter (TCP)

Configuration

Connected station
Ethernet adapter Relayed module
CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Only FX3SCPU, FX3G(C)CPU and FX3U(C)CPU can be accessed.

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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_TCPIP
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXETHER

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 147
 Ethernet communication when the connected station is Ethernet
adapter (UDP)

Configuration

Connected station
Ethernet adapter Relayed module
CPU

Relayed network

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Only FX3SCPU, FX3G(C)CPU and FX3U(C)CPU can be accessed.

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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_UDPIP
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXETHER_DIRECT

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

148 4.2 Ethernet Communication
Ethernet communication when the connected station is robot
controller

Configuration

Robot controller

Personal computer 4

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
ActProtocolType 0x04(PROTOCOL_SERIAL) RC_PROTOCOL_TCPIP(0x02)
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
ActTimeOut 10000 Any value specified by user in ms units
ActCpuTimeOut 0(0x00) Any value specified by user in 10ms units
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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 149
 Ethernet communication when the connected station is CC-Link
IE TSN module (TCP)

Configuration

Connected station CC-Link IE TSN

Relayed module
CPU module

Relayed network

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
RCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN (2)    
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication (3)    
CC-Link (4)    

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

150 4.2 Ethernet Communication
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) (3) (4)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*5 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)
■For multiple CPUs
(0x3FF)
■For multiple CPUs
4
• 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)
ActDestinationPortNumber 0(0x00) 5002
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIONumber*5 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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*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 Null Password set to CC-Link IE TSN module on the connected station side
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP
ERIAL)
ActPacketType 0x01(PACKET_PLC1 PACKET_PLC1
)
ActPortNumber*2 1(PORT_1) Personal computer side port number
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RT Fixed to 0 (0x00)
S)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK Fixed to 0 (0x00)
)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActSourceNetworkNumber 0(0x00) Personal computer side network number
ActSourceStationNumber*3 0(0x00) Personal computer side station number

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 151
 Property Default value Property patterns
(1) (2) (3) (4)
*1*6
ActStationNumber 255(0xFF) Target station side Target station side Connected station side Connected station side
module station number module station number CC-Link IE TSN CC-Link IE TSN
module station number module station number
ActThroughNetworkType 0(0x00) Fixed to 0 (0x00)
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_RJ71GN11(0x1006)

*1 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.
*2 Specify the following value.
0: An empty slot number in a personal computer is automatically assigned.
*3 Specify the station number on the personal computer side to avoid the same station number set for CC-Link IE TSN module within the
same Ethernet loop.
*4 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
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
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".

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

152 4.2 Ethernet Communication
Ethernet communication when the connected station is CC-Link
IE TSN module (UDP)

Configuration

Connected station CC-Link IE TSN

Relayed module
CPU module

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
RCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*1 CC IE TSN (2)    
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication (3)    
CC-Link (4)    

Connected Relayed network Relayed station CPU

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

*1 Access to a CC-Link IE TSN module with a direct connection is not supported.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 153
 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) (3) (4)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*5 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)
ActDestinationPortNumber 0(0x00) 5001
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIONumber*5 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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*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 Null Password set to CC-Link IE TSN module on the connected station side
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP
ERIAL)
ActPacketType 0x01(PACKET_PLC1 PACKET_PLC1
)
ActPortNumber*2 1(PORT_1) For communication with IP address specified: Personal computer side COM port number
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RT Fixed to 0 (0x00)
S)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK Fixed to 0 (0x00)
)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActSourceNetworkNumber 0(0x00) Personal computer side network number
ActSourceStationNumber*3 0(0x00) Personal computer side station number

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

154 4.2 Ethernet Communication
Property Default value Property patterns
(1) (2) (3) (4)
*1*6
ActStationNumber 255(0xFF) Target station side Target station side Connected station side Connected station side
module station number module station number CC-Link IE TSN CC-Link IE TSN
module station number module station number
ActThroughNetworkType 0(0x00) Fixed to 0 (0x00)
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_RJ71GN11(0x1006)

*1 When the property pattern is (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
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'. 4
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 station number on the personal computer side to avoid the same station number set for CC-Link IE TSN module within the
same Ethernet loop.
*4 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
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
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".

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.2 Ethernet Communication 155
 4.3 CPU COM communication
CPU COM communication when the connected station is FX5CPU

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FX5CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     (3)

Connected Relayed network Relayed station CPU

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

*1 Only CC-Link IE Field Network can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

156 4.3 CPU COM communication
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) (3)
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
BAUDRATE_115200
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 8 (DATABIT_8)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
4
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) 1023(0x3FF)
ActDidPropertyBit 1(0x01) Fixed to 0 (0x00) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActDsidPropertyBit 1(0x01) Fixed to 0 (0x00) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) 1(0x01)
ActIONumber 1023(0x3FF) Fixed to 1023 (0x3FF) Module number of the
connected station
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00)
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side module Fixed to 0 (0x00)
network number
ActParity 1(ODD_PARITY) Fixed to 1 (ODD_PARITY)
ActPassword Null NULL
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Target station side module Fixed to 255 (0xFF)
station number
ActSourceNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActSourceStationNumber 0(0x00) Fixed to 0 (0x00)
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (STOPBIT_ONE)
ActSumCheck 0(NO_SUM_CHECK) Fixed to 0 (NO_SUM_CHECK)
ActHostAddress 1.1.1.1 NULL
ActTargetSimulator 0(0x00) Fixed to 0 (0x00)
ActThroughNetworkType 0(0x00) Fixed to 0 (0x00)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side module
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXVCPU(0x2000)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.3 CPU COM communication 157
 CPU COM communication when the connected station is QCPU
(Q mode)

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
QCPU (Q QCCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
mode)
(1) (1)*4 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station Relayed network Relayed station CPU

CPU
QCPU (Q QCCPU 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) 
Serial communication (3)*5  (3)  (3) 
CC-Link (4) (4) (4)  (4) (4)*3

*1 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.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 Supported by FX3G(C)CPU and FX3U(C)CPU within the own network only.
*4 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*5 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

158 4.3 CPU COM communication
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)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
ActControl 8(TRC_DTR_OR_R Depending on the used cable.
TS)
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
• Fixed to 1023
■For single CPU
• Fixed to 1023
4
(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
• Control system: 976
(0x3D0)
• 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) Fixed to 0 (0x00) Target station Target station
• QCPU (Q mode), • QCPU (Q mode),
LCPU: 1 (0x01) QCCPU, LCPU: 1
• Other than the (0x01)
above: 0 (0x00) • Other than the
above: 0 (0x00)
ActIONumber*2 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
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
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.3 CPU COM communication 159
 Property Default value Property patterns
(1) (2)*1 (3) (4)
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_QNCPU(0x13)

*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
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 of the actual start I/O number divided 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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

160 4.3 CPU COM communication
CPU COM communication when the connected station is LCPU

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

4
Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
*1
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.3 CPU COM communication 161
 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) (3) (4)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RT Depending on the used cable.
S)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
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)
■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 ■For redundant CPU
• Control system: 976 • Control system: 976
(0x3D0) (0x3D0)
• No specification: • No specification:
1023 (0x3FF) 1023 (0x3FF)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Fixed to NULL
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
• QCPU (Q mode), • QCPU (Q mode),
LCPU: 1 (0x01) QCCPU, LCPU: 1
• Other than the (0x01)
above: 0 (0x00) • Other than the
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)
■For multiple CPUs
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
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)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

162 4.3 CPU COM communication
Property Default value Property patterns
(1) (2) (3) (4)
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
ActSourceNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActSourceStationNumber 0(0x00) Fixed to 0 (0x00)
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)
)
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00)
• MELSECNET/10 is included.: 1 (0x01)
4
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LNCPU(0x50)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.3 CPU COM communication 163
 CPU COM communication when the connected station is Q
motion CPU

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
Q motion RCPU RCCPU R motion CPU LHCPU FX5CPU
CPU
(1)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Relayed stations cannot be accessed when the Q motion CPU is Q172CPU, Q173CPU, Q172HCPU, or Q173HCPU.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

164 4.3 CPU COM communication
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)
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
BAUDRATE_115200
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActIONumber 1023(0x3FF) ■For multiple CPUs
• Control CPU: 1023 (0x3FF)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
4
• No. 4: 995 (0x3E3)
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) UNIT_QNMOTION(0x1C)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.3 CPU COM communication 165
 CPU COM communication when the connected station is FXCPU

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

166 4.3 CPU COM communication
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)
ActBaudRate 19200(BAUDRATE_19200) • FX0(S), FX0N, FX1, FX1S, FX2(C): (BAUDRATE_9600)
• FX1N(C), FX2N(C): (BAUDRATE_9600, BAUDRATE_19200)
• FX3S, FX3UC, FX3G(C): (BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
BAUDRATE_57600, BAUDRATE_115200)
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) 1023(0x3FF) 4
ActDidPropertyBit 1(0x01) 0(0x00)
ActDsidPropertyBit 1(0x01) 0(0x00)
ActIONumber 1023(0x3FF) Fixed to 0 (0x00) Module number of the connected station
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXCPU(0x0F)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.3 CPU COM communication 167
 CPU COM communication when the connected station is inverter

Configuration

Inverter

Personal computer

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
ActMxUnitSeries 0(0x00) 1(0x01)
ActProtocolType 0x04(PROTOCOL_SERIAL) COMM_RS232C(0x00)
ActStationNumber 255(0xFF) Inverter station number (0 to 31)
ActCpuType 34(CPU_Q02CPU) INV_A800(0x1E60)
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_4800, BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
BAUDRATE_57600, BAUDRATE_115200
ActTimeOut 10000 Any value specified by user in ms units
ActCpuTimeOut 0(0x00) Any value specified by user in 10ms units
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.
Use the utility setting type control.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

168 4.3 CPU COM communication
CPU COM communication when the connected station is robot
controller

Configuration

Robot controller

Personal computer 4

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
ActProtocolType 0x04(PROTOCOL_SERIAL) RC_PROTOCOL_SERIAL(0x01)
ActCpuType 34(CPU_Q02CPU) Robot controller type (0x013001)
ActPortNumber 1(PORT_1) Personal computer side COM port number
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)
ActMxUnitSeries 0(0x00) 2(0x02)

When robot controller communication, the program setting type control cannot be used.
Use the utility setting type control.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.3 CPU COM communication 169
 4.4 CPU USB Communication
CPU USB communication when the connected station is RCPU

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
RCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN (2)    
CC IE Control (2)*1 (2)   (2)*2
CC IE Field
MELSECNET/H     
Ethernet (2)  (2)  
Serial communication (3)  (3)  
CC-Link (4) (4) (4)  (4)

Connected Relayed network Relayed station CPU

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

*1 Since CC-Link IE Controller Network is not supported, RCPU and LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*2 Only CC-Link IE Field Network can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

170 4.4 CPU USB Communication
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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*2 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) 4
• 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) 0(0x00) 0(0x00)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) 0(0x00) 0(0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
• RCPU, QCPU (Q • RCPU, QCPU (Q
mode), LCPU: 1 mode), LCPU: 1
(0x01) (0x01)
• Other than the • Other than the
above: 0 (0x00) above: 0 (0x00)
ActIONumber*2 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USB
ERIAL)
ActPacketType 0x01(PACKET_PLC PACKET_PLC1
1)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Target station side Fixed to 255 (0xFF) Fixed to 255 (0xFF)
module station number
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Fixed to 1 (PORT_1)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActHostAddress 1.1.1.1 Fixed to NULL
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.4 CPU USB Communication 171
 Property Default value Property patterns
(1) (2)*1 (3) (4)
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)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00) MELSECNET/10 is not
• MELSECNET/10 is included.: 1 (0x01) included.: 0 (0x00)
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_RUSB

*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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

172 4.4 CPU USB Communication
CPU USB communication when the connected station is R
motion CPU

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
R motion RCPU RCCPU R motion CPU LHCPU FX5CPU
CPU
(1)*1*2 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Relayed station CPUs cannot be accessed via R motion CPU.

*2 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.4 CPU USB Communication 173
 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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
Act DestinationIONumber 0(0x00) Fixed to 0 (0x00)
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01)
Act IntelligentPreference Bit 0(0x00) Fixed to 0 (0x00)
ActIONumber 1023(0x3FF) ■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)
■For redundant CPU
• No specification: 1023 (0x3FF)
ActMultiDropChannelNumber*1 0(0x00) Fixed to 0 (0x00)
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_SERIA PROTOCOL_USB
L)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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)
ActUnitType 0x13(UNIT_QNCPU) UNIT_RUSB

*1 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

174 4.4 CPU USB Communication
CPU USB communication when the connected station is LHCPU

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

4
Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LHCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.4 CPU USB Communication 175
 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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00)
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber 1023(0x3FF) ■For single CPU
Fixed to 1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00)
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_USB
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Fixed to 1 (PORT_1)
ActBaudRate 19200(BAUDRATE_19200) Fixed to 0 (0x00)
ActHostAddress 1.1.1.1 Fixed to NULL
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RTS) Fixed to 0 (0x00)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
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)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
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)
ActUnitType 0x13(UNIT_QNCPU) UNIT_LHUSB

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

176 4.4 CPU USB Communication
CPU USB communication when the connected station is FX5CPU

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU
4
Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FX5CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
(1) CC IE TSN     
CC IE Control     (2)*2
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     (3)

Connected Relayed network Relayed station CPU

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

*1 Only FX5UJCPU can be accessed.

*2 Only CC-Link IE Field Network can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.4 CPU USB Communication 177
 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) (3)
ActBaudRate 19200(BAUDRATE_19200) 0(0x00)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RTS) 0(0x00)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) 0(0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) 1023(0x3FF)
ActDestinationPortNumber 0(0x00) Fixed to 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)
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
ActPacketType 0x01(PACKET_PLC1) Fixed to 0x01 (PACKET_PLC1)
ActPassword Null NULL
ActPortNumber 1(PORT_1) Fixed to 1 (PORT_1)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_USB
ActSourceNetworkNumber 0(0x00) 0(0x00)
ActSourceStationNumber 0(0x00) 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) Fixed to 0 (0x00)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) 0(0x00) Target station side module
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXVUSB

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

178 4.4 CPU USB Communication
CPU USB communication when the connected station is QCPU (Q
mode)

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
QCPU (Q RCPU RCCPU R motion CPU LHCPU FX5CPU
mode)
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU
QCPU (Q QCPU (Q mode) 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) 
Serial communication (3)*3  (3)*3  (3) 
CC-Link (4) (4) (4)  (4) (4)*4

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.4 CPU USB Communication 179
 Connected Relayed network Relayed station CPU
station CPU
QCCPU QCPU (Q 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      
Serial communication      
CC-Link (4) (4) (4)  (4) 

*1 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.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.
*4 Supported by FX3G(C)CPU and FX3U(C)CPU within the own network only.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

180 4.4 CPU USB Communication
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)
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) 4
• 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)
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) Fixed to 0 (0x00) Target station Target station
• QCPU (Q mode), • QCPU (Q mode),
LCPU: 1 (0x01) QCCPU, LCPU: 1
• Other than the (0x01)
above: 0 (0x00) • Other than the
above: 0 (0x00)
ActIONumber*2 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
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
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USB(0x0D)
ERIAL)
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_QNUSB(0x16)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.4 CPU USB Communication 181
 *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
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 of the actual start I/O number divided 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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

182 4.4 CPU USB Communication
CPU USB communication when the connected station is LCPU

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

4
Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*1     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.4 CPU USB Communication 183
 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) (3) (4)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
■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 ■For redundant CPU
• Control system: 976 • Control system: 976
(0x3D0) (0x3D0)
• No specification: • No specification:
1023 (0x3FF) 1023 (0x3FF)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Fixed to NULL
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
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)
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)
■For multiple CPUs
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
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_PLC Fixed to 0x01 (PACKET_PLC1)
1)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

184 4.4 CPU USB Communication
Property Default value Property patterns
(1) (2) (3) (4)
ActPortNumber 1(PORT_1) Fixed to 1 (PORT_1)
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USB(0x0D)
ERIAL)
ActSourceNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActSourceStationNumber 0(0x00) Fixed to 0 (0x00)
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)
)
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00)
• MELSECNET/10 is included.: 1 (0x01)
4
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LNUSB(0x51)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.4 CPU USB Communication 185
 CPU USB communication when the connected station is QSCPU

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
QSCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Relayed station CPUs cannot be accessed via QSCPU.

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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_USB(0x0D)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) UNIT_QSUSB(0x29)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

186 4.4 CPU USB Communication
CPU USB communication when the connected station is Q
motion CPU

Configuration

Connected station Relayed module

CPU

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
Q motion RCPU RCCPU R motion CPU LHCPU FX5CPU
CPU
(1)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Relayed stations cannot be accessed when the Q motion CPU is Q172CPU, Q173CPU, Q172HCPU, or Q173HCPU.

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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActIONumber 1023(0x3FF) ■For multiple CPUs
• Control CPU: 1023 (0x3FF)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_USB(0x0D)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) UNIT_QNMOTIONUSB(0x1D)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.4 CPU USB Communication 187
 CPU USB communication when the connected station is FXCPU

Configuration

Connected station Relayed module

CPU

Relayed network

Relayed station Relayed module

Personal computer
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Only FX3G(C)CPU and FX3U(C)CPU can 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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) 1023(0x3FF)
ActIONumber 1023(0x3FF) Fixed to 0 (0x00) Module number of the connected station
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_USB(0x0D)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXCPU(0x0F)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

188 4.4 CPU USB Communication
CPU USB communication when the connected station is inverter

Configuration

Inverter

Personal computer

4
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
ActMxUnitSeries 0(0x00) 1(0x01)
ActProtocolType 0x04(PROTOCOL_SERIAL) COMM_USB(0x01)
ActStationNumber 255(0xFF) Inverter station number (0 to 31)
ActCpuType 34(CPU_Q02CPU) Fixed to INV_A800 (0x1E60)
ActTimeOut 10000 Any value specified by user in ms units
ActCpuTimeOut 0(0x00) Any value specified by user in 10ms units

When performing inverter communication, the program setting type control cannot be used.
Use the utility setting type control.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.4 CPU USB Communication 189
 CPU USB communication when the connected station is robot
controller

Configuration

Robot controller

Personal computer

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
ActProtocolType 0x04(PROTOCOL_SERIAL) RC_PROTOCOL_USB(0x04)
ActCpuType 34(CPU_Q02CPU) Robot controller type (0x013001)
ActTimeOut 10000 Receive timeout time (msec)
ActCpuTimeOut 0(0x00) Send timeout time (msec)
ActMultiDropChannelNumber 0(0x00) 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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

190 4.4 CPU USB Communication
4.5 MELSECNET/H Communication

Configuration

Connected station MELSECNET/H

Relayed module
CPU module

Relayed network

Personal computer Relayed station Relayed module

CPU
4
Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Own Connected station CPU Relayed network Relayed station CPU

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)  
Serial communication (3)*4  (3)*4  (3) 
CC-Link (4) (4) (4)  (4) 

Own Connected station CPU Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.5 MELSECNET/H Communication 191
 Own Connected station CPU Relayed network Relayed station CPU
board QCCPU QCPU QCCPU LCPU QSCPU Q motion FXCPU
(Q CPU*5
mode)
(1) (2)*6 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link (4) (4) (4)  (4) 

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

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and QSCPU relayed by CC-Link IE Field Network cannot
be accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 For redundant CPU, serial communication modules on the main base cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*6 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

192 4.5 MELSECNET/H Communication
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) (3) (4)
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) 4
• 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)
ActDidPropertyBit 1(0x01) Fixed to 0 (0x00) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
ActDsidPropertyBit 1(0x01) Fixed to 0 (0x00) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
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)
■For multiple CPUs
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Connected station side Connected station side
module network module network module network
number number number
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_S PROTOCOL_MNETH(0x0F)
ERIAL)
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
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00)
• MELSECNET/10 is included.: 1 (0x01)
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_MNETHBOARD(0x1E)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.5 MELSECNET/H Communication 193
 4.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

Personal computer Relayed station Relayed module

CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Own Connected Relayed network Relayed station CPU
board station CPU
RCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
 (2) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication (3)*1    
CC-Link (4)    

Own Connected Relayed network Relayed station CPU

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

*1 For redundant CPU, serial communication modules on the main base cannot be accessed because the multi-drop connection cannot be
performed.
*2 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

194 4.6 CC-Link IE Controller Network Communication
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) (3) (4)
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) 4
• 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 0 (0x00) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
ActDsidPropertyBit 1(0x01) Fixed to 0 (0x00) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
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)
■For multiple CPUs
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Connected station side Connected station side
module network module network module network
number number 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_S PROTOCOL_MNETG(0x14)
ERIAL)
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
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00)
• MELSECNET/10 is included.: 1 (0x01)
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_MNETGBOARD(0x2B)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.6 CC-Link IE Controller Network Communication 195
 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

Personal computer Relayed station Relayed module

CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Own Connected station CPU Relayed network Relayed station 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Own Connected station CPU Relayed network Relayed station CPU

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)  
Serial communication (3)*4  (3)  (3) 
CC-Link (4) (4) (4)  (4) 

Own Connected station CPU Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

196 4.6 CC-Link IE Controller Network Communication
Own Connected station CPU Relayed network Relayed station CPU
board QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU*5
(1) (2)*6 CC IE TSN      
CC IE Control      
CC IE Field
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link (4) (4) (4)  (4) 

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

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and QSCPU relayed by CC-Link IE Field Network cannot

*3
be accessed.
Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
4
*4 For redundant CPU, serial communication modules on the main base cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*6 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.6 CC-Link IE Controller Network Communication 197
 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) (3) (4)
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 ■For redundant CPU
• Control system: 976 • Control system: 976
(0x3D0) (0x3D0)
• No specification: • No specification:
1023 (0x3FF) 1023 (0x3FF)
ActDidPropertyBit 1(0x01) Fixed to 0 (0x00) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
ActDsidPropertyBit 1(0x01) Fixed to 0 (0x00) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
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)
■For multiple CPUs
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Connected station side Connected station side
module network module network module network
number number 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_S PROTOCOL_MNETG(0x14)
ERIAL)
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
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00)
• MELSECNET/10 is included.: 1 (0x01)
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_MNETGBOARD(0x2B)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

198 4.6 CC-Link IE Controller Network Communication
4.7 CC-Link IE Field Network Communication
CC-Link IE Field Network communication when the connected
station is an RCPU

Configuration

Connected station CC-Link IE Field

Relayed module
CPU Network module

Relayed network
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Own Connected Relayed network Relayed station CPU
board station CPU
RCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
 (1) CC IE TSN     
CC IE Field     
MELSECNET/H     
Ethernet     
*1
Serial communication (2)    
CC-Link (3)    

Own Connected Relayed network Relayed station CPU

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

*1 For redundant CPU, serial communication modules on the main base cannot be accessed because the multi-drop connection cannot be
performed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.7 CC-Link IE Field Network Communication 199
 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) (3)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side
■For single CPU ■For single CPU
• Fixed to 1023 (0x3FF) • Fixed to 1023 (0x3FF)
■For multiple CPUs ■For multiple CPUs
• 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)
■For redundant CPU
• No specification: 1023
(0x3FF)
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
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
■For multiple CPUs
• Connected CPU: 1023
(0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• No specification: 1023
(0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Multi-drop channel number Fixed to 0 (0x00)
*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_S PROTOCOL_CCIEF(0x15)
ERIAL)
ActStationNumber 255(0xFF) Target station side module Connected station side module Connected station side module
station number station number station number
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00)
• MELSECNET/10 is included.: 1 (0x01)
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side module Target station side module
station number station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_CCIEFBOARD(0x2F)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

200 4.7 CC-Link IE Field Network Communication
CC-Link IE Field Network communication when the connected
station is a module supporting QCPU (Q mode) or LCPU

Configuration

Connected station CC-Link IE Field

Relayed module
CPU Network module

Relayed network

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Own Connected 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Own Connected Relayed network Relayed station CPU

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)     
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

Own Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.7 CC-Link IE Field Network Communication 201
 Own Connected Relayed network Relayed station CPU
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)   
MELSECNET/H      
Ethernet      
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

*1 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

202 4.7 CC-Link IE Field Network Communication
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) (3) (4)
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) 4
• 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)
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)
ActIONumber*1 1023(0x3FF) Fixed to 1023 (0x3FF) 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)
■For multiple CPUs
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Connected station side Connected station side
module network module network module network
number number 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_S PROTOCOL_CCIEF(0x15)
ERIAL)
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
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00)
• MELSECNET/10 is included.: 1 (0x01)
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_CCIEFBOARD(0x2F)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.7 CC-Link IE Field Network Communication 203
 4.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
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Own Connected Relayed network Relayed station CPU
board station CPU
RCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
 (1) CC IE TSN (2)    
CC IE Control (2)    
CC IE Field
MELSECNET/H     
Ethernet (2)    
Serial communication     
CC-Link     

Own Connected Relayed network Relayed station CPU

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

*1 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

204 4.8 CC-Link Communication
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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) ■For single CPU Target station side
• Fixed to 1023 (0x3FF) ■For single CPU
■For multiple CPUs • Fixed to 1023 (0x3FF)
• 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) 4
• No. 4: 995 (0x3E3) • No. 3: 994 (0x3E2)
■For redundant CPU • No. 4: 995 (0x3E3)
• 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)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.8 CC-Link Communication 205
 CC-Link communication when the connected station is an LCPU

Configuration

Connected station CC-Link Relayed module

CPU module

Relayed network

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Own Connected Relayed network Relayed station CPU
board station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) (2) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Own Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

206 4.8 CC-Link Communication
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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side
■For single CPU
Fixed to 1023 (0x3FF)
ActIONumber 1023(0x3FF) Fixed to 0 (0x00) Fixed to 1023 (0x3FF)
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Port number of personal computer side CC-Link Ver.2 board, PORT 1 to PORT 4 (first to fourth 4
boards)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_CCLINK(0x07)
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)
ActUnitType 0x13(UNIT_QNCPU) UNIT_CCLINKBOARD(0x0C)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.8 CC-Link Communication 207
 CC-Link communication when the connected station is a module
supporting Q series

Configuration

Connected station CC-Link Relayed module

CPU module

Relayed network

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Own Connected station CPU 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Own Connected station CPU Relayed network Relayed station CPU

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) 
Serial communication      
CC-Link      

Own Connected station CPU Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

208 4.8 CC-Link Communication
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
MELSECNET/H (3) (3)  (3) (3) 
Ethernet      
Serial communication      
CC-Link      

*1 Relayed station CPUs cannot be accessed via Q motion CPU.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode), QSCPU, and Q motion CPU relayed by CC-Link IE Field
Network cannot be accessed.
4
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*5 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.8 CC-Link Communication 209
 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) (3)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side
■For single CPU ■For single CPU
• Fixed to 1023 (0x3FF) • Fixed to 1023 (0x3FF)
■For multiple CPUs ■For multiple CPUs
• 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)
■For redundant CPU ■For redundant CPU
• Control system: 976 • Control system: 976
(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
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) 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
ActUnitType 0x13(UNIT_QNCPU) UNIT_CCLINKBOARD(0x0C)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

210 4.8 CC-Link Communication
4.9 CC-Link G4 communication

Configuration

Connected station CC-Link Relayed module

CPU module

CC-Link G4
Relayed network
module(Q mode)

Relayed station
Personal computer Relayed module
CPU
4
Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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) 
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.9 CC-Link G4 communication 211
 Connected station CPU Relayed network Relayed station CPU
QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
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) 
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed network Relayed station CPU

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

Connected station CPU Relayed network Relayed station CPU

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

*1 Relayed station CPUs cannot be accessed via Q motion CPU.

*2 Since CC-Link IE Field Network is not supported, 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.
*4 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

212 4.9 CC-Link G4 communication
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) (3)
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
BAUDRATE_115200
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
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 4
■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)
■For redundant CPU • No. 4: 995 (0x3E3)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: 1023 (0x3D0)
(0x3FF) • No specification: 1023
(0x3FF)
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side module Fixed to 0 (0x00)
network number
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Target station side module Fixed to 255 (0xFF)
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 module
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_G4QNCPU(0x1B)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.9 CC-Link G4 communication 213
 4.10 GX Simulator Communication

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
Host station Other station
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side network number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SHAREDMEMORY(0x06)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Target station side station number
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) UNIT_SIMULATOR(0x0B)

When any of the following settings is included in the property setting, the host station is accessed.
• ActNetworkNumber: The number outside the range of 1 to 255 is set.
• ActStationNumber: The number outside the range of 1 to 64 is set.

4.11 GX Simulator2 Communication

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
ActTargetSimulator 0(0x00) Refer to the property [ActTargetSimulator].
Page 64 Details of Control Properties
ActUnitType 0x13(UNIT_QNCPU) UNIT_SIMULATOR2(0x30)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

214 4.10 GX Simulator Communication
4.12 GX Simulator3 Communication

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
ActBaudRate 19200(BAUDRATE_19200) 0(0x00)
ActControl 8(TRC_DTR_OR_RTS) 0(0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits
ActDestinationPortNumber
8(DATABIT_8)
0(0x00)
0(0x00)
Fixed to 0 (0x00)
4
ActDidPropertyBit 1(0x01) 0(0x00)
ActDsidPropertyBit 1(0x01) 0(0x00)
ActHostAddress 1.1.1.1 Loopback address(127.0.0.1)
ActIONumber 1023(0x3FF) 0(0x00)
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActParity 1(ODD_PARITY) 0(0x00)
ActPassword Null 0(0x00)
ActPortNumber 1(PORT_1) 0(0x00)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_TCPIP(0x05)
ActStationNumber 255(0xFF) System number corresponding to target station
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK) Fixed to 0 (0x00)
ActThroughNetworkType 0(0x00) Fixed to 0 (0x00)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) UNIT_SIMULATOR3(0x31)
ActTargetSimulator 0(0x00) PLC number corresponding to target station

4.13 MT Simulator2 Communication

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
ActTargetSimulator 0(0x00) Refer to the property [ActTargetSimulator].
Page 64 Details of Control Properties
ActCpuType CPU_Q02CPU CPU type corresponding to the target station (Q motion CPU)
ActUnitType 0x13(UNIT_QNCPU) UNIT_SIMULATOR2(0x30)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.12 GX Simulator3 Communication 215
 4.14 Modem Communication
Modem communication when the connected module 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-compatible Relayed module

CPU C24

Subscrib
Modem er's line Modem Relayed network

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
QCPU (Q RCPU RCCPU R motion CPU LHCPU FX5CPU
mode)
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and QSCPU relayed by CC-Link IE Field Network cannot
be accessed.
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

216 4.14 Modem Communication
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) (3) (4)
ActATCommand Null Any value specified by user
ActATCommandPasswordCa 3 Any value specified by user
ncelRetry Times
ActATCommandResponse 1 Any value specified by user (in seconds)
WaitTime
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200 (Match to the setting of Q series-compatible C24.) 4
ActCallbackCancelWaitTime 90 Any value specified by user (in seconds)
ActCallbackDelayTime 20 Any value specified by user (in seconds)
ActCallbackNumber Null Telephone number of any value specified by user
ActCallbackReceptionWaitin 120 Any value specified by user (in seconds)
gTimeOut
ActConnectionCDWaitTime 90 Any value specified by user (in seconds)
ActConnectionModemReport 5 Any value specified by user (in seconds)
WaitTime
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActConnectWay 0(TEL_AUTO_CON TEL_AUTO_CONNECT(0), TEL_AUTO_CALLBACK(1), TEL_AUTO_CALLBACK_NUMBER(2),
NECT) TEL_CALLBACK(3), TEL_CALLBACK_NUMBER(4), TEL_CALLBACK_REQUEST(5),
TEL_CALLBACK_REQUEST_NUMBER(6), TEL_CALLBACK_WAIT(7) (Depending on callback
function setting)
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 ■For redundant CPU
• Control system: 976 • Control system: 976
(0x3D0) (0x3D0)
• No specification: • No specification:
1023 (0x3FF) 1023 (0x3FF)
ActDialNumber Null Telephone number of any value specified by user
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
ActDisconnectionCDWaitTim 5 Any value specified by user (in seconds)
e
ActDisconnectionDelayTime 3 Any value specified by user (in seconds)
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)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.14 Modem Communication 217
 Property Default value Property patterns
(1) (2) (3) (4)
*1
ActIONumber 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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
1023 (0x3FF) • No specification:
1023 (0x3FF)
ActLineType 1(LINETYPE_TONE) LINETYPE_PULSE(0), LINETYPE_TONE(1), LINETYPE_ISDN(2)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2 number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActOutsideLineNumber Null Outside line access number of any value specified by user
ActPassword Null Password set to Q series-compatible C24
ActPasswordCancelRespons 5 Any value specified by user (in seconds)
eWaitTime
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIALMODEM(0x0E)
ERIAL)
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
ActTransmissionDelayTime 0 Any value specified by user (in seconds)
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_QJ71C24(0x19)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

218 4.14 Modem Communication
Modem communication when the connected module 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

Connected station Q series-compatible

CPU C24

Subscrib
Multi-drop link
Modem er's line Modem

4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
QCPU (Q mode) RCPU RCCPU R motion CPU LHCPU FX5CPU
Independent (1) Serial communication     
mode*1

Connected station Relayed network Relayed station CPU

CPU
QCPU (Q mode) QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
Independent (1) Serial communication (2)*2  (2)   
mode*1

*1 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)
*2 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.14 Modem Communication 219
 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)
ActATCommand Null Any value specified by user
ActATCommandPasswordCancelRetryTimes 3 Any value specified by user
ActATCommandResponseWaitTime 1 Any value specified by user (in seconds)
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
BAUDRATE_57600, BAUDRATE_115200 (Match to the setting of Q series-
compatible C24.)
ActCallbackCancelWaitTime 90 Any value specified by user (in seconds)
ActCallbackDelayTime 20 Any value specified by user (in seconds)
ActCallbackNumber Null Telephone number of any value specified by user
ActCallbackReceptionWaitingTimeOut 120 Any value specified by user (in seconds)
ActConnectionCDWaitTime 90 Any value specified by user (in seconds)
ActConnectionModemReportWaitTime 5 Any value specified by user (in seconds)
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActConnectWay 0(TEL_AUTO_CONNECT) TEL_AUTO_CONNECT(0), TEL_AUTO_CALLBACK(1),
TEL_AUTO_CALLBACK_NUMBER(2), TEL_CALLBACK(3),
TEL_CALLBACK_NUMBER(4), TEL_CALLBACK_REQUEST(5),
TEL_CALLBACK_REQUEST_NUMBER(6), TEL_CALLBACK_WAIT(7)
(Depending on callback function setting)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side
■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)
■For redundant CPU
• Control system: 976 (0x3D0)
• No specification: 1023 (0x3FF)
ActDialNumber Null Telephone number of any value specified by user
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActDisconnectionCDWaitTime 5 Any value specified by user (in seconds)
ActDisconnectionDelayTime 3 Any value specified by user (in seconds)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*1 1023(0x3FF) ■For single CPU Connected station side relayed
• Fixed to 1023 (0x3FF) module I/O address
■For multiple CPUs
• Connected CPU: 1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976 (0x3D0)
• No specification: 1023 (0x3FF)
ActLineType 1(LINETYPE_TONE) LINETYPE_PULSE(0), LINETYPE_TONE(1), LINETYPE_ISDN(2)
*2
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Multi-drop channel number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActOutsideLineNumber Null Outside line access number of any value specified by user
ActPassword Null Password set to Q series-compatible C24
ActPasswordCancelResponseWaitTime 5 Any value specified by user (in seconds)
ActPortNumber 1(PORT_1) Personal computer side COM port number

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

220 4.14 Modem Communication
Property Default value Property patterns
(1) (2)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIALMODEM(0x0E)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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
ActTransmissionDelayTime 0 Any value specified by user (in seconds)
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side module station
number
ActUnitType 0x13(UNIT_QNCPU) UNIT_QJ71C24(0x19)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
4
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.14 Modem Communication 221
 Modem communication when the connected module is L series-
compatible C24 (1)
When a relayed module other than the connected station side LJ71C24 exists

Configuration

Connected station L series-compatible Relayed module

CPU C24

Subscrib
Modem er's line Modem Relayed network

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
(1) CC IE TSN     
CC IE Field*2     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Indicates the CH2 side setting. (The CH1 side is fixed to the independent mode.)
*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*4 For redundant CPU, serial communication modules on the main base cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

222 4.14 Modem Communication
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) (3) (4)
ActATCommand Null Any value specified by user
ActATCommandPasswordCanc 3 Any value specified by user
elRetryTimes
ActATCommandResponseWait 1 Any value specified by user (in seconds)
Time
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200 (Match to the setting of LJ71C24) 4
ActCallbackCancelWaitTime 90 Any value specified by user (in seconds)
ActCallbackDelayTime 20 Any value specified by user (in seconds)
ActCallbackNumber Null Telephone number of any value specified by user
ActCallbackReceptionWaitingTi 120 Any value specified by user (in seconds)
meOut
ActConnectionCDWaitTime 90 Any value specified by user (in seconds)
ActConnectionModemReportW 5 Any value specified by user (in seconds)
aitTime
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActConnectWay 0(TEL_AUTO_CON TEL_AUTO_CONNECT(0), TEL_AUTO_CALLBACK(1), TEL_AUTO_CALLBACK_NUMBER(2),
NECT) TEL_CALLBACK(3), TEL_CALLBACK_NUMBER(4), TEL_CALLBACK_REQUEST(5),
TEL_CALLBACK_REQUEST_NUMBER(6), TEL_CALLBACK_WAIT(7)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
■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 ■For redundant CPU
• Control system: 976 • Control system: 976
(0x3D0) (0x3D0)
• No specification: • No specification:
1023 (0x3FF) 1023 (0x3FF)
ActDialNumber Null Telephone number of any value specified by user
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDisconnectionCDWaitTime 5 Any value specified by user (in seconds)
ActDisconnectionDelayTime 3 Any value specified by user (in seconds)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.14 Modem Communication 223
 Property Default value Property patterns
(1) (2) (3) (4)
*1
ActIONumber 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side Connected station side Target station side
relayed module I/O relayed module I/O ■For single CPU
address address • 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)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActLineType 1(LINETYPE_TONE) LINETYPE_PULSE(0), LINETYPE_TONE(1), LINETYPE_ISDN(2)
ActMultiDropChannelNumber*2 0(0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00) Fixed to 0 (0x00)
number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station side
module network
number
ActOutsideLineNumber Null Outside line access number of any value specified by user
ActPassword Null Password set to the module
ActPasswordCancelResponse 5 Any value specified by user (in seconds)
WaitTime
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIALMODEM(0x0E)
ERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
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
ActTransmissionDelayTime 0 Any value specified by user (in seconds)
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LJ71C24(0x54)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

224 4.14 Modem Communication
Modem communication when the connected module is L series-
compatible C24 (2)
When performing multi-drop link on the connected station side LJ71C24 with the relayed module

Configuration

Connected station L series-compatible

CPU C24

Subscrib Multi-drop link

Modem er's line Modem

4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
Independent (1) Serial communication     
mode

Connected station Relayed network Relayed station CPU

CPU
LCPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
*1
Independent (1) Serial communication (2)  (2)   
mode

*1 For redundant CPU, serial communication modules on the main base 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)
ActATCommand Null Any value specified by user
ActATCommandPasswordCancelRetryTimes 3 Any value specified by user
ActATCommandResponseWaitTime 1 Any value specified by user (in seconds)
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
BAUDRATE_57600, BAUDRATE_11520 (Match to the setting of LJ71C24)
ActCallbackCancelWaitTime 90 Any value specified by user (in seconds)
ActCallbackDelayTime 20 Any value specified by user (in seconds)
ActCallbackNumber Null Telephone number of any value specified by user
ActCallbackReceptionWaitingTimeOut 120 Any value specified by user (in seconds)
ActConnectionCDWaitTime 90 Any value specified by user (in seconds)
ActConnectionModemReportWaitTime 5 Any value specified by user (in seconds)
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActConnectWay 0(TEL_AUTO_CONNECT) TEL_AUTO_CONNECT(0), TEL_AUTO_CALLBACK(1),
TEL_AUTO_CALLBACK_NUMBER(2), TEL_CALLBACK(3),
TEL_CALLBACK_NUMBER(4), TEL_CALLBACK_REQUEST(5),
TEL_CALLBACK_REQUEST_NUMBER(6), TEL_CALLBACK_WAIT(7)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.14 Modem Communication 225
 Property Default value Property patterns
(1) (2)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side
■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)
■For redundant CPU
• Control system: 976 (0x3D0)
• No specification: 1023 (0x3FF)
ActDialNumber Null Telephone number of any value specified by user
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActDisconnectionCDWaitTime 5 Any value specified by user (in seconds)
ActDisconnectionDelayTime 3 Any value specified by user (in seconds)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*1 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side relayed
module I/O address
ActLineType 1(LINETYPE_TONE) LINETYPE_PULSE(0), LINETYPE_TONE(1), LINETYPE_ISDN(2)
ActMultiDropChannelNumber*2 0(0x00) Fixed to 0 (0x00) Multi-drop channel number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActOutsideLineNumber Null Outside line access number of any value specified by user
ActPassword Null Password set to the module
ActPasswordCancelResponseWaitTime 5 Any value specified by user (in seconds)
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIALMODEM(0x0E)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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
ActTransmissionDelayTime 0 Any value specified by user (in seconds)
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side module station
number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LJ71C24(0x54)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

226 4.14 Modem Communication
Modem communication when the connected station is FXCPU

Configuration

Connected station Relayed module

CPU

Subscrib
Modem er's line Modem Relayed network

Relayed station
Personal computer Relayed module
CPU

4
Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.14 Modem Communication 227
 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)
ActATCommand Null Any value specified by user
ActATCommandPasswordCancelRetryTimes 3 Any value specified by user
ActATCommandResponseWaitTime 1 Any value specified by user (in seconds)
ActCallbackCancelWaitTime 90 Any value specified by user (in seconds)
ActCallbackDelayTime 20 Any value specified by user (in seconds)
ActCallbackNumber Null Telephone number of any value specified by user
ActCallbackReceptionWaitingTimeOut 120 Any value specified by user (in seconds)
ActConnectionCDWaitTime 90 Any value specified by user (in seconds)
ActConnectionModemReportWaitTime 5 Any value specified by user (in seconds)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDialNumber Null Telephone number of any value specified by user
ActDisconnectionCDWaitTime 5 Any value specified by user (in seconds)
ActDisconnectionDelayTime 3 Any value specified by user (in seconds)
ActLineType 1(LINETYPE_TONE) LINETYPE_PULSE(0), LINETYPE_TONE(1), LINETYPE_ISDN(2)
ActOutsideLineNumber Null Outside line access number of any value specified by user
ActPasswordCancelResponseWaitTime 5 Any value specified by user (in seconds)
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_TEL(0x0A)
ActTimeOut 10000 Any value specified by user in ms units
ActTransmissionDelayTime 0 Any value specified by user (in seconds)
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXCPU(0x0F)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

228 4.14 Modem Communication
4.15 Gateway Function Communication

Configuration

GOT

Personal computer
4
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
ActHostAddress 1.1.1.1 Host name or IP address of connected GOT
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_UDPIP(0x08)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) UNIT_A900GOT(0x21)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.15 Gateway Function Communication 229
 4.16 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)
Connection manuals for GOT1000 series (Mitsubishi Products), (Non-Mitsubishi Products 1), (Non-
Mitsubishi Products 2), (Microcomputer, MODBUS Products, Peripherals)

Personal computer side port: Serial, GOT1000 side port: Serial,

CPU side port: Direct connection (1)
When the connected station is FX5CPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Serial Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FX5CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     (3)

Connected Relayed network Relayed station CPU

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

*1 Only CC-Link IE Field Network can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

230 4.16 GOT Transparent Communication
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) (3)
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
BAUDRATE_115200
ActConnectUnitNumber 0(0x00) 0(0x00)
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuTimeOut 0(0x00) 0(0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) 8(0x08)
4
ActDestinationIONumber 0(0x00) 0(0x00) 1023(0x3FF)
ActDestinationPortNumber 0(0x00) 0(0x00)
ActDidPropertyBit 1(0x01) 0(0x00)
ActDsidPropertyBit 1(0x01) 0(0x00)
ActHostAddress 1.1.1.1 NULL
ActIntelligentPreferenceBit 0(0x00) 0(0x00) 1(0x01)
ActIONumber 1023(0x3FF) 1023(0x3FF) Module number of the
connected station
ActMultiDropChannelNumber 0(0x00) 0(0x00)
ActNetworkNumber 0(0x00) 0(0x00) Target station side module 0(0x00)
network number
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1(0x01)
ActParity 1(ODD_PARITY) 1(ODD_PARITY)
ActPassword Null Null
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
ActStopBits 0(STOPBIT_ONE) 0(STOPBIT_ONE)
ActSumCheck 0(NO_SUM_CHECK) 0(NO_SUM_CHECK)
ActSourceNetworkNumber 0(0x00) 0(0x00)
ActSourceStationNumber 0(0x00) 0(0x00)
ActStationNumber 255(0xFF) 255(0xFF) Target station side module 255(0xFF)
station number
ActTargetSimulator 0(0x00) 0(0x00)
ActThroughNetworkType 0(0x00) 0(0x00)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) 0(0x00) Target station side module
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXVCPU(0x2005)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 231
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Direct connection (2)
When the connected station is QCPU (Q mode)

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Serial Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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      
*3 *4 *3
CC IE Control (2) (2) (2)  (2) 
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.

*2 Relayed station CPUs cannot be accessed via Q motion CPU.
*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.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

232 4.16 GOT Transparent Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
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)
■For multiple CPUs
(0x3FF)
■For multiple CPUs
4
• 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
• Control system: 976
(0x3D0)
• 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) Fixed to 0 (0x00) Target station Target station
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)
ActIONumber*1 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_ PROTOCOL_SERIAL(0x04)
SERIAL)
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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 233
 Property Default value Property patterns
(1) (2) (3) (4)
ActUnitType 0x13(UNIT_QNCPU UNIT_QNCPU(0x13)
)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

234 4.16 GOT Transparent Communication
Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Direct connection (3)
When the connected station is LCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Serial Serial
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
*2
CC IE Field     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 235
 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) (3) (4)
ActBaudRate 19200(BAUDRATE_1 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
9200) BAUDRATE_115200
ActControl 8(TRC_DTR_OR_RT 8(TRC_DTR_OR_RTS)
S)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
■For single CPU ■For single CPU
• Fixed to 1023 (0x3FF) • Fixed to 1023 (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
• Control system: 976
(0x3D0)
• No specification: 1023
(0x3FF)
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Fixed to NULL
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
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)
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)
■For multiple CPUs
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
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
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

236 4.16 GOT Transparent Communication
Property Default value Property patterns
(1) (2) (3) (4)
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LNCPU(0x50)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 237
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Direct connection (4)
When the connected station is FXCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Serial Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

238 4.16 GOT Transparent Communication
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)
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
BAUDRATE_115200
ActControl 8(TRC_DTR_OR_RTS) 8(TRC_DTR_OR_RTS)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Fixed to 1023 (0x3FF)
ActDidPropertyBit 1(0x01) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 0 (0x00) Fixed to 1 (0x01)
4
ActIONumber 1023(0x3FF) Fixed to 0 (0x00) Module number of the connected station
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXCPU(0x0F)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 239
 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Direct connection (1)
When the connected station is FX5CPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

USB Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FX5CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     (3)

Connected Relayed network Relayed station CPU

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

*1 Only CC-Link IE Field Network can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

240 4.16 GOT Transparent Communication
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) (3)
ActBaudRate 19200(BAUDRATE_19200) 0(0x00)
ActConnectUnitNumber 0(0x00) 0(0x00)
ActControl 8(TRC_DTR_OR_RTS) 0(0x00)
ActCpuTimeOut 0(0x00) 0(0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits
ActDestinationIONumber
8(DATABIT_8)
0(0x00)
0(0x00)
0(0x00) 1023(0x3FF)
4
ActDestinationPortNumber 0(0x00) 0(0x00)
ActDidPropertyBit 1(0x01) 0(0x00)
ActDsidPropertyBit 1(0x01) 0(0x00)
ActHostAddress 1.1.1.1 NULL
ActIntelligentPreferenceBit 0(0x00) 0(0x00) 1(0x01)
ActIONumber 1023(0x3FF) 1023(0x3FF) Module number of the
connected station
ActMultiDropChannelNumber 0(0x00) 0(0x00)
ActNetworkNumber 0(0x00) 0(0x00) Target station side module 0(0x00)
network number
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1(0x01)
ActParity 1(ODD_PARITY) 0(0x00)
ActPassword Null Null
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_USBGOT(0x13)
ActStopBits 0(STOPBIT_ONE) 0(0x00)
ActSumCheck 0(NO_SUM_CHECK) 0(0x00)
ActSourceNetworkNumber 0(0x00) 0(0x00)
ActSourceStationNumber 0(0x00) 0(0x00)
ActStationNumber 255(0xFF) 255(0xFF) Target station side module 255(0xFF)
station number
ActTargetSimulator 0(0x00) 0(0x00)
ActThroughNetworkType 0(0x00) 0(0x00)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) 0(0x00) Target station side module
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXVCPU(0x2005)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 241
 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Direct connection (2)
When the connected station is QCPU (Q mode)

Configuration

Connected station Relayed module

CPU

GOT Relayed network

USB Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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.

*2 Relayed station CPUs cannot be accessed via Q motion CPU.
*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.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

242 4.16 GOT Transparent Communication
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) (3) (4)
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 (0x3FF) • Fixed to 1023 (0x3FF)
■For multiple CPUs ■For multiple CPUs
• Connected CPU: • Connected CPU: 1023
1023 (0x3FF) (0x3FF) 4
• 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)
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) Fixed to 0 (0x00) Target station Target station
QCPU (Q mode), QCPU (Q mode),
QCCPU, LCPU: 1 QCCPU, LCPU: 1 (0x01)
(0x01) Other than the above: 0
Other than the above: 0 (0x00)
(0x00)
ActIONumber*1 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2 number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActProtocolType 0x04(PROTOCOL PROTOCOL_USBGOT(0x13)
_SERIAL)
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_QNCP UNIT_QNCPU(0x13)
U)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 243
 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Direct connection (3)
When the connected station is LCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

USB Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*2     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

244 4.16 GOT Transparent Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00) 4
■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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Fixed to NULL
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
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)
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)
■For multiple CPUs
• Connected CPU:
1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
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
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USBGOT(0x13)
ERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
module station number

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 245
 Property Default value Property patterns
(1) (2) (3) (4)
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) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LNCPU(0x50)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

246 4.16 GOT Transparent Communication
Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Direct connection (4)
When the connected station is FXCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

USB Serial
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 247
 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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
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
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_USBGOT(0x13)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) 0(0x00) Target station side module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_FXCPU(0x0F)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

248 4.16 GOT Transparent Communication
Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Bus connection

Configuration

Connected Relayed module

station CPU

GOT Relayed network

Serial Bus

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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) 
Serial communication (3)  (3)  (3) 
CC-Link (4) (4) (4)  (4) 

Connected station CPU Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 249
 Connected station CPU Relayed network Relayed station CPU
QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
(1)*6 CC IE TSN      
*3 *4 *3
CC IE Control (2) (2) (2)  (2) 
CC IE Field
MELSECNET/H (2) (2)   (2) 
Ethernet      
Serial communication      
CC-Link (4) (4) (4)  (4) 

*1 Redundant CPU cannot be accessed.

*2 Relayed station CPUs cannot be accessed via Q motion CPU.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE Field Network
cannot be accessed.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.
*6 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

250 4.16 GOT Transparent Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
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)
■For multiple CPUs
(0x3FF)
■For multiple CPUs
4
• 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)
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) Fixed to 0 (0x00) Target station Target station
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)
ActIONumber*1 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Target station side Fixed to 255 (0xFF) Fixed to 255 (0xFF)
module station number
ActTimeOut*3 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_A900GOT(0x21)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*3 When a value between 0 and 5000 [ms] is specified, the value is fixed to 5000 ms. Note that the value is fixed to 255000 ms when a
value greater than 255000 ms is specified.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 251
 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Bus connection

Configuration

Connected Relayed module

station CPU

GOT Relayed network

USB Bus

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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) 
Serial communication (3)  (3)  (3) 
CC-Link (4) (4) (4)  (4) 

Connected station CPU Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

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

*1 Redundant CPU cannot be accessed.

*2 Relayed station CPUs cannot be accessed via Q motion CPU.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE Field Network
cannot be accessed.
4
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 253
 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) (3) (4)
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)
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) Fixed to 0 (0x00) Target station Target station
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)
ActIONumber*1 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2 number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActProtocolType 0x04(PROTOCOL_ PROTOCOL_USBGOT(0x13)
SERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Target station side Fixed to 255 (0xFF) Fixed to 255 (0xFF)
module station number
ActTimeOut*3 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_A900GOT(0x21)
)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*3 When a value between 0 and 5000 [ms] is specified, the value is fixed to 5000 ms. Note that the value is fixed to 255000 ms when a
value greater than 255000 ms is specified.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

254 4.16 GOT Transparent Communication
Personal computer side port: Serial, GOT1000 side port: Serial,
CPU 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

Serial
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network 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
MELSECNET/H     
Ethernet (2)    
Serial communication (3)    
CC-Link (4) (4)   

Connected station CPU Relayed network Relayed station CPU

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)   
Serial communication (3)  (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 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 255
 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)
ActBaudRate 19200(BAUDRATE_1 Match to the setting of R series-compatible C24.
9200)
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RT Depending on the used cable.
S)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*2 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)
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 module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
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
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SE PROTOCOL_SERIAL
RIAL)
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)
ActParity 1(ODD_PARITY) Fixed to 1 (0x01)
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)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

256 4.16 GOT Transparent Communication
Property Default value Property patterns
(1) (2)*1 (3) (4)
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
4
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 257
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Serial communication module (2)
When performing multi-drop link on the connected station side R series-compatible C24 with the relayed module

Configuration

Connected station R series-compatible Relayed module

CPU C24

GOT Multi-drop link

Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
RCPU, R motion RCPU RCCPU R motion CPU LHCPU FX5CPU
CPU*1*4
Independent (1) Serial communication (2)    
mode*2

Connected station Relayed network Relayed station CPU

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

*1 Relayed station CPUs cannot be accessed via R motion CPU.

*2 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)
*3 Redundant CPU cannot be accessed.
*4 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

258 4.16 GOT Transparent Communication
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)
ActBaudRate 19200(BAUDRATE_19200) Match to the setting of R series-compatible C24.
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*1 0(0x00) Fixed to 0 (0x00) Target station side
■For single CPU
• Fixed to 1023 (0x3FF) 4
■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)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*1 1023(0x3FF) ■For single CPU Connected station side relayed module I/O
• Fixed to 1023 (0x3FF) address
■For multiple CPUs
• Connected CPU: 1023 (0x3FF)
• 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
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 1(ODD_PARITY)
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL
ActHostAddress 1.1.1.1 Fixed to NULL
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActDataBits 8(DATABIT_8) Fixed to 8 (0x08)
ActParity 1(ODD_PARITY) Fixed to 1 (0x01)
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)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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) Target station side module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_RJ71C24

*1 For the I/O address, specify the value obtained by dividing the actual start I/O number by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 259
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Serial communication module (3)
When a relayed module other than the connected station side Q series-compatible C24 exists

Configuration

Connected station Q series-compatible Relayed module

CPU C24

GOT Relayed network

Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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) 
Serial communication (3)  (3)  (3) 
CC-Link (4) (4) (4)  (4) 

*1 Redundant CPU cannot be accessed.

*2 Relayed station CPUs cannot be accessed via Q motion CPU.
*3 Since CC-Link IE Field Network is not supported, R motion CPU, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE
Field Network cannot be accessed.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

260 4.16 GOT Transparent Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
ActConnectUnitNumber 0(0x00) Connected station side module station number
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
(0x3FF)
• Fixed to 1023
(0x3FF)
4
■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)
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*1 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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
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_QJ71C24(0x19)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 261
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Serial communication module (4)
When performing multi-drop link on the connected station side Q series-compatible C24 with the relayed module

Configuration

Connected station Q series-compatible Relayed module

CPU C24

GOT Multi-drop link

Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
QCPU (Q mode)*1 RCPU RCCPU R motion CPU LHCPU FX5CPU
Independent (1) Serial communication     
mode*2

Connected station Relayed network Relayed station CPU

CPU
QCPU (Q mode)*1 QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
Independent (1) Serial communication (2)  (2)   
mode*2

*1 For redundant CPU, serial communication modules on the main base cannot be accessed.
*2 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)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

262 4.16 GOT Transparent Communication
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)
ActBaudRate 19200(BAUDRATE_1920 Q series BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
0) BAUDRATE_115200
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side
■For single CPU 4
• 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)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*2 1023(0x3FF) ■For single CPU Connected station side relayed module I/O
• Fixed to 1023 (0x3FF) address
■For multiple CPUs
• Connected CPU: 1023 (0x3FF)
• No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber*1 0(0x00) Fixed to 0 (0x00) Multi-drop channel number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Match to the setting of Q series-compatible C24.
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIA PROTOCOL_SERIAL(0x04)
L)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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) Target station side module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_QJ71C24(0x19)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 263
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Serial communication module (5)
When a relayed module other than the connected station side L series-compatible C24 exists

Configuration

Connected station L series-compatible Relayed module

CPU C24

GOT Relayed network

Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*2     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

264 4.16 GOT Transparent Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_1 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
9200) BAUDRATE_115200
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RT Depending on the used cable.
S)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00) 4
■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)
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Fixed to NULL
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*1 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side Connected station side Target station side
relayed module I/O relayed module I/O ■For single CPU
address address • 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)
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
ActParity 1(ODD_PARITY) Fixed to 1(ODD_PARITY)
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
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) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LJ71C24(0x54)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 265
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Serial communication module (6)
When performing multi-drop link on the connected station side L series-compatible C24 with the relayed module

Configuration

Connected station L series-compatible Relayed module

CPU C24

GOT Multi-drop link

Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
Independent (1) Serial communication     
mode*2

Connected station Relayed network Relayed station CPU

CPU
LCPU QCPU (Q mode)*1 QCCPU LCPU QSCPU Q motion CPU FXCPU
Independent (1) Serial communication (2)  (2)   
mode*2

*1 Redundant CPU cannot be accessed.

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

266 4.16 GOT Transparent Communication
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)
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
BAUDRATE_115200
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side
■For single CPU 4
• 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)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*1 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side relayed module I/O
address
ActMultiDropChannelNumber*2 0(0x00) Fixed to 0 (0x00) Multi-drop channel number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Match to the setting of L series-compatible C24.
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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) Target station side module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LJ71C24(0x54)

*1 For the I/O address, specify the value obtained by dividing the actual start I/O number by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 267
 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU 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
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network 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
MELSECNET/H     
Ethernet (2)  (2)  
Serial communication (3)  (3)  
CC-Link (4) (4) (4)  

Connected station CPU Relayed network Relayed station CPU

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)   
Serial communication (3)  (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 PROPERTY SETTINGS OF COMMUNICATION ROUTES

268 4.16 GOT Transparent Communication
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)
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
*2
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
• Connected CPU:
■For multiple CPUs
• Connected CPU:
4
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)
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) Fixed to 0 (0x00) Fixed to 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)
• No. 4: 995 (0x3E3)
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
ActProtocolType 0x04(PROTOCOL_ PROTOCOL_USBGOT
SERIAL)
ActPacketType 0x01(PACKET_PLC PACKET_PLC1
1)
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActHostAddress 1.1.1.1 Fixed to NULL
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
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)
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)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 269
 Property Default value Property patterns
(1) (2)*1 (3) (4)
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 to R series-compatible E71 parameter settings on the target
station side.
⋅ 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".
*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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

270 4.16 GOT Transparent Communication
Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Serial communication module (2)
When performing multi-drop link on the connected station side R series-compatible C24 with the relayed module

Configuration

Connected station R series-compatible

CPU C24

GOT Multi-drop link

USB
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
RCPU, R motion RCPU RCCPU R motion CPU LHCPU FX5CPU
CPU*1*4
Independent (1) Serial communication (2)    
mode*3

Connected station Relayed network Relayed station CPU

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

*1 Relayed station CPUs cannot be accessed via R motion CPU.

*2 Redundant CPU cannot be accessed.
*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)
*4 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 271
 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)
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
*1
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side
■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)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*1 1023(0x3FF) ■For single CPU Connected station side relayed module I/O
• Fixed to 1023 (0x3FF) address
■For multiple CPUs
• Connected CPU: 1023 (0x3FF)
• 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
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_SERIAL PROTOCOL_USBGOT
)
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActBaudRate 19200(BAUDRATE_19200) Fixed to 0 (0x00)
ActHostAddress 1.1.1.1 Fixed to NULL
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RTS) Fixed to 0 (0x00)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
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)
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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) Target station side module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_RJ71C24

*1 For the I/O address, specify the value obtained by dividing the actual start I/O number by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

272 4.16 GOT Transparent Communication
Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Serial communication module (3)
When a relayed module other than the connected station side Q series-compatible C24 exists

Configuration

Connected station Q series-compatible Relayed module

CPU C24

GOT Relayed network

USB
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network 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 Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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) 
Serial communication (3)  (3)  (3) 
CC-Link (4) (4) (4)  (4) 

*1 Redundant CPU cannot be accessed.

*2 Relayed station CPUs cannot be accessed via Q motion CPU.
*3 Since CC-Link IE Field Network is not supported, R motion CPU, Q12DCCPU-V (Basic mode) and Q motion CPU relayed by CC-Link IE
Field Network cannot be accessed.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 273
 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) (3) (4)
ActConnectUnitNumber 0(0x00) Connected station side module station number
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)
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*1 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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActProtocolType 0x04(PROTOCOL_ PROTOCOL_USBGOT(0x13)
SERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Target station side Fixed to 255 (0xFF) Fixed to 255 (0xFF)
module station number
ActThrough 0(0x00) • MELSECNET/10 is not included.: 0 (0x00)
NetworkType • 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_QJ71C24(0x19)
)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

274 4.16 GOT Transparent Communication
Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Serial communication module (4)
When performing multi-drop link on the connected station side Q series-compatible C24 with the relayed module

Configuration

Connected station Q series-compatible

CPU C24

GOT Multi-drop link

USB
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
QCPU (Q mode)*1 RCPU RCCPU R motion CPU LHCPU FX5CPU
Independent (1) Serial communication     
mode*2

Connected station Relayed network Relayed station CPU

CPU
QCPU (Q mode)*1 QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
Independent (1) Serial communication (2)  (2)   
mode*2

*1 Redundant CPU cannot be accessed.

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 275
 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)
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side
■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)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*1 1023(0x3FF) ■For single CPU Connected station side relayed module I/
• Fixed to 1023 (0x3FF) O address
■For multiple CPUs
• Connected CPU: 1023 (0x3FF)
• 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
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_USBGOT(0x13)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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) Target station side module station
number
ActUnitType 0x13(UNIT_QNCPU) UNIT_QJ71C24(0x19)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

276 4.16 GOT Transparent Communication
Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Serial communication module (5)
When a relayed module other than the connected station side L series-compatible C24 exists

Configuration

Connected station L series-compatible Relayed module

CPU C24

GOT Relayed network

USB
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*2     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 277
 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) (3) (4)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
■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)
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Fixed to NULL
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
*1
ActIONumber 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side Connected station side Target station side
relayed module I/O relayed module I/O ■For single CPU
address address • 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)
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
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USBGOT(0x13)
ERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
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) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LJ71C24(0x54)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

278 4.16 GOT Transparent Communication
Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Serial communication module (6)
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
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station Relayed network Relayed station CPU
CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
Independent (1) Serial communication     
mode*2

Connected station Relayed network Relayed station CPU

CPU
LCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
Independent (1) Serial communication (2)  (2)   
mode*2

*1 Redundant CPU cannot be accessed.

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 279
 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)
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side
■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)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*1 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side relayed module I/
O address
ActMultiDropChannelNumber*2 0(0x00) Fixed to 0 (0x00) Multi-drop channel number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_SERIAL PROTOCOL_USBGOT(0x13)
)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF)
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) Target station side module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_LJ71C24(0x54)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

280 4.16 GOT Transparent Communication
Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: R series-compatible E71

Configuration

Connected station R series-compatible Relayed module

CPU E71

GOT Relayed network

Serial Ethernet

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
RCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet (2)    
Serial communication (3)    
CC-Link (4) (4)   

Connected Relayed network Relayed station CPU

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

*1 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 281
 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) (3) (4)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
ActConnectUnitNumber*1 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*2 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)
ActDestinationPortNumber 0(0x00) 5001
Host station port number for OPS connection*3
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIONumber*2 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*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
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL
ERIAL)
ActPacketType 0x01(PACKET_PLC PACKET_PLC1
1)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_R Depending on the used cable.
TS)
ActDataBits 8(DATABIT_8) Fixed to 8 (0x08)
ActParity 1(ODD_PARITY) Fixed to 1 (0x01)
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK Fixed to 0 (0x00)
)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
*6
ActSourceNetworkNumber 0(0x00) GOT side network number
ActSourceStationNumber*7 0(0x00) GOT side station number
*5
ActStationNumber 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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

282 4.16 GOT Transparent Communication
Property Default value Property patterns
(1) (2) (3) (4)
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_GOT_RJ71EN71

*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.
*2 For the I/O address, specify the value obtained by dividing the actual start I/O number by 16.
*3 When using OPS connection function at redundant CPU connection, set the port No. specified to "Host Station Port No." in Network
parameter.
*4 Specify the following value for the channel number to be multi-drop linked. 4
0: Default channel of module
1: Channel 1
2: Channel 2
*5 For the property pattern of (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 283
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Q series-compatible E71

Configuration

Connected station Q series-compatible Relayed module

CPU E71

GOT Relayed network

Serial Ethernet

Relayed station
Personal computer Relayed module
CPU

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

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
QCPU (Q mode) RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

284 4.16 GOT Transparent Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
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
• Fixed to 1023
■For single CPU
• Fixed to 1023
4
(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)
ActDestinationPortNumber 0(0x00) 5001
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIONumber*1 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2 number
ActNetworkNumber*3 0(0x00) Target station side Target station side Connected station side Connected station side
module network module network Q series-compatible Q series-compatible
number number E71 network number E71 network number
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
ActSourceNetworkNumber 0(0x00) GOT side network number
ActSourceStationNumber*4 0(0x00) GOT side station number
ActStationNumber*3 255(0xFF) Target station side Target station side Connected station side Connected station side
module station number module station number Q series-compatible Q series-compatible
E71 station number E71 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_GOT_QJ71E71(0x40)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 285
 *1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*3 For the property pattern of (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

286 4.16 GOT Transparent Communication
Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: L series-compatible E71

Configuration

Connected station L series-compatible Relayed module

CPU E71

GOT Relayed network

Serial Ethernet

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

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

station CPU
LCPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)*1
(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)   

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 For redundant CPU, serial communication modules on the main base cannot be accessed because the multi-drop connection cannot be
performed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 287
 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) (3) (4)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
ActConnectUnitNumber*1 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActControl 8(TRC_DTR_OR_R Depending on the used cable.
TS)
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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber*2 0(0x00) 5001
Host station port number for OPS connection
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIONumber*3 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
1023 (0x3FF) • No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*4 number
ActNetworkNumber*5 0(0x00) Target station side Target station side Connected station side Connected station side
module network module network L series-compatible L series-compatible
number number E71 network number E71 network number
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
ActSourceNetworkNumber*6 0(0x00) GOT side network number
ActSourceStationNumber*7 0(0x00) GOT 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 L series-compatible L series-compatible
E71 station number E71 station number

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

288 4.16 GOT Transparent Communication
Property Default value Property patterns
(1) (2) (3) (4)
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_GOT_LJ71E71(0x5D)

*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.
*2 When using OPS connection function at redundant CPU connection, set the port No. specified to "Host Station Port No." in Network
parameter.
*3 For the I/O address, specify the value of the actual start I/O number divided by 16.
*4 Specify the following value for the channel number to be multi-drop linked. 4
0: Default channel of module
1: Channel 1
2: Channel 2
*5 For the property pattern of (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 289
 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: R series-compatible E71

Configuration

Connected station R series-compatible Relayed module

CPU E71

GOT Relayed network

USB Ethernet

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station CPU
RCPU RCCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*1 (1)*1,*2 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet (2)    
Serial communication (3)    
CC-Link (4) (4)   

Connected station CPU Relayed network Relayed station CPU

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

*1 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

290 4.16 GOT Transparent Communication
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) (3) (4)
*1
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*2 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)
■For multiple CPUs
(0x3FF)
■For multiple CPUs
4
• 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)
ActDestinationPortNumber 0(0x00) 5001
Host station port number for OPS connection*3
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIONumber*2 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*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
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USBGOT
ERIAL)
ActPacketType 0x01(PACKET_PLC PACKET_PLC1
1)
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK Fixed to 0 (0x00)
)
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
*6
ActSourceNetworkNumber 0(0x00) GOT side network number
ActSourceStationNumber*7 0(0x00) GOT side station number
*5
ActStationNumber 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 network number E71 network number

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 291
 Property Default value Property patterns
(1) (2) (3) (4)
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_GOT_RJ71EN71

*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.
*2 For the I/O address, specify the value obtained by dividing the actual start I/O number by 16.
*3 When using OPS connection function at redundant CPU connection, set the port No. specified to "Host Station Port No." in Network
parameter.
*4 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*5 For the property pattern of (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

292 4.16 GOT Transparent Communication
Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Q series-compatible E71

Configuration

Connected station Q series-compatible Relayed module

CPU E71

GOT Relayed network

USB Ethernet

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

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station CPU
QCPU (Q QCCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
mode)
(1)*1 (1)*4 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
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)     
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Only CPU No.2 or later in a multiple CPU configuration can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 293
 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) (3) (4)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) 5001
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIONumber*1 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
1023 (0x3FF) • No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2 number
ActNetworkNumber*3 0(0x00) Target station side Target station side Connected station side Connected station side
module network module network Q series-compatible Q series-compatible
number number E71 network number E71 network number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USBGOT(0x13)
ERIAL)
ActSourceNetworkNumber 0(0x00) GOT side network number
ActSourceStationNumber*4 0(0x00) GOT side station number
ActStationNumber*3 255(0xFF) Target station side Target station side Connected station side Connected station side
module station number module station number Q series-compatible Q series-compatible
E71 station number E71 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_GOT_QJ71E71(0x40)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

294 4.16 GOT Transparent Communication
*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*3 For the property pattern of (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 295
 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: L series-compatible E71

Configuration

Connected station L series-compatible Relayed module

CPU E71

GOT Relayed network

USB Ethernet

Relayed station
Personal computer Relayed module
CPU

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

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 For redundant CPU, serial communication modules on the main base cannot be accessed because the multi-drop connection cannot be
performed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

296 4.16 GOT Transparent Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActConnectUnitNumber*1 0(0x00) Fixed to 0 (0x00) Connected station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station 4
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber*2 0(0x00) 5001
Host station port number for OPS connection
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIONumber*3 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• Control system: 976 ■For redundant CPU
(0x3D0) • Control system: 976
• No specification: (0x3D0)
1023 (0x3FF) • No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*4 number
ActNetworkNumber*5 0(0x00) Target station side Target station side Connected station side Connected station side
module network module network L series-compatible L series-compatible
number number E71 network number E71 network number
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USBGOT(0x13)
ERIAL)
ActSourceNetworkNumber*6 0(0x00) GOT side network number
ActSourceStationNumber*7 0(0x00) GOT side station number

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 297
 Property Default value Property patterns
(1) (2) (3) (4)
*5
ActStationNumber 255(0xFF) Target station side Target station side Connected station side Connected station side
module station number module station number L series-compatible L series-compatible
E71 station number E71 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_GOT_LJ71E71(0x5D)

*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.
*2 When using OPS connection function at redundant CPU connection, set the port No. specified to "Host Station Port No." in Network
parameter.
*3 For the I/O address, specify the value of the actual start I/O number divided by 16.
*4 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2
*5 For the property pattern of (1) or (2), specify the value set in the target station side parameter for ActNetworkNumber and
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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

298 4.16 GOT Transparent Communication
Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Ethernet port (1)
When the connected station is RCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Serial Ethernet
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station CPU
RCPU RCCPU R motion RCPU RCCPU R motion LHCPU FX5CPU
CPU CPU
(1) (1)*3 (1)*1*3 CC IE TSN     
CC IE Control (2)*2 (2)   (2)*5
CC IE Field
MELSECNET/H     
Ethernet (2)*4    
Serial communication (3)*4    
CC-Link (4) (4)   (4)

Connected station CPU Relayed network Relayed station CPU

RCPU RCCPU R motion QCPU (Q QCCPU LCPU QSCP Q motion FXCP
CPU mode) U CPU U
(1) (1)*3 (1)*1*3 CC IE TSN      
CC IE Control (2)  (2)*2   
CC IE Field
MELSECNET/H (2)*4     
Ethernet (2)*4  (2)*4   
Serial communication (3)*4  (3)*4   
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 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.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 299
 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)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*2 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)
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
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)
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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*3 number
ActNetworkNumber*4 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL
ERIAL)
ActPacketType 0x01(PACKET_PLC PACKET_PLC1
1)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_R Depending on the used cable.
TS)
ActDataBits 8(DATABIT_8) Fixed to 8 (0x08)
ActParity 1(ODD_PARITY) Fixed to 1 (0x01)
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)
ActDestinationPortNumber 0(0x00) 5006

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

300 4.16 GOT Transparent Communication
Property Default value Property patterns
(1) (2)*1 (3) (4)
*4
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 not
• MELSECNET/10 is included.: 1 (0x01) included.: 0 (0x00)
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_GOT_RETHER

*1 Note the following considerations when accessing via Ethernet module (R series-compatible E71).
⋅ For ActNetworkNumber and ActStationNumber, specify the value set to R series-compatible E71 parameter settings on the target
station side.
⋅ Set "MNET/10 routing information" to R series-compatible E71 parameter setting. When setting parameters, specify other than 4
Automatic Response System (any of IP address calculation system, table conversion system, or combined system) for "MNET/10
routing method".
*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
*4 For the property pattern of (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 301
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Ethernet port (2)
When the connected station is FX5CPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Serial Ethernet

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FX5CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     (3)

Connected Relayed network Relayed station CPU

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

*1 Only CC-Link IE Field Network can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

302 4.16 GOT Transparent Communication
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) (3)
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
BAUDRATE_115200
ActConnectUnitNumber 0(0x00) 0(0x00)
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuTimeOut 0(0x00) 0(0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) 8(DATABIT_8)
4
ActDestinationIONumber 0(0x00) 0(0x00) 1023(0x3FF)
ActDestinationPortNumber 0(0x00) 5562
ActDidPropertyBit 1(0x01) 1(0x01) 0(0x00)
ActDsidPropertyBit 1(0x01) 1(0x01) 0(0x00)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side IP address of a connected
module station CPU
ActIntelligentPreferenceBit 0(0x00) 0(0x00) 1(0x01)
ActIONumber 1023(0x3FF) 1023(0x3FF) Module number of the
connected station
ActMultiDropChannelNumber 0(0x00) 0(0x00)
ActNetworkNumber 0(0x00) 0(0x00) Target station side module 0(0x00)
network number
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1(0x01)
ActParity 1(ODD_PARITY) 1(ODD_PARITY)
ActPassword Null Null
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL(0x04)
ActStopBits 0(STOPBIT_ONE) 0(STOPBIT_ONE)
ActSumCheck 0(NO_SUM_CHECK) 0(NO_SUM_CHECK)
ActSourceNetworkNumber 0(0x00) 0(0x00)
ActSourceStationNumber 0(0x00) 0(0x00)
ActStationNumber 255(0xFF) 255(0xFF) Target station side module 255(0xFF)
station number
ActTargetSimulator 0(0x00) 0(0x00)
ActThroughNetworkType 0(0x00) 0(0x00)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) 0(0x00) Target station side module
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOT_FXVETHER(0x2007)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 303
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Ethernet port (3)
When the connected station is QnUDE(H)CPU or QCCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Serial Ethernet

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU*1
QnUDE(H)CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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)     
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

304 4.16 GOT Transparent Communication
Connected Relayed network Relayed station CPU
station CPU
QCCPU QCPU (Q mode)*2 QCCPU LCPU QSCPU Q motion CPU FXCPU
(1)*5 CC IE TSN      
*3 *4
CC IE Control (2) (2) (2)   
CC IE Field
MELSECNET/H (2) (2)    
Ethernet      
Serial communication      
CC-Link (4) (4) (4)   

*1 The communication cannot be established when a remote password is set to the connected station CPU.
*2 Redundant CPU cannot be accessed.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
4
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*5 Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS cannot be accessed because the communication route is
not supported.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 305
 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)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
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
• Control system: 976
(0x3D0)
• 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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
QCPU (Q mode), QCPU (Q mode),
LCPU: 1 (0x01) QCCPU, LCPU: 1
Other than the above: (0x01)
0 (0x00) Other than the above:
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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• 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*4 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
ActStationNumber*4 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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

306 4.16 GOT Transparent Communication
Property Default value Property patterns
(1) (2)*1 (3) (4)
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOT_QNETHER(0x41)

*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
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 of the actual start I/O number divided by 16.
*3 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1

*4
2: Channel 2
For the property pattern of (2), specify the value set in the target station side parameter for ActNetworkNumber and
4
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 307
 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Ethernet port (4)
When the connected station is LCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Serial Ethernet

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU*1
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*3     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 The communication cannot be established when a remote password is set to the connected station CPU.
*2 Redundant CPU cannot be accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

308 4.16 GOT Transparent Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
ActControl 8(TRC_DTR_OR_R Depending on the used cable.
TS)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
■For single CPU
• Fixed to 1023
■For single CPU
• Fixed to 1023
4
(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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) 5006
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
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)
ActIONumber*1 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side Connected station side Target station side
relayed module I/O relayed module I/O ■For single CPU
address address • 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)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
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
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
module station number
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00)
• MELSECNET/10 is included.: 1 (0x01)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 309
 Property Default value Property patterns
(1) (2) (3) (4)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOT_LNETHER(0x55)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

310 4.16 GOT Transparent Communication
Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Ethernet port (1)
When the connected station is RCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

USB Ethernet
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network 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
MELSECNET/H     
Ethernet (2)    
Serial communication (3)    
CC-Link (4) (4)   (4)

Connected station CPU Relayed network Relayed station CPU

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 Control      
CC IE Field
MELSECNET/H      
Ethernet   (2)   
Serial communication      
CC-Link      

*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 Only CC-Link IE Field Network on which connected station CPU is RCPU can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 311
 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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*2 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)
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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
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)
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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*3
number
ActNetworkNumber*4 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USBGOT
ERIAL)
ActPacketType 0x01(PACKET_PLC PACKET_PLC1
1)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK Fixed to 0 (0x00)
)
ActSourceStationNumber 0(0x00) Fixed to 0 (0x00)
ActDestinationPortNumber 0(0x00) 5006
ActStationNumber*4 255(0xFF) Fixed to 255 (0xFF) Target station side Fixed to 255 (0xFF) Fixed to 255 (0xFF)
module station number

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

312 4.16 GOT Transparent Communication
Property Default value Property patterns
(1) (2)*1 (3) (4)
ActThroughNetworkType 0(0x00) • MELSECNET/10 is not included.: 0 (0x00) MELSECNET/10 is not
• MELSECNET/10 is included.: 1 (0x01) included.: 0 (0x00)
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_GOT_RETHER

*1 Note the following considerations when accessing via Ethernet module (R series-compatible E71).
⋅ For ActNetworkNumber and ActStationNumber, specify the value set to R series-compatible E71 parameter settings on the target
station side.
⋅ 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". 4
*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
*4 For the property pattern of (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 313
 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Ethernet port (2)
When the connected station is FX5CPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

USB Ethernet

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FX5CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     (3)

Connected Relayed network Relayed station CPU

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

*1 Only CC-Link IE Field Network can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

314 4.16 GOT Transparent Communication
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) (3)
ActBaudRate 19200(BAUDRATE_19200) 0(0x00)
ActConnectUnitNumber 0(0x00) 0(0x00)
ActControl 8(TRC_DTR_OR_RTS) 0(0x00)
ActCpuTimeOut 0(0x00) 0(0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits
ActDestinationIONumber
8(DATABIT_8)
0(0x00)
0(0x00)
0(0x00) 1023(0x3FF)
4
ActDestinationPortNumber 0(0x00) 5562
ActDidPropertyBit 1(0x01) 1(0x01) 0(0x00)
ActDsidPropertyBit 1(0x01) 1(0x01) 0(0x00)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side IP address of a connected
module station CPU
ActIntelligentPreferenceBit 0(0x00) 0(0x00) 1(0x01)
ActIONumber 1023(0x3FF) 1023(0x3FF) Module number of the
connected station
ActMultiDropChannelNumber 0(0x00) 0(0x00)
ActNetworkNumber 0(0x00) 0(0x00) Target station side module 0(0x00)
network number
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1(0x01)
ActParity 1(ODD_PARITY) 0(0x00)
ActPassword Null Null
ActPortNumber 1(PORT_1) 1(0x01)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_USBGOT(0x13)
ActStopBits 0(STOPBIT_ONE) 0(0x00)
ActSumCheck 0(NO_SUM_CHECK) 0(0x00)
ActSourceNetworkNumber 0(0x00) 0(0x00)
ActSourceStationNumber 0(0x00) 0(0x00)
ActStationNumber 255(0xFF) 255(0xFF) Target station side module 255(0xFF)
station number
ActTargetSimulator 0(0x00) 0(0x00)
ActThroughNetworkType 0(0x00) 0(0x00)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) 0(0x00) Target station side module
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOT_FXVETHER(0x2007)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 315
 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Ethernet port (3)
When the connected station is QCPU (Q mode) or QCCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

USB Ethernet

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU*1
QnUDE(H)CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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)     
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

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

*1 The communication cannot be established when a remote password is set to the connected station CPU.
*2
*3
Redundant CPU cannot be accessed.
Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
4
accessed.
*4 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 317
 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)
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
• Control system: 976
(0x3D0)
• 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)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
QCPU (Q mode), QCPU (Q mode),
LCPU: 1 (0x01) QCCPU, LCPU:1
Other than the above: (0x01)
0 (0x00) Other than the above:
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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• 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*4 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USBGOT(0x13)
ERIAL)
ActStationNumber*4 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_GOT_QNETHER(0x41)

*1 Note the following considerations when accessing via Ethernet module (Q series-compatible E71).

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

318 4.16 GOT Transparent Communication
 ⋅ 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
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 of the actual start I/O number divided 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
*4 For the property pattern of (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 319
 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Ethernet port (4)
When the connected station is LCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

USB Ethernet

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU*1
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*3     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 The communication cannot be established when a remote password is set to the connected station CPU.
*2 Redundant CPU cannot be accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

320 4.16 GOT Transparent Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00) 4
■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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) 5006
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
QCPU (Q mode), QCPU (Q mode),
LCPU: 1 (0x01) QCCPU, LCPU: 1
Other than the above: (0x01)
0 (0x00) Other than the above:
0 (0x00)
ActIONumber*1 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side Connected station side Target station side
relayed module I/O relayed module I/O ■For single CPU
address address • 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)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
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
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USBGOT(0x13)
ERIAL)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 321
 Property Default value Property patterns
(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
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) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOT_LNETHER(0x55)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

322 4.16 GOT Transparent Communication
Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Ethernet adapter module

Configuration

Connected station CC-Link IE Field Relayed module

CPU Network module

Ethernet Adapter
GOT Relayed network
module

Serial Ethernet
Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
QnUDE(H)CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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)     
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 323
 Connected Relayed network Relayed station CPU
station CPU
LCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
(1) CC IE TSN      
CC IE Field*3 (2) (2)*2 (2)   
MELSECNET/H      
Ethernet      
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

324 4.16 GOT Transparent Communication
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) (3) (4)
ActBaudRate 19200(BAUDRATE_ BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
19200) BAUDRATE_115200
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)
■For multiple CPUs
(0x3FF)
■For multiple CPUs
4
• 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
• Control system: 976
(0x3D0)
• 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)
ActHostAddress 1.1.1.1 Host name or IP address of Ethernet adapter module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
*1
ActIONumber 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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*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 number Network module Network module
network number network number network number
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_SERIAL(0x04)
ERIAL)
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
number number 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_GOT_NZ2GF_ETB(0x5B)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 325
 *1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
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
connected station side for ActNetworkNumber and ActStationNumber.
For the property pattern of (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

326 4.16 GOT Transparent Communication
Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Ethernet adapter module

Configuration

Connected station CC-Link IE Field Relayed module

CPU Network module

Ethernet Adapter
GOT Relayed network
module

Serial Ethernet
Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
QnUDE(H)CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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)     
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

Connected Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 327
 Connected Relayed network Relayed station CPU
station CPU
LCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode)*1 CPU
(1) CC IE TSN      
CC IE Field*3 (2)  (2)   
MELSECNET/H      
Ethernet      
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

328 4.16 GOT Transparent Communication
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) (3) (4)
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) 4
• 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
• Control system: 976
(0x3D0)
• 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)
ActHostAddress 1.1.1.1 Host name or IP address of Ethernet adapter module
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
*1
ActIONumber 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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*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 number Network module Network module
network number network number network number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_USBGOT(0x13)
ERIAL)
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
number number 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_GOT_NZ2GF_ETB(0x5B)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 329
 *1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
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
connected station side for ActNetworkNumber and ActStationNumber.
For the property pattern of (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

330 4.16 GOT Transparent Communication
Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Ethernet adapter/module (1)
When the connected station is FXCPU

Configuration
Ethernet adapter: FX3U-ENET-ADP

Ethernet adapter Connected station Relayed module

CPU

Serial
GOT
Ethernet
Relayed network
4
Relayed station
Personal computer Relayed module
CPU

Ethernet module: FX3U-ENET (-L)

Ethernet module Connected station Relayed module

CPU

GOT Relayed network

Serial Ethernet

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Only FX3SCPU(FX3U-ENET-ADP), FX3G(C)CPU and FX3U(C)CPU can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 331
 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)
ActBaudRate 19200(BAUDRATE_19200) BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
BAUDRATE_115200
ActControl 8(TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
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
ActPortNumber 1(PORT_1) Personal computer side COM port number
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_SERIAL
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) FX3U-ENET-ADP: UNIT_GOT_FXETHER
FX3U-ENET(-L): UNIT_GOT_FXENET

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

332 4.16 GOT Transparent Communication
Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Ethernet adapter/module (1)
When the connected station is FXCPU

Configuration
Ethernet adapter: FX3U-ENET-ADP

Ethernet adapter Connected station Relayed module

CPU
Ethernet

4
GOT Relayed network
USB

Relayed station
Personal computer Relayed module
CPU

Ethernet module: FX3U-ENET (-L)

Ethernet module Connected station Relayed module

CPU
Ethernet
GOT Relayed network
USB

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Only FX3SCPU(FX3U-ENET-ADP), FX3G(C)CPU and FX3U(C)CPU can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 333
 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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
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
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) FX3U-ENET-ADP: UNIT_GOT_FXETHER
FX3U-ENET(-L): UNIT_GOT_FXENET

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

334 4.16 GOT Transparent Communication
Personal computer side port: Ethernet board, GOT2000/1000 side
port: Ethernet port, CPU side port: Serial (1)
When the connected station is FX5CPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Ethernet Serial
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FX5CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     (2)*1
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     (3)

Connected Relayed network Relayed station CPU

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

*1 Only CC-Link IE Field Network can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 335
 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) (3)
ActBaudRate 19200(BAUDRATE_19200) 0(0x00)
ActConnectUnitNumber 0(0x00) 0(0x00)
ActControl 8(TRC_DTR_OR_RTS) 0(0x00)
ActCpuTimeOut 0(0x00) 0(0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits 8(DATABIT_8) 0(0x00)
ActDestinationIONumber 0(0x00) 0(0x00) 1023(0x3FF)
ActDestinationPortNumber 0(0x00) GOT port number
ActDidPropertyBit 1(0x01) 1(0x01) 0(0x00)
ActDsidPropertyBit 1(0x01) 1(0x01) 0(0x00)
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActIntelligentPreferenceBit 0(0x00) 0(0x00) 1(0x01)
ActIONumber 1023(0x3FF) 1023(0x3FF) Module number of the
connected station
ActMultiDropChannelNumber 0(0x00) 0(0x00)
ActNetworkNumber 0(0x00) 0(0x00) Target station side module 0(0x00)
network number
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1(0x01)
ActParity 1(ODD_PARITY) 1(0x01)
ActPassword Null Null
ActPortNumber 1(PORT_1) 0(0x00)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_TCPIP(0x05)
ActStopBits 0(STOPBIT_ONE) 0(0x00)
ActSumCheck 0(NO_SUM_CHECK) 0(0x00)
ActSourceNetworkNumber 0(0x00) 0(0x00)
ActSourceStationNumber 0(0x00) 0(0x00)
ActStationNumber 255(0xFF) 255(0xFF) Target station side module 255(0xFF)
station number
ActTargetSimulator 0(0x00) 0(0x00)
ActThroughNetworkType 0(0x00) 0(0x00)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) 0(0x00) Target station side module
station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOTETHER_FXVCPU(0x2006)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

336 4.16 GOT Transparent Communication
Personal computer side port: Ethernet board, GOT2000/1000 side
port: Ethernet port, CPU side port: Serial (2)
When the connected station is QCPU (Q mode) or QCCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Ethernet Serial
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station CPU
QCPU (Q QCCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
mode)
(1)*1 (1)*4 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
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      
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*4 For Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG and Q26DHCCPU-LS, only CPU No.2 or later in a multiple CPU configuration
can be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 337
 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) (3) (4)
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
• Control system: 976
(0x3D0)
• No specification: 1023
(0x3FF)
ActDestinationPortNumber 0(0x00) GOT port number
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)
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
QCPU (Q mode), QCPU (Q mode),
LCPU: 1 (0x01) QCCPU, LCPU: 1
Other than the above: (0x01)
0 (0x00) Other than the above: 0
(0x00)
ActIONumber*1 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2 number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
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_GOTETHER_QNCPU(0x56)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

338 4.16 GOT Transparent Communication
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 339
 Personal computer side port: Ethernet board, GOT2000/1000 side
port: Ethernet port, CPU side port: Serial (3)
When the connected station is LCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Ethernet Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*2     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

340 4.16 GOT Transparent Communication
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) (3) (4)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
■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) 4
• 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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) GOT port number
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
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)
ActIONumber*1 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side Connected station side Target station side
relayed module I/O relayed module I/O ■For single CPU
address address • 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)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
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
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
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) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOTETHER_LNCPU(0x57)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 341
 *1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

342 4.16 GOT Transparent Communication
Personal computer side port: Ethernet board, GOT2000/1000 side
port: Ethernet port, CPU side port: Serial (4)
When the connected station is FXCPU

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Ethernet Serial
4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
FXCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationPortNumber*1 0(0x00) GOT port number
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_TCPIP
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOTETHER_FXCPU

*1 For ActPortNumber, specify the value set to GOT side.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 343
 Personal computer side port: Ethernet board, GOT2000/1000 side
port: Ethernet port, CPU side port: Serial communication module
(1)
When the connected station is R series-compatible C24

Configuration

Connected station R series-compatible Relayed module

CPU C24

GOT Relayed network

Ethernet Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station CPU
RCP R motion CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
U
(1) (1)*1*3 CC IE TSN     
*2
CC IE Control (4) (4)   
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication (2)    
CC-Link (3) (3)   

Connected station CPU Relayed network Relayed station CPU

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

*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 PROPERTY SETTINGS OF COMMUNICATION ROUTES

344 4.16 GOT Transparent Communication
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) (3) (4)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber*1 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) 4
• 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
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)
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
RCPU, QCPU (Q RCPU, QCPU (Q
mode), LCPU: 1 (0x01) mode), QCCPU,
Other than the above: 0 LCPU: 1 (0x01)
(0x00) Other than the above: 0
(0x00)
ActIONumber*1 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*3 number
ActNetworkNumber*4 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP
ERIAL)
ActPacketType 0x01(PACKET_PLC PACKET_PLC1
1)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActBaudRate 19200(BAUDRATE_ Fixed to 0 (0x00)
19200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_R Fixed to 0 (0x00)
TS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
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)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 345
 Property Default value Property patterns
(1) (2) (3) (4)
*4
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_GOTETHER_RJ71C24

*1 For the I/O address, specify the value obtained by dividing the actual start I/O number by 16.
*2 Specify the value set to GOT side for ActDestinationPortNumber.
*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
*4 For the property pattern of (2), specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

346 4.16 GOT Transparent Communication
Personal computer side port: Ethernet board, GOT2000/1000 side
port: Ethernet port, CPU side port: Serial communication module
(2)
When the connected station is Q series-compatible C24

Configuration

Connected station Q series-compatible Relayed module

CPU C24

Ethernet
GOT
Serial
Relayed network 4
Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station CPU
QCPU (Q QCCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
mode)
(1)*1 (1) CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q QCCPU QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
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)    
Ethernet      
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 347
 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) (3) (4)
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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) GOT port number
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)
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
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)
ActIONumber*1 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2
number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
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_GOTETHER_QNCPU(0x56)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

348 4.16 GOT Transparent Communication
*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 349
 Personal computer side port: Ethernet board, GOT2000/1000 side
port: Ethernet port, CPU side port: Serial communication module
(3)
When the connected station is L series-compatible C24

Configuration

Connected station L series-compatible Relayed module

CPU C24

GOT Relayed network

Ethernet Serial

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected Relayed network Relayed station CPU
station CPU
LCPU RCPU RCCPU R motion CPU LHCPU FX5CPU
(1) CC IE TSN     
CC IE Field*2     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected Relayed network Relayed station CPU

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

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.
*3 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

350 4.16 GOT Transparent Communication
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) (3) (4)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0(0x00) Fixed to 0 (0x00) Target station side Target station side Fixed to 0 (0x00)
■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) 4
• 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
• Control system: 976
(0x3D0)
• No specification:
1023 (0x3FF)
ActDestinationPortNumber 0(0x00) GOT port number
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Target station Target station Fixed to 0 (0x00)
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)
ActIONumber*1 1023(0x3FF) Fixed to 1023 (0x3FF) Connected station side Connected station side Target station side
relayed module I/O relayed module I/O ■For single CPU
address address • 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)
■For redundant CPU
• Control system: 976
(0x3D0)
• No specification:
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
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
ActStationNumber 255(0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Target station side
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) Target station side Target station side Fixed to 0 (0x00)
module station number module station number
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOTETHER_LNCPU(0x57)

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 351
 *1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

352 4.16 GOT Transparent Communication
Personal computer side port: Ethernet board, GOT2000/1000 side
port: Ethernet port, CPU side port: Bus connection

Configuration

Connected Relayed module

station CPU

GOT Relayed network

Ethernet Bus

Personal computer
Relayed station
CPU
Relayed module 4

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station CPU
QCPU (Q mode) RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

QCPU (Q mode) 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)    
Ethernet      
Serial communication (3)  (3)   
CC-Link (4) (4) (4)   

Connected station CPU Relayed network Relayed station CPU

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

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

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

*1 Redundant CPU cannot be accessed.

*2 Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*3 Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be accessed.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

354 4.16 GOT Transparent Communication
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) (3) (4)
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 (0x3FF) • Fixed to 1023
■For multiple CPUs (0x3FF)
• Connected CPU: ■For multiple CPUs
1023 (0x3FF) • Connected CPU:
• No. 1: 992 (0x3E0) 1023 (0x3FF) 4
• 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)
ActDestinationPortNumber 0(0x00) GOT port number
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)
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Target station Target station
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)
ActIONumber*1 1023(0x3FF) ■For single CPU Target station side Connected station side Connected station side
• Fixed to 1023 ■For single CPU module I/O address module I/O address
(0x3FF) • Fixed to 1023
■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)
• No. 4: 995 (0x3E3)
ActMultiDropChannelNumber 0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Multi-drop channel Fixed to 0 (0x00)
*2 number
ActNetworkNumber 0(0x00) Fixed to 0 (0x00) Target station side Fixed to 0 (0x00) Fixed to 0 (0x00)
module network
number
ActProtocolType 0x04(PROTOCOL_S PROTOCOL_TCPIP(0x05)
ERIAL)
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_GOTETHER_QBUS(0x58)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.
*2 Specify the following value for the channel number to be multi-drop linked.
0: Default channel of module
1: Channel 1
2: Channel 2

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 355
 Personal computer side port: Ethernet board, GOT2000/1000 side
port: Ethernet port, CPU side port: Ethernet port

Configuration

Connected station Relayed module

CPU

GOT Relayed network

Ethernet Ethernet

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station CPU
QCPU (Q mode) RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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

*1 Only operates for Qn(U)(J)(P)(D)(E)(V)(H). QnPRHCPU cannot be accessed because it is not supported.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

356 4.16 GOT Transparent Communication
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)
ActBaudRate 19200(BAUDRATE_19200) Fixed to 0 (0x00)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RTS) Fixed to 0 (0x00)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits
ActDestinationIONumber
8(DATABIT_8)
0(0x00)
Fixed to 0 (0x00)
Fixed to 0 (0x00)
4
ActDestinationPortNumber*1 0(0x00) GOT port number
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*2 1023(0x3FF) ■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)
ActMultiDropChannelNumber*3 0(0x00) Fixed to 0 (0x00)
*4
ActNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_TCPIP(0x05)/PROTOCOL_UDPIP(0x08)
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK) Fixed to 0 (0x00)
ActSourceNetworkNumber*5 0(0x00) Fixed to 0 (0x00)
*6
ActSourceStationNumber 0(0x00) Fixed to 0 (0x00)
ActStationNumber*4 255(0xFF) Fixed to 255 (0xFF)
ActThroughNetworkType 0(0x00) Fixed to 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Fixed to 0 (0x00)
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOTETHER_QN_ETHER(0x6F)

*1 Specify the value set on the GOT side.

*2 For the I/O address, specify the value of the actual start I/O number divided 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
*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 station number of the personal computer-side not to duplicate it with that set for QJ71E71 in the same Ethernet network.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 357
 Personal computer side port: Ethernet board, GOT2000/1000 side
port: Ethernet port, CPU side port: Q series-compatible E71

Configuration

Connected station Q series-compatible Relayed module

CPU E71

GOT Relayed network

Ethernet Ethernet

Relayed station
Personal computer Relayed module
CPU

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Connected station CPU Relayed network Relayed station CPU
QCPU (Q mode) RCPU RCCPU R motion CPU LHCPU FX5CPU
(1)*1 CC IE TSN     
CC IE Control     
CC IE Field
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

Connected station CPU Relayed network Relayed station CPU

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

*1 Only operates for Qn(U)(J)(P)(D)(E)(V)(H). QnPRHCPU cannot be accessed because it is not supported.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

358 4.16 GOT Transparent Communication
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)
ActBaudRate 19200(BAUDRATE_19200) Fixed to 0 (0x00)
ActConnectUnitNumber 0(0x00) Fixed to 0 (0x00)
ActControl 8(TRC_DTR_OR_RTS) Fixed to 0 (0x00)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActDataBits
ActDestinationIONumber
8(DATABIT_8)
0(0x00)
Fixed to 0 (0x00)
Fixed to 0 (0x00)
4
ActDestinationPortNumber*1 0(0x00) GOT port number
ActDidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActDsidPropertyBit 1(0x01) Fixed to 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActIntelligentPreferenceBit 0(0x00) Fixed to 0 (0x00)
ActIONumber*2 1023(0x3FF) ■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)
ActMultiDropChannelNumber*3 0(0x00) Fixed to 0 (0x00)
*4
ActNetworkNumber 0(0x00) Target station side module network number
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_TCPIP(0x05)/PROTOCOL_UDPIP(0x08)
ActStopBits 0(STOPBIT_ONE) Fixed to 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK) Fixed to 0 (0x00)
ActSourceNetworkNumber*5 0(0x00) GOT side network number
*6
ActSourceStationNumber 0(0x00) GOT side station number
ActStationNumber*4 255(0xFF) Target station side module station number
ActThroughNetworkType 0(0x00) Fixed to 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitNumber 0(0x00) Fixed to 0 (0x00)
ActUnitType 0x13(UNIT_QNCPU) UNIT_GOTETHER_QN_ETHER(0x6F)

*1 Specify the value set on the GOT side.

*2 For the I/O address, specify the value of the actual start I/O number divided 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
*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 station number of the personal computer-side not to duplicate it with that set for QJ71E71 in the same Ethernet network.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

4.16 GOT Transparent Communication 359
 4.17 Q Series Bus Communication

Configuration

No. 1 No. 2 No. 3 PC CPU module

Property patterns
(n): Accessible ('n' is the property pattern number), : Inaccessible
Own Base
RCPU RCCPU R motion CPU LHCPU
   

Own Base
QCPU (Q mode) QCCPU Q motion CPU
(1)  (1)

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)
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
ActIONumber*1 1023(0x3FF) • No. 1: 992 (0x3E0)
• No. 2: 993 (0x3E1)
• No. 3: 994 (0x3E2)
ActProtocolType 0x04(PROTOCOL_SERIAL) PROTOCOL_QBF(0x10)
ActUnitType 0x13(UNIT_QNCPU) UNIT_QBF(0x1F)

*1 For the I/O address, specify the value of the actual start I/O number divided by 16.

4 PROPERTY SETTINGS OF COMMUNICATION ROUTES

360 4.17 Q Series Bus Communication
5 FUNCTIONS
This chapter explains the considerations of programming and details of functions.
Read the considerations of programming described in Section 5.1 before creating a program.

Types of functions
Functions for .NET control and functions for ACT control are the types of functions.
An applicable interface and programming language are different according to the function.
Control Interface Programming language Reference
ACT control Dispatch interface (Recommended) VBA Page 366 Details of
Visual C++ .NET(MFC) Functions (For ACT
VBScript Control)
Visual Basic .NET
Visual C++ .NET
Visual C# .NET 5
Custom interface Visual C++ .NET(MFC)
.NET control Dispatch interface Visual Basic .NET Page 449 Details of
Visual C++ .NET Functions (For .NET
Visual C# .NET Control)

Interface types
Dispatch interface and custom interface can be used for the functions for ACT control.
Interface Description Characteristic
Dispatch interface Paste controls on the form of Visual Basic .NET, Visual C++ Programming to acquire the interface and to create objects is not
.NET, Visual C# .NET, or VBA (Excel, Access) to use the necessary. (Programs to create objects without pasting controls on the
controls. form can be created.)
Programming with dispatch interface is easier than programming with
custom interface
Custom interface Acquire the interface using the interface acquisition function Programs of custom interface are complicated as compared to those of
when using controls. dispatch interface, however the object creation/extinction can be
Use the object creation function to create objects. managed in detail.

5 FUNCTIONS
361
 5.1 Programming Considerations
This section explains the considerations of programming.

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.

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.
A user needs to create efficient programs in order to improve the speed performance of user applications.
The following figures are flows for creating efficient and inefficient user programs.

<Efficient user application> <Inefficient user application>

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 application?

No
Yes Close the user application?

Close the communication line. (Close)

Yes

Complete Complete

5 FUNCTIONS
362 5.1 Programming Considerations
Considerations for using RnSFCPU
The following functions cannot be used for RnSFCPU.
Function Name Function
Connect Connect telephone line.
Disconnect Disconnect a telephone line

In case of safety mode, the following functions cannot be used for the RnSFCPU safety device.
Function Name Function
WriteDeviceBlock Write devices in bulk.
WriteDeviceRandom Write devices randomly.
SetDevice Set device data.
WriteDeviceBlock2 Write devices in bulk.
WriteDeviceRandom2 Write devices randomly.
SetDevice2 Set device data.
WriteBuffer Write data to buffer memory. 5

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 Function
WriteDeviceBlock Write devices in bulk.
WriteDeviceRandom Write devices randomly.
SetDevice Set device data.
WriteBuffer Write data to buffer memory.
SetClockData Write clock data.
SetCpuStatus Remote control
WriteDeviceBlock2 Write devices in bulk.
WriteDeviceRandom2 Write devices randomly.
SetDevice2 Set device data.

If any of these functions is used, the error code "0x010A42A0" (mismatched CPU access password) will be
returned.

Considerations for using inverter/robot controller

The function of .NET control 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.

5 FUNCTIONS
5.1 Programming Considerations 363
 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 bulk", "write
devices in bulk", "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 application.
Write/read negative device values using the SHORT type/INT type functions described in the section (b).
Page 365 SHORT type/INT type function
Target function Reference
ReadDeviceBlock Page 369 ReadDeviceBlock (Reading devices in bulk)
WriteDeviceBlock Page 372 WriteDeviceBlock (Writing devices in bulk)
ReadDeviceRandom Page 376 ReadDeviceRandom (Reading devices randomly)
WriteDeviceRandom Page 376 ReadDeviceRandom (Reading devices randomly)
SetDevice Page 382 SetDevice (Set device data)
GetDevice Page 384 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.

5 FUNCTIONS
364 5.1 Programming Considerations
■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 364 LONG type function
Target function Reference
ReadDeviceBlock2 Page 418 ReadDeviceBlock2 (Reading devices in bulk)
WriteDeviceBlock2 Page 421 WriteDeviceBlock2 (Writing devices in bulk)
ReadDeviceRandom2 Page 424 ReadDeviceRandom2 (Reading devices randomly)
WriteDeviceRandom2 Page 427 WriteDeviceRandom2 (Writing devices randomly)
SetDevice2 Page 430 SetDevice2 (Set device data)
GetDevice2 Page 433 GetDevice2 (Acquiring device data)

Ex.
When reading a device data with a negative value using the ReadDeviceBlock2 function
5
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.

5 FUNCTIONS
5.1 Programming Considerations 365
 5.2 Details of Functions (For ACT Control)
Open (Opening communication line)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.

Feature
Open the communication line.

Format (Dispatch interface)

■Visual C++ .NET(MFC), VBA
lRet = object.Open()
Long lRet Returned value Output

■VBScript
varRet = object.Open()
VARIANT varRet Returned value (LONG type) Output

■Visual Basic .NET

IRet = object.Open()
Integer IRet Returned value Output

■Visual C++ .NET

iRet = object.Open()
int iRet Returned value Output

■Visual C# .NET
iRet = object.Open()
int iRet Returned value Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.Open( *lplRetCode )
HRESULT hResult Returned value of COM Output
LONG *lplRetCode Returned value of communication function Output

Description
Lines are connected according to the set value of the Open function property.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
366 5.2 Details of Functions (For ACT Control)
• When modem communication is used, the Open function cannot be executed without the execution of the
Connect function.
• 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.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 367
 Close (Closing communication line)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.

Feature
Close the communication line.

Format (Dispatch interface)

■Visual C++ .NET(MFC), VBA
lRet = object.Close()
Long lRet Returned value Output

■VBScript
varRet = object.Close()
VARIANT varRet Returned value (LONG type) Output

■Visual Basic .NET

IRet = object.Close()
Integer IRet Returned value Output

■Visual C++ .NET

iRet = object.Close()
int iRet Returned value Output

■Visual C# .NET
iRet = object.Close()
int iRet Returned value Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.Close( *lplRetCode )
HRESULT hResult Returned value of COM Output
LONG *lplRetCode Returned value of communication function Output

Description
The line connected using the Open function is closed.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
368 5.2 Details of Functions (For ACT Control)
ReadDeviceBlock (Reading devices in bulk)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Read devices in bulk.

Format (Dispatch interface)

■VBA
lRet = object.ReadDeviceBlock(szDevice, lSize, lData(0))
Long lRet Returned value Output
String szDevice Device name Input 5
Long lSize Number of read points Input
Long lData(n) Read device value Output

■Visual C++ .NET(MFC)

lRet = object.ReadDeviceBlock(szDevice, lSize, *lplData)
Long lRet Returned value Output
CString szDevice Device name Input
Long lSize Number of read points Input
Long *lplData Read device value Output

■VBScript
varRet = object.ReadDeviceBlock(varDevice, varSize, lpvarData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDevice Device name (character string type) Input
VARIANT varSize Number of read points (LONG type) Input
VARIANT lpvarData Read device value (LONG array type) Output

■Visual Basic .NET

IRet = object.ReadDeviceBlock(szDevice, iSize, iData(0))
Integer IRet Returned value Output
String szDevice Device name Input
Integer iSize Number of read points Input
Integer iData(n) Read device value Output

■Visual C++ .NET

iRet = object.ReadDeviceBlock(*szDevice, iSize, *iplData)
int iRet Returned value Output
String *szDevice Device name Input
int iSize Number of read points Input
int *iplData Read device value Output

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

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 369
 Format (Custom interface)
■Visual C++ .NET(MFC)
hResult = object.ReadDeviceBlock( szDevice, lSize, *lplData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDevice Device name Input
LONG lSize Number of read points Input
LONG *lplData Read device value Output
LONG *lplRetCode Returned value of communication function Output

Description
• The device values for the amount specified for lSize (varSize or iSize) are read in bulk starting from the device specified for
szDevice (varDevice).
• The read device values are stored in lData (lplData, lpvarData, or iData).
• For lData (lplData, lpvarData, or iData), reserve arrays for more than the amount specified for lSize (varSize or iSize).

How to specify devices

The following describes how to specify devices.

■When bit device is specified

Example: Read 3 points (3 words) of data in 16-point unit starting from M0.
Upper 2 bytes Lower 2 bytes
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 word device is specified

Example: Read 3 points of data starting from D0.
Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) D0
D1
D2

■When double-word device is specified

Example: Read 3 points from LTN0
Upper 2 bytes Lower 2 bytes
H of LTN0 L of LTN0
H of LTN1 L of LTN1
H of LTN2 L of LTN2

■When CN200 and later devices of FXCPU are specified

Example: Read 6 points of data 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.
Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

5 FUNCTIONS
370 5.2 Details of Functions (For ACT Control)
■When FD device is specified (4-word device)
Example: Read 6 points of data starting from FD0.
Upper 2 bytes Lower 2 bytes
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 starting from EG0.
(When 8-bit devices (from E0000 to E0007 of SHARP programmable controller) are assigned from EG0 to EG3.)
Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) EG0
(E0001) (E0000)
5
EG1
(E0003) (E0002)
EG2
(E0005) (E0004)
EG3
(E0007) (E0006)

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of read points that can be specified for lSize (varSize or iSize) should be the value
which satisfies the following condition.
Read start device number + Number of read points ≤ Last device number
• When specifying bit devices, a multiple of 16 can be specified as a device number.
• For lData (lplData, lpvarData, or iData), reserve a memory area for the number of points specified for lSize
(varSize or iSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 371
 WriteDeviceBlock (Writing devices in bulk)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Write devices in bulk.

Format (Dispatch interface)

■VBA
lRet = object.WriteDeviceBlock(szDevice, lSize, lData(0))
Long lRet Returned value Output
String szDevice Device name Input
Long lSize Number of write points Input
Long lData(n) Device value to be written Input

■Visual C++ .NET(MFC)

lRet = object.WriteDeviceBlock(szDevice, lSize, *lplData)
Long lRet Returned value Output
CString szDevice Device name Input
Long lSize Number of write points Input
Long *lplData Device value to be written Input

■VBScript
varRet = object.WriteDeviceBlock(varDevice, varSize, varData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDevice Device name (character string type) Input
VARIANT varSize Number of write points (LONG type) Input
VARIANT varData Device value to be written (LONG array type) Input

■Visual Basic .NET

IRet = object.WriteDeviceBlock(szDevice, iSize, iData(0))
Integer IRet Returned value Output
String szDevice Device name Input
Integer iSize Number of write points Input
Integer iData(n) Device value to be written Input

■Visual C++ .NET

iRet = object.WriteDeviceBlock(*szDevice, iSize, *iplData)
int iRet Returned value Output
String *szDevice Device name Input
int iSize Number of write points Input
int *iplData Device value to be written Input

5 FUNCTIONS
372 5.2 Details of Functions (For ACT Control)
■Visual C# .NET
iRet = object.WriteDeviceBlock(szDevice, iSize, ref iData[0])
int iRet Returned value Output
String szDevice Device name Input
int iSize Number of write points Input
int[n] iData Device value to be written Input

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.WriteDeviceBlock( szDevice, lSize, *lplData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDevice Device name Input
LONG lSize Number of write points Input
LONG *lplData Device value to be written Input
LONG *lplRetCode Returned value of communication function Output

Description 5
• The device values of lSize (varSize or iSize) are written in bulk starting from the device specified for szDevice (varDevice).
• The device values to be written are stored in lData (lplData, varData, or iData).
• For lData (lplData, varData, or iData), reserve arrays for more than the amount specified for lSize (varSize or iSize).

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 373
 How to specify devices
The following describes how to specify devices.

■When bit device is specified

Example: Write 3 points (3 words) of data in 16-point unit starting from M0.
Upper 2 bytes Lower 2 bytes
Not used 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 word device is specified

Example: Write 3 points of data starting from D0.
Upper 2 bytes Lower 2 bytes
Not used D0
D1
D2

■When double-word device is specified

Example: Write 3 points to LTN0
Upper 2 bytes Lower 2 bytes
H of LTN0 L of LTN0
H of LTN1 L of LTN1
H of LTN2 L of LTN2

■When FXCPU devices of CN200 and later are specified

Example: Write 6 points of data 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.
Upper 2 bytes Lower 2 bytes
Not used L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

■When FD device is specified (4-word device)

Example: Write 6 points of data starting from FD0.
Upper 2 bytes Lower 2 bytes
Not used LL of FD0
LH of FD0
HL of FD0
HH of FD0
LL of FD1
LH of FD1

5 FUNCTIONS
374 5.2 Details of Functions (For ACT Control)
■8-bit devices assigned to gateway devices
Example: Write 4 points of data starting from EG0.
(When 8-bit devices (from E0000 to E0007 of SHARP programmable controller) are assigned from EG0 to EG3.)
Upper 2 bytes Lower 2 bytes
Not used EG0
(E0001) (E0000)
EG1
(E0003) (E0002)
EG2
(E0005) (E0004)
EG3
(E0007) (E0006)

Returned value
Normal termination: 0 is returned. 5
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of write points that can be specified for lSize(varSize or iSize) should be the value
which satisfies the following condition.
Write starting device number + Number of write points ≤ Last device number
• When specifying bit devices, a multiple of 16 can be specified as a device number.
• For lData (lplData, varData, or iData), reserve a memory area for the number of points specified for lSize
(varSize or iSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• WriteDeviceBlock or WriteDeviceBlock2 cannot be used for writing long timer device (LT) and retentive long
timer device (LST).
Use WriteDeviceRandom, WriteDeviceRandom2, SetDevice or SetDevice2.
• 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.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 375
 ReadDeviceRandom (Reading devices randomly)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.

Feature
Read devices randomly.
Read monitor types of inverters/robot controllers randomly.

Format (Dispatch interface)

■VBA
lRet = object.ReadDeviceRandom(szDeviceList, lSize, lData(0))
Long lRet Returned value Output
String szDeviceList Device name/monitor type Input
Long lSize Number of read points Input
Long lData(n) Read device value Output

■Visual C++ .NET(MFC)

lRet = object.ReadDeviceRandom(szDeviceList, lSize,*lplData)
Long lRet Returned value Output
CString szDeviceList Device name/monitor type Input
Long lSize Number of read points Input
Long *lplData Read device value Output

■VBScript
varRet = object.ReadDeviceRandom(varDeviceList, varSize,lpvarData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDeviceList Device name/monitor type (character string type) Input
VARIANT varSize Number of read points (LONG type) Input
VARIANT lpvarData Read device value (LONG array type) Output

■Visual Basic .NET

IRet = object.ReadDeviceRandom(szDeviceList, iSize, iData(0))
Integer IRet Returned value Output
String szDeviceList Device name/monitor type Input
Integer iSize Number of read points Input
Integer iData(n) Read device value Output

■Visual C++ .NET

iRet = object.ReadDeviceRandom(*szDeviceList, iSize, *iplData)
int iRet Returned value Output
String *szDeviceList Device name/monitor type Input
int iSize Number of read points Input
int *iplData Read device value Output

■Visual C# .NET
iRet = object.ReadDeviceRandom(szDevice, iSize, out iData[0])
int iRet Returned value Output
String szDevice Device name/monitor type Input
int iSize Number of read points Input
int[n] iData Read device value Output

5 FUNCTIONS
376 5.2 Details of Functions (For ACT Control)
Format (Custom interface)
■Visual C++ .NET(MFC)
hResult = object.ReadDeviceRandom( szDevice, lSize, *lplData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDevice Device name/monitor type Input
LONG lSize Number of read points Input
LONG *lplData Read device value Output
LONG *lplRetCode Returned value of communication function Output

Description
• Data of a device group/monitor type group for the size of lSize (varSize or iSize) specified for szDeviceList (varDeviceList or
szDevice) are read.
• The read device values are stored in lData (lplData, lpvarData, or iData).
• 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. 5
Example:
When using Visual Basic .NET, VBA, VBScript: "D0" & vbLf & "D1" & vbLf & "D2"
When using Visual C++ .NET: D0\nD1\nD2
When using Visual C# .NET: D0\nD1\nD2

• For lData (lplData, lpvarData, or iData), reserve arrays for more than the amount specified for lSize (varSize or iSize).
• For the items (monitor types) that can be monitored, refer to the following manual.
MX Component Version 4 Operating Manual

How to specify devices

The following describes how to specify devices.

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

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

Upper 2 bytes Lower 2 bytes

Not used (0 is stored.) M0
D0
M16 to M31*1 M0 to M15*1

*1 Devices are stored from the lower bit in the order of device number.

■When double word devices are specified

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

Upper 2 bytes Lower 2 bytes

H of LTN0 L of LTN0
H of LTN1 L of LTN1
H of LTN2 L of LTN2

■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, VBScript: "D0" & vbLf & "CN200" & vbLf & "D1"
When using Visual C++ .NET: D0\nCN200\nD1
When using Visual C# .NET: D0\nCN200\nD1

Upper 2 bytes Lower 2 bytes

Not used (0 is stored.) D0
H of CN200 L of CN200
Not used (0 is stored.) D1

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 377
 ■When devices including FD are specified (Total number of points: 3 points)
When using Visual Basic .NET, VBA, VBScript: "D0" & vbLf & "FD0" & vbLf & "D1"
When using Visual C++ .NET: D0\nFD0\nD1
When using Visual C# .NET: D0\nFD0\nD1

Upper 2 bytes Lower 2 bytes

Not used (0 is stored.) D0
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, VBScript: "D0" & vbLf & "EG0" & vbLf & "D1"
When using Visual C++ .NET: D0\nEG0\nD1
When using Visual C# .NET: D0\nEG0\nD1

Upper 2 bytes Lower 2 bytes

Not used (0 is stored.) D0
EG0
(E0001)
D1

■When monitor types (1, 2, and 5) of inverter are specified (Total number of points: 3 points)
When using Visual Basic .NET, VBA, VBScript: "1" & vbLf &"2" & vbLf &"5"
When using Visual C++ .NET: 1\n2\n5
When using Visual C# .NET: 1\n2\n5

Upper 2 bytes Lower 2 bytes

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, VBScript: "223.102.A" & vbLf &"223.103.B"
When using Visual C++ .NET: 223.102.A\n223.103.B
When using Visual C# .NET: 223.102.A\n223.103.B

Upper 2 bytes Lower 2 bytes

H of 223.102.A L of 223.102.A
H of 223.103.B L of 223.103.B

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of read points that can be specified for lSize (varSize or iSize) is 0x7FFFFFFF
points.
• For lData (lplData, lpvarData, or iData), reserve a memory area for the number of points specified for lSize
(varSize or iSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.

5 FUNCTIONS
378 5.2 Details of Functions (For ACT Control)
WriteDeviceRandom (Writing devices randomly)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Write devices randomly.

Format (Dispatch interface)

■VBA
lRet = object.WriteDeviceRandom(szDeviceList, lSize,lData(0))
Long lRet Returned value Output
String szDeviceList Device name Input 5
Long lSize Number of write points Input
Long lData(n) Device value to be written Input

■Visual C++.NET(MFC)
lRet = object.WriteDeviceRandom(szDeviceList, lSize,*lplData)
Long lRet Returned value Output
CString szDeviceList Device name Input
Long lSize Number of write points Input
Long *lplData Device value to be written Input

■VBScript
varRet = object.WriteDeviceRandom(varDeviceList, varSize,varData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDeviceList Device name (character string type) Input
VARIANT varSize Number of write points (LONG type) Input
VARIANT varData Device value to be written (LONG array type) Input

■Visual Basic .NET

IRet = object.WriteDeviceRandom(szDeviceList, iSize, iData(0))
Integer IRet Returned value Output
String szDeviceList Device name Input
Integer iSize Number of write points Input
Integer iData(n) Device value to be written Input

■Visual C++ .NET

iRet = object.WriteDeviceRandom(*szDeviceList, iSize, *iplData)
int iRet Returned value Output
String *szDeviceList Device name Input
int iSize Number of write points Input
int *iplData Device value to be written Input

■Visual C# .NET
iRet = object.WriteDeviceRandom(szDevice, iSize, ref iData[0])
int iRet Returned value Output
String szDevice Device name Input
int iSize Number of write points Input
int[n] iData Device value to be written Input

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 379
 Format (Custom interface)
■Visual C++.NET(MFC)
hResult = object.WriteDeviceRandom( szDeviceList, lSize, *lplData,*lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDeviceList Device name Input
LONG lSize Number of write points Input
LONG *lplData Device value to be written Input
LONG *lplRetCode Returned value of communication function Output

Description
• Data of a device group for the size of lSize (varSize or iSize) specified for szDeviceList (varDeviceList or szDevice) are
written.
• The device values to be written are stored in lData (lplData, varData, or iData).
• 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, VBScript: "D0" & vbLf & "D1" & vbLf & "D2"
When using Visual C++ .NET: D0\nD1\nD2
When using Visual C# .NET: D0\nD1\nD2

• For lData (lplData, varData, or iData), reserve arrays for more than the amount specified for lSize (varSize or iSize).

How to specify devices

The following describes how to specify devices.

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

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

Upper 2 bytes Lower 2 bytes

Not used M0
D0
M16 to M31*1 M0 to M15*1

*1 Devices are stored from the lower bit in the order of device number.

■When double word devices are specified

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

Upper 2 bytes Lower 2 bytes

H of LTN0 L of LTN0
H of LTN1 L of LTN1
H of LTN2 L of LTN2

■When devices including CN200 and later of FXCPU are specified (Total number of points: 3
points)
For CN200 or later of FXCPU, 2 words are written for each point when writing devices randomly.
When using Visual Basic .NET, VBA, VBScript: "D0" & vbLf & "CN200" & vbLf & "D1"
When using Visual C++ .NET: D0\nCN200\nD1
When using Visual C# .NET: D0\nCN200\nD1

Upper 2 bytes Lower 2 bytes

Not used D0
H of CN200 L of CN200
Not used D1

5 FUNCTIONS
380 5.2 Details of Functions (For ACT Control)
■When devices including FD are specified (Total number of points: 3 points)
Upper 2 bytes Lower 2 bytes
Not used D0
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, VBScript: "D0" & vbLf & "EG0" & vbLf & "D1"
When using Visual C++ .NET: D0\nEG0\nD1
When using Visual C# .NET: D0\nEG0\nD1

Upper 2 bytes Lower 2 bytes

Not used D0
EG0
(E0001)
D1
(E0000)
5

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of write points that can be specified for lSize (varSize or iSize) is 0x7FFFFFFF
points.
• For lData (lplData, varData, or iData), reserve a memory area for the number of points specified for lSize
(varSize or iSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• If a Q motion CPU is accessed, an error is returned.
• 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.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 381
 SetDevice (Set device data)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Set one point of device.

Format (Dispatch interface)

■VBA
lRet = object.SetDevice(szDevice, lData)
Long lRet Returned value Output
String szDevice Device name Input
Long lData Set data Input

■Visual C++ .NET(MFC)

lRet = object.SetDevice(szDevice, lData)
Long lRet Returned value Output
CString szDevice Device name Input
Long lData Set data Input

■VBScript
varRet = object.SetDevice(varDevice, lpvarData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDevice Device name (character string type) Input
VARIANT varData Set data (LONG type) Input

■Visual Basic .NET

IRet = object.SetDevice(szDevice, iData)
Integer IRet Returned value Output
String szDevice Device name Input
Integer iData Set data Input

■Visual C++ .NET

iRet = object.SetDevice(*szDevice, iData)
int iRet Returned value Output
String *szDevice Device name Input
int iData Set data Input

■Visual C# .NET
iRet = object.SetDevice(szDevice, iData)
int iRet Returned value Output
String szDevice Device name Input
int iData Set data Input

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.SetDevice( szDevice, lData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDevice Device name Input
LONG lData Set data Input
LONG *lplRetCode Returned value of communication function Output

5 FUNCTIONS
382 5.2 Details of Functions (For ACT Control)
Description
• One point of device specified for szDevice (varDevice) is specified using lData (varData or iData).
• When specifying bit devices, the least significant bit of the lData value (varData value or iData value) is valid.

How to specify devices

The following describes how to specify devices.

■When bit device is specified

Example: M0
Upper 2 bytes Lower 2 bytes
Not used M0

■When word device is specified

Example: D0
Upper 2 bytes Lower 2 bytes 5
Not used D0

■When double-word device is specified

Example: LTN0
Upper 2 bytes Lower 2 bytes
H of LTN0 L of LTN0

■When double word device is specified (Digit specification)

Example: K8M0
Upper 2 bytes Lower 2 bytes
M16 to M31*1 M0 to M15*1

*1 Devices are stored from the lower bit in the order of device number.

■When CN200 or later device of FXCPU is specified

Example: CN200
Upper 2 bytes Lower 2 bytes
H of CN200 L of CN200

■When gateway device is specified

Example: When 8-bit devices (E0000 and E0001 of SHARP programmable controller) are assigned to EG0
Upper 2 bytes Lower 2 bytes
Not used EG0
(E0001) (E0000)

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

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.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 383
 GetDevice (Acquiring device data)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.

Feature
Acquire one point of device.
Acquire one point monitor type data of inverter/robot controller.

Format (Dispatch interface)

■VBA
lRet = object.GetDevice(szDevice, lData)
Long lRet Returned value Output
String szDevice Device name/monitor type Input
Long lData Acquired data Output

■Visual C++ .NET(MFC)

lRet = object.GetDevice(szDevice, *lplData)
Long lRet Returned value Output
CString szDevice Device name/monitor type Input
Long *lplData Acquired data Output

■VBScript
varRet = object.GetDevice(varDevice, lpvarData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDevice Device name/monitor type (character string type) Input
VARIANT lpvarData Acquired data (LONG type) Output

■Visual Basic .NET

IRet = object.GetDevice(szDevice, iData)
Integer IRet Returned value Output
String szDevice Device name/monitor type Input
Integer iData Acquired data Output

■Visual C++ .NET

iRet = object.GetDevice(*szDevice, *iplData)
int iRet Returned value Output
String *szDevice Device name/monitor type Input
int *iplData Acquired data Output

■Visual C# .NET
iRet = object.GetDevice(szDevice, out iData)
int iRet Returned value Output
String szDevice Device name/monitor type Input
int iData Acquired data Output

5 FUNCTIONS
384 5.2 Details of Functions (For ACT Control)
Format (Custom interface)
■Visual C++ .NET(MFC)
hResult = object.GetDevice( szDevice, *lplData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDevice Device name/monitor type Input
LONG *lplData Acquired data Output
LONG *lplRetCode Returned value of communication function Output

Description
One point of device data specified for szDevice (varDevice) is stored in lData (lplData, lpvarData, or iData).
For the items (monitor types) that can be monitored, refer to the following manual.
MX Component Version 4 Operating Manual

How to specify devices

The following describes how to specify devices/monitor type. 5
■When bit device is specified
Example: M0
Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) M0

■When word device is specified

Example: D0
Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) D0

■When double-word device is specified

Example: LTN0
Upper 2 bytes Lower 2 bytes
H of LTN0 L of LTN0

■When double-word device is specified (Digit specification)

Example: K8M0
Upper 2 bytes Lower 2 bytes
*1
M16 to M31 M0 to M15*1

*1 Devices are stored from the lower bit in the order of device number.

■When CN200 and later devices of FXCPU are specified

Example: CN200
Upper 2 bytes Lower 2 bytes
H of CN200 L of CN200

■When gateway device is specified

Example: When 8-bit devices (E0000 and E0001 of SHARP programmable controller) are assigned to EG0
Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) EG0
(E0001) (E0000)

■When monitor type of inverter is specified

Example: 2
Upper 2 bytes Lower 2 bytes
H of 1 L of 1

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 385
 ■When monitor type of robot controller is specified
Format: (Request ID).(Data type).(Argument)
Example: 223.102.A
Upper 2 bytes Lower 2 bytes
H of 223.102.A L of 223.102.A

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
386 5.2 Details of Functions (For ACT Control)
ReadBuffer (Reading data from buffer memory)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Applicable communication routes

The following table shows the applicable communication routes.
: Applicable, : Not applicable
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  5
C24
Connected module: L series-compatible UNIT_LJ71C24 
C24
Connected module: FX extended port UNIT_FX485BD 
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
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

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 387
 Communication route Property setting Applic
ActUnitType ActProtocolType ability

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 G4 communication UNIT_G4QCPU PROTOCOL_SERIAL 
GX Simulator communication UNIT_SIMULATOR PROTOCOL_SHAREDMEMORY *3
GX Simulator2 communication UNIT_SIMULATOR2  
GX Simulator3 communication (RCPU) UNIT_SIMULATOR3 
GX Simulator3 communication (FX5CPU)
MT Simulator2 communication UNIT_SIMULATOR2  
Modem Connected module: Q series-compatible UNIT_QJ71C24 PROTOCOL_SERIALMODEM 
communication C24
Connected module: L series-compatible UNIT_LJ71C24 PROTOCOL_SERIALMODEM
C24
Connection target CPU: FXCPU UNIT_FXCPU PROTOCOL_TEL *1
Gateway function communication UNIT_A900GOT PROTOCOL_UDPIP 
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 
Q series bus communication UNIT_QBF PROTOCOL_QBF 
Inverter communication - COMM_RS232C, COMM_USB 

*1 When the CPU is other than FX1N, FX1NC, FX2N, FX2NC, FX3U, FX3UC, FX3G and FX3GC an error is returned.
*2 An error is returned when the own board is accessed.
*3 When the CPU is other than FX0N, FX1N, FX1NC, FXU, FX2C, FX2N, FX2NC, FX3U, FX3UC, FX3G and FX3GC, an error is returned.

5 FUNCTIONS
388 5.2 Details of Functions (For ACT Control)
Feature
Read data from the buffer memory of special function module.

Format (Dispatch interface)

■VBA
lRet = object.ReadBuffer(lStartIO,lAddress,lReadSize, iData(0))
Long lRet Returned value Output
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++ .NET(MFC)

lRet = object.ReadBuffer(lStartIO, lAddress, lReadSize, *lpsData)
Long
Long
lRet
lStartIO
Returned value
Start I/O number of module from which values are
Output
Input
5
read
Long lAddress Buffer memory address Input
Long lReadSize Read size Input
Short *lpsData Values read from buffer memory Output

■VBScript
varRet = object.ReadBuffer(varStartIO, varAddress, varReadSize,lpvarData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varStartIO Start I/O number of module from which values are Input
read (LONG type)
VARIANT varAddress Buffer memory address (LONG type) Input
VARIANT varReadSize Read size (LONG type) Input
VARIANT lpvarData Values read from buffer memory (SHORT array Output
type)

■Visual Basic .NET

IRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, iData(0))
Integer IRet Returned value Output
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++ .NET

object.ReadBuffer(iStartIO, iAddress, iReadSize, *ipsData)
int iRet Returned value Output
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 *ipsData Values read from buffer memory Output

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 389
 ■Visual C# .NET
iRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, out sData[0])
int iRet Returned value Output
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

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.ReadBuffer( lStartIO, lAddress, lReadSize, *lpsData, *lplRetCode )
HRESULT hResult Returned value of COM Output
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
LONG *lplRetCode Returned value of communication function Output

Description
• For the start I/O number of the module specified for lStartIO (varStartIO or iStartIO), specify the value of the actual start I/O
number divided by 16.
For FX5CPU, specify the module number on the target station side.
• Buffer values of buffer memory address specified for lAddress (varAddress or iAddress) of the special function module of
the start I/O number specified for lStartIO (varStartIO or iStartIO) are read for the size of lReadSize (varReadSize or
iReadSize).
• When performing CPU COM communication with FXCPU as a connected station or GX Simulator communication, specify
the block number (0 to 7) of the special expansion equipment for the module's start I/O number and any value between 0
and 32767 for the buffer memory address.
• For iData (lpsData, lpvarData, or sData), reserve arrays for more than the amount specified for lReadSize (varReadSize or
iReadSize).

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
390 5.2 Details of Functions (For ACT Control)
Considerations for reading/writing data from/to buffer memory in multiple CPU system
Any of the following errors occurs when the function is executed under the situation where the configured multiple CPU
system differs from the I/O assignment set in GX Developer.
Execute the function after checking the I/O assignment set in GX Developer and checking the I/O numbers of the module
from/to which values are read/written.
• An error occurs even when the function is executed after the correct I/O numbers are specified.
• When the specific I/O numbers (I/O numbers whose I/O assignment is actually wrong) are specified, data can be read from
buffer memory normally, but an error (error code: 0x010A4030, 0x010A4042, etc.) occurs when data are written to the
buffer memory.
• Though a programmable controller CPU error (parameter error, SP. UNIT LAY ERR, etc.) does not occur in the multiple
CPU system, an error occurs in the user application when the function is executed.

• If an R motion CPU, or Q motion CPU is accessed, an error will be returned.

• For iData (lpsData, lpvarData, or sData), reserve a memory area for the number of points specified for 5
lReadSize (varReadSize or iReadSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• 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).

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 391
 WriteBuffer (Writing data to buffer memory)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Applicable communication routes

The following table shows the applicable communication routes.
: Applicable, : Not applicable
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 
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
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

5 FUNCTIONS
392 5.2 Details of Functions (For ACT Control)
Communication route Property setting Applic
ActUnitType ActProtocolType ability

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 *2
Connection target CPU: Q motion CPU UNIT_QNMOTIONUSB 
Connection target CPU: FXCPU UNIT_FXCPU 
MELSECNET/H communication UNIT_MNETHBOARD PROTOCOL_MNETH *3
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 G4 communication UNIT_G4QCPU PROTOCOL_SERIAL 
GX Simulator communication UNIT_SIMULATOR PROTOCOL_SHAREDMEMORY *4 5
GX Simulator2 communication UNIT_SIMULATOR2 - 
GX Simulator3 communication (RCPU) UNIT_SIMULATOR3 
GX Simulator3 communication (FX5CPU)
MT Simulator2 communication UNIT_SIMULATOR2 - 
Modem Connected module: Q series-compatible UNIT_QJ71C24 PROTOCOL_SERIALMODEM 
communication C24
Connected module: L series-compatible UNIT_LJ71C24 PROTOCOL_SERIALMODEM
C24
Connection target CPU: FXCPU UNIT_FXCPU PROTOCOL_TEL *1
Gateway function communication UNIT_A900GOT PROTOCOL_UDPIP 
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 
Q series bus communication UNIT_QBF PROTOCOL_QBF 
Inverter communication - COMM_RS232C, COMM_USB 

*1 When the CPU is other than FX1N, FX1NC, FX2N, FX2NC, FX3U, FX3UC, FX3G and FX3GC an error is returned.
*2 The error code "0x010A42A0" (the access password mismatch) is returned when accessing QSCPU.
*3 An error is returned when the own board is accessed.
*4 When the CPU is other than FX0N, FX1N, FX1NC, FXU, FX2C, FX2N, FX2NC, FX3U, FX3UC, FX3G and FX3GC, an error is returned.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 393
 Feature
Write data to the buffer memory of special function module.

Format (Dispatch interface)

■VBA
lRet = object.WriteBuffer(lStartIO, lAddress, lWriteSize, iData(0))
Long lRet Returned value Output
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
Integer iData(n) Values written from buffer memory Input

■Visual C++ .NET(MFC)

lRet = object.WriteBuffer(lStartIO, lAddress, lWriteSize, *lpsData)
Long lRet Returned value Output
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

■VBScript
varRet = object.WriteBuffer(varStartIO, varAddress, varWriteSize,varData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varStartIO Start I/O number of module to which values are Input
written (LONG type)
VARIANT varAddress Buffer memory address (LONG type) Input
VARIANT varWriteSize Write size (LONG type) Input
VARIANT varData Values written from buffer memory (SHORT array Input
type)

■Visual Basic .NET

IRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, iData(0))
Integer IRet Returned value Output
Integer iStartIO Start I/O number of module to which values are Input
written
Integer iAddress Buffer memory address Input
Integer iWriteSize Write size Input
short iData(n) Values written from buffer memory Input

■Visual C++ .NET

iRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, *ipsData)
int iRet Returned value Output
int iStartIO Start I/O number of module to which values are Input
written
int iAddress Buffer memory address Input
int iWriteSize Write size Input
short *ipsData Values written from buffer memory Input

■Visual C# .NET
iRet = object. WriteBuffer (iStartIO, iAddress, iWriteSize, ref sData[0])
int iRet Returned value Output
int iStartIO Start I/O number of module to which values are Input
written
int iAddress Buffer memory address Input
int iWriteSize Write size Input
short[n] sData Values written from buffer memory Input

5 FUNCTIONS
394 5.2 Details of Functions (For ACT Control)
Format (Custom interface)
■Visual C++ .NET(MFC)
hResult = object.WriteBuffer( lStartIO, lAddress, lWriteSize, *lpsData, *lplRetCode )
HRESULT hResult Returned value of COM Output
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
LONG *lplRetCode Returned value of communication function Output

Description
• For the start I/O number of the module specified for lStartIO (varStartIO or iStartIO), specify the value of the actual start I/O
number divided by 16.
For FX5CPU, specify the module number on the target station side.
• Buffer values of buffer memory address specified for lAddress (varAddress or iAddress) of the special function module of
5
the start I/O number specified for lStartIO (varStartIO or iStartIO) are written for the size of lWriteSize (varWriteSize or
iWriteSize).
• When performing CPU COM communication with FXCPU as a connected station or GX Simulator communication, specify
the block number (0 to 7) of the special expansion equipment for the module's start I/O number and any value between 0
and 32767 for the buffer memory address.
• For iData (lpsData, varData, or sData), reserve arrays for more than the amount specified for lWriteSize (varWriteSize or
iWriteSize).

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

Considerations for reading/writing data from/to buffer memory in multiple CPU system
Any of the following errors occurs when the function is executed under the situation where the configured multiple CPU
system differs from the I/O assignment set in GX Developer.
Execute the function after checking the I/O assignment set in GX Developer and checking the I/O numbers of the module
from/to which the values are read/written.
• An error occurs even when the function is executed after the correct I/O numbers are specified.
• When the specific I/O numbers (I/O numbers whose I/O assignment is actually wrong) are specified, data can be read from
buffer memory normally, but an error (error code: 0x010A4030, 0x010A4042, etc.) occurs when data are written to the
buffer memory.
• Though a programmable controller CPU error (parameter error, SP. UNIT LAY ERR, etc.) does not occur in the multiple
CPU system, an error occurs in the user application when the function is executed.

• If an R motion CPU, or Q motion CPU is accessed, an error will be returned.

• For iData (lpsData, varData, or sData), reserve a memory area for the number of points specified for
lWriteSize (varWriteSize or iWriteSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• 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).

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 395
 GetClockData (Reading clock data)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Applicable communication routes

The following table shows the applicable communication routes.
: Applicable, : Not applicable
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 
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
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 

5 FUNCTIONS
396 5.2 Details of Functions (For ACT Control)
Communication route Property setting Applic
ActUnitType ActProtocolType ability

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 *1
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 G4 communication UNIT_G4QCPU PROTOCOL_SERIAL 
GX Simulator communication UNIT_SIMULATOR PROTOCOL_SHAREDMEMORY  5
GX Simulator2 communication UNIT_SIMULATOR2 - 
GX Simulator3 communication (RCPU) UNIT_SIMULATOR3
GX Simulator3 communication (FX5CPU)
MT Simulator2 communication UNIT_SIMULATOR2 - 
Modem Connected module: Q series-compatible UNIT_QJ71C24 PROTOCOL_SERIALMODEM 
communication C24
Connected module: L series-compatible UNIT_LJ71C24 PROTOCOL_SERIALMODEM
C24
Connection target CPU: FXCPU UNIT_FXCPU PROTOCOL_TEL
Gateway function communication UNIT_A900GOT PROTOCOL_UDPIP 
GOT transparent function communication UNIT_RJ71C24, UNIT_FXVCPU, PROTOCOL_SERIAL, 
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_FXVCPU,
UNIT_GOTETHER_QNCPU,
UNIT_GOTETHER_LNCPU,
UNIT_GOTETHER_FXCPU,
UNIT_GOTETHER_QBUS,
UNIT_GOTETHER_QN_ETHER
Q series bus communication UNIT_QBF PROTOCOL_QBF 
Inverter communication - COMM_RS232C, COMM_USB 

*1 An error is returned when the own board is accessed.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 397
 Feature
Read clock data from a programmable controller CPU.

Format (Dispatch interface)

■VBA
lRet = object.GetClockData(iYear, iMonth, iDay, iDayOfWeek, iHour, iMinute, iSecond)
Long lRet Returned value Output
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++ .NET(MFC)

lRet = object.GetClockData(*lpsYear, *lpsMonth, *lpsDay, *lpsDayOfWeek, *lpsHour, *lpsMinute, *lpsSecond)
Long lRet Returned value Output
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

■VBScript
varRet = object.GetClockData(lpvarYear, lpvarMonth, lpvarDay, lpvarDayOfWeek, lpvarHour, lpvarMinute, lpvarSecond)
VARIANT varRet Returned value (LONG type) Output
VARIANT lpvarYear Read year value (SHORT type) Output
VARIANT lpvarMonth Read month value (SHORT type) Output
VARIANT lpvarDay Read day value (SHORT type) Output
VARIANT lpvarDayOfWeek Read day-of-week value (SHORT type) Output
VARIANT lpvarHour Read hour value (SHORT type) Output
VARIANT lpvarMinute Read minute value (SHORT type) Output
VARIANT lpvarSecond Read second value (SHORT type) Output

■Visual Basic .NET

IRet = object.GetClockData(iYear, iMonth, iDay, iDayOfWeek,iHour, iMinute,iSecond)
Integer IRet Returned value Output
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++ .NET

iRet = object.GetClockData(*lpsYear, *lpsMonth, *lpsDay, *lpsDayOfWeek, *lpsHour, *lpsMinute, *lpsSecond)
int iRet Returned value Output
short *lpsYear Read year value Output
short *lps Month Read month value Output
short *lps Day Read day value Output
short *lps DayOfWeek Read day-of-week value Output
short *lps Hour Read hour value Output
short *lps Minute Read minute value Output
short *lps Second Read second value Output

■Visual C# .NET
hResult = object.GetClockData(out sYear, out sMonth, out sDay, out sDayOfWeek,out sHour, out sMinute, out sSecond)
int iRet Returned value Output

5 FUNCTIONS
398 5.2 Details of Functions (For ACT Control)
 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

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.GetClockData( *lpsYear, *lpsMonth, *lpsDay, *lpsDayOfWeek, *lpsHour, *lpsMinute, *lpsSecond, *lplRetCode
)
HRESULT hResult Returned value of COM Output
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 5
SHORT *lpsMinute Read minute value Output
SHORT *lpsSecond Read second value Output
LONG *lplRetCode Returned value of communication function Output

Description
• An error is returned when the correct clock data is not set to the programmable controller CPU.
• The values stored in iYear (lpsYear, lpvarYear, or sYear) are: four digits of the year for RCPU and QCPU (Q mode) and last
two digits of the year for any other CPUs. Note that the applicable years for RCPU and QCPU (Q mode) are from 1980 to
2079.
• The values stored in iDayOfWeek (lpsDayOfWeek, lpvarDayOfWeek, or sDayOfWeek) are as follows.
Value Day of Week
0 Sunday
1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5 Friday
6 Saturday

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• If an R motion CPU, or Q motion CPU is accessed, an error will be returned.

• The clock data can be read from FXCPUs with the built-in clock or FXU/FX2C/FX2NC with the RTC
cassette.
An error is returned when the clock data is read from an FXCPU other than the ones described above.
• Note that an error of transfer time may occur in clock setting.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 399
 SetClockData (Writing clock data)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Applicable communication routes

The following table shows the applicable communication routes.
: Applicable, : Not applicable
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 
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
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 

5 FUNCTIONS
400 5.2 Details of Functions (For ACT Control)
Communication route Property setting Applic
ActUnitType ActProtocolType ability

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 *1
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 G4 communication UNIT_G4QCPU PROTOCOL_SERIAL 
GX Simulator communication UNIT_SIMULATOR PROTOCOL_SHAREDMEMORY  5
GX Simulator2 communication UNIT_SIMULATOR2 - 
GX Simulator3 communication (RCPU) UNIT_SIMULATOR3
GX Simulator3 communication (FX5CPU)
MT Simulator2 communication UNIT_SIMULATOR2 - 
Modem Connected module: Q series-compatible UNIT_QJ71C24 PROTOCOL_SERIALMODEM 
communication C24
Connected module: L series-compatible UNIT_LJ71C24 PROTOCOL_SERIALMODEM
C24
Connection target CPU: FXCPU UNIT_FXCPU PROTOCOL_TEL
Gateway function communication UNIT_A900GOT PROTOCOL_UDPIP 
GOT transparent function communication UNIT_RJ71C24, UNIT_FXVCPU, PROTOCOL_SERIAL, 
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_FXVCPU,
UNIT_GOTETHER_QNCPU,
UNIT_GOTETHER_LNCPU,
UNIT_GOTETHER_FXCPU,
UNIT_GOTETHER_QBUS,
UNIT_GOTETHER_QN_ETHER
Q series bus communication UNIT_QBF PROTOCOL_QBF 
Inverter communication - COMM_RS232C, COMM_USB 

*1 The error code "0x010A42A0" (the access password mismatch) is returned when accessing QSCPU.
*2 An error is returned when the own board is accessed.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 401
 Feature
Write clock data to a programmable controller CPU.

Format (Dispatch interface)

■VBA
object.SetClockData(iYear, iMonth, iDay, iDayOfWeek, iHour, iMinute, iSecond)
Long lRet Returned value Output
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++ .NET(MFC)

lRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
Long lRet Returned value Output
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

■VBScript
varRet = object.SetClockData(varYear, varMonth, varDay, varDayOfWeek, varHour, varMinute, varSecond)
VARIANT varRet Returned value (LONG type) Output
VARIANT varYear Year value to be written (SHORT type) Input
VARIANT varMonth Month value to be written (SHORT type) Input
VARIANT varDay Day value to be written (SHORT type) Input
VARIANT varDayOfWeek Day-of-week value to be written (SHORT type) Input
VARIANT varHour Hour value to be written (SHORT type) Input
VARIANT varMinute Minute value to be written (SHORT type) Input
VARIANT varSecond Second value to be written (SHORT type) Input

■Visual Basic .NET

IRet = object.SetClockData(iYear, iMonth, iDay, iDayOfWeek, iHour, iMinute,iSecond)
Integer IRet Returned value Output
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++ .NET

iRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
int iRet Returned value Output
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

5 FUNCTIONS
402 5.2 Details of Functions (For ACT Control)
■Visual C# .NET
lRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
int iRet Returned value Output
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

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond, *lplRetCode )
HRESULT hResult Returned value of COM Output
SHORT sYear Year value to be written Input
SHORT sMonth Month value to be written Input 5
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
LONG *lplRetCode Returned value of communication function Output

Description
• An error is returned when the clock data to be set are not correct values.
• The applicable values to be specified for iYear (sYear or varYear) are: four digits of the year for RCPU and QCPU (Q mode)
and last two digits of the year for any other CPUs.
Note that the applicable years for RCPU and QCPU (Q mode) are from 1980 to 2079. An error occurs when four digits are
set to a CPU other than RCPU and QCPU (Q mode).
• The values to be specified for iDayOfWeek (sDayOfWeek or varDayOfWeek) are as follows.
Value Day of Week
0 Sunday
1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5 Friday
6 Saturday

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• If an R motion CPU, or Q motion CPU is accessed, an error will be returned.

• The clock data can be written to FXCPUs with the built-in clock or FXU/FX2C/FX2NC with the RTC
cassette.
An error is returned when the clock data is written to an FXCPU other than the ones described above.
• Note that an error of transfer time may occur in clock setting.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 403
 GetCpuType (Reading programmable controller CPU model)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.

Feature
Read the model character string and the model code of programmable controller CPU, network board, and GOT.

Format (Dispatch interface)

■VBA
lRet = object.GetCpuType(szCpuName, lCpuType)
Long lRet Returned value Output
String szCpuName Programmable controller CPU model character string Output
Long lCpuType Programmable controller CPU model code Output

■Visual C++ .NET(MFC)

lRet = object.GetCpuType(*szCpuName, *lplCpuType)
Long lRet Returned value Output
BSTR *szCpuName Programmable controller CPU model character string Output
Long *lplCpuType Programmable controller CPU model code Output

■VBScript
varRet = object.GetCpuType(varCpuName, lpvarCpuCode)
VARIANT varRet Returned value (LONG type) Output
VARIANT lpvarCpuName Programmable controller CPU model character string Output
(character string type)
VARIANT lpvarCpuCode Programmable controller CPU model code (LONG type) Output

■Visual Basic .NET

IRet = object.GetCpuType(szCpuName, ICpuType)
Integer IRet Returned value Output
String szCpuName Programmable controller CPU model character string Output
Integer ICpuType Programmable controller CPU model code Output

■Visual C++ .NET

iRet = object.GetCpuType (**szCpuName, *iplCpuType)
int iRet Returned value Output
String **szCpuName Programmable controller CPU model character string Output
int *iplCpuType Programmable controller CPU model code Output

■Visual C# .NET
iRet = object.GetCpuType (out szCpuName, out iCpuType)
int iRet Returned value Output
String szCpuName Programmable controller CPU model character string Output
int iCpuType Programmable controller CPU model code Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.GetCpuType( *szCpuName, *lplCpuType, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR *szCpuName Programmable controller CPU model character string Output
LONG *lplCpuType Programmable controller CPU model code Output
LONG *lplRetCode Returned value of communication function Output

Description
• The model and the model code of the communication target programmable controller CPU are stored in szCpuName
(lpvarCpuName) and lCpuType (lplCpuType, lpvarCpuCode, or iCpuType) respectively.
• The model character string of the programmable controller CPU is returned in UNICODE.

5 FUNCTIONS
404 5.2 Details of Functions (For ACT Control)
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 CPU/own board is connected When GX Simulator is connected
Network board/GOT 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_R08CPU R08CPU 4801H
CPU_R08ENCPU R08ENCPU 4806H
CPU_R08PCPU R08PCPU 4841H
CPU_R08PSFCPU
CPU_R08SFCPU
R08PSFCPU
R08SFCPU
4851H
4891H
5
CPU_R16CPU R16CPU 4802H
CPU_R16ENCPU R16ENCPU 4807H
CPU_R16PCPU R16PCPU 4842H
CPU_R16PSFCPU R16PSFCPU 4852H
CPU_R16SFCPU R16SFCPU 4892H
CPU_R32CPU R32CPU 4803H
CPU_R32ENCPU R32ENCPU 4808H
CPU_R32PCPU R32PCPU 4843H
CPU_R32PSFCPU R32PSFCPU 4853H
CPU_R32SFCPU R32SFCPU 4893H
CPU_R120CPU R120CPU 4804H
CPU_R120ENCPU R120ENCPU 4809H
CPU_R120PCPU R120PCPU 4844H
CPU_R120PSFCPU R120PSFCPU 4854H
CPU_R120SFCPU R120SFCPU 4894H
CPU_R16MTCPU R16MTCPU 4C00H
CPU_R32MTCPU R32MTCPU 4C01H
CPU_R12CCPU-V R12CCPU-V 4820H
CPU_L04HCPU L04HCPU 48C0H
CPU_L08HCPU L08HCPU 48C1H
CPU_L16HCPU L16HCPU 48C2H
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_Q01UCPU Q01UCPU 262H Q01UCPU 262H
CPU_Q02CPU Q02CPU 41H Q02CPU 41H
CPU_Q02HCPU Q02HCPU Q02HCPU
CPU_Q02PHCPU Q02PHCPU Q02PHCPU
CPU_Q02UCPU Q02UCPU 263H Q02UCPU 263H
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_Q04UDVCPU Q04UDVCPU 367H -

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 405
 CPU type When CPU/own board is connected When GX Simulator is connected
Network board/GOT Model character string Model code Model character string Model code
CPU_Q06HCPU Q06HCPU 42H Q06HCPU 42H
CPU_Q06PHCPU Q06PHCPU Q06PHCPU
CPU_Q06UDHCPU Q06UDHCPU 26AH Q06UDHCPU 26AH
CPU_Q06UDEHCPU Q06UDEHCPU Q06UDEHCPU
CPU_Q06UDVCPU Q06UDVCPU 368H -
CPU_Q10UDHCPU Q10UDHCPU 266H Q10UDHCPU 266H
CPU_Q10UDEHCPU Q10UDEHCPU Q10UDEHCPU
CPU_Q12HCPU Q12HCPU 43H Q12HCPU 43H
CPU_Q12PHCPU
CPU_Q12PRHCPU Q12PRHCPU 4BH Q12PRHCPU 4BH
CPU_Q13UDHCPU Q13UDHCPU 26BH Q13UDHCPU 26BH
CPU_Q13UDEHCPU Q13UDEHCPU Q13UDEHCPU
CPU_Q13UDVCPU Q13UDVCPU 36AH -
CPU_Q20UDHCPU Q20UDHCPU 267H Q20UDHCPU 267H
CPU_Q20UDEHCPU Q20UDEHCPU Q20UDEHCPU
CPU_Q25HCPU Q25HCPU 44H Q25HCPU 44H
CPU_Q25PHCPU
CPU_Q25PRHCPU Q25PRHCPU 4CH Q25PRHCPU 4CH
CPU_Q26UDHCPU Q26UDHCPU 26CH Q26UDHCPU 26CH
CPU_Q26UDEHCPU Q26UDEHCPU Q26UDEHCPU
CPU_Q26UDVCPU Q26UDVCPU 36CH -
CPU_Q50UDEHCPU Q50UDEHCPU 26DH
CPU_Q100UDEHCPU Q100UDEHCPU 36CH
CPU_Q02CPU-A Q02CPU 141H Q02CPU-A 141H
CPU_Q02HCPU-A Q02HCPU
CPU_Q06HCPU-A Q06HCPU 142H Q06HCPU-A 142H
CPU_L02SCPU L02SCPU 543H -
CPU_L02CPU L02CPU 541H
CPU_L06CPU L06CPU 544H
CPU_L26CPU L26CPU 545H
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_Q172CPU Q172CPU 2010H
CPU_Q172HCPU Q172HCPU 2012H
CPU_Q173CPU Q173CPU 2011H
CPU_Q173HCPU Q173HCPU 2013H
CPU_Q172DCPU Q172DCPU 2014H
CPU_Q173DCPU Q173DCPU 2015H
CPU_Q172DSCPU Q172DSCPU 2018H
CPU_Q173DSCPU Q173DSCPU 2019H
CPU_FX0 FX0/FX0S F0H FX0/FX0S F0H
CPU_FX0S
CPU_FX0N FX0N 8EH FX0N 8EH
CPU_FX1 FX1 F1H FX1 F1H
CPU_FX1S FX1S F2H FX1S F2H
CPU_FX1N FX1N 9EH FX1N 9EH
CPU_FX1NC

5 FUNCTIONS
406 5.2 Details of Functions (For ACT Control)
 CPU type When CPU/own board is connected When GX Simulator is connected
Network board/GOT Model character string Model code Model character string Model code
CPU_FXU FXU/FX2C 8DH FXU/FX2C 8DH
CPU_FX2C
CPU_FX2N FX2N/FX2NC 9DH FX2N/FX2NC 9DH
CPU_FX2NC
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 5
Q81BD-J71GF11-T2 Q81BD-J71GF11-T2
*1
GOT E340H
A800 0xA8 A8H
CRnD-7xx/CR75x-D CRnD-7xx 03H

*1 A product model number of GOT is displayed.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 407
 SetCpuStatus (Remote control)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Applicable communication routes

The following table shows the applicable communication routes.
: Applicable, : Not applicable
Communication route Property setting Appli
ActUnitType ActProtocolType cabilit
y
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 *1,*2
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
UNIT_RETHER_DIRECT PROTOCOL_UDPIP
UNIT_FXVETHER PROTOCOL_TCPIP *1
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 *1
UNIT_FXETHER_DIRECT PROTOCOL_UDPIP
CPU COM Connection target CPU: FX5CPU UNIT_FXVCPU PROTOCOL_SERIAL *1
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

5 FUNCTIONS
408 5.2 Details of Functions (For ACT Control)
Communication route Property setting Appli
ActUnitType ActProtocolType cabilit
y
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 *3
Connection target CPU: Q motion CPU UNIT_QNMOTIONUSB 
Connection target CPU: FXCPU UNIT_FXCPU *1
MELSECNET/H communication UNIT_MNETHBOARD PROTOCOL_MNETH *4
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 G4 communication UNIT_G4QCPU PROTOCOL_SERIAL  5
GX Simulator communication UNIT_SIMULATOR PROTOCOL_SHAREDMEMORY 
GX Simulator2 communication UNIT_SIMULATOR2 - 
GX Simulator3 communication (RCPU) UNIT_SIMULATOR3
GX Simulator3 communication (FX5CPU) *1
MT Simulator2 communication UNIT_SIMULATOR2 - 
Modem Connected module: Q series-compatible UNIT_QJ71C24 PROTOCOL_SERIALMODEM 
communication C24
Connected module: L series-compatible UNIT_LJ71C24 PROTOCOL_SERIALMODEM
C24
Connection target CPU: FXCPU UNIT_FXCPU PROTOCOL_TEL *1
Gateway function communication UNIT_A900GOT PROTOCOL_UDPIP 
GOT transparent function communication UNIT_RJ71C24, UNIT_QNCPU, PROTOCOL_SERIAL, 
UNIT_LNCPU PROTOCOL_USBGOT
UNIT_FXVCPU, 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, *1
UNIT_GOT_FXENET
UNIT_GOTETHER_RJ71C24, PROTOCOL_TCPIP 
UNIT_GOTETHER_QNCPU,
UNIT_GOTETHER_LNCPU
UNIT_GOTETHER_FXVCPU, *1
UNIT_GOTETHER_FXCPU
UNIT_GOTETHER_QBUS 
UNIT_GOTETHER_QN_ETHER 
Q series bus communication UNIT_QBF PROTOCOL_QBF 
Inverter communication - COMM_RS232C, COMM_USB 

*1 An error is returned when PAUSE is specified.

*2 An error is returned when the CPU is other than FX1N, FX1NC, FX2N, FX2NC, FX3S, FX3U, FX3UC, FX3G and FX3GC.
*3 The error code "0x010A42A0" (the access password mismatch) is returned when accessing QSCPU.
*4 An error is returned when the own board is accessed.

Feature
Perform a remote operation of programmable controller CPU.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 409
 Format (Dispatch interface)
■VBA
lRet = object.SetCpuStatus(lOperation)
Long lRet Returned value Output
Long lOperation Remote RUN/STOP/PAUSE Input

■Visual C++ .NET(MFC)

lRet = object.SetCpuStatus(lOperation)
Long lRet Returned value Output
Long lOperation Remote RUN/STOP/PAUSE Input

■VBScript
varRet = object.SetCpuStatus(varOperation)
VARIANT varRet Returned value (LONG type) Output
VARIANT varOperation Remote RUN/STOP/PAUSE (LONG type) Input

■Visual Basic .NET

IRet = object.SetCpuStatus(IOperation)
Integer IRet Returned value Output
Integer IOperation Remote RUN/STOP/PAUSE Input

■Visual C++ .NET

iRet = object.SetCpuStatus (iOperation)
int iRet Returned value Output
int iOperation Remote RUN/STOP/PAUSE Input

■Visual C# .NET
iRet = object.SetCpuStatus (iOperation)
int iRet Returned value Output
int iOperation Remote RUN/STOP/PAUSE Input

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.SetCpuStatus(lOperation, *lplRetCode )
HRESULT hResult Returned value of COM Output
LONG lOperation Remote RUN/STOP/PAUSE Input
LONG *lplRetCode Returned value of communication function Output

Description
The operation specified for lOperation (varOperation or 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

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• Since FXCPU or FX5CPU does not have the PAUSE switch as a programmable controller CPU, an error is
returned if a remote pause operation is specified using the SetCpuStatus function.
• If a Q motion CPU is accessed and PAUSE is specified, an error is returned.
• If an R motion CPU is accessed, an error is returned.

5 FUNCTIONS
410 5.2 Details of Functions (For ACT Control)
EntryDeviceStatus (Registering devices for status monitoring)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Register devices whose status to be monitored.

Format (Dispatch interface)

■VBA
lRet = object.EntryDeviceStatus(szDeviceList, lSize, lMonitorCycle, lData(0))
Long lRet Returned value Output
String szDeviceList Registered device name list Input 5
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++ .NET(MFC)

lRet = object.EntryDeviceStatus (szDeviceList, lSize, lMonitorCycle, *lplData)
Long lRet Returned value Output
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

■VBScript
varRet = object.EntryDeviceStatus(varDeviceList, varSize, varMonitorCycle, varData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDeviceList Registered device name list (BSTR type) Input
VARIANT varSize Number of registered device points (LONG type) Input
VARIANT varMonitorCycle Status monitoring time interval (LONG type) Input
VARIANT varData Registered device value list (LONG type) Input

■Visual Basic .NET

IRet = object.EntryDeviceStatus(szDeviceList, ISize,IMonitorCycle, IData(0))
Integer IRet Returned value Output
String szDeviceList Registered device 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++ .NET

iRet = object.EntryDeviceStatus(szDeviceList, iSize, iMonitorCycle, *iplData)
int iRet Returned value Output
String *szDeviceList Registered device name list Input
int iSize Number of registered device points Input
int iMonitorCycle Status monitoring time interval Input
int *iplData Registered device value list Input

■Visual C# .NET
iRet = object. EntryDeviceStatus(szDeviceList, iSize, iMonitorCycle, ref iData[0])
int iRet Returned value Output
String szDeviceList Registered device 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

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 411
 Format (Custom interface)
■Visual C++ .NET(MFC)
hResult = object.EntryDeviceStatus(szDeviceList, lSize,lMonitorCycle, *lplData, *lplRetCode)
HRESULT hResult Returned value of COM Output
BSTR szDeviceList Registered device name list Input
LONG lSize Number of registered device points Input
LONG lMonitorCycle Status monitoring time interval Input
LONG *lplData Device value to be written Input
LONG *lplRetCode Returned value of communication function Output

Description
• A device group for the size of lSize (varSize or iSize) specified for szDeviceList (varDeviceList) is checked whether it is in
the status specified for lData (lplData, varData, or iData).
Specify the check time for lMonitorCycle (varMonitorCycle or iMonitorCycle).
When the status is established, the OnDeviceStatus function of the user application is executed.
• 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, VBScript: "D0" & vbLf & "D1" & vbLf & "D2"
When using Visual C++ .NET: D0\nD1\nD2
When using Visual C# .NET: D0\nD1\nD2

• The maximum number of device points that can be specified for lSize (varSize or iSize) is 20 points.
• Specify a value within the range from 1 second to 1 hour (set between 1 and 3600 in seconds) for lMonitorCycle
(varMonitorCycle or iMonitorCycle).
An error occurs when any other value outside the above range is specified.
• The registered device value list is stored in lData (lplData, varData, or iData).

How to specify devices

The following describes how to specify devices.

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

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

Upper 2 bytes Lower 2 bytes

Not used (0 is stored.) M0
D0
M16 to M31*1 M0 to M15*1

*1 Devices are stored from the lower bit in the order of device number.

■When double word devices are specified

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

Upper 2 bytes Lower 2 bytes

H of LTN0 L of LTN0
H of LTN1 L of LTN1
H of LTN2 L of LTN2

5 FUNCTIONS
412 5.2 Details of Functions (For ACT Control)
■When devices including CN200 and later of FXCPU are specified (Total number of points: 3
points)
For CN200 or later devices of FXCPU, 2 words are read for each point when reading devices randomly.
When using Visual Basic .NET, VBA, VBScript: "D0" & vbLf & "CN200" & vbLf & "D1"
When using Visual C++ .NET: D0\nCN200\nD1
When using Visual C# .NET: D0\nCN200\nD1

Upper 2 bytes Lower 2 bytes

Not used (0 is stored.) D0
H of CN200 L of CN200
Not used (0 is stored.) D1

■When devices including FD are specified (Total number of points: 3 points)

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

Upper 2 bytes
Not used (0 is stored.)
Lower 2 bytes
D0
5
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, VBScript: "D0" & vbLf & "EG0" & vbLf & "D1"
When using Visual C++ .NET: D0\nEG0\nD1
When using Visual C# .NET: D0\nEG0\nD1

Upper 2 bytes Lower 2 bytes

Not used (0 is stored.) D0
EG0
(E0001) (E0000)
D1

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 413
 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
bytes.
Example: When checking the D0 status for "-10"
Set the value "65526 (0000FFF6H)" where "0" is stored in the upper 2 bytes 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 section.
Page 585 Programming Examples for Monitoring Word Device Status

• 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.
• For lData (lplData, lpvarData, or iData), reserve a memory area for the number of points specified for lSize
(varSize or iSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• 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.

5 FUNCTIONS
414 5.2 Details of Functions (For ACT Control)
FreeDeviceStatus (Deregistering devices for status monitoring)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Deregister devices that are registered using the EntryDeviceStatus function to monitor their status.

Format (Dispatch interface)

■Visual C++ .NET(MFC), VBA
lRet = object.FreeDeviceStatus()
Long lRet Returned value Output

■VBScript
5
varRet = object.FreeDeviceStatus()
VARIANT varRet Returned value (LONG type) Output

■Visual Basic .NET

IRet = object.FreeDeviceStatus()
Integer IRet Returned value Output

■Visual C++ .NET

iRet = object. FreeDeviceStatus()
int iRet Returned value Output

■Visual C# .NET
iRet = object. FreeDeviceStatus()
int iRet Returned value Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.FreeDeviceStatus( *lplRetCode )
HRESULT hResult Returned value of COM Output
LONG *lplRetCode Returned value of communication function Output

Description
The devices that are set using the EntryDeviceStatus function to monitor their status are deregistered.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 415
 OnDeviceStatus (Event notification)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Execute the event notification when the device condition registered using the EntryDeviceStatus function is satisfied.

Format (Dispatch interface)

■VBA
object.OnDeviceStatus(szDevice, lData, lReturnCode)
String szDevice Name of device whose condition is satisfied Input
Long lData Value of device whose condition is satisfied Input
Long lReturnCode Returned value of condition check processing Input

■Visual C++ .NET(MFC)

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
Long lReturnCode Returned value of condition check processing Input

■VBScript
object.OnDeviceStatus(varDevice, varData, varReturnCode)
VARIANT varDevice Name of device whose condition is satisfied (BSTR type) Input
VARIANT varData Value of device whose condition is satisfied (LONG type) Input
VARIANT varReturnCode Returned value of condition check processing (LONG Input
type)

■Visual Basic .NET

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 following are the members of e.
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++ .NET

private: System::Void object_OnDeviceStatus (System::Object * sender, objectLib. ::_objectIEvents_OnDeviceStatusEvent *
e)
sender Event occurrence source Output
e Event data Output
The following are the members of e.
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# .NET
private void object_OnDeviceStatus
(object sender,object._IActUtlTypeEvents_OnDeviceStatusEvent e)
sender Event occurrence source Output
e Event data Output
The following are the members of e.
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

5 FUNCTIONS
416 5.2 Details of Functions (For ACT Control)
Format (Custom interface)
■Visual C++ .NET(MFC)
object.OnDeviceStatus(szDevice, lData, lReturnCode, *lplRetCode)
LPCTSTR szDevice Name of device whose condition is satisfied Input
LONG lData Value of device whose condition is satisfied Input
LONG lReturnCode Returned value of condition check processing Input
LONG *lplRetCode Returned value of communication function Output

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 application 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 (varData).
Example: When the word device is monitored for the value of "-1" 5
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 (varData).

Returned value
None

• When any of the following settings is set in the user application, 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) User applications created using Visual Basic .NET or VBA (Excel)
⋅ The message box is displayed in the user application.
⋅ The InputBox/OutputBox is displayed in the user application.
(2) User applications created using Visual Basic .NET, Visual C++ .NET, Visual C# .NET, VBA (Excel,
Access) or VBScript
⋅ The Sleep processing, WaitForSingleObject function, or similar standby function is used in the user
application.
• For installing Reference, refer to the sample programs for Reference for VB .NET/VC .NET.(Page 539
Visual Basic .NET Sample Programs, Page 547 Visual C++ .NET Sample Programs)

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 417
 ReadDeviceBlock2 (Reading devices in bulk)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Read devices in 2-byte data unit in bulk.

Format (Dispatch interface)

■VBA
lRet = object.ReadDeviceBlock2(szDevice, lSize, iData(0))
Long lRet Returned value Output
String szDevice Device name Input
Long lSize Number of read points Input
Integer iData(n) Read device value Output

■Visual C++ .NET(MFC)

lRet = object.ReadDeviceBlock2(szDevice, lSize, *lpsData)
Long lRet Returned value Output
CString szDevice Device name Input
Long lSize Number of read points Input
Short *lpsData Read device value Output

■VBScript
varRet = object.ReadDeviceBlock2(varDevice, varSize, lpvarData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDevice Device name (character string type) Input
VARIANT varSize Number of read points (LONG type) Input
VARIANT lpvarData Read device value (SHORT type) Output

■Visual Basic .NET

IRet = object.ReadDeviceBlock2(szDevice, ISize, sData(0))
Integer IRet Returned value Output
String szDevice Device name Input
Integer ISize Number of read points Input
short sData(n) Read device value Output

■Visual C++ .NET

iRet = object.ReadDeviceBlock2(*szDevice, iSize, *lpsData)
int iRet Returned value Output
String *szDevice Device name Input
int iSize Number of read points Input
short *lpsData Read device value Output

■Visual C# .NET
iRet = object.ReadDeviceBlock2(szDevice, iSize, out sData[0])
int iRet Returned value Output
String szDevice Device name Input
int iSize Number of read points Input
short[n] sData Read device value Output

5 FUNCTIONS
418 5.2 Details of Functions (For ACT Control)
Format (Custom interface)
■Visual C++ .NET(MFC)
hResult = object.ReadDeviceBlock2( szDevice, lSize, *lpsData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDevice Device name Input
LONG lSize Number of read points Input
SHORT *lpsData Read device value Output
LONG *lplRetCode Returned value of communication function Output

Description
• The device values of lSize (varSize or iSize) are read in bulk starting from the device specified for szDevice (varDevice) as
SHORT type data.
• The read device values are stored in iData (lpsData, lpvarData, or sData).
• For lData (lpsData, lpvarData, or sData), reserve arrays for more than the amount specified for lSize (varSize or iSize).
5
How to specify devices
The following describes how to specify devices.

■When bit device is specified

Example: Read 3 points (3 words) of data in 16-point unit starting from M0.
2 Bytes
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 word device is specified

Example: Read 3 points of data starting from D0.
2 Bytes
D0
D1
D2

■When double-word device is specified

Example: Read 3 points from LTN0
2 Bytes
L of LTN0
L of LTN1
L of LTN2

■When CN200 and later devices of FXCPU are specified

Example: Read 6 points of data starting from CN200.
For CN200 or later device of FXCPU, 2 words are read for each 2 points. Reading only 1 point will result in an error.
2 Bytes
L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 419
 ■When FD device is specified (4-word device)
Example: Read 6 points of data starting from FD0.
2 Bytes
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 starting from EG0.
(When 8-bit devices (from E0000 to E0007 of SHARP programmable controller) are assigned from EG0 to EG3.)
2 Bytes
EG0
(E0001) (E0000)
EG1
(E0003) (E0002)
EG2
(E0005) (E0004)
EG3
(E0007) (E0006)

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of read points that can be specified for lSize (varSize) should be the value which
satisfies the following condition.
Read starting device number + Number of read points ≤ Last device number
• When specifying bit devices, a multiple of 16 can be specified as a device number.
• For iData (lpsData, lpvarData, or sData), reserve a memory area for the number of points specified for lSize
(varSize or iSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.

5 FUNCTIONS
420 5.2 Details of Functions (For ACT Control)
WriteDeviceBlock2 (Writing devices in bulk)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Write devices in 2-byte data unit in bulk.

Format (Dispatch interface)

■VBA
lRet = object.WriteDeviceBlock2(szDevice, lSize, iData(0))
Long lRet Returned value Output
String szDevice Device name Input 5
Long lSize Number of write points Input
Integer iData(n) Device value to be written Input

■Visual C++ .NET(MFC)

lRet = object.WriteDeviceBlock2(szDevice, lSize, *lpsData)
Long lRet Returned value Output
CString szDevice Device name Input
Long lSize Number of write points Input
Short *lpsData Device value to be written Input

■VBScript
varRet = object.WriteDeviceBlock2(varDevice, varSize, varData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDevice Device name (character string type) Input
VARIANT varSize Number of write points (LONG type) Input
VARIANT varData Device value to be written (SHORT type) Input

■Visual Basic .NET

IRet = object.WriteDeviceBlock2(szDevice, ISize, sData(0))
Integer IRet Returned value Output
String szDevice Device name Input
Integer ISize Number of write points Input
short sData(n) Device value to be written Input

■Visual C++ .NET

iRet = object.WriteDeviceBlock2(*szDevice, iSize, *lpsData)
int iRet Returned value Output
String *szDevice Device name Input
int iSize Number of write points Input
short *lpsData Device value to be written Input

■Visual C# .NET
iRet = object.WriteDeviceBlock2(szDevice, iSize, ref sData[0])
int iRet Returned value Output
String szDevice Device name Input
int iSize Number of write points Input
short[n] sData Device value to be written Input

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 421
 Format (Custom interface)
■Visual C++ .NET(MFC)
hResult = object.WriteDeviceBlock2(szDevice, lSize, *lpsData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDevice Device name Input
LONG lSize Number of write points Input
SHORT *lpsData Device value to be written Input
LONG *lplRetCode Returned value of communication function Output

Description
• The device values of lSize (varSize or iSize) are written in bulk starting from the device specified for szDevice (varDevice).
• The device values to be written are stored in lData (lpsData, varData, or sData).
• For iData (lpsData, varData, or sData), reserve arrays for more than the amount specified for lSize(varSize or iSize).

How to specify devices

The following describes how to specify devices.

■When bit device is specified

Example: Write 3 points (3 words) of data in 16-point unit starting from M0.
2 Bytes
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 word device is specified

Example: Write 3 points of data starting from D0.
2 Bytes
D0
D1
D2

■When double-word device is specified

Example: Write 3 points to LTN0
2 Bytes
L of LTN0
L of LTN1
L of LTN2

■When CN200 and later devices of FXCPU are specified

Example: Write 6 points of data starting from CN200.
For CN200 or later device of FXCPU, 2 words are written for each 2 points. Writing only 1 point will result in an error.
2 Bytes
L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

5 FUNCTIONS
422 5.2 Details of Functions (For ACT Control)
■When FD device is specified (4-word device)
Example: Write 6 points of data starting from FD0.
2 Bytes
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: Write 4 points of data starting from EG0.
(When 8-bit devices (from E0000 to E0007 of SHARP programmable controller) are assigned from EG0 to EG3.)
2 Bytes
EG0
(E0001) (E0000)
5
EG1
(E0003) (E0002)
EG2
(E0005) (E0004)
EG3
(E0007) (E0006)

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of write points that can be specified for lSize (varSize or iSize) should be the value
which satisfies the following condition.
Write starting device number + Number of write points ≤ Last device number
• When specifying bit devices, a multiple of 16 can be specified as a device number.
• For iData (lpsData, varData, or sData), reserve a memory area for the number of points specified for lSize
(varSize or iSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• WriteDeviceBlock or WriteDeviceBlock2 cannot be used for writing long timer device (LT) and retentive long
timer device (LST).
Use WriteDeviceRandom, WriteDeviceRandom2, SetDevice or SetDevice2.
• 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.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 423
 ReadDeviceRandom2 (Reading devices randomly)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Read devices in 2-byte data unit randomly.

Format (Dispatch interface)

■VBA
lRet = object.ReadDeviceRandom2(szDeviceList, lSize, iData(0))
Long lRet Returned value Output
String szDeviceList Device name Input
Long lSize Number of read points Input
Integer iData(n) Read device value Output

■Visual C++ .NET(MFC)

lRet = object.ReadDeviceRandom2(szDeviceList, lSize, *lpsData)
Long lRet Returned value Output
CString szDeviceList Device name Input
Long lSize Number of read points Input
Short *lpsData Read device value Output

■VBScript
varRet = object.ReadDeviceRandom2(varDeviceList, varSize, lpvarData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDeviceList Device name (character string type) Input
VARIANT varSize Number of read points (LONG type) Input
VARIANT lpvarData Read device value (SHORT type) Output

■Visual Basic .NET

IRet = object.ReadDeviceRandom2(szDeviceList, ISize, sData(0))
Integer IRet Returned value Output
String szDeviceList Device name Input
Integer ISize Number of read points Input
short sData(n) Read device value Output

■Visual C++ .NET

iRet = object.ReadDeviceRandom2(*szDeviceList, iSize, *lpsData)
int iRet Returned value Output
String *szDeviceList Device name Input
int iSize Number of read points Input
short *lpsData Read device value Output

■Visual C# .NET
iRet = object.ReadDeviceRandom2(szDevice, iSize, out sData[0])
int iRet Returned value Output
String szDevice Device name Input
int iSize Number of read points Input
short[n] sData Read device value Output

5 FUNCTIONS
424 5.2 Details of Functions (For ACT Control)
Format (Custom interface)
■Visual C++ .NET(MFC)
hResult = object.ReadDeviceRandom2( szDeviceList, lSize, *lpsData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDeviceList Device name Input
LONG lSize Number of read points Input
SHORT *lpsData Read device value Output
LONG *lplRetCode Returned value of communication function Output

Description
• Data of a device group for the size of lSize (varSize or iSize) specified for szDeviceList (varDeviceList or szDevice) are
read.
• The read device values are stored in iData (lpsData, lpvarData, or sData).
• 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. 5
Example:
When using Visual Basic .NET, VBA, VBScript: "D0" & vbLf & "D1" & vbLf & "D2"
When using Visual C++ .NET: D0\nD1\nD2
When using Visual C# .NET: D0\nD1\nD2

• For lData (lpsData, lpvarData, or sData), reserve arrays for more than the amount specified for lSize (varSize or iSize).

How to specify devices

The following describes how to specify devices.

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

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

2 Bytes
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.
*2 Devices are stored from the lower bit in the order of device number.
Data are not read from the upper 2 bytes of M16 to M31.

■When double word devices are specified

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

2 Bytes
L of LTN0
L of LTN1
L of LTN2

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 425
 ■When devices including CN200 or later of FXCPU is specified (Total number of points: 3
points)
When using Visual Basic .NET, VBA, VBScript: "D0" & vbLf & "CN200" & vbLf & "D1"
When using Visual C++ .NET: D0\nCN200\nD1
When using Visual C# .NET: D0\nCN200\nD1

2 Bytes
D0
L of CN200*1
D1

*1 For CN200 and later devices of FXCPU, the L (lower 2 bytes) of the specified devices is read for each point when the
ReadDeviceRandom2 function is executed.
The H (upper 2 bytes) of the specified devices is not read.

■When devices including FD are specified (Total number of points: 3 points)

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

2 Bytes
D0
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, VBScript: "D0" & vbLf & "EG0" & vbLf & "D1"
When using Visual C++ .NET: D0\nEG0\nD1
When using Visual C# .NET: D0\nEG0\nD1

2 Bytes
D0
EG0
(E0001) (E0000)
D1

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of read points that can be specified for lSize (varSize or iSize) is 0x7FFFFFFF
points.
• For iData (lpsData, lpvarData, or sData), reserve a memory area for the number of points specified for lSize
(varSize or iSize).
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• When a double word device is specified, only the data of the lower 1 word (2 bytes) are stored using the
ReadDeviceRandom2 function. (An error does not occur.)
When reading data from a double word device, use the ReadDeviceRandom function or the GetDevice
function.

5 FUNCTIONS
426 5.2 Details of Functions (For ACT Control)
WriteDeviceRandom2 (Writing devices randomly)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Write devices in 2-byte data unit randomly.

Format (Dispatch interface)

■VBA
lRet = object.WriteDeviceRandom2(szDeviceList, lSize,iData(0))
Long lRet Returned value Output
String szDeviceList Device name Input 5
Long lSize Number of write points Input
Integer iData(n) Device value to be written Input

■Visual C++ .NET(MFC)

lRet = object.WriteDeviceRandom2(szDeviceList, lSize,*lpsData)
Long lRet Returned value Output
CString szDeviceList Device name Input
Long lSize Number of write points Input
Short *lpsData Device value to be written Input

■VBScript
varRet = object.WriteDeviceRandom2(varDeviceList, varSize,varData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDeviceList Device name (character string type) Input
VARIANT varSize Number of write points (LONG type) Input
VARIANT varData Device value to be written (SHORT type) Input

■Visual Basic .NET

IRet = object.WriteDeviceRandom2(szDeviceList, ISize, sData(0))
Integer IRet Returned value Output
String szDeviceList Device name Input
Integer ISize Number of write points Input
short sData(n) Device value to be written Input

■Visual C++ .NET

iRet = object.WriteDeviceRandom2(*szDeviceList, iSize, *lpsData)
int iRet Returned value Output
String *szDeviceList Device name Input
int iSize Number of write points Input
short *lpsData Device value to be written Input

■Visual C# .NET
iRet = object.WriteDeviceRandom2(szDevice, iSize, ref sData[0])
int iRet Returned value Output
String szDevice Device name Input
int iSize Number of write points Input
short[n] sData Device value to be written Input

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 427
 Format (Custom interface)
■Visual C++ .NET(MFC)
hResult = object.WriteDeviceRandom2( szDeviceList, lSize, *lpsData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDeviceList Device name Input
LONG lSize Number of write points Input
SHORT *lpsData Device value to be written Input
LONG *lplRetCode Returned value of communication function Output

Description
• Data of a device group for the size of lSize (varSize or iSize) specified for szDeviceList (varDeviceList or szDevice) are
written.
• The device values to be written are stored in iData (lpsData, varData, or sData).
• 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, VBScript: "D0" & vbLf & "D1" & vbLf & "D2"
When using Visual C++ .NET: D0\nD1\nD2
When using Visual C# .NET: D0\nD1\nD2

• For iData (lpsData, varData, or sData), reserve arrays for more than the amount specified for lSize (varSize or iSize).

How to specify devices

The following describes how to specify devices.

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

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

2 Bytes
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.
*2 Devices are stored from the lower bit in the order of device number. "0" is written to the upper 2 bytes of M16 to M31.

■When double word devices are specified

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

2 Bytes
L of LTN0
L of LTN1
L of LTN2

■When devices including CN200 or later of FXCPU is specified (Total number of points: 3
points)
When using Visual Basic .NET, VBA, VBScript: "D0" & vbLf & "CN200" & vbLf & "D1"
When using Visual C++ .NET: D0\nCN200\nD1
When using Visual C# .NET: D0\nCN200\nD1

2 Bytes
D0
L of CN200*1
D1

*1 For CN200 or later device of FXCPU, data is written to the L (lower 2 bytes) of the specified devices for each point when the
WriteDeviceRandom2 function is executed. "0" is written to the H (upper 2 bytes) of the specified devices.

5 FUNCTIONS
428 5.2 Details of Functions (For ACT Control)
■When devices including FD are specified (Total number of points: 3 points)
When using Visual Basic .NET, VBA, VBScript: "D0" & vbLf & "FD0" & vbLf & "D1"
When using Visual C++ .NET: D0\nFD0\nD1
When using Visual C# .NET: D0\nFD0\nD1

2 Bytes
D0
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, VBScript: "D0" & vbLf & "EG0" & vbLf & "D1"
When using Visual C++ .NET: D0\nEG0\nD1
When using Visual C# .NET: D0\nEG0\nD1

2 Bytes
D0
5
EG0
(E0001) (E0000)
D1

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of write points that can be specified for lSize (varSize or iSize) is 0x7FFFFFFF
points.
• For iData (lpsData, varData, or sData), reserve a memory area for the number of points specified for lSize
(varSize or iSize)..
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• When a double word device is specified, data are written to the data area of the lower 1 word (2 bytes) using
the WriteDeviceRandom2 function, and "0" is written to the data area of the upper 1 word (2 bytes).
When writing a double word device, use the WriteDeviceRandom function or the SetDevice function.
• If a Q motion CPU is accessed, an error is returned.
• 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.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 429
 SetDevice2 (Set device data)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Set one point of device in 2-byte data unit.

Format (Dispatch interface)

■VBA
lRet = object.SetDevice2(szDevice, iData)
Long lRet Returned value Output
String szDevice Device name Input
Integer iData Set data Input

■Visual C++ .NET(MFC)

lRet = object.SetDevice2(szDevice, sData)
Long lRet Returned value Output
CString szDevice Device name Input
Short sData Set data Input

■VBScript
varRet = object.SetDevice2(varDevice, varData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDevice Device name (character string type) Input
VARIANT varData Set data (SHORT type) Input

■Visual Basic .NET

IRet = object.SetDevice2(szDevice, sData)
Integer IRet Returned value Output
String szDevice Device name Input
short sData Set data Input

■Visual C++ .NET

iRet = object.SetDevice2(*szDevice, sData)
int iRet Returned value Output
String *szDevice Device name Input
short sData Set data Input

■Visual C# .NET
iRet = object.SetDevice2(szDevice, sData)
int iRet Returned value Output
String szDevice Device name Input
short sData Set data Input

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.SetDevice2( szDevice, sData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDevice Device name Input
SHORT sData Set data Input
LONG *lplRetCode Returned value of communication function Output

5 FUNCTIONS
430 5.2 Details of Functions (For ACT Control)
Description
• One point of device specified for szDevice (varDevice) is specified using iData (sData or varData).
• When specifying bit devices, the least significant bit of the iData value (sData value or varData value) is valid.

How to specify devices

The following describes how to specify devices.

■When bit device is specified

Example: M0
2 Bytes
M0*1

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

■When word device is specified

Example: D0
5
2 Bytes
D0

■When double-word device is specified

Example: LTN0
2 Bytes
L of LTN0

■When double-word device is specified (Digit specification)

Example: K8M0
2 Bytes
M0 to M15*1

*1 Devices are stored from the lower bit in the order of device number. "0" is written to the upper 2 bytes of M16 to M31.

■When CN200 or later device of FXCPU is specified

Example: CN200
2 Bytes
L of CN200*1

*1 For CN200 and later devices of FXCPU, data are written to the L (lower 2 bytes) of the specified devices for each point when the
SetDevice2 function is executed.
"0" is written to the H (upper 2 bytes) of the specified devices.

■When gateway device is specified

Example: When 8-bit devices (E0000 and E0001 of SHARP programmable controller) are assigned to EG0
2 Bytes
EG0
(E0001) (E0000)

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 431
 Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• When a double word device is specified, data are written to the data area of the lower 1 word (2 bytes) using
the SetDevice2 function, and "0" is written to the data area of the upper 1 word (2 bytes).
When writing a double word device, use the WriteDeviceRandom function or the SetDevice function.
• 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.

5 FUNCTIONS
432 5.2 Details of Functions (For ACT Control)
GetDevice2 (Acquiring device data)

Applicable controls
Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.
(Not applicable to inverter communication/robot controller communication.)

Feature
Acquire one point of device in 2-byte data unit.

Format (Dispatch interface)

■VBA
lRet = object.GetDevice2(szDevice, iData)
Long lRet Returned value Output
String szDevice Device name Input 5
Integer iData Acquired data Output

■Visual C++ .NET(MFC)

lRet = object.GetDevice2(szDevice, *lpsData)
Long lRet Returned value Output
CString szDevice Device name Input
Short *lpsData Acquired data Output

■VBScript
varRet = object.GetDevice2(varDevice, lpvarData)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDevice Device name (character string type) Input
VARIANT lpvarData Acquired data (SHORT type) Output

■Visual Basic .NET

IRet = object.GetDevice2(szDevice, sData)
Integer IRet Returned value Output
String szDevice Device name Input
short sData Acquired data Output

■Visual C++ .NET

iRet = object.GetDevice2(*szDevice, *spsData)
int iRet Returned value Output
String *szDevice Device name Input
short *spsData Acquired data Output

■Visual C# .NET
iRet = object.GetDevice2(szDevice, out sData)
int iRet Returned value Output
String szDevice Device name Input
short sData Acquired data Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.GetDevice2( szDevice, *lpsData, *lplRetCode )
HRESULT hResult Returned value of COM Output
BSTR szDevice Device name Input
SHORT *lpsData Acquired data Output
LONG *lplRetCode Returned value of communication function Output

Description
One point of device data specified for szDevice (varDevice) is stored in iData (lpsData, lpvarData, or sData).

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 433
 How to specify devices
The following describes how to specify devices.

■When bit device is specified

Example: M0
2 Bytes
M0*1

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

■When word device is specified

Example: D0
2 Bytes
D0

■When double-word device is specified

Example: LTN0
2 Bytes
L of LTN0

■When double-word device is specified (Digit specification)

Example: K8M0
2 Bytes
M0 to M15*1

*1 Devices are stored from the lower bit in the order of device number.
Data are not read from the upper 2 bytes of M16 to M31.

■When CN200 or later device of FXCPU is specified

Example: CN200
2 Bytes
L of CN200*1

*1 For CN200 and later devices of FXCPU, the L (lower 2 bytes) of the specified devices is read for each point when the GetDevice2
function is executed.
The H (upper 2 bytes) of the specified devices is not read.

■When gateway device is specified

Example: When 8-bit devices (E0000 and E0001 of SHARP programmable controller) are assigned to EG0
2 Bytes
EG0
(E0001) (E0000)

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• When a double word device is specified, only the data of the lower 1 word (2 bytes) are stored using the
GetDevice2 function. (An error does not occur.)
• When reading data from a double word device, use the ReadDeviceRandom function or the GetDevice
function.

5 FUNCTIONS
434 5.2 Details of Functions (For ACT Control)
Connect (Connecting telephone line)

Applicable controls
Applicable to the ActProgType control and the ActUtlType control.
(Applicable to the modem communication only.)

Feature
Connect the telephone line.

Format (Dispatch interface)

■Visual C++ .NET(MFC), VBA
lRet = object.Connect()
Long lRet Returned value Output

■Visual Basic .NET

5
IRet = object.Connect()
Integer IRet Returned value Output

■Visual C++ .NET

iRet = object.Connect()
int iRet Returned value Output

■Visual C# .NET
iRet = object. Connect()
int iRet Returned value Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.Connect( *lplRetCode )
HRESULT hResult Returned value of COM Output
LONG *lplRetCode Returned value of communication function Output

Description
• The telephone line is connected according to the property settings of the modem communication control.
• When routing a serial communication module, the telephone line is connected in the connection system set in the
ActConnectWay property.
When auto line connect (callback number specification), callback connect (number specification), or callback request
(number specification) is set in the ActConnectWay property, an error occurs if a number is not set in the
ActCallbackNumber property.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

Considerations for executing the Connect function

• Always connect the telephone line before the execution of the Open function.
• When disconnecting the telephone line, execute the Disconnect function.
During the execution of the Connect function, the telephone line remains connected even when the Open and Close
functions are executed repeatedly.
• If the telephone line is disconnected in the Open status for some reason, always execute the Close function before
reconnecting the telephone line.

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 435
 Considerations when using multiple telephone line connection objects
• When control types, port numbers, and telephone numbers of controls are different
When control types, port numbers, and telephone numbers set to multiple controls are different, an error (error code:
0xF1000016) occurs if the Connect function is executed to connect the control whose port number and telephone number
are different from those of the control which executed the Connect function first.
• When port numbers and telephone numbers of controls are the same
When control types, port numbers, and telephone numbers set to multiple controls are the same, the termination status are
different according to the connection system of the callback function. The following table shows the relations between the
connection system and the termination status of the callback function.
 Normal termination : Abnormal termination (Error occurrence)
Connection system of Connection system of control which executed the Connect function second or Later
control which executed Auto line connect Callback connect Callback request Callback
the Connect function first Auto line connect (Callback (Fixation) (Fixation) reception
fixation) Callback connect Callback request waiting
Auto line connect (Callback (Number specification) (Number specification)
number specification)
Auto line connect    
Auto line connect (Callback
fixation)
Auto line connect (Callback
number specification)
Callback connect (Fixation)    
Callback connect (Number
specification)
Callback request (Fixation)    
Callback request (Number
specification)
Callback reception waiting    

5 FUNCTIONS
436 5.2 Details of Functions (For ACT Control)
Disconnect (Disconnecting telephone line)

Applicable controls
Applicable to the ActProgType control and the ActUtlType control.
(Applicable to the modem communication only.)

Feature
Disconnect the telephone line.

Format (Dispatch interface)

■Visual C++ .NET(MFC), VBA
lRet = object.Disconnect()
Long lRet Returned value Output

■Visual Basic .NET

5
IRet = object.Disconnect()
Integer IRet Returned value Output

■Visual C++ .NET

iRet = object.Disconnect()
int iRet Returned value Output

■Visual C# .NET
iRet = object. Disconnect ()
int iRet Returned value Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.Disconnect( *lplRetCode )
HRESULT hResult Returned value of COM Output
LONG *lplRetCode Returned value of communication function Output

Description
The telephone line that was connected using the Connect function is disconnected.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 437
 Considerations for executing the Disconnect function
• When executing the Disconnect function during the execution of the Open function, execute the Close function before
executing the Disconnect function.
• If the telephone line is disconnected in the Open status for some reason, always execute the Close function before
reconnecting the telephone line.
• When multiple telephone line connection objects are used, execute the Disconnect function on the object which executed
the Connect function first after executing the Disconnect function on other objects.
When multiple telephone line connection objects are used, the telephone line is not disconnected if the Disconnect function
is not executed on the object that executed the Connect function first.
The following figure shows the example of how to use multiple objects simultaneously.

Example: When using two controls simultaneously

(Including the case when the objects A and B are operated by different applications)

<Object A> <Object B>

Connection Connection
start start

Execution of the Connect function

Execution of the Connect function

Execution of the Open function

Execution of the Open function

Execution of the function such as

Telephone line is connected.

the ReadDeviceBlock function

Execution of the function such as
the ReadDeviceBlock function

Execution of the Close function

Execution of the Close function

Execution of the Disconnect function

Complete

Execution of the Disconnect function*1

*1 : The actual telephone line is disconnected.

The Disconnect function on the object A does not
Complete terminate normally if the Disconnection function is
not executed on the object B.

5 FUNCTIONS
438 5.2 Details of Functions (For ACT Control)
GetErrorMessage (Receiving error message)

Applicable controls
Applicable to the Act(ML)SupportMsg control.
(Not applicable to inverter communication)

Feature
Receive the error description and its corrective action corresponding to the error code.

Format (Dispatch interface)

■VBA
lRet = object.GetErrorMessage(lErrorCode, szErrorMessage)
Long lRet Returned value Output
Long lErrorCode Error code Input 5
String szErrorMessage Error message Output

■Visual C++ .NET(MFC)

lRet = object.GetErrorMessage(lErrorCode, *lpszErrorMessage)
Long lRet Returned value Output
Long lErrorCode Error code Input
BSTR *lpszErrorMessage Error message Output

■VBScript
varRet = object.GetErrorMessage(varErrorCode, lpvarErrorMessage)
VARIANT varRet Returned value (LONG type) Output
VARIANT varErrorCode Error code (LONG type) Input
VARIANT lpvarErrorMessage Error message (character string type) Output

■Visual Basic .NET

IRet = object.GetErrorMessage(IErrorCode, szErrorMessage)
Integer IRet Returned value Output
Integer IErrorCode Error code Input
String szErrorMessage Error message Output

■Visual C++ .NET

iRet = object.GetErrorMessage(iErrorCode, **lpsErrorMessage)
int iRet Returned value Output
int iErrorCode Error code Input
String **lpsErrorMessage Error message Output

■Visual C# .NET
iRet = object.GetErrorMessage(iErrorCode, out szErrorMessage)
int iRet Returned value Output
int iErrorCode Error code Input
String szErrorMessage Error message Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.GetErrorMessage( lErrorCode, *lpszErrorMessage, *lplRetCode )
HRESULT hResult Returned value of COM Output
LONG lErrorCode Error code Input
BSTR *lpszErrorMessage Error message Output
LONG *lplRetCode Returned value of communication function Output

5 FUNCTIONS
5.2 Details of Functions (For ACT Control) 439
 Description
• The error description and its corrective action of the error code specified for lErrorCode (varErrorCode or iErrorCode) are
read.
• The read error description and its corrective action are stored in szErrorMessage (lpszErrorMessage, lpsvarErrorMessage,
or lpvarErrorMessage).

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
440 5.2 Details of Functions (For ACT Control)
5.3 Details of Functions (For ACT Control (Logging
File Transfer))
Open (Opening communication line)

Applicable controls
Applicable to the ActProgDataLogging control and the ActUtlDataLogging control.

Feature
Open the communication line.

Format (Dispatch interface)

■Visual C++ .NET(MFC), VBA 5
lRet = object.Open()
Long lRet Returned value Output

■Visual Basic .NET

IRet = object.Open()
Integer IRet Returned value Output

■Visual C# .NET
iRet = object.Open()
int iRet Returned value Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.Open( *lplReturnCode )
HRESULT hResult Returned value of COM Output
LONG *lplReturnCode Returned value of communication function Output

Description
Lines are connected according to the set value of the Open function property.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• 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 one used for the communication is set to the ActCpuType
property, the Open function may be completed normally.
When executing the Open function, set the correct CPU type to the ActCpuType property.

5 FUNCTIONS
5.3 Details of Functions (For ACT Control (Logging File Transfer)) 441
 Close (Closing communication line)

Applicable controls
Applicable to the ActProgDataLogging control and the ActUtlDataLogging control.

Feature
Close the communication line.

Format (Dispatch interface)

■Visual C++ .NET(MFC), VBA
lRet = object.Close()
Long lRet Returned value Output

■Visual Basic .NET

IRet = object.Close()
Integer IRet Returned value Output

■Visual C# .NET
iRet = object.Close()
int iRet Returned value Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.Close( *lplReturnCode )
HRESULT hResult Returned value of COM Output
LONG *lplReturnCode Returned value of communication function Output

Description
The line connected using the Open function is closed.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• Call this function when an error occurred after calling the Open function or when exit the program.

5 FUNCTIONS
442 5.3 Details of Functions (For ACT Control (Logging File Transfer))
ReadFirstFile (Searching for a file/directory)

Applicable controls
Applicable to the ActProgDataLogging control and the ActUtlDataLogging control.

Feature
Search a file or directly in the specified directory.

Format (Dispatch interface)

■Visual C++ .NET(MFC)
Ret = object.ReadFirstFile(srcDir, *srcFilename, *srcType)
Long Ret Returned value Output
CString srcDir Directory name Input
BSTR
Long
*srcFileName
*srcType
File name or directory name
Type
Output
Output
5
■Visual Basic .NET
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# .NET
Ret = object.ReadFirstFile(srcDir, out srcFilename, out srcType)
int Ret Returned value Output
String srcDir Directory name Input
String srcFileName File name or directory name Output
int srcType Type Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.ReadFirstFile(srcDir, *srcFilename, *srcType, *lplReturnCode)
HRESULT hResult Returned value of COM Output
BSTR srcDir Directory name Input
BSTR *srcFileName File name or directory name Output
LONG *srcType Type Output
LONG *lplReturnCode Returned value of communication function Output

Description
Search for a file or a 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.
Example: When srcType is 24 (0x18), it indicates that the target is a directory.

Upper 3 byte Lower 1 byte

0 0 0 0 1 1 0 0 0

Example: When srcType is 16 (0x10), it indicates that the target is a file.

Upper 3 byte Lower 1 byte

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.

5 FUNCTIONS
5.3 Details of Functions (For ACT Control (Logging File Transfer)) 443
 Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

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

5 FUNCTIONS
444 5.3 Details of Functions (For ACT Control (Logging File Transfer))
ReadNextFile (Searching for a file/directory)

Applicable controls
Applicable to the ActProgDataLogging control and the ActUtlDataLogging control.

Feature
After searching a file or directory with ReadFirstFile, search the next file or directory in the specified directory.

Format (Dispatch interface)

■Visual C++ .NET(MFC)
Ret = object.ReadFirstFile(srcDir, *srcFilename, *srcType)
Long Ret Returned value Output
CString srcDir Directory name Input
BSTR
Long
*srcFileName
*srcType
File name or directory name
Type
Output
Output
5
■Visual Basic .NET
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# .NET
Ret = object.ReadFirstFile(srcDir, out srcFilename, out srcType)
int Ret Returned value Output
String srcDir Directory name Input
String srcFileName File name or directory name Output
int srcType Type Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.ReadFirstFile(srcDir, *srcFilename, *srcType, *lplReturnCode)
HRESULT hResult Returned value of COM Output
BSTR srcDir Directory name Input
BSTR *srcFileName File name or directory name Output
LONG *srcType Type Output
LONG *lplReturnCode Returned value of communication function Output

5 FUNCTIONS
5.3 Details of Functions (For ACT Control (Logging File Transfer)) 445
 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.

Upper 3 byte Lower 1 byte

0 0 0 0 1 1 0 0 0

Example: When srcType is 16 (0x10), it indicates that the target is a file.

Upper 3 byte Lower 1 byte

0 0 0 0 1 0 0 0 0

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The control does not return until the processing is completed.

• This function is available while logging is stopped.
• The search result is displayed randomly.

5 FUNCTIONS
446 5.3 Details of Functions (For ACT Control (Logging File Transfer))
ReadClose (Ending the search)

Applicable controls
Applicable to the ActProgDataLogging control and the ActUtlDataLogging control.

Feature
End the search.

Format (Dispatch interface)

■Visual C++ .NET(MFC)
Ret = object.ReadClose()
Long Ret Returned value Output

■Visual Basic .NET

Ret = object.ReadClose()
5
Integer Ret Returned value Output

■Visual C# .NET
Ret = object.ReadClose()
int Ret Returned value Output

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.ReadClose(*lplReturnCode)
HRESULT hResult Returned value of COM Output
LONG *lplReturnCode Returned value of communication function Output

Description
End the search.
• The result for searching for a directory or file name is deleted.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The control does not return until the processing is completed.

• This function is available while logging is stopped.

5 FUNCTIONS
5.3 Details of Functions (For ACT Control (Logging File Transfer)) 447
 GetFile (Transferring logging files)

Applicable controls
Applicable to the ActProgDataLogging control and the ActUtlDataLogging control.

Feature
Transfer a logging file.

Format (Dispatch interface)

■Visual C++ .NET(MFC)
Ret = object.GetFile(srcFileName , dstFileName)
Long Ret Returned value Output
CString srcFileName Transfer source file name Input
CString dstFileName Transfer destination file name Input

■Visual Basic .NET

Ret = object.GetFile(srcFileName , dstFileName)
Integer Ret Returned value Output
String srcFileName Transfer source file name Input
String dstFileName Transfer destination file name Input

■Visual C# .NET
Ret = object.GetFile(srcFileName , dstFileName)
int Ret Returned value Output
String srcFileName Transfer source file name Input
String dstFileName Transfer destination file name Input

Format (Custom interface)

■Visual C++ .NET(MFC)
hResult = object.GetFile(srcFileName , dstFileName, *lplReturnCode)
HRESULT hResult Returned value of COM Output
BSTR srcFileName Transfer source file name Input
BSTR dstFileName Transfer destination file name Input
LONG *lplReturnCode Returned value of communication function Output

Description
Transfer a logging file.
• The file specified for srcFileName is transferred to the file specified for dstFileName.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The control does not return until the processing is completed.

• This function is available while logging is stopped.
• Specify a character string for srcFileName within 318 bytes.
• Specify a character string for dstFileName within 259 bytes.

5 FUNCTIONS
448 5.3 Details of Functions (For ACT Control (Logging File Transfer))
5.4 Details of Functions (For .NET Control)
Open (Opening communication line)

Applicable controls
Applicable to the DotUtlType control.

Feature
Open the communication line.

Format
■Visual Basic .NET
IRet = object.Open() 5
Integer IRet Returned value Output

■Visual C++ .NET

iRet = object.Open()
int iRet Returned value Output

■Visual C# .NET
iRet = object.Open()
int iRet Returned value Output

Description
Lines are connected according to the set value of the Open function property.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• When modem communication is used, the Open function cannot be executed without the execution of the
Connect function.
• 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.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 449
 Close (Closing communication line)

Applicable controls
Applicable to the DotUtlType control.

Feature
Close the communication line.

Format
■Visual Basic .NET
IRet = object.Close()
Integer IRet Returned value Output

■Visual C++ .NET

iRet = object.Close()
int iRet Returned value Output

■Visual C# .NET
iRet = object.Close()
int iRet Returned value Output

Description
The line connected using the Open function is closed.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
450 5.4 Details of Functions (For .NET Control)
ReadDeviceBlock (Reading devices in bulk)

Applicable controls
Applicable to the DotUtlType control.

Feature
Read devices in bulk.

Format
■Visual Basic .NET
IRet = object.ReadDeviceBlock(szLabel, iSize, iData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer
Integer
iSize
iData(n)
Number of read points
Read device value
Input
Output
5
■Visual C++ .NET
iRet = object.ReadDeviceBlock(szLabel, iSize, iData)
Int iRet Returned value Output
String^ szLabel Label name Input
int iSize Number of read points Input
array<int>^ iData Read device value Output

■Visual C# .NET
iRet = object.ReadDeviceBlock(ref szLabel, iSize, ref iData)
Int iRet Returned value Output
String szLabel Label name Input
int iSize Number of read points Input
int[n] iData Read device value Output

Description
• The devices for the amount specified for iSize (number of read points) are read in bulk 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.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 451
 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
Array Label name
Array member Bit, Word, Double Word, Float (Single Precision), Float (Double Precision), String*1, String Label name [number of
(Unicode)*1, Time, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive elements]
timer Label name [n1] [n2] [n3]

*1 The maximum number of characters that can be specified is 32 + NULL.

■Number of read points

Set the following values for the number of read points 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 divided
by 16 (rounded up)
Word 1 Number of label array elements
Double Word, Float (Single Precision) 2 Number of label array elements multiplied
by 2
Float (Double Precision) 4 Number of label array elements multiplied
by 4
String 17 Number of label array elements multiplied
by 17
String (Unicode) 33 Number of label array elements multiplied
by 33
Time 2 Number of label array elements multiplied
by 2
Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer 1 Number of label array elements

How to specify devices

The read device values are stored as follows.

■When bit device is specified

Example: Read 3 points of data (3 words = 48 bits) from the devices starting from M0.
⋅ Label setting (Data type: Bit, Number of array elements: 48)
Data type Device
Bit (0..47) M0

⋅Number of read points: 3

⋅ Read device values
Upper 2 bytes Lower 2 bytes
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.

5 FUNCTIONS
452 5.4 Details of Functions (For .NET Control)
■When word device is specified
Example: Read 3 points of data from the devices starting from D0.
⋅ Label setting (Data type: Bit, Number of array elements: 48)
Data type Device
Word (0..2) D0

⋅Number of read points: 3

⋅ Read device values
Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) D0
D1
D2

■When CN200 and later devices of FXCPU are specified

Example: Read 6 points 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). 5
Reading only 1 point of data will result in an error.
⋅Label setting (Data type: Double Word, Number of array elements: 3)
Data type Device
Double Word (0..2) CN200

⋅Number of read points: 6

⋅ Read device values
Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

■When FD device is specified (4-word device)

Example: Read 8 points of data from the devices starting from FD0.
⋅Label setting (Data type: Double Word, Number of array elements: 2)
Data type Device
Double Word (0..1) FD0

⋅Number of read points: 8

⋅ Read device values
Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) LL of FD0
LH of FD0
HL of FD0
HH of FD0
LL of FD1
LH of FD1
HL of FD1
HH of FD1

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 453
 ■When label is Double Word array and word device is specified
Example: Read 6 points of data from the devices starting from D100.
⋅Label setting (Data type: Double Word, Number of array elements: 3)
Data type Device
Double Word (0..2) D100

⋅Number of read points: 6

⋅ Read device values
Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) D100
D101
D102
D103
D104
D105

■When long timer, long counter, or long retentive timer type is specified
Example: Read 3 points of data from the devices starting from LT0.
⋅Label setting (Data type: Long Timer, Number of array elements: 3)
Data type Device
Long timer (0..2) LT0

⋅Number of read points: 3

⋅ Read device values
Upper 2 bytes Lower 2 bytes
H of LT0 L of LT0
H of LT1 L of LT1
H of LT2 L of LT2

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of read points should be the value which satisfies the following condition.
Read start device number + Number of read points ≤ Last device number
• 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.
• 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.
• 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.

5 FUNCTIONS
454 5.4 Details of Functions (For .NET Control)
WriteDeviceBlock (Writing devices in bulk)

Applicable controls
Applicable to the DotUtlType control.

Feature
Write devices in bulk.

Format
■Visual Basic .NET
Ret = object.WriteDeviceBlock(szLabel, iSize, iData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer
Integer
iSize
iData(n)
Number of write points
Device value to be written
Input
Input
5
■Visual C++ .NET
iRet = object.WriteDeviceBlock(szLabel, iSize, iData)
int iRet Returned value Output
String^ szLabel Label name Input
int iSize Number of write points Input
array<int>^ ipiData Device value to be written Input

■Visual C# .NET
iRet = object.WriteDeviceBlock(ref szLabel, iSize, iData)
int iRet Returned value Output
String szLabel Label name Input
int iSize Number of write points Input
int[n] iData Device value to be written Input

Description
• The devices for the amount specified for iSize (number of write points) are written in bulk starting from the device specified
for szLabel (label name).
• The device values to be written are stored in iData.
• For iData, reserve arrays for more than the amount specified for iSize.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 455
 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
Array Label name
Array member Bit, Word, Double Word, Float (Single Precision), Float (Double Precision), String*1, String Label name [number of
(Unicode)*1, Time, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer elements]
Label name [n1] [n2] [n3]

*1 The maximum number of characters that can be specified is 32 + NULL.

■Number of write points

Set the following values for the number of write points according to the label data type.
Label (array) data type Number of Number of write points to be
applicable words specified
Bit 1 Number of label array elements divided
by 16 (rounded up)
Word 1 Number of label array elements
Double Word, Float (Single Precision) 2 Number of label array elements multiplied
by 2
Float (Double Precision) 4 Number of label array elements multiplied
by 4
String 17 Number of label array elements multiplied
by 17
String (Unicode) 33 Number of label array elements multiplied
by 33
Time 2 Number of label array elements multiplied
by 2
Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer 1 Number of label array elements

How to specify devices

Set the device values to be written as follows.

■When bit device is specified

Example: Write 3 points of data (3 words = 48 bits) to the devices starting from M0.
⋅ Label setting (Data type: Bit, Number of array elements: 48)
Data type Device
Bit (0..47) M0

⋅ Number of write points: 3

⋅Device values to be written
Upper 2 bytes Lower 2 bytes
Not used 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.

5 FUNCTIONS
456 5.4 Details of Functions (For .NET Control)
■When word device is specified
Example: Write 3 points of data to the devices starting from D0.
⋅Label setting (Data type: Word, Number of array elements: 3)
Data type Device
Word (0..2) D0

⋅ Number of write points: 3

⋅Device values to be written
Upper 2 bytes Lower 2 bytes
Not used D0
D1
D2

■When CN200 and later devices of FXCPU are specified

Example: Write 6 points 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). 5
Writing only 1 point of data will result in an error.
⋅Label setting (Data type: Double Word, Number of array elements: 3)
Data type Device
Double Word (0..2) CN200

⋅ Number of write points: 6

⋅Device values to be written
Upper 2 bytes Lower 2 bytes
Not used L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

■When FD device is specified (4-word device)

Example: Write 8 points of data to the devices starting from FD0.
⋅Label setting (Data type: Double Word, Number of array elements: 2)
Data type Device
Double Word (0..1) FD0

⋅ Number of write points: 8

⋅Device values to be written
Upper 2 bytes Lower 2 bytes
Not used LL of FD0
LH of FD0
HL of FD0
HH of FD0
LL of FD1
LH of FD1
HL of FD1
HH of FD1

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 457
 ■When label is Double Word array and word device is specified
Example: Write 6 points of data to the devices starting from D100.
⋅Label setting (Data type: Double Word, Number of array elements: 3)
Data type Device
Double Word (0..2) D100

⋅ Number of write points: 6

⋅Device values to be written
Upper 2 bytes Lower 2 bytes
Not used D100
D101
D102
D103
D104
D105

■When long timer, long counter, or long retentive timer type is specified
Example: Write 3 points of data from the devices starting from LT0.
⋅Label setting (Data type: Long Timer, Number of array elements: 3)
Data type Device
Long timer (0..2) LT0

⋅ Number of write points: 3

⋅Device values to be written
Upper 2 bytes Lower 2 bytes
H of LT0 L of LT0
H of LT1 L of LT1
H of LT2 L of LT2

5 FUNCTIONS
458 5.4 Details of Functions (For .NET Control)
Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of write points should be the value which satisfies the following condition.
Write starting device number + Number of write points ≤ Last device number
• When specifying bit type array labels, 0 or a multiple of 16 can be specified as a device number.
• 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.
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• When a device which corresponds to the label name does not exist, an error occurs and data cannot be
written. 5
When any one of devices which correspond to multiple label names does not exist, an error occurs and data
cannot be written.
• Digit specified bit device and index setting cannot be used.
• WriteDeviceBlock or WriteDeviceBlock2 cannot be used for writing long timer device (LT) and retentive long
timer device (LST).
Use WriteDeviceRandom, WriteDeviceRandom2, SetDevice or SetDevice2.
• 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.
• 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.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 459
 ReadDeviceRandom (Reading devices randomly)

Applicable controls
Applicable to the DotUtlType control.

Feature
Read devices randomly.

Format
■Visual Basic .NET
IRet = object.ReadDeviceRandom(szLabel, iSize, iData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of read points Input
Integer iData(n) Read device value Output

IRet = object.ReadDeviceRandom(szLabelList, iSize, iData)

Integer IRet Returned value Output
String^ szLabel Label list Input
int iSize Number of read points Input
array<int>^ iData Read device value Output

■Visual C++ .NET

iRet = object.ReadDeviceRandom(szLabel, iSize, iData)
Int iRet Returned value Output
String^ szLabel Label name Input
int iSize Number of read points Input
array<int>^ iData Read device value Output

iRet = object.ReadDeviceRandom(szLabelList, iSize, iData)

Int iRet Returned value Output
array<System::String ^>^ szLabelList Label list Input
int iSize Number of read points Input
array<int>^ iData Read device value Output

■Visual C# .NET
iRet = object.ReadDeviceRandom(ref szLabel, iSize, ref iData)
Int iRet Returned value Output
String szLabel Label name Input
int iSize Number of read points Input
int[n] iData Read device value Output

iRet = object.ReadDeviceRandom(ref szLabelList, iSize, ref iData)

Int iRet Returned value Output
System.String[n] szLabelList Label list Input
int iSize Number of read points Input
int[n] iData Read device value Output

Description
• Data of a device group for the size of iSize specified for the label name szLabel (szLabelList) are read.
• The read device values are stored in iData.
• For iData, reserve arrays for more than the amount specified for iSize.

5 FUNCTIONS
460 5.4 Details of Functions (For .NET Control)
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
Basic type Bit, Word, Double Word, Float (Single Precision), Float (Double Precision), String*1, String Label name
(Unicode)*1, Time, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive
timer
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]
Label name [n1] [n2] [n3]
Structure Label name
Structure member (The label data type can be specified in the same manner as the basic type.) Label name.Member name
Structured array Label name [number of
elements]
5
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
Label name [n1] [n2]
[n3].Element

*1 The maximum number of characters that can be specified is 32 + NULL.

■Number of read points

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
applicable words specified
Bit, Word 1 Number of label elements
Double Word, Float (Single Precision) 2 Number of label elements multiplied by 2
Float (Double Precision) 4 Number of label elements multiplied by 4
String 17 Number of label elements multiplied by
17
String (Unicode) 33 Number of label array elements multiplied
by 33
Time 2 Number of label elements multiplied by 2
Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer 1 Number of label elements

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 461
 How to specify devices
The read device values are stored as follows.

■When bit device and word device are specified

Example: Read data from each 1 point of M0 and D0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Bit M0
[1] LABEL2 Word D0

⋅Number of read points: 2

⋅ Read device values
Upper 2 bytes Lower 2 bytes Applicable label
*1
Not used (0 is stored.) M0 LABEL1
D0 LABEL2

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

■When CN200 and later devices of FXCPU are specified

Example: Read 3 points of data from the devices including CN200.
For CN200 and later devices of FXCPU, 4 bytes are read as 1 read point.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Word D0
[1] LABEL2 Word CN200
[2] LABEL3 Word D1

⋅Number of read points: 3

⋅ Read device values
Upper 2 bytes Lower 2 bytes Applicable label
Not used (0 is stored.) D0 LABEL1
H of CN200 L of CN200 LABEL2
Not used (0 is stored.) D1 LABEL3

■When FD device is specified (4-word device)

Example: Read 3 points of data from the devices including FD0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Word D0
[1] LABEL2 Word FD0
[2] LABEL3 Word D1

⋅Number of read points: 3

⋅ Read device values
Upper 2 bytes Lower 2 bytes Applicable label
Not used (0 is stored.) D0 LABEL1
*1
LL of FD0 LABEL2
D1 LABEL3

*1 Only lower 2 bytes are read. Data are not read from the specified devices HH, HL, and LH (upper 6 bytes).

5 FUNCTIONS
462 5.4 Details of Functions (For .NET Control)
■When data type equivalent to 2 words or more is specified for label
Example: Read data by specifying labels of Double Word, Float (Single Precision), Float (Double Precision), String*1, and
Time types.

*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.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Double Word D0
[1] LABEL2 Float (Single Precision) D100
[2] LABEL3 Float (Double Precision) D200
[3] LABEL4 String D300
[4] LABEL5 Time D400

⋅Number of read points: 27

⋅ Read device values 5
Upper 2 bytes Lower 2 bytes Applicable label
Not used (0 is stored.) D0 LABEL1
D1
D100 LABEL2
D101
D200 LABEL3
D201
D202
D203
D300 LABEL4
:
D316
D400 LABEL5
D401

■When array type label is specified

Example: Read data from the devices by specifying array type labels.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Bit (0..1) M0
[1] LABEL2 Word (0..1) CN200
[2] LABEL3 Double Word (0..1) D0

⋅Number of read points: 8

⋅ Read device values
Upper 2 bytes Lower 2 bytes Applicable label
Not used (0 is stored.) M0 LABEL1[0]
M1 LABEL1[1]
H of CN200 L of CN200 LABEL2[0]
H of CN201 L of CN201 LABEL2[1]
Not used (0 is stored.) D100 LABEL3[0]
D101
D102 LABEL3[1]
D103

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 463
 ■When long timer, long counter, or long retentive timer type is specified
Example: Read 3 points of data from LT0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL Long timer LT0
[1] LABEL Long timer LT1
[2] LABEL Long timer LT2

⋅Number of read points: 3

⋅ Read device values
Upper 2 bytes Lower 2 bytes Applicable label
H of LT0 L of LT0 LABEL[1]
H of LT1 L of LT1 LABEL[2]
H of LT2 L of LT2 LABEL[3]

■When structure type labels are specified

Example: Read data from the devices 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

⋅Number of read points: 6

⋅ Read device values
Upper 2 bytes Lower 2 bytes Applicable label
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.

5 FUNCTIONS
464 5.4 Details of Functions (For .NET Control)
■When labels in combination with structure and array are specified
Example: Read data from the devices by specifying structure type array and structure array type label.
⋅ Structure setting
Structure name Label name Data type
STRUCT1 L1 Bit
L2 Word
STRUCT2 L1 Bit (0..2)
L2 Double Word

⋅ Label setting
szLabelList Data type Label name Device
[0] LABEL1 STRUCT1(0..1) L1 X0
L2 D0
[1] LABEL2 STRUCT2 L1 M0
L2 D100
5
⋅Number of read points: 9
⋅ Read device values
Upper 2 bytes Lower 2 bytes Applicable label
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

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of read points is 0x7FFFFFFF.

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

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 465
 WriteDeviceRandom (Writing devices randomly)

Applicable controls
Applicable to the DotUtlType control.

Feature
Write devices randomly.

Format
■Visual Basic .NET
Ret = object.WriteDeviceRandom(szLabel, iSize, iData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of write points Input
Integer iData(n) Device value to be written Input

Ret = object.WriteDeviceRandom(szLabelList, iSize, iData)

Integer IRet Returned value Output
String szLabelList(n) Label list Input
Integer iSize Number of write points Input
Integer iData(n) Device value to be written Input

■Visual C++ .NET

iRet = object.WriteDeviceRandom(szLabel, iSize, iData)
int iRet Returned value Output
String^ szLabel Label name Input
int iSize Number of write points Input
array<int>^ iData Device value to be written Input

iRet = object.WriteDeviceRandom(szLabelList, iSize, iData)

int iRet Returned value Output
array<System::String ^>^ szLabelList Label list Input
int iSize Number of write points Input
array<int>^ iData Device value to be written Input

■Visual C# .NET
iRet = object.WriteDeviceRandom(ref szLabel, iSize, ref iData)
int iRet Returned value Output
String szLabel Label name Input
int iSize Number of write points Input
int[n] iData Device value to be written Input

iRet = object. WriteDeviceRandom (ref szLabelList, iSize, ref iData)

int iRet Returned value Output
System.String[n] szLabelList Label list Input
int iSize Number of write points Input
int[n] iData Device value to be written Input

Description
• Data of a device group for the size of iSize specified for the label name szLabel (szLabelList) are written.
• The device values to be written are stored in iData.
• For iData, reserve arrays for more than the amount specified for iSize.

5 FUNCTIONS
466 5.4 Details of Functions (For .NET Control)
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
Basic type Bit, Word, Double Word, Float (Single Precision), Float (Double Precision), String*1, String Label name
(Unicode)*1, Time, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive
timer
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]
Label name [n1] [n2] [n3]
Structure Label name
Structure member (The label data type can be specified in the same manner as the basic type.) Label name.Member name
Structured array Label name [number of
elements]
5
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
Label name [n1] [n2]
[n3].Element

*1 The maximum number of characters that can be specified is 32 + NULL.

■Number of write points

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
applicable words specified
Bit, Word 1 Number of label elements
Double Word, Float (Single Precision) 2 Number of label elements multiplied by 2
Float (Double Precision) 4 Number of label elements multiplied by 4
String 17 Number of label elements multiplied by
17
String (Unicode) 33 Number of label array elements multiplied
by 33
Time 2 Number of label elements multiplied by 2
Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer 1 Number of label elements

How to specify devices

Set the device values to be written as follows.

■When bit device and word device are specified

Example: Write data to each 1 point of M0 and D0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Bit M0
[1] LABEL2 Word D0

⋅ Number of write points: 2

⋅Device values to be written
Upper 2 bytes Lower 2 bytes Applicable label
Not used M0 LABEL1
D0 LABEL2

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 467
 ■When CN200 and later devices of FXCPU are specified
Example: Write 3 points of data to the devices including CN200.
For CN200 and later devices of FXCPU, 4 bytes are written as 1 read point.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Word D0
[1] LABEL2 Word CN200
[2] LABEL3 Word D1

⋅ Number of write points: 3

⋅Device values to be written
Upper 2 bytes Lower 2 bytes Applicable label
Not used D0 LABEL1
H of CN200 L of CN200 LABEL2
Not used D1 LABEL3

■When FD device is specified (4-word device)

Example: Write 3 points of data to the devices including FD0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Word D0
[1] LABEL2 Word FD0
[2] LABEL3 Word D1

⋅ Number of write points: 3

⋅Device values to be written
Upper 2 bytes Lower 2 bytes Applicable label
Not used D0 LABEL1
LL of FD0*1 LABEL2
D1 LABEL3

*1 Only lower 2 bytes can be set.

"0" is written to the specified devices HH, HL, and LH (upper 6 bytes).

5 FUNCTIONS
468 5.4 Details of Functions (For .NET Control)
■When data type equivalent to 2 words or more is specified for label
Example: Write data by specifying labels of Double Word, Float (Single Precision), Float (Double Precision), String*1, and
Time types.

*1
The number of points of characters to be written is 17 (32 characters + NULL).
The characters need to be converted in a user program because the characters of String type are not converted.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Double Word D0
[1] LABEL2 Float (Single Precision) D100
[2] LABEL3 Float (Double Precision) D200
[3] LABEL4 String D300
[4] LABEL5 Time D400

⋅ Number of write points: 27

⋅Device values to be written 5
Upper 2 bytes Lower 2 bytes Applicable label
Not used D0 LABEL1
D1
D100 LABEL2
D101
D200 LABEL3
D201
D202
D203
D300 LABEL4
:
D316
D400 LABEL5
D401

■Writing data to the devices by specifying array type labels

⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Bit (0..1) M0
[1] LABEL2 Word (0..1) CN200
[2] LABEL3 Double Word (0..1) D0

⋅ Number of write points: 8

⋅Device values to be written
Upper 2 bytes Lower 2 bytes Applicable label
Not used (0 is stored.) M0 LABEL1[0]
M1 LABEL1[1]
H of CN200 L of CN200 LABEL2[0]
H of CN201 L of CN201 LABEL2[1]
Not used D100 LABEL3[0]
D101
D102 LABEL3[1]
D103

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 469
 ■When long timer, long counter, or long retentive timer type is specified
Example: Write 3 points of data from LT0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL Long timer LT0
[1] LABEL Long timer LT1
[2] LABEL Long timer LT2

⋅ Number of write points: 3

⋅Device values to be written
Upper 2 bytes Lower 2 bytes Applicable label
H of LT0 L of LT0 LABEL[1]
H of LT1 L of LT1 LABEL[2]
H of LT2 L of LT2 LABEL[3]

■When structure type labels are specified

Example: Write data to the devices 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

⋅ Number of write points: 5

⋅Device values to be written
Upper 2 bytes Lower 2 bytes Applicable label
Not used D0.0 LABEL1.L1
D0 LABEL1.L2
D1
M0 LABEL2.L1
H of CN200 L of CN200 LABEL2.L2

5 FUNCTIONS
470 5.4 Details of Functions (For .NET Control)
■When labels in combination with structure and array are specified
Example: Write data to the devices by specifying structure type array and structure array type label.
⋅ Structure setting
Structure name Label name Data type
STRUCT1 L1 Bit
L2 Word
STRUCT2 L1 Bit (0..2)
L2 Double Word

⋅ Label setting
szLabelList Data type Label name Device
[0] LABEL1 STRUCT1(0..1) L1 X0
L2 D0
[1] LABEL2 STRUCT2 L1 M0
L2 D100
5
⋅ Number of write points: 9
⋅Device values to be written
Upper 2 bytes Lower 2 bytes Applicable label
Not used 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

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of write points is 0x7FFFFFFF.

• 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.
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• When a device which corresponds to the label name does not exist, an error occurs and data cannot be
written.
When any one of devices which correspond to multiple label names does not exist, an error occurs and data
cannot be written.
• Digit specified bit device and index setting cannot be used.
• If a Q motion CPU is accessed, an error is returned.
• 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.
• 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.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 471
 SetDevice (Set device data)

Applicable controls
Applicable to the DotUtlType control.

Feature
Set one point of device.

Format
■Visual Basic .NET
IRet = object.SetDevice(szLabel, iData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer iData Device value to be written Input

■Visual C++ .NET

iRet = object.SetDevice(szLabel, iData)
int iRet Returned value Output
String^ szLabel Label name Input
int iData Device value to be written Input

■Visual C# .NET
iRet = object.SetDevice(ref szLabel, iData)
int iRet Returned value Output
String szLabel Label name Input
int iData Device value to be written Input

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.

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
*1 *1 *1 *1
Basic type Bit, Word, Double Word , Float (Single Precision) , Float (Double Precision) , String , String Label name
(Unicode), Time*1, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer

*1 Only lower 2 bytes of start device can be written.

When writing 2 words or more of devices, use the WriteDeviceBlock function.
Note that when any of the following devices is specified, the upper 2 bytes are also written in Double Word type.
⋅ CN200 and later devices of FXCPU

5 FUNCTIONS
472 5.4 Details of Functions (For .NET Control)
How to specify devices
Set the device values to be written as follows.

■When bit device is specified

Example: Write data to M0.
⋅ Label setting
Data type Device
Bit M0

⋅Device values to be written

Upper 2 bytes Lower 2 bytes
Not used M0

■When word device is specified

Example: Write data to D0.
⋅ Label setting 5
Data type Device
Word D0

⋅Device values to be written

Upper 2 bytes Lower 2 bytes
Not used D0

■When CN200 or later device of FXCPU is specified

Example: Write data to CN200.
For CN200 and later devices of FXCPU, 4 bytes are written.
⋅ Label setting
Data type Device
Double Word CN200

⋅Device values to be written

Upper 2 bytes Lower 2 bytes
H of CN200 L of CN200

■When FD device is specified (4-word device)

Example: Write data by specifying FD0.
⋅ Label setting
Data type Device
Word FD0

⋅Device values to be written

Upper 2 bytes Lower 2 bytes
Not used LL of FD0*1

*1 Only lower 2 bytes can be set.

"0" is written to the specified devices HH, HL, and LH (upper 6 bytes).

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 473
 ■When data type equivalent to 2 words or more is specified for label
Example: Write data by specifying String type label.
⋅ Label setting
Data type Device
String D0

⋅Device values to be written

Upper 2 bytes Lower 2 bytes
Not used D0*1

*1 Only lower 2 bytes are written to the start device.

■When long timer, long counter, or long retentive timer type is specified
Example: Write data to LT0.
⋅ Label setting
Data type Device
Long timer LT0

⋅Device values to be written

Upper 2 bytes Lower 2 bytes
H of LT0 L of LT0

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• When a device which corresponds to the label name does not exist, an error occurs and data cannot be
written.
• When a Double Word device is specified at the time other than the digit specification for bit device and
specification of CN200 and later devices of FXCPU, this function writes data of lower 1 word (2 bytes), and
"0" is written to data of upper 1 word (2 bytes).
When writing Double Word devices, use the WriteDeviceRandom or the WriteDeviceBlock2 function.
• Digit specified bit device and index setting cannot be used.
• 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.

5 FUNCTIONS
474 5.4 Details of Functions (For .NET Control)
GetDevice (Acquiring device data)

Applicable controls
Applicable to the DotUtlType control.

Feature
Acquire one point of device.

Format
■Visual Basic .NET
IRet = object.GetDevice(szLabel, lData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer iData Read device value Output
5
■Visual C++ .NET
iRet = object.GetDevice(szLabel, iData)
int iRet Returned value Output
String^ szLabel Label name Input
int iData Read device value Output

■Visual C# .NET
iRet = object.GetDevice(ref szLabel, ref iData)
int iRet Returned value Output
String szLabel Label name Input
int iData Read device value Output

Description
• One point of device data specified for szLabel (label name)is stored in iData (read device values).

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
Basic type Bit, Word, Double Word*1, Float (Single Precision)*1, Float (Double Precision)*1, String*1, String Label name
(Unicode), Time*1, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer

*1 Only lower 2 bytes of start device can be read.

When reading 2 words or more of devices, use the ReadDeviceBlock function.
Note that when any of the following devices is specified, the upper 2 bytes are also read in Double Word type.
⋅CN200 or later device of FXCPU

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 475
 How to specify devices
The read device values are stored as follows.

■When bit device is specified

Example: Read data from M0.
⋅ Label setting
Data type Device
Bit M0

⋅ Read device values

Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) M0*1

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

■When word device is specified

Example: Read data from D0.
⋅ Label setting
Data type Device
Word D0

⋅ Read device values

Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) D0

■When CN200 or later device of FXCPU is specified

Example: Read data from CN200.
⋅ Label setting
Data type Device
Double Word CN200

⋅ Read device values

Upper 2 bytes Lower 2 bytes
H of CN200 L of CN200*1

*1 For CN200 and later devices of FXCPU, 4 bytes are read.

■When FD device is specified (4-word device)

Example: Read data by specifying FD0.
⋅ Label setting
Data type Device
Word FD0

⋅ Read device values

Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) LL of FD0*1

*1 Only lower 2 bytes are read. Data are not read from the specified devices HH, HL, and LH (upper 6 bytes).

5 FUNCTIONS
476 5.4 Details of Functions (For .NET Control)
■When data type equivalent to 2 words or more is specified for label
Example: Read data by specifying String type label.
⋅ Label setting
Data type Device
String D0

⋅ Read device values

Upper 2 bytes Lower 2 bytes
Not used (0 is stored.) D0*1

*1 Only lower 2 bytes are read to the start device.

■When long timer, long counter, or long retentive timer type is specified
Example: Read data to LT0.
⋅ Label setting
Data type Device
Long timer LT0 5
⋅ Read device values
Upper 2 bytes Lower 2 bytes
H of LT0 L of LT0

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• When a device which corresponds to the label name does not exist, an error occurs and data cannot be
read.
• For the read device values, reserve 4 bytes of memory area. If the memory area is not reserved, a critical
error (an application error or the like) may occur.
• Digit specified bit device and index setting cannot be used.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 477
 ReadBuffer (Reading data from buffer memory)

Applicable controls
Applicable to the DotUtlType control.

Feature
Read data from the buffer memory of special function module.

Format
■Visual Basic .NET
IRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, sData)
Integer IRet Returned value Output
Integer iStartIO Start I/O number of module from which values Input
are read
Integer iAddress Buffer memory address Input
Integer iReadSize Read size Input
Short sData(n) Values read from buffer memory Output

■Visual C++ .NET

iRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, sData)
int iRet Returned value Output
int iStartIO Start I/O number of module from which values Input
are read
int iAddress Buffer memory address Input
int iReadSize Read size Input
array<short>^ sData Values read from buffer memory Output

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

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.
For FX5CPU, specify the module number on the target station side.
• 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.
• When performing CPU COM communication with FXCPU as a connected station or GX Simulator communication, specify
the block number (0 to 7) of the special expansion equipment for the module's start I/O number and any value between 0
and 32767 for the buffer memory address.
• For sData, reserve arrays for more than the amount specified for iReadSize.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
478 5.4 Details of Functions (For .NET Control)
Considerations for reading/writing data from/to buffer memory in multiple CPU system
Any of the following errors occurs when the function is executed under the situation where the configured multiple CPU
system differs from the I/O assignment set in GX Developer.
Execute the function after checking the I/O assignment set in GX Developer and checking the I/O numbers of the module
from/to which values are read/written.
• An error occurs even when the function is executed after the correct I/O numbers are specified.
• When the specific I/O numbers (I/O numbers whose I/O assignment is actually wrong) are specified, data can be read from
buffer memory normally, but an error (error code: 0x010A4030, 0x010A4042, etc.) occurs when data are written to the
buffer memory.
• Though a programmable controller CPU error (parameter error, SP. UNIT LAY ERR, etc.) does not occur in the multiple
CPU system, an error occurs in the user application when the function is executed.

• If an R motion CPU, or Q motion CPU is accessed, an error will be returned.

• For sData, reserve a memory area for the number of points specified for iReadSize. 5
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• 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).
• For the availability of communication routes, refer to the table in Page 387 ReadBuffer (Reading data
from buffer memory).

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 479
 WriteBuffer (Write data to buffer memory.)

Applicable controls
Applicable to the DotUtlType control.

Feature
Write data to the buffer memory of special function module.

Format
■Visual Basic .NET
IRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, sData)
Integer IRet Returned value Output
Integer iStartIO Start I/O number of module to where Input
values will be written
Integer iAddress Buffer memory address Input
Integer iWriteSize Write size Input
Short sData(n) Values written from buffer memory Input

■Visual C++ .NET

iRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, sData)
int iRet Returned value Output
int iStartIO Start I/O number of module to where Input
values will be written
int iAddress Buffer memory address Input
int iWriteSize Write size Input
array<short>^ sData Values written from buffer memory Input

■Visual C# .NET
iRet = object. WriteBuffer (iStartIO, iAddress, iWriteSize, sData)
int iRet Returned value Output
int iStartIO Start I/O number of module to where Input
values will be written
int iAddress Buffer memory address Input
int iWriteSize Write size Input
short[n] sData Values written from buffer memory Input

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.
For FX5CPU, specify the module number on the target station side.
• 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.
• When performing CPU COM communication with FXCPU as a connected station or GX Simulator communication, specify
the block number (0 to 7) of the special expansion equipment for the module's start I/O number and any value between 0
and 32767 for the buffer memory address.
• For sData, reserve arrays for more than the amount specified for iWriteSize.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
480 5.4 Details of Functions (For .NET Control)
Considerations for reading/writing data from/to buffer memory in multiple CPU system
Any of the following errors occurs when the function is executed under the situation where the configured multiple CPU
system differs from the I/O assignment set in GX Developer.
Execute the function after checking the I/O assignment set in GX Developer and checking the I/O numbers of the module
from/to which the values are read/written.
• An error occurs even when the function is executed after the correct I/O numbers are specified.
• When the specific I/O numbers (I/O numbers whose I/O assignment is actually wrong) are specified, data can be read from
buffer memory normally, but an error (error code: 0x010A4030, 0x010A4042, etc.) occurs when data are written to the
buffer memory.
• Though a programmable controller CPU error (parameter error, SP. UNIT LAY ERR, etc.) does not occur in the multiple
CPU system, an error occurs in the user application when the function is executed.

• If an R motion CPU, or Q motion CPU is accessed, an error will be returned.

• For sData, reserve a memory area for the number of points specified for iWriteSize. 5
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• 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).
• For the availability of communication routes, refer to the table in Page 392 WriteBuffer (Writing data to
buffer memory).

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 481
 GetClockData (Reading clock data)

Applicable controls
Applicable to the DotUtlType control.

Feature
Read clock data from a programmable controller CPU.

Format
■Visual Basic .NET
IRet = object.GetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
Integer IRet Returned value Output
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++ .NET

iRet = object.GetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
int iRet Returned value Output
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# .NET
hResult = object.GetClockData
(ref sYear, ref sMonth, ref sDay, ref sDayOfWeek,ref sHour, ref sMinute, ref sSecond)
int iRet Returned value Output
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

5 FUNCTIONS
482 5.4 Details of Functions (For .NET Control)
Description
• An error is returned when the correct clock data is not set to the programmable controller CPU.
• The values stored in sYear are: four digits of the year for RCPU and QCPU (Q mode) and last two digits of the year for any
other CPUs.
Note that the applicable years for RCPU and QCPU (Q mode) are from 1980 to 2079.
• The values stored in sDayOfWeek are as follows.
Value Day of Week
0 Sunday
1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5 Friday
6 Saturday
5
Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• If an R motion CPU, or Q motion CPU is accessed, an error will be returned.

• The clock data can be read from FXCPUs with the built-in clock or FXU/FX2C/FX2NC with the RTC
cassette.
An error is returned when the clock data is read from an FXCPU other than the ones described above.
• Note that an error of transfer time may occur in clock setting.
• For the availability of communication routes, refer to the table in Page 396 GetClockData (Reading
clock data).

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 483
 SetClockData (Writing clock data)

Applicable controls
Applicable to the DotUtlType control.

Feature
Write clock data to a programmable controller CPU.

Format
■Visual Basic .NET
IRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
Integer IRet Returned value Output
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++ .NET

iRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
int iRet Returned value Output
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# .NET
lRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
int iRet Returned value Output
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

5 FUNCTIONS
484 5.4 Details of Functions (For .NET Control)
Description
• An error is returned when the clock data to be set are not correct values.
• The applicable values to be specified for sYear are: four digits of the year for RCPU and QCPU (Q mode) and last two digits
of the year for any other CPUs.
Note that the applicable years for RCPU and QCPU (Q mode) are from 1980 to 2079.
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
0 Sunday
1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5
6
Friday
Saturday
5

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• If an R motion CPU, or Q motion CPU is accessed, an error will be returned.

• The clock data can be read from FXCPUs with the built-in clock or FXU/FX2C/FX2NC with the RTC
cassette.
An error is returned when the clock data is read from an FXCPU other than the ones described above.
• Note that an error of transfer time may occur in clock setting.
• For the availability of communication routes, refer to the table in Page 400 SetClockData (Writing clock
data).
• An error is returned when the own board is accessed.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 485
 GetCpuType (Reading programmable controller CPU model)

Applicable controls
Applicable to the DotUtlType control.

Feature
Read the model character string and the model code of programmable controller CPU, network board, and GOT.

Format
■Visual Basic .NET
IRet = object.GetCpuType(szCpuName, ICpuType)
Integer IRet Returned value Output
String szCpuName Programmable controller CPU model Output
character string
Integer ICpuType Programmable controller CPU model Output
code

■Visual C++ .NET

iRet = object.GetCpuType (szCpuName, iCpuType)
int iRet Returned value Output
String^ szCpuName Programmable controller CPU model Output
character string
int iCpuType Programmable controller CPU model Output
code

■Visual C# .NET
iRet = object.GetCpuType (ref szCpuName, ref iCpuType)
int iRet Returned value Output
String szCpuName Programmable controller CPU model Output
character string
int iCpuType Programmable controller CPU model Output
code

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 404 GetCpuType (Reading programmable controller CPU model).

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
486 5.4 Details of Functions (For .NET Control)
SetCpuStatus (Remote control)

Applicable controls
Applicable to the DotUtlType control.

Feature
Perform a remote operation of programmable controller CPU.

Format
■Visual Basic .NET
IRet = object.SetCpuStatus(IOperation)
Integer IRet Returned value Output
Integer IOperation Remote RUN/STOP/PAUSE Input

■Visual C++ .NET 5

iRet = object.SetCpuStatus (iOperation)
int iRet Returned value Output
int iOperation Remote RUN/STOP/PAUSE Input

■Visual C# .NET
iRet = object.SetCpuStatus (iOperation)
int iRet Returned value Output
int iOperation Remote RUN/STOP/PAUSE Input

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

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• Since FXCPU or FX5CPU does not have the PAUSE switch as a programmable controller CPU, an error is
returned if a remote pause operation is specified using the SetCpuStatus function.
• If a Q motion CPU is accessed and PAUSE is specified, an error is returned.
• For the availability of communication routes, refer to the table in Page 408 SetCpuStatus (Remote
control).
• If an R motion CPU is accessed, an error is returned.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 487
 EntryDeviceStatus (Registering devices for status monitoring)

Applicable controls
Applicable to the DotUtlType control.

Feature
Register devices whose status to be monitored.

Format
■Visual Basic .NET
IRet = object.EntryDeviceStatus(szLabelList, iSize, iMonitorCycle, iData)
Integer IRet Returned value Output
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++ .NET

iRet = object.EntryDeviceStatus(szLabelList, iSize, iMonitorCycle, iData)
int iRet Returned value Output
array<System::String ^>^ szLabelList Registered label name list Input
int iSize Number of registered device points Input
int iMonitorCycle Status monitoring time interval Input
array<int>^ iData Registered device value list Input

■Visual C# .NET
iRet = object. EntryDeviceStatus(szLabelList, iSize, iMonitorCycle, iData)
int iRet Returned value Output
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

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 application is executed.
• maximum number of device points that can be specified for iSize is 20 points.
• 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.

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
Basic type Bit, Word Label name

5 FUNCTIONS
488 5.4 Details of Functions (For .NET Control)
How to specify devices
Set the device values to be registered as follows.

■When bit device and word device are specified

Example: Register 1 point of M0 and D0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Bit M0
[1] LABEL2 Word D0

⋅Number of registered device points: 2

⋅Registered device values
Upper 2 bytes Lower 2 bytes
Not used M0
D0
5
■When CN200 and later devices of FXCPU are specified
Example: Register 3 points of devices including CN200.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Word D0
[1] LABEL2 Word CN200
[2] LABEL3 Word D1

⋅Number of registered device points: 3

⋅Registered device values
Upper 2 bytes Lower 2 bytes
Not used D0
H of CN200 L of CN200*1
Not used D1

*1 For CN200 and later devices of FXCPU, 4 bytes can be registered.

■When FD device is specified (4-word device)

Example: Register 3 points of data from FD0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Word D0
[1] LABEL2 Word FD0
[2] LABEL3 Word D1

⋅Number of registered device points: 3

⋅Registered device values
Upper 2 bytes Lower 2 bytes
Not used D0
LL of FD0*1
D1

*1 Only lower 2 bytes can be registered. The specified devices HH, HL, and LH (upper 6 bytes) cannot be registered.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 489
 Considerations for checking the 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
bytes.
(Example) When checking the D0 status for "-10"
Set the value "65526 (0000FFF6H)" where "0" is stored in the upper 2 bytes 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 section.
Page 585 Programming Examples for Monitoring Word Device Status

• 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. If the memory area is not
reserved, a critical error (an application error or the like) may occur.
• 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.
• Digit specified bit device and index setting cannot be used.

5 FUNCTIONS
490 5.4 Details of Functions (For .NET Control)
FreeDeviceStatus (Deregistering devices for status monitoring)

Applicable controls
Applicable to the DotUtlType control.

Feature
Deregister devices that are registered using the EntryDeviceStatus function to monitor their status.

Format
■Visual Basic .NET
IRet = object.FreeDeviceStatus()
Integer IRet Returned value Output

■Visual C++ .NET

iRet = object. FreeDeviceStatus()
5
int iRet Returned value Output

■Visual C# .NET
iRet = object. FreeDeviceStatus()
int iRet Returned value Output

Description
The devices that are set using the EntryDeviceStatus function to monitor their status are deregistered.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 491
 OnDeviceStatus (Event notification)

Applicable controls
Applicable to the DotUtlType control.

Feature
Execute the event notification when the device condition registered using the EntryDeviceStatus function is satisfied.

Format
■Visual Basic .NET
Private Sub object_OnDeviceStatus(sender, e)
ByVal sender As System.Object Event occurrence Input
source
ByVal e As objectLib_IobjectIFEvents_OnDeviceStatusEvent Event data Input
The following are the members of e.
e.szLabel Name of label whose condition is satisfied
e.lData Value of device whose condition is satisfied
e.lReturnCode Returned value of condition check processing

■Visual C++ .NET

private: System::Void objectIF_OnDeviceStatus (*sender, e)
System::Object *sender Event occurrence Input
source
objectLib::objectIF_OnDeviceStatusEvent* e Event data Input
The following are the members of e.
e->szLabel Name of label whose condition is satisfied
e->lData Value of device whose condition is satisfied
e->lReturnCode Returned value of condition check processing

■Visual C# .NET
private void object_OnDeviceStatus(object sender, object.DeviceStatusEventArgs e)
sender Event occurrence output
source
e Event data output
The following are the members of e.
e->szLabel Name of label whose condition is satisfied
e->lData Value of device whose condition is satisfied
e->lReturnCode Returned value of condition check processing

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

5 FUNCTIONS
492 5.4 Details of Functions (For .NET Control)
Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

When any of the following settings is set in the user application, 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.
• User applications created using Visual Basic .NET
The message box is displayed in the user application.
The InputBox/OutputBox is displayed in the user application.
• User applications created using Visual Basic .NET, Visual C++ .NET and Visual C# .NET
The Sleep processing, WaitForSingleObject function, or similar standby function is used in the user
application. 5

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 493
 ReadDeviceBlock2 (Reading devices in bulk)

Applicable controls
Applicable to the DotUtlType control.

Feature
Read devices in 2-byte data unit in bulk.

Format
■Visual Basic .NET
IRet = object.ReadDeviceBlock2(szLabel, iSize, sData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of read points Input
Short sData(n) Read device value Output

■Visual C++ .NET

iRet = object.ReadDeviceBlock2(szLabel, iSize, sData)
int iRet Returned value Output
String^ szLabel Label name Input
int iSize Number of read points Input
array<short>^ sData Read device value Output

■Visual C# .NET
iRet = object.ReadDeviceBlock2(ref szLabel, iSize, ref sData)
int iRet Returned value Output
String szLabel Label name Input
int iSize Number of read points Input
short[n] sData Read device value Output

Description
• The devices for the amount specified for iSize (number of read points) are read in bulk 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.

5 FUNCTIONS
494 5.4 Details of Functions (For .NET Control)
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
Array Label name
Array member Bit, Word, Double Word, Float (Single Precision), Float (Double Precision), String*1, String Label name [number of
(Unicode)*1, Time, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive elements]
timer Label name [n1] [n2] [n3]

*1 The maximum number of characters that can be specified is 32 + NULL.

■Number of read points

Set the following values for the number of read points according to the label data type.
Label (array) data type Number of Number of read points to be
applicable words specified 5
Bit 1 Number of label array elements divided
by 16 (rounded up)
Word 1 Number of label array elements
Double Word, Float (Single Precision) 2 Number of label array elements multiplied
by 2
Float (Double Precision) 4 Number of label array elements multiplied
by 4
String 17 Number of label array elements multiplied
by 17
String (Unicode) 33 Number of label array elements multiplied
by 33
Time 2 Number of label array elements multiplied
by 2
Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer 1 Number of label array elements

How to specify devices

The read device values are stored as follows.

■When bit device is specified

Example: Read 3 points of data (3 words = 48 bits) from the devices starting from M0.
⋅ Label setting (Data type: Bit, Number of array elements: 48)
Data type Device
Bit (0..47) M0

⋅Number of read points: 3

⋅ Read device values
2 Bytes
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.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 495
 ■When word device is specified
Example: Read 3 points of data from the devices starting from D0.
⋅Label setting (Data type: Word, Number of array elements: 3)
Data type Device
Word (0..2) D0

⋅Number of read points: 3

⋅ Read device values
2 Bytes
D0
D1
D2

■When CN200 and later devices of FXCPU are specified

Example: Read 6 points 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 (Data type: Double Word, Number of array elements: 3)
Data type Device
Double Word (0..2) CN200

⋅Number of read points: 6

⋅ Read device values
2 Bytes
L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

■When FD device is specified (4-word device)

Example: Read 8 points of data from the devices starting from FD0.
⋅Label setting (Data type: Double Word, Number of array elements: 2)
Data type Device
Double Word (0..1) FD0

⋅Number of read points: 8

⋅ Read device values
2 Bytes
LL of FD0
LH of FD0
HL of FD0
HH of FD0
LL of FD1
LH of FD1
HL of FD1
HH of FD1

5 FUNCTIONS
496 5.4 Details of Functions (For .NET Control)
■When label is Double Word array and word device is specified
Example: Read 6 points of data from the devices starting from D100.
⋅Label setting (Data type: Double Word, Number of array elements: 3)
Data type Device
Double Word (0..2) D100

⋅Number of read points: 6

⋅ Read device values
2 Bytes
D100
D101
D102
D103
D104
D105
5
Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of read points should be the value which satisfies the following condition.
Read start device number + Number of read points ≤ Last device number
• 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.
• 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.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 497
 WriteDeviceBlock2 (Writing devices in bulk)

Applicable controls
Applicable to the DotUtlType control.

Feature
Write devices in 2-byte data unit in bulk.

Format
■Visual Basic .NET
IRet = object.WriteDeviceBlock2(szLabel, iSize, sData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of write points Input
Short sData(n) Device value to be written Input

■Visual C++ .NET

iRet = object.WriteDeviceBlock2(szLabel, iSize, sData)
int iRet Returned value Output
String^ szLabel Label name Input
int iSize Number of write points Input
array<short>^ sData Device value to be written Input

■Visual C# .NET
iRet = object.WriteDeviceBlock2(ref szLabel, iSize, sData)
int iRet Returned value Output
String szLabel Label name Input
int iSize Number of write points Input
short[n] sData Device value to be written Input

Description
• The devices for the amount specified for iSize (number of write points) are written in bulk starting from the device specified
for szLabel (label name).
• Store the device values to be written in sData.
• For sData, reserve arrays for more than the amount specified for iSize.

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
Array Label name
*1
Array member Bit, Word, Double Word, Float (Single Precision), Float (Double Precision), String , String Label name [number of
(Unicode)*1, Time, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer elements]
Label name [n1] [n2] [n3]

*1 The maximum number of characters that can be specified is 32 + NULL.

5 FUNCTIONS
498 5.4 Details of Functions (For .NET Control)
■Number of write points
Set the following values for the number of write points according to the label data type.
Label (array) data type Number of Number of write points to be
applicable words specified
Bit 1 Number of label array elements divided
by 16 (rounded up)
Word 1 Number of label array elements
Double Word, Float (Single Precision) 2 Number of label array elements multiplied
by 2
Float (Double Precision) 4 Number of label array elements multiplied
by 4
String 17 Number of label array elements multiplied
by 17
String (Unicode) 33 Number of label array elements multiplied
by 33
Time 2 Number of label array elements multiplied
by 2 5
Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer 1 Number of label array elements

How to specify devices

Set the device values to be written as follows.

■When bit device is specified

Example: Write 3 points of data (3 words = 48 bits) to the devices starting from M0.
⋅ Label setting (Data type: Bit, Number of array elements: 48)
Data type Device
Bit (0..47) M0

⋅ Number of write points: 3

⋅Device values to be written
2 Bytes
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 word device is specified

Example: Write 3 points of data to the devices starting from D0.
⋅Label setting (Data type: Word, Number of array elements: 3)
Data type Device
Word (0..2) D0

⋅ Number of write points: 3

⋅Device values to be written
2 Bytes
D0
D1
D2

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 499
 ■When CN200 and later devices of FXCPU are specified
Example: Write 6 points 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.
⋅Label setting (Data type: Double Word, Number of array elements: 3)
Data type Device
Double Word (0..2) CN200

⋅ Number of write points: 6

⋅Device values to be written
2 Bytes
L of CN200
H of CN200
L of CN201
H of CN201
L of CN202
H of CN202

■When FD device is specified (4-word device)

⋅Label setting (Data type: Double Word, Number of array elements: 2)
Data type Device
Double Word (0..1) FD0

⋅ Number of write points: 8

⋅Device values to be written
2 Bytes
LL of FD0
LH of FD0
HL of FD0
HH of FD0
LL of FD1
LH of FD1
HL of FD1
HH of FD1

■When label is Double Word array and word device is specified

Example: Write 6 points of data to the devices starting from D100.
⋅Label setting (Data type: Double Word, Number of array elements: 3)
Data type Device
Double Word (0..2) D100

⋅ Number of write points: 6

⋅Device values to be written
2 Bytes
D100
D101
D102
D103
D104
D105

5 FUNCTIONS
500 5.4 Details of Functions (For .NET Control)
Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of write points should be the value which satisfies the following condition.
Write starting device number + Number of write points ≤ Last device number
• When specifying bit type array labels, 0 or a multiple of 16 can be specified as a device number.
• 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.
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• When a device which corresponds to the label name does not exist, an error occurs and data cannot be
written. 5
When any one of devices which correspond to multiple label names does not exist, an error occurs and data
cannot be written.
• Digit specified bit device and index setting cannot be used.
• WriteDeviceBlock or WriteDeviceBlock2 cannot be used for writing long timer device (LT) and retentive long
timer device (LST).
Use WriteDeviceRandom, WriteDeviceRandom2, SetDevice or SetDevice2.
• 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.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 501
 ReadDeviceRandom2 (Reading devices randomly)

Applicable controls
Applicable to the DotUtlType control.

Feature
Read devices in 2-byte data unit randomly.

Format
■Visual Basic .NET
IRet = object.ReadDeviceRandom2(szLabel, iSize, sData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of read points Input
Short sData(n) Read device value Output

IRet = object.ReadDeviceRandom2(szLabelList, iSize, sData)

Integer IRet Returned value Output
String szLabelList(n) Label list Input
Integer iSize Number of read points Input
Short sData(n) Read device value Output

■Visual C++ .NET

iRet = object.ReadDeviceRandom2(szLabel, iSize, sData)
Int iRet Returned value Output
String^ szLabel Label name Input
int iSize Number of read points Input
array<short>^ sData Read device value Output

iRet = object.ReadDeviceRandom2(szLabelList, iSize, sData)

Int iRet Returned value Output
array<System::String^>^ szLabelList Label list Input
int iSize Number of read points Input
array<short>^ sData Read device value Output

■Visual C# .NET
iRet = object.ReadDeviceRandom2(ref szLabel, iSize, ref sData)
Int iRet Returned value Output
String szLabel Label name Input
int iSize Number of read points Input
short[n] sData Read device value Output

iRet = object.ReadDeviceRandom2(ref szLabelList, iSize, ref sData)

Int iRet Returned value Output
System.String[n] szLabelList Label list Input
int iSize Number of read points Input
short[n] sData Read device value Output

Description
• Data of a device group for the size of iSize specified for the label name szLabel (szLabelList) are read.
• The read device values are stored in sData.
• For sData, reserve arrays for more than the amount specified for iSize.

5 FUNCTIONS
502 5.4 Details of Functions (For .NET Control)
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
Basic type Bit, Word, Double Word, Float (Single Precision), Float (Double Precision), String*1, String Label name
(Unicode)*1, Time, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive
timer
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]
Label name [n1] [n2] [n3]
Structure Label name
Structure member (The label data type can be specified in the same manner as the basic type.) Label name.Member name
Structured array Label name [number of
elements]
5
Structured array member (The label data type can be specified in the same manner as the basic type.) Label name [number of
elements].Member
Label name [n1] [n2]
[n3].Element

*1 The maximum number of characters that can be specified is 32 + NULL.

■Number of read points

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
applicable words specified
Bit, Word 1 Number of label elements
Double Word, Float (Single Precision) 2 Number of label elements multiplied by 2
Float (Double Precision) 4 Number of label elements multiplied by 4
String 17 Number of label elements multiplied by
17
String (Unicode) 33 Number of label array elements multiplied
by 33
Time 2 Number of label elements multiplied by 2
Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer 1 Number of label elements

How to specify devices

The read device values are stored as follows.

■When bit device and word device are specified

Example: Read data from each 1 point of M0 and D0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Bit M0
[1] LABEL2 Word D0

⋅Number of read points: 2

⋅ Read device values
2 Bytes Applicable label
*1
M0 LABEL1
D0 LABEL2

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

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 503
 ■When CN200 and later devices of FXCPU are specified
Example: Read 3 points of data from the devices including CN200.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Word D0
[1] LABEL2 Word CN200
[2] LABEL3 Word D1

⋅Number of read points: 3

⋅ Read device values
2 Bytes Applicable label
D0 LABEL1
L of CN200*1 LABEL2
D1 LABEL3

*1 Only lower 2 bytes are read. Data are not read from the specified device H (upper 2 bytes).

■When FD device is specified (4-word device)

Example: Read 3 points of data from the devices including FD0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Word D0
[1] LABEL2 Word FD0
[2] LABEL3 Word D1

⋅Number of read points: 3

⋅ Read device values
2 Bytes Applicable label
D0 LABEL1
LL of FD0*1 LABEL2
D1 LABEL3

*1 Only lower 2 bytes are read. Data are not read from the specified devices HH, HL, and LH (upper 6 bytes).

5 FUNCTIONS
504 5.4 Details of Functions (For .NET Control)
■When data type equivalent to 2 words or more is specified for label
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
[0] LABEL1 Double Word D0
[1] LABEL2 Float (Single Precision) D100
[2] LABEL3 Float (Double Precision) D200
[3] LABEL4 String D300
[4] LABEL5 Time D400

⋅Number of read points: 27

⋅ Read device values
2 Bytes Applicable label
D0 LABEL1
D1
5
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.

■When array type label is specified

Example: Read data from the devices by specifying array type labels.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Bit (0..1) M0
[1] LABEL2 Word (0..1) CN200
[2] LABEL3 Double Word (0..1) D0

⋅Number of read points: 8

⋅ Read device values
2 Bytes Applicable label
M0 LABEL1[0]
M1 LABEL1[1]
L of CN200 LABEL2[0]
L of CN201 LABEL2[1]
D100 LABEL3[0]
D101
D102 LABEL3[1]
D103

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 505
 ■When structure type labels are specified
Example: Read data from the devices 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

⋅Number of read points: 6

⋅ Read device values
2 Bytes Applicable label
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.

■When labels in combination with structure and array are specified

Example: Read data from the devices by specifying structure type array and structure array type label.
⋅ Structure setting
Structure name Label name Data type
STRUCT1 L1 Bit
L2 Word
STRUCT2 L1 Bit (0..2)
L2 Double Word

⋅ Label setting
szLabelList Data type Label name Device
[0] LABEL1 STRUCT1(0..1) L1 X0
L2 D0
[1] LABEL2 STRUCT2 L1 M0
L2 D100

⋅Number of read points: 9

⋅ Read device values
2 Bytes Applicable label
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

5 FUNCTIONS
506 5.4 Details of Functions (For .NET Control)
Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of read points is 0x7FFFFFFF.

• 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.
• 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. 5
• When a Double Word device is specified, only the data of the lower 1 word (2 bytes) are stored using this
function.(An error does not occur.)
When reading data from a Double Word device, use the ReadDeviceRandom function or the
ReadDeviceBlock2 function.
• Digit specified bit device and index setting cannot be used.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 507
 WriteDeviceRandom2 (Writing devices randomly)

Applicable controls
Applicable to the DotUtlType control.

Feature
Write devices in 2-byte data unit randomly.

Format
■Visual Basic .NET
Ret = object.WriteDeviceRandom2(szLabel, iSize, sData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of write points Input
Short sData(n) Device value to be written Input

Ret = object.WriteDeviceRandom2(szLabelList, iSize, sData)

Integer IRet Returned value Output
String szLabelList(n) Label list Input
Integer iSize Number of write points Input
Short sData(n) Device value to be written Input

■Visual C++ .NET

iRet = object.WriteDeviceRandom2(szLabel, iSize, sData)
int iRet Returned value Output
String^ szLabel Label name Input
int iSize Number of write points Input
array<short>^ sData Device value to be written Input

iRet = object.WriteDeviceRandom2(szLabelList, iSize, sData)

int iRet Returned value Output
array<System::String^>^ szLabelList Label list Input
int iSize Number of write points Input
array<short>^ sData Device value to be written Input

■Visual C# .NET
iRet = object.WriteDeviceRandom2(szLabel, iSize, sData)
int iRet Returned value Output
String szLabel Label name Input
int iSize Number of write points Input
short[n] sData Device value to be written Input

iRet = object. WriteDeviceRandom2 (szLabelList, iSize, sData)

int iRet Returned value Output
System.String[n] szLabelList Label list Input
int iSize Number of write points Input
short[n] sData Device value to be written Input

Description
• Data of a device group for the size of iSize specified for the label name szLabel are written.
• Store the device values to be written in sData.
• For sData, reserve arrays for more than the amount specified for iSize.

5 FUNCTIONS
508 5.4 Details of Functions (For .NET Control)
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
Basic type Bit, Word, Double Word, Float (Single Precision), Float (Double Precision), String*1, String Label name
(Unicode)*1, Time, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive
timer
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]
Label name [n1] [n2] [n3]
Structure Label name
Structure member (The label data type can be specified in the same manner as the basic type.) Label name.Member name
Structured array Label name [number of
elements]
5
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
Label name [n1] [n2]
[n3].Element

*1 The maximum number of characters that can be specified is 32 + NULL.

■Number of write points

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
applicable words specified
Bit, Word 1 Number of label elements
Double Word, Float (Single Precision) 2 Number of label elements multiplied by 2
Float (Double Precision) 4 Number of label elements multiplied by 4
String 17 Number of label elements multiplied by
17
String (Unicode) 33 Number of label array elements multiplied
by 33
Time 2 Number of label elements multiplied by 2
Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer 1 Number of label elements

How to specify devices

Set the device values to be written as follows.

■When bit device and word device are specified

Example: Write data to each 1 point of M0 and D0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Bit M0
[1] LABEL2 Word D0

⋅ Number of write points: 2

⋅Device values to be written
2 Bytes
M0*1
D0

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

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 509
 ■When CN200 and later devices of FXCPU are specified
Example: Write 3 points of data to the devices including CN200.
4 bytes are written as 1 point for CN200 and later devices of FXCPU.
Only lower 2 bytes can be set.
"0" is written to the specified device H (upper 2 bytes).
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Word D0
[1] LABEL2 Word CN200
[2] LABEL3 Word D1

⋅ Number of write points: 3

⋅Device values to be written
2 Bytes Applicable label
D0 LABEL1
L of CN200 LABEL2
D1 LABEL3

■When FD device is specified (4-word device)

Example: Write 3 points of data to the devices including FD0.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Word D0
[1] LABEL2 Word FD0
[2] LABEL3 Word D1

⋅ Number of write points: 3

⋅Device values to be written
2 Bytes Applicable label
D0 LABEL1
LL of FD0*1 LABEL2
D1 LABEL3

*1 Only lower 2 bytes can be set.

"0" is written to the specified devices HH, HL, and LH (upper 6 bytes).

5 FUNCTIONS
510 5.4 Details of Functions (For .NET Control)
■When data type equivalent to 2 words or more is specified for label
Example: Write data by specifying labels of Double Word, Float (Single Precision), Float (Double Precision), String*1, and
Time types.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Double Word D0
[1] LABEL2 Float (Single Precision) D100
[2] LABEL3 Float (Double Precision) D200
[3] LABEL4 String D300
[4] LABEL5 Time D400

⋅ Number of write points: 27

⋅Device values to be written
2 Bytes Applicable label
D0 LABEL1
D1
5
D100 LABEL2
D101
D200 LABEL3
D201
D202
D203
D300 LABEL4
:
D316*1
D400 LABEL5
D401

*1 The number of points of characters to be written is 17 (32 characters + NULL).

The characters need to be converted in a user program because the characters of String type are not converted.

■When array type label is specified

Example: Write data to the devices by specifying array type labels.
⋅ Label setting
szLabelList Data type Device
[0] LABEL1 Bit (0..1) M0
[1] LABEL2 Word (0..1) CN200
[2] LABEL3 Double Word (0..1) D0

⋅ Number of write points: 8

⋅Device values to be written
2 Bytes Applicable label
M0 LABEL1[0]
M1 LABEL1[1]
L of CN200 LABEL2[0]
L of CN201 LABEL2[1]
D100 LABEL3[0]
D101
D102 LABEL3[1]
D103

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 511
 ■When structure type labels are specified
Example: Write data to the devices 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

⋅ Number of write points: 5

⋅Device values to be written
2 Bytes Applicable label
D0.0 LABEL1.L1
D0 LABEL1.L2
D1
M0 LABEL2.L1
L of CN200 LABEL2.L2

■When labels in combination with structure and array are specified

Example: Write data to the devices by specifying structure type array and structure array type label.
⋅ Structure setting
Structure name Label name Data type
STRUCT1 L1 Bit
L2 Word
STRUCT2 L1 Bit (0..2)
L2 Double Word

⋅ Label setting
szLabelList Data type Label name Device
[0] LABEL1 STRUCT1(0..1) L1 X0
L2 D0
[1] LABEL2 STRUCT2 L1 M0
L2 D100

⋅ Number of write points: 9

⋅Device values to be written
2 Bytes Applicable label
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

5 FUNCTIONS
512 5.4 Details of Functions (For .NET Control)
Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• The maximum number of write points is 0x7FFFFFFF.

• 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.
If the memory area is not reserved, a critical error (an application error or the like) may occur.
• When a device which corresponds to the label name does not exist, an error occurs and data cannot be
written.
When any one of devices which correspond to multiple label names does not exist, an error occurs and data
cannot be written. 5
• When a Double Word device is specified, this function writes data of lower 1 word (2 bytes), and "0" is
written to data of upper 1 word (2 bytes).
When writing Double Word devices, use the WriteDeviceRandom or the WriteDeviceBlock2 function.
• Digit specified bit device and index setting cannot be used.
• If a Q motion CPU is accessed, an error is returned.
• 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.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 513
 SetDevice2 (Set device data)

Applicable controls
Applicable to the DotUtlType control.

Feature
Set one point of device in 2-byte data unit.

Format
■Visual Basic .NET
IRet = object.SetDevice2(szLabel, sData)
Integer IRet Returned value Output
String szLabel Label name Input
Short sData Device value to be written Input

■Visual C++ .NET

iRet = object.SetDevice2(szLabel, sData)
int iRet Returned value Output
String^ szLabel Label name Input
short sData Device value to be written Input

■Visual C# .NET
iRet = object.SetDevice2(ref szLabel, sData)
int iRet Returned value Output
String szLabel Label name Input
short sData Device value to be written Input

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.

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
Basic type Bit, Word, Double Word*1, Float (Single Precision)*1, Float (Double Precision)*1, String*1, String (Unicode), Label name
Time*1, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer

*1 Only lower 2 bytes of start device can be written.

When writing 2 words or more of devices, use the WriteDeviceBlock2 function.

5 FUNCTIONS
514 5.4 Details of Functions (For .NET Control)
How to specify devices
Set the device values to be written as follows.

■When bit device is specified

Example: Write data to M0.
⋅ Label setting
Data type Device
Bit M0

⋅Device values to be written

2 Bytes
M0*1

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

■When word device is specified 5

Example: Write data to D0.
⋅ Label setting
Data type Device
Word D0

⋅Device values to be written

2 Bytes
D0

■When CN200 or later device of FXCPU is specified

Example: Write data to CN200.
For CN200 and later devices of FXCPU, 4 bytes are written.
Only lower 2 bytes can be set.
"0" is written to the specified device H (upper 2 bytes).
⋅ Label setting
Data type Device
Double Word CN200

⋅Device values to be written

2 Bytes
L of CN200

■When FD device is specified (4-word device)

Example: Write data by specifying FD0.
⋅ Label setting
Data type Device
Word FD0

⋅Device values to be written

2 Bytes
LL of FD0*1

*1 Only lower 2 bytes are written. Data cannot be written to the specified devices HH, HL, and LH (upper 6 bytes).

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 515
 ■When data type equivalent to 2 words or more is specified for label
Example: Write data by specifying String type label.
⋅ Label setting
Data type Device
String D0

⋅Device values to be written

2 Bytes
D0*1

*1 Only lower 2 bytes are written to the start device.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

• When a device which corresponds to the label name does not exist, an error occurs and data cannot be
written.
• When a Double Word device is specified, this function writes data of lower 1 word (2 bytes), and "0" is
written to data of upper 1 word (2 bytes).
When writing Double Word devices, use the WriteDeviceRandom or the WriteDeviceBlock2 function.
• Digit specified bit device and index setting cannot be used.
• 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.

5 FUNCTIONS
516 5.4 Details of Functions (For .NET Control)
GetDevice2 (Acquiring device data)

Applicable controls
Applicable to the DotUtlType control.

Feature
Acquire one point of device in 2-byte data unit.

Format
■Visual Basic .NET
IRet = object.GetDevice2(szLabel, sData)
Integer IRet Returned value Output
String szLabel Label name Input
Short sData Read device value Output
5
■Visual C++ .NET
iRet = object.GetDevice2(szLabel, sData)
int iRet Returned value Output
String^ szLabel Label name Input
short sData Read device value Output

■Visual C# .NET
iRet = object.GetDevice2(ref szLabel, ref sData)
int iRet Returned value Output
String szLabel Label name Input
short sData Read device value Output

Description
• One point of device data specified for szLabel (label name) is stored in sData (read device values).

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
Basic type Bit, Word, Double Word*1, Float (Single Precision)*1, Float (Double Precision)*1, String*1, String (Unicode), Label name
Time*1, Timer, Long timer, Counter, Long counter, Retentive Timer, Long retentive timer

*1 Only lower 2 bytes of start device can be read.

When reading 2 words or more of devices, use the ReadDeviceBlock2 function.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 517
 How to specify devices
The read device values are stored as follows.

■When bit device is specified

Example: Read data from M0.
⋅ Label setting
Data type Device
Bit M0

⋅ Read device values

2 Bytes
M0*1

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

■When word device is specified

Example: Read data from D0.
⋅ Label setting
Data type Device
Word D0

⋅ Read device values

2 Bytes
D0

■When CN200 and later devices of FXCPU are specified

Example: Read data from CN200.
The specified device L (lower 2 bytes) is read as 1 point for FXCPU devices of CN200 and later.
Data are not read from the specified device H (upper 2 bytes).
⋅ Label setting
Data type Device
Double Word CN200

⋅ Read device values

2 Bytes
L of CN200

■When FD device is specified (4-word device)

Example: Read data by specifying FD0.
⋅ Label setting
Data type Device
Word FD0

⋅ Read device values

2 Bytes
LL of FD0*1

*1 Only lower 2 bytes are read. Data are not read from the specified devices HH, HL, and LH (upper 6 bytes).

5 FUNCTIONS
518 5.4 Details of Functions (For .NET Control)
■When data type equivalent to 2 words or more is specified for label
Example: Read data by specifying String type label.
⋅ Label setting
Data type Device
String D0

⋅ Read device values

2 Bytes
D0*1

*1 Only lower 2 bytes are read to the start device.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)
5
• When a device which corresponds to the label name does not exist, an error occurs and data cannot be
read.
• For the read device values, reserve 2 bytes of memory area. If the memory area is not reserved, a critical
error (an application error or the like) may occur.
• When a Double Word device is specified, only the data of the lower 1 word (2 bytes) are stored using this
function. (An error does not occur.)
When reading data from a Double Word device, use the ReadDeviceRandom function or the
ReadDeviceBlock2 function.
• Digit specified bit device and index setting cannot be used.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 519
 Connect (Connecting telephone line)

Applicable controls
Applicable to the DotUtlType control.

Feature
Connect the telephone line.

Format
■Visual Basic .NET
IRet = object.Connect()
Integer IRet Returned value Output

■Visual C++ .NET

iRet = object.Connect()
int iRet Returned value Output

■Visual C# .NET
iRet = object.Connect()
int iRet Returned value Output

Description
• The telephone line is connected according to the property settings of the modem communication control.
• When routing a serial communication module, the telephone line is connected in the connection system set in the
ActConnectWay property.
When auto line connect (callback number specification), callback connect (number specification), or callback request
(number specification) is set in the ActConnectWay property, an error occurs if a number is not set in the
ActCallbackNumber property.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

Considerations for executing the Connect function

• Always connect the telephone line before the execution of the Open function.
• When disconnecting the telephone line, execute the Disconnect function.
During the execution of the Connect function, the telephone line remains connected even when the Open and Close
functions are executed repeatedly.
• If the telephone line is disconnected in the Open status for some reason, always execute the Close function before
reconnecting the telephone line.

5 FUNCTIONS
520 5.4 Details of Functions (For .NET Control)
Considerations when using multiple telephone line connection objects
• When control types, port numbers, and telephone numbers of controls are different
When control types, port numbers, and telephone numbers set to multiple controls are different, an error (error code:
0xF1000016) occurs if the Connect function is executed to connect the control whose port number and telephone number
are different from those of the control which executed the Connect function first.
• When port numbers and telephone numbers of controls are the same
When control types, port numbers, and telephone numbers set to multiple controls are the same, the termination status are
different according to the connection system of the callback function. The following table shows the relations between the
connection system and the termination status of the callback function.
: Normal termination : Abnormal termination (Error occurrence)
Connection system of Connection system of control which executed the Connect function second or Later
control which executed Auto line connect Callback connect Callback request Callback
the Connect function first Auto line connect (Callback (Fixation) (Fixation) reception
fixation) Callback connect Callback request waiting
Auto line connect (Callback (Number specification) (Number specification) 5
number specification)
Auto line connect    
Auto line connect (Callback
fixation)
Auto line connect (Callback
number specification)
Callback connect (Fixation)    
Callback connect (Number
specification)
Callback request (Fixation)    
Callback request (Number
specification)
Callback reception waiting    

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 521
 Disconnect (Disconnecting telephone line)

Applicable controls
Applicable to the DotUtlType control.

Feature
Disconnect the telephone line.

Format
■Visual Basic .NET
IRet = object.Disconnect()
Integer IRet Returned value Output

■Visual C++ .NET

iRet = object.Disconnect()
int iRet Returned value Output

■Visual C# .NET
iRet = object.Disconnect()
int iRet Returned value Output

Description
The telephone line that was connected using the Connect function is disconnected.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
522 5.4 Details of Functions (For .NET Control)
Considerations for executing the Disconnect function
• When executing the Disconnect function during the execution of the Open function, execute the Close function before
executing the Disconnect function.
• If the telephone line is disconnected in the Open status for some reason, always execute the Close function before
reconnecting the telephone line.
• When multiple telephone line connection objects are used, execute the Disconnect function on the object which executed
the Connect function first after executing the Disconnect function on other objects.
When multiple telephone line connection objects are used, the telephone line is not disconnected if the Disconnect function
is not executed on the object that executed the Connect function first.
The following figure shows the example of how to use multiple objects simultaneously.

Example: When using two controls simultaneously

(Including the case when the objects A and B are operated by different applications)

<Object A> <Object B>

5
Connection Connection
start start

Execution of the Connect function

Execution of the Connect function

Execution of the Open function

Execution of the Open function

Execution of the function such as

Telephone line is connected.

the ReadDeviceBlock function

Execution of the function such as
the ReadDeviceBlock function

Execution of the Close function

Execution of the Close function

Execution of the Disconnect function

Complete

Execution of the Disconnect function*1

*1 : The actual telephone line is disconnected.

The Disconnect function on the object A does not
Complete terminate normally if the Disconnection function is
not executed on the object B.

5 FUNCTIONS
5.4 Details of Functions (For .NET Control) 523
 GetErrorMessage (Receiving error message)

Applicable controls
Applicable to the DotSupportMsg control.

Feature
Receive the error description and its corrective action corresponding to the error code.

Format
■Visual Basic .NET
IRet = object.GetErrorMessage(IErrorCode, szErrorMessage)
Integer IRet Returned value Output
Integer IErrorCode Error code Input
String szErrorMessage Error message Output

■Visual C++ .NET

iRet = object.GetErrorMessage(iErrorCode, szErrorMessage)
int iRet Returned value Output
int iErrorCode Error code Input
String^ szErrorMessage Error message Output

■Visual C# .NET
iRet = object.GetErrorMessage(iErrorCode, ref szErrorMessage)
int iRet Returned value Output
int iErrorCode Error code Input
String szErrorMessage Error message Output

Description
• The error description and its corrective action of the error code specified for lErrorCode (iErrorCode) are read.
• The read error description and its corrective action are stored in szErrorMessage.

Returned value
Normal termination: 0 is returned.
Abnormal termination: Any value other than 0 is returned.(Page 555 ERROR CODES)

5 FUNCTIONS
524 5.4 Details of Functions (For .NET Control)
6 SAMPLE PROGRAMS
This chapter explains the sample programs registered at the installation of MX Component.

Sample programs, test programs, and sample sequence programs

■Sample programs and test programs
Sample programs are for references when creating user programs.
Test programs are for conducting communication tests.
Use the programs with your responsibility.

■Sample sequence programs

Sample sequence programs require modifications according to the system configuration and parameter settings.
Modify the program to suit the system.
Use the programs with your responsibility.

List of sample programs, test programs, and sample sequence programs

The following table shows the list of sample programs registered under [user specified folder] - [Act] - [Samples] when
installing MX Component.
6
■Folder name: AccessVBA
Folder name Description Supported language Reference
AccessVBA Sample Sample program for ActUtlType VBA(Access) Page 533 Sample
program for Access
TestPro Test program for ActUtlType*1 

*1 A test program for checking operations.

■Folder name: ExcelVBA

Folder name Description Supported language Reference
ExcelVBA Sample Sample program for ActUtlType VBA(Excel) Page 529 Sample
program for Excel
Sample program for ActUtlType and Page 531 Sample
ActSupportMsg (Reading/writing program for Excel
devices) (Reading/writing
devices)
TestPro Test program for ActUtlType and 
ActSupportMsg*1

*1 A test program for checking operations.

■Folder name: VBScript

Folder name Description Supported language Reference
VBScript*2 SampleASP Sample program for ActMLUtlType HTML (ASP function) Page 536 ASP Sample
Programs
SampleHTML HTML Page 535 VBScript
Sample Program
TestPro Test program for ActUtlType and 
ActSupportMsg*1

*1 A test program for checking operations.

*2 The test programs will be operate with the following Internet Explorer.
⋅ Internet Explorer 8
⋅ Internet Explorer 9
⋅ Internet Explorer 10
⋅ Internet Explorer 11

6 SAMPLE PROGRAMS
525
 ■Folder name: Vb.NET
Folder name Description Supported language Reference
*1
Vb.NET ModemSample Modem communication sample program Visual Basic .NET(Visual Page 539 Modem
for ActUtlType and ActSupportMsg Studio 2005) communication sample
program
ModemSample2010 Visual Basic .NET(Visual
Studio 2010)
Sample Read/Write sample program for Visual Basic .NET(Visual Page 541 Read/Write
ActUtlType and ActProgType Studio 2005) sample program
Sample2010 Visual Basic .NET(Visual
Studio 2010)
SampleDot Read/Write sample program for Visual Basic .NET(Visual
DotUtlType Studio 2005)
SampleDot2010 Visual Basic .NET(Visual
Studio 2010)
Sample_References Read/Write sample program for Visual Basic .NET(Visual
ActUtlType and ActProgType (for Studio 2005)
Reference)
Sample_References2010 Visual Basic .NET(Visual
Studio 2010)
Sample_ReferencesDot Read/Write sample program for Visual Basic .NET(Visual
DotUtlType (for Reference) Studio 2005)
Sample_ReferencesDot2010 Visual Basic .NET(Visual
Studio 2010)
Sample_TypeConv Type conversion sample program for Visual Basic .NET(Visual Page 544 Type
ActUtlType and ActSupportMsg Studio 2005) conversion sample
program
Sample_TypeConv2010 Visual Basic .NET(Visual
Studio 2010)
SampleDataLogging2010 Logging file transfer sample program for Visual Basic .NET(Visual Page 546 Logging file
ActUtlDataLogging and Studio 2010) transfer sample program
ActProgDataLogging
SampleDataLogging_References2010 Logging file transfer sample program for Visual Basic .NET(Visual
ActUtlDataLogging and Studio 2010)
ActProgDataLogging (for Reference)

*1 When the operation environment of the sample program is Visual Studio 2013/2015, the installation of MFC library (DLL) for multiple
byte character encode (MBCS) is required.

6 SAMPLE PROGRAMS
526
■Folder name: Vc.NET
Folder name Description Supported language Reference
Vc.NET Sample2005 Read/Write sample program for Visual Basic .NET(Visual Page 547 Read/Write
ActUtlType and ActProgType Studio 2005) sample program
Sample2010 Visual Basic .NET(Visual
Studio 2010)
Sample2017 Visual Basic .NET(Visual
Studio 2017)
SampleDot2005 Read/Write sample program for Visual Basic .NET(Visual
DotUtlType Studio 2005)
SampleDot2010 Visual Basic .NET(Visual
Studio 2010)
SampleDot2017 Visual Basic .NET(Visual
Studio 2017)
Sample_References2005 Read/Write sample program for Visual Basic .NET(Visual
ActUtlType and ActProgType (for Studio 2005)
Reference)
Sample_References2010 Visual Basic .NET(Visual
Studio 2010)
Sample_References2017 Visual Basic .NET(Visual
Studio 2017)
Sample_ReferencesDot2005 Read/Write sample program for
DotUtlType (for Reference)
Visual Basic .NET(Visual
Studio 2005)
6
Sample_ReferencesDot2010 Visual Basic .NET(Visual
Studio 2010)
Sample_ReferencesDot2017 Visual Basic .NET(Visual
Studio 2017)
Sample_Support Troubleshooting function sample Visual Basic .NET(Visual Page 548
program for DotSupportMsg Studio 2005) Troubleshooting function
Sample_Support2010 Visual Basic .NET(Visual sample program
Studio 2010)
Sample_Support2017 Visual Basic .NET(Visual
Studio 2017)

■Folder name: Vcs.NET

Folder name Description Supported language Reference
Vcs.NET*1 Sample Read/Write sample program for Visual C# .NET(Visual Page 549 Read/Write
ActUtlType and ActProgType Studio 2005) sample program
Sample2010 Visual C# .NET(Visual
Studio 2010)
SampleDot Read/Write sample program for Visual C# .NET(Visual
DotUtlType Studio 2005)
SampleDot2010 Visual C# .NET(Visual
Studio 2010)
Sample_References Read/Write sample program for Visual C# .NET(Visual
ActUtlType and ActProgType (for Studio 2005)
Reference)
Sample_References2010 Visual C# .NET(Visual
Studio 2010)
Sample_ReferencesDot Read/Write sample program for Visual C# .NET(Visual
DotUtlType (for Reference) Studio 2005)
Sample_ReferencesDot2010 Visual C# .NET(Visual
Studio 2010)
SampleDataLogging2010 Logging file transfer sample program for Visual C# .NET(Visual Page 549 Logging file
ActUtlDataLogging and Studio 2010) transfer sample program
ActProgDataLogging
SampleDataLogging_References2010 Logging file transfer sample program for Visual C# .NET(Visual
ActUtlDataLogging and Studio 2010)
ActProgDataLogging (for Reference)

*1 When the operation environment of the sample program is Visual Studio 2013/2015, the installation of MFC library (DLL) for multiple
byte character encode (MBCS) is required.

6 SAMPLE PROGRAMS
527
 ■Folder name: Vc
Folder name Description Supported language Reference
Vc Sample Read/Write sample program for Visual C++ Page 550 Dispatch
ActUtlType and ActProgType .NET(MFC)(Visual Studio interface
2005)
Sample2017 Visual C++
.NET(MFC)(Visual Studio
2017)
CustomSample Read/Write sample program for Visual C++ Page 552 Custom
ActUtlType and ActProgType .NET(MFC)(Visual Studio interface
2005)
CustomSample2017 Visual C++
.NET(MFC)(Visual Studio
2017)
Sample_Support For ActSupportMsg Visual C++ Page 553
.NET(MFC)(Visual Studio Troubleshooting
2005) function sample
program
Sample_Support2017 Visual C++
.NET(MFC)(Visual Studio
2017)
CustomSampleDataLogging2010 Logging file transfer sample program for Visual C++ Page 554 Logging file
ActUtlDataLogging and .NET(MFC)(Visual Studio transfer sample
ActProgDataLogging 2010) program
CustomSampleDataLogging2017 Visual C++
.NET(MFC)(Visual Studio
2017)
SampleDataLogging2010 Visual C++
.NET(MFC)(Visual Studio
2010)
SampleDataLogging2017 Visual C++
.NET(MFC)(Visual Studio
2017)

■Folder name: GppW

Folder name Description Supported language Reference
GppW CCG4A Sample ladder for CC-Link G4 Sequence program (GX MX Component
communication Developer) Version 4 Operating
FXCPUtel Sample ladder for modem Manual
communication (FXCPU)
QJ71C24Callback Sample ladder for modem
communication (Q series-compatible
C24) in which the setting 1 is specified
for the callback function
QJ71C24Callback_Number Sample ladder for modem
communication (Q series-compatible
C24) in which the setting 3 is specified
for the callback function
QJ71C24TEL Sample ladder for modem
communication (Q series-compatible
C24)

6 SAMPLE PROGRAMS
528
6.1 VBA Sample Programs
This section explains the VBA sample programs for Excel and Access.

Sample program for Excel

This sample program is a program to log and graph device values of a programmable controller CPU using the ActUtlType
control.
This sample program was created on Excel 2003.

How to use the sample program

1. Open the sample sheet.

2. Enter the logical station number, which was specified for the communication setting in Communication Setup Utility, into
the "LogicalStationNumber" input cell.

3. Enter the start device of devices to be read into the "DeviceName" input cell.

4. Enter the logging interval into the "LoggingTiming" input cell.

5. Click the [LoggingStart] button to start logging. 6

When the logging starts, the past 10 device values and line graphs are displayed on the graph.

6. Click the [LoggingStop] button to stop logging.

Note that the logging data on the screen are not cleared.

7. If an error occurs during the process, an error message is displayed on the "Message" output cell and an error code is
displayed on the "Return Code" output cell.
When an error occurs, perform the troubleshooting corresponds to the error code.(Page 555 ERROR CODES)

Considerations for using the sample program

• Before executing the sample program, set the communication settings in Communication Setup Utility.
• When changing the input value, click the [LoggingStop] button to stop logging, change the input value, and click the
[LoggingStart] button to start logging.
• In this sample program, the number of device points to be logged is 10, and the number of logging times is 10.

Sample file
The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [ExcelVBA] - [Sample] Sample.xls

6 SAMPLE PROGRAMS
6.1 VBA Sample Programs 529
 Screen
The following explains the settings on the sample program screen.

Item Description
LogicalStationNumber Enter the logical station number which was specified for the communication setting in Communication Setup Utility.
DeviceName Enter the start device of devices to be read.
LoggingTiming (hh:mm:ss) Enter the logging interval.
Example: Logging at an interval of 1 second: 0:0:1
Logging at an interval of 1 hour 30 minutes: 1:30:0
Message Display the function execution result. (Character string)
ReturnCode Display the function execution result. (Hexadecimal value)
Time Display the logged system time.
Data01 to 10 Display the logged device values.
Graph Display the past 10 logged values of 10 devices in line graphs.
[LoggingStart] button Start logging.
[LoggingStop] button Stop logging.

6 SAMPLE PROGRAMS
530 6.1 VBA Sample Programs
Sample program for Excel (Reading/writing devices)
This sample program is a program to read/write the programmable controller CPU devices (D0 to D9) using the ActUtlType
control.
This program displays the error code and error message on the dialog box using the ActSupportMsg control when an error
occurs.
This sample program was created on Excel 2003.

How to use the sample program

1. Open the sample sheet.

2. Enter the logical station number, which was specified for the communication setting in Communication Setup Utility, into
the "LogicalStationNumber" input cell.

3. Click the [DeviceRead] button to read the device values of D0 to D9 of the programmable controller CPU and display
them on the DeviceRead area.

4. Enter values into D0 to D9 of the DeviceWrite area and click the [DeviceWrite] button to write the values to D0 to D9 of
the programmable controller CPU.

5. If reading/writing data from/to the devices D0 to D9 fails, the error message corresponds to the error code is displayed on 6
the dialog box.

Considerations for using the sample program

Before executing the sample program, set the communication settings in Communication Setup Utility.

Sample file
The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [ExcelVBA] - [Sample] Sample_DeviceRW.xls

6 SAMPLE PROGRAMS
6.1 VBA Sample Programs 531
 Screen
The following explains the settings on the sample program screen.

(1) (2)

Item Description
LogicalStationNumber Enter the logical station number which was specified for the communication setting in Communication Setup Utility.
(1) (DeviceRead area) Display the device values of D0 to D9 of the programmable controller CPU.
(2) (DeviceWrite area) Enter the values to be written into D0 to D9 of the programmable controller CPU.
[DeviceRead] button Read the device values of D0 to D9 of the programmable controller CPU and display them on the DeviceRead area.
[DeviceWrite] button Write the device values entered into D0 to D9 of the DeviceWrite area to D0 to D9 of the programmable controller CPU.

6 SAMPLE PROGRAMS
532 6.1 VBA Sample Programs
Sample program for Access
This sample program is a program to log and monitor device values of a programmable controller CPU using the ActUtlType
control.
This sample program was created on Access 2003.

How to use the sample program

1. Open the database.
2. Enter the logical station number, which was specified for the communication setting in Communication Setup Utility, into
the "LogicalStationNumber" text box.

3. Enter the logging interval into the "LoggingTiming" text box.

4. Click the [LoggingStart] button to start logging.

5. Click the [LoggingStop] button to stop logging.

Note that the logging data on the screen are not cleared.

6. If an error occurs during the process, an error message and error code are displayed on the message box. When an
error occurs, perform the troubleshooting corresponds to the error code.(Page 555 ERROR CODES)
6
Considerations for using the sample program
• Before executing the sample program, set the communication settings in Communication Setup Utility.
• When changing the input value, click the [LoggingStop] button to stop logging, change the input value, and click the
[LoggingStart] button to start logging.
• In this sample program, devices "D0" to "D4" are set as the devices to be monitored, and "D10" to "D17" are set as the
devices to be logged.
The monitoring interval is 1 second.
• This sample program logs device values up to 100 times.
If the number of logging times exceeds 100, the oldest logging data is deleted and the newest logging data is registered.

Sample file
The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [AccessVBA] - [Sample] Sample.mdb

6 SAMPLE PROGRAMS
6.1 VBA Sample Programs 533
 Screen
The following explains the settings on the sample program screen.

Item Description
LogicalStationNumber Enter the logical station number which was specified for the communication setting in Communication Setup Utility.
LoggingTiming Enter the logging interval. (In seconds)
LoggingData Display the logged data.
OnDeviceStatus Display the devices whose conditions are satisfied among the devices being monitored.
[LoggingStart] button Start logging.
[LoggingStop] button Stop logging.

6 SAMPLE PROGRAMS
534 6.1 VBA Sample Programs
6.2 VBScript Sample Program
This section explains the VBScript sample program.
This sample program is a program to define device values of a programmable controller CPU as a capacity and status of a
tank, and monitor their values using the ActUtlType control.
This sample program was created on Microsoft FrontPage 2000.

How to use the sample program

1. Open the sample file to open the communication line to the programmable controller CPU.

2. The device values of the programmable controller CPU are acquired at an interval of 1 second and they are used to
display the capacity and status of the tank.

3. If an error occurs during the process, an error message and error code are displayed on the message box. When an
error occurs, perform the troubleshooting corresponds to the error code.(Page 555 ERROR CODES)

Considerations for using the sample program

• Before executing the sample program, set the logical station number to "0" for the communication setting in Communication
Setup Utility. 6
• In this sample program, the device "D100" is used for the tank capacity, and the device "D101" is used for the tank status.

Sample file
The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [VBScript] - [SampleHTML] Sample.html

Screen
The following explains the settings on the sample program screen.
Tank capacity: Empty Tank capacity: Full
Tank status: Normal Tank status: Error

Item Description Remarks

Tank capacity Indicate the tank capacity. Linked with the device "D100".
(Within the range of 0 ≤ device value ≤ 200)
Tank status Indicate the tank status. Linked with the device "D101".
Normal (device value = 0): Blue lamp ON
Error (device value <> 0): Red lamp ON

6 SAMPLE PROGRAMS
6.2 VBScript Sample Program 535
 6.3 ASP Sample Programs
This sample program is a program to read programmable controller CPU data and device values using the ActUtlType control.

File structure
• Sample.asp (data input screen)
The initial display screen used to set data for monitoring.
• SampleControl.asp (data acquisition screen)
Acquire input data of Sample.asp, store them in global variables, and check them for errors.
• SampleMon.asp (data display screen)
Display data according to input data of Sample.asp. Display an error description when an error occurs.

How to use the sample program

1. Store Sample.asp, SampleControl.asp, and SampleMon.asp in the same folder on the WWW server.

2. Browse the URL of Sample.asp on the Microsoft Internet Explorer and display the initial screen.

3. Enter data into "MonitorTiming", "LogicalStationNumber", "DeviceName", and "DeviceSize" on the initial screen.
Press the [MonitorStart] button to start the Open processing, ReadDeviceBlock processing, GetCpuType processing,
and Close processing.

4. The input data for "MonitorTiming:", "LogicalStationNumber:", "DeviceName:", and "DeviceSize:" are displayed on the
data display screen.

5. An error occurrence processing is displayed for "Message:" when an error occurs in the process.
6. The result of the process is displayed for "Return Code:".
7. The model of the connected programmable controller CPU is displayed for "CpuType:".
8. The device data of the connected programmable controller CPU is displayed for "ReadData(Hex)".
9. When an error occurs, perform the troubleshooting corresponds to the error code.(Page 555 ERROR CODES)
10. The data display screen repeats updating at the interval set for "MonitorTiming:".
11. Press the [Back] button to return to the initial screen.

Considerations for using the sample program

Before executing the sample program, set the communication settings in Communication Setup Utility.

Sample file list

The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [VBScript] - [SampleASP] Sample.asp
SampleControl.asp
SampleMon.asp

6 SAMPLE PROGRAMS
536 6.3 ASP Sample Programs
Screen
The following explains the settings on the sample program screen.

■Data input screen (Sample-E.asp)

Item Description
MonitorTiming Enter the monitoring interval.
LogicalStationNumber Enter the logical station number.
DeviceName Enter the device name of the device to be read.
DeviceSize Enter the number of points of the devices to be read.
[MonitorStart] button Start the monitor processing.

■Data acquisition screen (SampleControl-E.asp)

The data acquisition screen is a screen used to store the data entered on the data input screen into the global variables and
check them for errors. This screen is not displayed on the Internet Explorer screen.

6 SAMPLE PROGRAMS
6.3 ASP Sample Programs 537
 ■Data display screen (SampleMon-E.asp)

Item Description
MonitorTiming: Display the monitoring interval.
LogicalStationNumber: Display the logical station number.
DeviceName: Display the device name of the device to be read.
DeviceSize: Display the number of points of the devices to be read.
Message: Display an error description at an error occurrence.
Return Code: Display the method execution result.
CpuType: Display the CPU model.
ReadData(Hex) Display the read device values.
[Back] button Return to the initial screen.

6 SAMPLE PROGRAMS
538 6.3 ASP Sample Programs
6.4 Visual Basic .NET Sample Programs
Modem communication sample program
This sample program is a program to monitor devices of a programmable controller CPU corresponds to the specified logical
station number using the ActUtlType control.
This program displays the error code and error message on the dialog box using the ActSupportMsg control when an error
occurs.
This sample program was created on Visual Basic .NET (Visual Studio 2005).

How to use the sample program

1. Enter the logical station number, which was specified for the modem communication setting in Communication Setup
Utility, into the "LogicalStationNumber" text box.

2. If a password is set to the module to be connected, enter the password into the "Password" text box.

3. Enter the monitoring interval into the "MonitorInterval" text box.

4. Enter the device name to be monitored into the "DeviceName" text box, and the number of device points into the "Size"
text box. 6
5. Click the [MonitorStart] button to open the communication line after connecting the telephone line,and read device values
at the interval specified using the ReadDeviceBlock function. (For the logical station number that does not require the
telephone line connection, the telephone line is not connected and only the Open function is executed on the
communication line.)

6. Click the [MonitorStop] button to disconnect the telephone line after closing the communication line.

7. If an error occurs during the process of this sample program, an error code is displayed on the "ReturnValue" text box.
If the error code is displayed on the "ReturnValue" text box, click the [GetErrorMessage] button to display the error
description and corrective action corresponds to the displayed error code.
When an error occurs, perform the troubleshooting corresponds to the error code.
(Page 555 ERROR CODES)

Considerations for using the sample program

• Since the ActUtlType control is used, set the logical station number in Communication Setup Utility before executing the
sample program.
• When changing the logical station number, monitoring interval, device name, and number of read points, click the
[MonitorStop] button to close the communication line, and click the [MonitorStart] button to resume the communication.

Sample file
The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [Vb.NET] - [ModemSample] ModemSample.sln

6 SAMPLE PROGRAMS
6.4 Visual Basic .NET Sample Programs 539
 Screen
The following explains the settings on the sample program screen.

Item Description
LogicalStationNumber Enter the logical station number set in Communication Setup Utility.
Password Enter the password when it is required.
MonitorInterval Set the monitoring interval. (In seconds)
DeviceName Enter the device name to be monitored.
Size Enter the number of read points.
ReturnValue Display the returned value of the executed method.
[MonitorStart] button Open the communication line and start monitoring after connecting the telephone line.
[MonitorStop] button Disconnect the telephone line and stop monitoring after closing the communication line.
[GetErrorMessage] button Acquire and display the error description and corrective action for the error code of "ReturnValue".

6 SAMPLE PROGRAMS
540 6.4 Visual Basic .NET Sample Programs
Read/Write sample program
This sample program is a program to read/write device values of a programmable controller CPU and monitor device status
using any of the ActUtlType control, the DotUtlType control, or the ActProgType control.
This sample program was created on Visual Basic .NET (Visual Studio 2005) or Visual Basic .NET (Visual Studio 2010).
In case of DotUtlType control, replace the terms such as "DeviceName", "DeviceSize" to "LabelName" and "DataSize" in the
description.
In addition, replace the terms such as "Device name", "Points" and "DeviceValue" to "LabelName", "DataSize" and "Data
value".

How to use the sample program

1. Load the form and select the control to be used.

2. When using the ActUtlType control, enter the logical number, which was specified for the communication setting in
Communication Setup Utility, into the "LogicalStationNumber" text box before clicking the [Open] button.

3. Click the [Open] button to open the communication line.

4. For reading devices randomly, enter the device name and the number of points to be read into the "DeviceName" and
"DeviceSize" text boxes in the "Random Read/Write" frame, and click the [ReadDeviceRandom2] button to display the 6
device data on the "Data" text box in the "Output" frame.

5. For writing devices randomly, enter the device name and the number of points to be written in the "DeviceName" and
"DeviceSize" text boxes in the "Random Read/Write" frame, enter the device value to be written into the "DeviceData"
text box inside the same frame, and click the [WriteDeviceRandom2] button to write the device value to the
programmable controller CPU.

6. For reading devices in bulk, enter the device name and the number of points to be read into the "DeviceName" and
"DeviceSize" text boxes in the "Block Read/Write" frame, and click the [ReadDeviceBlock2] button to display the device
data on the "Data" text box in the "Output" frame.

7. For writing devices in bulk, enter the device name and the number of points to be written into the "DeviceName" and
"DeviceSize" text boxes in the "Block Read/Write" frame, enter the device value to be written into the "DeviceData" text
box in the same frame, and click the [WriteDeviceBlock2] button to write the device value to the programmable controller
CPU.

8. For registering devices for status monitoring, enter the device name, number of points, device value and status
monitoring interval into the "DeviceName", "DeviceSize", "DeviceData", and "MonitorCycle" text boxes in the "Status
Entry/Free" frame as the event occurrence conditions, and click the [EntryDeviceStatus] button.
When the registered event occurrence conditions are satisfied, the event data are displayed on the "Data" text box in the
"Output" frame.

9. For deregistering registered devices for status monitoring, click the [FreeDeviceStatus] button.
10. If an error occurs during the process, an error code is displayed on the "Return Code" box in the "Output" frame.
When an error occurs, perform the troubleshooting corresponds to the error code.
(Page 555 ERROR CODES)

11. Click the [Close] button to close the communication line.

Considerations for using the sample program

• When using the ActUtlType control, set the communication settings in Communication Setup Utility before executing the
sample program.
• When using the ActProgType control in this sample program, "Q02(H)" is set for the programmable controller CPU, "COM1"
is set for the COM port, and 19200bps is set for the transmission speed.
The specification can be changed by changing values of the corresponding property.
• When changing the control to be used, close the communication line by clicking the [Close] button, change the control, and
click the [Open] button to reopen the line.

6 SAMPLE PROGRAMS
6.4 Visual Basic .NET Sample Programs 541
 Sample file list
The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [Vb.NET] - [Sample] Sample.sln
[User specified folder] - [Act] - [Samples] - [Vb.NET] - [Sample_References] Sample_References.sln
[User specified folder] - [Act] - [Samples] - [Vb.NET] - [SampleDot] Sample.sln
[User specified folder] - [Act] - [Samples] - [Vb.NET] - [Sample_ReferencesDot] Sample_References.sln

Screen
The following explains the settings on the sample program screen.
<Sample> <Sample_References>

<SampleDot> <Sample_ReferencesDot>

6 SAMPLE PROGRAMS
542 6.4 Visual Basic .NET Sample Programs
Item Description
"Control" frame Any of ActUtlType, ActProgType, or Select the control to be used.
DotUtlType
LogicalStationNumber Enter the logical station number which was specified for the communication
setting in Communication Setup Utility.
[Open] button Open the communication line.
[Close] button Close the communication line.
"Random Read/Write" frame DeviceName Enter the device name for reading/writing devices randomly.
DeviceSize Enter the number of device points for reading/writing devices randomly.
DeviceData Enter the device value for writing devices randomly.
[ReadDeviceRandom2] button Read device data randomly from the programmable controller CPU to the data
source entered into the "DeviceName" and "DeviceSize" text boxes in the same
frame, and display the data on the "Data" text box in the "Output" frame.
[WriteDeviceRandom2] button Write device data randomly to the programmable controller CPU from the data
source entered into the "DeviceName", "DeviceSize", and "DeviceData" text
boxes in the same frame.
"Block Read/Write" frame DeviceName Enter the device name for reading/writing devices in bulk.
DeviceSize Enter the number of device points for reading/writing devices in bulk.
DeviceData Enter the device values for writing devices in bulk.
[ReadDeviceBlock2] button Read device data in bulk from the programmable controller CPU to the data 6
source entered into the "DeviceName" and "DeviceSize" text boxes in the same
frame, and display the data on the "Data" text box in the Output" frame.
[WriteDeviceBlock2] button Write device data in bulk to the programmable controller CPU from the data
source entered into the "DeviceName", "DeviceSize", and "DeviceData" text
boxes in the same frame.
"Status Entry/Free" frame DeviceName Enter the device name as an event occurrence condition.
DeviceSize Enter the number of device points as an event occurrence condition.
MonitorCycle Enter the event monitoring interval.
DeviceData Enter the device value as an event occurrence condition.
[EntryDeviceStatus] button Register the on-device status/event to the data source entered into the
"DeviceName", "DeviceSize", "MonitorCycle", and "DeviceData" text boxes in
the same frame.
When the registered event occurrence condition is satisfied, the event data is
displayed on the "Data" text box of the "Output" frame.
[FreeDeviceStatus] button Delete the registered on-device status/event.
"Output" frame Return Code Display the method execution result.
Data Display the read device values.

6 SAMPLE PROGRAMS
6.4 Visual Basic .NET Sample Programs 543
 Type conversion sample program
This sample program is a program to read/write ASCII character string, 32-bit integer, or real number data from/to a
programmable controller CPU devices in the corresponding data format using the ActUtlType control, and display the error
message using the ActSupportMsg control when an error occurs during the process.
This sample program was created on Visual Basic .NET (Visual Studio 2005).

How to use the sample program

1. Load the form, enter the logical number, which was specified for the communication setting in Communication Setup
Utility, into the "LogicalStationNumber" text box, and click the [Open] button to open the communication line.

2. For writing ASCII character data to the programmable controller CPU, enter the ASCII character data into the upper text
box in the "ASCII character" frame, and click the [Write] button in the same frame.(The data write function is executed
within the range of D0 to D9, regardless of the number of entered characters. When the number of characters is
insufficient, the blanks are filled with 0 (Hex).)

3. For reading ASCII character data, click the [Read] button in the "ASCII character" frame. Data from the programmable
controller CPU is displayed on the lower text box in the same frame. (The data read function is executed within the range
of D0 to D9.)

4. For writing 32-bit integer data to the programmable controller CPU, enter the 32-bit integer data into the upper text box in
the "32bit integer" frame, and click the [Write] button in the same frame. (The data write function is executed within the
range of D10 to D11.)

5. For reading 32-bit integer data, click the [Read] button in the "32bit integer" frame. Data from the programmable
controller CPU is displayed on the lower text box in the same frame. (The data read function is executed within the range
of D10 to D11.)

6. For writing real number data to the programmable controller CPU, enter the real number data into the upper text box in
the "Real number" frame, and click the [Write] button in the same frame. (The data write function is executed within the
range of D12 to D13.)

7. For reading real number data, click the [Read] button in the "Real number" frame. Data from the programmable controller
CPU is displayed on the lower text box in the same frame. (The data read function is executed within the range of D12 to
D13.)

8. When an error occurs, perform the troubleshooting corresponds to the error code.(Page 555 ERROR CODES)

9. Click the [Close] button to close the communication line.

Considerations for using the sample program

• When using the ActUtlType control, set the communication settings in Communication Setup Utility before executing the
sample program.
• If an error which does not relate to the ActUtlType control occurs (for example, a character string or out-of-range value is
entered for 32-bit integer or real number), the corresponding error message is displayed on the message box, and the
program is terminated.

Sample file
The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [Vb.NET] - [Sample_TypeConv] Sample_TypeConv.sln

6 SAMPLE PROGRAMS
544 6.4 Visual Basic .NET Sample Programs
Screen
The following explains the settings on the sample program screen.

Item Description
Logical Station Number Enter the logical station number which was specified for the communication setting in
Communication Setup Utility.
[Open] button Open the communication line.
[Close] button Close the communication line.
"ASCII character" frame [Write] button Write the ASCII character data, which was entered into the upper text box in the frame, to the
programmable controller CPU.
[Read] button Display the ASCII character data, which was read from the programmable controller CPU, on
the lower text box in the frame.
"32bit integer" frame [Write] button Write the 32-bit integer data, which was entered into the upper text box in the frame, to the
programmable controller CPU.
[Read] button Display the 32-bit integer data, which was read from the programmable controller CPU, on the
lower text box in the frame.
"Real number" frame [Write] button Write the real number data, which was entered into the upper text box in the frame, to the
programmable controller CPU.
[Read] button Display the real number data, which was read from the programmable controller CPU, on the
lower text box in the frame.

6 SAMPLE PROGRAMS
6.4 Visual Basic .NET Sample Programs 545
 Logging file transfer sample program
This sample program is a program to transfer a logging file using the ActUtlDataLogging control or ActProgDataLogging
control.
This sample program was created on Visual Basic .NET (Visual Studio 2010)

How to use the sample program

1. Load the form and select a control to be used.
2. Specify the path of a folder to transfer a logging file for "Folder".

3. Click the [Save to PC] button to save a logging file to the specified folder.

Sample file
The sample programs are installed into the following folders at default installation.
Folder name File name
[User specified folder] - [Act] - [Samples] - [Vb.NET] - [SampleDataLogging_References2010] SampleDataLogging_References2010.sln
[User specified folder] - [Act] - [Samples] - [Vb.NET] - [SampleDataLogging2010] SampleDataLogging2010.sln

Screen
The following explains the settings on the sample program screen.

(1)

Item Description
Controls Select a control to be used.
(ActUtlDataLogging /
ActProgDataLogging)
Result Display an error code.
Folder name Specify a folder path to transfer a logging file.
[Display] button Update the content displayed in "File list".
[Select] button Apply the folder name selected in "File list" to "Folder".
When a file name is selected, a logging file is saved in the personal computer.
[Save to PC] button Display the "Save As" screen.
Only a text file (*.txt) can be selected in "Save as type".
[Close] button Exit the sample program.
(1) File list Display files or folders in the path specified for "Folder" in a list.
For a folder name, a slash '/' is prefixed.

6 SAMPLE PROGRAMS
546 6.4 Visual Basic .NET Sample Programs
6.5 Visual C++ .NET Sample Programs
Read/Write sample program
This sample program is a program to read/write device values of a programmable controller CPU and monitor device status
using any of the ActUtlType control, the DotUtlType control, or the ActProgType control.
This sample program was created on Visual C++ .NET (Visual Studio 2005), Visual C++ .NET (Visual Studio 2010), and
Visual C++ .NET (Visual Studio 2017).

How to use the sample program

The operation is the same as that for Visual Basic .NET (Visual Studio 2005).(Page 541 How to use the sample program)

Considerations for using the sample program

• The considerations are the same as those for Visual Basic .NET (Visual Studio 2005).(Page 541 Considerations for
using the sample program)
• If a sample program created in Visual Studio 2017 is used, a build error may occur.
For details, refer to the following section.
6
Page 613 A build error occurred when using a sample program created in Visual Studio 2017

Sample file list

The sample program is installed in the following folder when the default pass is selected.

■For Visual C++ .NET (Visual Studio 2005)

Folder name File name
[User specified folder] - [Act ] - [Samples] - [Vc.NET] - [Sample2005] Sample2005.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [Sample_References2005] Sample_References2005.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [SampleDot2005] Sample2005.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [Sample_ReferencesDot2005] Sample_References2005.sln

■For Visual C++ .NET (Visual Studio 2010)

Folder name File name
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [Sample2010] Sample2010.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [Sample_References2010] Sample_References2010.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [SampleDot2010] Sample2010.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [Sample_ReferencesDot2010] Sample_References2010.sln

■For Visual C++ .NET (Visual Studio 2017)

Folder name File name
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [Sample2017] Sample2017.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [Sample_References2017] Sample_References2017.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [SampleDot2017] Sample2017.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [Sample_ReferencesDot2017] Sample_References2017.sln

Screen
The settings on the screen are the same as those for Visual Basic .NET (Visual Studio 2005).(Page 542 Screen)

6 SAMPLE PROGRAMS
6.5 Visual C++ .NET Sample Programs 547
 Troubleshooting function sample program
This sample program is a program to perform the troubleshooting function using the DotSupportMsg control.

How to use the sample program

1. Load the form.

2. Enter the error code into the "ErrorCode" text box to display the error description.

3. Click the [GetErrorMessage] button to display the error description and corrective action on the text box for displaying the
error description. Displayed error descriptions and corrective actions are the same as the descriptions on Page 555
Error Codes Returned by Controls.

4. Click the [Exit] button to exit the sample program.

Considerations for using the sample program

• For error codes to be entered into the "ErrorCode" text box, enter the error code described on Page 555 Error Codes
Returned by Controls (0x********), or enter it in decimal number.
• If a sample program created in Visual Studio 2017 is used, a build error may occur.
For details, refer to the following section.
Page 613 A build error occurred when using a sample program created in Visual Studio 2017

Sample file
The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [Vc.Net] - [Sample_Support] Sample_Support.sln

Screen
The following explains the settings on the sample program screen.

(1)

Item Description
Error Code Enter the error code.
[GetErrorMessage] button Read the error description and corrective action of the error code entered into the "ErrorCode" text box.
[Exit] button Exit the sample program.
(1) (Error definition displaying text box) Display the error description and corrective action of the error code entered into the "ErrorCode" text box.

6 SAMPLE PROGRAMS
548 6.5 Visual C++ .NET Sample Programs
6.6 Visual C# .NET Sample Programs
Read/Write sample program
This sample program is a program to read/write device values of a programmable controller CPU and monitor device status
using any of the ActUtlType control, the DotUtlType control, or the ActProgType control.
This sample program was created on Visual C# .NET (Visual Studio 2005).

How to use the sample program

The operation is the same as that for Visual Basic .NET (Visual Studio 2005). (Page 541 How to use the sample program)

Considerations for using the sample program

The considerations are the same as those for Visual Basic .NET (Visual Studio 2005). (Page 541 Considerations for
using the sample program)

Sample file list

The sample program is installed in the following folder when the default pass is selected. 6
Folder name File name
[User specified folder] - [Act] - [Samples] - [Vcs.NET] - [Sample] Sample.sln
[User specified folder] - [Act] - [Samples] - [Vcs.NET] - [Sample_References] Sample_References.sln
[User specified folder] - [Act] - [Samples] - [Vcs.NET] - [SampleDot] Sample.sln
[User specified folder] - [Act] - [Samples] - [Vcs.NET] - [Sample_ReferencesDot] Sample_References.sln

Screen
The settings on the screen are the same as those for Visual Basic .NET (Visual Studio 2005). (Page 542 Screen)

Logging file transfer sample program

This sample program is a program to transfer a logging file using the ActUtlDataLogging control or ActProgDataLogging
control.
This sample program was created on Visual C# .NET (Visual Studio 2010).

How to use the sample program

The operation is the same as that for Visual Basic .NET(Visual Studio 2010). (Page 546 How to use the sample program)

Sample file list

The sample programs are installed into the following folders at default installation.
Folder name File name
[User specified folder] - [Act] - [Samples] - [Vcs.NET] - [SampleDataLogging_References2010] SampleDataLogging_References2010.sln
[User specified folder] - [Act] - [Samples] - [Vcs.NET] - [SampleDataLogging2010] SampleDataLogging2010.sln

Screen
The screen is the same as that for Visual Basic .NET(Visual Studio 2010). (Page 546 Screen)

6 SAMPLE PROGRAMS
6.6 Visual C# .NET Sample Programs 549
 6.7 Visual C++ .NET (MFC) Sample Programs
Dispatch interface
This sample program is a program to read a model of connected CPU and read/write device values using the ActUtlType
control or the ActProgType control with the dispatch interface.

How to use the sample program

1. Load the form and select the control to be used.

2. Click the [Open Communication] button to open the communication line through Ethernet communication.

3. Click the [GetCpuType] button to display the model code and the CPU model of the currently connected programmable
controller CPU on the upper text box and the lower text box of "Output Data" respectively.

4. Enter the device to be read into the "Device Name" text box, and click the [GetDevice] button to display the device data
on the upper text box of "Output Data".

5. Enter the device to be written into the "Device Name" text box, enter the device value to be written into the "Device
Value" text box, and click the [SetDevice] button to write the device value.

6. Click the [Close Communication] button to close the communication line.

7. If an error occurs during the process, an error code is displayed on the "Return Value" text box.
When an error occurs, perform the troubleshooting corresponds to the error code. (Page 555 ERROR CODES)

Considerations for using the sample program

• When using the ActUtlType control, set the logical station number "1" for the Ethernet communication information in
Communication Setup Utility before executing the sample program.
• When changing the control to be used, close the communication line by clicking the [Close Communication] button, change
the control, and reopen the line.
• If a sample program created in Visual Studio 2017 is used, a build error may occur.
For details, refer to the following section.
Page 613 A build error occurred when using a sample program created in Visual Studio 2017

Sample file
The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [Vc] - [SampleENG] sample.sln

6 SAMPLE PROGRAMS
550 6.7 Visual C++ .NET (MFC) Sample Programs
Screen
The following explains the settings on the sample program screen.

Item Description
Control Select the control to be used.
[Open Communication] button Open the communication line.
[GetCpuType] button Read the programmable controller CPU model.
Device Name Enter the device to be read/written.
Device Value Enter the device value to be written. 6
[Close Communication] button Close the communication line.
[GetDevice] button Read the data of the device entered into the "Device Name" text box.
[SetDevice] button Write the data of the device entered into the "Device Name" text box.
Return Value Display the function execution result.
Output Data Upper Display the CPU model code or the read device value.
Lower Display the CPU model.

6 SAMPLE PROGRAMS
6.7 Visual C++ .NET (MFC) Sample Programs 551
 Custom interface
This sample program is a program to read a model of connected CPU and read/write device values using the ActUtlType
control or ActProgType control with the custom interface.

How to use the sample program

The operation is the same as that for the dispatch interface. (Page 550 How to use the sample program)

Considerations for using the sample program

• When using the ActUtlType control, set the logical station number "2" for the Ethernet communication information in
Communication Setup Utility before executing the sample program.
• When changing the control to be used, close the communication line by clicking the [Close Communication] button, change
the control, and reopen the line.
• If a sample program created in Visual Studio 2017 is used, a build error may occur.
For details, refer to the following section.
Page 613 A build error occurred when using a sample program created in Visual Studio 2017

Sample file
The sample programs are installed into the following folders at default installation.
Folder name File name
[User specified folder] - [Act] - [Samples] - [Vc] - [CustomSampleENG] CustomSample.sln

Screen
The settings on the screen are the same as those for the dispatch interface. (Page 551 Screen)

6 SAMPLE PROGRAMS
552 6.7 Visual C++ .NET (MFC) Sample Programs
Troubleshooting function sample program
This sample program is a program to perform the troubleshooting function using the ActSupportMsg control.

How to use the sample program

1. Load the form.

2. Enter the error code into the "ErrorCode" text box to display the error description.

3. Click the [GetErrorMessage] button to display the error description and corrective action on the text box for displaying the
error description.
Displayed error descriptions and corrective actions are the same as the descriptions on Page 555 Error Codes
Returned by Controls.

4. Click the [Exit] button to exit the sample program.

Considerations for using the sample program

• For error codes to be entered into the "ErrorCode" text box, enter the error code described on Page 555 Error Codes
Returned by Controls (0x********), or enter it in decimal number.
• If a sample program created in Visual Studio 2017 is used, a build error may occur. 6
For details, refer to the following section.
Page 613 A build error occurred when using a sample program created in Visual Studio 2017

Sample file
The sample program is installed in the following folder when the default pass is selected.
Folder name File name
[User specified folder] - [Act] - [Samples] - [Vc] - [Sample_SupportENG] Sample_Support.sln

Screen
The following explains the settings on the sample program screen.

(1)

Item Description
ErrorCode Enter the error code.
[GetErrorMessage] button Read the error description and corrective action of the error code entered into the "ErrorCode" text box.
[Exit] button Exit the sample program.
(1) (Error definition displaying text box) Display the error description and corrective action of the error code entered into the "ErrorCode" text box.

6 SAMPLE PROGRAMS
6.7 Visual C++ .NET (MFC) Sample Programs 553
 Logging file transfer sample program
This sample program is a program to transfer a logging file using the ActUtlDataLogging control or ActProgDataLogging
control.
This sample program was created on Visual C++ .NET (Visual Studio 2010) or Visual C++ .NET (Visual Studio 2017).

How to use the sample program

The operation is the same as that for Visual Basic .NET(Visual Studio 2010).(Page 546 How to use the sample program)

Sample file list

The sample programs are installed into the following folders at default installation.

■For Visual C++ .NET (Visual Studio 2010)

Folder name File name
[User specified folder] - [Act] - [Samples] - [Vc] - [CustomSampleDataLogging2010] CustomSampleDataLogging2010.sln
[User specified folder] - [Act] - [Samples] - [Vc] - [SampleDataLogging2010] SampleDataLogging2010.sln

■For Visual C++ .NET (Visual Studio 2017)

Folder name File name
[User specified folder] - [Act] - [Samples] - [Vc] - [CustomSampleDataLogging2017] CustomSampleDataLogging2017.sln
[User specified folder] - [Act] - [Samples] - [Vc] - [SampleDataLogging2017] SampleDataLogging2017.sln

Screen
The screen is the same as that for Visual Basic .NET(Visual Studio 2010).
(Page 546 Screen)

6 SAMPLE PROGRAMS
554 6.7 Visual C++ .NET (MFC) Sample Programs
7 ERROR CODES
This chapter explains the error codes returned by controls and the error codes returned by CPUs, modules, and network
boards.

7.1 Error Codes Returned by Controls

The following table shows the error codes returned by controls.
Error code Error description Corrective action
0x00000000 Normal end -
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.
7
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.
• Check the settings in the communication settings utility.
• Check the programmable controller, unit settings, status of the cable, etc.
• Close and Open again.
• Exit the program and restart the personal computer.
0x01010010 Programmable controller No. error • Check the station number set on the communication setup 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.
• Exit the program and restart the personal computer.
• 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 that the CPU type setting is correct.
• Exit the program and restart the personal computer.
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

7 ERROR CODES
7.1 Error Codes Returned by Controls 555
 Error code Error description Corrective action
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.
• Exit other programs and secure free memory area.
• Reinstall MX Component.
0x01800005 Resource securing error • Exit the program and restart the personal computer.
• Exit other programs and secure free memory area.
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.
• Reinstall MX Component.
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.
• Reinstall MX Component.
0x01801005 Specified port error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
0x01801007 Specified CPU error • Check the CPU type set to ActCpuType.
• Check that the system configuration is not an unsupported configuration.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
• Check the packet type set to ActPacketType.
0x01801008 Target station access error • Review the target station.
0x01801009 Registry open failure • Exit the program and restart the personal computer.
Failed while opening data key of the registry. • Reinstall MX Component.
0x0180100A Packet Type error • Recheck the ActPacketType.
The packet type specified is incorrect. • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Reinstall MX Component.
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.
• Reinstall MX Component.
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.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
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.

7 ERROR CODES
556 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
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.
• Exit the program and restart the personal computer.
0x01802008 Write Protect error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
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
7
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.
• Reinstall MX Component.
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).
• Exit the program and restart the personal computer.
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.

7 ERROR CODES
7.1 Error Codes Returned by Controls 557
 Error code Error description Corrective action
0x01802022 Pattern error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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
0x0180202B Version Control error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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 Unit 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
E2PROM
0x01802038 Clock data read/write error • Do not execute clock data read/write.
The clock data read/write method was executed for the
programmable controller CPU which does not have the
clock devices.
0x01802039 Trace not completed error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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

7 ERROR CODES
558 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
0x0180204D Detached during RUN state error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
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 7
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.
programmable controller CPU.
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.
• Reinstall MX Component.
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.

7 ERROR CODES
7.1 Error Codes Returned by Controls 559
 Error code Error description Corrective action
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.
• Make Ethernet board and protocol settings on the control panel of the OS.
• Right-click and select "Run as administrator" when starting the
application.
• Exit the program and restart the personal computer.
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.
• Exit the program and restart the personal computer.
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.
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.
• Exit the program and restart the personal computer.
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 • Review the time-out value of the property.
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.
• Exit the program and restart the personal computer.
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.
0x01808104 Overlap Event Close error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Exit the program and restart the personal computer.
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. • Perform Close once and execute Open again.
0x01808301 Receive error • Review the system, e.g. programmable controller CPU, module setting
Data receive failed. and cable status.
• Review the time-out value of the property.
• Review the time-out value on the communication settings utility.
• Retry the method.
• Exit the program and restart the personal computer.
0x01808302 Not Sent error • Exit the program and restart the personal computer.
• Reinstall MX Component.
0x01808303 Error in retrieving Overlap Event • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.

7 ERROR CODES
560 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
0x01808402 Signal Line Control error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Exit the program and restart the personal computer.
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.
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 • Review the time-out value of the property.
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.
• Retry the method. 7
• Perform Close once and execute Open again.
• Exit the program and restart the personal computer.
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.
• Reinstall MX Component.
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
• Retry the method.
Data receive failed.
• Exit the program and restart the personal computer.
0x01808505 USB Driver Timeout error • Recheck the timeout value.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Reinstall MX Component.
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.

7 ERROR CODES
7.1 Error Codes Returned by Controls 561
 Error code Error description Corrective action
0x01809002 GX Simulator2 start error • Exit the program and restart the personal computer.
• Reinstall MX Component.
0x01809003 GX Simulator2 start time-out error
0x01809004 GX Simulator2 stop error
0x01809005 GX Simulator2 start error
0x01809007 GX Simulator2 stop error
0x01809008 GX Simulator2 start 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.
0x01809009 GX Simulator2 start error
The simulation of only one project that can be started has
started.
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.
0x01809021 GX Simulator2 start 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.
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 Secure error • Close the other applications.
Failed in securing memory for the monitoring server. • Increase the system memory.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Reinstall MX Component.
0x02000006 Monitoring Server Startup error • Start the Monitoring Server.
Monitoring Server is not started. • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Reinstall MX Component.
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 Error Securing Memory
Failed in securing the memory.
0x03000004 DLL read error
Failed in reading DLL.
0x03000005 Error in securing Resources.
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.

7 ERROR CODES
562 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
0x03010005 Filename error • Specify a shorter filename.
The specified filename is too long. • Exit the program and restart the personal computer.
• Reinstall MX Component.
0x03010006 File does not exist error • Check the file name.
The specified file does not exist. • Check if the file exists or not.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Reinstall MX Component.
0x03010009 File does not exist error
The specified file does not exist.
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 Filename error • Check the file name.
The specified filename is incorrect. • Exit the program and restart the personal computer.
• Reinstall MX Component.
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 7
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.
0x03010015 File Type error
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.

7 ERROR CODES
7.1 Error Codes Returned by Controls 563
 Error code Error description Corrective action
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.
0x03FF0000 Initialization error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
0x03FF000C Table Initialization error
Failed in initializing TfieldInformation 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

7 ERROR CODES
564 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
0x04000001 No command error • Check the CPU type set to ActCpuType.
The specified CPU type cannot be used to perform • Check whether the system configuration is supported or not.
processing. • Exit the program and restart the personal computer.
• Reinstall MX Component.
0x04000002 Memory lock error • Exit the program and restart the personal computer.
Failed in locking memory. • Reinstall MX Component.
0x04000003 Memory Secure error
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.
• Reinstall MX Component.
0x04000005 Securing Resources 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 7
The intermediate code of the code to be converted was
insufficient.
0x04010004 Intermediate Code Data error
The intermediate code to be converted is incorrect.

7 ERROR CODES
7.1 Error Codes Returned by Controls 565
 Error code Error description Corrective action
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.
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
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.

7 ERROR CODES
566 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
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.
0x04021007 Other errors (Other errors generated during the conversion
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 7
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.
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.
0x04031008 Other errors (Other errors generated during the conversion
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 CAD data to be
converted.
0x04040006 Abnormal Command Code
There is abnormal command code in the CAD data to be
converted.
0x04040007 Device No. error
The device number is out of range.

7 ERROR CODES
7.1 Error Codes Returned by Controls 567
 Error code Error description Corrective action
0x04040008 Step No. error • Exit the program and restart the personal computer.
The step number is out of range. • Reinstall MX Component.
0x04040009 The 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.
0x04040010 Other errors (Other errors generated during the conversion
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.
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 CAD data to be
converted.
0x04041007 Abnormal Command Code
There is abnormal command code in the CAD data to be
converted.
0x04041008 Device No. error
The device number is out of range.
0x04041009 Step No. error
The step number is out of range.
0x0404100A The specified circuit size exceeded error
1 circuit block is too big.
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.

7 ERROR CODES
568 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
0x04041010 Statement error • Exit the program and restart the personal computer.
The statement data to be converted is incorrect. • Reinstall MX Component.
0x04041011 Other errors (Other errors generated during the conversion
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.
0x04051003 Other errors (The errors generated during the conversion of
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.
0x04052003 Other errors (The errors generated during the conversion of
the Device Character String to Device Representation
Code) 7
0x04053001 Device Representation error
The classification specified for the device intermediate code
is incorrect.
0x04053002 Device Representation error • Exit the program and restart the personal computer.
The classification specified for the extended specification • Reinstall MX Component.
device intermediate code is incorrect.
0x04053003 Device Representation error
The rectification part specified for the device is incorrect.
0x04053004 Device Representation error
The rectification part specified for the extended device is
incorrect.
0x04053005 Other errors (The errors generated during the conversion of
the Device Representation Code to Device Character
String)
0x04064001 Abnormal Device Intermediate Code error
The intermediate code for the device is incorrect.
0x04064002 Other errors (Other errors generated during the conversion
of the Intermediate code for the Device to Device Name)
0x04065001 Abnormal Device Name error
The classification specified for the intermediate code of the
device is incorrect.
0x04065002 Abnormal Device Name error
The classification for the intermediate code of the extended
specification device is incorrect.
0x04065003 Other errors (Other errors generated during the conversion
of the device name to Intermediate code)
0x04066001 Device Intermediate Code error
The intermediate code for the device is incorrect.
0x04066002 Other errors (Other errors generated during the conversion
of the device intermediate code to device representation
code.)

7 ERROR CODES
7.1 Error Codes Returned by Controls 569
 Error code Error description Corrective action
0x04067001 Device Representation error • Exit the program and restart the personal computer.
The classification specified for the intermediate code of the • Reinstall MX Component.
device is incorrect.
0x04067002 Device Representation error
The classification for the intermediate code of the extended
specification device is incorrect.
0x04067003 Device Representation error
The rectification part specified for the device is incorrect.
0x04067004 Device Representation error
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.
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

7 ERROR CODES
570 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
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.
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.
0x04074303 Error in Common Parameter Block No. 1003
0x04074304 Error in Common Parameter Block No. 1008
0x04074305 Error in Common Parameter Block No. 1100
0x04074306 Error in Common Parameter Block No. 2001
The device intermediate code specified does not exist.
0x04074307 Error in Common Parameter Block No. 3000
0x04074308 Error in Common Parameter Block No. 3002
0x04074309 Error in Common Parameter Block No. 3004
The settings for the annunciator display mode is incorrect. 7
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
0x04074310 Error in Common Parameter Block No. 5NM1 • Exit the program and restart the personal computer.
• Reinstall MX Component.
0x04074311 Error in Common Parameter Block No. 5NM2
0x04074312 Error in Common Parameter Block No. 5NM3
0x04074313 Error in Common Parameter Block No. 6000
0x04074314 Error in Common Parameter Block No. FF18
Link parameter Capacity is not set.
0x04074315 Error in Common Parameter Block No. FF25
Calculation circuit check is not set.
0x04074316 Error in Common Parameter Block No. FF30
Sampling Trace Data is not created.
0x04074317 Error in Common Parameter Block No. FF31
Status latch data is not created.
0x04074318 Error in Common Parameter Block No. F42
Timer processing points are not set.
0x04074319 Error in Common Parameter Block No. FF30
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.

7 ERROR CODES
7.1 Error Codes Returned by Controls 571
 Error code Error description Corrective action
0x04074401 Error in Conversion of CPU Parameter Block • Exit the program and restart the personal computer.
• Reinstall MX Component.
0x04074402 Error in CPU Parameter Block No.1001
0x04074403 Error in CPU Parameter Block No.1003
0x04074404 Error in CPU Parameter Block No.1008
0x04074405 Error in CPU Parameter Block No.1100
0x04074406 Error in CPU Parameter Block No. 2001
0x04074407 Error in CPU Parameter Block No. 3000
0x04074408 Error in CPU Parameter Block No. 3002
0x04074409 Error in CPU Parameter Block No. 3004
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
The specified network type is not supported.
0x04074410 Error in CPU Parameter Block No. 5NM1 • Exit the program and restart the personal computer.
• Reinstall MX Component.
0x04074411 Error in CPU Parameter Block No. 5NM2
The specified network type is not supported.
0x04074412 Error in CPU Parameter Block No. 5NM3
0x04074413 Error in CPU Parameter Block No. 6000
0x04074414 Error in CPU Parameter Block No. FF18
0x04074415 Error in CPU Parameter Block No. FF25
0x04074416 Error in CPU Parameter Block No. FF30
0x04074417 Error in CPU Parameter Block No. FF31
0x04074418 Error in CPU Parameter Block No. FF42
0x04074419 Error in CPU Parameter Block No. FF43
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
0x04075001 Common Data Conversion error • Exit the program and restart the personal computer.
Failed while converting the device memory settings portion. • Reinstall MX Component.
0x04075002 Common Data Conversion error
Failed while converting the device memory settings portion.
0x04075003 Common Data Conversion error
Device memory data portion did not exist.
0x04075101 CPU Data Conversion error
Failed while converting the settings portion of the device
memory.
0x04075102 CPU Data Conversion error
Failed while converting the data portion of the device
memory.
0x04076001 Common Data Conversion error
Failed while converting the settings portion of the device
comments.
0x04076002 Common Data Conversion error
Failed while converting the data portion of the device
comments.
0x04076101 CPU Data Conversion error
Failed while converting the settings portion of the device
comments.
0x04076102 CPU Data Conversion error
Failed while converting the settings portion of the device
comments.

7 ERROR CODES
572 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
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.
0x04077002 Common Data Conversion error
Failed during the conversion of sampling trace data portion.
0x04077101 CPU Data Conversion error
Failed during the conversion of sampling trace settings
portion.
0x04077102 CPU Data Conversion error
Failed during the conversion of sampling trace data portion.
0x04078001 Common Data Conversion error
Failed in the conversion of the status latch settings portion.
0x04078002 Common Data Conversion error
Failed in the conversion of the status latch data portion.
0x04078101 CPU Data Conversion error
Failed in the conversion of the status latch settings portion.
0x04078102 CPU Data Conversion error
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.
• Reinstall MX Component.
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 7
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
Indirect Address storage area is not secured.
0x0407C005 Error in Conversion of Indirect Address to Device Character
String
Device Character String storage area is not secured.
0x0407C006 Error in Conversion of Device Character String to Indirect • Exit the program and restart the personal computer.
Address • Reinstall MX Component.
Indirect Address storage area is not secured.
0x0407C007 Error in Conversion of Intermediate Code to Device Name
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
Intermediate Code storage area is not secured.
0x0407C00B Error in Conversion of Intermediate Code to Indirect
Address
Indirect Address storage area is not secured.
0x0407C00C Error in Conversion of Indirect Address to Intermediate
Code
Intermediate Code storage area is not secured.
0x0407C00D CPU Type error
The specified CPU type is not supported.

7 ERROR CODES
7.1 Error Codes Returned by Controls 573
 Error code Error description Corrective action
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 CPU Data Conversion error
Error in Conversion of SFC trace condition settings portion.
0x0407D102 CPU Data Conversion error
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.
0x04090002 File Type error
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.
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 to store the data after conversion is insufficient.
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.
• Reinstall MX Component.
0x040A1002 Step No. out of range error
0x040A1003 Step Not Used / No Output error
0x040A1004 Transition No. out of range
0x040A1005 Maximum Number Exceeded error
0x040A1006 Microcontroller Program space error
0x040A1007 Non-SFC Program error

7 ERROR CODES
574 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
0x040B0001 Insufficient Intermediate Code Storage Space • Exit the program and restart the personal computer.
The space to store the data after conversion is insufficient. • Reinstall MX Component.
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 No 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 • Reinstall MX Component. 7
0x10000007 File Access Denied error
0x10000008 Disk Full error
0x10000009 File Delete 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.
• Exit the program and restart the personal computer.
0x1000000D Folder Creation error • Exit the program and restart the personal computer.
0x1000000E Folder/ File Type error • Reinstall MX Component.

0x1000000F Offset Address error

0x10000010 Request Cancel
Cancel Process has occurred.
0x10000011 Memory securing error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Reinstall MX Component.
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.
• Exit the program and restart the personal computer.
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.
• Reinstall MX Component.
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.
• Exit other programs and secure free memory area.
• Reinstall MX Component.

7 ERROR CODES
7.1 Error Codes Returned by Controls 575
 Error code Error description Corrective action
0x1000001F File Type error • Exit the program and restart the personal computer.
• Reinstall MX Component.
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.
• Reinstall MX Component.
0x10000030 Multiple Device Registration error
0x10000031 Device Not Registered error
0x10000032 Specified device error • Review the specified device data.
• Exit the program and restart the personal computer.
0x10000033 Specified device range error
• Exit other programs and secure free memory area.
0x10000034 File Write error • Exit the program and restart the personal computer.
• Reinstall MX Component.
0x10000040 Server start failed.
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.
0x10000059 Timeout 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.
0x1000005A System number error • Check the system number set on the communication setup utility
0x8001000C Data out of the allowable setting range is specified. • Review the value of the property.
0x80010016 • Set it again on the communication settings utility.

0x80010101 Timeout error • Check the property timeout value.

• Check the settings in the communication settings utility.
• Check the unit settings, state of the cable, etc.
• Close and Open again.
• Exit the program and restart the personal computer.
0x80020001 Type of data is invalid. • Review the value of the property.
• Set it again on the communication settings utility.
0x80020002 Range of the data is incorrect.
0x80030001 The specification of the communication port is incorrect. • Review the communication port value of the property.
• Set it again on the communication settings utility.
0x80030002 The specification of the Transmission speed is incorrect. • Review the transmission speed value of the property.
• Set it again on the communication settings utility.
0x80030003 The specification of the Data bit length is incorrect. • Review the data bit length of the property.
• Set it again on the communication settings utility.
0x80030004 The specification of the parity is incorrect. • Review the parity value of the property.
• Set it again on the communication settings utility.
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.
0x80030006 The specification of the wait time is incorrect. • Review the wait time of the property.
• Set it again on the communication settings utility.

7 ERROR CODES
576 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
0x80030007 The specification of the CR/LF is incorrect. • Review the CR/LF of the property.
• Set it again on the communication settings utility.
0x80030008 The specification of the timeout is incorrect. • Review the time-out value of the property.
• Set it again on the communication settings utility.
0x80030009 The specification of the station number is incorrect. • Review the station number of the property.
• Set it again on the communication settings utility.
0x8003000A USB communication setting is invalid. • Review the value of the property.
• Set it again on the communication settings utility.
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.
• Exit the program and restart the personal computer.
0x80200203 Memory Secure error • Exit the program and restart the personal computer.
• Exit other programs and secure free memory area.
0x80201001 Specified CPU error • Check the CPU type set to ActCpuType.
• Check that the system configuration is not an unsupported configuration.
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.
• Exit other programs and secure free memory area.
• Reinstall MX Component.
0x80201106 Error in Communication object generation • Exit the program and restart the personal computer.
• Reinstall MX Component.
0x80201201 Not yet open error • After executing the Open method, execute the corresponding method. 7
The Open method is not yet executed.
0x80201203 Memory Secure error • Exit the program and restart the personal computer.
• Exit other programs and secure free memory area.
0x80204203 Memory Secure error
0x80205203 Memory Secure error
0x80205001 Specified CPU error • Check the CPU type set to ActCpuType.
• Check that the system configuration is not an unsupported configuration.
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.
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.
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.
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.
• Exit other programs and secure free memory area.
• Reinstall MX Component.

7 ERROR CODES
7.1 Error Codes Returned by Controls 577
 Error code Error description Corrective action
0x8020A203 Memory Secure error • Exit the program and restart the personal computer.
• Exit other programs and secure free memory area.
0x80A00101 Not yet open error • After executing the Open method, execute the corresponding method.
The Open method is not yet executed.
0x80A00104 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.
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
The Open method was executed in the open status. method after performing Close.
0xF0000004 Not yet open error • After executing the Open method, execute the corresponding method.
The Open method is not yet executed.
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.
• Exit the program and restart the personal computer.
• 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.
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
EntryDeviceStatus method was more than 20.
0xF1000009 Monitored device data registration error • After making deregistration in the FreeDeviceStatus method, execute the
EntryDeviceStatus method again.

7 ERROR CODES
578 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
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) 7
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.
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.
• Reinstall MX Component.

7 ERROR CODES
7.1 Error Codes Returned by Controls 579
 Error code Error description Corrective action
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.
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.
• Exit the program and restart the personal computer.
• Reinstall Component.
0xF2010002 QJ71C24 did not receive the specified connection method. • Check whether the settings of QJ71C24 and the MX Component are
Causes can be the following. matching.
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.)

7 ERROR CODES
580 7.1 Error Codes Returned by Controls
Error code Error description Corrective action
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
settings type and change the contents of the detailed settings that were
set using the wizard in case of utility settings type.
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
settings type and change the contents of the detailed settings that were
set using the wizard in case of utility settings type.
0xF202**** There was a communication failure. • Check whether the cable is broken.
Following causes can be considered depending on the
status.
•
•
Check whether the specified port is not supported.
Check whether correct COM port is set.
7
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.
• Reinstall MX Component.
• Start Label Utility, please check System label information.
0xF3000003 MMS Service not started • Exit the program and restart the personal computer.
• Reinstall MX Component.
0xF3000004 The specified LabelSpace is currently being used and • Please retry.
cannot be opened.
0xF3000005 Label data access timeout error • Please retry.
• Reduce system label definition.
0xF3000006 MUTEX acquisition error • Exit the program and restart the personal computer.
Acquisition of MUTEX to exercise exclusive control failed.
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 manual.
MELSEC Data Link Library Reference Manual

7 ERROR CODES
7.1 Error Codes Returned by Controls 581
 7.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 582 Error code list.
Check the considerations described in Page 582 Considerations for confirming error codes, and refer to
Page 582 Error code list.

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.
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
*1
0x010F0000 to 0x010FFFFF GOT

*1 Refer to "Point"
*2 The error codes are also described in the following section.
Page 555 Error Codes Returned by Controls

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

7 ERROR CODES
582 7.2 Error Codes Returned by CPUs, Modules, and Network Boards
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.
Error code Error description Corrective action
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.
0x010A4000 to 0x010A4FFF For the errors and their corrective actions, refer to the following manual.
MELSEC iQ-R CPU Module User's Manual (Application)

7.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
termination
The function processing is normally terminated.
7
S_FALSE Normal The function processing (as ActiveX control) is normally terminated, but the operation (access to programmable
termination controller) failed.
E_POINTER Abnormal The pointer passed to the function is abnormal.
termination
E_OUTOFMEMORY Abnormal Memory reservation or object creation failed.
termination
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.

7.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.
• Reinstall MX Component.
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.

7 ERROR CODES
7.3 HRESULT Type Error Codes 583
 APPENDIX
Appendix 1 Connection System of Callback Function
This section explains the connection system of the callback function for modem communication using Q series-compatible
C24.
The callback function enables access from MX Component to a programmable controller CPU by the line reconnection
(callback) performed from Q series-compatible C24 after the line connection from MX Component.
For details of the callback function, refer to the following manual.
Q Corresponding Serial Communication Module User's Manual (Application)
Connection system Description Telephone usage
charge
Auto line connect Select this when the callback function is not set to Q series-compatible C24. Personal computer side
Auto line connect (Callback fixation) Connect the line without using the callback function when the callback function is set to
Q series-compatible C24.
Only personal computers whose telephone number is registered in the buffer memory
(2101H) of Q series-compatible C24 can be connected.
Auto line connect (Callback number Connect the line without using the callback function when the callback function is set to
specification) Q series-compatible C24.
Only personal computers whose telephone number is specified by MX Component can
be connected.
Callback connect (Fixation) Callback only personal computers whose telephone number is registered in the buffer Q series-compatible C24
memory (2101H) of Q series-compatible C24. side
Callback connect (Number Callback only personal computers whose telephone number is specified by MX
specification) Component.
Callback request (Fixation) Send a callback request from the selected personal computer to callback personal
computers whose telephone number is registered in the buffer memory (2101H) of Q
series-compatible C24. (The callback is not performed on the personal computer which
is connected first.)
Callback request (Number Send a callback request from the selected personal computer to callback personal
specification) computers whose telephone number is specified by MX Component. (The callback is
not performed on the personal computer which is connected first.)
Callback reception waiting When connecting a line with callback request (fixation, number specification),
"Callback reception waiting" is selected on the callback target personal computer to
connect the line.

APPX
584 Appendix 1 Connection System of Callback Function
Appendix 2 Programming 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))

A
■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
Appendix 2 Programming Examples for Monitoring Word Device Status 585
 When using Visual C++ .NET
The following is a programming example to monitor D0 for -10, D1 for 0, and D2 for 10 using Visual C++ .NET

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;
// 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;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
//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
586 Appendix 2 Programming Examples for Monitoring Word Device Status
When using Visual C# .NET
The following is a programming example to monitor D0 for -10, D1 for 0, and D2 for 10 using Visual C# .NET.

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;
// Sets the checked device value "0" for D1.
iInputData[1] = 0;
// Sets the checked device value "10" for D2.
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
Appendix 2 Programming Examples for Monitoring Word Device Status 587
 Appendix 3 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.
The following shows communication routes for retries at a time-out error occurrence.

Serial communication
■Configuration
1 2
Connected station Connected module Relayed module
CPU

3 Relayed network
4
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for retries at a time-out error occurrence.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
1. 2. Connected 3. Relayed network 4. Relayed station CPU
Connected module RCPU RCCPU R motion CPU LHCPU FX5CPU
station CPU
RCPU, RCCPU R series-compatible CC IE TSN     
C24
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connected module QCPU (Q QCCP LCPU QSCP Q motion CPU FXCP
station CPU mode) U U U
RCPU, RCCPU R series-compatible CC IE TSN      
C24 CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      

APPX
588 Appendix 3 Time-Out Periods
1. Connected 2. Connected 3. Relayed network 4. Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode) Q series-compatible CC IE TSN     
C24
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     

1. Connected 2. Connected 3. Relayed network 4. Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
QCPU (Q mode) Q series-compatible CC IE TSN      
C24
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connected module RCPU RCCPU R motion CPU LHCPU FX5CPU
station CPU
LCPU L series-compatible CC IE TSN     
C24
CC IE Field     
CC IE Control     
MELSECNET/H      A
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connected module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
station CPU mode) CPU
LCPU L series-compatible CC IE TSN      
C24
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      

APPX
Appendix 3 Time-Out Periods 589
 1. 2. Connected 3. Relayed network 4. Relayed station CPU
Connected module RCPU RCCPU R motion CPU LHCPU FX5CPU
station CPU
FXCPU FX extended port CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connected module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
station CPU mode) CPU
FXCPU FX extended port CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      

APPX
590 Appendix 3 Time-Out Periods
CPU COM communication
■Configuration
1
Connected station Relayed module
CPU

2 Relayed network
3
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for retries at a time-out error occurrence.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FX5CPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
FX5CPU CC IE TSN
CC IE Field












A
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode) CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

APPX
Appendix 3 Time-Out Periods 591
 1. Connected 2. Relayed network 3. Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
Q motion CPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

APPX
592 Appendix 3 Time-Out Periods
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FXCPU CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      *1

*1 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.

APPX
Appendix 3 Time-Out Periods 593
 CPU USB communication
■Configuration
1
Connected station Relayed module
CPU

2 Relayed network
3
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for retries at a time-out error occurrence.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
RCPU, R motion CPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
RCPU, R motion CPU CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LHCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU QCPU (Q mode) QCCPU LCPU QSCPU Q motion CPU FXCPU
LHCPU CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

APPX
594 Appendix 3 Time-Out Periods
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
*1
FX5CPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode) CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
A
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCPU (Q mode) CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

APPX
Appendix 3 Time-Out Periods 595
 1. Connected 2. Relayed network 3. Relayed station CPU
station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCCPU CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

*1 Only FX5UJCPU can be accessed.

*2 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.

APPX
596 Appendix 3 Time-Out Periods
CC-Link G4 communication
■Configuration
1
Connected station CC-Link module Relayed module
CPU

CC-Link
2 Relayed network
G4 module
3
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for retries at a time-out error occurrence.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
• When CC-Link G4-S3 module is Q mode and connected station CPU is QCPU (Q mode) or QCCPU
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode) CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

APPX
Appendix 3 Time-Out Periods 597
 1. Connected 2. Relayed network 3. Relayed station CPU
station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCCPU CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

• When CC-Link G4-S3 module is Q mode and connected station CPU is LCPU
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

APPX
598 Appendix 3 Time-Out Periods
Modem communication (when using FXCPU)
■Configuration
1
Connected station Relayed module
CPU

Subscrib
Modem er's line Modem 2 Relayed network
3
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for retries at a time-out error occurrence.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FXCPU CC IE TSN      
A
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

APPX
Appendix 3 Time-Out Periods 599
 Modem communication (when using Q series-compatible C24 or QC24N)
■Configuration
1 2
Connected station Relayed module
Connected module
CPU

Subscrib
Modem er's line Modem 3 Relayed network
4
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for retries at a time-out error occurrence.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
1. Connected 2. Connected 3. Relayed network 4. Relayed station CPU
station CPU module RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode) Q series-compatible CC IE TSN     
C24
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode)

1. Connected 2. Connected 3. Relayed network 4. Relayed station CPU

station CPU module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
mode) CPU
QCPU (Q mode) Q series-compatible CC IE TSN      
C24
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)

APPX
600 Appendix 3 Time-Out Periods
Modem communication (when using L series-compatible C24)
■Configuration
1 2
Connected station Relayed module
Connected module
CPU

Subscrib
Modem er's line Modem 3 Relayed network
4
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for retries at a time-out error occurrence.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
1. 2. Connected 3. Relayed network 4. Relayed station CPU
Connect module RCPU RCCPU R motion CPU LHCPU FX5CPU
ed
station
CPU
LCPU L series-compatible CC IE TSN     
C24
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     
(Independent mode) A
1. 2. Connected 3. Relayed network 4. Relayed station CPU
Connect module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
ed mode) CPU
station
CPU
LCPU L series-compatible CC IE TSN      
C24
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      
(Independent mode)

APPX
Appendix 3 Time-Out Periods 601
 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.
The following shows communication routes for retries at a receive data error occurrence.

Ethernet communication
■Configuration
1 2
Connected station Connected module Relayed module
CPU

3 Relayed network
Ethernet
4
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for retries at a receive data error occurrence.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
1. 2. Connected 3. Relayed network 4. Relayed station CPU
Connect module RCPU RCCPU R motion CPU LHCPU FX5CPU
ed
station
CPU
RCPU, R series-compatible CC IE TSN     
RCCPU E71, RCPU, RCCPU
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
ed mode) CPU
station
CPU
RCPU, R series-compatible CC IE TSN      
RCCPU E71, RCPU, RCCPU CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

APPX
602 Appendix 3 Time-Out Periods
1. 2. Connected 3. Relayed network 4. Relayed station CPU
Connect module RCPU RCCPU R motion CPU LHCPU FX5CPU
ed
station
CPU
LHCPU LHCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
ed mode) CPU
station
CPU
LHCPU LHCPU CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module RCPU RCCPU R motion CPU LHCPU FX5CPU
ed
station A
CPU
FX5CPU FX5CPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
ed mode) CPU
station
CPU
FX5CPU FX5CPU CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

APPX
Appendix 3 Time-Out Periods 603
 1. 2. Connected 3. Relayed network 4. Relayed station CPU
Connect module RCPU RCCPU R motion CPU LHCPU FX5CPU
ed
station
CPU
QCPU (Q Q series-compatible CC IE TSN     
mode) E71, Built-in
CC IE Field     
Ethernet port QCPU
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
ed mode) CPU
station
CPU
QCPU (Q Q series-compatible CC IE TSN      
mode) E71, Built-in
CC IE Field      
Ethernet port QCPU
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module RCPU RCCPU R motion CPU LHCPU FX5CPU
ed
station
CPU
LCPU Built-in Ethernet CC IE TSN     
port LCPU
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
ed mode) CPU
station
CPU
LCPU Built-in Ethernet CC IE TSN      
port LCPU
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

APPX
604 Appendix 3 Time-Out Periods
1. 2. Connected 3. Relayed network 4. Relayed station CPU
Connect module RCPU RCCPU R motion CPU LHCPU FX5CPU
ed
station
CPU
RCPU CC-Link IE TSN CC IE TSN     
module
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
ed mode) CPU
station
CPU
RCPU CC-Link IE TSN CC IE TSN      
module
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

APPX
Appendix 3 Time-Out Periods 605
 Time-out errors at fixed time in 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.
The following shows communication routes for a time-out error occurrence at the fixed time in the ACT control.

Serial communication
■Configuration
1 2
Connected station Connected module Relayed module
CPU

3 Relayed network
4
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for a time-out error occurrence at the fixed time in the ACT control.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
1. 2. Connected 3. Relayed network 4. Relayed station CPU
Connect module RCPU RCCPU R motion CPU LHCPU FX5CPU
ed
station
CPU
RCPU, R series-compatible CC IE TSN     
RCCPU C24
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
ed mode) CPU
station
CPU
RCPU, R series-compatible CC IE TSN      
RCCPU C24
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      

APPX
606 Appendix 3 Time-Out Periods
1. 2. Connected 3. Relayed network 4. Relayed station CPU
Connect module RCPU RCCPU R motion CPU LHCPU FX5CPU
ed
station
CPU
QCPU (Q Q series-compatible CC IE TSN     
mode) C24
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
ed mode) CPU
station
CPU
QCPU (Q Q series-compatible CC IE TSN      
mode) C24
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module RCPU RCCPU R motion CPU LHCPU FX5CPU
ed
station A
CPU
LCPU L series-compatible CC IE TSN     
C24
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     
Multi-drop connection     

1. 2. Connected 3. Relayed network 4. Relayed station CPU

Connect module QCPU (Q QCCPU LCPU QSCPU Q motion FXCPU
ed mode) CPU
station
CPU
LCPU L series-compatible CC IE TSN      
C24
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      
Multi-drop connection      

APPX
Appendix 3 Time-Out Periods 607
 CPU COM communication
■Configuration
1
Connected station Relayed module
CPU

2 Relayed network
3
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for a time-out error occurrence at the fixed time in the ACT control.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FX5CPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
FX5CPU CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode), CC IE TSN     
QCCPU
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

APPX
608 Appendix 3 Time-Out Periods
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCPU (Q mode), CC IE TSN      
QCCPU
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
FXCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

*1 Only FX3G(C)CPU and FX3U(C)CPU can be accessed.

APPX
Appendix 3 Time-Out Periods 609
 CC-Link G4 communication
■Configuration
1
Connected station CC-Link module Relayed module
CPU

CC-Link
2 Relayed network
G4 module
3
Relayed station
Personal computer Relayed module
CPU

■Target/non-target communication path

The following table shows the communication routes for a time-out error occurrence at the fixed time in the ACT control.
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).
Connect CC-Link G4-S3 module in Q mode.
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCPU (Q mode) CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

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

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
QCCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

APPX
610 Appendix 3 Time-Out Periods
1. Connected 2. Relayed network 3. Relayed station CPU
station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
QCCPU CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication      
CC-Link      

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU RCPU RCCPU R motion CPU LHCPU FX5CPU
LCPU CC IE TSN     
CC IE Field     
CC IE Control     
MELSECNET/H     
Ethernet     
Serial communication     
CC-Link     

1. Connected 2. Relayed network 3. Relayed station CPU

station CPU QCPU (Q QCCPU LCPU QSCPU Q motion CPU FXCPU
mode)
LCPU CC IE TSN      
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
Serial communication       A
CC-Link      

APPX
Appendix 3 Time-Out Periods 611
 Appendix 4 Troubleshooting
This section explains the errors which may occur when using MX Component and the troubleshooting.

Error occurred 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'.
Page 37 When pasting a control to the form
Page 39 When using control without pasting it to a form (Reference setting)

Link error occurred when creating a user application in Visual

C++ .NET
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 (Visual Studio 2015)

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 (Visual Studio 2015)

For the corrective actions, refer to the following 'Point'.
Page 51 When using Visual C++ .NET

APPX
612 Appendix 4 Troubleshooting
The unstart error occurred during communication with GX
Simulator3
If GX Simulator3 communication is performed using the setting of MX Component Version 4.15R or earlier in MX Component
Version 4.16S, GX Simulator3 unstart error (0xF1000020) will occur.
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 Setup
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)

A build error occurred when using a sample program created in

Visual Studio 2017
If an MFC project or VC++.NET project in which a sample program created in Visual Studio 2017 is used, an error may occur.
The corrective actions are shown below.

1. Open the Visual Studio installer, and select a Windows 10 SDK (predetermined version) in the [Individual components]
tab to install the Windows 10 SDK.

2. Select [Project]  [Property], and change the SDK version in "Windows SDK Version" in the [General] tab to the one
installed on the personal computer.
A

APPX
Appendix 4 Troubleshooting 613
 REVISIONS
*The manual number is given on the bottom left of the back cover.
Revision date *Manual number Description
July 2012 SH(NA)-081085ENG-A Due to the transition to the e-Manual, the details on revision have been deleted.
to to
May 2019 SH(NA)-081085ENG-Q
January 2020 SH(NA)-081085ENG-R Complete revision (layout change)
■Added or modified parts
OPERATING CONSIDERATIONS, TERMS, Section 1.1, Section 2.1, Section 2.3, Section 2.4, Section
3.2, Section 4.2 to Section 4.10, Section 4.13, Section 4.15, Section 5.2, Section 5.3, Section 7.1,
Appendix 3
November 2020 SH(NA)-081085ENG-S ■Added or modified parts
SAFETY PRECAUTIONS, CONDITIONS OF USE FOR THE PRODUCT, TERMS, Section 1.1, Section
3.2, Section 4.2, Section 4.3, Section 4.4, Section 4.16, Section 5.2, Section 5.4, Appendix 3

Japanese manual number: SH-081083-S

This manual confers no industrial property rights of any other kind, nor does it confer any patent licenses. Mitsubishi Electric Corporation cannot be held
responsible for any problems involving industrial property rights which may occur as a result of using the contents noted in this manual.

 2012 MITSUBISHI ELECTRIC CORPORATION

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

615
 TRADEMARKS
Intel is either registered trademarks or trademarks of Intel Corporation in the United States and/or other countries.
Microsoft, Microsoft Access, Excel, Visual Basic, Visual C++, Visual C#, Visual Studio, Windows, Windows Vista, and
Windows XP are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.
The company names, system names and product names mentioned in this manual are either registered trademarks or
trademarks of their respective companies.
In some cases, trademark symbols such as '' or '' are not specified in this manual.

616
SH(NA)-081085ENG-S(2011)KWIX
MODEL: SW4DNC-ACT-P-E
MODEL CODE: 13JW12

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.