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,

WARNING
resulting in death or severe injury.

Indicates that incorrect handling may cause hazardous conditions,

CAUTION resulting in minor or moderate injury or property damage.

Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to
serious consequences.
Make sure that the end users read this manual and then keep the manual in a safe place for future
reference.

[Design Instructions]
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.

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.

1
 CONDITIONS OF USE FOR THE PRODUCT
(1) Mitsubishi programmable controller ("the PRODUCT") shall be used in conditions;
i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major
or serious accident; and
ii) where the backup and fail-safe function are systematically or automatically provided outside of
the PRODUCT for the case of any problem, fault or failure occurring in the PRODUCT.

(2) The PRODUCT has been designed and manufactured for the purpose of being used in general
industries.
MITSUBISHI SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT
LIMITED TO ANY AND ALL RESPONSIBILITY OR LIABILITY BASED ON CONTRACT,
WARRANTY, TORT, PRODUCT LIABILITY) FOR ANY INJURY OR DEATH TO PERSONS OR
LOSS OR DAMAGE TO PROPERTY CAUSED BY the PRODUCT THAT ARE OPERATED OR
USED IN APPLICATION NOT INTENDED OR EXCLUDED BY INSTRUCTIONS, PRECAUTIONS,
OR WARNING CONTAINED IN MITSUBISHI'S USER, INSTRUCTION AND/OR SAFETY
MANUALS, TECHNICAL BULLETINS AND GUIDELINES FOR the PRODUCT.
("Prohibited Application")
Prohibited Applications include, but not limited to, the use of the PRODUCT in;
• 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 may in its sole discretion, authorize use of the
PRODUCT in one or more of the Prohibited Applications, provided that the usage of the PRODUCT
is limited only for the specific applications agreed to by Mitsubishi and provided further that no
special quality assurance or fail-safe, redundant or other safety features which exceed the general
specifications of the PRODUCTs are required. For details, please contact the Mitsubishi
representative in your region.

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 of Robot controller

Considerations of operating system and personal computer to be used

(1) 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.

(a) 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

(b) 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.

(c) 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.

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

(1) Installation
When performing overwrite installation, install the software in the same folder where it is installed previously.

(2) Start menu

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

(3) 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

(1) Considerations for performing USB communication

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

(2) Clock data of programmable controller CPU

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

(3) Restrictions on using FXCPU

(a) When 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 earlier and 200 or later.
(b) Since FXCPU does not feature the PAUSE switch as the programmable controller CPU, an error is returned if
remote pause is specified in SetCpuStatus.
(c) Note that specifying the first I/O number of a non-existing module and executing the WriteBuffer() method will
not return an error.
(d) For the index registers (Z, V) of FXCPU, data cannot be written to 2 or more consecutive points using
WriteDeviceBlock(). (Data may be written to only one point.)

(4) Serial communication function of Q00UJ/Q00/Q00U/Q01/Q01U/Q02UCPU*1

*1 : 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.
• 1)The serial communication function of the connected CPU is valid.
• 2)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
(5) Considerations for using built-in Ethernet CPU
(a) 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.
(b) 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.

(6) 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.

(7) 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.

(8) Considerations for using FX5CPU

(a) Since FX5CPU does not feature the PAUSE switch as the programmable controller CPU, an error is returned if
remote pause is specified in SetCpuStatus.
(b) FX5CPU does not support the ReadBuffer() and WriteBuffer() methods. For writing/reading buffer memory,
specify the device (U*\G*).
(c) Multiple simultaneous communications cannot be established via the route specified by different adapter when
an adapter to be used for Ethernet direct connection is specified to establish a communication.
(d) 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

(1) 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.
If GX Simulator or GX Developer is terminated while the user program is running, the user program will not be
terminated normally.

(2) Considerations for performing MT Simulator2 communication

• After installing MT Component, install MT Developer2.
• The maximum number of connections*1 to MT Simulator2 is 4.
*1 : Including in MT Developer2.
Example) When two MT Developer2s and one MT Simulator2 are activated:
three connections can be established from MT Component.

Considerations for using Ethernet modules

(1) 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.

5
 (2) 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.)

(3) 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.)

(4) 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.
• Q series-compatible E71 module (except QJ71E71-100) whose first five digits of the serial number is
"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].

(5) Unlocking password when using QJ71E71

The range where the password can be unlocked by remote operation is up to the connection target station.
If the password is 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

1) With setting (AAAA)
2) Without setting
Ethernet
3) With setting (AAAA)
4) With setting (BBBB)
QCPU 1) 2)
(Q QJ71 QJ71 5) Without setting
mode) E71 E71

Ethernet
QCPU 3)
: Accessible
QCPU 4) QCPU 5)
(Q QJ71 (Q QJ71 (Q QJ71 : Inaccessible
mode) E71 mode) E71 mode) E71

1) Unlocking QJ71E71 password enables

access to Programmable controller CPUs in this range.

6
(6) Ethernet communication
(a) 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).

(b) 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.
 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

(1) 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

(1) Serial communication

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

(2) Considerations for connecting personal computer and serial communication module
(a) When using QJ71C24-R2 of function version A
An MX Component application can use only either 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

(1) 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.

(2) Considerations for using telephone line

(a) 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.

(b) Do not connect the line to master/slave phones.

If the handset of the slave phone is lifted while the telephone line is connecting to the master/slave phones, the
telephone line may be disconnected.

(c) Use an analog 2 wire type telephone line.

When using a digital line, use a terminal 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.

(3) Considerations for using cellular phone

(a) 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.

(b) 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

(1) Sample programs, test programs, and sample sequence programs

(a) 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.

(b) 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.

(2) 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.

(3) 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, when the programmable controller power is OFF)

(4) CheckDeviceString
Do not use the CheckDeviceString method of ACT control.

(5) ActUMsg control and ActUWzd control

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

(6) Considerations for using Ethernet modules

(a) 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.

(b) Provide an interval of at least 500ms for a period from when the Close method is executed until the Open
method is executed again.

(7) 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.

(8) Error at building sample programs

(a) 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.

(b) 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.
• "Sample\64bit" in the CD-ROM

9
 Considerations for using Microsoft® Excel®

(1) Considerations for using Excel VBA

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

(2) Considerations for using Microsoft® Excel®

(a) Occasionally, controls may not be pasted to Excel.
This symptom occurs if the cache file (temporary file) of Excel remains.
In such a case, perform the operation in the following procedure.

Operating procedure
1. Close Excel.
2. Delete "*.exd" in the Excel 8.0 folder of the temp folders. *1, *2
3. Restart Excel.
*1 : The location of temp folder differs according to the operating system.
*2 : When the corresponding folder and file are not displayed, set the settings in the folder option setting to display all files
and folders.

(b) 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 Microsoft® Access®

(1) Considerations for using Microsoft® Access®

(a) When the ACT control is pasted to an Access form and the ACT control is double-clicked or the custom control
in the property is selected, 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.)

(b) When the ACT control is pasted and the property is displayed, the displayed property name may be collapsed.
This symptom only occurs on the display of the property, and this does not affect the functions of the property.

(c) 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

(1) 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

(1) 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.

(2) 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.

RELATED MANUALS
The manuals related to this product are shown below.
Refer to the following tables when ordering required manuals.
Manual name
Description
< Manual number, model code >
MX Component Version 4 Operating Manual Explains the programming procedures, detailed explanations and
<SH-081084ENG, 13JU75> error codes of the ACT controls.
Type Q80BD-J61BT11N/Q81BD-J61BT11 CC-Link System Master/ Explains the system configuration, specifications, functions,
Local Interface Board User's Manual (For SW1DNC-CCBD2-B) handling, wiring, and troubleshooting of the type Q80BD-J61BT11N/
<SH-080527ENG, 13JR77> Q81BD-J61BT11 CC-Link system master/local interface board.
MELSECNET/H Interface Board User's Manual
Explains the system configuration, specifications, functions,
(For SW0DNC-MNETH-B)
handling, wiring, and troubleshooting of the MELSEC/H board.
<SH-080128, 13JR24>
CC-Link IE Controller Network Interface Board User’s Manual Explains the system configuration, specifications, functions,
(For SW1DNC-MNETG-B) handling, wiring, and troubleshooting of the CC-Link IE
<SH-080691ENG, 13JZ02> Controller Network board.
CC-Link IE Field Network Interface Board User’s Manual Explains the system configuration, specifications, functions,
(For SW1DNC-CCIEF-B) handling, wiring, and troubleshooting of the CC-Link IE
<SH-080980ENG, 13JZ58> Field Network board.
Explains the system configuration, specifications, functions,
MELSEC-Q C Controller Module User's Manual handling, wiring, troubleshooting, and programming and function of
<SH-081130ENG, 13JZ75> Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG,
Q26DHCCPU-LS, and Q12DCCPU-V (Extended mode).
C Controller Module User's Manual Explains the system configuration, specifications, functions,
(Hardware Design, Function Explanation) handling, wiring, and troubleshooting of Q12DCCPU-V (Basic mode)
<SH-080766ENG, 13JZ17> and Q06CCPU-V.
Explains the setting and operating method for monitoring the device
GX Simulator Version 7 Operating Manual
memory and simulating the machine side operations using GX
<SH-080468ENG, 13JU51>
Simulator.
Explains the system configuration of GX Works2 and the functions
GX Works2 Version 1 Operating Manual (Common)
common to a Simple project and Structured project such as
<SH-080779ENG, 13JU63>
parameter setting, operation method for the online function.

Remark
MX Component Version 4 Operating Manual is included on the CD-ROM of the software package in a PDF file format.
Manuals in printed form are sold separately for single purchase. Order a manual by quoting the manual number (model
code) listed in the table above.

12
Memo

13
 CONTENTS
CONTENTS

SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
OPERATING CONSIDERATIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
RELATED MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
HOW TO READ THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

CHAPTER 1 OVERVIEW 24
1.1 Outline of Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.2 Control and Function Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.2.1 Control list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.2.2 Function list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

CHAPTER 2 CONTROLS 28
2.1 Settings for Using Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.1.1 When using VBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.1.2 When using VBScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.1.3 When Using Visual Studio® .NET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.2 Programming Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2.2.1 When using VBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.2.2 When using VBScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.2.3 When using Visual Basic® .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.2.4 When using Visual C++® .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.2.5 When using Visual C#® .NET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

2.3 Device Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

2.4 Accessible Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

CHAPTER 3 PROPERTIES OF CONTROLS 57

3.1 Property List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.2 Details of Control Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS 74

4.1 Descriptions of Property Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.2 Serial Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.2.1 Serial communication when the connected station is R series-compatible C24 . . . . . . . . . . 75
4.2.2 Serial communication when the connected station is Q series-compatible C24 . . . . . . . . . . 81
4.2.3 Serial communication when the connected station is L series-compatible C24. . . . . . . . . . . 87
4.2.4 Serial communication when the connected station is FX extended port . . . . . . . . . . . . . . . . 92

4.3 Ethernet Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

4.3.1 Ethernet communication when the connected station is R series-compatible E71 (TCP) . . . 94
4.3.2 Ethernet communication when the connected station is R series-compatible E71 (UDP) . . . 97
4.3.3 Ethernet communication when the connected station is Q series-compatible E71 (TCP) . . 100
4.3.4 Ethernet communication when the connected station is Q series-compatible E71 (UDP). . 103
4.3.5 Ethernet communication when the connected station is L series-compatible E71 (TCP) . . 106

14
 4.3.6 Ethernet communication when the connected station is L series-compatible E71 (UDP) . . 109
4.3.7 Ethernet communication when the connected station is RCPU (TCP) . . . . . . . . . . . . . . . . 112
4.3.8 Ethernet communication when the connected station is RCPU (UDP) . . . . . . . . . . . . . . . . 115
4.3.9 Ethernet communication when the connected station is FX5CPU (TCP) . . . . . . . . . . . . . . 118
4.3.10 Ethernet communication when the connected station is FX5CPU (UDP) . . . . . . . . . . . . . . 120
4.3.11 Ethernet communication when the connected station is built-in Ethernet port QCPU
(TCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4.3.12 Ethernet communication when the connected station is built-in Ethernet port QCPU
(UDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
4.3.13 Ethernet communication when the connected station is built-in Ethernet port LCPU
(TCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
4.3.14 Ethernet communication when the connected station is built-in Ethernet port LCPU
(UDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
4.3.15 Ethernet communication when the connected station is Ethernet adapter module
(TCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
4.3.16 Ethernet communication when the connected station is Ethernet adapter module
(UDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
4.3.17 Ethernet communication when the connected station is Ethernet adapter (TCP) . . . . . . . . 146
4.3.18 Ethernet communication when the connected station is Ethernet adapter (UDP) . . . . . . . . 148
4.3.19 Ethernet communication when the connected station is robot controller . . . . . . . . . . . . . . . 149

4.4 COM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

4.4.1 CPU COM communication when the connected station is FX5CPU . . . . . . . . . . . . . . . . . . 150
4.4.2 CPU COM communication when the connected station is QCPU (Q mode) . . . . . . . . . . . . 152
4.4.3 CPU COM communication when the connected station is LCPU . . . . . . . . . . . . . . . . . . . . 155
4.4.4 CPU COM communication when the connected station is Q motion CPU . . . . . . . . . . . . . 158
4.4.5 CPU COM communication when the connected station is FXCPU . . . . . . . . . . . . . . . . . . . 160
4.4.6 COM communication when the connected station is inverter . . . . . . . . . . . . . . . . . . . . . . . 162
4.4.7 COM communication when the connected station is robot controller . . . . . . . . . . . . . . . . . 163

4.5 USB Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

4.5.1 USB communication when the connected station is RCPU . . . . . . . . . . . . . . . . . . . . . . . . . 164
4.5.2 USB communication when the connected station is R motion CPU . . . . . . . . . . . . . . . . . . 167
4.5.3 USB communication when the connected station is QCPU (Q mode). . . . . . . . . . . . . . . . . 170
4.5.4 USB communication when the connected station is LCPU . . . . . . . . . . . . . . . . . . . . . . . . . 174
4.5.5 USB communication when the connected station is QSCPU . . . . . . . . . . . . . . . . . . . . . . . 177
4.5.6 USB communication when the connected station is Q motion CPU . . . . . . . . . . . . . . . . . . 178
4.5.7 USB communication when the connected station is FXCPU . . . . . . . . . . . . . . . . . . . . . . . . 180
4.5.8 USB communication when the connected station is inverter . . . . . . . . . . . . . . . . . . . . . . . . 182
4.5.9 USB communication when the connected station is robot controller . . . . . . . . . . . . . . . . . . 183

4.6 MELSECNET/H Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

4.7 CC-Link IE Controller Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
4.8 CC-Link IE Field Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
4.9 CC-Link Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
4.10 CC-Link G4 communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
4.11 GX Simulator Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
4.12 GX Simulator2 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
4.13 GX Simulator3 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
4.14 MT Simulator2 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

15
 4.15 Modem Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
4.15.1 Modem communication when the connected module is Q series-compatible C24 . . . . . . . 203
4.15.2 Modem communication when the connected module is L series-compatible C24. . . . . . . . 210
4.15.3 Modem communication when the connected station is FXCPU . . . . . . . . . . . . . . . . . . . . . 216

4.16 Gateway Function Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

4.17 GOT Transparent Function Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
4.17.1 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Direct connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
4.17.2 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Direct connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
4.17.3 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Bus connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
4.17.4 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Bus connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
4.17.5 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Serial communication module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
4.17.6 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Serial communication module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
4.17.7 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
R series-compatible E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
4.17.8 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Q series-compatible E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
4.17.9 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
L series-compatible E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
4.17.10 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
R series-compatible E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
4.17.11 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Q series-compatible E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
4.17.12 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
L series-compatible E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
4.17.13 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
4.17.14 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
4.17.15 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Ethernet adapter module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
4.17.16 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Ethernet adapter module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
4.17.17 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port:
Ethernet adapter/module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
4.17.18 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port:
Ethernet adapter/module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
4.17.19 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port,
CPU side port: Serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
4.17.20 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port,
CPU side port: Serial communication module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

16
 4.17.21 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port,
CPU side port: Bus connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

4.18 Q Series Bus Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

CHAPTER 5 FUNCTIONS 362

5.1 Programming Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
5.2 Details of Functions (For ACT Control). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
5.2.1 Open (Opening communication line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
5.2.2 Close (Closing communication line). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
5.2.3 ReadDeviceBlock (Reading devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
5.2.4 WriteDeviceBlock (Writing devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
5.2.5 ReadDeviceRandom (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
5.2.6 WriteDeviceRandom (Writing devices randomly). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
5.2.7 SetDevice (Setting device data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
5.2.8 GetDevice (Acquiring device data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
5.2.9 ReadBuffer (Reading data from buffer memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
5.2.10 WriteBuffer (Writing data to buffer memory). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
5.2.11 GetClockData (Reading clock data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
5.2.12 SetClockData (Writing clock data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
5.2.13 GetCpuType (Reading programmable controller CPU model). . . . . . . . . . . . . . . . . . . . . . . 409
5.2.14 SetCpuStatus (Remote control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
5.2.15 EntryDeviceStatus (Registering devices for status monitoring) . . . . . . . . . . . . . . . . . . . . . . 418
5.2.16 FreeDeviceStatus (Deregistering devices for status monitoring) . . . . . . . . . . . . . . . . . . . . . 423
5.2.17 OnDeviceStatus (Event notification). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
5.2.18 ReadDeviceBlock2 (Reading devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
5.2.19 WriteDeviceBlock2 (Writing devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
5.2.20 ReadDeviceRandom2 (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
5.2.21 WriteDeviceRandom2 (Writing devices randomly). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
5.2.22 SetDevice2 (Setting device data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
5.2.23 GetDevice2 (Acquiring device data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
5.2.24 Connect (Connecting telephone line). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
5.2.25 Disconnect (Disconnecting telephone line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
5.2.26 GetErrorMessage (Receiving error message) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451

5.3 Details of Functions (For .NET Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

5.3.1 Open (Opening communication line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
5.3.2 Close (Closing communication line). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
5.3.3 ReadDeviceBlock (Reading devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
5.3.4 WriteDeviceBlock (Writing devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
5.3.5 ReadDeviceRandom (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
5.3.6 WriteDeviceRandom (Writing devices randomly). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
5.3.7 SetDevice (Setting device data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
5.3.8 GetDevice (Acquiring device data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
5.3.9 ReadBuffer (Reading data from buffer memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
5.3.10 WriteBuffer (Writing data to buffer memory). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
5.3.11 GetClockData (Reading clock data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
5.3.12 SetClockData (Writing clock data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
5.3.13 GetCpuType (Reading programmable controller CPU model). . . . . . . . . . . . . . . . . . . . . . . 486

17
 5.3.14 SetCpuStatus (Remote control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
5.3.15 EntryDeviceStatus (Registering devices for status monitoring) . . . . . . . . . . . . . . . . . . . . . . 488
5.3.16 FreeDeviceStatus (Deregistering devices for status monitoring) . . . . . . . . . . . . . . . . . . . . . 491
5.3.17 OnDeviceStatus (Event notification). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
5.3.18 ReadDeviceBlock2 (Reading devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
5.3.19 WriteDeviceBlock2 (Writing devices in bulk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
5.3.20 ReadDeviceRandom2 (Reading devices randomly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
5.3.21 WriteDeviceRandom2 (Writing devices randomly). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
5.3.22 SetDevice2 (Setting device data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
5.3.23 GetDevice2 (Acquiring device data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
5.3.24 Connect (Connecting telephone line). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
5.3.25 Disconnect (Disconnecting telephone line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
5.3.26 GetErrorMessage (Receiving error message) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520

CHAPTER 6 SAMPLE PROGRAMS 521

6.1 VBA Sample Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
6.1.1 Sample program for Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
6.1.2 Sample program for Excel (Reading/writing devices) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
6.1.3 Sample program for Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

6.2 VBScript Sample Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530

6.3 ASP Sample Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
6.4 Visual Basic® .NET Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
6.4.1 Modem communication sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
6.4.2 Read/Write sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
6.4.3 Type conversion sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

6.5 Visual C++® .NET Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543

6.5.1 Read/Write sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
6.5.2 Troubleshooting function sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544

6.6 Visual C#® .NET Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

6.6.1 Read/Write sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

6.7 Visual C++ ® .NET (MFC) Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547

6.7.1 Dispatch interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
6.7.2 Custom interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
6.7.3 Troubleshooting function sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550

CHAPTER 7 ERROR CODES 552

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

APPENDIX 586
Appendix 1 Connection System of Callback Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Appendix 2 Programming Examples for Monitoring Word Device Status . . . . . . . . . . . . . . . . . . . . 587
Appendix 3 Time-Out Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590

18
 Appendix 3.1 Communication retries at time-out error occurrence . . . . . . . . . . . . . . . . . . . 590
Appendix 3.2 Communication retries at receive data error occurrence . . . . . . . . . . . . . . . . 605
Appendix 3.3 Time-out errors at fixed time in ACT control . . . . . . . . . . . . . . . . . . . . . . . . 608
REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

19
 HOW TO READ THIS MANUAL
The following explains the page composition and symbols in this manual.
The content of the example page used here are different from the actual content for the intention of explaining how to use this
manual.

Indicates the chapter

of currently open page.

indicates
the particular
attention.

Remark indicates

the useful tip.

Indicates the section

of currently open page.

* indicates
the reference page.

$ indicates
the reference manual.

The following shows the symbols used in this manual with descriptions and examples.
Notation Description Example
[ ] Menu name on a menu bar [Tools][Property]
<< >> Tab name on a screen <<.NET>> tab
" " Item name on a screen "References"

Button on a screen button

20
 TERMS
This manual uses the terms listed in the following table unless otherwise noted.
Term Description
Generic product name for SWnDNC-ACT-E and SWnDNC-ACT-EA (n: version)
MX Component
-EA indicates a volume-license product.
Personal computer Generic term for personal computers on which Windows® operates
PC CPU module Abbreviation for MELSEC Q series-compatible PC CPU module (CONTEC CO., LTD.product)
Generic product name for SWnD5C-GPPW-E, SWnD5C-GPPW-EA, SWnD5C-GPPW-EV, and
GX Developer SWnD5C-GPPW-EVA (n: version)
-EA indicates a volume-license product, and -EV an updated product.
GX Works3 Generic product name for SWnDND-GXW3 (n: version)
GX Works2 Generic product name for SWnDNC-GXW2 (n: version)
MT Works2 Generic product name for SWnDNC-MTW2 (n: version)
Generic product name for SWnD5C-LLT-E, SWnD5C-LLT-EA, SWnD5C-LLT-EV, and SWnD5C-LLT-EVA
GX Simulator (n: version)
-EA means a volume-license product, and -EV an updated product.
Generic term for Q80BD-J71LP21-25, Q80BD-J71LP21S-25, Q81BD-J71LP21-25, Q80BD-J71LP21G,
MELSECNET/H board and Q80BD-J71BR11
Abbreviation for MELSECNET/H interface board
CC-Link IE Controller Network Generic term for Q80BD-J71GP21-SX and Q80BD-J71GP21S-SX
board Abbreviation for CC-Link IE Controller Network interface board
CC-Link IE Field Network
Abbreviation for Q81BD-J71GF11-T2 CC-Link IE Field Network interface board
board
Generic term for Q80BD-J61BT11N and Q81BD-J61BT11
CC-Link Ver.2 board
Abbreviation for CC-Link system master/local interface board
Generic term for R04, R04EN, R08, R08P, R08SF, R08EN, R16, R16P, R16SF, R16EN, R32, R32P,
RCPU
R32SF, R32EN, R120, R120P, R120SF and R120EN
RnPCPU Generic term for R08P, R16P, R32P and R120P
RnSFCPU Generic term for R08SF, R16SF, R32SF and R120SF
RnENCPU Generic term for R04EN, R08EN, R16EN, R32EN and R120EN
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,
QCPU (Q mode)
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
Generic term for Q03UDE, Q03UDV, Q04UDEH, Q04UDV, Q06UDEH, Q06UDV, Q10UDEH, Q13UDEH,
Built-in Ethernet port QCPU
Q13UDV, Q20UDEH, Q26UDEH, Q26UDV, Q50UDEH, and Q100UDEH
LCPU Generic term for L02S, L02, L06, L26, and L26-BT
FX5CPU Generic term for FX5U and FX5UC
Generic term for FX0, FX0S, FX0N, FX1, FX1N, FX1NC, FX1S, FXU, FX2C, FX2N, FX2NC, FX3S, FX3G, FX3GC, FX3U,
FXCPU
and FX3UC
Built-in Ethernet CPU Generic term for RCPU, built-in Ethernet port QCPU, LCPU and FX5CPU
R motion CPU Generic term for R16MT, R32MT
Q motion CPU Generic term for Q172, Q173, Q172H, Q173H, Q172D, Q173D, Q172DS, and Q173DS
QSCPU Abbreviation for a safety CPU module (QS001CPU)
Generic term for R12CCPU-V, Q12DCCPU-V (Basic mode), Q12DCCPU-V (Extended mode),
C Controller module
Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG, and Q26DHCCPU-LS
RCCPU Another term for R12CCPU-V
Generic term for Q12DCCPU-V (Basic mode), Q12DCCPU-V (Extended mode), Q24DHCCPU-V,
QCCPU
Q24DHCCPU-LS, Q24DHCCPU-VG, and Q26DHCCPU-LS

21
 Term Description
Status that Q12DCCPU-V is initialized with the basic mode
Q12DCCPU-V
For Q12DCCPU-V (Basic mode), refer to the following manual.
(Basic mode)
C Controller Module User's Manual (Hardware Design, Function Explanation)
Status that Q12DCCPU-V is initialized with the extended mode
Q12DCCPU-V
For Q12DCCPU-V (Extended mode), refer to the following manual.
(Extended mode)
MELSEC-Q C Controller Module User's Manual
Generic term for RCPU, QCPU (Q mode), LCPU, FX5CPU, FXCPU, R motion CPU, Q motion CPU,
Programmable controller CPU
QSCPU, and C Controller module
R series-compatible C24 Generic term for RJ71C24, RJ71C24-R2, and RJ71C24-R4
Q series-compatible C24 Generic term for QJ71C24, QJ71C24-R2, QJ71C24N, QJ71C24N-R2, and QJ71C24N-R4
L series-compatible C24 Generic term for LJ71C24 and LJ71C24-R2
Generic term for FX0N-485ADP, FX2NC-485ADP, FX1N-485-BD, FX2N-485-BD, FX3G-485-BD, FX3U-485-BD,
FX extended port
and FX3U-485ADP
Generic term for R series-compatible C24, Q series-compatible C24, L series-compatible C24, and FX
Serial communication module
extended port
R series-compatible E71 Another term for RJ71EN71
Q series-compatible E71 Generic term for QJ71E71, QJ71E71-B2, QJ71E71-B5, and QJ71E71-100
L series-compatible E71 Another term for LJ71E71
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 module Generic term for R series-compatible E71, Q series-compatible E71, and L series-compatible E71
CC-Link G4 module Abbreviation for AJ65BT-G4-S3 GPP function peripheral connection module
GOT Abbreviation for Graphic Operation Terminal
GOT2000 Abbreviation for Graphic Operation Terminal GOT2000 series
GOT1000 Abbreviation for Graphic Operation Terminal GOT1000 series
GOT900 Abbreviation for Graphic Operation Terminal GOT900 series
Inverter Abbreviation for FREQROL-A800 series
Robot controller Abbreviation for CR750-D/CRnD-700 series
Abbreviation for communication with programmable controller CPU using the serial communication
Serial communication
module
Abbreviation for communication by connecting the personal computer to Ethernet module or the built-in
Ethernet communication
Ethernet CPU
Abbreviation of communication performed by connecting the personal computer to the RS-232 or RS-422
CPU COM communication
connector of programmable controller CPU
Abbreviation for communication by connecting personal computer to the USB connector of Programmable
CPU USB communication
controller CPU
MELSECNET/H
Abbreviation for communication with programmable controller CPU using MELSECNET/H board
communication
CC-Link IE Controller Network Abbreviation for communication with programmable controller CPU using CC-Link IE Controller Network
communication board
CC-Link IE Field Network
Abbreviation for communication with programmable controller CPU using CC-Link IE Field Network board
communication
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
Abbreviation for communication with programmable controller CPU on the same base using PC CPU
Q series bus communication
module
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
MT Simulator2 communication Abbreviation for communication using the simulation function of MT Developer2
Abbreviation for communication with programmable controller CPU via modems using
Modem communication
Q series-compatible C24, L series-compatible C24 or FXCPU

22
 Term Description
Gateway function Abbreviation for communication with programmable controller CPU and third-party programmable
communication controllers using the gateway functions of GOT
GOT transparent Abbreviation for communication with programmable controller CPU using the GOT transparent functions
communication of GOT
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
Robot controller COM
Abbreviation for communication by connecting the robot controller to the COM port of personal computer
communication
Robot controller USB
Abbreviation for communication by connecting the robot controller to the USB port of personal computer
communication
Robot controller Ethernet
Abbreviation for communication by connecting the robot controller and personal computer to Ethernet
communication
Utility setting type A development type for creating user programs using Communication Setup Utility
Program setting type A development type for creating user programs without using Communication Setup Utility
ACT control Generic term for ActiveX control provided by MX Component
.NET control Generic term for .NET control provided by MX Component
Redundant CPU Generic term for QnPRH and RnPCPU
Redundant type extension
Abbreviation for Q65WRB extension base unit for redundant system
base unit

Abbreviation for Microsoft® Excel® 2003, Microsoft® Excel® 2007, 32-bit Microsoft® Excel® 2010,
Excel
32-bit Microsoft® Excel® 2013, and 32-bit Microsoft® Excel® 2016

Abbreviation for Microsoft® Access® 2003, Microsoft® Access® 2007, 32-bit Microsoft® Access® 2010,
Access
32-bit Microsoft® Access® 2013, and 32-bit Microsoft® Access® 2016

Generic term for Visual Basic version Microsoft® Visual Studio® 2005, Microsoft® Visual Studio® 2008,
Visual Basic® .NET Microsoft® Visual Studio® 2010, Microsoft® Visual Studio® 2012, Microsoft® Visual Studio® 2013, and
Microsoft® Visual Studio® 2015

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

Generic term for Visual C# version Microsoft® Visual Studio® 2005, Microsoft® Visual Studio® 2008,
Visual C#® .NET Microsoft® Visual Studio® 2010, Microsoft® Visual Studio® 2012, Microsoft® Visual Studio® 2013, and
Microsoft® Visual Studio® 2015

23
CHAPTER 1 OVERVIEW

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
Network
CC-Link IE Field Network module

Ethernet adapter/module

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

RS-232, RS-232/RS-422 conversion QCPU (Q mode), LCPU,

Q motion CPU, FXCPU

Converter/cable
FXCPU
(FX0/FX0S/FXON/FX1S/FX1N/FX2N/FX1NC/
FX2NC/FX3S/FX3G/FX3GC/FX3U/FX3UC)

USB RCPU, R motion CPU, QCPU (Q mode),

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

MELSECNET/H communication MELSECNET/H MELSECNET/H module

MELSECNET/H board

CC-Link IE Controller Network CC-Link IE Controller

communication CC-Link IE Controller Network module
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)

24
 CHAPTER 1 OVERVIEW

Personal computer 1
Perform communication with the specified
programmable controller easily without being
aware of communication protocol.

GX Developer Version 5
GX Developer (SW5D5C-GPPW-E) or later
GX Simulator communication + GX Simulator 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 (GX Simulator3) (SW1DND-GXW3-E)
Sold separately

Simulation function of MT Developer2 MT Developer2 Version 1

MT Simulator2 communication (SW1DNC-MTW2-E) or later
(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
RCPU, QCPU (Q mode),
USB,RS-232 RS-232
GOT transparent communication LCPU, C Controller module,
Ethernet Q motion CPU
GOT
RS-232/RS-422
FX5CPU, FXCPU

R series-compatible C24,
RS-232
Q series-compatible C24,
L series-compatible C24

Bus connection QCPU (Q mode),

QCCPU,
Q motion CPU

1.1 Outline of Controls

Ethernet
Ethernet module

Ethernet
Built-in Ethernet CPU

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

Network

Ethernet
Ethernet Adapter/module

Inverter COM RS-232/RS-485 conversion

Inverter
communication

Inverter USB USB Inverter

communication

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)

25
1.2 Control and Function Lists

This section shows the lists of controls and functions.

1.2.1 Control list

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

(1) ACT control

The following table shows the ActiveX controls supported by MX Component.
Data can be accessed using devices.
Included control name
DLL name For VB, VC++, Application
For VBScript
VC#, VBA
The utility setting type control which is used to create a user
ActUtlType.dll ActUtlType ActMLUtlType*1
program using Communication Setup Utility.
The program setting type control which is used to create a user
ActProgType.dll*2 ActProgType ActMLProgType*1
program without using Communication Setup Utility.
ActSupportMsg.dll ActSupportMsg ActMLSupportMsg Used for the troubleshooting function.
*1 : Communication is disabled if the communication path is a modem.
*2 : Not applicable to inverter communication/robot controller communication.

(2) .NET control

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

26
 CHAPTER 1 OVERVIEW

1.2.2 Function list 1

The following table shows the features of the functions and the functions that can be used for the controls.

Function name Feature Refer

Open Open a communication line. Page 366, Section 5.2.1, Page 453, Section 5.3.1
Close Close a communication line. Page 368, Section 5.2.2, Page 454, Section 5.3.2
ReadDeviceBlock Read devices in bulk. (4-byte data) Page 369, Section 5.2.3, Page 455, Section 5.3.3
WriteDeviceBlock Write devices in bulk. (4-byte data) Page 373, Section 5.2.4, Page 459, Section 5.3.4
ReadDeviceRandom Read devices randomly. (4-byte data) Page 376, Section 5.2.5, Page 462, Section 5.3.5
WriteDeviceRandom Write devices randomly. (4-byte data) Page 380, Section 5.2.6, Page 467, Section 5.3.6
SetDevice Set one point of device. (4-byte data) Page 384, Section 5.2.7, Page 474, Section 5.3.7
GetDevice Acquire data of one point of device. (4-byte data) Page 386, Section 5.2.8, Page 476, Section 5.3.8
ReadBuffer Read data from buffer memory. Page 389, Section 5.2.9, Page 478, Section 5.3.9
WriteBuffer Write data to buffer memory. Page 394, Section 5.2.10, Page 480, Section 5.3.10
GetClockData Read clock data from programmable controller CPU. Page 399, Section 5.2.11, Page 482, Section 5.3.11
SetClockData Write clock data to programmable controller CPU. Page 404, Section 5.2.12, Page 484, Section 5.3.12
GetCpuType Read programmable controller CPU model. Page 409, Section 5.2.13, Page 486, Section 5.3.13
Remote RUN/STOP/PAUSE of programmable controller
SetCpuStatus Page 414, Section 5.2.14, Page 487, Section 5.3.14
CPU.
EntryDeviceStatus Register device status monitor. Page 418, Section 5.2.15, Page 488, Section 5.3.15
FreeDeviceStatus Deregister device status monitor. Page 423, Section 5.2.16, Page 491, Section 5.3.16
OnDeviceStatus Announce event. Page 424, Section 5.2.17, Page 492, Section 5.3.17
ReadDeviceBlock2 Read devices in bulk. (2-byte data) Page 427, Section 5.2.18, Page 494, Section 5.3.18
WriteDeviceBlock2 Write devices in bulk. (2-byte data) Page 430, Section 5.2.19, Page 497, Section 5.3.19

1.2.2 Function list

1.2 Control and Function Lists
ReadDeviceRandom2 Read devices randomly. (2-byte data) Page 433, Section 5.2.20, Page 501, Section 5.3.20
WriteDeviceRandom2 Write devices randomly. (2-byte data) Page 437, Section 5.2.21, Page 506, Section 5.3.21
SetDevice2 Set one point of device. (2-byte data) Page 441, Section 5.2.22, Page 512, Section 5.3.22
GetDevice2 Acquire data of one point of device. (2-byte data) Page 444, Section 5.2.23, Page 514, Section 5.3.23
Connect Connect a telephone line. Page 447, Section 5.2.24, Page 516, Section 5.3.24
Disconnect Disconnect a telephone line. Page 449, Section 5.2.25, Page 518, Section 5.3.25
GetErrorMessage Display error definition and corrective action. Page 451, Section 5.2.26, Page 520, Section 5.3.26

● Considerations for using RnSFSCPU

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.

27
CHAPTER 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.

2.1.1 When using VBA

Perform the following setting operation when using VBA.

(1) When using Microsoft® Excel 2010

Operating procedure

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

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

28
 CHAPTER 2 CONTROLS

3. Paste the selected ACT control to the sheet.

4. Select [Visual Basic] on the <<Developer>> tab to start Visual Basic Editor.

5. Create a program with Visual Basic Editor.

2.1.1 When using VBA

2.1 Settings for Using Controls

29
 (2) 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 button.

4. Paste the selected ACT control to the sheet.

30
 CHAPTER 2 CONTROLS

5. Select [View Code] on the <<Design>> tab to start Visual Basic Editor.

6. Create a program with Visual Basic Editor.

2.1.1 When using VBA

2.1 Settings for Using Controls

31
2.1.2 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.

32
 CHAPTER 2 CONTROLS

2.1.3 When Using Visual Studio® .NET

Perform the following setting operation when using Visual Studio® .NET.
2
(1) Setting the include file (for Visual Basic® .NET)

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

2. Select the ActDefine.vb file and click the button.

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

2.1.3 When Using Visual Studio® .NET

3. The ActDefine.vb file is displayed on the Solution Explorer window. 2.1 Settings for Using Controls

33
 (2) Setting the include file (for Visual C++® .NET)

Operating procedure
1. Start Visual Studio® .NET and select [Project]  [Property].*1

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

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

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

34
 CHAPTER 2 CONTROLS

4. Click (New line).

5. Click .

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.1.3 When Using Visual Studio® .NET

2.1 Settings for Using Controls

35
 (3) 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 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.

36
 CHAPTER 2 CONTROLS

(4) When pasting a control to the form

(Common setting for Visual C++® .NET, Visual Basic® .NET, and Visual C#® .NET projects)

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

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

2.1.3 When Using Visual Studio® .NET

2.1 Settings for Using Controls
3. The control is added to the bottom of the tab selected under "Toolbox".

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.
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0"/>
</startup>
</configuration>

For details, refer to Visual Studio® Help.

(5) 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. Right-click the project and select "Reference".*1

*1 : For Visual Studio® 2010, Visual Studio® 2012, or Visual Studio® 2015, select "Add Reference". (To Step 4)
For Visual Studio® 2013, select "Add"  "References". (To Step 4)

3. Select the button on "Property Pages".

38
 CHAPTER 2 CONTROLS

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

*1 : For Visual Studio® 2012, Visual Studio® 2013, or Visual Studio® 2015, select "COM"  "Type Libraries" (for pasting ACT
control) or "Assemblies"  "Extensions" (for pasting .NET control), select the control to be used, and click the
button.

2.1.3 When Using Visual Studio® .NET

2.1 Settings for Using Controls

39
 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".)

40
 CHAPTER 2 CONTROLS

6. For Visual Basic® .NET of Visual Studio® 2010/2012/2013/2015, click 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".

2.1.3 When Using Visual Studio® .NET

2.1 Settings for Using Controls

● When using .NET Control

The following library is added to "References".
• For DotUtlType: ActTypeLib
• For DotSupportMsg: ActSupportMsgLib
Set "False" for "Embed Interop Types" in the property of each library.
● 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.
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0"/>
</startup>
</configuration>

For details, refer to Visual Studio® Help.

41
 (6) 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 button.

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

4. Right-click the form and select "Add Variable".

42
 CHAPTER 2 CONTROLS

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

6. Check that the member variable set in Step 5 is created.

• In the form class of Class View

2.1.3 When Using Visual Studio® .NET

2.1 Settings for Using Controls
• In the header file of form class

43
 (7) 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 <<Command>> tab, and click the button.

3. Select "File"  "Advanced Save Options", and click the button.

44
 CHAPTER 2 CONTROLS

2.2 Programming Procedure

This section explains the procedure to create a user application.

2

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

2.2.1 When using VBA

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

Power on the personal computer and start Windows R .

Install MX Component Version 4. *1

Program setting type

Select the setting type.

Utility setting type

Start Communication Setup Utility and set the communication

*1 Start Excel or Access.
settings by following the instructions of wizard.
Page 28,
Start Excel or Access. Start Visual Basic Editor and create Section 2.1.1
an application.
Page 28,
Start Visual Basic Editor and create Section 2.1.1 Form the controls to be used
an application. in VBA. (ActProgType)

Form the controls to be used

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

2.2.1 When using VBA

2.2 Programming Procedure
Set the property of the formed controls.
(Set the logical station number only.) *1

Create a program using the functions supported by

corresponding controls. Page 57, CHAPTER 3, Page 74, CHAPTER 4, Page 362, CHAPTER 5

Debug the program using PLC Monitor Utility.*1

Completion of user application

*1 : MX Component Version 4 Operating Manual

45
2.2.2 When using VBScript

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

Power on the personal computer and start Windows R.

Install MX Component Version 4. *1

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 Page 32,
VBScript. (ActProgType) Section 2.1.2
On the website, form the controls for
MX Component controls to be used in Page 32,
VBScript. (ActUtlType) Set the property of the formed controls.
Section 2.1.2 *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. Page 57, CHAPTER 3, Page 74, CHAPTER 4, Page 362, CHAPTER 5

Debug the program using PLC Monitor Utility.*1

Completion of user application

*1 : MX Component Version 4 Operating Manual

46
 CHAPTER 2 CONTROLS

2.2.3 When using Visual Basic® .NET

Create a user application with the following procedure when using Visual Basic® .NET.
2
Power on the personal computer and start Windows R .

Install MX Component Version 4. *1

Program setting type

Select the setting type.

Utility setting type

Yes Start Visual Basic R .NET.

Use labels.
*2
R
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
R
Start Visual Basic .NET. Start Visual Basic R .NET.
*2 *2
R R
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. Page 57, CHAPTER 3, Page 74, CHAPTER 4, Page 362, CHAPTER 5

2.2.3 When using Visual Basic® .NET

2.2 Programming Procedure
Debug the program using PLC Monitor Utility.*1

Completion of user application

*1 : MX Component Version 4 Operating Manual

*2 : Page 33, Section 2.1.3 (1)

47
2.2.4 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 R .

Install MX Component Version 4. *1

Program setting type

Select the setting type.

Utility setting type

Yes Start Visual C++ R .NET.

Use labels.

R
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++ R .NET. Start Visual C++R .NET.

R
Add controls to Visual C++ .NET.
R
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. Page 57, CHAPTER 3, Page 74, CHAPTER 4, Page 362, CHAPTER 5

Debug the program using PLC Monitor Utility.*1

Completion of user application

*1 : MX Component Version 4 Operating Manual

*2 : Page 34, Section 2.1.3 (2)

When using both .NET control (DotUtlType) and Act control (ActUtlType) by pasting them, perform the following operations
by selecting [Project] - [Property] 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
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.

48
 CHAPTER 2 CONTROLS

2.2.5 When using Visual C#® .NET

Create a user application with the following procedure when using Visual C#® .NET.
2
Power on the personal computer and start Windows R .

Install MX Component Version 4. *1

Program setting type

Select the setting type.

Utility setting type

R
Yes Start Visual C# .NET.
Use labels.
*2
R
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
R R
Start Visual C# .NET. Start Visual C# .NET.
*2 *2
R R
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) 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. Page 57, CHAPTER 3, Page 74, CHAPTER 4, Page 362, CHAPTER 5

2.2.5 When using Visual C#® .NET

2.2 Programming Procedure
Debug the program using PLC Monitor Utility.*1

Completion of user application

*1 : MX Component Version 4 Operating Manual

*2 : Page 36, Section 2.1.3 (3)

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

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

(1) Common device types (except for communication to FX5CPU, gateway

function communication, inverter communication, and robot controller
communication)
The following device types are common to all communication paths 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
Contact TS Bit device Decimal
Timer*12 Coil TC Bit device Decimal
Present value TN Word device Decimal
Contact CS Bit device Decimal

Counter *12 Coil CC Bit device Decimal

Present value*3 CN Word device Decimal

Contact STS/SS Bit device Decimal
*12 Coil STC/SC Bit device Decimal
Retentive timer
Present value STN/SN Word device Decimal
Link special relay SB Bit device Hexadecimal

50
 CHAPTER 2 CONTROLS

Device Device name Device type Device number

Link special register SW Word device Hexadecimal
Step relay S Bit device Decimal
Accumulator A *4 Word device Decimal

Z *4 Word device Decimal 2

Index register
V *4 Word device Decimal
5 Word device Decimal
R*
File register
ZR Word device Decimal
Extended file register 6 Word device Decimal
ER*\R *
Link input 7 Bit device Hexadecimal
J*\X *
Link output J*\Y *7 Bit device Hexadecimal

Link relay J*\B *7 Bit device Hexadecimal

Direct link *8
Link special relay J*\SB *7 Bit device Hexadecimal

Link register J*\W *7 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.

2.3 Device Types

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

51
 (2) When access target is RCPU
The devices described in the following table can be used when access target is RCPU.
Device Device name Device type Device number
Contact LTS Bit device Decimal
*1 Coil LTC Bit device Decimal
Long timer
Present value LTN Double word device Decimal
Contact LCS Bit device Decimal
*1 Coil LCC Bit device Decimal
Long counter
Present value LCN Double word device Decimal
Contact LSTS/LSS Bit device Decimal
*1 Coil LSTC/LSC Bit device Decimal
Retentive long timer
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.

(3) When access target is RnSFCPU(Safety devices)

The safety devices described in the following table can be used when access target is RnSFCPU.
In safety mode, you can only read from but not write to the safety device.
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

(4) When access target is R motion CPU and 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

52
 CHAPTER 2 CONTROLS

(5) 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
2
Special relay SM Bit device Decimal
Special register SD Word device Decimal
Input relay X Bit device Octal
Output relay Y Bit device Octal
Internal relay M Bit device Decimal
Latch relay L Bit device Decimal
Annunciator F Bit device Decimal
Edge relay V Bit device Decimal
Link relay B Bit device Hexadecimal
Data register D Word device Decimal
Link register W Word device Hexadecimal
Contact TS Bit device Decimal
Timer Coil TC Bit device Decimal
Present value TN Word device Decimal
Contact CS Bit device Decimal
Counter Coil CC Bit device Decimal
Present value CN Word device Decimal
Contact STS/SS Bit device Decimal
Retentive timer Coil STC/SC Bit device Decimal
Present value STN/SN Word device Decimal
Contact LCS Bit device Decimal

2.3 Device Types

Long counter Coil LCC Bit device Decimal
Present value LCN Double word 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

53
 (6) 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 paths.
Device Device Device
Device Remarks
name type number
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-Link) WW Word device Hexadecimal RWw
Remote register (Data read area for CC-Link) WR Word device Hexadecimal RWr
Buffer memory ML Word device Hexadecimal Buffer memory of own station CC-Link module
Random access buffer in buffer memory of own
Random access buffer MC Word device Hexadecimal
station CC-Link module

(7) 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 paths.
Device Device Device
Device Remarks
name type number
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

(8) 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 paths.
Device Device Device
Device Remarks
name type number
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

54
 CHAPTER 2 CONTROLS

(9) 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 paths.
2
Device Device Device
Device Remarks
name type number
W0000 to W1FFF = RWw0 to RWw1FFF
Remote register of own board (for sending)
Remote register W Word device Hexadecimal
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

(10)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.

2.3 Device Types

(11)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

55
 (12)Device extension representations
The following table shows applicability of device extension representation.
These representations cannot be used for ReadDeviceBlock and WriteDeviceBlock.
Device extension Target CPU
representation RCPU RCCPU R motion CPU FX5CPU
Digit specification (Example: K4M0) 1 6  
* *
Bit specification (Example: D0.1) 2   
*
Index setting (Example: M100Z0) *3   

Target CPU
Device extension
QCPU Q motion
representation QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
Digit specification (Example: K4M0)*4  *6    

Bit specification (Example: D0.1) *7  *7 *7 *7 

5      
Index setting (Example: M100Z0)*

Device extension
GOT Inverter robot controller
representation
Digit specification (Example: K4M0)*4   
Bit specification (Example: D0.1)   
5   
Index setting (Example: M100Z0)*
: Applicable : Not applicable
*1 : FX/FY, FD/SD, V, CT/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/FX, DX/DY, and T/C/ST (contact, coil) cannot be specified.
*5 : FX/FX, 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.4 Accessible Ranges

For the ranges that can be accessed in each communication, refer to the following manual.
MX Component Version 4 Operating Manual

56
 CHAPTER 3 PROPERTIES OF CONTROLS

CHAPTER 3 PROPERTIES OF CONTROLS

This chapter explains the details of properties of the controls.

3.1 Property List

3
The following table shows the properties of each control.
Control name Property name
ActUtlType ActLogicalStationNumber
ActMLUtlType ActPassword

ActATCommand*1

ActATCommandPasswordCancelRetryTimes*1

ActATCommandResponseWaitTime*1
ActBaudRate

ActCallbackCancelWaitTime*1

ActCallbackDelayTime*1

ActCallbackNumber*1

ActCallbackReceptionWaitingTimeOut*1

ActConnectionCDWaitTime*1

ActConnectionModemReportWaitTime*1
ActConnectUnitNumber

ActConnectWay*1

3.1 Property List

ActControl
ActCpuTimeOut
ActCpuType

ACT Control ActDataBits

ActProgType ActDestinationIONumber
ActMLProgType
ActDestinationPortNumber

ActDialNumber*1
ActDidPropertyBit

ActDisconnectionCDWaitTime*1

ActDisconnectionDelayTime*1
ActDsidPropertyBit
ActHostAddress
ActIntelligentPreferenceBit
ActIONumber

ActLineType*1
ActMultiDropChannelNumber

ActMxUnitSeries*2
ActNetworkNumber

ActOutsideLineNumber*1
ActPacketType
ActParity
ActPassword

57
 Control name Property name
ActPasswordCancelResponseWaitTime*1
ActPortNumber
ActProtocolType
ActSourceNetworkNumber
ActSourceStationNumber
ActStationNumber
ActProgType ActStopBits
ActMLProgType ActSumCheck
ACT Control
ActTargetSimulator
ActThroughNetworkType
ActTimeOut

ActTransmissionDelayTime*1
ActUnitNumber
ActUnitType
ActSupportMsg
–
ActMLSupportMsg
ActLogicalStationNumber
DotUtlType
.NET Control 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.

58
 CHAPTER 3 PROPERTIES OF CONTROLS

3.2 Details of Control Properties

This section explains the details of properties set when creating a user application.

(1) Properties of utility setting type controls

The following table shows the properties of the Act(ML)UtlType control and the DotUtlType control.
3
Property name
Description Default value
(Type)
ActLogicalStation A logical station number set in Communication Setup Utility.
0(0x00)
Number (LONG) (Applicable setting range: 0 to 1023)
ActPassword Specify a password to disable the password set to the password protected modules.*1, *2, *3
Empty
(BSTR) 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 a characters other than alphanumeric is specified, a character code conversion error (0xF1000001) occurs at the execution of the
Open function.

(2) Properties of program setting type controls

The following table shows the properties of the Act(ML)ProgType control.
Property name
Description Default value
(Type)
Specify the series of connection target module.
The property value is set automatically, and it cannot be changed.

Property value Description

ActMxUnitSeries

3.2 Details of Control Properties

Specify programmable controller/motion 0(0x00)
(LONG) 0 (0x00)
controller/GOT.
1 (0x01) Specify inverter.
2 (0x02) Specify robot controller.

Specify the network number for MELSECNET/H.

(Specify "0" (0x00) when specifying the host station.)
Specify the network number for accessing other station with GX Simulator.
Specify the following value for the multi-drop connection (via Q series-compatible C24,
QJ61BT11).
ActNetworkNumber
0(0x00)
(LONG)
Property value of
Description
ActIntelligentPreferenceBit
0 (0x00) Specify the own network.
1 (0x01) Specify another network of multi-drop destination.

59
 Property name
Description Default value
(Type)
Specify the station number for MELSECNET/H or CC-Link.
(Specify "255" (0xFF) when specifying the host station.)
Specify the station number for accessing other station with GX Simulator.
Specify the following value for the multi-drop connection (via Q series-compatible C24,
QJ61BT11).
ActStationNumber
255(0xFF)
(LONG) Property value of
Description
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.
Specify the module number of the serial communication module or the station number when
the target is the Q series-compatible intelligent function module.
ActUnitNumber
This setting is invalid when the target is not a serial communication or Q series-compatible 0(0x00)
(LONG)
intelligent function module.
For multi-drop link, specify the module number of the target serial communication module.
Specify the module number of serial communication module, QE71, or Q series-compatible
E71.
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
ActConnectUnit requesting station is not required. (Specify "0" (00x0))
0(0x00)
Number (LONG) 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.
Specify the module I/O number.
For multi-drop link or intelligent function module access, specify the actual I/O number (start I/
ActIONumber O number divided by 16) of the target serial communication module or intelligent function
1023(0x3FF)
(LONG) 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.

60
 CHAPTER 3 PROPERTIES OF CONTROLS

Property name
Description Default value
(Type)
When the ActMxUnitSeries property is set to '0' (programmable controller/motion controller)
Specify the target CPU to communicate with.
In the parameter, specify any of the CPU types in the following table.

Property value
(Property window input value) Target CPU
CPU type Dec. Hex. 3
CPU_R04CPU 4097 0x1001 R04CPU
CPU_R04ENCPU 4104 0x1008 R04ENCPU
CPU_R08CPU 4098 0x1002 R08CPU
CPU_R08PCPU 4354 0x1102 R08PCPU
CPU_R08SFCPU 4386 0x1122 R08SFCPU
CPU_R08ENCPU 4105 0x1009 R08ENCPU
CPU_R16CPU 4099 0x1003 R16CPU
CPU_R16PCPU 4355 0x1103 R16PCPU
CPU_R16SFCPU 4387 0x1123 R16SFCPU
CPU_R16ENCPU 4106 0x100A R16ENCPU
CPU_R32CPU 4100 0x1004 R32CPU
CPU_R32PCPU 4356 0x1104 R32PCPU
CPU_R32SFCPU 4388 0x1124 R32SFCPU
CPU_R32ENCPU 4107 0x100B R32ENCPU
CPU_R120CPU 4101 0x1005 R120CPU
CPU_R120PCPU 4357 0x1105 R120PCPU
CPU_R120SFCPU 4389 0x1125 R120SFCPU
ActCpuType CPU_R120ENCPU 4108 0x100C R120ENCPU 34(CPU_

3.2 Details of Control Properties

(LONG) Q02CPU)
CPU_R16MTCPU 4113 0x1011 R16MTCPU
CPU_R32MTCPU 4114 0x1012 R32MTCPU
CPU_R12CCPU-V 4129 0x1021 R12CCPU-V
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

61
 Property name
Description Default value
(Type)

Property value
(Property window input value) Target CPU
CPU type Dec. Hex.
CPU_Q10UDHCPU 117 0x75 Q10UDHCPU
CPU_Q10UDEHCPU 149 0x95 Q10UDEHCPU
CPU_Q12CPU 36 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
ActCpuType 34(CPU_
CPU_Q100UDEHCPU 154 0x9A Q100UDEHCPU
(LONG) Q02CPU)
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

62
 CHAPTER 3 PROPERTIES OF CONTROLS

Property name
Description Default value
(Type)

Property value
(Property window input value) Target CPU
CPU type Dec. Hex.
CPU_FX0CPU 513 0x201 FX0(S)CPU
CPU_FX0NCPU 514 0x202 FX0NCPU 3
CPU_FX1CPU 515 0x203 FX1CPU
CPU_FX1SCPU 518 0x206 FX1SCPU
CPU_FX1NCPU 519 0x207 FX1N(C)CPU
FXUCPU
CPU_FX2CPU 516 0x204
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
ActCpuType 34(CPU_
(LONG) CPU_BOARD 1025 0x401 For own board access*1 Q02CPU)
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.

Property value
(Property window input value) Target CPU
CPU type Dec. Hex.

3.2 Details of Control Properties

INV_A800 7776 0x1E60 A800

When the ActMxUnitSeries property is set to '2' (Robot)

Specify the target Robot to communicate with.
In the parameter, specify the CPU type in the following table.

Property value
(Property window input value) Target CPU
CPU type Dec. Hex.
UCPU_CRD700 77825 0x13001 CRnD-7xx/CR75x-D

63
 Property name
Description Default value
(Type)
Specify the connection port number of personal computer.
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.
Property value (Property window input value)
Description
Port number Dec. Hex.
ActPortNumber
PORT_1 1 0x01 Communication port 1 1(PORT_1)
(LONG)
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
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

Specify the baud rate for serial communication.

Property value (Property window input value) Description
BAUDRATE_300 (300) 300bps
BAUDRATE_600 (600) 600bps
BAUDRATE_1200 (1200) 1200bps
BAUDRATE_2400 (2400) 2400bps
19200
ActBaudRate BAUDRATE_4800 (4800) 4800bps (BAUDRATE_
(LONG)
BAUDRATE_9600 (9600) 9600bps 19200)
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).
Specify the number of bits of the byte data sent and received for serial communication.
Property value (Property window input value) Description
ActDataBit
DATABIT_7 (7) 7 bits 8(DATABIT_8)
(LONG)
DATABIT_8 (8) 8 bits

For robot controller, specify the character size.

Specify the parity system used for serial communication.
Property value (Property window input value) Description
ActParity NO_PARITY (0) No parity 1
(LONG) (ODD_PARITY)
ODD_PARITY (1) Odd
EVEN_PARITY (2) Even

64
 CHAPTER 3 PROPERTIES OF CONTROLS

Property name
Description Default value
(Type)
Specify the number of stop bits used for serial communication.
Property value (Property window input value) Description
STOPBIT_ONE (0) 1 stop bit
STOPBITS_TWO (2) 2 stop bits
0
ActStopBits
For robot controller, specify the following setting. (STOPBIT_
(LONG)
Property value (Property window input value) Description ONE) 3
ONESTOPBIT (0) 1 stop bit
ONE5STOPBITS (1) 1.5 stop bits
TWOSTOPBITS (2) 2 stop bits

Specify the control setting of the signal line.

Property value (Property window input value)
Description
Control setting Dec. Hex. 8
ActControl
TRC_DTR 1 0x01 DTR control (TRC_DTR_
(LONG)
TRC_RTS 2 0x02 RTS control OR_RTS)
TRC_DRT_AND_RTS 7 0x07 DTR control and RTS control
TRC_DTR_OR_RTS 8 0x08 DTR control or RTS control

ActHostAddress
Pointer which indicates the connection host name (IP address) for Ethernet communication. 1.1.1.1
(BSTR)
Specify the CPU watchdog timer for Ethernet communication. (Unit: Multiplied by 250ms)
ActCpuTimeOut For FXCPU/inverter, specify the transmission waiting time for serial communication of FXCPU/
0(0x00)
(LONG) inverter. (Unit: Multiplied by 10ms)
For robot controller, specify the transmission timeout time. (1000 to 30000ms)
Set the time-out value of communication between the personal computer and programmable
controller/inverter. (Unit: ms)

3.2 Details of Control Properties

For robot controller, specify the transmission timeout time. (5000 to 120000ms)
ActTimeOut
A time-out processing may be performed internally depending on the communication path in 10000
(LONG)
MX Component.
For details, refer to the following section.
Page 590, Appendix 3 Time-Out Periods
Specify whether sum check is applied or not.
This setting is valid for serial communication module only.
0
ActSumCheck Property value (Property window input value) Description (NO_SUM_
(LONG)
NO_SUM_CHECK (0) Without sum check CHECK)
SUM_CHECK (1) With sum check

Specify the requesting network number when the QE71 or Q series-compatible E71 is
ActSourceNetwork specified.
0(0x00)
Number (LONG) Specify the same network number (which is specified in the network parameter) as that of the
connected QE71 or Q series-compatible E71.
Specify the requesting station number (personal computer side station number) when the
ActSourceStation QE71 or Q series-compatible E71 is specified.
0(0x00)
Number (LONG) Set the setting to avoid setting the same station number as that of the QE71 set within the
same Ethernet loop.

65
 Property name
Description Default value
(Type)
Specify the port number of the target when Ethernet communication is specified.
When accessing another network, specify the relay destination port number.
For the system other than the automatic response system, set the following setting.
Communication Setting
R series-compatible E71 MELSOFT connection Fixed to "5002"
(TCP/IP) OPS connection Depending on network parameter
ActDestinationPort
R series-compatible E71(UDP/IP) Fixed to "5001" 0(0x00)
Number (LONG)
QE71(UDP/IP) Fixed to "5001"
Other than Redundant CPU Fixed to "5002"
Q series-compatible E71
MELSOFT connection*2 Fixed to "5002"
(TCP/IP)
*2 Depending on network parameter
OPS connection
Q series-compatible E71(UDP/IP) Fixed to "5001"

For multi-drop connection (via R series-compatible C24/Q series-compatible C24/L series-

compatible C24/CC-Link), specify the actual I/O number (start I/O number divided by 16) of the
ActDestinationIO last access target station.
0(0x00)
Number (LONG) (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.
For multi-drop connection (via R series-compatible C24/Q series-compatible C24/L series-
ActMultiDropChannel compatible C24/CC-Link), specify the multi-drop connection channel number (CH1/CH2).
0(0x00)
Number (LONG) For robot controller, specify the retry count at communication error. (0 to 10 times)
This setting is invalid for other connections.
Specify whether MELSECNET/10 is included in the relayed network when accessing other
station via network.
Property value Relayed network
ActThroughNetwork
0 (0x00) MELSECNET/10 is not included. 0(0x00)
Type (LONG)
1 (0x01) MELSECNET/10 is included.

For robot controller, specify the protocol to be used (communication method). (Procedural (0)/
Nonprocedural (1))
For multi-drop connection (via R series-compatible C24/Q series-compatible C24/L series-
compatible C24/CC-Link), specify whether to relay the network of the multi-drop link
destination. (To differentiate the own network module.)
ActIntelligent
Property value Relayed network 0(0x00)
PreferenceBit (LONG)
0 (0x00) Another network of multi-drop link destination is not accessed.
1 (0x01) Another network of multi-drop link destination is accessed.

For accessing the Q series-compatible host station intelligent function module (intelligent
function 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
ActDidPropertyBit "ActIONumber" only.)
1(0x01)
(LONG) Property value Relayed network
0 (0x00) Module number is validated.
1 (0x01) Module number is invalidated.

66
 CHAPTER 3 PROPERTIES OF CONTROLS

Property name
Description Default value
(Type)
For multi-drop connection (via R series-compatible C24/Q series-compatible C24/L series-
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".
ActDsidPropertyBit
(Specify the property with the setting of "ActUnitNumber".) 1(0x01)
(LONG)
Property value Relayed network
0 (0x00) I/O number of the last access target station is validated.
3
1 (0x01) I/O number of the last access target station is invalidated.

Specify whether CR/LF exists or not.

Property value (Property window input value) Description
ActPacketType
CRLF_NONE (0) Without CR/LF 1(CRLF_CR)
(LONG)*3
CRLF_CR (1) With CR
CRLF_CRLF (2) With CR/LF

ActPassword Specify a password to disable the password set to the password protected modules.*5,*6,*7
Empty
(BSTR)*4 This setting is ignored when a password protected module is not used.
Set the connection system.
Property value (Property window input value)
Description
Connection system Dec. Hex.
TEL_AUTO_CONNECT 0 0x00 Auto line connect
Auto line connect (Callback
TEL_AUTO_CALLBACK 1 0x01
fixation)
Auto line connect (Callback
ActConnectWay TEL_AUTO_CALLBACK_NUMBER 2 0x02 0(TEL_AUTO_
number specification)
(LONG)*8 CONNECT)
TEL_CALLBACK 3 0x03 Callback connect (Fixation)

3.2 Details of Control Properties

Callback connect (Number
TEL_CALLBACK_NUMBER 4 0x04
specification)
TEL_CALLBACK_REQUEST 5 0x05 Callback request (Fixation)
Callback request (Number
TEL_CALLBACK_REQUEST_NUMBER 6 0x06
specification)
TEL_CALLBACK_WAIT 7 0x07 Callback reception waiting

ActATCommand Specify the AT command that initializes the modem. If no value (do not enter the property
*8
Empty
(BSTR) value) is set, the modem-standard AT command is used. Up to 70 characters can be set.*9
ActDialNumber Specify the telephone number. Up to 50 characters can be set.*9
*8
Empty
(BSTR) (The characters that can be set are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, -, *, #)
ActOutsideLine Specify the number to access the outside line. Up to 10 characters can be set.*9
Empty
Number (BSTR)*8 (The characters that can be set are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, -, *, #)

Specify the callback telephone number. Up to 62 characters can be set.*9

ActCallbackNumber (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 Empty
(BSTR)*8
(ActConnectWay) is other than auto line connect (callback number specification), callback
connect (number specification), or callback request (number specification).

67
 Property name
Description Default value
(Type)
Recognize the line type.
Property value (Property window input value)
Description
Line type Dec. Hex. 1(LINETYPE_
ActLineType (LONG)*8
LINETYPE_PULSE 0 0x00 Pulse (Dial line) TONE)
LINETYPE_TONE 1 0x01 Tone (Push button line)
LINETYPE_ISDN 2 0x02 ISDN (ISDN line)

Line connection CD signal confirmation time

Set the time for watching the ON/OFF of the CD signal line when the line is connected.
ActConnectionCD
(Applicable setting range: 1 to 999, unit: seconds) 90
WaitTime (LONG)*8
Increase the set time if the CD signal does not turn ON within the preset time depending on the
line-connected region (Example: overseas).
Line connection modem waiting time
ActConnectionModem
Set the waiting time for a result code response from the modem after line connection.
ReportWaitTime 5
(Applicable setting range: 1 to 999, unit: seconds)
(LONG)*8
Increase the set time if the response speed of the modem is slow.
Line disconnection CD signal confirmation time
Set the time for watching the ON/OFF of the CD signal line when the line is disconnected.
ActDisconnectionCD
(Applicable setting range: 1 to 999, unit: seconds) 5
WaitTime (LONG)*8
Increase the set time if the CD signal does not turn OFF within the preset time depending on
the line-connected region (Example: overseas).
Line disconnection delay time
ActDisconnectionDelay Set the guard time (no communication time) of the escape command sent to the modem.
3
Time (LONG)*8 (Applicable setting range: 1 to 999, unit: seconds)
Increase the set time if the response speed of the modem is slow.
Data send delay time
Set the time to be provided before the AT command is sent. (Applicable setting range: 0 to
ActTransmissionDelay 999, unit: seconds)
0
Time (LONG)*8 Increase the set time if the error code (0xF2100008) is returned though the correct AT
command is set.
Increase the set time if the response speed of the modem is slow.
ActATCommand
ResponseWaitTime AT command send response waiting time (Applicable setting range: 1 to 999, unit: seconds)
1
*8 Increase the set time if the response speed of the modem is slow.
(LONG)
ActPasswordCancel
ResponseWaitTime Password cancel response waiting time (Applicable setting range: 1 to 999, unit: seconds)
5
*8 Increase the set time if the quality of the line with the other end is low.
(LONG)
ActATCommand
PasswordCancelRetry AT command/password cancel send retry count
3
*8 (Applicable setting range: 1 to 999, unit: number of times)
Times (LONG)

68
 CHAPTER 3 PROPERTIES OF CONTROLS

Property name
Description Default value
(Type)
Callback line disconnection waiting time (Applicable setting range: 1 to 180, unit: seconds)
ActCallbackCancel 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). 90
WaitTime (LONG)*8 The setting is not necessary when the connection system (ActConnectWay) is other than
callback connect or callback request.
Callback execution delay time (Applicable setting range: 1 to 999, unit: seconds)
Increase the set time if the device for relaying connection to the line (Example: modem or like)
ActCallbackDelayTime
(LONG)*8
requires the predetermined time for reconnection after line disconnection. 20 3
The setting is not necessary when the connection system (ActConnectWay) is other than
callback connect or callback request.
Callback receive waiting time-out period (Applicable setting range: 1 to 3600, unit: seconds)
Set the waiting time for a telephone line connection request from Q series-compatible C24 in a
ActCallbackReception callback receive waiting status.
WaitingTimeOut If the set time elapsed, the callback reception waiting status is exited, and since the connection 120
(LONG)*8 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.
Specify the connection destination GX Simulator2 in start status.
When connecting to FXCPU, specify "0" (0x00).
Property value Description
None
(When only one simulator is in start status, connects to the simulator
0 (0x00) 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
ActTargetSimulator 2 (0x02) Simulator B 0(0x00)
(LONG)
3 (0x03) Simulator C
4 (0x04) Simulator D

3.2 Details of Control Properties

Specify the connection destination MT Simulator2 in start status..
Property value Description
2 (0x02) Simulator No.2
3 (0x03) Simulator No.3
4 (0x04) Simulator No.4

69
 Property name
Description Default value
(Type)
Specify the module type connected to the physical port.
Module type Connection system Value
R series-compatible C24 module direct
connection
UNIT_RJ71C24 0x1000
R series-compatible C24 connection via
GOT2000/1000 series
Q series-compatible C24 module direct
connection
Q series-compatible C24/CMO connection via
UNIT_QJ71C24 0x19
modem
Q series-compatible C24 connection via
GOT2000/1000 series
L series-compatible C24 module direct
connection
UNIT_LJ71C24 L series-compatible C24 connection via modem 0x54
L series-compatible C24 connection via
GOT2000/1000 series
UNIT_FX485BD FX extended port (RS-485) connection 0x24
Via R series-compatible E71 connection (IP
UNIT_RJ71EN71 0x1001
specification)
Via R series-compatible E71 connection (Direct
UNIT_RJ71EN71_DIRECT 0x1005
connection)
Q series-compatible E71 Ethernet port
UNIT_QJ71E71 connection 0x1A
/direct connection 0x13
ActUnitType (LONG)
UNIT_LJ71E71 L series-compatible E71 module connection 0x5C (UNIT_QNCPU)
UNIT_RETHER RCPU Ethernet port connection (IP specification) 0x1002
UNIT_RETHER_DIRECT RCPU Ethernet port direct connection 0x1003
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
Ethernet adapter module (NZ2GF-ETB)
UNIT_NZ2GF_ETB 0x59
connection
Ethernet adapter module (NZ2GF-ETB) direct
UNIT_NZ2GF_ETB_DIRECT 0x5A
connection
FXCPU Ethernet adapter (FX3U-ENET-ADP)
UNIT_FXETHER 0x4A
via hub
FXCPU Ethernet adapter (FX3U-ENET-ADP)
UNIT_FXETHER_DIRECT 0x4B
direct connection
UNIT_FXVCPU FX5CPU Serial port connection 0x2000
QCPU (Q mode) RS232C port direct connection
UNIT_QNCPU GOT2000/1000 series QCPU (Q mode) direct 0x13
connection
LCPU RS232C port direct connection
UNIT_LNCPU 0x50
GOT2000/1000 series LCPU direct connection
UNIT_QNMOTION Q motion CPU-RS232C port direct connection 0x1C

70
 CHAPTER 3 PROPERTIES OF CONTROLS

Property name
Description Default value
(Type)
Specify the module type connected to the physical port.
Module type Connection system Value
FXCPU-RS422 port direct connection
FXCPU direct connection via modem
UNIT_FXCPU 0x0F
FXCPU USB direct connection
GOT2000/1000 series FXCPU direct connection 3
UNIT_RUSB RCPU USB port direct connection 0x1004
UNIT_QNUSB QCPU (Q mode) USB port direct connection 0x16
UNIT_LNUSB LCPU USB port direct connection 0x51
QSCPU (Safety programmable controller) USB
UNIT_QSUSB 0x29
port connection
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
Q series-compatible AJ65BT-G4-S3 module
UNIT_G4QNCPU 0x1B
direct connection
UNIT_SIMULATOR Simulator (GX Simulator) connection 0x0B
Simulator (GX Simulator 2) connection
UNIT_SIMULATOR2*10 0x30
Simulator (MT Simulator 2) connection
UNIT_SIMULATOR3 Simulator (GX Simulator 3) connection 0x31
UNIT_A900GOT GOT2000/1000/900 series connection 0x21
R series-compatible E71 connection via 0x13
ActUnitType (LONG) UNIT_GOT_RJ71EN71 0x1051 (UNIT_QNCPU)

3.2 Details of Control Properties

GOT2000/1000 series
Q series-compatible E71 connection via
UNIT_GOT_QJ71E71 0x40
GOT2000/1000 series
L series-compatible E71 connection via
UNIT_GOT_LJ71E71 0x5D
GOT2000/1000 series
RCPU Ethernet port connection via GOT2000/
UNIT_GOT_RETHER 0x1052
1000 series
QCPU Ethernet port connection via GOT2000/
UNIT_GOT_QNETHER 0x41
1000 series
LCPU Ethernet port connection via GOT2000/
UNIT_GOT_LNETHER 0x55
1000 series
Ethernet adapter module (NZ2GF-ETB)
UNIT_GOT_NZ2GF_ETB 0x5B
connection via GOT2000/1000 series
FXCPU Ethernet adapter (FX3U-ENET-ADP)
UNIT_GOT_FXETHER 0x61
connection via GOT2000/1000 series
FXCPU Ethernet module (FX3U-ENET(-L))
UNIT_GOT_FXENET 0x62
connection via GOT2000/1000 series
FX5CPU Serial port connection via GOT2000/
UNIT_GOT_FXVCPU 0x2005
1000 series
FX5CPU Ethernet port connection via GOT2000/
UNIT_GOTETHER_FXVCPU 0x2006
1000 series
Built-in Ethernet port FX5CPU connection via
UNIT_GOT_FXVETHER 0x2007
GOT2000/1000 series
RCPU Ethernet port (RS422) connection via
UNIT_GOTETHER_RJ71C24 0x1061
GOT2000/1000 series

71
 Property name
Description Default value
(Type)
Specify the module type connected to the physical port.
Module type Connection system Value
QCPU (Q mode) Ethernet port (RS422)
UNIT_GOTETHER_QNCPU 0x56
connection via GOT2000/1000 series
LCPU Ethernet port (RS232C) connection via
UNIT_GOTETHER_LNCPU 0x57 0x13
ActUnitType (LONG) GOT2000/1000 series
(UNIT_QNCPU)
FXCPU Ethernet port connection via GOT2000/
UNIT_GOTETHER_FXCPU 0x60
1000 series
Q series bus Ethernet port connection via
UNIT_GOTETHER_QBUS 0x58
GOT2000/1000 series
UNIT_QBF Bus connection 0x1F

72
 CHAPTER 3 PROPERTIES OF CONTROLS

Property name
Description Default value
(Type)
Specify the communication protocol type of the module (board) to be connected.
Communication protocol
Connection system Value
type
PROTOCOL_SERIAL Via serial port 0x04 (4)
PROTOCOL_USB Via USB port 0x0D (13)
PROTOCOL_TCPIP Via TCP/IP 0x05 (5) 3
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) 0x04
ActProtocolType
PROTOCOL_SERIALMODEM Via serial port and modem 0x0E (14) (PROTOCOL_
(LONG)
SERIAL)
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*11 Inverter RS232C communication 0x00 (0)

COMM_USB*11 Inverter USB port communication 0x01 (1)

RC_PROTOCOL_SERIAL Robot controller COM communication 0x01 (1)
RC_PROTOCOL_USB Robot controller USB communication 0x04 (4)
Robot controller Ethernet
RC_PROTOCOL_TCPIP 0x02 (2)
communication

*1 : Except for CPU boards and AF boards.

3.2 Details of Control Properties

*2 : For details, refer to the following manual.
 Q Corresponding Ethernet Interface Module User's Manual (Basic)
*3 : This property can be used for inverter communication.
*4 : This property can be used for Ethernet communication.
*5 : The setting of ActPassword is not necessary if a password is not set.
*6 : Characters exceeded the maximum number of characters for the password are ignored.
*7 : If a character other than alphanumeric is specified, a character code conversion error (0xF1000001) occurs at the execution of the
Open function.
*8 : This property can be used for modem communication. It cannot be used for ActMLProgType control.
*9 : If the characters entered exceed the limit of set characters, the characters outside the setting range are ignored.
*10 : When the CPU type is Q motion CPU, connected to MT Simulator2. Other than that, connected to GX Simulator2.
*11 : The communication protocol type can be used when ActMxUnitSeries is 1 (0x01).

73
CHAPTER 4 PROPERTY SETTINGS OF
COMMUNICATION PATHS

This chapter explains the details of accessible communication paths and property settings.

4.1 Descriptions of Property Setting

The following is the descriptions of how communication paths and properties of control are explained in this chapter.

(1) Configuration
A diagram of system configuration

(2) Property pattern

Indicates the accessible ranges of the
used control and the patterns of the properties.

(3) Property list

(a) Property
Describes the property name.
(b) Default value
Describes the default value of the property.
The default value used for changing the property in the program are shown in the parentheses.
(c) Property pattern
Describes the property settings necessary to set the communication settings.
The property pattern numbers correspond to the numbers in the table of "Property pattern".

The indicated default values are the property values displayed on the property window of Visual Basic® .NET, Visual C++®
.NET, or Visual C#® .NET.
For the default values required to be entered in values other than the decimal number to change the property values in a
program are described in the parentheses.

74
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.2 Serial Communication

4.2.1 Serial communication when the connected station is R series-

compatible C24

(1) When a relayed module other than the connected station side R series-
compatible C24 exists

(a) Configuration
4
Connected R series- Relayed
station CPU compatible C24 module

Relayed network

Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected station
Relayed station CPU
CPU
Relayed network
R motion R motion
RCPU RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
*2   
CC IE Field

4.2.1 Serial communication when the connected station is R series-compatible C24

4.2 Serial Communication
MELSECNET/H    
 *1,*3
Ethernet    
Serial communication    
CC-Link    

Connected station
Relayed station CPU
CPU
Relayed network
R motion QCPU Q motion
RCPU QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
  *2   
CC IE Field
MELSECNET/H      
 *1,*3
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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.

75
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  

19200
ActBaudRate (BAUDRATE_ Match to the setting of R series-compatible C24.
19200)
ActConnectUnit
0 (0x00) Connected station side module station number
Number
8
ActControl (TRC_DTR_OR_ Depending on the used cable.
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber *2 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
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) Connected station side Connected station side
ActIONumber *2 1023 (0x3FF) No. 3: 994 (0x3E2)
No. 3: 994 (0x3E2) module I/O address module I/O address
No. 4: 995 (0x3E3)
No. 4: 995 (0x3E3)
For Redundant CPU
For Redundant CPU
Target station side
Control system:
Control system:
976 (0x3D0)
976 (0x3D0)
No specification:
No specification:
1023 (0x3FF)
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *3 number

76
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
 *1  
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
1
ActParity Fixed to 1(ODD_PARITY)
(ODD_PARITY)
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL
SERIAL)
0x01
4
ActPacketType 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)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActSource
0(0x00) Fixed to 0 (0x00)
NetworkNumber
ActSourceStation
0(0x00) Fixed to 0 (0x00)
Number
ActDestination
0(0x00) Fixed to 0 (0x00)
PortNumber
ActStation Target station side
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number module station number

4.2.1 Serial communication when the connected station is R series-compatible C24

4.2 Serial Communication
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_RJ71C24
(UNIT_QNCPU)
*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 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

77
 (2) When performing multi-drop link on the connected station side R series-
compatible C24 with the relayed module

(a) Configuration

Connected R series-compatible
station CPU C24
Multi-drop link
Personal computer Relayed network

Relayed Relayed
station CPU module

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
RCPU RCPU RCCPU FX5CPU
CPU
Independent
    
mode *1 Serial
Synchronous communication
*2
    
mode

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
RCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
Independent
      
mode *1 Serial
Synchronous communication
*2
      
mode
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*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

78
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
  
19200
ActBaudRate (BAUDRATE_ Match to the setting of R series-compatible C24.
19200)
ActConnectUnit Target station side
0 (0x00) Connected station side module station number
Number module station number 4
8
ActControl (TRC_DTR_OR_ Depending on the used cable.
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
IONumber *1 1023 (0x3FF)
No. 1: 992 (0x3E0)
No. 2: 993 (0x3E1)
No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01)
Bit

4.2.1 Serial communication when the connected station is R series-compatible C24

4.2 Serial Communication
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01)
Bit
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
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 station side Connected CPU:
ActIONumber *1 1023 (0x3FF) 1023 (0x3FF)
module I/O address 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)
ActMultiDrop Multi-drop channel
*2
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber number
ActNetwork
0 (0x00) Fixed to 0 (0x00)
Number
1
ActParity Fixed to 1(ODD_PARITY)
(ODD_PARITY)
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL
SERIAL)
0x01
ActPacketType PACKET_PLC1
(PACKET_PLC1)

79
 Property pattern
Property Default value
  
ActHostAddress 1.1.1.1 Fixed to NULL
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
ActDataBits 8(DATABIT_8) Fixed to 8 (0x08)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActSource
0(0x00) Fixed to 0 (0x00)
NetworkNumber
ActSourceStation
0(0x00) Fixed to 0 (0x00)
Number
ActDestination
0(0x00) Fixed to 0 (0x00)
PortNumber
ActStation
255 (0xFF) Fixed to 255 (0xFF)
Number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
0x13
ActUnitType UNIT_RJ71C24
(UNIT_QNCPU)
*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

When the connected station side R series-compatible C24 is set to the synchronous mode, always validate (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.

80
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.2.2 Serial communication when the connected station is Q series-

compatible C24

(1) When a relayed module other than the connected station side Q series-
compatible C24 exists

(a) Configuration

Connected Q series-compatible Relayed

station CPU C24 module 4
Personal computer Relayed network

Relayed Relayed
station CPU module

(b) Property patterns

Connected station CPU Relayed station CPU
QCPU Q motion Relayed network R motion
QCCPU RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 *6 *1 Ethernet    
Serial
   
communication
CC-Link    

4.2.2 Serial communication when the connected station is Q series-compatible C24

4.2 Serial Communication
Connected station CPU Relayed station CPU
Q
QCPU Q motion Relayed network QCPU
QCCPU QCCPU LCPU QSCPU motion FXCPU
(Q mode) CPU (Q mode)
CPU
CC IE Control
 *2 *3 *2 *2 
CC IE Field
MELSECNET/H      
 *6  *1 Ethernet      
Serial
*4     
communication
CC-Link      *5
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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.

81
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  

19200
ActBaudRate (BAUDRATE_ Match to the setting of Q series-compatible C24.
19200)
ActConnectUnit
0 (0x00) Connected station side module station number
Number
8
ActControl (TRC_DTR_OR_ Depending on the used cable.
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Fixed to NULL
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
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 (0x3FF) 1023 (0x3FF)
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
Connected station side Connected station side
ActIONumber*2 1023 (0x3FF) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1)
module I/O address module I/O address
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)
ActMultiDrop Multi-drop channel
*3
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber number

82
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
 *1  
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
1
ActParity Match to the setting of Q series-compatible C24.
(ODD_PARITY)
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)
ActStation Target station side
4
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_QJ71C24 (0x19)
(UNIT_QNCPU)
*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

4.2.2 Serial communication when the connected station is Q series-compatible C24

4.2 Serial Communication
1: Channel 1
2: Channel 2

83
 (2) When performing multi-drop link on the connected station side Q series-
compatible C24 with the relayed module

(a) Configuration

Connected Q series-compatible
station CPU C24
Multi-drop link
Personal computer Relayed network

Relayed Relayed
station CPU module

(b) Property patterns

Connected
Relayed station CPU
station CPU
QCPU Relayed network
R motion
(Q mode), RCPU RCCPU FX5CPU
CPU
QCCPU*3
Independent
    
mode*1 Serial
Synchronous communication
*1
    
mode

Connected
Relayed station CPU
station CPU
QCPU Relayed network
QCPU Q motion
(Q mode), QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
QCCPU*3
Independent
 *2     
mode*1 Serial
Synchronous communication
*1
 *2     
mode
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

84
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
  
19200
ActBaudRate Match to the setting of Q series-compatible C24.
(BAUDRATE_19200)
ActConnectUnitNumber 0 (0x00) Connected station side module station number
8
ActControl Depending on the used cable.
(TRC_DTR_OR_RTS)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to the target station
4
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No. 1: 992 (0x3E0)
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1) Fixed to 0 (0x00)
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)

4.2.2 Serial communication when the connected station is Q series-compatible C24

4.2 Serial Communication
ActIntelligentPreferenceBit 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 station side Connected CPU:
ActIONumber*1 1023 (0x3FF)
1023 (0x3FF) module I/O address 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)
Multi-drop channel
ActMultiDropChannelNumber*2 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
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
0x04
ActProtocolType PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)
MELSECNET/10 is not included. : 0 (0x00)
ActThroughNetworkType 0 (0x00)
MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_QJ71C24 (0x19)

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

When the connected station side Q series-compatible C24 is set to the synchronous mode, always validate (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.

86
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.2.3 Serial communication when the connected station is L series-

compatible C24

(1) When a relayed module other than the connected station side LJ71C24 exists

(a) Configuration

Connected L series-compatible Relayed

station CPU C24 module

Relayed network
4
Personal computer

Relayed Relayed
station CPU module

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field *1    
MELSECNET/H    
 Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU

4.2.3 Serial communication when the connected station is L series-compatible C24

4.2 Serial Communication
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Field *1  *2    
MELSECNET/H      
 Ethernet      
Serial communication *3     

CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

87
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
ActConnectUnit
0 (0x00) Connected station side module station number
Number
8
ActControl (TRC_DTR_OR_ Depending on the used cable.
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1) Fixed to 0 (0x00)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
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
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
Connected station side Connected station side No. 1: 992 (0x3E0)
Fixed to 1023
ActIONumber*1 1023 (0x3FF) relayed module I/O relayed module I/O No. 2: 993 (0x3E1)
(0x3FF)
address address No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
For Redundant CPU
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number

88
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
1
ActParity Match to the setting of L series-compatible C24.
(ODD_PARITY)
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)
Fixed to 255 Target station side
4
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LJ71C24 (0x54)
(UNIT_QNCPU)
*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.2.3 Serial communication when the connected station is L series-compatible C24

4.2 Serial Communication

89
 (2) When performing multi-drop link on the connected station side LJ71C24 with
the relayed module

(a) Configuration

Connected L series-compatible
station CPU C24
Multi-drop link
Personal computer Relayed network

Relayed Relayed
station CPU module

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
Independent
    
mode Serial
Synchronous communication
    
mode

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
Independent
 *1     
mode Serial
Synchronous communication
 *1     
mode
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : For Redundant CPU, serial communication modules on the main base cannot be accessed.

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
  
19200
ActBaudRate Match to the setting of L series-compatible C24.
(BAUDRATE_19200)
ActConnectUnitNumber 0 (0x00) Connected station side module station number
8
ActControl Depending on the used cable.
(TRC_DTR_OR_RTS)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to the target station

90
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
  
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Fixed to 0 Connected CPU:
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00)
(0x00) 1023 (0x3FF)
No. 1: 992 (0x3E0)
No. 2: 993 (0x3E1)
No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
4
Fixed to 1
ActDidPropertyBit 1 (0x01) Fixed to 0 (0x00) Fixed to 1 (0x01)
(0x01)
Fixed to 1
ActDsidPropertyBit 1 (0x01) Fixed to 0 (0x00) Fixed to 1 (0x01)
(0x01)
ActIntelligentPreferenceBit 0 (0x00) Fixed to 0 (0x00)
Fixed to 1023 Connected station side
ActIONumber*1 1023 (0x3FF)
(0x3FF) module I/O address
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Fixed to 0 Multi-drop channel Connected CPU:
ActMultiDropChannelNumber*2 0 (0x00)
(0x00) number 1023 (0x3FF)
No. 1: 992 (0x3E0)
No. 2: 993 (0x3E1)
No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)

4.2.3 Serial communication when the connected station is L series-compatible C24

4.2 Serial Communication
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
0x04
ActProtocolType PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)
MELSECNET/10 is not included. : 0 (0x00)
ActThroughNetworkType 0 (0x00)
MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Fixed to 0 Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00)
(0x00) 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

91
4.2.4 Serial communication when the connected station is FX
extended port

(1) Configuration

Connected FX
station CPU extended port
Multi-drop link
Personal computer Relayed network

Relayed Relayed
station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FXCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      *1
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

92
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

19200
ActBaudRate Match to the setting of FX extended port
(BAUDRATE_19200)
8
ActControl Depending on the used cable
(TRC_DTR_OR_RTS)
ActCpuTimeOut 0 (0x00) Any value specified by user in 10ms units
4
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
0x04
ActProtocolType PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIAL)
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.2.4 Serial communication when the connected station is FX extended port

4.2 Serial Communication

93
4.3 Ethernet Communication

4.3.1 Ethernet communication when the connected station is R

series-compatible E71 (TCP)

(1) Configuration

Connected R series- Relayed

station CPU compatible E71 module

Relayed network

Relayed Relayed
station CPU module

Personal computer

(2) Property patterns

Connected station
Relayed station CPU
CPU
Relayed network
R motion R motion
RCPU RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 *1,*2
Ethernet    
Serial communication    
CC-Link    

Connected station
Relayed station CPU
CPU
Relayed network
R motion QCPU Q motion
RCPU QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 *1,*2
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations cannot be accessed via R motion CPU.

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

94
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  
ActConnectUnit Connected station side
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
Number module station number
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
4
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber *3 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination 5002 for MELSOFT connection
0(0x00)
PortNumber Any port number for OPS connection. *2
ActDidProperty

4.3.1 Ethernet communication when the connected station is R series-compatible E71 (TCP)
4.3 Ethernet Communication
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
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 (0x3FF)
1023 (0x3FF)
No. 1: 992 (0x3E0)
No. 1: 992 (0x3E0)
No. 2: 993 (0x3E1) Connected station side Connected station side
ActIONumber *3 1023 (0x3FF) No. 2: 993 (0x3E1)
No. 3: 994 (0x3E2) module I/O address module I/O address
No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
No. 4: 995 (0x3E3)
For Redundant CPU
For Redundant CPU
Control system:
Control system:
976 (0x3D0)
976 (0x3D0)
No specification:
No specification:
1023 (0x3FF)
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *4 number
Target station side Target station side Connected station side Connected station side
ActNetwork
0 (0x00) module network module network R series-compatible R series-compatible
Number *5
number number E71 network number E71 network number
ActPassword Null Password set to R series-compatible E71 on the connected station side

95
 Property pattern
Property Default value
 *1  
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP(0x05)
SERIAL)
0x01(PACKET_
ActPacketType PACKET_PLC1
PLC1)
ActPortNumber 1 (PORT_1) Personal computer side COM port number
19200
ActBaudRate (BAUDRATE_ Fixed to 0 (0x00)
19200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
8(TRC_DTR_
ActControl Fixed to 0 (0x00)
OR_RTS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
1(ODD_
ActParity Fixed to 0 (0x00)
PARITY)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
ActSource
0(0x00) Personal computer side network number
NetworkNumber
ActSourceStation
0(0x00) Personal computer side station number
Number *6
Connected station side Connected station side
ActStation Target station side Target station side
255 (0xFF) R series-compatible R series-compatible
Number *5 module station number module station number
E71 station number E71 station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_RJ71EN71(0x1001)
(UNIT_QNCPU)
*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 : 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 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 : When the property pattern is  or , 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.

96
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.3.2 Ethernet communication when the connected station is R

series-compatible E71 (UDP)

(1) Configuration

Connected R series- Relayed

station CPU compatible E71 module

Relayed network

Relayed Relayed
station CPU module
4
Personal computer

(2) Property patterns

Connected station
Relayed station CPU
CPU
Relayed network
R motion R motion
RCPU RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 *1,*2
Ethernet    
Serial communication    
CC-Link    

Connected station
Relayed station CPU

4.3.2 Ethernet communication when the connected station is R series-compatible E71 (UDP)
4.3 Ethernet Communication
CPU
Relayed network
R motion QCPU Q motion
RCPU QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 *1,*2
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations cannot be accessed via R motion CPU.

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

97
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  
ActConnectUnit Connected station side
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
Number module station number
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber *3 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination For communication with IP address specified: 5001
0(0x00)
PortNumber For direct communication without IP address specified: 5003
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
For communication with IP address specified: Host name or IP address of the connected station side
ActHostAddress 1.1.1.1
For direct communication without IP address specified: 255.255.255.255
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 (0x3FF)
1023 (0x3FF)
No. 1: 992 (0x3E0)
No. 1: 992 (0x3E0)
No. 2: 993 (0x3E1) Connected station side Connected station side
ActIONumber *3 1023 (0x3FF) No. 2: 993 (0x3E1)
No. 3: 994 (0x3E2) module I/O address module I/O address
No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
No. 4: 995 (0x3E3)
For Redundant CPU
For Redundant CPU
Control system:
Control system:
976 (0x3D0)
976 (0x3D0)
No specification:
No specification:
1023 (0x3FF)
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *4 number
Target station side Target station side Connected station side Connected station side
ActNetwork
0 (0x00) module network module network R series-compatible R series-compatible
Number *5
number number E71 network number E71 network number
ActPassword Null Password set to R series-compatible E71 on the connected station side

98
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
 *1  
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_UDPIP(0x08)
SERIAL)
0x01(PACKET_
ActPacketType PACKET_PLC1
PLC1)
19200
ActBaudRate (BAUDRATE_ Fixed to 0 (0x00)
19200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
4
8(TRC_DTR_
ActControl Fixed to 0 (0x00)
OR_RTS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
1(ODD_
ActParity Fixed to 0 (0x00)
PARITY)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
ActSource
0(0x00) Personal computer side network number
NetworkNumber
ActSourceStation
0(0x00) Personal computer side station number
Number *6
Connected station side Connected station side

4.3.2 Ethernet communication when the connected station is R series-compatible E71 (UDP)
4.3 Ethernet Communication
ActStation Target station side Target station side
255 (0xFF) R series-compatible R series-compatible
Number *5 module station number module station number
E71 station number E71 station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13 For communication with IP address specified: UNIT_RJ71EN71(0x1001)
ActUnitType
(UNIT_QNCPU) 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 : 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 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 : When the property pattern is  or , 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.

99
4.3.3 Ethernet communication when the connected station is Q
series-compatible E71 (TCP)

(1) Configuration

Connected Q series-compatible Relayed

station CPU E71 module

Relayed network

Relayed Relayed
station CPU module

Personal computer

(2) Property patterns

Connected station CPU Relayed station CPU
Q Relayed
QCPU R motion
QCCPU QSCPU motion network RCPU RCCPU FX5CPU
(Q mode) CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 *6 *2 *1,*2 Ethernet    
  
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

Q Relayed Q
QCPU QCPU
QCCPU QSCPU motion network QCCPU LCPU QSCPU motion FXCPU
(Q mode) (Q mode)
CPU CPU
CC IE Control
 *3 *4 *2,*3 *3 
CC IE Field
MELSECNET/H    *2  
 *6 *2 *1,*2
 Ethernet    *2  
Serial
*5     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations cannot be accessed when the Q motion CPU is Q172CPU, Q173CPU, Q172HCPU, or Q173HCPU.
*2 : Relayed stations 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.

100
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
ActConnectUnit Connected station side
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
Number module station number
34
ActCpuType CPU type corresponds to the target station
(CPU_Q02CPU)
Target station side
4
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination 5002 for MELSOFT connection
0 (0x00)
PortNumber Any port number for OPS connection*1
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)

4.3.3 Ethernet communication when the connected station is Q series-compatible E71 (TCP)
4.3 Ethernet Communication
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
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 (0x3FF) 1023 (0x3FF)
Connected station Connected station
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
side relayed side relayed
ActIONumber *2 1023 (0x3FF) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1)
module I/O module I/O
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
address address
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)
ActMultiDrop Multi-drop channel
*3
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber number
Target station side Target station side Connected station side Connected station side
ActNetwork
0 (0x00) module network module network Q series-compatible Q series-compatible
Number *4
number number E71 network number E71 network number
ActPassword Null Password set to Q series-compatible E71 on the connected station side

101
 Property pattern
Property Default value
   
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP (0x05)
SERIAL)
ActSource
0 (0x00) Personal computer side network number
NetworkNumber
ActSourceStation
0 (0x00) Personal computer side station number
Number *5
Target station side Target station side Connected station side Connected station side
ActStation
255 (0xFF) module network module network Q series-compatible Q series-compatible
Number *4
number number E71 network number E71 network number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units.
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_QJ71E71 (0x1A)
(UNIT_QNCPU)
*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  or , 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.

102
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.3.4 Ethernet communication when the connected station is Q

series-compatible E71 (UDP)

(1) Configuration

Connected Q series-compatible Relayed

station CPU E71 module

Relayed network

Relayed Relayed
station CPU module
4
Personal computer

(2) Property patterns

Connected station CPU Relayed station CPU
Q Relayed
QCPU R motion
QCCPU QSCPU motion network RCPU RCCPU FX5CPU
(Q mode) CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 *6,*7 *2 *1,*2 Ethernet    
Serial
   
communication
CC-Link    

4.3.4 Ethernet communication when the connected station is Q series-compatible E71 (UDP)
4.3 Ethernet Communication
Connected station CPU Relayed station CPU
Q Relayed Q
QCPU QCPU
QCCPU QSCPU motion network QCCPU LCPU QSCPU motion FXCPU
(Q mode) (Q mode)
CPU CPU
CC IE Control
 *3 *4 *2,*3 *3 
CC IE Field
MELSECNET/H    *2  
 *6,*7 *2 *1,*2
   Ethernet    *2  
Serial
*5     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations cannot be accessed when the Q motion CPU is Q172CPU, Q173CPU, Q172HCPU, or Q173HCPU.
*2 : Relayed stations 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.

103
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
ActConnectUnit Connected station side
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
Number module station number
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination
0(0x00) 5001
PortNumber
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
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 (0x3FF) 1023 (0x3FF)
Connected station Connected station
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
side relayed side relayed
ActIONumber*1 1023 (0x3FF) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1)
module I/O module I/O
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
address address
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side Target station side Connected station side Connected station side
ActNetwork
0 (0x00) module network module network Q series-compatible Q series-compatible
Number*3
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

104
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_UDPIP (0x08)
SERIAL)
ActSource
0 (0x00) Personal computer side network number
NetworkNumber*4
ActSourceStation
0 (0x00) Personal computer side station number
Number*5
Target station side Target station side Connected station side Connected station side
ActStation
Number*3
255 (0xFF) module network
number
module network
number
Q series-compatible
E71 network number
Q series-compatible
E71 network number
4
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units.
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_QJ71E71 (0x1A)
(UNIT_QNCPU)
*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  or , 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.3.4 Ethernet communication when the connected station is Q series-compatible E71 (UDP)
4.3 Ethernet Communication

105
4.3.5 Ethernet communication when the connected station is L
series-compatible E71 (TCP)

(1) Configuration

Connected L series-compatible Relayed

station CPU E71 module

Relayed network

Relayed Relayed
station CPU module

Personal computer

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU*1
CC IE Control
 *3 *4 *2,*3 *3 
CC IE Field
MELSECNET/H      

Ethernet    *2  

Serial communication *5   *5   *5 

CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

*2 : Relayed stations cannot be accessed via QSCPU.
*3 : 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 : 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.

106
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
ActBaudRate (BAUDRATE_19 Fixed to 0 (0x00)
200)
ActConnectUnit Connected station side
Number
0 (0x00) Fixed to 0 (0x00)
module station number
Fixed to 0 (0x00) Fixed to 0 (0x00) 4
8
ActControl (TRC_DTR_OR_ Fixed to 0 (0x00)
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
ActDataBits 8 (DATABIT_8) Fixed to 0 (0x00)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)

4.3.5 Ethernet communication when the connected station is L series-compatible E71 (TCP)
4.3 Ethernet Communication
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination 5002 for MELSOFT connection
0 (0x00)
PortNumber Any port number for OPS connection*1
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
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 (0x3FF) 1023 (0x3FF)
Connected station Connected station
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
side relayed side relayed
ActIONumber*2 1023 (0x3FF) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1)
module I/O module I/O
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
address address
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)

107
 Property pattern
Property Default value
   
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *3 number
Target station side Target station side Connected station side Connected station side
ActNetwork
0 (0x00) module network module network L series-compatible L series-compatible
Number *4
number number E71 network number E71 network number
1
ActParity Fixed to 0 (0x00)
(ODD_PARITY)
ActPassword Null Password set to L series-compatible E71 on the connected station side
ActPortNumber 1 (PORT_1) Personal computer side port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP (0x05)
SERIAL)
ActSource
0 (0x00) Personal computer side network number
NetworkNumber
ActSource
0 (0x00) Personal computer side station number
StationNumber *5
Connected station side Connected station side
ActStation Target station side Target station side
255 (0xFF) L series-compatible L series-compatible
Number *4 module station number module station number
E71 station number E71 station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LJ71E71 (0x5C)
(UNIT_QNCPU)
*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  or , 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.

108
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.3.6 Ethernet communication when the connected station is L

series-compatible E71 (UDP)

(1) Configuration

Connected L series-compatible Relayed

station CPU E71 module

Relayed network

Relayed Relayed
station CPU module
4
Personal computer

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected

4.3.6 Ethernet communication when the connected station is L series-compatible E71 (UDP)
4.3 Ethernet Communication
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU*1
CC IE Control
 *2 *3 *3,*4 *2 
CC IE Field
MELSECNET/H      

Ethernet    *4  

Serial communication *5   *5   *5 

CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

*2 : Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode), QSCPU, and Q motion CPU relayed by
CC-Link IE Field Network cannot be accessed.
*3 : Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be
accessed.
*4 : Relayed stations cannot be accessed via QSCPU.
*5 : For Redundant CPU, serial communication modules on the main base cannot be accessed.

109
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
ActBaudRate (BAUDRATE_19 Fixed to 0 (0x00)
200)
ActConnectUnit Connected station side
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
Number module station number
8
ActControl (TRC_DTR_OR_ Fixed to 0 (0x00)
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
ActDataBits 8 (DATABIT_8) Fixed to 0 (0x00)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination
0 (0x00) 5001
PortNumber
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
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 (0x3FF) 1023 (0x3FF)
Connected station Connected station
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
side relayed side relayed
ActIONumber*2 1023 (0x3FF) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1)
module I/O module I/O
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
address address
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)

110
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *3 number
Target station side Target station side Connected station side Connected station side
ActNetwork
0 (0x00) module network module network L series-compatible L series-compatible
Number *4
number number E71 network number E71 network number
1
ActParity Fixed to 0 (0x00)
(ODD_PARITY)
ActPassword Null Password set to L series-compatible E71 on the connected station side

ActPortNumber *5 1 (PORT_1) Personal computer side port number

4
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_UDPIP (0x08)
SERIAL)
ActSource
0 (0x00) Personal computer side network number
NetworkNumber
ActSource
0 (0x00) Personal computer side station number
StationNumber *6
Connected station side Connected station side
ActStation Target station side Target station side
255 (0xFF) L series-compatible L series-compatible
Number *4 module station number module station number
E71 station number E71 station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units.
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LJ71E71 (0x5C)
(UNIT_QNCPU)

4.3.6 Ethernet communication when the connected station is L series-compatible E71 (UDP)
4.3 Ethernet Communication
*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  or , specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.
*5 : Do not use 1 to 1024 of ActPortNumber.
*6 : 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.

111
4.3.7 Ethernet communication when the connected station is RCPU
(TCP)

(1) Configuration

Connected Relayed
station CPU module

Relayed network

Relayed Relayed
Personal computer station CPU module

(2) Property patterns

Connected station CPU Relayed station CPU
R motion Relayed network R motion
RCPU RCCPU RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
*2 *2  *5
CC IE Field
MELSECNET/H    
 *3 *1,*3 Ethernet *4  *4 

Serial communication *4  *4 

CC-Link    

Connected station CPU Relayed station CPU

R motion Relayed network QCPU Q motion
RCPU RCCPU QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
*4  *2,*4   
CC IE Field
MELSECNET/H *4     
 *3  *1,*3
Ethernet *4     

Serial communication *4  *4   

CC-Link *4  *4   

: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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 of which connected station is RCPU and relayed station is FX5UCPU can be accessed.

112
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
ActPortNumber 1(PORT_1) 0(0x00)

ActBaudRate
19200(BAUDRA
TE_19200)
0(0x00) 4
8(TRC_DTR_OR
ActControl 0(0x00)
_RTS)
ActDataBits 8(DATABIT_8) 0(0x00)
ActParity 1(ODD_PARITY) 0(0x00)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
*2
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)

4.3.7 Ethernet communication when the connected station is RCPU (TCP)

4.3 Ethernet Communication
No specification:
1023 (0x3FF)
ActDestination
0(0x00) 5007
PortNumber
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
Target station Target station
RCPU, RCCPU, RCPU, RCCPU,
R motion CPU, R motion CPU,
ActIntelligent QCPU (Q mode), QCPU (Q mode),
0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit QCCPU, QCCPU,
LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the Other than the
above : 0 (0x00) above : 0 (0x00)

113
 Property pattern
Property Default value
 *1  
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to 1023 (0x3FF) Connected CPU:
For multiple CPUs 1023 (0x3FF)
Connected station Connected station
Connected CPU: No. 1: 992 (0x3E0)
side relayed side relayed
ActIONumber*2 1023 (0x3FF) 1023 (0x3FF) No. 2: 993 (0x3E1)
module I/O module I/O
No. 1: 992 (0x3E0) No. 3: 994 (0x3E2)
address address
No. 2: 993 (0x3E1) No. 4: 995 (0x3E3)
No. 3: 994 (0x3E2) For Redundant CPU
No. 4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
*3
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number *4
number
ActPassword Null Password set to the connected station side
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP(0x05)
SERIAL)
ActStation Target station side
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number *4 module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units.
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_RETHER(0x1002)
(UNIT_QNCPU)
*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 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 , specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

114
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.3.8 Ethernet communication when the connected station is RCPU

(UDP)

(1) Configuration

Connected Relayed
station CPU module

Relayed network
4
Relayed Relayed
Personal computer station CPU module

(2) Property patterns

Connected station CPU Relayed station CPU
R motion Relayed network R motion
RCPU RCCPU RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
*2 *2  *5
CC IE Field
MELSECNET/H    
 *3 *1,*3 Ethernet *4  *4 

Serial communication *4  *4 

CC-Link    

Connected station CPU Relayed station CPU

4.3.8 Ethernet communication when the connected station is RCPU (UDP)

4.3 Ethernet Communication
R motion Relayed network QCPU Q motion
RCPU RCCPU QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
*4  *2,*4   
CC IE Field
MELSECNET/H *4     
 *3  *1,*3
Ethernet *4  *4   

Serial communication *4  *4   

CC-Link *4  *4   

: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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 of which connected station is RCPU and relayed station is FX5UCPU can be accessed.

115
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
ActPortNumber 1(PORT_1) 0(0x00)
19200(BAUDRA
ActBaudRate 0(0x00)
TE_19200)
8(TRC_DTR_OR
ActControl 0(0x00)
_RTS)
ActDataBits 8(DATABIT_8) 0(0x00)
ActParity 1(ODD_PARITY) 0(0x00)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
*2
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
Target station Target station
RCPU, RCCPU, RCPU, RCCPU,
R motion CPU, R motion CPU,
ActIntelligent QCPU (Q mode), QCPU (Q mode),
0(0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit QCCPU QCCPU
LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the Other than the
above : 0 (0x00) above : 0 (0x00)
For communication with IP address specified: Host name or IP address of the connected station side
ActHostAddress 1.1.1.1
For direst communication without IP address specified: 255.255.255.255
ActDestination For communication with IP address specified: 5006
0(0x00)
PortNumber For direct communication without IP address specified: 5008

116
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
 *1  
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to 1023 (0x3FF) Connected CPU:
For multiple CPUs 1023 (0x3FF)
Connected CPU: No. 1: 992 (0x3E0) Connected station Connected station
ActIONumber*2 1023 (0x3FF) 1023 (0x3FF) No. 2: 993 (0x3E1) side module I/O side module I/O
No. 1: 992 (0x3E0) No. 3: 994 (0x3E2) address address
No. 2: 993 (0x3E1) No. 4: 995 (0x3E3) 4
No. 3: 994 (0x3E2) For Redundant CPU
No. 4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
*3
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number *4
number
0x01
ActPacketType PACKET_PLC1
(iPACKET_PLC1)
ActPassword Null Password set to the connected station side
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_UDPIP(0x08)
SERIAL)
ActStation Target station side

4.3.8 Ethernet communication when the connected station is RCPU (UDP)

4.3 Ethernet Communication
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number *4 module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units.
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13 For communication with IP address specified: UNIT_RETHER(0x1002)
ActUnitType
(UNIT_QNCPU) 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 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 , specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

117
4.3.9 Ethernet communication when the connected station is
FX5CPU (TCP)

(1) Configuration

Connected Relayed
station CPU module

Relayed network

Relayed Relayed
Personal computer station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FX5CPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   *1
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FX5CPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Only CC-Link IE Field Network of which relayed station is FX5UCPU can be accessed.

118
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200
ActBaudRate 0 (0x00)
(BAUDRATE_19200)
ActControl 8(TRC_DTR_OR_RTS) 0 (0x00)

ActCpuType
34
(CPU_Q02CPU)
CPU type corresponding to the target station 4
ActDataBits 8(DATABIT_8) 0 (0x00)
ActDestinationPortNumber 0(0x00) 5562
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
Target station side module
ActNetworkNumber 0(0x00) 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)
0x04
ActProtocolType PROTOCOL_TCPIP(0x05)
(PROTOCOL_SERIAL)
Target station side module
ActStationNumber 255(0xFF) 255(0xFF)
station number
ActStopBits 0(STOPBIT_ONE) 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK) 0 (0x00)
ActThroughNetworkType 0(0x00) 1 (0x01) 0(0x00)

4.3.9 Ethernet communication when the connected station is FX5CPU (TCP)

4.3 Ethernet Communication
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXETHER(0x2001)

119
4.3.10 Ethernet communication when the connected station is
FX5CPU (UDP)

(1) Configuration

Connected Relayed
station CPU module

Relayed network

Relayed Relayed
Personal computer station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FX5CPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   *1
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FX5CPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Only CC-Link IE Field Network of which relayed station is FX5UCPU can be accessed.

120
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200
ActBaudRate 0 (0x00)
(BAUDRATE_19200)
ActControl 8(TRC_DTR_OR_RTS) 0 (0x00)

ActCpuType
34
(CPU_Q02CPU)
CPU type corresponding to the target station 4
ActDataBits 8(DATABIT_8) 0 (0x00)
ActDestinationPortNumber 0(0x00) 5560
ActHostAddress 1.1.1.1 255.255.255.255
Target station side module
ActNetworkNumber 0(0x00) 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)
0x04
ActProtocolType PROTOCOL_UDPIP(0x08)
(PROTOCOL_SERIAL)
Target station side module
ActStationNumber 255(0xFF) 255(0xFF)
station number
ActStopBits 0(STOPBIT_ONE) 0 (0x00)
ActSumCheck 0(NO_SUM_CHECK) 0 (0x00)
ActThroughNetworkType 0(0x00) 1 (0x01) 0 (0x00)

4.3.10 Ethernet communication when the connected station is FX5CPU (UDP)

4.3 Ethernet Communication
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXVETHER_DIRECT(0x2002)

121
4.3.11 Ethernet communication when the connected station is built-in
Ethernet port QCPU (TCP)

(1) Configuration

Connected Relayed
station CPU module

Relayed network

Relayed Relayed
Personal computer station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
QnUDE(H) R motion
RCPU RCCPU FX5CPU
CPU CPU*4
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QnUDE(H) QCPU Q motion
QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
 *1 *2 *1 *1 
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication *3     
CC-Link      

122
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected
Relayed station CPU
station CPU
Relayed network
R motion
QCCPU RCPU RCCPU FX5CPU
CPU*4
CC IE Control
   
CC IE Field
MELSECNET/H    
*4,*5,*6 Ethernet    
Serial communication    
CC-Link    

Connected
4
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
QCCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
CC IE Field
 *1 *2 *1 *1 

MELSECNET/H      
*4,*5,*6 Ethernet      
Serial communication      
CC-Link      

Connected
Relayed station CPU
station CPU
Relayed network
Q motion R motion
RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
   
CC IE Field

4.3.11 Ethernet communication when the connected station is built-in Ethernet port QCPU (TCP)
4.3 Ethernet Communication
MELSECNET/H    
*7 Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
Q motion QCPU Q motion
QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*7 Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

124
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF) 4
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination
0 (0x00) 5007
PortNumber
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)

4.3.11 Ethernet communication when the connected station is built-in Ethernet port QCPU (TCP)
4.3 Ethernet Communication
Bit
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module
Target station Target station
RCPU, RCCPU, RCPU, RCCPU,
R motion CPU, R motion CPU,
ActIntelligent QCPU(Q mode), QCPU(Q mode),
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit QCCPU, QCCPU,
LCPU :1 (0x01) LCPU :1 (0x01)
Other than the Other than the
above :0 (0x00) above :0 (0x00)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to 1023 (0x3FF) Connected CPU:
For multiple CPUs 1023 (0x3FF)
Connected CPU: No. 1: 992 (0x3E0) Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) 1023 (0x3FF) No. 2: 993 (0x3E1) relayed module I/O relayed module I/O
No. 1: 992 (0x3E0) No. 3: 994 (0x3E2) address address
No. 2: 993 (0x3E1) No. 4: 995 (0x3E3)
No. 3: 994 (0x3E2) For Redundant CPU
No. 4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number

125
 Property pattern
Property Default value
   
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number*3
number
ActPassword Null Remote password set to the connected station
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP (0x05)
SERIAL)
ActStation Target station side
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number*3 module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_QNETHER (0x2C)
(UNIT_QNCPU)
*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  or , specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

126
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.3.12 Ethernet communication when the connected station is built-in

Ethernet port QCPU (UDP)

(1) Configuration

Connected Relayed
station CPU module

Relayed network
4
Relayed Relayed
Personal computer station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
QnUDE(H) R motion
RCPU RCCPU FX5CPU
CPU CPU*4
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

4.3.12 Ethernet communication when the connected station is built-in Ethernet port QCPU (UDP)
4.3 Ethernet Communication
Connected
Relayed station CPU
station CPU
Relayed network
QnUDE(H) QCPU Q motion
QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
 *1 *2 *1 *1 
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication *3     
CC-Link      

127
 Connected
Relayed station CPU
station CPU
Relayed network
R motion
QCCPU RCPU RCCPU FX5CPU
CPU*4
CC IE Control
   
CC IE Field
MELSECNET/H    
*4,*5,*6
Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
QCCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
 *1 *2 *1 *1 
CC IE Field
MELSECNET/H      
*4,*5,*6
Ethernet      
Serial communication      
CC-Link      

Connected
Relayed station CPU
station CPU
Relayed network
Q motion R motion
RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*7
Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
Q motion QCPU Q motion
QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*7
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

128
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

*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.3.12 Ethernet communication when the connected station is built-in Ethernet port QCPU (UDP)
4.3 Ethernet Communication

129
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination For communication with IP address specified: 5006
0 (0x00)
PortNumber For direct communication without IP address specified: Unused
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
For communication with specified IP address: Host name or IP address of
ActHostAddress 1.1.1.1 the connected station side module
For direct communication without specified IP address: The specification is invalid.
Target station Target station
RCPU, RCCPU, RCPU, RCCPU,
R motion CPU, R motion CPU,
ActIntelligent QCPU(Q mode), QCPU(Q mode),
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit QCCPU, QCCPU,
LCPU :1 (0x01) LCPU :1 (0x01)
Other than the Other than the
above :0 (0x00) above :0 (0x00)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to 1023 (0x3FF) Connected CPU:
For multiple CPUs 1023 (0x3FF)
Connected CPU: No. 1: 992 (0x3E0) Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) 1023 (0x3FF) No. 2: 993 (0x3E1) relayed module I/O relayed module I/O
No. 1: 992 (0x3E0) No. 3: 994 (0x3E2) address address
No. 2: 993 (0x3E1) No. 4: 995 (0x3E3)
No. 3: 994 (0x3E2) For Redundant CPU
No. 4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)

130
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number*3
number
ActPassword Null Remote password set to the connected station
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_UDPIP (0x08)
SERIAL)
ActStation Target station side
4
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number*3 module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13 For communication with specified IP address: UNIT_QNETHER (0x2C)
ActUnitType
(UNIT_QNCPU) For direct communication without specified IP address: UNIT_QNETHER_DIRECT (0x2D)
*1 : For the I/O address, specify the value of the actual start I/O number divided by 16.
*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  or , specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

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

131
4.3.13 Ethernet communication when the connected station is built-in
Ethernet port LCPU (TCP)

(1) Configuration

Connected Relayed
station CPU module

Relayed network

Relayed Relayed
Personal computer station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*1    
MELSECNET/H    
 Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Field*1  *2    
MELSECNET/H      
 Ethernet      
Serial communication *3     
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

132
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
ActBaudRate (BAUDRATE_19 Fixed to 0 (0x00)
200)
8
ActControl (TRC_DTR_OR_ Fixed to 0 (0x00) 4
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
ActDataBits 8 (DATABIT_8) Fixed to 0 (0x00)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1) Fixed to 0 (0x00)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)

4.3.13 Ethernet communication when the connected station is built-in Ethernet port LCPU (TCP)
4.3 Ethernet Communication
No specification:
1023 (0x3FF)
ActDestination
0 (0x00) 5007
PortNumber
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
Target station Target station
RCPU, RCCPU, RCPU, RCCPU,
R motion CPU, R motion CPU,
ActIntelligent QCPU(Q mode), QCPU(Q mode),
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit QCCPU, QCCPU,
LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the Other than the
above : 0 (0x00) above : 0 (0x00)

133
 Property pattern
Property Default value
   
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
For single CPU Connected station side Connected station side No. 1: 992 (0x3E0)
ActIONumber*1 1023 (0x3FF) Fixed to 1023 relayed module I/O relayed module I/O No. 2: 993 (0x3E1)
(0x3FF) address address No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
For Redundant CPU
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetworkNumber*3 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
1
ActParity Fixed to 0 (0x00)
(ODD_PARITY)
ActPassword Null Password set to the connected station side
ActPortNumber 1 (PORT_1) Fixed to 0 (0x00)
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP (0x05)
SERIAL)
Fixed to 255 Target station side
ActStationNumber*3 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units.
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LNETHER (0x52)
(UNIT_QNCPU)
*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  or , specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

134
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.3.14 Ethernet communication when the connected station is built-in

Ethernet port LCPU (UDP)

(1) Configuration

Connected Relayed
station CPU module

Relayed network
4
Relayed Relayed
Personal computer station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*1    
MELSECNET/H    
 Ethernet    
Serial communication    
CC-Link    

Connected

4.3.14 Ethernet communication when the connected station is built-in Ethernet port LCPU (UDP)
4.3 Ethernet Communication
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Field*1  *2    
MELSECNET/H      
 Ethernet      
Serial communication *3     
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

135
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
ActBaudRate (BAUDRATE_19 Fixed to 0 (0x00)
200)
8
ActControl (TRC_DTR_OR_ Fixed to 0 (0x00)
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
ActDataBits 8 (DATABIT_8) Fixed to 0 (0x00)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1) Fixed to 0 (0x00)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination For communication with IP address specified: 5006
0 (0x00)
PortNumber 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)
For communication with specified IP address: Host name or IP address of
ActHostAddress 1.1.1.1 the connected station side module
For direct communication without specified IP address: 255.255.255.255
Target station Target station
RCPU, RCCPU, RCPU, RCCPU,
R motion CPU, R motion CPU,
ActIntelligent QCPU(Q mode), QCPU(Q mode),
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit QCCPU, QCCPU,
LCPU :1 (0x01) LCPU :1 (0x01)
Other than the Other than the
above :0 (0x00) above :0 (0x00)

136
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
For single CPU No. 1: 992 (0x3E0)
Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) Fixed to 1023 No. 2: 993 (0x3E1)
module I/O address module I/O address
(0x3FF) No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
For Redundant CPU
4
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetworkNumber*3 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
1
ActParity Fixed to 0 (0x00)
(ODD_PARITY)
ActPassword Null Remote password set to the connected station
ActPortNumber 1 (PORT_1) Fixed to 0 (0x00)
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_UDPIP (0x08)
SERIAL)

4.3.14 Ethernet communication when the connected station is built-in Ethernet port LCPU (UDP)
4.3 Ethernet Communication
Fixed to 255 Target station side
ActStationNumber*3 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13 For communication with specified IP address: UNIT_LNETHER(0x52)
ActUnitType
(UNIT_QNCPU) 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  or , specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

137
4.3.15 Ethernet communication when the connected station is
Ethernet adapter module (TCP)

(1) Configuration

Connected CC-Link IE Field Relayed

station CPU Network module module

Relayed network

Relayed Relayed
Ethernet adapter module station CPU module
Personal computer

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
QnUDE(H) R motion
RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QnUDE(H) QCPU Q motion
QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
 *1 *2   
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      
CC-Link      

138
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*2    
MELSECNET/H    
 Ethernet    
Serial communication    
CC-Link    

Connected 4
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Field*2  *1    
MELSECNET/H      
 Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*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.3.15 Ethernet communication when the connected station is Ethernet adapter module (TCP)
4.3 Ethernet Communication

139
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of the Ethernet adapter module
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0) Connected station side Connected station side
*1
Connected CPU:
ActIONumber 1023 (0x3FF) No. 2: 993 (0x3E1) relayed module I/O relayed module I/O
1023 (0x3FF)
No. 3: 994 (0x3E2) address address
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Connected station side Connected station side Connected station side
Target station side
ActNetwork CC-Link IE Field CC-Link IE Field CC-Link IE Field
0 (0x00) module network
Number*3 Network module Network module Network module
number
station number station number station number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP (0x05)
SERIAL)

140
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Connected station side Connected station side Connected station side
ActStation CC-Link IE Field Target station side CC-Link IE Field CC-Link IE Field
255 (0xFF)
Number*3 Network module module station number Network module Network module
station number station number station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
4
ActUnitType UNIT_NZ2GF_ETB (0x59)
(UNIT_QNCPU)
*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 , , or , 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 , specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4.3.15 Ethernet communication when the connected station is Ethernet adapter module (TCP)
4.3 Ethernet Communication

141
4.3.16 Ethernet communication when the connected station is
Ethernet adapter module (UDP)

(1) Configuration

Connected CC-Link IE Field Relayed

station CPU Network module module

Relayed network

Relayed Relayed
Ethernet adapter module station CPU module
Personal computer

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
QnUDE(H) R motion
RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QnUDE(H) QCPU Q motion
QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
 *1 *2   
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      
CC-Link      

142
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*2    
MELSECNET/H    
 Ethernet    
Serial communication    
CC-Link    

Connected 4
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Field*2  *1    
MELSECNET/H      
 Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*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.3.16 Ethernet communication when the connected station is Ethernet adapter module (UDP)
4.3 Ethernet Communication

143
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
For communication with specified IP address: Host name or IP address of the Ethernet adapter module
ActHostAddress 1.1.1.1
For direct communication without specified IP address: The specification is invalid.
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to 1023 (0x3FF) Connected CPU:
For multiple CPUs 1023 (0x3FF)
Connected CPU: No. 1: 992 (0x3E0) Connected station side Connected station side
*1 1023 (0x3FF) 1023 (0x3FF) No. 2: 993 (0x3E1) relayed module I/O relayed module I/O
ActIONumber
No. 1: 992 (0x3E0) No. 3: 994 (0x3E2) address address
No. 2: 993 (0x3E1) No. 4: 995 (0x3E3)
No. 3: 994 (0x3E2) For Redundant CPU
No. 4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Connected station side Connected station side Connected station side
ActNetwork CC-Link IE Field Target station side CC-Link IE Field CC-Link IE Field
0 (0x00)
Number*3 Network module module station number Network module Network module
station number station number station number

144
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_UDPIP (0x08)
SERIAL)
Connected station side Connected station side Connected station side
ActStation CC-Link IE Field Target station side CC-Link IE Field CC-Link IE Field
255 (0xFF)
Number*3 Network module module station number Network module Network module
station number station number station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units 4
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13 For communication with specified IP address: UNIT_NZ2GF_ETB (0x59)
ActUnitType
(UNIT_QNCPU) For direct communication without specified IP address: UNIT_NZ2GF_ETB_DIRECT (0x5A)
*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 , , or , 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 , specify the value set in the target station side parameter for ActNetworkNumber and
ActStationNumber.

4.3.16 Ethernet communication when the connected station is Ethernet adapter module (UDP)
4.3 Ethernet Communication

145
4.3.17 Ethernet communication when the connected station is
Ethernet adapter (TCP)

(1) Configuration
Ethernet Connected Relayed
adapter station CPU module

Relayed network

Relayed Relayed
station CPU module
Personal computer

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1
Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FXCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*1
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

146
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
ActHostAddress 1.1.1.1 Host name or IP address of the connected station side module

ActProtocolType
0x04
(PROTOCOL_SERIAL)
PROTOCOL_TCPIP 4
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXETHER

4.3.17 Ethernet communication when the connected station is Ethernet adapter (TCP)
4.3 Ethernet Communication

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

(1) Configuration
Ethernet Connected Relayed
adapter station CPU module

Relayed network

Relayed Relayed
station CPU module
Personal computer

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1
Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FXCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*1
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
0x04
ActProtocolType PROTOCOL_UDPIP
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXETHER_DIRECT

148
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.3.19 Ethernet communication when the connected station is robot

controller

(1) Configuration

Robot controller

Personal computer

(2) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

0x04
ActProtocolType RC_PROTOCOL_TCPIP(0x02)
(PROTOCOL_SERIAL)
34
ActCpuType Robot controller type(0x013001)
(CPU_Q02CPU)
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

4.3.19 Ethernet communication when the connected station is robot controller

4.3 Ethernet Communication
ActTimeOut 10000 Any value specified by user in ms units.
ActCpuTimeOut 0(0x00) Any value specified by user in 10ms units.
ActMultiDropChanne
8(TRC_DTR_OR_RTS) Retry count
lNumber
ActMxUnitSeries 0(0x00) 2(0x02)

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

149
4.4 COM Communication

4.4.1 CPU COM communication when the connected station is

FX5CPU

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FX5CPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   *1
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FX5CPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Only CC-Link IE Field Network of which relayed station is FX5UCPU can be accessed.

150
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
ActBaudRate
(BAUDRATE_19200) 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
4
ActDidPropertyBit 1 (0x01) 0 (0x00)
ActDsidPropertyBit 1 (0x01) 0 (0x00)
Target station side module
ActNetworkNumber 0(0x00) 0(0x00)
network number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType PROTOCOL_SERIAL(0x04)
(PROTOCOL_SERIAL)
Target station side module
ActStationNumber 255(0xFF) 255(0xFF)
station number
ActHostAddress 1.1.1.1 NULL
ActTimeOut 10000 Any value specified by user in ms units.
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXVCPU(0x2000)

4.4.1 CPU COM communication when the connected station is FX5CPU

4.4 COM Communication

151
4.4.2 CPU COM communication when the connected station is QCPU
(Q mode)

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module

(2) Property patterns

Connected station CPU Relayed station CPU
QCPU Relayed network R motion
QCCPU RCPU RCCPU FX5CPU
(Q mode) CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 *4
Ethernet    
Serial communication    
CC-Link    

Connected station CPU Relayed station CPU

QCPU Relayed network QCPU Q motion
QCCPU QCCPU LCPU QSCPU FXCPU
(Q mode) (Q mode) CPU
CC IE Control
 *1 *2 *1 *1 
CC IE Field
MELSECNET/H      
 *4 Ethernet      
Serial communication      

CC-Link      *3
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

152
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)

ActControl
8
(TRC_DTR_OR_ Depending on the used cable.
4
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:

4.4.2 CPU COM communication when the connected station is QCPU (Q mode)
4.4 COM Communication
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU :1 (0x01) LCPU :1 (0x01)
Other than the Other than the
above :0 (0x00) above :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 (0x3FF) 1023 (0x3FF)
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
Connected station side Connected station side
ActIONumber*2 1023 (0x3FF) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1)
module I/O address module I/O address
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)

153
 Property pattern
Property Default value
 *1  
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*3 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)
ActStation Target station side
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units.
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_QNCPU (0x13)
(UNIT_QNCPU)
*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

154
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.4.3 CPU COM communication when the connected station is LCPU

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module 4
(2) Property patterns
Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field *1    
MELSECNET/H    
 Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU

4.4.3 CPU COM communication when the connected station is LCPU

4.4 COM Communication
(Q mode) CPU
CC IE Field *1  *2    
MELSECNET/H      
 Ethernet      
Serial communication *3     
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

155
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
8
ActControl (TRC_DTR_OR_ Depending on the used cable.
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
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 (0x3FF) 1023 (0x3FF)
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1) Fixed to 0 (0x00)
IONumber
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 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
Target station Target station
RCPU, RCCPU, RCPU, RCCPU,
QCPU (Q mode), QCPU (Q mode),
ActIntelligent
0 (0x00) Fixed to 0 (0x00) QCCPU, QCCPU, Fixed to 0 (0x00)
PreferenceBit
LCPU :1 (0x01) LCPU :1 (0x01)
Other than the Other than the
above :0 (0x00) above :0 (0x00)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No. 1: 992 (0x3E0)
Fixed to 1023 Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) No. 2: 993 (0x3E1)
(0x3FF) module I/O address module I/O address
No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
For Redundant CPU
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)

156
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
ActMultiDrop
0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)
Fixed to 255 Target station side
4
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units.
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LNCPU (0x50)
(UNIT_QNCPU)
*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.4.3 CPU COM communication when the connected station is LCPU

4.4 COM Communication

157
4.4.4 CPU COM communication when the connected station is Q
motion CPU

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
Q motion R motion
RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1
Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
Q motion QCPU Q motion
QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*1
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

158
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

19200 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
ActBaudRate
(BAUDRATE_19200) BAUDRATE_57600, BAUDRATE_115200
8
ActControl Depending on the used cable.
(TRC_DTR_OR_RTS)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to the target station
4
For multiple CPUs
Control CPU: 1023 (0x3FF)
ActIONumber 1023 (0x3FF) No. 2: 993 (0x3E1)
No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units.
ActUnitType 0x13 (UNIT_QNCPU) UNIT_QNMOTION (0x1C)

4.4.4 CPU COM communication when the connected station is Q motion CPU
4.4 COM Communication

159
4.4.5 CPU COM communication when the connected station is
FXCPU

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FXCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      
CC-Link      *1
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

160
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
FX0(S), FX0N, FX1, FX1S, FX2(C)
(Fixed to BAUDRATE_9600)
FX1N(C), FX2N(C)
19200
ActBaudRate (BAUDRATE_9600, BAUDRATE_19200)
(BAUDRATE_19200)
FX3S, FX3UC, FX3G(C)
4
(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) Fixed to 1023 (0x3FF)
ActDidPropertyBit 1 (0x01) 0 (0x00)
ActDsidPropertyBit 1 (0x01) 0 (0x00)
Module number of the
ActIONumber 1023 (0x3FF) Fixed to 0 (0x00)
connected station
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType PROTOCOL_SERIAL(0x04)
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units.
Target station side module station
ActUnitNumber 0 (0x00) Fixed to 0 (0x00)
number

4.4.5 CPU COM communication when the connected station is FXCPU

4.4 COM Communication
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXCPU(0x0F)

161
4.4.6 COM communication when the connected station is inverter

(1) Configuration

Inverter

Personal computer

(2) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

ActMxUnitSeries 0 (0x00) 1 (0x01)
0x04
ActProtocolType COMM_RS232C (0x00)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) Inverter station number (0 to 31)
ActCpuType 34 (CPU_Q02CPU) Fixed to INV_A800 (0x1E60)
ActPortNumber 1 (PORT_1) Personal computer side COM port number
BAUDRATE_4800, BAUDRATE_9600,
19200
ActBaudRate BAUDRATE_19200, BAUDRATE_38400,
(BAUDRATE_19200)
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 1 (CRLF_CR) CRLF_NONE, CRLF_CR, CRLF_CRLF
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.

162
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.4.7 COM communication when the connected station is robot

controller

(1) Configuration

Robot controller

4
Personal computer

(2) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

0x04
ActProtocolType RC_PROTOCOL_SERIAL(0x01)
(PROTOCOL_SERIAL)
34
ActCpuType Robot controller type(0x013001)
(CPU_Q02CPU)
ActPortNumber 1(PORT_1) Personal computer side COM port number
BAUDRATE_4800, BAUDRATE_9600,
19200
ActBaudRate BAUDRATE_19200, BAUDRATE_38400,

4.4.7 COM communication when the connected station is robot controller

4.4 COM Communication
(BAUDRATE_19200)
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.
ActDataBits 8(DATABIT_8) DATABIT_7, DATABIT_8
ActParity 1(ODD_PARITY) NO_PARRITY, ODD_PARITY, EVEN_PARITY
ActStopBits 0(STOPBIT_ONE) ONESTOPBIT, ONE5STOPBITS, TWOSTOPBITS
ActMultiDropChanne
0(0x00) Retry count
lNumber
ActThroughNetwork
0(0x00) Procedural/Nonprocedural (0/1)
Type
ActMxUnitSeries 0(0x00) 2(0x02)

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

163
4.5 USB Communication

4.5.1 USB communication when the connected station is RCPU

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
RCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
*1   *2
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
RCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
  *1   
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*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 of which relayed station is FX5UCPU can be accessed.

164
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
4
Target station side
For multiple CPUs
For single CPU
Connected CPU:
Fixed to 1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No. 1: 992 (0x3E0)
ActDestination Connected CPU:
*2
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1)
IONumber 1023 (0x3FF)
No. 3: 994 (0x3E2)
No. 1: 992 (0x3E0)
No. 4: 995 (0x3E3)
No. 2: 993 (0x3E1)
For Redundant CPU
No. 3: 994 (0x3E2)
Control system:
No. 4: 995 (0x3E3)
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
Target station Target station

4.5.1 USB communication when the connected station is RCPU

4.5 USB Communication
RCPU, RCCPU, RCPU, RCCPU,
QCPU (Q mode), QCPU (Q mode),
ActIntelligent
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) QCCPU, QCCPU,
PreferenceBit
LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the Other than the
above : 0 (0x00) above : 0 (0x00)
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 (0x3FF)
1023 (0x3FF)
No. 1: 992 (0x3E0)
No. 1: 992 (0x3E0)
No. 2: 993 (0x3E1) Connected station side Connected station side
ActIONumber *2 1023 (0x3FF) No. 2: 993 (0x3E1)
No. 3: 994 (0x3E2) module I/O address module I/O address
No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
No. 4: 995 (0x3E3)
For Redundant CPU
For Redundant CPU
Control system:
Control system:
976 (0x3D0)
976 (0x3D0)
No specification:
No specification:
1023 (0x3FF)
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *3 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number

165
 Property pattern
Property Default value
 *1  
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USB
SERIAL)
0x01(PACKET_
ActPacketType PACKET_PLC1
PLC1)
ActStation Target station side
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number module station number
ActConnectUnit
0(0x00) Fixed to 0 (0x00)
Number
ActPortNumber 1(PORT_1) Fixed to 1 (PORT_1)
19200
ActBaudRate (BAUDRATE_ Fixed to 0 (0x00)
19200)
ActHostAddress 1.1.1.1 Fixed to NULL
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
8(TRC_DTR_
ActControl Fixed to 0 (0x00)
OR_RTS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
1
ActParity Fixed to 0 (0x00)
(ODD_PARITY)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActSource
0(0x00) Fixed to 0 (0x00)
NetworkNumber
ActSourceStation
0(0x00) Fixed to 0 (0x00)
Number
ActDestination
0(0x00) Fixed to 0 (0x00)
PortNumber
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_RUSB
(UNIT_QNCPU)
*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 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

166
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.5.2 USB communication when the connected station is R motion

CPU

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed 4
station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion R motion
RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1,*2
Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU

4.5.2 USB communication when the connected station is R motion CPU

4.5 USB Communication
Relayed network
R motion QCPU Q motion
QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*1,*2
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations cannot be accessed via R motion CPU.

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

167
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
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 (0x3FF) 1023 (0x3FF)
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1)
IONumber *2
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
Target station Target station
RCPU, RCCPU, RCPU, RCCPU,
QCPU (Q mode), QCPU (Q mode),
ActIntelligent
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) QCCPU, QCCPU,
PreferenceBit
LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the Other than the
above : 0 (0x00) above : 0 (0x00)
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 (0x3FF)
1023 (0x3FF)
No. 1: 992 (0x3E0)
No. 1: 992 (0x3E0)
No. 2: 993 (0x3E1) Connected station side Connected station side
ActIONumber *2 1023 (0x3FF) No. 2: 993 (0x3E1)
No. 3: 994 (0x3E2) module I/O address module I/O address
No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
No. 4: 995 (0x3E3)
For Redundant CPU
For Redundant CPU
Control system:
Control system:
976 (0x3D0)
976 (0x3D0)
No specification:
No specification:
1023 (0x3FF)
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *3 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number

168
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
 *1  
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USB
SERIAL)
ActStation Target station side
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
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
module station number
Target station side
module station number
4
0x13
ActUnitType UNIT_RUSB
(UNIT_QNCPU)
*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 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.5.2 USB communication when the connected station is R motion CPU

4.5 USB Communication

169
4.5.3 USB communication when the connected station is QCPU (Q
mode)

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
QCPU R motion
RCPU RCCPU FX5CPU
(Q mode) CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QCPU Q motion
QCCPU LCPU QSCPU FXCPU
(Q mode) (Q mode) CPU
CC IE Control
 *1 *2 *1 *1 
CC IE Field
MELSECNET/H      
 Ethernet      
Serial communication *3     

CC-Link      *4

170
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected
Relayed station CPU
station CPU
Relayed network
R motion
QCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    
4
Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
QCCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
 *1 *2 *1 *1 
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*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.5.3 USB communication when the connected station is QCPU (Q mode)

4.5 USB Communication
*4 : Supported by FX3G(C)CPU and FX3U(C)CPU within the own network only.

171
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
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 (0x3FF) 1023 (0x3FF)
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1)
IONumber
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU :1 (0x01) LCPU :1 (0x01)
Other than the Other than the
above :0 (0x00) above :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 (0x3FF) 1023 (0x3FF)
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
Connected station side Connected station side
ActIONumber*2 1023 (0x3FF) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1)
module I/O address module I/O address
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*3 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number

172
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
 *1  
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USB (0x0D)
SERIAL)
ActStation Target station side
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
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
module station number
Target station side
module station number
4
0x13
ActUnitType UNIT_QNUSB (0x16)
(UNIT_QNCPU)
*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.5.3 USB communication when the connected station is QCPU (Q mode)

4.5 USB Communication

173
4.5.4 USB communication when the connected station is LCPU

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*1    
MELSECNET/H    
 Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Field*1  *2    
MELSECNET/H      
 Ethernet      
Serial communication *3     

CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

174
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
ActBaudRate (BAUDRATE_19 Fixed to 0 (0x00)
200)
8
ActControl (TRC_DTR_OR_ Fixed to 0 (0x00) 4
RTS)
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
ActDataBits 8 (DATABIT_8) 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 (0x3FF) 1023 (0x3FF)
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1) Fixed to 0 (0x00)
IONumber
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)

4.5.4 USB communication when the connected station is LCPU

4.5 USB Communication
No specification: No specification:
1023 (0x3FF) 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
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU :1 (0x01) LCPU :1 (0x01)
Other than the Other than the
above :0 (0x00) above :0 (0x00)
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No. 1: 992 (0x3E0)
Fixed to 1023 Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) No. 2: 993 (0x3E1)
(0x3FF) module I/O address module I/O address
No. 3: 994 (0x3E2)
No. 4: 995 (0x3E3)
For Redundant CPU
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)

175
 Property pattern
Property Default value
   
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
1
ActParity Fixed to 0 (0x00)
(ODD_PARITY)
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USB (0x0D)
SERIAL)
Fixed to 255 Target station side
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LNUSB (0x51)
(UNIT_QNCPU)
*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

176
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.5.5 USB communication when the connected station is QSCPU

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module 4
(2) Property patterns
Connected
Relayed station CPU
station CPU
Relayed network
R motion
QSCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1
Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion

4.5.5 USB communication when the connected station is QSCPU

4.5 USB Communication
QSCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*1
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations cannot be accessed via QSCPU.

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to the target station
0x04
ActProtocolType PROTOCOL_USB (0x0D)
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13 (UNIT_QNCPU) UNIT_QSUSB (0x29)

177
4.5.6 USB communication when the connected station is Q motion
CPU

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
Q motion R motion
RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1
Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
Q motion QCPU Q motion
QCCPU LCPU QSCPU FXCPU
CPU (Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*1
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

178
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to the target station
For multiple CPUs
Control CPU: F1023 (0x3FF)
ActIONumber 1023 (0x3FF) No. 2: 993 (0x3E1)
No. 3: 994 (0x3E2) 4
No. 4: 995 (0x3E3)
0x04
ActProtocolType PROTOCOL_USB (0x0D)
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13 (UNIT_QNCPU) UNIT_QNMOTIONUSB (0x1D)

4.5.6 USB communication when the connected station is Q motion CPU

4.5 USB Communication

179
4.5.7 USB communication when the connected station is FXCPU

(1) Configuration

Connected Relayed
station CPU module

Personal computer Relayed network

Relayed Relayed
station CPU module

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FXCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      
CC-Link      *1
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

180
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to the target station
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Fixed to 1023 (0x3FF)
Module number of the
ActIONumber 1023 (0x3FF) Fixed to 0 (0x00)
connected station
4
0x04
ActProtocolType PROTOCOL_USB (0x0D)
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units
Target station side module
ActUnitNumber 0 (0x00) Fixed to 0 (0x00)
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXCPU (0x0F)

4.5.7 USB communication when the connected station is FXCPU

4.5 USB Communication

181
4.5.8 USB communication when the connected station is inverter

(1) Configuration

Inverter

Personal computer

(2) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

ActMxUnitSeries 0 (0x00) 1 (0x01)
0x04
ActProtocolType COMM_USB (0x01)
(PROTOCOL_SERIAL)
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.

182
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.5.9 USB communication when the connected station is robot

controller

(1) Configuration

Robot controller

Personal computer

(2) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

0x04
ActProtocolType RC_PROTOCOL_USB(0x04)
(PROTOCOL_SERIAL)
34
ActCpuType Robot controller type(0x013001)
(CPU_Q02CPU)
ActTimeOut 10000 Any value specified by user in ms units.
ActCpuTimeOut 0(0x00) Any value specified by user in 10ms units.
ActMultiDropChanne

4.5.9 USB communication when the connected station is robot controller

4.5 USB Communication
0(0x00) Retry count
lNumber
ActMxUnitSeries 0(0x00) 2(0x02)

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

183
4.6 MELSECNET/H Communication

(1) Configuration
Connected MELSECNET/H Relayed
station CPU module module

Relayed network

Relayed Relayed
station CPU module

Personal computer

(2) Property patterns

Connected station CPU Relayed station CPU
Own
QCPU Q motion Relayed network R motion
board QSCPU RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
  *1 *1,*5
Ethernet    
Serial communication    
CC-Link    

Connected station CPU Relayed station CPU

Own Q
QCPU Q motion Relayed network QCPU QS FX
board QSCPU QCCPU LCPU motion
(Q mode) CPU (Q mode) CPU CPU
CPU
CC IE Control
 *2 *3 *1,*2  
CC IE Field
MELSECNET/H    *1  
  *1 *1,*5
Ethernet    *1  

Serial communication *4     

CC-Link      

184
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected station CPU Relayed station CPU

Own
Relayed network R motion
board QCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 *6
Ethernet    
Serial communication    
CC-Link    

Connected station CPU Relayed station CPU 4

Own Q
Relayed network QCPU QS FX
board QCCPU QCCPU LCPU motion
(Q mode) CPU CPU
CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 *6
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations cannot be accessed via QCPU and 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

4.6 MELSECNET/H Communication

not supported.

185
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
Connected CPU: Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
ActDestination No.1: 992 (0x3E0) No.1: 992 (0x3E0)
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
IONumber 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: Control system:
976 (0x3D0) 976 (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)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
Connected station side Connected station side
No.1: 992 (0x3E0)
ActIONumber*1 1023 (0x3FF) Fixed to 0 (0x00) relayed module I/O relayed module I/O
No.2: 993 (0x3E1)
address address
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
For Redundant CPU
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side Connected station side Connected station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) module network module network module network
number number number
Port number of personal computer side MELSECNET/H board,
ActPortNumber 1 (PORT_1)
PORT 1 to PORT 4 (first to fourth boards)
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_MNETH (0x0F)
SERIAL)
Fixed to 255 Target station side Connected station side Connected station side
ActStationNumber 255 (0xFF)
(0xFF) module station number module station number module station number

186
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_MNETHBOARD (0x1E)
(UNIT_QNCPU)
*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

4.6 MELSECNET/H Communication

187
4.7 CC-Link IE Controller Network Communication

(1) Configuration
Connected CC-Link IE Controller Relayed
station CPU Network module module

Relayed network

Relayed Relayed
station CPU module

Personal computer

(2) Property patterns

Connected station CPU Relayed station CPU
Own
QCPU Q motion Relayed network R motion
board QSCPU RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
  *1 *1,*5
Ethernet    
Serial communication    
CC-Link    

Connected station CPU Relayed station CPU

Own Q
QCPU Q motion Relayed network QCPU QS FX
board QSCPU QCCPU LCPU motion
(Q mode) CPU (Q mode) CPU CPU
CPU
CC IE Control
 *2 *3 *1,*2  
CC IE Field
MELSECNET/H    *1  
  *1 *1,*5
Ethernet    *1  

Serial communication *4     

CC-Link      

188
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected station CPU Relayed station CPU

Own
Relayed network R motion
board QCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 *6
Ethernet    
Serial communication    
CC-Link    

Connected station CPU Relayed station CPU 4

Own Q
Relayed network QCPU QS FX
board QCCPU QCCPU LCPU motion
(Q mode) CPU CPU
CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 *6
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed station CPU

Own
Relayed network R motion
board RCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

4.7 CC-Link IE Controller Network Communication

 
Ethernet    
Serial communication *4   
CC-Link    

Connected station CPU Relayed station CPU

Own Q
Relayed network QCPU QS FX
board RCPU QCCPU LCPU motion
(Q mode) CPU CPU
CPU*5
CC IE Control
     
CC IE Field
MELSECNET/H      
 
Ethernet      
Serial communication *4  *4   
 
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations cannot be accessed via QCPU and 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.

189
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU:
IONumber
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 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)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) Fixed to 0 (0x00) Connected CPU: relayed module I/O relayed module I/O
1023 (0x3FF) address address
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
ActMultiDrop Multi-drop channel
*2
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber number
Target station side Connected station side Connected station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) module network module network module network
number number number
Port number of personal computer side CC-Link IE Controller Network board,
ActPortNumber 1 (PORT_1)
PORT 1 to PORT 4 (first to fourth boards)
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_MNETG (0x14)
SERIAL)
Fixed to 255 Target station side Connected station side Connected station side
ActStationNumber 255 (0xFF)
(0xFF) module station number module station number module station number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_MNETGBOARD (0x2B)
(UNIT_QNCPU)

*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

190
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.8 CC-Link IE Field Network Communication

(1) Configuration

Connected CC-Link IE Field Relayed

station CPU Network module module

Relayed network

Relayed Relayed
station CPU module
4
Personal computer

(2) Property patterns

Connected
Relayed station CPU
Own station CPU
Relayed network
board QCPU R motion
RCPU RCCPU FX5CPU
(Q mode) CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 
Ethernet    
Serial communication    
CC-Link    

Connected

4.8 CC-Link IE Field Network Communication

Relayed station CPU
Own station CPU
Relayed network
board QCPU QCPU Q motion
QCCPU LCPU QSCPU FXCPU
(Q mode) (Q mode) CPU
CC IE Control
 *1 *2   
CC IE Field
MELSECNET/H      
 
Ethernet      
Serial communication      
CC-Link      

191
 Connected
Relayed station CPU
Own station CPU
Relayed network
board R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field *2    
MELSECNET/H    
  Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
Own station CPU
Relayed network
board QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Field *2      
MELSECNET/H      
  Ethernet      
Serial communication      
CC-Link      

Connected
Relayed station CPU
Own station CPU
Relayed network
board R motion
RCPU RCPU RCCPU FX5CPU
CPU
CC IE Field    
MELSECNET/H    
  Ethernet    
Serial communication *3   

CC-Link    

Connected
Relayed station CPU
Own station CPU
Relayed network
board QCPU Q motion
RCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Field      
MELSECNET/H      
  Ethernet      
Serial communication *3  *3   
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

192
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to 4
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU:
IONumber
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)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs Connected station side Connected station side
Fixed to 1023
ActIONumber*1 1023 (0x3FF) Connected CPU: relayed module I/O relayed module I/O
(0x3FF)
1023 (0x3FF) address address
No.1: 992 (0x3E0)

4.8 CC-Link IE Field Network Communication

No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
ActMultiDrop Multi-drop channel
*2
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber number
Target station side Connected station side Connected station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) module network module network module network
number number number
Port number of personal computer side CC-Link IE Field Network board,
ActPortNumber 1 (PORT_1)
PORT 1 to PORT 4 (first to fourth boards)
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_CCIEF (0x15)
SERIAL)
Fixed to 255 Target station side Connected station side Connected station side
ActStationNumber 255 (0xFF)
(0xFF) module station number module station number module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_CCIEFBOARD (0x2F)
(UNIT_QNCPU)

*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

193
4.9 CC-Link Communication

(1) Configuration

Connected CC-Link Relayed

station CPU module module

Relayed network

Relayed Relayed
station CPU module

Personal computer

(2) Property patterns

Connected station CPU Relayed station CPU
Own
QCPU Q motion Relayed network R motion
board RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
  *1,*4
Ethernet    
Serial communication    
CC-Link    

Connected station CPU Relayed station CPU

Own
QCPU Q motion Relayed network QCPU QS Q motion FX
board QCCPU LCPU
(Q mode) CPU (Q mode) CPU CPU CPU
CC IE Control
 *2 *3 *2 *2 
CC IE Field
MELSECNET/H      
  *1,*4
Ethernet      
Serial communication      
CC-Link      

194
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected station CPU Relayed station CPU

Own
Relayed network R motion
board QCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 *5
Ethernet    
Serial communication    
CC-Link    

Own
Connected station CPU Relayed station CPU
4
Relayed network QCPU QS Q motion FX
board QCCPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Control
 *2  *2 *2 
CC IE Field
MELSECNET/H      
 *5
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed station CPU

Own
Relayed network R motion
board LCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 
Ethernet    

4.9 CC-Link Communication

Serial communication    
CC-Link    

Connected station CPU Relayed station CPU

Own
Relayed network QCPU QS Q motion FX
board LCPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 
Ethernet      
Serial communication      
CC-Link      

195
 Connected station CPU Relayed station CPU
Own
Relayed network R motion
board RCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 
Ethernet    
Serial communication    
CC-Link    

Connected station CPU Relayed station CPU

Own
Relayed network QCPU QS Q motion FX
board RCPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Control
  *3   
CC IE Field
MELSECNET/H      
 
Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations cannot be accessed via Q motion CPU.

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

196
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
  
ActCpuType 34(CPU_Q02CPU) CPU type corresponding to the target station
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF) 4
For multiple CPUs For multiple CPUs
Fixed to 0
ActDestinationIONumber 0 (0x00) Connected CPU: Connected CPU:
(0x00)
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)
Fixed to 0
ActIONumber 1023 (0x3FF) Fixed to 1023 (0x3FF) Fixed to 1023 (0x3FF)
(0x00)
Target station side
Fixed to 0
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) module network
(0x00)
number
Port number of personal computer side CC-Link Ver.2 board,
ActPortNumber 1 (PORT_1)
PORT 1 to PORT 4 (first to fourth boards)
0x04
ActProtocolType PROTOCOL_CCLINK (0x07)
(PROTOCOL_SERIAL)
Target station side

4.9 CC-Link Communication

Fixed to 255 Target station side
ActStationNumber 255 (0xFF) CC-Link module
(0xFF) module station number
station number
Connected station side
Fixed to 0
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) CC-Link module
(0x00)
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_CCLINKBOARD (0x0C)

197
4.10 CC-Link G4 communication

(1) Configuration

Connected CC-Link Relayed

station CPU module module

Relayed network

CC-Link G4
module Relayed Relayed
(Q mode) station CPU module
Personal computer

(2) Property patterns

Connected station CPU Relayed station CPU
QCPU Q motion Relayed network R motion
RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 *1,*5
Ethernet    
Serial communication    
CC-Link    

Connected station CPU Relayed station CPU

QCPU Q motion Relayed network QCPU Q motion FX
QCCPU LCPU QSCPU
(Q mode) CPU (Q mode) CPU CPU
CC IE Control
 *2 *3 *2 *2 
CC IE Field
MELSECNET/H      
 *1,*5
Ethernet      
Serial communication      
CC-Link      

198
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected station CPU Relayed station CPU

Relayed network R motion
QCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*4
Ethernet    
Serial communication    
CC-Link    

Connected station CPU Relayed station CPU 4

Relayed network QCPU Q motion FX
QCCPU QCCPU LCPU QSCPU
(Q mode) CPU CPU
CC IE Control
 *2 *3 *2 *2 
CC IE Field
MELSECNET/H      
*4
Ethernet      
Serial communication      
CC-Link      

Connected station CPU Relayed station CPU

Relayed network R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    

Ethernet    

4.10 CC-Link G4 communication

Serial communication    
CC-Link    

Connected station CPU Relayed station CPU

Relayed network QCPU Q motion FX
LCPU QCCPU LCPU QSCPU
(Q mode) CPU CPU
CC IE Control
     
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication      
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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 : 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.

199
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
  
19200 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
ActBaudRate
(BAUDRATE_19200) BAUDRATE_57600, BAUDRATE_115200
ActConnectUnitNumber 0 (0x00) Connected station side module station number
8
ActControl Depending on the used cable.
(TRC_DTR_OR_RTS)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to the target station
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 (0x3FF) 1023 (0x3FF)
Connected
No. 1: 992 (0x3E0) No. 1: 992 (0x3E0)
station side
ActIONumber*1 1023 (0x3FF) No. 2: 993 (0x3E1) No. 2: 993 (0x3E1)
relayed module
No. 3: 994 (0x3E2) No. 3: 994 (0x3E2)
I/O address
No. 4: 995 (0x3E3) No. 4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)
Target station side
Fixed to 0
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) module network
(0x00)
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIAL)
Target station side Fixed to 255
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)
module station number (0xFF)
MELSECNET/10 is not included. : 0 (0x00)
ActThroughNetworkType 0 (0x00)
MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) 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.

200
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.11 GX Simulator Communication

(1) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
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 4
network number
0x04
ActProtocolType PROTOCOL_SHAREDMEMORY(0x06)
(PROTOCOL_SERIAL)
Target station side
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)
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 0 to 64 is set.

4.12 GX Simulator2 Communication

4.11 GX Simulator Communication

(1) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property Default value Property pattern
ActTargetSimulator 0 (0x00) Refer to the property [ActTargetSimulator] in Section 3.2
ActUnitType 0x13 (UNIT_QNCPU) UNIT_SIMULATOR2 (0x30)

201
4.13 GX Simulator3 Communication

(1) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property Default value Property pattern
19200
ActBaudRate 0 (0x00)
(BAUDRATE_19200)
8
ActControl 0 (0x00)
(TRC_DTR_OR_RTS)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
ActDataBits 8 (DATABIT_8) 0 (0x00)
RCPU:5511
ActDestinationPortNumber The target port number*1
FX5CPU:5573
ActDidPropertyBit 1 (0x01) 0 (0x00)
ActDsidPropertyBit 1 (0x01) 0 (0x00)
ActHostAddress 1.1.1.1 Loopback address(127.0.0.1)
ActPacketType 0x01 (PACKET_PLC1) PACKET_PLC1
ActParity 1 (ODD_PARITY) 0 (0x00)
ActPassword Null 0 (0x00)
ActPortNumber 1 (PORT_1) 0 (0x00)
0x04
ActProtocolType PROTOCOL_TCPIP (0x05)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) 0 (0x00)
ActStopBits 0 (STOPBIT_ONE) 0 (0x00)
ActSumCheck 0 (NO_SUM_CHECK) 0 (0x00)
ActThroughNetworkType 0 (0x00) 0 (0x00)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13 (UNIT_QNCPU) UNIT_SIMULATOR3 (0x31)

*1 :
The target port number is calculated with the following calculation formula.
RCPU: PortNumber=5500+ System No. ×10+ Unit No.
FX5CPU: PortNumber=5562+ System No. ×10+ Unit No.
For System No.=1, Unit No.=1
5511=5500+1×10+1
Refer to the following manual for system No. and unit No. to calculate the target port number.
GX Works3 Operating Manual

4.14 MT Simulator2 Communication

(1) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property Default value Property pattern
ActTargetSimulator 0 (0x00) Refer to the property [ActTargetSimulator] in Section 3.2
CPU type corresponding to the target station
ActCpuType CPU_Q02CPU
(Q motion CPU)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_SIMULATOR2 (0x30)

202
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.15 Modem Communication

4.15.1 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

(a) Configuration 4
Connected Q series-compatible Relayed
station CPU C24 module

Modem Relayed network

Subscriber's line
Relayed Relayed
Modem station CPU module
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
QCPU R motion
RCPU RCCPU FX5CPU
(Q mode) CPU
CC IE Control
   
CC IE Field

4.15.1 Modem communication when the connected module is Q series-compatible C24

4.15 Modem Communication
MELSECNET/H    

Ethernet    
Serial communication    
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QCPU Q motion
QCCPU LCPU QSCPU FXCPU
(Q mode) (Q mode) CPU
CC IE Control
 *1 *2 *1  
CC IE Field
MELSECNET/H      

Ethernet      
Serial communication *3     
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

203
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
ActATCommand Null Any value specified by user
ActATCommand
PasswordCancel 3 Any value specified by user
RetryTimes
ActATCommand
ResponseWait 1 Any value specified by user (in seconds)
Time
19200 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_ BAUDRATE_115200
19200) (Match to the setting of Q series-compatible C24.)
ActCallback
90 Any value specified by user (in seconds)
CancelWaitTime
ActCallback
20 Any value specified by user (in seconds)
DelayTime
ActCallback
Null Telephone number of any value specified by user
Number
ActCallback
ReceptionWaiting 120 Any value specified by user (in seconds)
TimeOut
ActConnection
90 Any value specified by user (in seconds)
CDWaitTime
ActConnection
ModemReport 5 Any value specified by user (in seconds)
WaitTime
ActConnectUnit
0 (0x00) Connected station side module station number
Number
TEL_AUTO_CONNECT(0), TEL_AUTO_CALLBACK(1), TEL_AUTO_CALLBACK_NUMBER(2),
0 (TEL_AUTO_ TEL_CALLBACK(3), TEL_CALLBACK_NUMBER(4), TEL_CALLBACK_REQUEST(5),
ActConnectWay
CONNECT) TEL_CALLBACK_REQUEST_NUMBER(6), TEL_CALLBACK_WAIT(7)
(Depending on callback function setting)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
Connected CPU: Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
ActDestination No.1: 992 (0x3E0) No.1: 992 (0x3E0)
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
IONumber 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: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)

204
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
ActDialNumber Null Telephone number of any value specified by user
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDisconnection
5 Any value specified by user (in seconds)
CDWaitTime
ActDisconnection
3 Any value specified by user (in seconds)
DelayTime
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActIntelligent
4
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
Connected CPU: Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
Connected station side Connected station side
No.1: 992 (0x3E0) No.1: 992 (0x3E0)
ActIONumber*1 1023 (0x3FF) relayed module I/O relayed module I/O
No.2: 993 (0x3E1) No.2: 993 (0x3E1)
address address
No.3: 994 (0x3E2) No.3: 994 (0x3E2)
No.4: 995 (0x3E3) No.4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Control system:
976 (0x3D0) 976 (0x3D0)
No specification: No specification:
1023 (0x3FF) 1023 (0x3FF)

4.15.1 Modem communication when the connected module is Q series-compatible C24

4.15 Modem Communication
1 (LINETYPE_
ActLineType LINETYPE_PULSE(0), LINETYPE_TONE(1), LINETYPE_ISDN(2)
TONE)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
ActOutsideLineN
Null Outside line access number of any value specified by user
umber
ActPassword Null Password set to Q series-compatible C24
ActPassword
CancelResponse 5 Any value specified by user (in seconds)
WaitTime
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIALMODEM (0x0E)
SERIAL)
ActStation Target station side
255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
ActTransmission
0 Any value specified by user (in seconds)
DelayTime

205
 Property pattern
Property Default value
   
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_QJ71C24 (0x19)
(UNIT_QNCPU)
*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

206
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(2) When performing multi-drop link on the connected station side Q series-
compatible C24 with the relayed module

(a) Configuration

Connected Q series-
station CPU compatible C24

Modem Multi-drop link

Subscriber's line
Modem
Relayed Relayed
station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
QCPU R motion
RCPU RCCPU FX5CPU
(Q mode) CPU
Independent Serial
*1
    
mode communication

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QCPU Q motion
QCCPU LCPU QSCPU FXCPU
(Q mode) (Q mode) CPU
Independent Serial
 *2     
mode *1 communication

4.15.1 Modem communication when the connected module is Q series-compatible C24

4.15 Modem Communication
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

207
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
ActATCommand Null Any value specified by user
ActATCommandPasswordCancelRetryTi
3 Any value specified by user
mes
ActATCommandResponseWaitTime 1 Any value specified by user (in seconds)
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
19200
ActBaudRate BAUDRATE_57600, BAUDRATE_115200
(BAUDRATE_19200)
(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 Any value specified by user (in seconds)
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
TEL_AUTO_CONNECT(0), TEL_AUTO_CALLBACK(1),
TEL_AUTO_CALLBACK_NUMBER(2), TEL_CALLBACK(3),
0 TEL_CALLBACK_NUMBER(4), TEL_CALLBACK_REQUEST(5),
ActConnectWay
(TEL_AUTO_CONNECT) TEL_CALLBACK_REQUEST_NUMBER(6),
TEL_CALLBACK_WAIT(7)
(Depending on callback function setting)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) 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 1 (0x01)
ActIntelligentPreferenceBit 0 (0x00) Fixed to 0 (0x00)

208
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
 
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
Connected station side relayed
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1)
module I/O address
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
For Redundant CPU
4
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
LINETYPE_PULSE(0), LINETYPE_TONE(1),
ActLineType 1 (LINETYPE_TONE)
LINETYPE_ISDN(2)
*2 0 (0x00) Fixed to 0 (0x00) Multi-drop channel number
ActMultiDropChannelNumber
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
0x04
ActProtocolType PROTOCOL_SERIALMODEM (0x0E)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)

4.15.1 Modem communication when the connected module is Q series-compatible C24

4.15 Modem Communication
MELSECNET/10 is not included. : 0 (0x00)
ActThroughNetworkType 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)
Target station side module
ActUnitNumber 0 (0x00) 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

209
4.15.2 Modem communication when the connected module is L series-
compatible C24

(1) When a relayed module other than the connected station side LJ71C24 exists

(a) Configuration

Connected L series-compatible Relayed

station CPU C24 module

Modem Relayed network

Subscriber's line
Relayed Relayed
Modem station CPU module
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field *2    
MELSECNET/H    
Ethernet    
*1
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Field *2  *3    
MELSECNET/H      
Ethernet      
*1
Serial
*4     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*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, computer link modules on the main base cannot be accessed.

210
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
ActATCommand Null Any value specified by user
ActATCommand
PasswordCancel 3 Any value specified by user
RetryTimes
ActATCommand
ResponseWaitTime
1 Any value specified by user (in seconds) 4
19200 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_ BAUDRATE_115200
19200) (Match to the setting of LJ71C24)
ActCallback
90 Any value specified by user (in seconds)
CancelWaitTime
ActCallback
20 Any value specified by user (in seconds)
DelayTime
ActCallbackNumber Null Telephone number of any value specified by user
ActCallback
ReceptionWaiting 120 Any value specified by user (in seconds)
TimeOut
ActConnection
90 Any value specified by user (in seconds)
CDWaitTime
ActConnection
ModemReportWait 5 Any value specified by user (in seconds)
Time
ActConnectUnit

4.15.2 Modem communication when the connected module is L series-compatible C24

4.15 Modem Communication
0 (0x00) Connected station side module station number
Number
TEL_AUTO_CONNECT(0), TEL_AUTO_CALLBACK(1),
0 (TEL_AUTO_ TEL_AUTO_CALLBACK_NUMBER(2), TEL_CALLBACK(3), TEL_CALLBACK_NUMBER(4),
ActConnectWay
CONNECT) TEL_CALLBACK_REQUEST(5), TEL_CALLBACK_REQUEST_NUMBER(6),
TEL_CALLBACK_WAIT(7)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
Connected CPU: Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
ActDestination No.1: 992 (0x3E0) No.1: 992 (0x3E0)
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
IONumber 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: Control system:
976 (0x3D0) 976 (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)
ActDisconnection
5 Any value specified by user (in seconds)
CDWaitTime

211
 Property pattern
Property Default value
   
ActDisconnection
3 Any value specified by user (in seconds)
DelayTime
ActDsidPropertyBit 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
Connected station side Connected station side
Fixed to No.1: 992 (0x3E0)
ActIONumber*1 1023 (0x3FF) relayed module I/O relayed module I/O
1023 (0x3FF) No.2: 993 (0x3E1)
address address
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
For Redundant CPU
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
1 (LINETYPE_
ActLineType LINETYPE_PULSE(0), LINETYPE_TONE(1), LINETYPE_ISDN(2)
TONE)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
ActOutsideLine
Null Outside line access number of any value specified by user
Number
ActPassword Null Password set to the module
ActPasswordCancel
5 Any value specified by user (in seconds)
ResponseWaitTime
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIALMODEM (0x0E)
SERIAL)
Fixed to 255 Module station number
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) on target station side
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
ActTransmission
0 Any value specified by user (in seconds)
DelayTime
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LJ71C24 (0x54)
(UNIT_QNCPU)
*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

212
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(2) When performing multi-drop link on the connected station side LJ71C24 with
the relayed module

(a) Configuration

Connected L series-
station CPU compatible C24

Modem Multi-drop link

Subscriber's line
Modem
Relayed Relayed
station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
Independent Serial
    
mode communication

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
Independent Serial
 *1     
mode communication
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

4.15.2 Modem communication when the connected module is L series-compatible C24

4.15 Modem Communication
*1 : For Redundant CPU, computer link modules on the main base cannot be accessed.

213
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
ActATCommand Null Any value specified by user
ActATCommandPasswordCancelRetry
3 Any value specified by user
Times
ActATCommandResponseWaitTime 1 Any value specified by user (in seconds)
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
19200(BAUDRATE_
ActBaudRate BAUDRATE_57600, BAUDRATE_115200
19200)
(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 Any value specified by user (in seconds)
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
TEL_AUTO_CONNECT(0), TEL_AUTO_CALLBACK(1),
0 TEL_AUTO_CALLBACK_NUMBER(2), TEL_CALLBACK(3),
ActConnectWay (TEL_AUTO_ TEL_CALLBACK_NUMBER(4), TEL_CALLBACK_REQUEST(5),
CONNECT) TEL_CALLBACK_REQUEST_NUMBER(6),
TEL_CALLBACK_WAIT(7)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) 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)
Connected station side relayed
ActIONumber*1 1023 (0x3FF) Fixed to 1023 (0x3FF)
module I/O address
LINETYPE_PULSE(0), LINETYPE_TONE(1),
ActLineType 1 (LINETYPE_TONE)
LINETYPE_ISDN(2)

ActMultiDropChannelNumber*2 0 (0x00) Fixed to 0 (0x00) Multi-drop channel number

214
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
 
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
0x04
ActProtocolType PROTOCOL_SERIALMODEM(0x0E)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)

ActThroughNetworkType 0 (0x00)
MELSECNET/10 is not included. : 0 (0x00) 4
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)
Target station side module
ActUnitNumber 0 (0x00) 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.15.2 Modem communication when the connected module is L series-compatible C24

4.15 Modem Communication

215
4.15.3 Modem communication when the connected station is FXCPU

(1) Configuration

Connected Relayed
station CPU module

Modem Relayed network

Subscriber's line
Relayed Relayed
Modem station CPU module
Personal computer

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FXCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

216
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

ActATCommand Null Any value specified by user
ActATCommandPasswordCancelRetry
3 Any value specified by user
Times
ActATCommandResponseWaitTime 1 Any value specified by user (in seconds)
4
ActCallbackCancelWaitTime 90 Any value specified by user (in seconds)
ActCallbackDelayTime 20 Any value specified by user (in seconds)
ActCallbackNumber Null Any value specified by user (in seconds)
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 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)
LINETYPE_PULSE(0), LINETYPE_TONE(1),
ActLineType 1 (LINETYPE_TONE)
LINETYPE_ISDN(2)
Outside line access number of any value specified
ActOutsideLineNumber Null
by user
ActPasswordCancelResponseWaitTime 5 Any value specified by user (in seconds)
ActPortNumber 1 (PORT_1) Personal computer side COM port number

4.15.3 Modem communication when the connected station is FXCPU

4.15 Modem Communication
0x04
ActProtocolType PROTOCOL_TEL (0x0A)
(PROTOCOL_SERIAL)
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)

217
4.16 Gateway Function Communication

(1) Configuration

GOT

Personal computer

(2) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

ActHostAddress 1.1.1.1 Host name or IP address of connected GOT
ActPortNumber 1 (PORT_1) Personal computer side port number
0x04
ActProtocolType PROTOCOL_UDPIP (0x08)
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units
ActUnitType 0x13 (UNIT_QNCPU) UNIT_A900GOT (0x21)

218
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.17 GOT Transparent Function 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 Products,Peripherals)
• Connection manuals for GOT1000 series
(Mitsubishi Products), (Non-Mitsubishi Products 1), (Non-Mitsubishi Products 2),
(Microcomputer, MODBUS Products,Peripherals)
4

4.17 GOT Transparent Function Communication

219
4.17.1 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Direct connection

(1) When the connected station is FX5CPU

(a) Configuration

Connected Relayed
GOT
Serial station CPU module
Serial
Relayed network

Relayed Relayed
station CPU module
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FX5CPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   *1
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FX5CPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Only CC-Link IE Field Network of which relayed station is FX5UCPU can be accessed.

220
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
ActBaudRate
(BAUDRATE_19200) BAUDRATE_57600, BAUDRATE_115200
ActConnectUnitNumber 0 (0x00) 0 (0x00)
ActControl 8 (TRC_DTR_OR_RTS) 8 (TRC_DTR_OR_RTS) Depending on the used cable.
ActCpuTimeOut 0 (0x00) 0 (0x00) 4
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
ActDataBits 8 (DATABIT_8) 8 (0x08)
ActDestinationIONumber 0 (0x00) 0 (0x00)
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)
ActIONumber 1023 (0x3FF) 1023 (0x3FF)
ActMultiDropChannelNumber 0 (0x00) 0 (0x00)
Target station side module
ActNetworkNumber 0 (0x00) 0 (0x00)
network number
ActPacketType 0x01 (PACKET_PLC1) PACKET_PLC1 (0x01)
ActParity 1(ODD_PARITY) 1 (ODD_PARITY)
ActPassword Null NULL

4.17.1 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Direct
4.17 GOT Transparent Function Communication
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04

connection
ActProtocolType PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIAL)
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)
Target station side module
ActStationNumber 255 (0xFF) 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)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOT_FXVCPU (0x2005)

221
 (2) When the connected station is QCPU (Q mode)

(a) Configuration

Connected Relayed
GOT
Serial station CPU module
Serial
Relayed network

Relayed Relayed
station CPU module
Personal computer

(b) Property patterns

Connected station CPU Relayed station CPU
QCPU Q motion Relayed network R motion
QCCPU RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 *2 *5 Ethernet    
  
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

QCPU Q motion Relayed network QCPU QS Q motion FX
QCCPU QCCPU LCPU
(Q mode) CPU (Q mode)*1 CPU CPU CPU
CC IE Control
 *3 *4  *3 
CC IE Field
MELSECNET/H      
*1 *2 *5 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Redundant CPU cannot be accessed.

*2 : Relayed stations 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.

222
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
4
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)

4.17.1 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Direct
4.17 GOT Transparent Function Communication
Bit
ActDsidProperty

connection
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For single CPU
For multiple CPUs
Fixed to
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No.1: 992 (0x3E0) Connected station Connected station
Connected CPU:
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1) side module I/O side module I/O
1023 (0x3FF)
No.3: 994 (0x3E2) address address
No.1: 992 (0x3E0)
No.4: 995 (0x3E3)
No.2: 993 (0x3E1)
For Redundant CPU
No.3: 994 (0x3E2)
Target station side
No.4: 995 (0x3E3)
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)

223
 Property pattern
Property Default value
   
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)
Target station side
ActStation
255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number
number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_QNCPU (0x13)
(UNIT_QNCPU)
*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

224
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) When the connected station is LCPU

(a) Configuration

Connected Relayed
GOT
Serial station CPU module
Serial
Relayed network

Relayed Relayed
station CPU module
Personal computer 4
(b) Property patterns
Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field *2    
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU

4.17.1 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Direct
4.17 GOT Transparent Function Communication
*1 CPU
(Q mode)

connection
CC IE Field *2  *3    
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

225
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
8 (TRC_DTR
ActControl 8 (TRC_DTR_OR_RTS)
_OR_RTS)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1) Fixed to 0 (0x00)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) 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
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
Fixed to 1023 Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1)
(0x3FF) module I/O address module I/O address
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
For Redundant CPU
Target station side
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)

226
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)
Fixed to 255 Target station side
4
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LNCPU (0x50)
(UNIT_QNCPU)
*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.17.1 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Direct
4.17 GOT Transparent Function Communication
connection

227
 (4) When the connected station is FXCPU

(a) Configuration

Connected Relayed
GOT
Serial station CPU module
Serial
Relayed network

Relayed Relayed
station CPU module
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FXCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      *1
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

228
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
ActBaudRate
(BAUDRATE_19200) BAUDRATE_57600, BAUDRATE_115200
ActControl 8 (TRC_DTR_OR_RTS) 8 (TRC_DTR_OR_RTS)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Fixed to 1023 (0x3FF) 4
ActDidPropertyBit 1 (0x01) Fixed to 0 (0x00) Fixed to 1 (0x01)
ActDsidPropertyBit 1 (0x01) Fixed to 0 (0x00) Fixed to 1 (0x01)
1023 Module number of the
ActIONumber Fixed to 0 (0x00)
(0x3FF) connected station
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units
Target station side module
ActUnitNumber 0 (0x00) Fixed to 0 (0x00)
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXCPU (0x0F)

4.17.1 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Direct
4.17 GOT Transparent Function Communication
connection

229
4.17.2 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Direct connection

(1) When the connected station is FX5CPU

(a) Configuration

Connected Relayed
GOT
Serial station CPU module
USB
Relayed network

Relayed Relayed
station CPU module
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   *1
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FXCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Only CC-Link IE Field Network of which relayed station is FX5UCPU can be accessed.

230
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200
ActBaudRate 0 (0x00)
(BAUDRATE_19200)
ActConnectUnitNumber 0 (0x00) 0 (0x00)
8
ActControl 0 (0x00)
(TRC_DTR_OR_RTS) 4
ActCpuTimeOut 0(0x00) 0 (0x00)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
ActDataBits 8(DATABIT_8) 0 (0x00)
ActDestinationIONumber 0 (0x00) 0 (0x00)
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)
ActIONumber 1023 (0x3FF) 1023 (0x3FF)
ActMultiDropChannelNumber 0 (0x00) 0 (0x00)
Target station side module
ActNetworkNumber 0 (0x00) 0 (0x00)
network number
ActPacketType 0x01(PACKET_PLC1) PACKET_PLC1(0x01)
ActParity 1 (ODD_PARITY) 0 (0x00)

4.17.2 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Direct
4.17 GOT Transparent Function Communication
ActPassword Null NULL
ActPortNumber 1 (PORT_1) Personal computer side COM port number

connection
0x04
ActProtocolType PROTOCOL_USBGOT (0x13)
(PROTOCOL_SERIAL)
ActStopBits 0 (STOPBIT_ONE) 0 (0x00)
ActSumCheck 0 (NO_SUM_CHECK) 0 (0x00)
ActSourceNetworkNumber 0 (0x00) 0 (0x00)
ActSourceStationNumber 0 (0x00) 0 (0x00)
Target station side module
ActStationNumber 255 (0xFF) 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)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOT_FXVCPU (0x2005)

231
 (2) When the connected station is QCPU (Q mode)

(a) Configuration

Connected Relayed
GOT
Serial station CPU module
USB
Relayed network

Relayed Relayed
station CPU module
Personal computer

(b) Property patterns

Connected station CPU Relayed station CPU
Relayed
QCPU Q motion R motion
QCCPU network RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 *2 *5 Ethernet    
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

Relayed
QCPU Q motion QCPU QS Q motion FX
QCCPU network QCCPU LCPU
(Q mode) CPU (Q mode)*1 CPU CPU CPU
CC IE Control
 *3 *4  *3 
CC IE Field
MELSECNET/H      
*1 *2 *5 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Redundant CPU cannot be accessed.

*2 : Relayed stations 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.

232
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
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
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU:
IONumber
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)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)

4.17.2 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Direct
4.17 GOT Transparent Function Communication
Target station side Target station side
For single CPU For single CPU

connection
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs Connected station Connected station
*1 1023 (0x3FF) Connected CPU: Connected CPU: side module I/O side module I/O
ActIONumber
1023 (0x3FF) 1023 (0x3FF) address address
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)
ActMultiDrop Multi-drop channel
*2
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module station Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT (0x13)
SERIAL)
Target station side
ActStation
255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number
number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units

233
 Property pattern
Property Default value
   
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_QNCPU (0x13)
(UNIT_QNCPU)
*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

234
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) When the connected station is LCPU

(a) Configuration

Connected Relayed
GOT
Serial station CPU module
USB
Relayed network

Relayed Relayed
station CPU module
Personal computer 4
(b) Property patterns
Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field *2    
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
LCPU QCCPU LCPU QSCPU FXCPU

4.17.2 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Direct
4.17 GOT Transparent Function Communication
*1 CPU
(Q mode)

connection
CC IE Field *2  *3    
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

235
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
ActBaudRate (BAUDRATE_19 Fixed to 0 (0x00)
200)
8
ActControl (TRC_DTR_OR_ Fixed to 0(0x00)
RTS)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
ActDataBits 8 (DATABIT_8) Fixed to 0 (0x00)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1) Fixed to 0 (0x00)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) 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
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)

236
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
Fixed to 1023 Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1)
(0x3FF) module I/O address module I/O address
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
4
For Redundant CPU
Target station side
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
1
ActParity Fixed to 0 (0x00)
(ODD_PARITY)
ActPortNumber 1 (PORT_1) Fixed to 0 (0x00)
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT (0x13)

4.17.2 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Direct
4.17 GOT Transparent Function Communication
SERIAL)
Fixed to 255 Target station side

connection
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number
ActTimeOut 10000 Any value specified by user in ms units
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LNCPU (0x50)
(UNIT_QNCPU)
*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

237
 (4) When the connected station is FXCPU

(a) Configuration

Connected Relayed
GOT
Serial station CPU module
USB
Relayed network

Relayed Relayed
station CPU module
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU Q motion
FXCPU QCCPU LCPU QSCPU FXCPU
(Q mode) CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      *1
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

238
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to 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
0 (0x00)
Module number of the 4
(0x3FF) connected station
0x04
ActProtocolType PROTOCOL_USBGOT (0x13)
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units
Target station side module
ActUnitNumber 0 (0x00) 0 (0x00)
station number
ActUnitType 0x13 (UNIT_QNCPU) UNIT_FXCPU (0x0F)

4.17.2 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Direct
4.17 GOT Transparent Function Communication
connection

239
4.17.3 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Bus connection

(1) Configuration

Connected Relayed
GOT Bus
station CPU module
Serial
Relayed network

Relayed Relayed
station CPU module
Personal computer

(2) Property patterns

Connected station CPU Relayed station CPU
QCPU Q motion Relayed network R motion
RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 *2,*5 Ethernet    
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

QCPU Q motion Relayed network QCPU QS Q motion FX
QCCPU LCPU
(Q mode) CPU (Q mode)*1 CPU CPU CPU
CC IE Control
 *3 *4  *3 
CC IE Field
MELSECNET/H      
*1 *2,*5 Ethernet      
 
Serial
     
communication
CC-Link      

240
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected station CPU Relayed station CPU

Relayed network R motion
QCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*6 Ethernet    

Serial
   
communication
CC-Link    
4
Connected station CPU Relayed station CPU
Relayed network QCPU QS Q motion FX
QCCPU QCCPU LCPU
(Q mode)*1 CPU CPU CPU
CC IE Control
 *3 *4  *3 
CC IE Field
MELSECNET/H      
*6 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Redundant CPU cannot be accessed.

*2 : Relayed stations 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.

4.17.3 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Bus connection
4.17 GOT Transparent Function Communication
*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.

241
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU:
IONumber
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)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs Connected station Connected station
*1 1023 (0x3FF) Connected CPU: Connected CPU: side module I/O side module I/O
ActIONumber
1023 (0x3FF) 1023 (0x3FF) address address
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)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)

242
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Target station side
ActStation
255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number
number

ActTimeOut*3 10000 Any value specified by user in ms units

Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_A900GOT (0x21)
(UNIT_QNCPU)
*1 : For the I/O address, specify the value of the actual start I/O number divided by 16.
4
*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 5000ms. When a value greater than 255000ms is specified,
the value is fixed to 255000ms.

4.17.3 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Bus connection
4.17 GOT Transparent Function Communication

243
4.17.4 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Bus connection

(1) Configuration

Connected Relayed
GOT Bus
station CPU module
USB
Relayed network

Relayed Relayed
station CPU module
Personal computer

(2) Property patterns

Connected station CPU Relayed station CPU
QCPU Q motion Relayed network R motion
RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 *2,*5 Ethernet    
 
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

QCPU Q motion Relayed network QCPU QS Q motion FX
QCCPU LCPU
(Q mode) CPU (Q mode)*1 CPU CPU CPU
CC IE Control
 *3 *4  *3 
CC IE Field
MELSECNET/H      
*1 *2,*5 Ethernet      
 
Serial
     
communication
CC-Link      

244
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected station CPU Relayed station CPU

Relayed network R motion
QCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    
4
Connected station CPU Relayed station CPU
Relayed network QCPU QS Q motion FX
QCCPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Control
 *3 *4  *3 
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Redundant CPU cannot be accessed.

*2 : Relayed stations 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.

4.17.4 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Bus
4.17 GOT Transparent Function Communication
connection

245
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU:
IONumber
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)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs Connected station Connected station
ActIONumber*1 1023 (0x3FF) Connected CPU: Connected CPU: side module I/O side module I/O
1023 (0x3FF) 1023 (0x3FF) address address
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)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT (0x13)
SERIAL)
Target station side
ActStation
255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number
number

ActTimeOut*3 10000 Any value specified by user in ms units

246
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_A900GOT (0x21)
(UNIT_QNCPU)
*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

*3 :
2: Channel 2
When a value between 0 and 5000 [ms] is specified, the value is fixed to 5000ms. When a value greater than 255000ms is specified,
4
the value is fixed to 255000ms.

4.17.4 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Bus
4.17 GOT Transparent Function Communication
connection

247
4.17.5 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

(a) Configuration

Connected R series- Relayed

station CPU compatible C24 module
GOT

Serial Relayed network

Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected station CPU Relayed station CPU
R motion Relayed network R motion
RCPU RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
*2   
CC IE Field
MELSECNET/H    
 *1,*3 Ethernet    

Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

Q
R motion Relayed network QCPU QS FX
RCPU QCCPU LCPU motion
CPU (Q mode) CPU CPU
CPU
CC IE Control
  *2   
CC IE Field
MELSECNET/H      
 *1,*3 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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.

248
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  

19200
ActBaudRate (BAUDRATE_ Match to the setting of R series-compatible C24.
19200)
ActConnectUnit
0(0x00) Connected station side module station number
Number 4
8 (TRC_DTR
ActControl Depending on the used cable.
_OR_RTS)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber *2
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:

4.17.5 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial
4.17 GOT Transparent Function Communication
976 (0x3D0)
No specification:

communication module
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)
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
Connected CPU: Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
No.1: 992 (0x3E0) No.1: 992 (0x3E0) Connected station Connected station
ActIONumber *2 1023 (0x3FF) No.2: 993 (0x3E1) No.2: 993 (0x3E1) side module I/O side module I/O
No.3: 994 (0x3E2) No.3: 994 (0x3E2) address address
No.4: 995 (0x3E3) No.4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Target station side
976 (0x3D0) Control system:
No specification: 976 (0x3D0)
1023 (0x3FF) No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *3 number

249
 Property pattern
Property Default value
 *1  
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL
SERIAL)
0x01
ActPacketType 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)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActSourceNetwork
0(0x00) Fixed to 0 (0x00)
Number
ActSourceStation
0(0x00) Fixed to 0 (0x00)
Number
ActDestinationPort
0(0x00) Fixed to 0 (0x00)
Number
ActIntelligent
0(0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_RJ71C24
(UNIT_QNCPU)
*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 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

250
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(2) When performing multi-drop link on the connected station side R series-
compatible C24 with the relayed module

(a) Configuration

Connected R series- Relayed

station CPU compatible C24 module
GOT

Serial Multi-drop link

Relayed Relayed
station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
RCPU, Relayed network
R motion
R motion RCPU RCCPU FX5CPU
CPU
CPU *1,*4
Independent Serial
    
mode *2 communication

Connected
Relayed station CPU
station CPU
RCPU, Relayed network
QCPU Q motion
R motion QCCPU LCPU QSCPU FXCPU

4.17.5 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial
4.17 GOT Transparent Function Communication
*3 CPU
(Q mode)
CPU *1,*4

communication module
Independent Serial
*2
      
mode communication
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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.

251
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200 Match to the setting of
ActBaudRate
(BAUDRATE_19200) R series-compatible C24.
ActConnectUnitNumber 0(0x00) Connected station side module station number
ActControl 8 (TRC_DTR_OR_RTS) Depending on the used cable.
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
ActDestinationIONumber *1 0 (0x00) Fixed to 0 (0x00) Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
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)
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected station
Connected CPU:
ActIONumber *1 1023 (0x3FF) side module I/O
1023 (0x3FF)
address
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
Multi-drop channel
ActMultiDropChannelNumber *2 0 (0x00) Fixed to 0 (0x00)
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
0x04
ActProtocolType 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)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActSourceNetworkNumber 0(0x00) Fixed to 0 (0x00)
ActSourceStationNumber 0(0x00) Fixed to 0 (0x00)

252
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
 
ActDestinationPortNumber 0(0x00) Fixed to 0 (0x00)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)
MELSECNET/10 is not included. : 0 (0x00)
ActThroughNetworkType 0 (0x00)
MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) module station
number

ActUnitType
0x13
(UNIT_QNCPU)
UNIT_RJ71C24 4
*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.17.5 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial
4.17 GOT Transparent Function Communication
communication module

253
 (3) When a relayed module other than the connected station side Q series-
compatible C24 exists

(a) Configuration

Connected Q series- Relayed

station CPU compatible C24 module
GOT
Serial Relayed network

Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected station CPU Relayed station CPU
QCPU Q motion Relayed network R motion
RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 *2,*5 Ethernet    
 
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

QCPU Q motion Relayed network QCPU QS Q motion FX
QCCPU LCPU
(Q mode) CPU (Q mode)*1 CPU CPU CPU
CC IE Control
 *3 *4  *3 
CC IE Field
MELSECNET/H      
*1 *2,*5 Ethernet      
 
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Redundant CPU cannot be accessed.

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

254
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
ActConnectUnit
0 (0x00) Connected station side module station number
Number
4
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU:
IONumber
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)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActIntelligent

4.17.5 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial
4.17 GOT Transparent Function Communication
0 (0x00) Fixed to 0 (0x00)
PreferenceBit

communication module
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs Connected station Connected station
ActIONumber*1 1023 (0x3FF) Connected CPU: Connected CPU: side module I/O side module I/O
1023 (0x3FF) 1023 (0x3FF) address address
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)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)
Target station side
ActStation
255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number
number

255
 Property pattern
Property Default value
   
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_QJ71C24 (0x19)
(UNIT_QNCPU)
*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

256
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(4) When performing multi-drop link on the connected station side Q series-
compatible C24 with the relayed module

(a) Configuration

Connected Q series- Relayed

station CPU compatible C24 module
GOT
Multi-drop link
Serial

Relayed Relayed
station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
QCPU R motion
RCPU RCCPU FX5CPU
(Q mode)*1 CPU
Independent Serial
    
mode *2 communication

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QCPU QS Q motion FX
QCCPU LCPU
(Q mode)*1 (Q mode)*1 CPU CPU CPU
Independent

4.17.5 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial
4.17 GOT Transparent Function Communication
Serial
      
mode *2 communication

communication module
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : For Redundant CPU, computer link 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)

257
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200 Q series BAUDRATE_9600, BAUDRATE_19200,
ActBaudRate
(BAUDRATE_19200) BAUDRATE_38400, BAUDRATE_57600, BAUDRATE_115200
ActConnectUnitNumber 0 (0x00) Connected station side module station number
8
ActControl Depending on used cable.
(TRC_DTR_OR_RTS)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
Target station side
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00)
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)
For single CPU
Fixed to 1023 (0x3FF)
For multiple CPUs
Connected CPU:
Connected station side module
ActIONumber*2 1023 (0x3FF) 1023 (0x3FF)
I/O address
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
Multi-drop channel
ActMultiDropChannelNumber*1 0 (0x00) Fixed to 0 (0x00)
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
0x04
ActProtocolType PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)
MELSECNET/10 is not included. : 0 (0x00)
ActThroughNetworkType 0 (0x00)
MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side module
ActUnitNumber 0 (0x00) 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

258
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(5) When a relayed module other than the connected station side L series-
compatible C24 exists

(a) Configuration

Connected L series- Relayed

station CPU compatible C24 module
GOT
Serial Relayed network

Relayed Relayed
station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*2    
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    

Connected

4.17.5 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial
4.17 GOT Transparent Function Communication
Relayed station CPU
station CPU
Relayed network

communication module
QCPU QS Q motion FX
LCPU QCCPU LCPU
(Q mode)*1 CPU CPU CPU

CC IE Field*2  *3    
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

259
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
ActConnectUnit
0 (0x00) Connected station side module station number
Number
8
ActControl (TRC_DTR_OR_ Depending on used cable.
RTS)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
ActDestination
0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU: Fixed to 0 (0x00)
IONumber
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
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Fixed to 1023 Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) Connected CPU:
(0x3FF) module I/O address module I/O address
1023 (0x3FF)
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
1
ActParity ODD_PARITY
(ODD_PARITY)
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)

260
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Fixed to 255 Target station side
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LJ71C24 (0x54)
(UNIT_QNCPU)
*1 : For the I/O address, specify the value of the actual start I/O number divided by 16.
4
*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.17.5 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial
4.17 GOT Transparent Function Communication
communication module

261
 (6) When performing multi-drop link on the connected station side L series-
compatible C24 with the relayed module

(a) Configuration

Connected L series- Relayed

station CPU compatible C24 module
GOT
Multi-drop link
Serial

Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
Independent Serial
*2
    
mode communication

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
LCPU QCCPU LCPU
(Q mode)*1 CPU CPU CPU
Independent Serial
      
mode *2 communication
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

262
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
BAUDRATE_9600, BAUDRATE_19200,
19200
ActBaudRate BAUDRATE_38400, BAUDRATE_57600,
(BAUDRATE_19200)
BAUDRATE_115200
ActConnectUnitNumber 0 (0x00) Connected station side module station number

ActControl
8
Depending on used cable. 4
(TRC_DTR_OR_RTS)
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
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)
Connected station side
ActIONumber*1 1023 (0x3FF) Fixed to 1023 (0x3FF)

4.17.5 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Serial
4.17 GOT Transparent Function Communication
module I/O address
Multi-drop channel

communication module
ActMultiDropChannelNumber*2 0 (0x00) Fixed to 0 (0x00)
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
0x04
ActProtocolType PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)
MELSECNET/10 is not included. : 0 (0x00)
ActThroughNetworkType 0 (0x00)
MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00)
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

263
4.17.6 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

(a) Configuration

Connected R series- Relayed

station CPU compatible C24 module
GOT
Relayed network
USB

Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected station
Relayed station CPU
CPU
Relayed network
R motion R motion
RCPU RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
*2   
CC IE Field
MELSECNET/H    
 *1,*3 Ethernet    

Serial
   
communication
CC-Link    

Connected station
Relayed station CPU
CPU
Relayed network
R motion QCPU QS Q motion FX
RCPU QCCPU LCPU
CPU (Q mode) CPU CPU CPU
CC IE Control
  *2   
CC IE Field
MELSECNET/H      
 *1,*3 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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.

264
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  

ActConnectUnit
0(0x00) Connected station side module station number
Number
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side 4
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber *2
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) 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)

4.17.6 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial
4.17 GOT Transparent Function Communication
ActIntelligent
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)

communication module
PreferenceBit
Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
Connected CPU: Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
No.1: 992 (0x3E0) No.1: 992 (0x3E0) Connected station Connected station
ActIONumber *2 1023 (0x3FF) No.2: 993 (0x3E1) No.2: 993 (0x3E1) side module I/O side module I/O
No.3: 994 (0x3E2) No.3: 994 (0x3E2) address address
No.4: 995 (0x3E3) No.4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Target station side
976 (0x3D0) Control system:
No specification: 976 (0x3D0)
1023 (0x3FF) No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *3 number
Target station side
*4 0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
ActNetworkNumber
number

265
 Property pattern
Property Default value
 *1  
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT
SERIAL)
0x01
ActPacketType PACKET_PLC1
(PACKET_PLC1)
ActPortNumber 1 (PORT_1) Fixed to 0 (0x00)
19200
ActBaudRate (BAUDRATE_ Fixed to 0 (0x00)
19200)
ActHostAddress 1.1.1.1 Fixed to NULL
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
8(TRC_DTR_
ActControl Fixed to 0 (0x00)
OR_RTS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActSourceNetwork
0(0x00) Fixed to 0 (0x00)
Number
ActSourceStation
0(0x00) Fixed to 0 (0x00)
Number
ActDestinationPort
0(0x00) Fixed to 0 (0x00)
Number
Target station side
*4 255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
ActStationNumber
number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_RJ71C24
(UNIT_QNCPU)
*1 : When accessing via Ethernet module (R series-compatible E71), consider the following:
• 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 (either of IP address calculation system, table conversion system, or combined
system) for "MNET/H routing information".
*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

266
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(2) When performing multi-drop link on the connected station side R series-
compatible C24 with the relayed module

(a) Configuration

Connected R series-
station CPU compatible C24
GOT

USB Multi-drop link

Relayed Relayed
station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
RCPU, Relayed network
R motion
R motion RCPU RCCPU FX5CPU
CPU
CPU *1,*4
Independent Serial
    
mode *3 communication

Connected
Relayed station CPU
station CPU
RCPU, Relayed network
QCPU QS Q motion FX
R motion QCCPU LCPU

4.17.6 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial
4.17 GOT Transparent Function Communication
(Q mode)*2 CPU CPU CPU
CPU *1,*4

communication module
Independent Serial
      
mode *3 communication
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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.

267
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
ActConnectUnitNumber 0(0x00) Connected station side module station number
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
ActDestinationIONumber *1 0 (0x00) Fixed to 0 (0x00) Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
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)
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected station
Connected CPU:
ActIONumber *1 1023 (0x3FF) side module I/O
1023 (0x3FF)
address
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
Multi-drop channel
ActMultiDropChannelNumber *2 0 (0x00) Fixed to 0 (0x00)
number
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00)
0x04
ActProtocolType PROTOCOL_USBGOT
(PROTOCOL_SERIAL)
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)

268
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
 
MELSECNET/10 is not included. : 0 (0x00)
ActThroughNetworkType 0 (0x00)
MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) module station
number
0x13
ActUnitType UNIT_RJ71C24
(UNIT_QNCPU)
*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. 4
0: Default channel of module
1: Channel 1
2: Channel 2

4.17.6 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial
4.17 GOT Transparent Function Communication
communication module

269
 (3) When a relayed module other than the connected station side Q series-
compatible C24 exists

(a) Configuration

Connected Q series- Relayed

station CPU compatible C24 module
GOT
USB Relayed network

Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected station CPU Relayed station CPU
Relayed
QCPU Q motion R motion
network RCPU RCCPU FX5CPU
(Q mode) CPU CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 *2,*5 Ethernet    
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

Relayed
QCPU Q motion QCPU QS Q motion FX
network QCCPU LCPU
(Q mode) CPU *1 CPU CPU CPU
(Q mode)
CC IE Control
 *3 *4  *3 
CC IE Field
MELSECNET/H      
*1 *2,*5 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Redundant CPU cannot be accessed.

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

270
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
ActConnectUnit
0 (0x00) Connected station side module station number
Number
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side Target station side 4
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU:
IONumber
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)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
For single CPU
For single CPU

4.17.6 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial
4.17 GOT Transparent Function Communication
Fixed to
Fixed to
1023 (0x3FF)

communication module
1023 (0x3FF)
For multiple CPUs
For multiple CPUs Connected station Connected station
Connected CPU:
ActIONumber*1 1023 (0x3FF) Connected CPU: side module I/O side module I/O
1023 (0x3FF)
1023 (0x3FF) address address
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)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT (0x13)
SERIAL)
Target station side
ActStation
255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number
number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units

271
 Property pattern
Property Default value
   
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_QJ71C24 (0x19)
(UNIT_QNCPU)
*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

272
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(4) When performing multi-drop link on the connected station side Q series-
compatible C24 with the relayed module

(a) Configuration

Connected Q series-
station CPU compatible C24
GOT

USB Multi-drop link

Relayed Relayed
station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
QCPU R motion
RCPU RCCPU FX5CPU
*1 CPU
(Q mode)
Independent Serial
    
mode*2 communication

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QCPU QS Q motion FX
QCCPU LCPU
(Q mode)*1 (Q mode)*1 CPU CPU CPU
Independent

4.17.6 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial
4.17 GOT Transparent Function Communication
Serial
*2
      
mode communication

communication module
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

273
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
ActConnectUnitNumber 0 (0x00) Connected station side module station number
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
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)
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected CPU: Connected station side
ActIONumber*1 1023 (0x3FF)
1023 (0x3FF) module I/O address
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
Multi-drop channel
ActMultiDropChannelNumber*2 0 (0x00) Fixed to 0 (0x00)
number
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00)
0x04
ActProtocolType PROTOCOL_USBGOT (0x13)
(PROTOCOL_SERIAL)
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)
MELSECNET/10 is not included. : 0 (0x00)
ActThroughNetworkType 0 (0x00)
MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side
ActUnitNumber 0(0x00) Fixed to 0 (0x00)
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

274
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(5) When a relayed module other than the connected station side L series-
compatible C24 exists

(a) Configuration

Connected L series- Relayed

station CPU compatible C24 module
GOT
Relayed network
USB

Relayed Relayed
station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*2    
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    

Connected

4.17.6 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial
4.17 GOT Transparent Function Communication
Relayed station CPU
station CPU
Relayed network

communication module
QCPU QS Q motion FX
LCPU QCCPU LCPU
(Q mode)*1 CPU CPU CPU

CC IE Field*2  *3    
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

275
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
ActBaudRate (BAUDRATE_19 Fixed to 0 (0x00)
200)
ActConnectUnit
0 (0x00) Connected station side module station number
Number
8
ActControl (TRC_DTR_OR_ Fixed to 0 (0x00)
RTS)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
ActDataBits 8 (DATABIT_8) Fixed to 0 (0x00)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
ActDestination
0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU: Fixed to 0 (0x00)
IONumber
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
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Fixed to 1023 Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) Connected CPU:
(0x3FF) module I/O address module I/O address
1023 (0x3FF)
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
1
ActParity Fixed to 0 (0x00)
(ODD_PARITY)
ActPortNumber 1 (PORT_1) Fixed to 0 (0x00)
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT (0x13)
SERIAL)
Fixed to 255 Target station side
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number

276
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_LJ71C24 (0x54)
(UNIT_QNCPU)
*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

4.17.6 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial
4.17 GOT Transparent Function Communication
communication module

277
 (6) When performing multi-drop link on the connected station side L series-
compatible C24 with the relayed module

(a) Configuration

Connected L series-
station CPU compatible C24
GOT
USB Multi-drop link

Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
Independent Serial
*2
    
mode communication

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
LCPU QCCPU LCPU
*1 CPU CPU CPU
(Q mode)
Independent Serial
      
mode*2 communication
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

278
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
ActConnectUnitNumber 0 (0x00) Connected station side module station number
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
Target station side
For single CPU
Fixed to 4
1023 (0x3FF)
For multiple CPUs
ActDestinationIONumber 0 (0x00) Fixed to 0 (0x00) Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
No.2: 993 (0x3E1)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
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)
Connected station side
ActIONumber*1 1023 (0x3FF) Fixed to 1023 (0x3FF) relayed module I/O
address
Multi-drop channel
ActMultiDropChannelNumber*2 0 (0x00) Fixed to 0 (0x00)
number
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00)

4.17.6 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Serial
4.17 GOT Transparent Function Communication
0x04
ActProtocolType PROTOCOL_USBGOT (0x13)
(PROTOCOL_SERIAL)

communication module
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF)
MELSECNET/10 is not included. : 0 (0x00)
ActThroughNetworkType 0 (0x00)
MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00)
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

279
4.17.7 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: R series-compatible E71

(1) Configuration

Connected R series- Relayed

station CPU compatible E71 module
Ethernet

GOT Relayed network

Serial Relayed Relayed

station CPU module

Personal computer

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
RCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 Ethernet    

Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
RCPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*1 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

280
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
ActBaudRate (BAUDRATE_
BAUDRATE_57600, BAUDRATE_115200
19200)
Connected station
ActConnectUnit
0(0x00) Fixed to 0 (0x00) side module station Fixed to 0 (0x00) Fixed to 0 (0x00) 4
Number *1
number
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber *2
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:

4.17.7 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: R series-
4.17 GOT Transparent Function Communication
976 (0x3D0)
No specification:

compatible E71
1023 (0x3FF)
ActDestinationPort 5001 for MELSOFT connection
0(0x00)
Number Any 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 connected station side module
Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
Connected CPU: Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
No.1: 992 (0x3E0) No.1: 992 (0x3E0) Connected station Connected station
ActIONumber *2 1023 (0x3FF) No.2: 993 (0x3E1) No.2: 993 (0x3E1) side module I/O side module I/O
No.3: 994 (0x3E2) No.3: 994 (0x3E2) address address
No.4: 995 (0x3E3) No.4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Target station side
976 (0x3D0) Control system:
No specification: 976 (0x3D0)
1023 (0x3FF) No specification:
1023 (0x3FF)

281
 Property pattern
Property Default value
   
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *4 number
Connected station Connected station
Target station side Target station side side R series- side R series-
ActNetworkNumber *5 0 (0x00) module network module network compatible compatible
number number E71 E71
network number network number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL
SERIAL)
0x01
ActPacketType PACKET_PLC1
(PACKET_PLC1)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
8(TRC_DTR_
ActControl Depending on the used cable.
OR_RTS)
ActDataBits 8(DATABIT_8) Fixed to 8 (0x08)
ActParity 1(ODD_PARITY) Fixed to 1 (0x01)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
ActSourceNetwork
0(0x00) GOT side network number
Number *6
ActSourceStation
0(0x00) GOT side station number
Number *7
Connected station Connected station
Target station side Target station side side R series- side R series-
ActStationNumber *5 255 (0xFF) module station module station compatible compatible
number number E71 E71
station number station number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOT_RJ71EN71
(UNIT_QNCPU)

282
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

*1 : When the property pattern is , 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 of the actual start I/O number divided 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  or , 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 4
same Ethernet loop.

4.17.7 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: R series-
4.17 GOT Transparent Function Communication
compatible E71

283
4.17.8 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Q series-compatible E71

(1) Configuration

Connected Q series- Relayed

station CPU compatible E71*1 module
Ethernet

GOT Relayed network

Serial Relayed Relayed

station CPU module

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

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
QCPU R motion
RCPU RCCPU FX5CPU
(Q mode) CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 Ethernet    

Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QCPU QS Q motion FX
QCCPU LCPU
(Q mode) *1 CPU CPU CPU
(Q mode)
CC IE Control
 *2 *3   
CC IE Field
MELSECNET/H      
*1 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

284
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
Connected station
ActConnectUnit
0 (0x00) Fixed to 0 (0x00) side module station Fixed to 0 (0x00) Fixed to 0 (0x00) 4
Number
number
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU:
IONumber
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)
ActDestination
0 (0x00) 5001
PortNumber
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)

4.17.8 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Q series-
4.17 GOT Transparent Function Communication
Bit
ActDsidProperty

compatible E71
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of connected station side module
Target station side
For single CPU
For single CPU
Fixed to
Fixed to
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
For multiple CPUs Connected station Connected station
*1
Connected CPU:
ActIONumber 1023 (0x3FF) Connected CPU: side relayed module side relayed module
1023 (0x3FF)
1023 (0x3FF) I/O address I/O address
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)
ActMultiDrop Multi-drop channel
*2
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber number
Connected station Connected station
Target station side Target station side
ActNetwork side Q series- side Q series-
0 (0x00) module network module network
Number*3 compatible E71 compatible E71
number number
network number network number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_S PROTOCOL_SERIAL (0x04)
ERIAL)

285
 Property pattern
Property Default value
   
ActSource
0 (0x00) GOT side network number
NetworkNumber
ActSource
0 (0x00) GOT side station number
StationNumber*4
Connected station Connected station
Target station side Target station side
ActStation side Q series- side Q series-
255 (0xFF) module station module station
Number*3 compatible E71 compatible E71
number number
station number station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOT_QJ71E71 (0x40)
(UNIT_QNCPU)
*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  or  , 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.

286
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.17.9 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: L series-compatible E71

(1) Configuration

Connected L series- Relayed

station CPU compatible E71*1 module
Ethernet

GOT Relayed network

Serial Relayed Relayed

station CPU module
4

Personal computer

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

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 Ethernet    


4.17.9 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: L series-
4.17 GOT Transparent Function Communication
Serial
   

compatible E71
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
LCPU QCCPU LCPU
*1 CPU CPU CPU
(Q mode)
CC IE Control
 *2 *3   
CC IE Field
MELSECNET/H      
*1 Ethernet      
Serial
*4 *4 *4   
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

287
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
Connected station
ActConnectUnit
0 (0x00) Fixed to 0 (0x00) side module station Fixed to 0 (0x00) Fixed to 0 (0x00)
Number*1
number
8
ActControl (TRC_DTR_OR_ Depending on the used cable.
RTS)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination 5001
0 (0x00)
PortNumber*2 Host station port number for OPS connection
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of connected station side module

288
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
Connected CPU: Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
No.1: 992 (0x3E0) No.1: 992 (0x3E0) Connected station Connected station
ActIONumber*3 1023 (0x3FF) No.2: 993 (0x3E1) No.2: 993 (0x3E1) side relayed module side relayed module
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
I/O address I/O address 4
For Redundant CPU For Redundant CPU
Control system: Target station side
976 (0x3D0) Control system:
No specification: 976 (0x3D0)
1023 (0x3FF) No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*4 number
Connected station Connected station
Target station side Target station side
ActNetwork side L series- side L series-
0 (0x00) module network module network
Number*5 compatible E71 compatible E71
number number
network number network number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_S PROTOCOL_SERIAL (0x04)
ERIAL)

4.17.9 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: L series-
4.17 GOT Transparent Function Communication
ActSource
0 (0x00) GOT side network number
NetworkNumber*6

compatible E71
ActSource
0 (0x00) GOT side station number
StationNumber*7
Connected station Connected station
Target station side Target station side
ActStation side L series- side L series-
255 (0xFF) module station module station
Number*5 compatible E71 compatible E71
number number
station number station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOT_LJ71E71 (0x5D)
(UNIT_QNCPU)

289
*1 : When the property pattern is , 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  or  , 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.

290
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.17.10 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: R series-compatible E71

(1) Configuration

Connected R series- Relayed

station CPU compatible E71 module
Ethernet

GOT Relayed network

USB Relayed Relayed

station CPU module
4

Personal computer

(2) Property patterns

Connected station CPU Relayed station CPU
Relayed network R motion
RCPU RCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 *1,*2 Ethernet    
Serial
   
communication
CC-Link    

4.17.10 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: R series-
4.17 GOT Transparent Function Communication
Connected station

compatible E71
Relayed station CPU
CPU
Relayed network
QCPU QS Q motion FX
RCPU RCCPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*1 *1,*2 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

291
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
Connected station
ActConnectUnit
*1
0(0x00) Fixed to 0 (0x00) side module station Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber *2
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestinationPort 5001 for MELSOFT connection
0(0x00)
Number Any 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 connected station side module
Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
Connected CPU: Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
No.1: 992 (0x3E0) No.1: 992 (0x3E0) Connected station Connected station
ActIONumber *2 1023 (0x3FF) No.2: 993 (0x3E1) No.2: 993 (0x3E1) side module I/O side module I/O
No.3: 994 (0x3E2) No.3: 994 (0x3E2) address address
No.4: 995 (0x3E3) No.4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Target station side
976 (0x3D0) Control system:
No specification: 976 (0x3D0)
1023 (0x3FF) No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
*4
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber number

292
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Connected station Connected station
Target station side Target station side side R series- side R series-
ActNetworkNumber *5 0 (0x00) module network module network compatible compatible
number number E71 E71
network number network number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT
SERIAL)
0x01
ActPacketType
(PACKET_PLC1)
PACKET_PLC1
4
ActPortNumber 1 (PORT_1) Fixed to 0 (0x00)
19200
ActBaudRate (BAUDRATE_ Fixed to 0 (0x00)
19200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
8(TRC_DTR_
ActControl Fixed to 0 (0x00)
OR_RTS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
ActSourceNetwork
0(0x00) GOT side network number

4.17.10 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: R series-
4.17 GOT Transparent Function Communication
Number *6

compatible E71
ActSourceStation
0(0x00) GOT side station number
Number *7
Connected station Connected station
Target station side Target station side side R series- side R series-
ActStationNumber *5 255 (0xFF) module station module station compatible compatible
number number E71 E71
network number network number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOT_RJ71EN71
(UNIT_QNCPU)

293
*1 : When the property pattern is , 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 of the actual start I/O number divided 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  or , 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.

294
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.17.11 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Q series-compatible E71

(1) Configuration

Connected Q series- Relayed

station CPU compatible E71*1 module
Ethernet

GOT Relayed network

USB Relayed Relayed

station CPU module
4

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

(2) Property patterns

Connected station CPU Relayed station CPU
Relayed
QCPU R motion
QCCPU network RCPU RCCPU FX5CPU
(Q mode) CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 *4 Ethernet    
Serial

4.17.11 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Q series-
4.17 GOT Transparent Function Communication
   
communication

compatible E71
CC-Link    

Connected station CPU Relayed station CPU

Relayed
QCPU QCPU QS Q motion FX
QCCPU network QCCPU LCPU
(Q mode) *1 CPU CPU CPU
(Q mode)
CC IE Control
 *2 *3   
CC IE Field
MELSECNET/H      
*1 *4 Ethernet      
 
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

295
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
Connected station
ActConnectUnit
0 (0x00) Fixed to 0 (0x00) side module station Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination
0 (0x00) 5001
PortNumber
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of connected station side module
Target station side
Target station side
For single CPU
For single CPU
Fixed to
Fixed to
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
For multiple CPUs
Connected CPU:
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
No.1: 992 (0x3E0) Connected station Connected station
*1
No.1: 992 (0x3E0)
ActIONumber 1023 (0x3FF) No.2: 993 (0x3E1) side relayed module side relayed module
No.2: 993 (0x3E1)
No.3: 994 (0x3E2) I/O address I/O address
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
No.4: 995 (0x3E3)
For Redundant CPU
For Redundant CPU
Target station side
Control system:
Control system:
976 (0x3D0)
976 (0x3D0)
No specification:
No specification:
1023 (0x3FF)
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number

296
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Connected station Connected station
Target station side Target station side
ActNetwork side Q series- side Q series-
0 (0x00) module network module network
Number*3 compatible E71 compatible E71
number number
network number network number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT (0x13)
SERIAL)
ActSource
0 (0x00) GOT side network number
NetworkNumber
ActSource 4
0 (0x00) GOT side station number
StationNumber*4
Connected station Connected station
Target station side Target station side
ActStation side Q series- side Q series-
255 (0xFF) module station module station
Number*3 compatible E71 station compatible E71 station
number number
number number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOT_QJ71E71 (0x40)
(UNIT_QNCPU)
*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.17.11 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Q series-
4.17 GOT Transparent Function Communication
2: Channel 2
*3 : For the property pattern of  or  , specify the value set in the target station side parameter for ActNetworkNumber and

compatible E71
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.

297
4.17.12 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: L series-compatible E71

(1) Configuration

Connected L series- Relayed

station CPU compatible E71*1 module
Ethernet

GOT Relayed network

USB Relayed Relayed

station CPU module

Personal computer

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

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 Ethernet    

Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
LCPU QCCPU LCPU
*1 CPU CPU CPU
(Q mode)
CC IE Control
 *2 *3   
CC IE Field
MELSECNET/H      
*1 Ethernet      
Serial
*4 *4 *4   
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

298
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
ActBaudRate (BAUDRATE_ Fixed to 0 (0x00)
19200)
Connected station
ActConnectUnit
0 (0x00) Fixed to 0 (0x00) side module station Fixed to 0 (0x00) Fixed to 0 (0x00) 4
Number*1
number
8
ActControl (TRC_DTR_OR_ Fixed to 0 (0x00)
RTS)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
ActDataBits 8 (DATABIT_8) Fixed to 0 (0x00)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)

4.17.12 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: L series-
4.17 GOT Transparent Function Communication
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU

compatible E71
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination 5001
0 (0x00)
PortNumber*2 Host station port number for OPS connection
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of connected station side module

299
 Property pattern
Property Default value
   
Target station side
For single CPU For single CPU
Fixed to Fixed to
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
Connected CPU: Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
No.1: 992 (0x3E0) No.1: 992 (0x3E0) Connected station Connected station
ActIONumber*3 1023 (0x3FF) No.2: 993 (0x3E1) No.2: 993 (0x3E1) side relayed module side relayed module
No.3: 994 (0x3E2) No.3: 994 (0x3E2) I/O address I/O address
No.4: 995 (0x3E3) No.4: 995 (0x3E3)
For Redundant CPU For Redundant CPU
Control system: Target station side
976 (0x3D0) Control system:
No specification: 976 (0x3D0)
1023 (0x3FF) No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*4 number
Connected station Connected station
Target station side Target station side
ActNetwork side L series- side L series-
0 (0x00) module network module network
Number*5 compatible E71 compatible E71
number number
network number network number
1
ActParity Fixed to 0 (0x00)
(ODD_PARITY)
ActPortNumber 1 (PORT_1) Fixed to 0 (0x00)
0x04
ActProtocolType (PROTOCOL_S PROTOCOL_USBGOT (0x13)
ERIAL)
ActSource
0 (0x00) GOT side network number
NetworkNumber*6
ActSource
0 (0x00) GOT side station number
StationNumber*7
Connected station Connected station
Target station side Target station side
ActStation side L series- side L series-
255 (0xFF) module station module station
Number*5 compatible E71 compatible E71
number number
station number station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOT_LJ71E71 (0x5D)
(UNIT_QNCPU)

300
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

*1 : When the property pattern is , 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  or  , 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 4
same Ethernet loop.

4.17.12 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: L series-
4.17 GOT Transparent Function Communication
compatible E71

301
4.17.13 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Ethernet port

(1) When the connected station is RCPU

(a) Configuration

Connected Relayed
station CPU module
Ethernet

GOT Relayed network

Serial Relayed Relayed

station CPU module

Personal computer

(b) Property patterns

Connected station CPU Relayed station CPU
Relayed
R motion R motion
RCPU RCCPU network RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
*2   *5
CC IE Field
MELSECNET/H    
 *3 *1,*3 Ethernet *4   
Serial
*4   
communication
CC-Link    

Connected station CPU Relayed station CPU

Relayed
R motion QCPU QS Q motion FX
RCPU RCCPU network QCCPU LCPU
CPU (Q mode) CPU CPU CPU
CC IE Control
  *2   
CC IE Field
MELSECNET/H *4     
 *3 *1,*3 Ethernet *4  *4   
Serial
*4  *4   
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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 of which connected station is RCPU and relayed station is FX5UCPU can be accessed.

302
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  

19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
ActBaudRate (BAUDRATE_
BAUDRATE_57600, BAUDRATE_115200
19200)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU) 4
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber *2
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) 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)

4.17.13 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet port
4.17 GOT Transparent Function Communication
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 connected station side module
Target station Target station
RCPU, RCCPU, RCPU, RCCPU,
QCPU (Q mode), QCPU (Q mode),
ActIntelligent
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) QCCPU, QCCPU,
PreferenceBit
LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the Other than the
above : 0 (0x00) above : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For single CPU
For multiple CPUs
Fixed to
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No.1: 992 (0x3E0) Connected station Connected station
*2
Connected CPU:
ActIONumber 1023 (0x3FF) No.2: 993 (0x3E1) side module I/O side module I/O
1023 (0x3FF)
No.3: 994 (0x3E2) address address
No.1: 992 (0x3E0)
No.4: 995 (0x3E3)
No.2: 993 (0x3E1)
For Redundant CPU
No.3: 994 (0x3E2)
Target station side
No.4: 995 (0x3E3)
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)

303
 Property pattern
Property Default value
 *1  
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *3 number
Target station side
ActNetworkNumber *4 0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL
SERIAL)
0x01
ActPacketType PACKET_PLC1
(PACKET_PLC1)
ActConnectUnit
0(0x00) Fixed to 0 (0x00)
Number
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
8(TRC_DTR_
ActControl Depending on the used cable.
OR_RTS)
ActDataBits 8(DATABIT_8) Fixed to 8 (0x08)
ActParity 1(ODD_PARITY) Fixed to 1 (0x01)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActSourceNetwork
0(0x00) Fixed to 0 (0x00)
Number
ActSourceStation
0(0x00) Fixed to 0 (0x00)
Number
ActDestinationPort
0(0x00) 5006
Number
Target station side
ActStationNumber *4 255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOT_RETHER
(UNIT_QNCPU)
*1 : When accessing via Ethernet module (R series-compatible E71), consider the following:
• 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 (either of IP address calculation system, table conversion system, or combined
system) for "MNET/H routing information".
*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 , specify the value set in the target station side parameter for ActNetworkNumber and ActStationNumber.

304
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(2) When the connected station is FX5CPU

(a) Configuration

Connected Relayed
station CPU module
Ethernet

GOT Relayed network

Serial Relayed Relayed

station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FX5CPU RCPU RCCPU FX5CPU
CPU
CC IE Field    *1
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    

Connected
Relayed station CPU

4.17.13 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet port
4.17 GOT Transparent Function Communication
station CPU
Relayed network
QCPU QS Q motion FX
FX5CPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Only CC-Link IE Field Network of which relayed station is FX5UCPU can be accessed.

305
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
ActBaudRate
(BAUDRATE_19200) 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 target station
ActDataBits 8 (DATABIT_8) 8 (0x08)
ActDestinationIONumber 0 (0x00) 0 (0x00)
ActDestinationPortNumber 0 (0x00) 5562
ActDidPropertyBit 1 (0x01) 1 (0x01)
ActDsidPropertyBit 1 (0x01) 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of connected station side module
ActIntelligentPreferenceBit 0 (0x00) 0 (0x00)
ActIONumber 1023 (0x3FF) 1023 (0x3FF)
ActMultiDropChannelNumber 0 (0x00) 0 (0x00)
Target station side module
ActNetworkNumber 0 (0x00) 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
0x04
ActProtocolType PROTOCOL_SERIAL (0x04)
(PROTOCOL_SERIAL)
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)
Target station side module
ActStationNumber 255 (0xFF) 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)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOT_FXVETHER (0x2007)

306
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) When the connected station is QnUDE(H)CPU or QCCPU

(a) Configuration

Connected Relayed
station CPU module
Ethernet

GOT Relayed network

Serial Relayed Relayed

station CPU module
4
Personal computer

(b) Property patterns

Connected station CPU*1 Relayed station CPU
Relayed network R motion
QnUDE(H)CPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected station CPU*1 Relayed station CPU

4.17.13 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet port
4.17 GOT Transparent Function Communication
Relayed network QCPU QS Q motion FX
QnUDE(H)CPU QCCPU LCPU
(Q mode)*2 CPU CPU CPU
CC IE Control
 *3 *4   
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      

307
 Connected station CPU Relayed station CPU
Relayed network R motion
QCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*5 Ethernet    

Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

Relayed network QCPU QS Q motion FX
QCCPU QCCPU LCPU
(Q mode)*2 CPU CPU CPU
CC IE Control
 *3 *4   
CC IE Field
MELSECNET/H      
*5 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : The communication cannot be established when a remote password is set to the connected station CPU.
*2 : Redundant CPU cannot be accessed.
*3 : Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network cannot be
accessed.
*4 : Since CC-Link IE Controller Network is not supported, 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.

308
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  

19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU) 4
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty

4.17.13 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet port
4.17 GOT Transparent Function Communication
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
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 connected station side module
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For single CPU
For multiple CPUs
Fixed to
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No.1: 992 (0x3E0) Connected station Connected station
*2
Connected CPU:
ActIONumber 1023 (0x3FF) No.2: 993 (0x3E1) side module I/O side module I/O
1023 (0x3FF)
No.3: 994 (0x3E2) address address
No.1: 992 (0x3E0)
No.4: 995 (0x3E3)
No.2: 993 (0x3E1)
For Redundant CPU
No.3: 994 (0x3E2)
Target station side
No.4: 995 (0x3E3)
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)

309
 Property pattern
Property Default value
 *1  
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*3 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number*4
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)
Target station side
ActStation
*4
255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number
number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOT_QNETHER (0x41)
(UNIT_QNCPU)
*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 : For the property pattern of , specify the value set in the target station side parameter for ActNetworkNumber and ActStationNumber.

310
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(4) When the connected station is LCPU

(a) Configuration

Connected Relayed
station CPU module
Ethernet

GOT Relayed network

Serial Relayed Relayed

station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU*1
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*3    
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    

Connected
Relayed station CPU

4.17.13 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet port
4.17 GOT Transparent Function Communication
station CPU*1
Relayed network
QCPU QS Q motion FX
LCPU QCCPU LCPU
(Q mode)*2 CPU CPU CPU
CC IE Field*3  *4    
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

311
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
8
ActControl (TRC_DTR_OR_ Depending on used cable.
RTS)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1) Fixed to 0 (0x00)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination
0 (0x00) 5006
PortNumber
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 connected station side module
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)

312
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
Fixed to 1023 Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1)
(0x3FF) module I/O address module I/O address
No.3: 994 (0x3E2)
No.4: 995 (0x3E3) 4
For Redundant CPU
Target station side
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)
Target station side
Fixed to 255
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Module Station
(0xFF)
number

4.17.13 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet port
4.17 GOT Transparent Function Communication
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Module Station Module Station Fixed to 0 (0x00)
number number
0x13
ActUnitType UNIT_GOT_LNETHER (0x55)
(UNIT_QNCPU)
*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

313
4.17.14 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Ethernet port

(1) When the connected station is RCPU

(a) Configuration

Connected Relayed
station CPU module
Ethernet

GOT Relayed network

USB Relayed Relayed

station CPU module

Personal computer

(b) Property patterns

Connected station CPU Relayed station CPU
Relayed
R motion R motion
RCPU RCCPU network RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
*2   *4
CC IE Field
MELSECNET/H    
 *3 *1,*3 Ethernet    
 
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

Relayed
R motion QCPU QS Q motion FX
RCPU RCCPU network QCCPU LCPU
CPU (Q mode) CPU CPU CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 *3 *1,*3 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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 of which connected station is RCPU and relayed station is FX5UCPU can be accessed.

314
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  

34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 4
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber *2
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) 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 connected station side module
Target station Target station

4.17.14 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
RCPU, RCCPU, RCPU, RCCPU,

port
QCPU (Q mode), QCPU (Q mode),
ActIntelligent
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) QCCPU, QCCPU,
PreferenceBit
LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the Other than the
above : 0 (0x00) above : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For single CPU
For multiple CPUs
Fixed to
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No.1: 992 (0x3E0) Connected station Connected station
Connected CPU:
ActIONumber *2 1023 (0x3FF) No.2: 993 (0x3E1) side module I/O side module I/O
1023 (0x3FF)
No.3: 994 (0x3E2) address address
No.1: 992 (0x3E0)
No.4: 995 (0x3E3)
No.2: 993 (0x3E1)
For Redundant CPU
No.3: 994 (0x3E2)
Target station side
No.4: 995 (0x3E3)
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *3 number

315
 Property pattern
Property Default value
 *1  
Target station side
ActNetworkNumber *4 0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT
SERIAL)
0x01
ActPacketType PACKET_PLC1
(PACKET_PLC1)
ActConnectUnit
0(0x00) Fixed to 0 (0x00)
Number
ActPortNumber 1(PORT_1) Fixed to 0 (0x00)
19200
ActBaudRate (BAUDRATE_ Fixed to 0 (0x00)
19200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
8(TRC_DTR_
ActControl Fixed to 0 (0x00)
OR_RTS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActSourceNetwork
0(0x00) Fixed to 0 (0x00)
Number
ActSourceStation
0(0x00) Fixed to 0 (0x00)
Number
ActDestinationPort
0(0x00) 5006
Number
Target station side
ActStationNumber *4 255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOT_RETHER
(UNIT_QNCPU)
*1 : When accessing via Ethernet module (R series-compatible E71), consider the following:
• 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 (either of IP address calculation system, table conversion system, or combined
system) for "MNET/H routing information".
*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 , specify the value set in the target station side parameter for ActNetworkNumber and ActStationNumber.

316
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(2) When the connected station is FX5CPU

(a) Configuration

Connected Relayed
station CPU module
Ethernet

GOT Relayed network

USB Relayed Relayed

station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FX5CPU RCPU RCCPU FX5CPU
CPU
CC IE Field    *1
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    

Connected
Relayed station CPU

4.17.14 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
station CPU
Relayed network
QCPU QS Q motion FX

port
FX5CPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Only CC-Link IE Field Network of which relayed station is FX5UCPU can be accessed.

317
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200
ActBaudRate 0 (0x00)
(BAUDRATE_19200)
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 target station
ActDataBits 8 (DATABIT_8) 0 (0x00)
ActDestinationIONumber 0 (0x00) 0 (0x00)
ActDestinationPortNumber 0 (0x00) 5562
ActDidPropertyBit 1 (0x01) 1 (0x01)
ActDsidPropertyBit 1 (0x01) 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of connected station side module
ActIntelligentPreferenceBit 0 (0x00) 0 (0x00)
ActIONumber 1023 (0x3FF) 1023 (0x3FF)
ActMultiDropChannelNumber 0 (0x00) 0 (0x00)
Target station side module
ActNetworkNumber 0 (0x00) 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)
0x04
ActProtocolType PROTOCOL_USBGOT (0x13)
(PROTOCOL_SERIAL)
ActStopBits 0 (STOPBIT_ONE) 0 (0x00)
ActSumCheck 0 (NO_SUM_CHECK) 0 (0x00)
ActSourceNetworkNumber 0 (0x00) 0 (0x00)
ActSourceStationNumber 0 (0x00) 0 (0x00)
Target station side module
ActStationNumber 255 (0xFF) 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)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOT_FXVETHER (0x2007)

318
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

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

(a) Configuration

Connected Relayed
station CPU module
Ethernet

GOT Relayed network

USB Relayed Relayed

station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU*1
Relayed network
R motion
QnUDE(H)CPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

4.17.14 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
Connected
Relayed station CPU
station CPU*1

port
Relayed network
QCPU QS Q motion FX
QnUDE(H)CPU QCCPU LCPU
(Q mode)*2 CPU CPU CPU
CC IE Control
 *3 *4   
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      

319
 Connected
Relayed station CPU
station CPU*1
Relayed network
R motion
QCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU*1
Relayed network
QCPU QS Q motion FX
QCCPU QCCPU LCPU
*2 CPU CPU CPU
(Q mode)
CC IE Control
 *3 *4   
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : The communication cannot be established when a remote password is set to the connected station CPU.
*2 : Redundant CPU cannot be accessed.
*3 : Since CC-Link IE Field Network is not supported, Q12DCCPU-V (Basic mode) relayed by CC-Link IE Field Network
cannot be accessed.
*4 : Since CC-Link IE Controller Network is not supported, LCPU relayed by CC-Link IE Controller Network cannot be
accessed.

320
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 *1  

34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to 4
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit

4.17.14 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
ActHostAddress 1.1.1.1 Host name or IP address of connected station side module

port
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For single CPU
For multiple CPUs
Fixed to
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No.1: 992 (0x3E0) Connected station Connected station
Connected CPU:
ActIONumber*2 1023 (0x3FF) No.2: 993 (0x3E1) side module I/O side module I/O
1023 (0x3FF)
No.3: 994 (0x3E2) address address
No.1: 992 (0x3E0)
No.4: 995 (0x3E3)
No.2: 993 (0x3E1)
For Redundant CPU
No.3: 994 (0x3E2)
Target station side
No.4: 995 (0x3E3)
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*3 number

321
 Property pattern
Property Default value
 *1  
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number*4
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT (0x13)
SERIAL)
Target station side
ActStation
255 (0xFF) Fixed to 255 (0xFF) Module Station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number*4
number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Module Station Module Station
number number
0x13
ActUnitType UNIT_GOT_QNETHER (0x41)
(UNIT_QNCPU)
*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 : For the property pattern of , specify the value set in the target station side parameter for ActNetworkNumber and ActStationNumber.

322
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(4) When the connected station is LCPU

(a) Configuration

Connected Relayed
station CPU module
Ethernet

GOT Relayed network

USB Relayed Relayed

station CPU module
4
Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU*1
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*3    
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    

Connected

4.17.14 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
Relayed station CPU
station CPU*1
Relayed network

port
QCPU QS Q motion FX
LCPU QCCPU LCPU
*2 CPU CPU CPU
(Q mode)
CC IE Field*3  *4    
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

323
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
ActBaudRate (BAUDRATE_ Fixed to 0 (0x00)
19200)
8
ActControl (TRC_DTR_OR_ Fixed to 0 (0x00)
RTS)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
ActDataBits 8 (DATABIT_8) Fixed to 0 (0x00)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1) Fixed to 0 (0x00)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination
0 (0x00) 5006
PortNumber
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 connected station side module
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent LCPU, QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit RCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)

324
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
Fixed to 1023 Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1)
(0x3FF) module I/O address module I/O address
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
4
For Redundant CPU
Target station side
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
1
ActParity Fixed to 0 (0x00)
(ODD_PARITY)
ActPortNumber 1 (PORT_1) Fixed to 0 (0x00)
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT (0x13)

4.17.14 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
SERIAL)
Target station side

port
Fixed to 255
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF) Module Station
(0xFF)
number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Module Station Module Station Fixed to 0 (0x00)
number number
0x13
ActUnitType UNIT_GOT_LNETHER (0x55)
(UNIT_QNCPU)
*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

325
4.17.15 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Ethernet adapter module

(1) Configuration

Connected CC-Link IE Field Relayed

station CPU Network module module

Relayed network
Ethernet Adapter module

Ethernet Relayed Relayed

station CPU module
GOT
Serial

Personal computer

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
QnUDE(H)CPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
QnUDE(H)CPU QCCPU LCPU
(Q mode)*1 CPU CPU CPU
CC IE Control
 *2 *3   
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      

326
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*3    
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    
4
Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
LCPU QCCPU LCPU
(Q mode)*1 CPU CPU CPU

CC IE Field*3  *2    
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*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.17.15 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
adapter module

327
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
19200
BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400, BAUDRATE_57600,
ActBaudRate (BAUDRATE_
BAUDRATE_115200
19200)
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of Ethernet adapter module
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For single CPU
For multiple CPUs
Fixed to
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No.1: 992 (0x3E0) Connected station Connected station
Connected CPU:
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1) side module I/O side module I/O
1023 (0x3FF)
No.3: 994 (0x3E2) address address
No.1: 992 (0x3E0)
No.4: 995 (0x3E3)
No.2: 993 (0x3E1)
For Redundant CPU
No.3: 994 (0x3E2)
Target station side
No.4: 995 (0x3E3)
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number

328
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Connected station Connected station Connected station
Target station side
ActNetwork side CC-Link IE Field side CC-Link IE Field side CC-Link IE Field
0 (0x00) module station
Number*3 Network module Network module Network module
number
network number network number network number
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_SERIAL (0x04)
SERIAL)
Connected station Connected station Connected station
ActStation
255 (0xFF)
side CC-Link IE Field
Target station side
Module Station
side CC-Link IE Field side CC-Link IE Field 4
*3 Network module Network module Network module
Number
number
station number station number station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Module Station Module Station
number number
0x13
ActUnitType UNIT_GOT_NZ2GF_ETB (0x5B)
(UNIT_QNCPU)
*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 ,  or , 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 , specify the value set in the target station side parameter for ActNetworkNumber and ActStationNumber.

4.17.15 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
adapter module

329
4.17.16 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Ethernet adapter module

(1) Configuration

Connected CC-Link IE Field Relayed

station CPU Network module module

Relayed network
Ethernet Adapter module
Relayed Relayed
Ethernet
station CPU module
GOT

USB

Personal computer

(2) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
QnUDE(H)CPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
QnUDE(H)CPU QCCPU LCPU
(Q mode)*1 CPU CPU CPU
CC IE Control
 *2 *3   
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      

330
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*3    
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    
4
Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
LCPU QCCPU LCPU
(Q mode)*1 CPU CPU CPU

CC IE Field*3      
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*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.17.16 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
adapter module

331
 (3) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of Ethernet adapter module
ActIntelligent
0 (0x00) Fixed to 0 (0x00)
PreferenceBit
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For single CPU
For multiple CPUs
Fixed to
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No.1: 992 (0x3E0) Connected station Connected station
*1
Connected CPU:
ActIONumber 1023 (0x3FF) No.2: 993 (0x3E1) side module I/O side module I/O
1023 (0x3FF)
No.3: 994 (0x3E2) address address
No.1: 992 (0x3E0)
No.4: 995 (0x3E3)
No.2: 993 (0x3E1)
For Redundant CPU
No.3: 994 (0x3E2)
Target station side
No.4: 995 (0x3E3)
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Connected station Connected station Connected station
Target station side
ActNetwork side CC-Link IE Field side CC-Link IE Field side CC-Link IE Field
0 (0x00) module station
Number*3 Network module Network module Network module
number
network number network number network number

332
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_USBGOT (0x13)
SERIAL)
Connected station Connected station Connected station
Target station side
ActStation side CC-Link IE Field side CC-Link IE Field side CC-Link IE Field
255 (0xFF) Module Station
Number*3 Network module Network module Network module
number
station number station number station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units 4
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Module Station Module Station
number number
0x13
ActUnitType UNIT_GOT_NZ2GF_ETB (0x5B)
(UNIT_QNCPU)
*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 ,  or , 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 , specify the value set in the target station side parameter for ActNetworkNumber and ActStationNumber.

4.17.16 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
adapter module

333
4.17.17 Personal computer side port: Serial, GOT1000 side port: Serial,
CPU side port: Ethernet adapter/module

(1) When the connected station is FXCPU

(a) Configuration
Ethernet adapter: FX3U-ENET-ADP Ethernet module: FX3U-ENET (-L)
Ethernet Connected Relayed Relayed Connected Ethernet
adapter station CPU module module station CPU module
Ethernet Ethernet

GOT Relayed network Relayed network GOT

Serial Relayed Relayed Relayed Relayed Serial

station CPU module module station CPU

Personal computer Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
FXCPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*1 Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

334
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

19200 BAUDRATE_9600, BAUDRATE_19200, BAUDRATE_38400,
ActBaudRate
(BAUDRATE_19200) BAUDRATE_57600, BAUDRATE_115200
8
ActControl Depending on used cable
(TRC_DTR_OR_RTS)

ActCpuType
34
CPU type corresponding to the target station 4
(CPU_Q02CPU)
Host name or IP address of FX3U-ENET-ADP module
ActHostAddress 1.1.1.1
Host name or IP address of FX3U-ENET (-L) module
ActPortNumber 1 (PORT_1) Personal computer side COM port number
0x04
ActProtocolType PROTOCOL_SERIAL
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units
0x13 FX3U-ENET-ADP: UNIT_GOT_FXETHER
ActUnitType
(UNIT_QNCPU) FX3U-ENET(-L): UNIT_GOT_FXENET

4.17.17 Personal computer side port: Serial, GOT1000 side port: Serial, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
adapter/module

335
4.17.18 Personal computer side port: USB, GOT2000/1000 side port: USB,
CPU side port: Ethernet adapter/module

(1) When the connected station is FXCPU

(a) Configuration

Ethernet adapter: FX3U-ENET-ADP Ethernet module: FX3U-ENET (-L)

Ethernet Connected Relayed Relayed Connected Ethernet
adapter station CPU module module station CPU module
Ethernet Ethernet

GOT Relayed network Relayed network GOT

USB Relayed Relayed Relayed Relayed USB

station CPU module module station CPU

Personal computer Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
FXCPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
*1 Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

336
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

34
ActCpuType CPU type corresponding to the target station
(CPU_Q02CPU)
Host name or IP address of FX3U-ENET-ADP module
ActHostAddress 1.1.1.1
Host name or IP address of FX3U-ENET (-L) module

ActProtocolType
0x04
PROTOCOL_SERIAL
4
(PROTOCOL_SERIAL)
ActTimeOut 10000 Any value specified by user in ms units
0x13 FX3U-ENET-ADP: UNIT_GOT_FXETHER
ActUnitType
(UNIT_QNCPU) FX3U-ENET(-L): UNIT_GOT_FXENET

4.17.18 Personal computer side port: USB, GOT2000/1000 side port: USB, CPU side port: Ethernet
4.17 GOT Transparent Function Communication
adapter/module

337
4.17.19 Personal computer side port: Ethernet port,
GOT2000/1000 side port: Ethernet port, CPU side port: Serial

(1) When the connected station is FX5CPU

(a) Configuration

Connected Relayed
GOT
Serial station CPU module

Ethernet Relayed network

Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FX5CPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   *1
CC IE Field
MELSECNET/H    

 Ethernet   

Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
FX5CPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Only CC-Link IE Field Network of which relayed station is FX5UCPU can be accessed.

338
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
 
19200
ActBaudRate 0 (0x00)
(BAUDRATE_19200)
ActConnectUnitNumber 0 (0x00) 0 (0x00)
ActControl 8 (TRC_DTR_OR_RTS) 0 (0x00)
ActCpuTimeOut 0 (0x00) 0 (0x00) 4
ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station
ActDataBits 8 (DATABIT_8) 0 (0x00)
ActDestinationIONumber 0 (0x00) 0 (0x00)
ActDestinationPortNumber 0 (0x00) GOT port number
ActDidPropertyBit 1 (0x01) 1 (0x01)
ActDsidPropertyBit 1 (0x01) 1 (0x01)
ActHostAddress 1.1.1.1 Host name or IP address of GOT
ActIntelligentPreferenceBit 0 (0x00) 0 (0x00)
ActIONumber 1023(0x3FF) 1023 (0x3FF)
ActMultiDropChannelNumber 0 (0x00) 0 (0x00)
Target station side module
ActNetworkNumber 0 (0x00) 0 (0x00)
network number
ActPacketType 0x01 (PACKET_PLC1) PACKET_PLC1 (0x01)
ActParity 1 (ODD_PARITY) 1 (0x01)
ActPassword Null NULL

4.17.19 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
ActPortNumber 1 (PORT_1) 0 (0x00)
0x04

port: Serial
ActProtocolType PROTOCOL_TCPIP (0x05)
(PROTOCOL_SERIAL)
ActStopBits 0 (STOPBIT_ONE) 0 (0x00)
ActSumCheck 0 (NO_SUM_CHECK) 0 (0x00)
ActSourceNetworkNumber 0 (0x00) 0 (0x00)
ActSourceStationNumber 0 (0x00) 0 (0x00)
Target station side module
ActStationNumber 255 (0xFF) 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)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_GOTETHER_FXVCPU (0x2006)

339
 (2) When the connected station is QCPU (Q mode) or QCCPU

(a) Configuration

Connected Relayed
GOT
Serial station CPU module

Ethernet Relayed network

Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected station CPU Relayed station CPU
Relayed
QCPU R motion
QCCPU network RCPU RCCPU FX5CPU
(Q mode) CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 *4 Ethernet    
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

Relayed
QCPU QCPU QS Q motion FX
QCCPU network QCCPU LCPU
(Q mode) (Q mode)*1 CPU CPU CPU
CC IE Control
 *2 *3   
CC IE Field
MELSECNET/H      
*1 *4 Ethernet      
 
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

340
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU

Target station side

Fixed to
1023 (0x3FF)
4
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination
0 (0x00) GOT port number
PortNumber
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit

4.17.19 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit

port: Serial
ActHostAddress 1.1.1.1 Host name or IP address of GOT
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For single CPU
For multiple CPUs
Fixed to
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No.1: 992 (0x3E0) Connected station Connected station
Connected CPU:
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1) side module I/O side module I/O
1023 (0x3FF)
No.3: 994 (0x3E2) address address
No.1: 992 (0x3E0)
No.4: 995 (0x3E3)
No.2: 993 (0x3E1)
For Redundant CPU
No.3: 994 (0x3E2)
Target station side
No.4: 995 (0x3E3)
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)

341
 Property pattern
Property Default value
   
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module station Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP (0x05)
SERIAL)
Target station side
ActStation
255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number
number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOTETHER_QNCPU (0x56)
(UNIT_QNCPU)
*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

342
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) When the connected station is LCPU

(a) Configuration

Connected Relayed
GOT
Serial station CPU module

Ethernet Relayed network

Relayed Relayed
station CPU module

Personal computer
4
(b) Property patterns
Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*2    
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU

4.17.19 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
QS Q motion FX
LCPU QCCPU LCPU
(Q mode)*1 CPU CPU CPU

port: Serial
CC IE Field*2  *3    
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

343
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1) Fixed to 0 (0x00)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination
0 (0x00) GOT port number
PortNumber
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
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
Fixed to 1023 Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1)
(0x3FF) module I/O address module I/O address
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
For Redundant CPU
Target station side
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number

344
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP (0x05)
SERIAL)
Fixed to 255 Target station side
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
Type
0 (0x00)
MELSECNET/10 is included. : 1 (0x01) 4
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_GOTETHER_LNCPU (0x57)
(UNIT_QNCPU)
*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.17.19 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
port: Serial

345
 (4) When the connected station is FXCPU

(a) Configuration

Connected Relayed
GOT
Serial station CPU module

Ethernet Relayed network

Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
FXCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
FXCPU QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Control
     
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

346
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value

ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to target station

ActDestination PortNumber*1 0 (0x00) GOT port number

ActHostAddress 1.1.1.1 Host name or IP address of GOT
0x04
ActProtocolType
(PROTOCOL_SERIAL)
PROTOCOL_TCPIP (0x05)
4
ActTimeOut 10000 Any value specified by user in ms units
0x13
ActUnitType UNIT_GOTETHER_LNCPU (0x57)
(UNIT_QNCPU)

*1 : For ActPortNumber, specify the value set to GOT side.

4.17.19 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
port: Serial

347
4.17.20 Personal computer side port: Ethernet port,
GOT2000/1000 side port: Ethernet port,
CPU side port: Serial communication module

(1) When the connected station is R series-compatible C24

(a) Configuration

Connected R series- Relayed

station CPU compatible C24 module
GOT
Serial
Relayed network
Ethernet
Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected station
Relayed station CPU
CPU Relayed
R motion network R motion
RCPU RCPU RCCPU FX5CPU
CPU CPU
CC IE Control
*2   
CC IE Field
MELSECNET/H    
 *1,*3 Ethernet    
Serial
   
communication
CC-Link    

Connected station
Relayed station CPU
CPU Relayed
R motion network QCPU QS Q motion FX
RCPU QCCPU LCPU
CPU (Q mode) CPU CPU CPU
CC IE Control
  *2   
CC IE Field
MELSECNET/H      
 *1,*3 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

*1 : Relayed stations 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.

348
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU

Target station side

Fixed to
1023 (0x3FF)
4
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber *1
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestinationPort
0(0x00) GOT port number
Number *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)

4.17.20 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
ActHostAddress 1.1.1.1 Host name or IP address of GOT

port: Serial communication module

Target station Target station
RCPU, RCCPU, RCPU, RCCPU,
QCPU (Q mode), QCPU (Q mode),
ActIntelligent
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) QCCPU, QCCPU,
PreferenceBit
LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the Other than the
above : 0 (0x00) above : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For single CPU
For multiple CPUs
Fixed to
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No.1: 992 (0x3E0) Connected station Connected station
Connected CPU:
ActIONumber *1 1023 (0x3FF) No.2: 993 (0x3E1) side module I/O side module I/O
1023 (0x3FF)
No.3: 994 (0x3E2) address address
No.1: 992 (0x3E0)
No.4: 995 (0x3E3)
No.2: 993 (0x3E1)
For Redundant CPU
No.3: 994 (0x3E2)
Target station side
No.4: 995 (0x3E3)
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)

349
 Property pattern
Property Default value
   
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber *3 number
Target station side
ActNetworkNumber *4 0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP
SERIAL)
0x01
ActPacketType PACKET_PLC1
(PACKET_PLC1)
ActConnectUnit
0(0x00) Fixed to 0 (0x00)
Number
ActPortNumber 1 (PORT_1) Fixed to 0 (0x00)
19200
ActBaudRate (BAUDRATE_ Fixed to 0 (0x00)
19200)
ActCpuTimeOut 0(0x00) Fixed to 0 (0x00)
8(TRC_DTR_
ActControl Fixed to 0 (0x00)
OR_RTS)
ActDataBits 8(DATABIT_8) Fixed to 0 (0x00)
ActParity 1(ODD_PARITY) Fixed to 0 (0x00)
0(STOPBIT_
ActStopBits Fixed to 0 (0x00)
ONE)
0(NO_SUM_
ActSumCheck Fixed to 0 (0x00)
CHECK)
ActSourceNetwork
0(0x00) Fixed to 0 (0x00)
Number
ActSourceStation
0(0x00) Fixed to 0 (0x00)
Number
Target station side
ActStationNumber *4 255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
number
ActThroughNetwork MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
Type MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOTETHER_RJ71C24
(UNIT_QNCPU)
*1 : For the I/O address, specify the value of the actual start I/O number divided 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 , specify the value set in the target station side parameter for ActNetworkNumber and ActStationNumber.

350
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(2) When the connected station is Q series-compatible C24

(a) Configuration

Connected Q series- Relayed

station CPU compatible C24 module
GOT
Serial
Relayed network
Ethernet
Relayed Relayed
station CPU module
4
Personal computer

(b) Property patterns

Connected station CPU Relayed station CPU
Relayed
QCPU R motion
QCCPU network RCPU RCCPU FX5CPU
(Q mode) CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1  Ethernet    
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

Relayed
QCPU QCPU QS Q motion FX

4.17.20 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
QCCPU network QCCPU LCPU
(Q mode) (Q mode)*1 CPU CPU CPU

port: Serial communication module

CC IE Control
 *2 *3   
CC IE Field
MELSECNET/H      
*1  Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

351
 (c) Property list
The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1)
IONumber
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestination
0 (0x00) GOT port number
PortNumber
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of GOT
Target station Target station
QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For single CPU
For multiple CPUs
Fixed to
Connected CPU:
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
No.1: 992 (0x3E0) Connected station Connected station
Connected CPU:
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1) side module I/O side module I/O
1023 (0x3FF)
No.3: 994 (0x3E2) address address
No.1: 992 (0x3E0)
No.4: 995 (0x3E3)
No.2: 993 (0x3E1)
For Redundant CPU
No.3: 994 (0x3E2)
Target station side
No.4: 995 (0x3E3)
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)

352
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

Property pattern
Property Default value
   
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP (0x05)
SERIAL)
Target station side
ActStation
255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF) 4
Number
number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOTETHER_QNCPU (0x56)
(UNIT_QNCPU)
*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.17.20 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
port: Serial communication module

353
 (3) When the connected station is L series-compatible C24

(a) Configuration

Connected L series- Relayed

station CPU compatible C24 module
GOT
Serial
Relayed network
Ethernet
Relayed Relayed
station CPU module

Personal computer

(b) Property patterns

Connected
Relayed station CPU
station CPU
Relayed network
R motion
LCPU RCPU RCCPU FX5CPU
CPU
CC IE Field*2    
MELSECNET/H    
Ethernet    

Serial
   
communication
CC-Link    

Connected
Relayed station CPU
station CPU
Relayed network
QCPU QS Q motion FX
LCPU QCCPU LCPU
*1 CPU CPU CPU
(Q mode)
*2  *3    
CC IE Field 
MELSECNET/H      
Ethernet      

Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

354
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(c) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side
For single CPU
Fixed to
Target station side 1023 (0x3FF)
4
For single CPU For multiple CPUs
Fixed to Connected CPU:
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs No.1: 992 (0x3E0)
ActDestinationIO
0 (0x00) Fixed to 0 (0x00) Connected CPU: No.2: 993 (0x3E1) Fixed to 0 (0x00)
Number
1023 (0x3FF) No.3: 994 (0x3E2)
No.1: 992 (0x3E0) No.4: 995 (0x3E3)
No.2: 993 (0x3E1) For Redundant CPU
No.3: 994 (0x3E2) Target station side
No.4: 995 (0x3E3) Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActDestinationPort
0 (0x00) GOT port number
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)

4.17.20 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
ActHostAddress 1.1.1.1 Host name or IP address of GOT
Target station Target station

port: Serial communication module

QCPU (Q mode), QCPU (Q mode),
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side
For single CPU
Fixed to
1023 (0x3FF)
For multiple CPUs
Connected CPU:
1023 (0x3FF)
No.1: 992 (0x3E0)
Fixed to 1023 Connected station side Connected station side
ActIONumber*1 1023 (0x3FF) No.2: 993 (0x3E1)
(0x3FF) module I/O address module I/O address
No.3: 994 (0x3E2)
No.4: 995 (0x3E3)
For Redundant CPU
Target station side
Control system:
976 (0x3D0)
No specification:
1023 (0x3FF)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number

355
 Property pattern
Property Default value
   
Target station side
ActNetworkNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module network
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP (0x05)
SERIAL)
Fixed to 255 Target station side
ActStationNumber 255 (0xFF) Fixed to 255 (0xFF) Fixed to 255 (0xFF)
(0xFF) module station number
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
module station number module station number
0x13
ActUnitType UNIT_GOTETHER_LNCPU (0x57)
(UNIT_QNCPU)
*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

356
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.17.21 Personal computer side port: Ethernet port,

GOT2000/1000 side port: Ethernet port,
CPU side port: Bus connection

(1) Configuration

Connected Relayed
GOT
Bus station CPU module

Ethernet Relayed network

4
Relayed Relayed
station CPU module

Personal computer

(2) Property patterns

Connected station CPU Relayed station CPU
Relayed network R motion
QCPU (Q mode) RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
*1 Ethernet    

Serial
   
communication
CC-Link    

4.17.21 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
Connected station CPU Relayed station CPU

port: Bus connection

Relayed network QCPU QS Q motion FX
QCPU (Q mode) QCCPU LCPU
*1 CPU CPU CPU
(Q mode)
CC IE Control
 *2 *3   
CC IE Field
MELSECNET/H      
*1 Ethernet      

Serial
     
communication
CC-Link      

357
 Connected station CPU Relayed station CPU
Relayed network R motion
QCCPU RCPU RCCPU FX5CPU
CPU
CC IE Control
   
CC IE Field
MELSECNET/H    
 Ethernet    
Serial
   
communication
CC-Link    

Connected station CPU Relayed station CPU

Relayed network QCPU QS Q motion FX
QCCPU QCCPU LCPU
(Q mode)*1 CPU CPU CPU
CC IE Control
 *2 *3   
CC IE Field
MELSECNET/H      
 Ethernet      
Serial
     
communication
CC-Link      
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

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

358
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.
Property pattern
Property Default value
   
34
ActCpuType CPU type corresponding to target station
(CPU_Q02CPU)
Target station side Target station side
For single CPU
Fixed to
For single CPU
Fixed to
4
1023 (0x3FF) 1023 (0x3FF)
For multiple CPUs For multiple CPUs
ActDestination
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Connected CPU: Connected CPU:
IONumber
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)
ActDestination
0 (0x00) GOT port number
PortNumber
ActDidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActDsidProperty
1 (0x01) Fixed to 1 (0x01) Fixed to 1 (0x01) Fixed to 0 (0x00) Fixed to 0 (0x00)
Bit
ActHostAddress 1.1.1.1 Host name or IP address of GOT
Target station Target station
QCPU (Q mode), QCPU (Q mode),

4.17.21 Personal computer side port: Ethernet port, GOT2000/1000 side port: Ethernet port, CPU side
4.17 GOT Transparent Function Communication
ActIntelligent QCCPU, QCCPU,
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)

port: Bus connection

PreferenceBit LCPU : 1 (0x01) LCPU : 1 (0x01)
Other than the above Other than the above
: 0 (0x00) : 0 (0x00)
Target station side
For single CPU
For single CPU
Fixed to
Fixed to
1023 (0x3FF)
1023 (0x3FF)
For multiple CPUs
For multiple CPUs Connected station Connected station
Connected CPU:
ActIONumber*1 1023 (0x3FF) Connected CPU: side module I/O side module I/O
1023 (0x3FF)
1023 (0x3FF) address address
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)
ActMultiDrop Multi-drop channel
0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00)
ChannelNumber*2 number
Target station side
ActNetwork
0 (0x00) Fixed to 0 (0x00) module network Fixed to 0 (0x00) Fixed to 0 (0x00)
Number
number
0x04
ActProtocolType (PROTOCOL_ PROTOCOL_TCPIP (0x05)
SERIAL)
Target station side
ActStation
255 (0xFF) Fixed to 255 (0xFF) module station Fixed to 255 (0xFF) Fixed to 255 (0xFF)
Number
number

359
 Property pattern
Property Default value
   
ActThrough MELSECNET/10 is not included. : 0 (0x00)
0 (0x00)
NetworkType MELSECNET/10 is included. : 1 (0x01)
ActTimeOut 10000 Any value specified by user in ms units
Target station side Target station side
ActUnitNumber 0 (0x00) Fixed to 0 (0x00) Fixed to 0 (0x00) module station module station
number number
0x13
ActUnitType UNIT_GOTETHER_QBUS (0x58)
(UNIT_QNCPU)
*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

360
 CHAPTER 4 PROPERTY SETTINGS OF COMMUNICATION PATHS

4.18 Q Series Bus Communication

(1) Configuration

PC CPU module
4
No. 1 No. 2 No. 3

(2) Property patterns

Own Base
RCPU RCCPU R motion CPU
  

Own Base
QCPU (Q mode) QCCPU Q motion CPU
  
: Accessible (The number in the circle is the property pattern number.), : Inaccessible

(3) Property list

The following table shows the property settings of communication paths. The setting is not necessary for those
properties without description.

4.18 Q Series Bus Communication

Property pattern
Property Default value

ActCpuType 34 (CPU_Q02CPU) CPU type corresponding to the target station
No.1 992 (0x3E0)
ActIONumber*1 1023 (0x3FF) No.2 993 (0x3E1)
No.3 994 (0x3E2)
0x04
ActProtocolType PROTOCOL_QBF (0x10)
(PROTOCOL_SERIAL)
ActUnitType 0x13 (UNIT_QNCPU) UNIT_QBF (0x1F)

361
CHAPTER 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.

(1) 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
VBA
Visual C++® .NET (MFC)
Dispatch interface VBScript

ACT control (Recommended) Visual Basic® .NET Page 366, Section 5.2
Visual C++® .NET
Visual C#® .NET
Custom interface Visual C++® .NET (MFC)

Visual Basic® .NET

.NET control Dispatch interface Visual C++® .NET Page 453, Section 5.3
®
Visual C# .NET

(2) Interface types

Dispatch interface and custom interface can be used for the functions for ACT control.
Interface Description Characteristic
Programming to acquire the interface and to create
Paste controls on the form of Visual Basic® objects is not necessary. (Programs to create objects
Dispatch
.NET, Visual C++® .NET, Visual C#® .NET, or without pasting controls on the form can be created.)
interface
VBA (Excel, Access) to use the controls. Programming with dispatch interface is easier than
programming with custom interface
Acquire the interface using the interface
Programs of custom interface are complicated as
acquisition function when using controls.
Custom interface compared to those of dispatch interface, however the
Use the object creation function to create
object creation/extinction can be managed in detail.
objects.

362
 CHAPTER 5 FUNCTIONS

5.1 Programming Considerations

This section explains the considerations of programming.

(1) 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.
5

(2) Open function (opening communication line)

The processing may take long time due to the Open function processes: establishment of communication paths,
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)

5.1 Programming Considerations

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

363
 (3) Considerations for using RnSFCPU
The following functions cannot be used for RnSFCPU.
Function Name Description
Connect Connect telephone line.
Disconnect Disconnect telephone line

In case of safety mode, the following functions cannot be used for the RnSFCPU safety device.
Function Name Description
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.

If any of these functions is used, the error code "0x010A42A5" (Operation that can not be carried out in safety mode)will be
returned.

(4) Considerations for using QSCPU

The following functions cannot be used for QSCPU.
Function Name Description
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.

(5) 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.

364
 CHAPTER 5 FUNCTIONS

(6) 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.

(a) LONG type function (Page 369, Section 5.2.3 to Page 386, Section 5.2.8)
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).
Target function
ReadDeviceBlock, WriteDeviceBlock, ReadDeviceRandom, WriteDeviceRandom, SetDevice, GetDevice
5
<Example> 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.

(b) SHORT type/INT type function (Page 427, Section 5.2.18 to Page 444, Section
5.2.23)

5.1 Programming Considerations

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 described in the section (a).
Target function
ReadDeviceBlock2, WriteDeviceBlock2, ReadDeviceRandom2, WriteDeviceRandom2, SetDevice2, GetDevice2

<Example> When reading a device data with a negative value using the ReadDeviceBlock2 function
lpsData = -1 (0xFFFF)

The data is stored as SHORT

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

Read D0 data using

the ReadDeviceBlock2 function.

365
5.2 Details of Functions (For ACT Control)

5.2.1 Open (Opening communication line)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.

(2) Feature
Open the communication line.

(3) Format (Dispatch interface)

(a) Visual C++® .NET (MFC), VBA

lRet = object.Open()
Long lRet Returned value Output

(b) VBScript
varRet = object.Open()
VARIANT varRet Returned value (LONG type) Output

(c) Visual Basic® .NET

IRet = object.Open()
Integer IRet Returned value Output

(d) Visual C++® .NET

iRet = object.Open()
int iRet Returned value Output

(e) Visual C#® .NET

iRet = object.Open()
int iRet Returned value Output

(4) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.Open( *lplRetCode )
HRESULT hResult Returned value of COM Output
Returned value of communication
LONG *lplRetCode Output
function

(5) Description
Lines are connected according to the set value of the Open function property.

366
 CHAPTER 5 FUNCTIONS

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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

5.2.1 Open (Opening communication line)

5.2 Details of Functions (For ACT Control)

367
5.2.2 Close (Closing communication line)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.

(2) Feature
Close the communication line.

(3) Format (Dispatch interface)

(a) Visual C++® .NET (MFC), VBA

lRet = object.Close()
Long lRet Returned value Output

(b) VBScript
varRet = object.Close()
VARIANT varRet Returned value (LONG type) Output

(c) Visual Basic® .NET

IRet = object.Close()
Integer IRet Returned value Output

(d) Visual C++® .NET

iRet = object.Close()
int iRet Returned value Output

(e) Visual C#® .NET

iRet = object.Close()
int iRet Returned value Output

(4) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.Close( *lplRetCode )
HRESULT hResult Returned value of COM Output
Returned value of communication
LONG *lplRetCode Output
function

(5) Description
The line connected using the Open function is closed.

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

368
 CHAPTER 5 FUNCTIONS

5.2.3 ReadDeviceBlock (Reading devices in bulk)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Read devices in bulk.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.ReadDeviceBlock(szDevice, lSize, lData(0))
5
Long lRet Returned value Output
String szDevice Device name Input
Long lSize Number of read points Input
Long lData(n) Read device value Output

(b) 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

5.2.3 ReadDeviceBlock (Reading devices in bulk)

5.2 Details of Functions (For ACT Control)
(c) 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

(d) 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

(e) 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

369
 (f) 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

(4) Format (Custom interface)

(a) 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

(5) 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).

370
 CHAPTER 5 FUNCTIONS

(6) How to specify devices

The following describes how to specify devices.
<When bit device is specified> <When word device is specified>
Example: Read 3 points (3 words) of data in 16-point unit
Example: Read 3 points of data starting from D0.
starting from M0.

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

M0 to M15*1 D0
Not used Not used
D1
M16 to M31*1 (0 is stored.)
(0 is stored.)
D2
M32 to M47*1

<When double-word device is specified> <When FXCPU devices of CN200 and later are specified>
Example: Read 3 points from LTN0 Example: Read 6 points of data starting from CN200.*2
5

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

L of CN200
H of LTN0 L of LTN0
H of CN200
H of LTN1 L of LTN1
Not used L of CN201
H of LTN2 L of LTN2 (0 is stored.) H of CN201
L of CN202
H of CN202

<When FD device is specified (4-word device)>

Example: Read 6 points of data starting from FD0.

Upper 2 bytes Lower 2 bytes

5.2.3 ReadDeviceBlock (Reading devices in bulk)

5.2 Details of Functions (For ACT Control)
LL of FD0
LH of FD0
Not used HL of FD0
(0 is stored.) 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

EG0
(E0001) (E0000)
EG1
Not used (E0003) (E0002)
(0 is stored.) EG2
(E0005) (E0004)
EG3
(E0007) (E0006)

*1 : Devices are stored from the lower bit in the order of device number.
*2 : For CN200 or later of FXCPU, 2 words are read for each 2 points. Reading only 1 point of data will result in an error.

371
 (7) Returned value
Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

372
 CHAPTER 5 FUNCTIONS

5.2.4 WriteDeviceBlock (Writing devices in bulk)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Write devices in bulk.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.WriteDeviceBlock(szDevice, lSize, lData(0))
5
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

(b) 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

5.2.4 WriteDeviceBlock (Writing devices in bulk)

5.2 Details of Functions (For ACT Control)
(c) 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

(d) 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

(e) 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

373
 (f) 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

(4) Format (Custom interface)

(a) 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

(5) 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 (lplData, varData, or iData).
• For lData (lplData, varData, or iData), reserve arrays for more than the amount specified for lSize (varSize or
iSize).

(6) How to specify devices

The following describes how to specify devices.
<When bit device is specified> <When word device is specified>
Example: Write 3 points (3 words) of data in 16-point unit
Example: Write 3 points of data starting from D0.
starting from M0.

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

M0 to M15*1 D0
Not used Not used
D1
M16 to M31*1 (0 is stored.)
(0 is stored.)
D2
M32 to M47*1

<When double-word device is specified> <When FXCPU devices of CN200 and later are specified>
Example: Write 3 points to LTN0 Example: Write 6 points of data starting from CN200.*2

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

L of CN200
H of LTN0 L of LTN0
H of CN200
H of LTN1 L of LTN1
Not used L of CN201
H of LTN2 L of LTN2 (0 is stored.) H of CN201
L of CN202
H of CN202

*1 : Devices are stored from the lower bit in the order of device number.
*2 : For CN200 or later of FXCPU, 2 words are written for each 2 points. Writing only 1 point of data will result in an error.

374
 CHAPTER 5 FUNCTIONS

<When FD device is specified (4-word device)>

Example: Write 6 points of data starting from FD0.

Upper 2 bytes Lower 2 bytes

LL of FD0
LH of FD0
Not used HL of FD0
(0 is stored.) 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.)
5
Upper 2 bytes Lower 2 bytes
EG0
(E0001) (E0000)
EG1
Not used (E0003) (E0002)
(0 is stored.) EG2
(E0005) (E0004)
EG3
(E0007) (E0006)

(7) Returned value

Normal termination : 0 is returned.

5.2.4 WriteDeviceBlock (Writing devices in bulk)

5.2 Details of Functions (For ACT Control)
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

375
5.2.5 ReadDeviceRandom (Reading devices randomly)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.

(2) Feature
Read devices randomly.
Read monitor types of inverters/robot controllers randomly.

(3) Format (Dispatch interface)

(a) 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

(b) 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

(c) 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

(d) 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

(e) 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

376
 CHAPTER 5 FUNCTIONS

(f) 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

(4) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.ReadDeviceRandom( szDevice, lSize, *lplData, *lplRetCode )
HRESULT hResult Returned value of COM Output
5
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

(5) 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.2.5 ReadDeviceRandom (Reading devices randomly)

5.2 Details of Functions (For ACT Control)
Example
When using Visual Basic®.NET ,VBA,VBScript: "D0" & vbLf & "D1" & vbLf & "D2"
®.NET: D0\nD1\nD2
When using Visual C++

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

377
 (6) How to specify devices
The following describes how to specify devices.
Example 1: 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
(0 is stored.) D0

M16 to M31*1 M0 to M15*1

Example 2: 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

Example 3: When devices including FXCPU devices of CN200 and later are specified (Total number of points: 3
points)*2
When using Visual Basic®.NET ,VBA,VBScript: "D0" & vbLf & "CN200" & vbLf & "D1"

When usingVisual C++®.NET: D0\nCN200\nD1

When using Visual C#®.NET: D0\nCN200\nD1

Upper 2 bytes Lower 2 bytes

Not used
D0
(0 is stored.)
H of CN200 L of CN200
Not used
D1
(0 is stored.)

Example 4: 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

D0
Not used
LL of FD0
(0 is stored.)
D1

*1 : Devices are stored from the lower bit in the order of device number.
*2 : For CN200 or later of FXCPU, 2 words are read for each point when reading devices randomly.

378
 CHAPTER 5 FUNCTIONS

Example 5: When 8-bit 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

D0
Not used EG0
(0 is stored.) (E0001) (E0000)
D1

Example 6: When monitor types (1, 2, and 5) of inverter are specified (Total number of points: 3 points)
5
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

Example 7: 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"

5.2.5 ReadDeviceRandom (Reading devices randomly)

5.2 Details of Functions (For ACT Control)
®.NET: 223.102.A\n223.103.B
When using Visual C++
® 223.102.A\n223.103.B
When using Visual C# .NET:

Upper 2 bytes Lower 2 bytes

H of 223.102.A L of 223.102.A
H of 223.102.B L of 223.102.B

(7) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

379
5.2.6 WriteDeviceRandom (Writing devices randomly)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Write devices randomly.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.WriteDeviceRandom(szDeviceList, lSize, lData(0))
Long lRet Returned value Output
String szDeviceList Device name Input
Long lSize Number of write points Input
Long lData(n) Device value to be written Input

(b) 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

(c) 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

(d) 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

(e) 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

380
 CHAPTER 5 FUNCTIONS

(f) 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

(4) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.WriteDeviceRandom( szDeviceList, lSize, *lplData,*lplRetCode )
HRESULT hResult Returned value of COM Output
5
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

(5) 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.

5.2.6 WriteDeviceRandom (Writing devices randomly)

5.2 Details of Functions (For ACT Control)
Example
When using Visual Basic®.NET ,VBA,VBScript: "D0" & vbLf & "D1" & vbLf & "D2"
®.NET: D0\nD1\nD2
When using Visual C++

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

(6) How to specify devices

The following describes how to specify devices.
Example 1: 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
(0 is stored.) D0
*1
M16 to M31 M0 to M15*1

*1 : Devices are stored from the lower bit in the order of device number.

381
 Example 2: 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

Example 3: When devices including FXCPU devices of CN200 and later are specified (Total number of points: 3
points)*2
When using Visual Basic®.NET ,VBA,VBScript: "D0" & vbLf & "CN200" & vbLf & "D1"
®.NET: D0\nCN200\nD1
When using Visual C++

When using Visual C#®.NET: D0\nCN200\nD1

Upper 2 bytes Lower 2 bytes

Not used
D0
(0 is stored.)
H of CN200 L of CN200
Not used
D1
(0 is stored.)

Example 4: 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

D0
Not used
LL of FD0
(0 is stored.)
D1

Example 5: When 8-bit 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

D0
Not used EG0
(0 is stored.) (E0001) (E0000)
D1

*2 : For CN200 or later of FXCPU, 2 words are written for each point when writing devices randomly.

382
 CHAPTER 5 FUNCTIONS

(7) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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

5.2.6 WriteDeviceRandom (Writing devices randomly)

5.2 Details of Functions (For ACT Control)

383
5.2.7 SetDevice (Setting device data)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Set one point of device.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.SetDevice(szDevice, lData)
Long lRet Returned value Output
String szDevice Device name Input
Long lData Set data Input

(b) Visual C++® .NET (MFC)

lRet = object.SetDevice(szDevice, lData)
Long lRet Returned value Output
CString szDevice Device name Input
Long lData Set data Input

(c) 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

(d) Visual Basic® .NET

IRet = object.SetDevice(szDevice, iData)
Integer IRet Returned value Output
String szDevice Device name Input
Integer iData Set data Input

(e) Visual C++® .NET

iRet = object.SetDevice(*szDevice, iData)
int iRet Returned value Output
String *szDevice Device name Input
int iData Set data Input

(f) Visual C#® .NET

iRet = object.SetDevice(szDevice, iData)
int iRet Returned value Output
String szDevice Device name Input
int iData Set data Input

384
 CHAPTER 5 FUNCTIONS

(4) Format (Custom interface)

(a) 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) 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. 5
(6) How to specify devices
The following describes how to specify devices.
<When bit device is specified> <When word device is specified>
Example: M0 Example: D0

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

Not used Not used
M0 D0
(0 is stored.) (0 is stored.)

<When double-word device is specified> <When double word device is specified(Digit specification)>
Example: LTN0 Example: K8M0

5.2.7 SetDevice (Setting device data)

5.2 Details of Functions (For ACT Control)
Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes
H of LTN0 L of LTN0 M16 to M31 *1
M0 to M15*1

<When CN200 or later 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
(0 is stored.) (E0001) (E0000)

*1 : Devices are stored from the lower bit in the order of device number.

(7) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

385
5.2.8 GetDevice (Acquiring device data)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.

(2) Feature
Acquire one point of device.
Acquire one point monitor type data of inverter/robot controller.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.GetDevice(szDevice, lData)
Long lRet Returned value Output
String szDevice Device name/monitor type Input
Long lData Acquired data Output

(b) 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

(c) 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

(d) 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

(e) Visual C++® .NET

iRet = object.GetDevice(*szDevice, *iplData)
int iRet Returned value Output
String *szDevice Device name/monitor type Input
int *ipIData Acquired data Output

(f) 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

386
 CHAPTER 5 FUNCTIONS

(4) Format (Custom interface)

(a) 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

(5) Description
One point of device data specified for szDevice (varDevice) is stored in lData (lplData, lpvarData, or iData).
5
For the items (monitor types) that can be monitored, refer to the following manual.
MX Component Version 4 Operating Manual

(6) How to specify devices

The following describes how to specify devices/monitor type.
<When bit device is specified> <When word device is specified>
Example: M0 Example: D0

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

Not used Not used
M0 D0
(0 is stored.) (0 is stored.)

<When double-word device is specified> <When double-word device is specified(Digit specification)>

5.2.8 GetDevice (Acquiring device data)

5.2 Details of Functions (For ACT Control)
Example: LTN0 Example: K8M0

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

H of LTN0 L of LTN0 M16 to M31 *1
M0 to M15*1

<When CN200 or later of FXCPU is specified> *1 : Devices are stored from the lower bit in the order of
Example: CN200 device number.

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
(0 is stored.) (E0001) (E0000)

<When monitor type of robot controller is specified>

<When monitor type of inverter is specified>
Format: (Request ID).(Data type).(Argument)
Example: 2 Example: 223.102.A

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

H of 1 L of 1 H of 223.102.A L of 223.102.A

387
 (7) Returned value
Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

388
 CHAPTER 5 FUNCTIONS

5.2.9 ReadBuffer (Reading data from buffer memory)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Applicable communication paths

The following table shows the applicable communication paths.
Property setting
Communication path Applicability
ActUnitType ActProtocolType
Connected module:
UNIT_RJ71C24 
R series-compatible C24
Connected module:
5
UNIT_QJ71C24 
Serial Q series-compatible C24
PROTOCOL_SERIAL
communication Connected module:
UNIT_LJ71C24 
L series-compatible C24
Connected module:
UNIT_FX485BD 
FX extended port
PROTOCOL_TCPIP,
UNIT_RJ71EN71
PROTOCOL_UDPIP
UNIT_RJ71EN71_DIRECT PROTOCOL_UDPIP
PROTOCOL_TCPIP,
UNIT_QJ71E71
PROTOCOL_UDPIP

PROTOCOL_TCPIP,
UNIT_LJ71E71
PROTOCOL_UDPIP
PROTOCOL_TCPIP,

5.2.9 ReadBuffer (Reading data from buffer memory)

5.2 Details of Functions (For ACT Control)
UNIT_RETHER
PROTOCOL_UDPIP
UNIT_RETHER_DIRECT PROTOCOL_UDPIP
UNIT_FXVETHER PROTOCOL_TCPIP

Ethernet communication 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_NZ2GF_ETB PROTOCOL_TCPIP
UNIT_NZ2GF_ETB,
PROTOCOL_UDPIP
UNIT_NZ2GF_ETB_DIRECT
UNIT_FXETHER PROTOCOL_TCPIP
UNIT_FXETHER_DIRECT PROTOCOL_UDPIP
Connection target CPU: FX5CPU UNIT_FXVCPU 
Connection target CPU:
UNIT_QNCPU 
QCPU (Q mode)
CPU COM
Connection target CPU: LCPU UNIT_LNCPU PROTOCOL_SERIAL 
communication
Connection target CPU:
UNIT_QNMOTION 
Q motion CPU
Connection target CPU: FXCPU UNIT_FXCPU *1
: Applicable, : Not applicable
*1 : When the CPU is other than FX1N, FX1NC, FX2N, FX2NC, FX3U, FX3UC, FX3G and FX3GC an error is returned.

389
 Property setting
Communication path Applicability
ActUnitType ActProtocolType
Connection target CPU: RCPU UNIT_RUSB 
Connection target CPU:
UNIT_QNUSB 
QCPU (Q mode)
USB Connection target CPU: LCPU UNIT_LNUSB 
PROTOCOL_USB
communication Connection target CPU: QSCPU UNIT_QSUSB 
Connection target CPU:
UNIT_QNMOTIONUSB 
Q motion CPU
Connection target CPU: FXCPU UNIT_FXCPU 
MELSECNET/H communication UNIT_MNETHBOARD PROTOCOL_MNETH
CC-Link IE Controller Network communication UNIT_MNETGBOARD PROTOCOL_MNETG
*2
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 – 
Connected module:
UNIT_QJ71C24 PROTOCOL_SERIALMODEM
Q series-compatible C24
Modem 
Connected module:
communication UNIT_LJ71C24 PROTOCOL_SERIALMODEM
L series-compatible C24
Connection target CPU: FXCPU UNIT_FXCPU PROTOCOL_TEL *1
Gateway function communication UNIT_A900GOT PROTOCOL_UDPIP 
UNIT_RJ71C24,
UNIT_QNCPU, 
UNIT_LNCPU
UNIT_FXCPU *1
UNIT_QJ71C24,
UNIT_LJ71C24,
UNIT_GOT_RJ71EN71,
UNIT_GOT_QJ71E71, PROTOCOL_SERIAL,
UNIT_GOT_LJ71E71, PROTOCOL_USBGOT
UNIT_GOT_RETHER,

GOT transparent function communication UNIT_GOT_QNETHER,
UNIT_GOT_LNETHER,
UNIT_A900GOT,
UNIT_GOT_NZ2GF_ETB,
UNIT_GOT_FXETHER,
UNIT_GOT_FXENET
UNIT_GOTETHER_RJ71C24,
UNIT_GOTETHER_QNCPU, 
UNIT_GOTETHER_LNCPU PROTOCOL_TCPIP
UNIT_GOTETHER_FXCPU *1
UNIT_GOTETHER_QBUS 
Q series bus communication UNIT_QBF PROTOCOL_QBF 
COMM_RS232C,
Inverter communication – 
COMM_USB
: Applicable, : Not applicable
*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.

390
 CHAPTER 5 FUNCTIONS

*3 : When the CPU is other than FX0N, FX1N, FX1NC, FX2, FX2C, FX2N, FX2NC, FX3U, FX3UC, FX3G and FX3GC an error is returned.

(3) Feature
Read data from the buffer memory of special function module.

(4) Format (Dispatch interface)

(a) VBA
lRet = object.ReadBuffer(lStartIO, lAddress, lReadSize, iData(0))
Long lRet Returned value Output
Start I/O number of module from
Long lStartIO Input
which values are read
Long lAddress Buffer memory address Input
Long lReadSize Read size Input 5
Integer iData(n) Values read from buffer memory Output

(b) Visual C++® .NET (MFC)

lRet = object.ReadBuffer(lStartIO, lAddress, lReadSize, *lpsData)
Long lRet Returned value Output
Start I/O number of module from
Long lStartIO Input
which values are read
Long lAddress Buffer memory address Input
Long lReadSize Read size Input
Short *lpsData Values read from buffer memory Output

(c) VBScript

5.2.9 ReadBuffer (Reading data from buffer memory)

5.2 Details of Functions (For ACT Control)
varRet = object.ReadBuffer(varStartIO, varAddress, varReadSize, lpvarData)
VARIANT varRet Returned value (LONG type) Output
Start I/O number of module from
VARIANT varStartIO Input
which values are read (LONG type)
VARIANT varAddress Buffer memory address (LONG type) Input
VARIANT varReadSize Read size (LONG type) Input
Values read from buffer memory
VARIANT lpvarData Output
(SHORT array type)

(d) Visual Basic® .NET

IRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, iData(0))
Integer lRet Returned value Output
Start I/O number of module from
Integer iStartIO Input
which values are read
Integer iAddress Buffer memory address Input
Integer iReadSize Read size Input
short iData(n) Values read from buffer memory Output

391
 (e) Visual C++® .NET
iRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, *ipsData)
int iRet Returned value Output
Start I/O number of module from
int iStartIO Input
which values are read
int iAddress Buffer memory address Input
int iReadSize Read size Input
short *ipsData Values read from buffer memory Output

(f) Visual C#® .NET

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

(5) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.ReadBuffer( lStartIO, lAddress, lReadSize, *lpsData, *lplRetCode )
HRESULT hResult Returned value of COM Output
Start I/O number of module from
LONG lStartIO Input
which values are 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

(6) 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.
• 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).

(7) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

392
 CHAPTER 5 FUNCTIONS

(8) Considerations for reading/writing data from/to buffer memory in multiple CPU
system configuration
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.
5

● 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 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.2.9 ReadBuffer (Reading data from buffer memory)

5.2 Details of Functions (For ACT Control)

393
5.2.10 WriteBuffer (Writing data to buffer memory)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Applicable communication paths

The following table shows the applicable communication paths.
Property setting
Communication path Applicability
ActUnitType ActProtocolType
Connected module:
UNIT_RJ71C24 
R series-compatible C24
Connected module:
UNIT_QJ71C24 
Serial Q series-compatible C24
PROTOCOL_SERIAL
communication Connected module:
UNIT_LJ71C24 
L series-compatible C24
Connected module:
UNIT_FX485BD 
FX extended port
PROTOCOL_TCPIP,
UNIT_RJ71EN71
PROTOCOL_UDPIP
UNIT_RJ71EN71_DIRECT PROTOCOL_UDPIP
PROTOCOL_TCPIP,
UNIT_QJ71E71
PROTOCOL_UDPIP

PROTOCOL_TCPIP,
UNIT_LJ71E71
PROTOCOL_UDPIP
PROTOCOL_TCPIP,
UNIT_RETHER
PROTOCOL_UDPIP
UNIT_RETHER_DIRECT PROTOCOL_UDPIP
UNIT_FXVETHER PROTOCOL_TCPIP

Ethernet communication 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_NZ2GF_ETB PROTOCOL_TCPIP
UNIT_NZ2GF_ETB,
PROTOCOL_UDPIP
UNIT_NZ2GF_ETB_DIRECT
UNIT_FXETHER PROTOCOL_TCPIP
UNIT_FXETHER_DIRECT PROTOCOL_UDPIP
Connection target CPU: FX5CPU UNIT_FXVCPU 
Connection target CPU:
UNIT_QNCPU 
QCPU (Q mode)
CPU COM
Connection target CPU: LCPU UNIT_LNCPU PROTOCOL_SERIAL 
communication
Connection target CPU:
UNIT_QNMOTION 
Q motion CPU
Connection target CPU: FXCPU UNIT_FXCPU *1
: Applicable, : Not applicable
*1 : When the CPU is other than FX1N, FX1NC, FX2N, FX2NC, FX3U, FX3UC, FX3G and FX3GC an error is returned.

394
 CHAPTER 5 FUNCTIONS

Property setting
Communication path Applicability
ActUnitType ActProtocolType
Connection target CPU: RCPU UNIT_RUSB 
Connection target CPU:
UNIT_QNUSB 
QCPU (Q mode)
USB Connection target CPU: LCPU UNIT_LNUSB 
PROTOCOL_USB
communication Connection target CPU: QSCPU UNIT_QSUSB *2
Connection target CPU:
UNIT_QNMOTIONUSB 
Q motion CPU
Connection target CPU: FXCPU UNIT_FXCPU 
MELSECNET/H communication UNIT_MNETHBOARD PROTOCOL_MNETH
CC-Link IE Controller Network communication UNIT_MNETGBOARD PROTOCOL_MNETG
*3
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 *4
GX Simulator2 communication UNIT_SIMULATOR2 
GX Simulator3 communication (RCPU) –
UNIT_SIMULATOR3 
GX Simulator3 communication (FX5CPU)
MT Simulator2 communication UNIT_SIMULATOR2 – 
Connected module:
UNIT_QJ71C24 PROTOCOL_SERIALMODEM
Q series-compatible C24
Modem 
Connected module:
communication UNIT_LJ71C24 PROTOCOL_SERIALMODEM
L series-compatible C24
Connection target CPU: FXCPU UNIT_FXCPU PROTOCOL_TEL *1
Gateway function communication UNIT_A900GOT PROTOCOL_UDPIP 
UNIT_RJ71C24,

5.2.10 WriteBuffer (Writing data to buffer memory)

5.2 Details of Functions (For ACT Control)
UNIT_QNCPU, 
UNIT_LNCPU
UNIT_FXCPU *1
UNIT_QJ71C24,
UNIT_LJ71C24,
UNIT_GOT_RJ71EN71
UNIT_GOT_QJ71E71, PROTOCOL_SERIAL,
UNIT_GOT_LJ71E71, PROTOCOL_USBGOT
UNIT_GOT_RETHER

GOT transparent function communication UNIT_GOT_QNETHER,
UNIT_GOT_LNETHER,
UNIT_A900GOT,
UNIT_GOT_NZ2GF_ETB,
UNIT_GOT_FXETHER,
UNIT_GOT_FXENET
UNIT_GOTETHER_RJ71C24,
UNIT_GOTETHER_QNCPU, 
UNIT_GOTETHER_LNCPU PROTOCOL_TCPIP
UNIT_GOTETHER_FXCPU *1
UNIT_GOTETHER_QBUS 
Q series bus communication UNIT_QBF PROTOCOL_QBF 
COMM_RS232C,
Inverter communication – 
COMM_USB
: Applicable, : Not applicable
*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.

395
*3 : An error is returned when the own board is accessed.
*4 : When the CPU is other than FX0N, FX1N, FX1NC, FX2, FX2C, FX2N, FX2NC, FX3U, FX3UC, FX3G and FX3GC an error is returned.

(3) Feature
Write data to the buffer memory of special function module.

(4) Format (Dispatch interface)

(a) VBA
lRet = object.WriteBuffer(lStartIO, lAddress, lWriteSize, iData(0))
Long lRet Returned value Output
Start I/O number of module to
Long lStartIO Input
which values are written
Long lAddress Buffer memory address Input
Long lWriteSize Write size Input
Integer iData(n) Values written from buffer memory Input

(b) Visual C++® .NET (MFC)

lRet = object.WriteBuffer(lStartIO, lAddress, lWriteSize, *lpsData)
Long lRet Returned value Output
Start I/O number of module to
Long lStartIO Input
which values are written
Long lAddress Buffer memory address Input
Long lWriteSize Write size Input
Short *lpsData Values written from buffer memory Input

(c) VBScript
varRet = object.WriteBuffer(varStartIO, varAddress, varWriteSize, varData)
VARIANT varRet Returned value (LONG type) Output
Start I/O number of module to
VARIANT varStartIO Input
which values are written (LONG type)
VARIANT varAddress Buffer memory address (LONG type) Input
VARIANT varWriteSize Write size (LONG type) Input
Values written from buffer memory
VARIANT varData Input
(SHORT array type)

(d) Visual Basic® .NET

IRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, iData(0))
Integer lRet Returned value Output
Start I/O number of module to
Integer iStartIO Input
which values are written
Integer iAddress Buffer memory address Input
Integer iWriteSize Write size Input
Short iData(n) Values written from buffer memory Input

396
 CHAPTER 5 FUNCTIONS

(e) Visual C++® .NET

iRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, *ipsData)
int iRet Returned value Output
Start I/O number of module to
int iStartIO Input
which values are written
int iAddress Buffer memory address Input
int iWriteSize Write size Input
Short *ipsData Values written from buffer memory Input

(f) Visual C#® .NET

iRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, ref sData(0))
int iRet Returned value Output
Start I/O number of module to 5
int iStartIO Input
which values are written
int iAddress Buffer memory address Input
int iWriteSize Write size Input
short[n] sData Values written from buffer memory Input

(5) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.WriteBuffer( lStartIO, lAddress, lWriteSize, *lpsData, *lplRetCode )
HRESULT hResult Returned value of COM Output
Start I/O number of module to
LONG lStartIO Input
where values are written

5.2.10 WriteBuffer (Writing data to buffer memory)

5.2 Details of Functions (For ACT Control)
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

(6) 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.
• 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 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).

(7) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

397
 (8) Considerations for reading/writing data from/to buffer memory in multiple CPU
system configuration
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).

398
 CHAPTER 5 FUNCTIONS

5.2.11 GetClockData (Reading clock data)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Applicable communication paths

The following table shows the applicable communication paths.
Property setting
Communication path Applicability
ActUnitType ActProtocolType
Connected module:
UNIT_RJ71C24 
R series-compatible C24
5
Connected module:
UNIT_QJ71C24 
Serial Q series-compatible C24
PROTOCOL_SERIAL
communication Connected module:
UNIT_LJ71C24 
L series-compatible C24
Connected module:
UNIT_FX485BD 
FX extended port
PROTOCOL_TCPIP,
UNIT_RJ71EN71
PROTOCOL_UDPIP
UNIT_RJ71EN71_DIRECT PROTOCOL_UDPIP
PROTOCOL_TCPIP,
UNIT_QJ71E71
PROTOCOL_UDPIP
PROTOCOL_TCPIP,
UNIT_LJ71E71
PROTOCOL_UDPIP

5.2.11 GetClockData (Reading clock data)

5.2 Details of Functions (For ACT Control)
PROTOCOL_TCPIP,
UNIT_RETHER
PROTOCOL_UDPIP
UNIT_RETHER_DIRECT PROTOCOL_UDPIP
UNIT_FXVETHER PROTOCOL_TCPIP
Ethernet communication 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_NZ2GF_ETB PROTOCOL_TCPIP
UNIT_NZ2GF_ETB,
PROTOCOL_UDPIP
UNIT_NZ2GF_ETB_DIRECT
UNIT_FXETHER PROTOCOL_TCPIP
UNIT_FXETHER_DIRECT PROTOCOL_UDPIP
Connection target CPU: FX5CPU UNIT_FXVCPU 
Connection target CPU:
UNIT_QNCPU 
QCPU (Q mode)
CPU COM
Connection target CPU: LCPU UNIT_LNCPU PROTOCOL_SERIAL 
communication
Connection target CPU:
UNIT_QNMOTION 
Q motion CPU
Connection target CPU: FXCPU UNIT_FXCPU 
: Applicable, : Not applicable

399
 Property setting
Communication path Applicability
ActUnitType ActProtocolType
Connection target CPU: RCPU UNIT_RUSB 
Connection target CPU:
UNIT_QNUSB 
QCPU (Q mode)
USB Connection target CPU: LCPU UNIT_LNUSB 
PROTOCOL_USB
communication Connection target CPU: QSCPU UNIT_QSUSB 
Connection target CPU:
UNIT_QNMOTIONUSB 
Q motion CPU
Connection target CPU: FXCPU UNIT_FXCPU 
MELSECNET/H communication UNIT_MNETHBOARD PROTOCOL_MNETH
CC-Link IE Controller Network communication UNIT_MNETGBOARD PROTOCOL_MNETG
*1
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 
GX Simulator2 communication UNIT_SIMULATOR2
GX Simulator3 communication (RCPU) – 
UNIT_SIMULATOR3
GX Simulator3 communication (FX5CPU)
MT Simulator2 communication UNIT_SIMULATOR2 – 
Connected module:
UNIT_QJ71C24 PROTOCOL_SERIALMODEM
Q series-compatible C24
Modem
Connected module: 
communication UNIT_LJ71C24 PROTOCOL_SERIALMODEM
L series-compatible C24
Connection target CPU: FXCPU UNIT_FXCPU PROTOCOL_TEL
Gateway function communication UNIT_A900GOT PROTOCOL_UDPIP 
UNIT_RJ71C24,
UNIT_QNCPU,
UNIT_LNCPU,
UNIT_FXCPU,
UNIT_QJ71C24,
UNIT_LJ71C24,
UNIT_GOT_RJ71EN71,
UNIT_GOT_QJ71E71, PROTOCOL_SERIAL,
UNIT_GOT_LJ71E71, PROTOCOL_USBGOT
UNIT_GOT_RETHER,
GOT transparent function communication UNIT_GOT_QNETHER, 
UNIT_GOT_LNETHER,
UNIT_A900GOT,
UNIT_GOT_NZ2GF_ETB,
UNIT_GOT_FXETHER,
UNIT_GOT_FXENET
UNIT_GOTETHER_RJ71C24,
UNIT_GOTETHER_QNCPU,
UNIT_GOTETHER_LNCPU, PROTOCOL_TCPIP
UNIT_GOTETHER_FXCPU,
UNIT_GOTETHER_QBUS
Q series bus communication UNIT_QBF PROTOCOL_QBF 
COMM_RS232C,
Inverter communication – 
COMM_USB
: Applicable, : Not applicable
*1 : An error is returned when the own board is accessed.

400
 CHAPTER 5 FUNCTIONS

(3) Feature
Read clock data from a programmable controller CPU.

(4) Format (Dispatch interface)

(a) 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(n) Read day-of-week value Output
5
Integer iHour Read hour value Output
Integer iMinute Read minute value Output
Integer iSecond Read second value Output

(b) 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

5.2.11 GetClockData (Reading clock data)

5.2 Details of Functions (For ACT Control)
Short *lpsMinute Read minute value Output
Short *lpsSecond Read second value Output

(c) 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

401
 (d) Visual Basic® .NET
IRet = object.GetClockData(iYear, iMonth, iDay, iDayOfWeek, iHour, iMinute, iSecond)
Integer lRet 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

(e) 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

(f) 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
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

402
 CHAPTER 5 FUNCTIONS

(5) Format (Custom interface)

(a) 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
SHORT
SHORT
*lpsMinute
*lpsSecond
Read minute value
Read second value
Output
Output
5
LONG *lplRetCode Returned value of communication function Output

(6) 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

5.2.11 GetClockData (Reading clock data)

5.2 Details of Functions (For ACT Control)
1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5 Friday
6 Saturday

(7) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

● If an R motion CPU or a Q motion CPU is accessed, an error is 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.

403
5.2.12 SetClockData (Writing clock data)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Applicable communication paths

The following table shows the applicable communication paths.
Property setting
Communication path Applicability
ActUnitType ActProtocolType
Connected module:
UNIT_RJ71C24 
R series-compatible C24
Connected module:
UNIT_QJ71C24 
Serial Q series-compatible C24
PROTOCOL_SERIAL
communication Connected module:
UNIT_LJ71C24 
L series-compatible C24
Connected module:
UNIT_FX485BD 
FX extended port
PROTOCOL_TCPIP,
UNIT_RJ71EN71
PROTOCOL_UDPIP
UNIT_RJ71EN71_DIRECT PROTOCOL_UDPIP
PROTOCOL_TCPIP,
UNIT_QJ71E71
PROTOCOL_UDPIP
PROTOCOL_TCPIP,
UNIT_LJ71E71
PROTOCOL_UDPIP
PROTOCOL_TCPIP,
UNIT_RETHER
PROTOCOL_UDPIP
UNIT_RETHER_DIRECT PROTOCOL_UDPIP
UNIT_FXVETHER PROTOCOL_TCPIP
Ethernet communication 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_NZ2GF_ETB PROTOCOL_TCPIP
UNIT_NZ2GF_ETB,
PROTOCOL_UDPIP
UNIT_NZ2GF_ETB_DIRECT
UNIT_FXETHER PROTOCOL_TCPIP
UNIT_FXETHER_DIRECT PROTOCOL_UDPIP
Connection target CPU: FX5CPU UNIT_FXVCPU 
Connection target CPU:
UNIT_QNCPU 
QCPU (Q mode)
CPU COM
Connection target CPU: LCPU UNIT_LNCPU PROTOCOL_SERIAL 
communication
Connection target CPU:
UNIT_QNMOTION 
Q motion CPU
Connection target CPU: FXCPU UNIT_FXCPU 
: Applicable, : Not applicable

404
 CHAPTER 5 FUNCTIONS

Property setting
Communication path Applicability
ActUnitType ActProtocolType
Connection target CPU: RCPU UNIT_RUSB 
Connection target CPU:
UNIT_QNUSB 
QCPU (Q mode)

USB Connection target CPU: LCPU UNIT_LNUSB 

PROTOCOL_USB
communication Connection target CPU: QSCPU UNIT_QSUSB *1
Connection target CPU:
UNIT_QNMOTIONUSB 
Q motion CPU
Connection target CPU: FXCPU UNIT_FXCPU 
MELSECNET/H communication UNIT_MNETHBOARD PROTOCOL_MNETH
CC-Link IE Controller Network communication UNIT_MNETGBOARD PROTOCOL_MNETG
*2
CC-Link IE Field Network communication UNIT_CCIEFBOARD PROTOCOL_CCIEF
CC-Link communication UNIT_CCLINKBOARD PROTOCOL_CCLINK 5
CC-Link G4 communication UNIT_G4QCPU PROTOCOL_SERIAL 
GX Simulator communication UNIT_SIMULATOR PROTOCOL_SHAREDMEMORY 
GX Simulator2 communication UNIT_SIMULATOR2
GX Simulator3 communication (RCPU) – 
UNIT_SIMULATOR3
GX Simulator3 communication (FX5CPU)
MT Simulator2 communication UNIT_SIMULATOR2 – 
Connected module:
UNIT_QJ71C24 PROTOCOL_SERIALMODEM
Q series-compatible C24
Modem
Connected module: 
communication UNIT_LJ71C24 PROTOCOL_SERIALMODEM
L series-compatible C24
Connection target CPU: FXCPU UNIT_FXCPU PROTOCOL_TEL
Gateway function communication UNIT_A900GOT PROTOCOL_UDPIP 

5.2.12 SetClockData (Writing clock data)

5.2 Details of Functions (For ACT Control)
UNIT_RJ71C24,
UNIT_QNCPU,
UNIT_LNCPU,
UNIT_FXCPU,
UNIT_QJ71C24,
UNIT_LJ71C24,
UNIT_GOT_RJ71EN71,
UNIT_GOT_QJ71E71, PROTOCOL_SERIAL,
UNIT_GOT_LJ71E71, PROTOCOL_USBGOT
UNIT_GOT_RETHER,
GOT transparent function communication UNIT_GOT_QNETHER, 
UNIT_GOT_LNETHER,
UNIT_A900GOT,
UNIT_GOT_NZ2GF_ETB,
UNIT_GOT_FXETHER,
UNIT_GOT_FXENET
UNIT_GOTETHER_RJ71C24,
UNIT_GOTETHER_QNCPU,
UNIT_GOTETHER_LNCPU, PROTOCOL_TCPIP
UNIT_GOTETHER_FXCPU,
UNIT_GOTETHER_QBUS
Q series bus communication UNIT_QBF PROTOCOL_QBF 
COMM_RS232C,
Inverter communication – 
COMM_USB
: Applicable, : Not applicable
*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.

405
 (3) Feature
Write clock data to a programmable controller CPU.

(4) Format (Dispatch interface)

(a) VBA
lRet = 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(n) 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

(b) 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

(c) 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

406
 CHAPTER 5 FUNCTIONS

(d) Visual Basic® .NET

IRet = object.SetClockData(iYear, iMonth, iDay, iDayOfWeek, iHour, iMinute, iSecond)
Integer lRet 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

(e) Visual C++® .NET

iRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond) 5
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

(f) Visual C#® .NET

IRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
int iRet Returned value Output

5.2.12 SetClockData (Writing clock data)

5.2 Details of Functions (For ACT Control)
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) Format (Custom interface)

(a) 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
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

407
 (6) 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

(7) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

● If an R motion CPU or a Q motion CPU is accessed, an error is 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.

408
 CHAPTER 5 FUNCTIONS

5.2.13 GetCpuType (Reading programmable controller CPU model)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.

(2) Feature
Read the model character string and the model code of programmable controller CPU, network board, and GOT.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.GetCpuType(szCpuName, lCpuType)
5
Long lRet Returned value Output
Programmable controller CPU model
String szCpuName Output
character string
Programmable controller CPU model
Long lCpuType Output
code

(b) Visual C++® .NET (MFC)

lRet = object.GetCpuType(*szCpuName, *lplCpuType)
Long lRet Returned value Output
Programmable controller CPU model
BSTR *szCpuName Output
character string
Programmable controller CPU model
Long *lplCpuType Output
code

5.2.13 GetCpuType (Reading programmable controller CPU model)

5.2 Details of Functions (For ACT Control)
(c) VBScript
varRet = object.GetCpuType(varCpuName, lpvarCpuCode)
VARIANT varRet Returned value (LONG type) Output
Programmable controller CPU model
VARIANT varCpuName Output
character string (character string type)
Programmable controller CPU model
VARIANT lpvarCpuCode Output
code (LONG type)

(d) Visual Basic® .NET

IRet = object.GetCpuType(szCpuName, ICpuType)
Integer IRet Returned value Output
Programmable controller CPU model
String szCpuName Output
character string
Programmable controller CPU model
Integer ICpuType Output
code

409
 (e) Visual C++® .NET
iRet = object.GetCpuType (**szCpuName, *iplCpuType)
int iRet Returned value Output
Programmable controller CPU model
String **szCpuName Output
character string
Programmable controller CPU model
int *iplCpuType Output
code

(f) Visual C#® .NET

iRet = object.GetCpuType (out szCpuName, out iCpuType)
int iRet Returned value Output
Programmable controller CPU model
String szCpuName Output
character string
Programmable controller CPU model
int iCpuType Output
code

(4) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.GetCpuType( *szCpuName, *lplCpuType, *lplRetCode )
HRESULT hResult Returned value of COM Output
Programmable controller CPU model character
BSTR *szCpuName Output
string
LONG *lplCpuType Programmable controller CPU model code Output
LONG *lplRetCode Returned value of communication function Output Output

(5) 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.

410
 CHAPTER 5 FUNCTIONS

(6) Model character string and model code of CPU

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/ Model character

network board/ When CPU/own board is connected When GX Simulator is connected
GOT strings code strings code
R04CPU R04CPU 4800H
R04ENCPU R04ENCPU 4805H
R08CPU R08CPU 4801H
R08PCPU R08PCPU 4841H
R08SFCPU R08SFCPU 4891H
5
R08ENCPU R08ENCPU 4806H
R16CPU R16CPU 4802H
R16PCPU R16PCPU 4842H
R16SFCPU R16SFCPU 4892H
R16ENCPU R16ENCPU 4807H
R32CPU R32CPU 4803H –
R32PCPU R32PCPU 4843H
R32SFCPU R34SFCPU 4893H
R32ENCPU R32ENCPU 4808H
R120CPU R120CPU 4804H
R120PCPU R120PCPU 4844H
R120SFCPU R120SFCPU 4894H

5.2.13 GetCpuType (Reading programmable controller CPU model)

5.2 Details of Functions (For ACT Control)
R120ENCPU R120ENCPU 4809H
R16MTCPU R16MTCPU 4C00H
R32MTCPU R32MTCPU 4C01H
R12CCPU-V R12CCPU-V 4820H
Q00JCPU Q00JCPU 250H Q00JCPU 250H
Q00UJCPU Q00UJCPU 260H Q00UJCPU 260H
Q00CPU Q00CPU 251H Q00CPU 251H
Q00UCPU Q00UCPU 261H Q00UCPU 261H
Q01CPU Q01CPU 252H Q01CPU 252H
Q01UCPU Q01UCPU 262H Q01UCPU 262H
Q02CPU Q02CPU Q02CPU
Q02HCPU Q02HCPU 41H Q02HCPU 41H
Q02PHCPU Q02PHCPU Q02PHCPU
Q02UCPU Q02UCPU 263H Q02UCPU 263H
Q03UDCPU Q03UDCPU Q03UDCPU
268H 268H
Q03UDECPU Q03UDECPU Q03UDECPU
Q03UDVCPU Q03UDVCPU 366H –
Q04UDHCPU Q04UDHCPU Q04UDHCPU
269H 269H
Q04UDEHCPU Q04UDEHCPU Q04UDEHCPU
Q04UDVCPU Q04UDVCPU 367H –
Q06HCPU Q06HCPU Q06HCPU
42H 42H
Q06PHCPU Q06PHCPU Q06PHCPU

411
 CPU/ Model character
network board/ When CPU/own board is connected When GX Simulator is connected
GOT strings code strings code
Q06UDHCPU Q06UDHCPU Q06UDHCPU
26AH 26AH
Q06UDEHCPU Q06UDEHCPU Q06UDEHCPU
Q06UDVCPU Q06UDVCPU 368H –
Q10UDHCPU Q10UDHCPU Q10UDHCPU
266H 266H
Q10UDEHCPU Q10UDEHCPU Q10UDEHCPU
Q12HCPU
Q12HCPU 43H Q12HCPU 43H
Q12PHCPU
Q12PRHCPU Q12PRHCPU 4BH Q12PRHCPU 4BH
Q13UDHCPU Q13UDHCPU Q13UDHCPU
26BH 26BH
Q13UDEHCPU Q13UDEHCPU Q13UDEHCPU
Q13UDVCPU Q13UDVCPU 36AH –
Q20UDHCPU Q20UDHCPU Q20UDHCPU
267H 267H
Q20UDEHCPU Q20UDEHCPU Q20UDEHCPU
Q25HCPU
Q25HCPU 44H Q25HCPU 44H
Q25PHCPU
Q25PRHCPU Q25PRHCPU 4CH Q25PRHCPU 4CH
Q26UDHCPU Q26UDHCPU Q26UDHCPU
26CH 26CH
Q26UDEHCPU Q26UDEHCPU Q26UDEHCPU
Q26UDVCPU Q26UDVCPU 36CH
Q50UDEHCPU Q50UDEHCPU 26DH –
Q100UDEHCPU Q100UDEHCPU 26EH
Q02CPU-A Q02CPU
141H Q02CPU-A 141H
Q02HCPU-A Q02HCPU
Q06HCPU-A Q06HCPU 142H Q06HCPU-A 142H
L02SCPU L02SCPU 543H
L02CPU L02CPU 541H
L06CPU L06CPU 544H
L26CPU L26CPU 545H
L26CPU-BT L26CPU-BT 542H
Q12DCCPU-V Q12DCCPU-V 2043H
Q24DHCCPU-V Q24DHCCPU-V 2044H
Q24DHCCPU-LS Q24DHCCPU-LS 2045H
Q24DHCCPU-VG Q24DHCCPU-VG 2046H
Q26DHCCPU-LS Q26DHCCPU-LS 2047H –
QS001CPU QS001CPU 230H
Q172CPU Q172CPU 2010H
Q172HCPU Q172HCPU 2012H
Q173CPU Q173CPU 2011H
Q173HCPU Q173HCPU 2013H
Q172DCPU Q172DCPU 2014H
Q173DCPU Q173DCPU 2015H
Q172DSCPU Q172DSCPU 2018H
Q173DSCPU Q173DSCPU 2019H
FX0
FX0/FX0S F0H FX0/FX0S F0H
FX0S

412
 CHAPTER 5 FUNCTIONS

CPU/ Model character

network board/ When CPU/own board is connected When GX Simulator is connected
GOT strings code strings code
FX0N FX0N 8EH FX0N 8EH
FX1 FX1 F1H FX1 F1H
FX1S FX1S F2H FX1S F2H
FX1N
FX1N 9EH FX1N 9EH
FX1NC
FXU
FXU/FX2C 8DH FXU/FX2C 8DH
FX2C
FX2N
FX2N/FX2NC 9DH FX2N/FX2NC 9DH
FX2NC
FX3S FX3S F5H –
FX3G
5
FX3G F4H FX3G F4H
FX3GC
FX3U
FX3UC F3H FX3UC F3H
FX3UC
FX5CPU FX5CPU 4A00H
Q80BD-J71LP21-25 Q80BD-J71LP21-25
Q80BD-J71LP21G Q80BD-J71LP21G
90H
Q80BD-J71BR11 Q80BD-J71BR11
–
Q81BD-J71GF11-T2 Q81BD-J71GF11-T2
GOT *1 E340H
A800 0xA8 A8H
CRnD-7xx/CR75x-D CRnD-7xx 03H
*1 : A product model number of GOT is displayed.

5.2.13 GetCpuType (Reading programmable controller CPU model)

5.2 Details of Functions (For ACT Control)
(7) Returned value
Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

413
5.2.14 SetCpuStatus (Remote control)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Applicable communication paths

The following table shows the applicable communication paths.
Property setting
Communication path Applicability
ActUnitType ActProtocolType
Connected module:
UNIT_RJ71C24 
R series-compatible C24
Connected module:
UNIT_QJ71C24 
Serial Q series-compatible C24
PROTOCOL_SERIAL
communication Connected module:
UNIT_LJ71C24 
L series-compatible C24
Connected module:
UNIT_FX485BD *1, *2
FX extended port
PROTOCOL_TCPIP,
UNIT_RJ71EN71
PROTOCOL_UDPIP
UNIT_RJ71EN71_DIRECT PROTOCOL_UDPIP
PROTOCOL_TCPIP,
UNIT_QJ71E71
PROTOCOL_UDPIP

PROTOCOL_TCPIP,
UNIT_LJ71E71
PROTOCOL_UDPIP
PROTOCOL_TCPIP,
UNIT_RETHER
PROTOCOL_UDPIP
UNIT_RETHER_DIRECT PROTOCOL_UDPIP
UNIT_FXVETHER PROTOCOL_TCPIP
*1
Ethernet communication 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_NZ2GF_ETB PROTOCOL_TCPIP
UNIT_NZ2GF_ETB
PROTOCOL_UDPIP
UNIT_NZ2GF_ETB_DIRECT
UNIT_FXETHER PROTOCOL_TCPIP
*1
UNIT_FXETHER_DIRECT PROTOCOL_UDPIP
Connection target CPU: FX5CPU UNIT_FXVCPU *1
Connection target CPU:
UNIT_QNCPU 
QCPU (Q mode)
CPU COM
Connection target CPU: LCPU UNIT_LNCPU PROTOCOL_SERIAL 
communication
Connection target CPU:
UNIT_QNMOTION 
Q motion CPU
Connection target CPU: FXCPU UNIT_FXCPU *1
: Applicable, : Not applicable
*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.

414
 CHAPTER 5 FUNCTIONS

Property setting
Communication path Applicability
ActUnitType ActProtocolType
Connection target CPU: RCPU UNIT_RUSB 
Connection target CPU:
UNIT_QNUSB 
QCPU (Q mode)

USB Connection target CPU: LCPU UNIT_LNUSB 

PROTOCOL_USB
communication Connection target CPU: QSCPU UNIT_QSUSB *3
Connection target CPU:
UNIT_QNMOTIONUSB 
Q motion CPU
Connection target CPU: FXCPU UNIT_FXCPU *1
MELSECNET/H communication UNIT_MNETHBOARD PROTOCOL_MNETH
CC-Link IE Controller Network communication UNIT_MNETGBOARD PROTOCOL_MNETG
*4
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 – 
Connected module:
UNIT_QJ71C24 PROTOCOL_SERIALMODEM
Q series-compatible C24
Modem 
Connected module:
communication UNIT_LJ71C24 PROTOCOL_SERIALMODEM
L series-compatible C24
Connection target CPU: FXCPU UNIT_FXCPU PROTOCOL_TEL *1
Gateway function communication UNIT_A900GOT PROTOCOL_UDPIP 
UNIT_RJ71C24,
UNIT_QNCPU, 

5.2.14 SetCpuStatus (Remote control)

5.2 Details of Functions (For ACT Control)
UNIT_LNCPU
UNIT_FXCPU *1
UNIT_QJ71C24,
UNIT_LJ71C24,
UNIT_GOT_RJ71EN71,
UNIT_GOT_QJ71E71, PROTOCOL_SERIAL,
UNIT_GOT_LJ71E71, PROTOCOL_USBGOT

UNIT_GOT_RETHER,
GOT transparent function communication UNIT_GOT_QNETHER,
UNIT_GOT_LNETHER,
UNIT_A900GOT,
UNIT_GOT_NZ2GF_ETB
UNIT_GOT_FXETHER,
*1
UNIT_GOT_FXENET
UNIT_GOTETHER_RJ71C24,
UNIT_GOTETHER_QNCPU, 
UNIT_GOTETHER_LNCPU PROTOCOL_TCPIP
UNIT_GOTETHER_FXCPU *1
UNIT_GOTETHER_QBUS 
Q series bus communication UNIT_QBF PROTOCOL_QBF 
COMM_RS232C,
Inverter communication – 
COMM_USB
: Applicable, : Not applicable
*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.

415
*4 : An error is returned when the own board is accessed.

(3) Feature
Perform a remote operation of programmable controller CPU.

(4) Format (Dispatch interface)

(a) VBA
lRet = object.SetCpuStatus(lOperation)
Long lRet Returned value Output
Long lOperation Remote RUN/STOP/PAUSE Input

(b) Visual C++® .NET (MFC)

lRet = object.SetCpuStatus(lOperation)
Long lRet Returned value Output
Long lOperation Remote RUN/STOP/PAUSE Input

(c) VBScript
varRet = object.SetCpuStatus(varOperation)
VARIANT varRet Returned value (LONG type) Output
VARIANT varOperation Remote RUN/STOP/PAUSE (LONG type) Input

(d) Visual Basic® .NET

IRet = object.SetCpuStatus(IOperation)
Integer lRet Returned value Output
Integer lOperation Remote RUN/STOP/PAUSE Input

(e) Visual C++® .NET

iRet = object.SetCpuStatus (iOperation)
int iRet Returned value Output
int iOperation Remote RUN/STOP/PAUSE Input

(f) Visual C#® .NET

iRet = object.SetCpuStatus (iOperation)
int iRet Returned value Output
int iOperation Remote RUN/STOP/PAUSE Input

(5) Format (Custom interface)

(a) 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 Output

416
 CHAPTER 5 FUNCTIONS

(6) 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

(7) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)
5

● 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.2.14 SetCpuStatus (Remote control)

5.2 Details of Functions (For ACT Control)

417
5.2.15 EntryDeviceStatus (Registering devices for status monitoring)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Register devices whose status to be monitored.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.EntryDeviceStatus(szDeviceList, lSize, lMonitorCycle, lData(0))
Long lRet Returned value Output
String szDeviceList Registered device name list Input
Long lSize Number of registered device points Input
Long lMonitorCycle Status monitoring time interval Input
Long lData(n) Registered device value list Input

(b) 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

(c) 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

(d) 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 lMonitorCycle Status monitoring time interval Input
Integer IData(n) Registered device value list Input

418
 CHAPTER 5 FUNCTIONS

(e) 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

(f) 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
5
int iMonitorCycle Status monitoring time interval Input
int[n] iData Registered device value list Input

(4) Format (Custom interface)

(a) 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

5.2.15 EntryDeviceStatus (Registering devices for status monitoring)

5.2 Details of Functions (For ACT Control)
LONG *lplData Registered device value list Input
LONG *lplRetCode Returned value of communication function Output

(5) 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).

419
 (6) How to specify devices
The following describes how to specify devices.
Example 1: 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
(0 is stored.) D0

M16 to M31*1 M0 to M15*1

Example 2: 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

Example 3: When devices including FXCPU devices of CN200 and later are specified (Total number of points: 3
points)*2
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
(0 is stored.)
H of CN200 L of CN200
Not used
D1
(0 is stored.)

Example 4: 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

D0
Not used
LL of FD0
(0 is stored.)
D1

*1 : Devices are stored from the lower bit in the order of device number.
*2 : For CN200 or later of FXCPU, 2 words are read for each point when reading devices randomly.

420
 CHAPTER 5 FUNCTIONS

Example 5: When 8-bit 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

D0
Not used EG0
(0 is stored.) (E0001) (E0000)
D1

5
(7) Returned value
Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

(8) 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

5.2.15 EntryDeviceStatus (Registering devices for status monitoring)

5.2 Details of Functions (For ACT Control)
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 587, Appendix 2 Programming Examples for Monitoring Word Device Status

421
 ● 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 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.

422
 CHAPTER 5 FUNCTIONS

5.2.16 FreeDeviceStatus (Deregistering devices for status monitoring)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Deregister devices that are registered using the EntryDeviceStatus function to monitor their status.

(3) Format (Dispatch interface)

(a) Visual C++® .NET (MFC), VBA 5

lRet = object.FreeDeviceStatus()
Long lRet Returned value Output

(b) VBScript
varRet = object.FreeDeviceStatus()
VARIANT varRet Returned value (LONG type) Output

(c) Visual Basic® .NET

IRet = object.FreeDeviceStatus()
Integer IRet Returned value Output

(d) Visual C++® .NET

5.2.16 FreeDeviceStatus (Deregistering devices for status monitoring)

5.2 Details of Functions (For ACT Control)
iRet = object.FreeDeviceStatus()
int iRet Returned value Output

(e) Visual C#® .NET

iRet = object.FreeDeviceStatus()
int iRet Returned value Output

(4) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.FreeDeviceStatus( *lplRetCode )
HRESULT hResult Returned value of COM Output
Returned value of
LONG *lplRetCode Output
communication function

(5) Description
The devices that are set using the EntryDeviceStatus function to monitor their status are deregistered.

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

423
5.2.17 OnDeviceStatus (Event notification)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Execute the event notification when the device condition registered using the EntryDeviceStatus function is
satisfied.

(3) Format (Dispatch interface)

(a) VBA
object.OnDeviceStatus(szDevice, lData, lReturnCode)
String szDevice Name of device whose condition is satisfied Input
Long lData Name of device whose condition is satisfied Input
Long lReturnCode Returned value of condition check processing Input

(b) Visual C++® .NET (MFC)

object.OnDeviceStatus(*szDevice, lData, lReturnCode)
LPCTSTR *szDevice Name of device whose condition is satisfied Input
Long lData Name of device whose condition is satisfied Input
Long lReturnCode Returned value of condition check processing Input

(c) VBScript
object.OnDeviceStatus(varDevice, varData, varReturnCode)
Name of device whose condition is satisfied
VARIANT varDevice Input
(BSTR type)
Name of device whose condition is satisfied
VARIANT varData Input
(LONG type)
Returned value of condition check processing
VARIANT varReturnCode Input
(LONG type)

(d) 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

424
 CHAPTER 5 FUNCTIONS

(e) 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

(f) Visual C#® .NET

private void object_OnDeviceStatus
(object sender,object._IActUtlTypeEvents_OnDeviceStatusEvent e) 5
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

(4) Format (Custom interface)

(a) Visual C++® .NET (MFC)

object.OnDeviceStatus(szDevice, lData, lReturnCode, *lplRetCode)

5.2.17 OnDeviceStatus (Event notification)

5.2 Details of Functions (For ACT Control)
LPCTSTR szDevice Name of device whose condition is satisfied Input
LONG lData Name of device whose condition is satisfied Input
LONG lReturnCode Returned value of condition check processing Input
LONG *lplRetCode Returned value of communication function Output

(5) 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"
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).

425
 (6) 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.
• User applications created using Visual Basic® or VBA (Excel)
The message box is displayed in the user application.
The InputBox/OutputBox is displayed in the user application.
• User applications created using Visual Basic® , Visual C++® , Visual C#® , 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 535, Section 6.4,
Page 543, Section 6.5)

426
 CHAPTER 5 FUNCTIONS

5.2.18 ReadDeviceBlock2 (Reading devices in bulk)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Read devices in 2-byte data unit in bulk.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.ReadDeviceBlock2(szDevice, lSize, iData(0))
5
Long lRet Returned value Output
String szDevice Device name Input
Long lSize Number of read points Input
Integer iData(n) Read device value Output

(b) 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

5.2.18 ReadDeviceBlock2 (Reading devices in bulk)

5.2 Details of Functions (For ACT Control)
(c) 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

(d) 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

(e) 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

427
 (f) 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

(4) Format (Custom interface)

(a) 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

(5) 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).

(6) How to specify devices

The following describes how to specify devices.
<When bit device is specified> <When word device is specified>
Example: Read 3 points (3 words) of data in 16-point unit
Example: Read 3 points of data starting from D0.
starting from M0.

2 Bytes 2 Bytes
M0 to M15*1 D0
D1
M16 to M31*1
D2
M32 to M47*1

<When double-word device is specified> <When FXCPU devices of CN200 and later are specified>
Example: Read 3 points from LTN0 Example: Read 6 points of data starting from CN200.*2

2 Bytes 2 Bytes
L of LTN0 L of CN200
L of LTN1 H of CN200
L of LTN2 L of CN201
H of CN201
L of CN202
H of CN202

*1 : Devices are stored from the lower bit in the order of device number.
*2 : For CN200 or later of FXCPU, 2 words are read for each 2 points. Reading only 1 point will result in an error.

428
 CHAPTER 5 FUNCTIONS

<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.)
5
2 Bytes
EG0
(E0001) (E0000)
EG1
(E0003) (E0002)
EG2
(E0005) (E0004)
EG3
(E0007) (E0006)

(7) Returned value

Normal termination : 0 is returned.

5.2.18 ReadDeviceBlock2 (Reading devices in bulk)

5.2 Details of Functions (For ACT Control)
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

429
5.2.19 WriteDeviceBlock2 (Writing devices in bulk)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Write devices in 2-byte data unit in bulk.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.WriteDeviceBlock2(szDevice, lSize, iData(0))
Long lRet Returned value Output
String szDevice Device name Input
Long lSize Number of write points Input
Integer iData(n) Device value to be written Input

(b) 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

(c) 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

(d) 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

(e) 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

430
 CHAPTER 5 FUNCTIONS

(f) 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

(4) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.WriteDeviceBlock2(szDevice, lSize, *lpsData, *lplRetCode )
HRESULT hResult Returned value of COM Output
5
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

(5) 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 lData (lpsData, varData, or sData), reserve arrays for more than the amount specified for lSize (varSize
or iSize).

5.2.19 WriteDeviceBlock2 (Writing devices in bulk)

5.2 Details of Functions (For ACT Control)
(6) How to specify devices
The following describes how to specify devices.
<When bit device is specified> <When word device is specified>
Example: Write 3 points (3 words) of data in 16-point unit
Example: Write 3 points of data starting from D0.
starting from M0.

2 bytes 2 bytes
M0 to M15*1 D0
D1
M16 to M31*1
D2
M32 to M47*1

<When double-word device is specified> <When FXCPU devices of CN200 and later are specified>
Example: Write 3 points to LTN0 Example: Write 6 points of data starting from CN200.*2

2 bytes 2 bytes
L of LTN0 L of CN200
L of LTN1 H of CN200
L of LTN2 L of CN201
H of CN201
L of CN202
H of CN202

*1 : Devices are stored from the lower bit in the order of device number.
*2 : For CN200 or later of FXCPU, 2 words are written for each 2 points. Writing only 1 point will result in an error.

431
 <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)
EG1
(E0003) (E0002)
EG2
(E0005) (E0004)
EG3
(E0007) (E0006)

(7) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

432
 CHAPTER 5 FUNCTIONS

5.2.20 ReadDeviceRandom2 (Reading devices randomly)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Read devices in 2-byte data unit randomly.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.ReadDeviceRandom2(szDeviceList, lSize, iData(0))
5
Long lRet Returned value Output
String szDeviceList Device name Input
Long lSize Number of read points Input
Integer iData(n) Read device value Output

(b) 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

5.2.20 ReadDeviceRandom2 (Reading devices randomly)

5.2 Details of Functions (For ACT Control)
(c) 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

(d) 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

(e) Visual C++® .NET

iRet = object.ReadDeviceRandom(*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

433
 (f) Visual C#® .NET
iRet = object.ReadDeviceRandom(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

(4) Format (Custom interface)

(a) 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

(5) 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.
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).

(6) How to specify devices

The following describes how to specify devices.
Example 1: 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

®.NET: M0\nD0\nK8M0
When using Visual C#

2 Bytes
*1
M0
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.

434
 CHAPTER 5 FUNCTIONS

Example 2: 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

Example 3: When devices including FXCPU devices of CN200 and later are specified (Total number of points: 3
points)*3
When using Visual Basic®.NET ,VBA,VBScript: "D0" & vbLf & "CN200" & vbLf & "D1"

When usingVisual C++ ®.NET: D0\nCN200\nD1

5
When using Visual C#®.NET: D0\nCN200\nD1

2 Bytes
D0

L of CN200*3
D1

*3 : For FXCPU devices of CN200 and later, 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.

Example 4: When devices including FD are specified (Total number of points: 3 points)
When using Visual Basic®.NET ,VBA,VBScript: "D0" & vbLf & "FD0" & vbLf & "D1"

5.2.20 ReadDeviceRandom2 (Reading devices randomly)

5.2 Details of Functions (For ACT Control)
When using Visual C++®.NET: D0\nFD0\nD1
® D0\nFD0\nD1
When using Visual C# .NET:

2 Bytes
D0
LL of FD0
D1

Example 5: When 8-bit 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"
® D0\nEG0\nD1
When using Visual C++ .NET:
®.NET: D0\nEG0\nD1
When using Visual C#

2 Bytes
D0
EG0
(E0001) (E0000)
D1

435
 (7) Returned value
Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

436
 CHAPTER 5 FUNCTIONS

5.2.21 WriteDeviceRandom2 (Writing devices randomly)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Write devices in 2-byte data unit randomly.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.WriteDeviceRandom2(szDeviceList, lSize, iData(0))
5
Long lRet Returned value Output
String szDeviceList Device name Input
Long lSize Number of write points Input
Integer iData(n) Device value to be written Input

(b) 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

5.2.21 WriteDeviceRandom2 (Writing devices randomly)

5.2 Details of Functions (For ACT Control)
(c) 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

(d) 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

(e) Visual C++® .NET

iRet = object.WriteDeviceRandom2(*szDeviceList, iSize, *ipsData)
int iRet Returned value Output
String *szDeviceList Device name Input
int iSize Number of write points Input
short *ipsData Device value to be written Input

437
 (f) 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

(4) Format (Custom interface)

(a) 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

(5) 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 lData (lpsData, varData, or sData), reserve arrays for more than the amount specified for lSize (varSize
or iSize).

(6) How to specify devices

The following describes how to specify devices.
Example 1: 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

®.NET: M0\nD0\nK8M0
When using Visual C#

2 Bytes
*1
M0
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.

438
 CHAPTER 5 FUNCTIONS

Example 2: 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

Example 3: When devices including FXCPU devices of CN200 and later are specified (Total number of points: 3
points)*3
When using Visual Basic®.NET ,VBA,VBScript: "D0" & vbLf & "CN200" & vbLf & "D1"

When using Visual C++ ®.NET: D0\nCN200\nD1

5
When using Visual C#®.NET: D0\nCN200\nD1

2 Bytes
D0

L of CN200*3
D1

*3 : For FXCPU devices of CN200 and later, data are 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.

Example 4: When devices including FD are specified (Total number of points: 3 points)
When using Visual Basic®.NET ,VBA,VBScript: "D0" & vbLf & "FD0" & vbLf & "D1"
®.NET: D0\nFD0\nD1
When using Visual C++

5.2.21 WriteDeviceRandom2 (Writing devices randomly)

5.2 Details of Functions (For ACT Control)
® D0\nFD0\nD1
When using Visual C# .NET:

2 Bytes
D0
LL of FD0
D1

Example 5: When 8-bit 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

439
 (7) Returned value
Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

440
 CHAPTER 5 FUNCTIONS

5.2.22 SetDevice2 (Setting device data)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Set one point of device in 2-byte data unit.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.SetDevice2(szDevice, iData)
5
Long lRet Returned value Output
String szDevice Device name Input
Integer iData Set data Input

(b) Visual C++® .NET (MFC)

lRet = object.SetDevice2(szDevice, sData)
Long lRet Returned value Output
CString szDevice Device name Input
Short sData Set data Input

(c) VBScript
varRet = object.SetDevice2(varDevice, varData)

5.2.22 SetDevice2 (Setting device data)

5.2 Details of Functions (For ACT Control)
VARIANT varRet Returned value (LONG type) Output
VARIANT varDevice Device name (character string type) Input
VARIANT varData Set data (SHORT type) Input

(d) Visual Basic® .NET

IRet = object.SetDevice2(szDevice, sData)
Integer IRet Returned value Output
String szDevice Device name Input
short sData Set data Input

(e) Visual C++® .NET

iRet = object.SetDevice2(*szDevice, sData)
int iRet Returned value Output
String *szDevice Device name Input
short sData Set data Input

(f) Visual C#® .NET

iRet = object.SetDevice2(szDevice, sData)
int iRet Returned value Output
String szDevice Device name Input
short sData Set data Input

441
 (4) Format (Custom interface)

(a) 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) 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.

(6) How to specify devices

The following describes how to specify devices.
<When bit device is specified> <When word device is specified>
Example: M0 Example: D0

2 Bytes 2 Bytes
M0*1 D0

<When double-word device is specified> <When double-word device is specified(Digit specification)>

Example: LTN0 Example: K8M0

2 Bytes 2 Bytes
L of LTN0 M0 to M15*2

<When CN200 or later of FXCPU is specified>

Example: CN200

2 Bytes
L of CN200*3

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

*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.
*3 : For FXCPU devices of CN200 and later, 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.

442
 CHAPTER 5 FUNCTIONS

(7) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.2.22 SetDevice2 (Setting device data)

5.2 Details of Functions (For ACT Control)

443
5.2.23 GetDevice2 (Acquiring device data)

(1) Applicable controls

Applicable to the Act(ML)ProgType control and the Act(ML)UtlType control.*1
*1 : Not applicable to inverter communication/robot controller communication.

(2) Feature
Acquire one point of device in 2-byte data unit.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.GetDevice2(szDevice, iData)
Long lRet Returned value Output
String szDevice Device name Input
Integer iData Acquired data Output

(b) Visual C++® .NET (MFC)

lRet = object.GetDevice2(szDevice, lSize, *lpsData)
Long lRet Returned value Output
CString szDevice Device name Input
Short *lpsData Acquired data Output

(c) 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

(d) Visual Basic® .NET

IRet = object.GetDevice2(szDevice, sData)
Integer IRet Returned value Output
String szDevice Device name Input
short sData Acquired data Output

(e) Visual C++® .NET

iRet = object.GetDevice(*szDevice, *ipsData)
int iRet Returned value Output
String *szDevice Device name Input
short *spsData Acquired data Output

(f) Visual C#® .NET

iRet = object.GetDevice2(szDevice, out sData)
int iRet Returned value Output
String szDevice Device name Input
short sData Acquired data Output

444
 CHAPTER 5 FUNCTIONS

(4) Format (Custom interface)

(a) 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

(5) Description
One point of device data specified for szDevice (varDevice) is stored in iData (lpsData, lpvarData, or sData).
5
(6) How to specify devices
The following describes how to specify devices.
<When bit device is specified> <When word device is specified>
Example: M0 Example: D0

2 Bytes 2 Bytes
*1
M0 D0

<When double-word device is specified> <When double-word device is specified (Digit specification)>
Example: LTN0 Example: K8M0

2 Bytes 2 Bytes

5.2.23 GetDevice2 (Acquiring device data)

5.2 Details of Functions (For ACT Control)
L of LTN0 M0 to M15*2

<When CN200 or later of FXCPU is specified>

Example: CN200

2 Bytes
L of CN200*3

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

*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.
*3 : For FXCPU devices of CN200 and later, 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.

445
 (7) Returned value
Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

446
 CHAPTER 5 FUNCTIONS

5.2.24 Connect (Connecting telephone line)

(1) Applicable controls

Applicable to the ActProgType control and the ActUtlType control.*1
*1 : Applicable to the modem communication only.

(2) Feature
Connect the telephone line.

(3) Format (Dispatch interface)

(a) Visual C++® .NET (MFC) , VBA 5

lRet = object.Connect()
Long lRet Returned value Output

(b) Visual Basic® .NET

IRet = object.Connect()
Integer IRet Returned value Output

(c) Visual C++® .NET

iRet = object.Connect()
int iRet Returned value Output

(d) Visual C#® .NET

5.2.24 Connect (Connecting telephone line)

5.2 Details of Functions (For ACT Control)
iRet = object.Connect()
int iRet Returned value Output

(4) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.Connect( *lplRetCode )
HRESULT hResult Returned value of COM Output
LONG *lplRetCode Returned value of communication function Output

(5) 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.

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

447
 (7) 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.

(8) 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.
Connection system of control which executed the Connect function second or Later
Auto line connect Callback connect Callback request
Connection system of
Auto line connect (Callback (Fixation) (Fixation) Callback
control which executed the
fixation) Callback connect Callback request reception
Connect function first
Auto line connect (Callback (Number (Number waiting
number specification) specification) 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    

: Normal termination : Abnormal termination (Error occurrence)

448
 CHAPTER 5 FUNCTIONS

5.2.25 Disconnect (Disconnecting telephone line)

(1) Applicable controls

Applicable to the ActProgType control and the ActUtlType control.*1
*1 : Applicable to the modem communication only.

(2) Feature
Disconnect the telephone line.

(3) Format (Dispatch interface)

(a) Visual C++® .NET (MFC) 5

lRet = object.Disconnect()
Long lRet Returned value Output

(b) Visual Basic® .NET

IRet = object.Disconnect()
Integer IRet Returned value Output

(c) Visual C++® .NET

iRet = object.Disconnect()
int iRet Returned value Output

(d) Visual C#® .NET

5.2.25 Disconnect (Disconnecting telephone line)

5.2 Details of Functions (For ACT Control)
iRet = object.Disconnect()
int iRet Returned value Output

(4) Format (Custom interface)

(a) Visual C++® .NET (MFC)

hResult = object.Disconnect( *lplRetCode )
HRESULT hResult Returned value of COM Output
LONG *lplRetCode Returned value of communication function Output

(5) Description
The telephone line that was connected using the Connect function is disconnected.

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

449
 (7) 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 start Connection 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

the ReadDeviceBlock function Telephone line is connected.
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.

450
 CHAPTER 5 FUNCTIONS

5.2.26 GetErrorMessage (Receiving error message)

(1) Applicable control

Applicable to the Act(ML)SupportMsg control.*1
*1 : Not applicable to inverter communication.

(2) Feature
Receive the error description and its corrective action corresponding to the error code.

(3) Format (Dispatch interface)

(a) VBA
lRet = object.GetErrorMessage(lErrorCode, szErrorMessage)
5
Long lRet Returned value Output
String lErrorCode Error code Input
String szErrorMessage Error message Output

(b) Visual C++® .NET (MFC)

lRet = object.GetErrorMessage(lErrorCode, *lpszErrorMessage)
Long lRet Returned value Output
Long lErrorCode Error code Input
BSTR *lpszErrorMessage Error message Output

(c) VBScript
varRet = object.GetErrorMessage(varErrorCode, lpvarErrorMessage)

5.2.26 GetErrorMessage (Receiving error message)

5.2 Details of Functions (For ACT Control)
VARIANT varRet Returned value (LONG type) Output
VARIANT varErrorCode Error code (LONG type) Input
VARIANT lpvarErrorMessage Error message (character string type) Output

(d) Visual Basic® .NET

IRet = object.GetErrorMessage(IErrorCode, szErrorMessage)
Integer IRet Returned value Output
Integer IErrorCode Error code Input
String szErrorMessage Error message Output

(e) Visual C++® .NET

iRet = object.GetErrorMessage(iErrorCode, **lpsErrorMessage)
int iRet Returned value Output
int iErrorCode Error code Input
String **lpsErrorMessage Error message Output

(f) Visual C#® .NET

iRet = object.GetErrorMessage(iErrorCode, out szErrorMessage)
int iRet Returned value Output
int iErrorCode Error code Input
String szErrorMessage Error message Output

451
 (4) Format (Custom interface)

(a) 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) 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,
lpsErrorMessage, or lpvarErrorMessage).

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

452
 CHAPTER 5 FUNCTIONS

5.3 Details of Functions (For .NET Control)

5.3.1 Open (Opening communication line)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Open the communication line.

(3) Format 5
(a) Visual Basic® .NET
IRet = object.Open()
Integer IRet Returned value Output

(b) Visual C++® .NET

iRet = object.Open()
int iRet Returned value Output

(c) Visual C#® .NET

iRet = object.Open()
int iRet Returned value Output

5.3.1 Open (Opening communication line)

5.3 Details of Functions (For .NET Control)
(4) Description
Lines are connected according to the set value of the Open function property.

(5) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

453
5.3.2 Close (Closing communication line)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Close the communication line.

(3) Format

(a) Visual Basic® .NET

IRet = object.Close()
Integer IRet Returned value Output

(b) Visual C++® .NET

iRet = object.Close()
int iRet Returned value Output

(c) Visual C#® .NET

iRet = object.Open()
int iRet Returned value Output

(4) Description
The line connected using the Open function is closed.

(5) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

454
 CHAPTER 5 FUNCTIONS

5.3.3 ReadDeviceBlock (Reading devices in bulk)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Read devices in bulk.

(3) Format

(a) Visual Basic® .NET

IRet = object.ReadDeviceBlock(szLabel, iSize, iData) 5
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of read points Input
Integer iData(n) Read device values Output

(b) 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 values Output

5.3.3 ReadDeviceBlock (Reading devices in bulk)

5.3 Details of Functions (For .NET Control)
(c) 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 values Output

(4) 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.

455
 (5) How to specify devices
The following describes how to specify label names and device values to be read.
• The following data type can be specified for label name.
Type class Label data type Label name format
Label name
Bit, Word, Double Word,
Float (Single Precision), Float (Double Precision),
Array Label name [number of elements]
Member String*1, String (Unicode)*1, Time, Timer, Long timer,
Label name [n1] [n2] [n3]
Counter, Long counter,
Retentive Timer, Long retentive timer

*1 : The maximum number of characters that can be specified is 32 + NULL

• Set the following values for the number of read points according to the label data type.
Number of
Label (array) data type Number of read points to be specified
applicable words
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, 1 Number of label array elements
Retentive Timer, Long retentive timer

• The read device values are stored as follows.

<When bit device is specified> <When word device is specified>
Example: Read 3 points of data (3 words = 48 bits) from Example: Read 3 points of data from the devices starting
the devices starting from M0. from D0.
• Label setting (Data type: Bit, Number of array elements: • Label setting (Data type: Word, Number of array
48) elements: 3)

Data type Device Data type Device

Bit (0..47) M0 Word (0..2) D0
• Number of read points: 3 • Number of read points: 3
• Read device values • Read device values
Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes
*2
M0 to M15 D0
Not used *2
Not used
M16 to M31 D1
(0 is stored.) (0 is stored.)
M32 to M47 *2 D2

*2 : Devices are stored from the lower bit in the order of

device number.

456
 CHAPTER 5 FUNCTIONS

<When FXCPU devices of CN200 and later are specified> <When FD device is specified (4-word device)>
Example: Read 6 points of data from the devices starting Example: Read 8 points of data from the devices starting
from CN200.*3 from FD0.
• Label setting (Data type: Double Word, Number of array • Label setting (Data type: Double Word, Number of array
elements: 3) elements: 2)

Data type Device Data type Device

Double Word (0..2) CN200 Double Word (0..1) FD0

• Number of read points: 6 • Number of read points: 8

• Read device values • Read device values

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

L of CN200 LL of FD0
H of CN200 LH of FD0
Not used L of CN201 HL of FD0 5
(0 is stored.) H of CN201 HH of FD0
Not used
L of CN202 (0 is stored.) LL of FD1
H of CN202 LH of FD1

*3 : For FXCPU devices of CN200 and later, 2 points of HL of FD1

data are read from each 1 point of device (upper (H) HH of FD1
and lower (L) data).
Reading only 1 point of data will result in an error.

<When label is Double Word array and word device is <When long timer, long counter, or long retentive timer
specified> type is specified>
Example: Read 6 points of data from the devices starting Example: Read 3 points of data from the devices starting
from D100. from LT0.
• Label setting (Data type: Double Word, Number of array • Label setting (Data type: Long timer, Number of array
elements: 3) elements: 3)

5.3.3 ReadDeviceBlock (Reading devices in bulk)

5.3 Details of Functions (For .NET Control)
Data type Device Data type Device
Double Word (0..2) D100 Long timer (0..2) LT0

• Number of read points: 6 • Number of read points: 3

• Read device values • Read device values

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

D100 H of LT0 L of LT0
D101 H of LT1 L of LT1
Not used D102 H of LT2 L of LT2
(0 is stored.) D103
D104
D105

457
 (6) Returned value
Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

458
 CHAPTER 5 FUNCTIONS

5.3.4 WriteDeviceBlock (Writing devices in bulk)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Write devices in bulk.

(3) Format

(a) Visual Basic® .NET

Ret = object.WriteDeviceBlock(szLabel, iSize, iData)
5
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of write points Input
Integer iData(n) Device values to be written Input

(b) 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 values to be written Input

(c) Visual C#® .NET

5.3.4 WriteDeviceBlock (Writing devices in bulk)

5.3 Details of Functions (For .NET Control)
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 values to be written Input

(4) 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) How to specify devices

The following describes how to specify label names and device values to be written.
• The following data type can be specified for label name.
Type class Label data type Label name format
Label name
Bit, Word, Double Word,
Float (Single Precision), Float (Double Precision),
Array Label name [number of elements]
Member String*1, String (Unicode)*1, Time, Timer, Long timer,
Label name [n1] [n2] [n3]
Counter, Long counter,
Retentive Timer, Long retentive timer

*1 : The maximum number of characters that can be specified is 32 + NULL

459
 • Set the following values for the number of write points according to the label data type.
Number of
Label (array) data type Number of read points to be specified
applicable words
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 1 Number of label array elements
retentive timer

• Set the device values to be written as follows.

<When bit device is specified> <When word device is specified>
Example: Write 3 points of data (3 words = 48 bits) to the Example: Write 3 points of data to the devices starting
devices starting from M0. from D0.
• Label setting (Data type: Bit, Number of array elements: 48) • Label setting (Data type: Word, Number of array
elements: 3)
Data type Device
Bit (0..47) M0 Data type Device
Word (0..2) D0
• Number of write points: 3
• Device values to be written
• Number of write points: 3
Upper 2 bytes Lower 2 bytes • Device values to be written

M0 to M15*2 Upper 2 bytes Lower 2 bytes

D0
Not used M16 to M31*2
Not used D1
M32 to M47*2
D2
*2 : Devices are stored from the lower bit in the order of
device number.

<When FXCPU devices of CN200 and later are specified> <When FD device is specified (4-word device)>
Example: Write 6 points of data to the devices starting Example: Write 8 points of data to the devices starting
from CN200.*3 from FD0.
• Label setting (Data type: Double Word, Number of array • Label setting (Data type: Double Word, Number of array
elements: 3) elements: 2)

Data type Device Data type Device

Double Word (0..2) CN200 Double Word (0..1) FD0

• Number of write points: 6 • Number of write points: 8

• Device values to be written • Device values to be written

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

L of CN200 LL of FD0
H of CN200 LH of FD0
L of CN201 HL of FD0
Not used
H of CN201 HH of FD0
Not used
L of CN202 LL of FD1
H of CN202 LH of FD1

*3 : For FXCPU devices of CN200 and later, 2 points of HL of FD1

data are written to each 1 point of device (upper (H) HH of FD1
and lower (L) data).
Writing only 1 point of data will result in an error.

460
 CHAPTER 5 FUNCTIONS

<When label is Double Word array and word device is <When long timer, long counter, or long retentive timer
specified> type is specified>
Example: Write 3 points of data from the devices starting
Example: Write 6 points of data to the devices starting
from LT0.
from D100.
• Label setting (Data type: Long timer, Number of array
• Label setting (Data type: Double Word, Number of array
elements: 3)
elements: 3)
Data type Device
Data type Device
Long timer (0..2) LT0
Double Word (0..2) D100
• Number of write points: 3
• Number of write points: 6
• Device values to be written
• Device values to be written
Upper 2 bytes Lower 2 bytes
Upper 2 bytes Lower 2 bytes
H of LT0 L of LT0
D100
D101
H of LT1 L of LT1 5
H of LT2 L of LT2
D102
Not used
D103
D104
D105

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

● The maximum number of write points should be the value which satisfies the following condition.

5.3.4 WriteDeviceBlock (Writing devices in bulk)

5.3 Details of Functions (For .NET Control)
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.
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.

461
5.3.5 ReadDeviceRandom (Reading devices randomly)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Read devices randomly.

(3) Format

(a) 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 values Output

IRet = object.ReadDeviceRandom(szLabelList, iSize, iData)

Integer IRet Returned value Output
String szLabelList(n) Label list Input
Integer iSize Number of read points Input
Integer iData(n) Read device values Output

(b) 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 values Output

iRet = object.ReadDeviceRandom(szLabelList, iSize, iData)

Int iRet Returned value Output
<System::String^>^ szLabelList Label list Input
int iSize Number of read points Input
array<int>^ iData Read device values Output

(c) 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 values 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 values Output

462
 CHAPTER 5 FUNCTIONS

(4) 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) How to specify devices

The following describes how to specify label names and device values to be read.
• The following data type can be specified for label name.
Type class Label data type Label name format
Bit, Word, Double Word,
Float (Single Precision),

Basic type
Float (Double Precision),
String*1, String (Unicode)*1, Time, Label name
5
Timer, Long timer,
Counter, Long counter,
Retentive Timer, Long retentive timer
Label name
(The label data type can be specified
Array Label name [number of elements]
Member in the same manner as the basic
Label name [n1] [n2] [n3]
type.)
Label name
(The label data type can be specified
Structure
Member in the same manner as the basic Label name.Member name
type.)
Label name [number of elements]
Structured (The label data type can be specified Label name [number of elements].Member

5.3.5 ReadDeviceRandom (Reading devices randomly)

5.3 Details of Functions (For .NET Control)
array Member in the same manner as the basic name
type.) Label name [n1] [n2] [n3].Element

*1 : The maximum number of characters that can be specified is 32 + NULL.

• For the number of read points, specify the sum of the following values correspond to the elements according
to the label data type.
Number of
Label data type Number of read points to be specified
applicable words
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, 1 Number of label elements
Retentive Timer, Long retentive timer

463
 • 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 Lower 2 Applicable

bytes bytes label
*1 LABEL1
Not used M0
(0 is stored.) D0 LABEL2

*1 : The device to be read is 1 point of "M0", and "0" or

"1" is stored for the device value.
<When FXCPU devices of CN200 and later are specified> <When FD device is specified (4-word device)>
Example: Read 3 points of data from the devices including Example: Read 3 points of data from the devices including
CN200.*2 FD0.
• Label setting • Label setting

szLabelList Data type Device szLabelList Data type Device

[0] LABEL1 Word D0 [0] LABEL1 Word D0
[1] LABEL2 Double Word CN200 [1] LABEL2 Double Word FD0
[2] LABEL3 Word D1 [2] LABEL3 Word D1

• Number of read points: 3 • Number of read points: 3

• Read device values • Read device values

Upper 2 Lower 2 Applicable Upper 2 Lower 2 Applicable

bytes bytes label bytes bytes label
Not used D0 LABEL1
D0 LABEL1 Not used
(0 is stored.) LL of FD0*3 LABEL2
(0 is stored.)
H of CN200 L of CN200 LABEL2 D1 LABEL3
Not used
D1 LABEL3 *3 : Only lower 2 bytes are read. Data are not read from
(0 is stored.)
the specified devices HH, HL, and LH (upper 6
*2 : For FXCPU devices of CN200 and later, 4 bytes are bytes).
read as 1 read point.

464
 CHAPTER 5 FUNCTIONS

<When data type equivalent to 2 words or more is

<When array type label is specified>
specified for label>
Example: Read data by specifying labels of Double Word, Example: Read data from the devices by specifying array
*4 type labels.
Float (Single Precision), Float (Double Precision), String ,
and Time types. • Label setting
• Label setting
szLabelList Data type Device
szLabelList Data type Device [0] LABEL1 Bit (0..1) M0
[0] LABEL1 Double Word D0 [1] LABEL2 Double Word (0..1) CN200
Float (Single [2] LABEL3 Double Word (0..1) D0
[1] LABEL2 D100
Precision)
• Number of read points: 8
Float (Double
[2] LABEL3 D200 • Read device values
Precision)
[3] LABEL4 String D300 Upper 2 Lower 2 Applicable
[4] LABEL5 Time D400
bytes bytes label 5
Not used M0 LABEL1[0]
• Number of read points: 27
(0 is stored.) M1 LABEL1[1]
• Read device values
H of CN200 L of CN200 LABEL2[0]
Upper 2 Lower 2 Applicable
H of CN201 L of CN201 LABEL2[1]
bytes bytes label
D100
D0 LABEL3[0]
LABEL1 Not used D101
D1
(0 is stored.) D102
D100 LABEL3[1]
LABEL2 D103
D101
D200
D201
Not used LABEL3
D202
(0 is stored.)
D203

5.3.5 ReadDeviceRandom (Reading devices randomly)

5.3 Details of Functions (For .NET Control)
D300
: LABEL4
D316*4
D400
LABEL5
D401

*4 : 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 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 Lower 2 Applicable

bytes bytes label
H of LT0 D0 LABEL[1]
H of LT1 L of CN200 LABEL[2]
H of LT2 D1 LABEL[3]

465
 <When labels with combined structure and label are
<When structure type labels are specified>
specified>
Example: Read data from the devices by specifying Example: Read data from the devices by specifying
structure type labels. structure type array and structure array type label.
• Structure setting • Structure setting

Structure Label Structure Label

Data type Data type
name name name name
L1 Bit L1 Bit
STRUCT STRUCT1
L2 Double Word L2 Word

• Label setting L1 Bit (0..2)

STRUCT2
L2 Double Word
Data Label
szLabelList Device • Label setting
type name
L1 D0.0 Data Label
[0] LABEL1 STRUCT szLabelList Device
L2 D0 type name
L1 M10 STRUCT1 L1 X0
[1] LABEL2 STRUCT [0] LABEL1
L2 CN200 (0..1) L2 D0
• Number of read points: 6 L1 M0
[1] LABEL2 STRUCT2
• Read device values L2 D100

Upper 2 Lower 2 Applicable • Number of read points: 9

bytes bytes label • Read device values

D0.0 LABEL1.L1
Upper 2 Lower 2 Applicable
Not used D0 bytes bytes label
LABEL1.L2
(0 is stored.) D1 X0 LABEL1[0].L1
M0 LABEL2.L1 D0 LABEL1[0].L2
H of CN200 L of CN200 X1 LABEL1[1].L1
LABEL2.L2
H of CN201 L of CN201*5 D1 LABEL1[1].L2
Not used
M0 LABEL2.L1[0]
*5 : Data of two devices are read when the device of (0 is stored.)
CN200 and later is specified for the Double Word M1 LABEL2.L1[1]
type label. M2 LABEL2.L1[2]
D100
LABEL2.L2
D101

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

466
 CHAPTER 5 FUNCTIONS

5.3.6 WriteDeviceRandom (Writing devices randomly)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Write devices randomly.

(3) Format

(a) Visual Basic® .NET

Ret = object.WriteDeviceRandom(szLabel, iSize, iData) 5
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of write points Input
Integer iData(n) Device values 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 values to be written Input

(b) Visual C++® .NET

iRet = object.WriteDeviceRandom(szLabel, iSize, iData)

5.3.6 WriteDeviceRandom (Writing devices randomly)

5.3 Details of Functions (For .NET Control)
int iRet Returned value Output
String^ szLabel Label name Input
int iSize Number of write points Input
array<int>^ iData Device values 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 values to be written Input

(c) Visual C#® .NET

Ret = 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 values to be written Input

Ret = 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 values to be written Input

467
 (4) 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) How to specify devices

The following describes how to specify label names and device values to be written.
• The following data type can be specified for label name.
Type class Label data type Label name format
Bit, Word, Double Word,
Float (Single Precision),
Float (Double Precision),
Basic type String*1, String (Unicode)*1, Time, Label name
Timer, Long timer,
Counter, Long counter,
Retentive Timer, Long retentive timer
Label name
(The label data type can be specified
Array Label name [number of elements]
Member in the same manner as the basic
Label name [n1] [n2] [n3]
type.)
Label name
(The label data type can be specified
Structure
Member in the same manner as the basic Label name.Member name
type.)
Label name [number of elements]
Structured (The label data type can be specified
Label name [number of elements].Member name
array Member in the same manner as the basic
Label name [n1] [n2] [n3].Element
type.)

*1 : The maximum number of characters that can be specified is 32 + NULL.

• For the number of write points, specify the sum of the following values correspond to the elements according
to the label data type.
Number of
Label data type Number of write points to be specified
applicable words
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, 1 Number of label elements
Retentive Timer, Long retentive timer

468
 CHAPTER 5 FUNCTIONS

• 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 Lower 2 Applicable

bytes bytes label
M0 LABEL1
Not used
D0 LABEL2 5
<When FXCPU devices of CN200 and later are specified> <When FD device is specified (4-word device)>
• Example: Write 3 points of data to the devices including Example: Write 3 points of data to the devices including
CN200. *1 FD0.
• Label setting • Label setting

szLabelList Data type Device szLabelList Data type Device

[0] LABEL1 Word D0 [0] LABEL1 Word D0

[1] LABEL2 Double Word CN200 [1] LABEL2 Double Word FD0

[2] LABEL3 Word D1 [2] LABEL3 Word D1

• Number of write points: 3 • Number of write points: 3

• Device values to be written • Device values to be written

Upper 2 Lower 2 Applicable Upper 2 Lower 2 Applicable

5.3.6 WriteDeviceRandom (Writing devices randomly)

5.3 Details of Functions (For .NET Control)
bytes bytes label bytes bytes label
Not used D0 LABEL1 D0 LABEL1

H of CN200 L of CN200 LABEL2 Not used LL of FD0*2 LABEL2

Not used D1 LABEL3 D1 LABEL3

*1 : For FXCPU devices of CN200 and later, 4 bytes are *2 : Only lower 2 bytes can be set. "0" is written to the
written as 1 read point. specified devices HH, HL, and LH (upper 6 bytes).

469
 <When data type equivalent to 2 words or more is
<When array type label is specified>
specified for label>
Example: Write data by specifying labels of Double Word, Example: Write data to the devices by specifying array type
Float (Single Precision), Float (Double Precision), String*3, labels.
and Time types. • Label setting
• Label setting
szLabelList Data type Device
szLabelList Data type Device [0] LABEL1 Bit (0..1) M0
[0] LABEL1 Double Word D0 [1] LABEL2 Double Word (0..1) CN200
Float (Single [2] LABEL3 Double Word (0..1) D0
[1] LABEL2 D100
Precision)
• Number of write points: 8
Float (Double
[2] LABEL3 D200 • Device values to be written
Precision)
[3] LABEL4 String D300 Upper 2 Lower 2 Applicable
[4] LABEL5 Time D400 bytes bytes label
Not used M0 LABEL1[0]
• Number of write points: 27
• Device values to be written (0 is stored.) M1 LABEL1[1]
H of CN200 L of CN200 LABEL2[0]
Upper 2 Lower 2 Applicable
H of CN201 L of CN201 LABEL2[1]
bytes bytes label
D100
D0 LABEL3[0]
LABEL1 D101
D1 Not used
D102
D100 LABEL3[1]
LABEL2 D103
D101
D200
D201
LABEL3
Not used D202
D203
D300
: LABEL4
*3
D316
D400
LABEL5
D401

*3 : 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 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 Lower 2 Applicable

bytes bytes 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]

470
 CHAPTER 5 FUNCTIONS

<When labels with combined structure and label are

<When structure type labels are specified>
specified>
Example: Write data to the devices by specifying structure Example: Write data to the devices by specifying structure
type labels. type array and structure array type label.
• Structure setting • Structure setting

Structure Label Structure Label

Data type Data type
name name name name
L1 Bit L1 Bit
STRUCT STRUCT1
L2 Double Word L2 Word
• Label setting L1 Bit (0..2)
STRUCT2
L2 Double Word
Data Label
szLabelList Device
type name • Label setting

[0] LABEL1 STRUCT

L1 D0.0
Data Label 5
L2 D0 szLabelList Device
type name
L1 M10
[1] LABEL2 STRUCT STRUCT1 L1 X0
L2 CN200 [0] LABEL1
(0..1) L2 D0
• Number of write points: 5 L1 M0
• Device values to be written [1] LABEL2 STRUCT2
L2 D100
Upper 2 Lower 2 Applicable
• Number of write points: 9
bytes bytes label • Device values to be written
D0.0 LABEL1.L1
Upper 2 Lower 2 Applicable
D0
Not used LABEL1.L2 bytes bytes label
D1
X0 LABEL1[0].L1
M0 LABEL2.L1
D0 LABEL1[0].L2
H of CN200 L of CN200 LABEL2.L2

5.3.6 WriteDeviceRandom (Writing devices randomly)

5.3 Details of Functions (For .NET Control)
X1 LABEL1[1].L1
D1 LABEL1[1].L2
Not used M0 LABEL2.L1[0]
M1 LABEL2.L1[1]
M2 LABEL2.L1[2]
D100
LABEL2.L2
D101

471
 <When a structure type label, in which the structure type is included in the element, is specified>
Example: Write data from the devices by specifying structure type labels in which the structure type is included in the
element.
• Structure setting

Structure Label
Data type
name name
LABEL11 Bit
STRUCT1 LABEL12 Word
LABEL13 Structure type(STRUCT2)
LABEL21 Double Word
STRUCT2
LABEL22 Float (Double Precision)
• Label setting

Data Label
szLabelList Device
type name
[0] STRUCT STRUCT1 LABEL11 D0.0
[1] STRUCT STRUCT1 LABEL12 D1
LABEL13,
D2
LABEL21
[2] STRUCT STRUCT1
LABEL13,
D4
LABEL22
• Number of write points: 8
• Device values to be written

Upper 2 Lower 2
Applicable label
bytes bytes
D0.0 STRUCT.LABEL11
D1 STRUCT.LABEL12
D2 STRUCT.LABEL13
Not used D3 .LABEL21
(0 is stored.) D4
D5 STRUCT.LABEL13
D6 .LABEL22
D7

472
 CHAPTER 5 FUNCTIONS

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.
5
● 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.3.6 WriteDeviceRandom (Writing devices randomly)

5.3 Details of Functions (For .NET Control)

473
5.3.7 SetDevice (Setting device data)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Set one point of device.

(3) Format

(a) Visual Basic® .NET

IRet = object.SetDevice(szLabel, iData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer iData Device values to be written Input

(b) Visual C++® .NET

iRet = object.SetDevice(szLabel, iData)
int iRet Returned value Output
String^ szLabel Label name Input
int iData Device values to be written Input

(c) Visual C#® .NET

iRet = object.SetDevice(ref szLabel, iData)
int iRet Returned value Output
String szLabel Label name Input
int iData Device values to be written Input

(4) 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.

(5) How to specify devices

The following describes how to specify label names and device values to be written.
• The following data type can be specified for label name.
Type class Label data type Label name format
*1 *1
Bit, Word, Double Word , Float (Single Precision) ,
Float (Double Precision)*1, String*1,
Basic type String (Unicode), Time*1, Label name
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.
• Digit specified bit devices
• FXCPU devices of CN200 and later

474
 CHAPTER 5 FUNCTIONS

• Set the device values to be written as follows.

<When bit device is specified> <When word device is specified>
Example: Write data to M0. Example: Write data to D0.
• Label setting • Label setting

Data type Device Data type Device

Bit M0 Word D0

• Device values to be written • Device values to be written

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

Not used M0 Not used D0

<When CN200 or later of FXCPU is specified> <When FD device is specified (4-word device)>

Example: Write data to CN200. *1 Example: Write data by specifying FD0.

• Label setting
• Label setting
5
Data type Device Data type Device
Double Word CN200 Word FD0

• Device values to be written • Device values to be written

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

H of CN200 L of CN200 Not used LL of FD0*2

*1 : For FXCPU devices of CN200 and later, 4 bytes are *2 : Only lower 2 bytes can be set. "0" is written to the
written. specified devices HH, HL, and LH (upper 6 bytes).
<When data type equivalent to 2 words or more is <When long timer, long counter, or long retentive timer
specified for label> type is specified>
Example: Write data by specifying String type label. Example: Write data to LT0.
• Label setting • Label setting

Data type Device Data type Device

5.3.7 SetDevice (Setting device data)

5.3 Details of Functions (For .NET Control)
String D0 Long timer LT0

• Device values to be written • Device values to be written

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

Not used D0 *3 H of LT0 L of LT0

*3 : Only lower 2 bytes are written to the start device.

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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
FXCPU devices of CN200 and later, 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.

475
5.3.8 GetDevice (Acquiring device data)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Acquire one point of device.

(3) Format

(a) Visual Basic® .NET

IRet = object.GetDevice(szLabel, iData)
Integer IRet Returned value Output
String szLabel Label name Input
Integer iData Read device values Output

(b) Visual C++® .NET

iRet = object.GetDevice(szLabel, iData)
int iRet Returned value Output
String^ szLabel Label name Input
int iData Read device values Output

(c) Visual C#® .NET

iRet = object.GetDevice(ref szLabel, ref iData)
int iRet Returned value Output
String szLabel Label name Input
int iData Read device values Output

(4) Description
One point of device data specified for szLabel (label name)is stored in iData (read device values).

(5) How to specify devices

The following describes how to specify label names and device values to be read.
• The following data type can be specified for label name.
Type class Label data type Label name format
Bit, Word, Double Word*1, Float (Single Precision)*1,
Float (Double Precision) , String*1,
*1

Basic type String (Unicode), Time*1, Label name

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.
• Digit specified bit devices
• FXCPU devices of CN200 and later

476
 CHAPTER 5 FUNCTIONS

• The read device values are stored as follows.

<When bit device is specified> <When word device is specified>
Example: Read data from M0. Example: Read data from D0.
• Label setting • Label setting

Data type Device Data type Device

Bit M0 Word D0

• Read device values • Read device values

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

Not used Not used
M0*1 D0
(0 is stored.) (0 is stored.)

*1 : The device to be read is 1 point of "M0", and "0" or

"1" is stored for the device value.
<When CN200 or later of FXCPU is specified> <When FD device is specified (4-word device)> 5
*2 Example: Read data by specifying FD0.
Example: Read data from CN200.
• Label setting • Label setting

Data type Device Data type Device

Double Word CN200 Word FD0

• Read device values • Read device values

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

H of CN200 L of CN200 Not used
LL of FD0*3
(0 is stored.)
*2 : For FXCPU devices of CN200 and later, 4 bytes are
read. *3 : Only lower 2 bytes are read. Data are not read from
the specified devices HH, HL, and LH (upper 6
bytes).
<When data type equivalent to 2 words or more is <When long timer, long counter, or long retentive timer

5.3.8 GetDevice (Acquiring device data)

5.3 Details of Functions (For .NET Control)
specified for label> type is specified>
Example: Read data by specifying String type label. Example: Read data to LT0.
• Label setting • Label setting

Data type Device Data type Device

String D0 Long timer LT0

• Read device values • Read device values

Upper 2 bytes Lower 2 bytes Upper 2 bytes Lower 2 bytes

Not used H of LT0 L of LT0
D0*4
(0 is stored.)

*4 : Only lower 2 bytes are read to the start device.

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

477
5.3.9 ReadBuffer (Reading data from buffer memory)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Read data from the buffer memory of special function module.

(3) Format

(a) Visual Basic® .NET

IRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, sData)
Integer lRet Returned value Output
Integer iStartIO Start I/O number of module from Input
Integer iAddress Buffer memory address Input
Integer iReadSize Read size Input
Short sData(n) Values read from buffer memory Output

(b) Visual C++® .NET

iRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, sData)
int iRet Returned value Output
int iStartIO Start I/O number of module from Input
int iAddress Buffer memory address Input
int iReadSize Read size Input
array<short>^ sData Values read from buffer memory Output

(c) Visual C#® .NET

iRet = object.ReadBuffer(iStartIO, iAddress, iReadSize, sData)
int iRet Returned value Output
int iStartIO Start I/O number of module from Input
int iAddress Buffer memory address Input
int iReadSize Read size Input
short[n] sData Values read from buffer memory Output

(4) Description
• For the start I/O number of the module specified for iStartIO, specify the value of the actual start I/O number
divided by 16.
• Buffer values of buffer memory address specified for iAddress of the special function module of the start I/O
number specified for iStartIO are read for the size of iReadSize.
• 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.

478
 CHAPTER 5 FUNCTIONS

(5) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

(6) Considerations for reading/writing data from/to buffer memory in multiple CPU
system configuration
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, 5
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.
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 paths, refer to the table in Page 389, Section 5.2.9.

5.3.9 ReadBuffer (Reading data from buffer memory)

5.3 Details of Functions (For .NET Control)

479
5.3.10 WriteBuffer (Writing data to buffer memory)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Write data to the buffer memory of special function module.

(3) Format

(a) Visual Basic® .NET

IRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, sData)
Integer lRet Returned value Output
Start I/O number of module to
Integer iStartIO Input
where values will be written
Integer iAddress Buffer memory address Input
Integer iWriteSize Write size Input
Short sData(n) Values written from buffer memory Input

(b) Visual C++® .NET

iRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, sData)
int iRet Returned value Output
Start I/O number of module to
int iStartIO Input
where values will be written
int iAddress Buffer memory address Input
int iWriteSize Write size Input
array<short>^ sData Values written from buffer memory Input

(c) Visual C#® .NET

IRet = object.WriteBuffer(iStartIO, iAddress, iWriteSize, sData)
int iRet Returned value Output
Start I/O number of module to
int iStartIO Input
where values will be written
int iAddress Buffer memory address Input
int iWriteSize Write size Input
Short[n] sData Values written from buffer memory Input

(4) Description
• For the start I/O number of the module specified for iStartIO, specify the value of the actual start I/O number
divided by 16.
• Buffer values of buffer memory address specified for iAddress of the special function module of the start I/O
number specified for iStartIO are written for the size of iWriteSize.
• 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.

480
 CHAPTER 5 FUNCTIONS

(5) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

(6) Considerations for reading/writing data from/to buffer memory in multiple CPU
system configuration
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, 5
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.
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 paths, refer to the table in Page 394, Section 5.2.10.

5.3.10 WriteBuffer (Writing data to buffer memory)

5.3 Details of Functions (For .NET Control)

481
5.3.11 GetClockData (Reading clock data)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Read clock data from a programmable controller CPU.

(3) Format

(a) Visual Basic® .NET

IRet = object.GetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
Integer lRet 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

(b) 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

(c) 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

482
 CHAPTER 5 FUNCTIONS

(4) 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
5 Friday
6 Saturday

(5) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

● If an R motion CPU or a Q motion CPU is accessed, an error is 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.3.11 GetClockData (Reading clock data)

5.3 Details of Functions (For .NET Control)
● For the availability of communication paths, refer to the table in Page 399, Section 5.2.11.

483
5.3.12 SetClockData (Writing clock data)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Write clock data to a programmable controller CPU.

(3) Format

(a) Visual Basic® .NET

IRet = object.SetClockData(sYear, sMonth, sDay, sDayOfWeek, sHour, sMinute, sSecond)
Integer 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 second Second value to be written Input

(b) 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

(c) 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 second Second value to be written Input

484
 CHAPTER 5 FUNCTIONS

(4) 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
5
4 Thursday
5 Friday
6 Saturday

(5) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

● If an R motion CPU or a Q motion CPU is accessed, an error is 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.

5.3.12 SetClockData (Writing clock data)

5.3 Details of Functions (For .NET Control)
● Note that an error of transfer time may occur in clock setting.
● For the availability of communication paths, refer to the table in Page 404, Section 5.2.12.
● An error is returned when the own board is accessed.

485
5.3.13 GetCpuType (Reading programmable controller CPU model)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Read the model character string and the model code of programmable controller CPU, network board, and GOT.

(3) Format

(a) Visual Basic® .NET

IRet = object.GetCpuType(szCpuName, ICpuType)
Integer IRet Returned value Output
Programmable controller CPU model
String szCpuName Output
character string
Programmable controller CPU model
Integer ICpuType Output
code

(b) Visual C++® .NET

iRet = object.GetCpuType (szCpuName, iCpuType)
int iRet Returned value Output
Programmable controller CPU model
String^ szCpuName Output
character string
Programmable controller CPU model
int iCpuType Output
code

(c) Visual C#® .NET

iRet = object.GetCpuType(ref szCpuName, ref iCpuType)
int iRet Returned value Output
Programmable controller CPU model
String szCpuName Output
character string
Programmable controller CPU model
int iCpuType Output
code

(4) 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.

(5) Model character string and model code of CPU

For details, refer to the following section.
Page 409, Section 5.2.13

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

486
 CHAPTER 5 FUNCTIONS

5.3.14 SetCpuStatus (Remote control)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Perform a remote operation of programmable controller CPU.

(3) Format

(a) Visual Basic® .NET

IRet = object.SetCpuStatus(IOperation) 5
Integer lRet Returned value Output
Integer lOperation Remote RUN/STOP/PAUSE Input

(b) Visual C++® .NET

iRet = object.SetCpuStatus (iOperation)
int iRet Returned value Output
int iOperation Remote RUN/STOP/PAUSE Input

(c) Visual C#® .NET

iRet = object.SetCpuStatus (iOperation)
int iRet Returned value Output
int iOperation Remote RUN/STOP/PAUSE Input

5.3.14 SetCpuStatus (Remote control)

5.3 Details of Functions (For .NET Control)
(4) 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

(5) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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 paths, refer to the table in Page 414, Section 5.2.14.
● If an R motion CPU is accessed, an error is returned.

487
5.3.15 EntryDeviceStatus (Registering devices for status monitoring)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Register devices whose status to be monitored.

(3) Format

(a) 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 monitor time interval Input
Integer iData(n) Registered device value list Input

(b) 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 monitor time interval Input
array<int>^ iData Registered device value list Input

(c) 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 monitor time interval Input
int[n] iData Registered device value list Input

(4) 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.
• The 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.

488
 CHAPTER 5 FUNCTIONS

(5) How to specify devices

The following explains how to specify label names and registered device values.
• The following data type can be specified for label name.
Type class Label data type Label name format
Basic type Bit, Word Label name

• Set the device values to be registered as follows.

<When bit device and word device are specified> <When CN200 or later of FXCPU is specified>
Example: Register 1 point of M0 and D0. Example: Register 3 points of devices including CN200.
• Label setting • Label setting

szLabelList Data type Device szLabelList Data type Device

[0] LABEL1 Bit M0 [0] LABEL1 Word D0
[1] LABEL2 Word D0 [1] LABEL2 Word CN200
5
• Number of registered device points: 2 [2] LABEL3 Word D1
• Registered device values
• Number of registered device points: 3
Upper 2 bytes Lower 2 bytes • Registered device values

M0 Upper 2 bytes Lower 2 bytes

Not used
D0 Not used D0
H of CN200 L of CN200*1
Not used D1

*1 : For FXCPU devices of CN200 and later, 4 bytes can

be registered.
<When FD device is specified (4-word device)>
Example: Register 3 points of data from FD0.

5.3.15 EntryDeviceStatus (Registering devices for status monitoring)

5.3 Details of Functions (For .NET Control)
• 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

D0
Not used LL of FD0*2
D1

*2 : Only lower 2 bytes can be registered. The specified

devices HH, HL, and LH (upper 6 bytes) cannot be
registered.

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

489
 (7) 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 587, Appendix 2 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
Execution of
(M0)
OnDeviceStatus event
M0 OFF
Event execution
M0, M1 read request
Content of M0, M1 M0, M1 ON !
Execution of Event notification
OnDeviceStatus event (M0)
Event execution
Execution of Event notification
OnDeviceStatus event (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.

490
 CHAPTER 5 FUNCTIONS

5.3.16 FreeDeviceStatus (Deregistering devices for status monitoring)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Deregister devices that are registered using the EntryDeviceStatus function to monitor their status.

(3) Format

(a) Visual Basic® .NET

IRet = object.FreeDeviceStatus() 5
Integer IRet Returned value Output

(b) Visual C++® .NET

iRet = object.FreeDeviceStatus()
int iRet Returned value Output

(c) Visual C#® .NET

iRet = object.FreeDeviceStatus()
int iRet Returned value Output

(4) Description
The devices that are set using the EntryDeviceStatus function to monitor their status are deregistered.

5.3.16 FreeDeviceStatus (Deregistering devices for status monitoring)

5.3 Details of Functions (For .NET Control)
(5) Returned value
Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

491
5.3.17 OnDeviceStatus (Event notification)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Execute the event notification when the device condition registered using the EntryDeviceStatus function is
satisfied.

(3) Format

(a) Visual Basic® .NET

Private Sub object_OnDeviceStatus(sender, e)
Event occurrence
ByVal sender As System.Object Input
source
ByVal e As objectLib_IobjectIFEvents_OnDeviceStatusEvent Event data Input
The following are the members of e.
Name of label whose condition is
e.szLabel
satisfied
Value of device whose condition is
e.lData
satisfied
Returned value of condition check
e.lReturnCode
processing

(b) Visual C++® .NET

private: System::Void objectIF_OnDeviceStatus (*sender, e)
Event occurrence
System::Object *sender Input
source
objectLib::objectIF_OnDeviceStatusEvent* e Event data Input
The following are the members of e.
Name of label whose condition is
e->szLabel
satisfied
Value of device whose condition is
e->lData
satisfied
Returned value of condition check
e->lReturnCode
processing

(c) Visual C#® .NET

private void object_OnDeviceStatus(object sender, object.DeviceStatusEventArgs e)
Event occurrence
sender output
source
e Event data output
The following are the members of e.
Name of label whose condition is
e->szLabel
satisfied
Value of device whose condition is
e->lData
satisfied
Returned value of condition check
e->lReturnCode
processing

492
 CHAPTER 5 FUNCTIONS

(4) 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) Returned value

5
Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.3.17 OnDeviceStatus (Event notification)

5.3 Details of Functions (For .NET Control)

493
5.3.18 ReadDeviceBlock2 (Reading devices in bulk)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Read devices in 2-byte data unit in bulk.

(3) Format

(a) 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 values Output

(b) 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 values Output

(c) 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 values Output

(4) 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) How to specify devices

The following describes how to specify label names and device values to be read.
• The following data type can be specified for label name.
Type class Label data type Label name format
Label name
Bit, Word, Double Word,
Float (Single Precision), Float (Double Precision),
Array Label name [number of elements]
Member String*1, String (Unicode)*1, Time, Long timer,
Label name [n1] [n2] [n3]
Counter, Long counter,
Retentive Timer, Long retentive timer

*1 : The maximum number of characters that can be specified is 32 + NULL

494
 CHAPTER 5 FUNCTIONS

• Set the following values for the number of read points according to the label data type.
Number of
Label (array) data type Number of read points to be specified
applicable words
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, 1 Number of label array elements
Retentive Timer, Long retentive timer

• The read device values are stored as follows. 5

<When bit device is specified> <When word device is specified>
Example: Read 3 points of data (3 words = 48 bits) from Example: Read 3 points of data from the devices starting
the devices starting from M0. from D0.
• Label setting (Data type: Bit, Number of array elements: • Label setting (Data type: Word, Number of array
48) elements: 3)

Data type Device Data type Device

Bit (0..47) M0 Word (0..1) D0

• Number of read points: 3 • Number of read points: 3

• Read device values • Read device values
2 Bytes 2 Bytes
*2
M0 to M15 D0

M16 to M31*2 D1

5.3.18 ReadDeviceBlock2 (Reading devices in bulk)

5.3 Details of Functions (For .NET Control)
D2
M32 to M47*2
*2 : Devices are stored from the lower bit in the order of
device number.
<When FXCPU devices of CN200 and later are specified> <When FD device is specified (4-word device)>
Example: Read 6 points of data from the devices starting Example: Read 8 points of data from the devices starting
from CN200.*3 from FD0.
• Label setting (Data type: Double Word, Number of array • Label setting (Data type: Double Word, Number of array
elements: 3) elements: 2)

Data type Device Data type Device

Double Word (0..2) CN200 Double Word (0..2) FD0

• Number of read points: 6 • Number of read points: 8

• Read device values • Read device values

2 Bytes 2 Bytes
L of CN200 LL of FD0
H of CN200 LH of FD0
L of CN201 HL of FD0
H of CN201 HH of FD0
L of CN202 LL of FD1
H of CN202 LH of FD1
*3 : For FXCPU devices of CN200 and later, 2 points of HL of FD1
data are read from each 1 point of device (upper (H) HH of FD1
and lower (L) data).
Reading only 1 point of data will result in an error.

495
 <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

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

496
 CHAPTER 5 FUNCTIONS

5.3.19 WriteDeviceBlock2 (Writing devices in bulk)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Write devices in 2-byte data unit in bulk.

(3) Format

(a) Visual Basic® .NET

IRet = object.WriteDeviceBlock2(szLabel, iSize, sData) 5
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of write points Input
Short sData(n) Device values to be written Input

(b) 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 values to be written Input

5.3.19 WriteDeviceBlock2 (Writing devices in bulk)

5.3 Details of Functions (For .NET Control)
(c) 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 values to be written Input

497
 (4) 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.

(5) How to specify devices

The following describes how to specify label names and device values to be written.
• The following data type can be specified for label name.
Type class Label data type Label name format
Label name
Bit, Word, Double Word,
Float (Single Precision), Float (Double Precision),
Array String*1, String (Unicode)*1, Time, Label name [number of elements]
Member
Timer, Long timer, Label name [n1] [n2] [n3]
Counter, Long counter,
Retentive Timer, Long retentive timer

*1 : The maximum number of characters that can be specified is 32 + NULL

• Set the following values for the number of write points according to the label data type.
Number of
Label (array) data type Number of write points to be specified
applicable words
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, 1 Number of label array elements
Retentive Timer, Long retentive timer

498
 CHAPTER 5 FUNCTIONS

• Set the device values to be written as follows.

<When bit device is specified> <When word device is specified>
Example: Write 3 points of data (3 words = 48 bits) to the Example: Write 3 points of data to the devices starting
devices starting from M0. from D0.
• Label setting (Data type: Bit, Number of array elements: • Label setting (Data type: Word, Number of array
48) elements: 3)

Data type Device Data type Device

Bit (0..47) M0 Word (0..2) D0

• Number of write points: 3 • Number of write points: 3

• Device values to be written • Device values to be written
2 Bytes 2 Bytes
M0 to M15*2 D0
M16 to M31 *2 D1 5
M32 to M47 *2 D2

*2 : Devices are stored from the lower bit in the order of

device number.
<When FXCPU devices of CN200 and later are specified> <When FD device is specified (4-word device)>
Example: Write 6 points of data to the devices starting Example: Write 8 points of data to the devices starting
from CN200. *3 from FD0.
• Label setting (Data type: Double Word, Number of array • Label setting (Data type: Double Word, Number of array
elements: 3) elements: 2)

Data type Device Data type Device

Double Word (0..2) CN200 Double Word (0..1) FD0

• Number of write points: 6 • Number of write points: 8

• Device values to be written • Device values to be written

5.3.19 WriteDeviceBlock2 (Writing devices in bulk)

5.3 Details of Functions (For .NET Control)
2 Bytes 2 Bytes
L of CN200 LL of FD0

H of CN200 LH of FD0

L of CN201 HL of FD0

H of CN201 HH of FD0

L of CN202 LL of FD1

H of CN202 LH of FD1
HL of FD1
*3 : For FXCPU devices of CN200 and later, 2 points of
data are written to each 1 point of device (upper (H) HH of FD1
and lower (L) data).
Writing only 1 point of data will result in an error.

499
 <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

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.
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.

500
 CHAPTER 5 FUNCTIONS

5.3.20 ReadDeviceRandom2 (Reading devices randomly)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Read devices in 2-byte data unit randomly.

(3) Format

(a) Visual Basic® .NET

IRet = object.ReadDeviceRandom2(szLabel, iSize, sData) 5
Integer IRet Returned value Output
String szLabel Label name Input
Integer iSize Number of read points Input
Short sData(n) Read device values 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 values Output

(b) Visual C++® .NET

iRet = object.ReadDeviceRandom2(szLabel, iSize, sData)

5.3.20 ReadDeviceRandom2 (Reading devices randomly)

5.3 Details of Functions (For .NET Control)
Int iRet Returned value Output
String^ szLabel Label name Input
int iSize Number of read points Input
array<short>^ sData Read device values 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 values Output

(c) 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 values 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 values Output

501
 (4) 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) How to specify devices

The following describes how to specify label names and device values to be read.
• The following data type can be specified for label name.
Type class Label data type Label name format
Bit, Word, Double Word,
Float (Single Precision),
Float (Double Precision),
Basic type String*1, String (Unicode)*1, Label name
Time, Timer, Long timer,
Counter, Long counter,
Retentive Timer, Long retentive timer
Label name
Array (The label data type can be specified in Label name [number of elements]
Member
the same manner as the basic type.) Label name [n1] [n2] [n3]
Label name
Structure (The label data type can be specified in
Member Label name.Member name
the same manner as the basic type.)
Label name [number of elements]
Structured Label name [number of elements].Member
(The label data type can be specified in
array Member name
the same manner as the basic type.)
Label name [n1] [n2] [n3].Element

*1 : The maximum number of characters that can be specified is 32 + NULL.

• For the number of read points, specify the sum of the following values correspond to the elements according
to the label data type.
Number of
Label data type Number of read points to be specified
applicable words
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, 1 Number of label elements
Retentive Timer, Long retentive timer

502
 CHAPTER 5 FUNCTIONS

• 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

M0*1 LABEL1
D0 LABEL2

*1 : The device to be read is 1 point of "M0", and "0" or 5

"1" is stored for the device value.
<When FXCPU devices of CN200 and later are specified> <When FD device is specified (4-word device)>
Example: Read 3 points of data from the devices including
Example: Read 3 points of data from the devices including
FD0.
CN200.
• Label setting
• Label setting
szLabelList Data type Device
szLabelList Data type Device
[0] LABEL1 Word D0
[0] LABEL1 Word D0
[1] LABEL2 Double Word FD0
[1] LABEL2 Double Word CN200
[2] LABEL3 Word D1
[2] LABEL3 Word D1
• Number of read points: 3
• Number of read points: 3
• Read device values
• Read device values
2 Bytes Applicable label

5.3.20 ReadDeviceRandom2 (Reading devices randomly)

5.3 Details of Functions (For .NET Control)
2 Bytes Applicable label
D0 LABEL1
D0 LABEL1
*2 LL of FD0*3 LABEL2
L of CN200 LABEL2
D1 LABEL3
D1 LABEL3
*3 : Only lower 2 bytes are read. Data are not read from
*2 : Only lower 2 bytes are read. Data are not read from
the specified devices HH, HL, and LH (upper 6
the specified device H (upper 2 bytes).
bytes).

503
 <When data type equivalent to 2 words or more is
<When array type label is specified>
specified for label>
Example: Write data by specifying labels of Double Word, Example: Read data from the devices by specifying array
Float (Single Precision), Float (Double Precision), String*4, type labels.
and Time types. • Label setting
• Label setting
szLabelList Data type Device
szLabelList Data type Device [0] LABEL1 Bit (0..1) M0
[0] LABEL1 Double Word D0 [1] LABEL2 Double Word (0..1) CN200
Float (Single [2] LABEL3 Double Word (0..1) D0
[1] LABEL2 D100
Precision)
• Number of read points: 8
Float (Double
[2] LABEL3 D200 • Read device values
Precision)
[3] LABEL4 String D300 Applicable
2 Bytes
[4] LABEL5 Time D400 label
M0 LABEL1[0]
• Number of read points: 27
M1 LABEL1[1]
• Read device values
L of CN200 LABEL2[0]
Applicable L of CN201 LABEL2[1]
2 Bytes
label D100
D0 LABEL3[0]
LABEL1 D101
D1
D102
D100 LABEL3[1]
LABEL2 D103
D101
D200
D201
LABEL3
D202
D203
D300
: LABEL4
D316*4
D400
LABEL5
D401

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

504
 CHAPTER 5 FUNCTIONS

<When labels with combined structure and label are

<When structure type labels are specified>
specified>
Example: Read data from the devices by specifying Example: Read data from the devices by specifying
structure type labels. structure type array and structure array type label.
• Structure setting • Structure setting

Structure Label Structure Label

Data type Data type
name name name name
L1 Bit L1 Bit
STRUCT STRUCT1
L2 Double Word L2 Word
L1 Bit (0..2)
• Label setting STRUCT2
L2 Double Word
Data Label
szLabelList Device • Label setting
type name

[0] LABEL1 STRUCT

L1 D0.0
szLabelList
Data Label
Device 5
L2 D0 type name
L1 M10 STRUCT1 L1 X0
[1] LABEL2 STRUCT [0] LABEL1
L2 CN200 (0..1) L2 D0
• Number of read points: 6 L1 M0
[1] LABEL2 STRUCT2
• Read device values L2 D100

Applicable • Number of read points: 9

2 Bytes • Read device values
label
D0.0 LABEL1.L1 Applicable
2 Bytes
D0 label
LABEL1.L2
D1 X0 LABEL1[0].L1
M0 LABEL2.L1 D0 LABEL1[0].L2
L of CN200 X1 LABEL1[1].L1
LABEL2.L2

5.3.20 ReadDeviceRandom2 (Reading devices randomly)

5.3 Details of Functions (For .NET Control)
L of CN201*5 D1 LABEL1[1].L2
M0 LABEL2.L1[0]
*5 : Data of two devices are read when the device of
CN200 and later is specified for the Double Word M1 LABEL2.L1[1]
type label. M2 LABEL2.L1[2]
D100
LABEL2.L2
D101

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.
● 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.

505
5.3.21 WriteDeviceRandom2 (Writing devices randomly)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Write devices in 2-byte data unit randomly.

(3) Format

(a) 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 values 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 values to be written Input

(b) 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 values 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 values to be written Input

(c) 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 values 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 values to be written Input

506
 CHAPTER 5 FUNCTIONS

(4) 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) How to specify devices

The following describes how to specify label names and device values to be written.
• The following data types can be specified for label names.
Type class Label data type Label name format
Bit, Word, Double Word,
Float (Single Precision),

Basic type
Float (Double Precision),
String*1, String (Unicode)*1, Time, Label name
5
Timer, Long timer,
Counter, Long counter,
Retentive Timer, Long retentive timer
Label name
Array (The label data type can be specified in Label name [number of elements]
Member
the same manner as the basic type.) Label name [n1] [n2] [n3]
Label name
Structure (The label data type can be specified in
Member Label name.Member name
the same manner as the basic type.)
Label name [number of elements]
Structured Label name [number of elements].Member
(The label data type can be specified in
array Member name
the same manner as the basic type.)
Label name [n1] [n2] [n3].Element

5.3.21 WriteDeviceRandom2 (Writing devices randomly)

5.3 Details of Functions (For .NET Control)
*1 : The maximum number of characters that can be specified is 32 + NULL.

• For the number of write points, specify the sum of the following values correspond to the elements according
to the label data type.
Number of
Label data type Number of write points to be specified
applicable words
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, 1 Number of label elements
Retentive Timer, Long retentive timer

507
 • 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 device to be written is 1 point of "M0", and the
value of least significant bit of 2 byte-data to be set
is the device value to be written.
<When FXCPU devices of CN200 and later are specified> <When FD device is specified (4-word device)>
Example: Write 3 points of data to the devices including
Example: Write 3 points of data to the devices including
CN200.*2
FD0.
• Label setting
• Label setting
szLabelList Data type Device
szLabelList Data type Device
[0] LABEL1 Word D0
[0] LABEL1 Word D0
[1] LABEL2 Double Word CN200
[1] LABEL2 Double Word FD0
[2] LABEL3 Word D1
[2] LABEL3 Word D1
• Number of write points: 3
• Number of write points: 3
• Device values to be written
• Device values to be written
Applicable
2 Bytes Applicable
label 2 Bytes
label
D0 LABEL1
D0 LABEL1
L of CN200 LABEL2
LL of FD0*3 LABEL2
D1 LABEL3

*2 : 4 bytes are written as 1 point for FXCPU devices of *3 : Only lower 2 bytes can be set. "0" is written to the
CN200 and later. Only lower 2 bytes can be set. "0" specified devices HH, HL, and LH (upper 6 bytes).
is written to the specified device H (upper 2 bytes).

508
 CHAPTER 5 FUNCTIONS

<When data type equivalent to 2 words or more is

<When array type label is specified>
specified for label>
Example: Write data by specifying labels of Double Word, Example: Write data to the devices by specifying array
Float (Single Precision), Float (Double Precision), String*4 , type labels.
and Time types. • Label setting
• Label setting szLabelList Data type Device
szLabelList Data type Device [0] LABEL1 Bit (0..1) M0
[0] LABEL1 Double Word D0 [1] LABEL2 Double Word (0..1) CN200
Float (Single [2] LABEL3 Double Word (0..1) D0
[1] LABEL2 D100
Precision)
• Number of write points: 8
Float (Double • Device values to be written
[2] LABEL3 D200
Precision)
[3] LABEL4 String D300
Applicable
2 Bytes
[4] LABEL5 Time D400
label 5
M0 LABEL1[0]
• Number of write points: 27
• Device values to be written M1 LABEL1[1]
L of CN200 LABEL2[0]
Applicable
2 Bytes L of CN201 LABEL2[1]
label
D100
D0 LABEL3[0]
LABEL1 D101
D1
D102
D100 LABEL3[1]
LABEL2 D103
D101
D200
D201
LABEL3
D202
D203

5.3.21 WriteDeviceRandom2 (Writing devices randomly)

5.3 Details of Functions (For .NET Control)
D300
: LABEL4
D316*4
D400
LABEL5
D401

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

509
 <When labels with combined structure and label are
<When structure type labels are specified>
specified>
Example: Write data to the devices by specifying structure
Example: Write data to the devices by specifying structure
type array and structure array type label.
type labels.
• Structure setting
• Structure setting
Structure Label
Structure Label Data type
Data type name name
name name
L1 Bit
L1 Bit STRUCT1
STRUCT L2 Word
L2 Double Word
L1 Bit (0..2)
• Label setting STRUCT2
L2 Double Word
Data Label
szLabelList Device • Label setting
type name
Data Label
L1 D0.0 szLabelList Device
[0] LABEL1 STRUCT type name
L2 D0
STRUCT1 L1 X0
L1 M10 [0] LABEL1
[1] LABEL2 STRUCT (0..1) L2 D0
L2 CN200
L1 M0
• Number of write points: 5 [1] LABEL2 STRUCT2
L2 D100
• Device values to be written
• Number of write points: 9
Applicable • Device values to be written
2 Bytes
label
Applicable
D0.0 LABEL1.L1 2 Bytes
label
D0
LABEL1.L2 X0 LABEL1[0].L1
D1
D0 LABEL1[0].L2
M0 LABEL2.L1
X1 LABEL1[1].L1
L of CN200 LABEL2.L2
D1 LABEL1[1].L2
X1 LABEL3.L1
M0 LABEL2.L1[0]
M0 to 15 LABEL3.L2
M1 LABEL2.L1[1]
M2 LABEL2.L1[2]
D100
LABEL2.L2
D101

510
 CHAPTER 5 FUNCTIONS

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.
● 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).
5
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.3.21 WriteDeviceRandom2 (Writing devices randomly)

5.3 Details of Functions (For .NET Control)

511
5.3.22 SetDevice2 (Setting device data)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Set one point of device in 2-byte data unit.

(3) Format

(a) Visual Basic® .NET

IRet = object.SetDevice2(szLabel, sData)
Integer IRet Returned value Output
String szLabel Label name Input
Short sData Device values to be written Input

(b) Visual C++® .NET

iRet = object.SetDevice2(szLabel, sData)
int iRet Returned value Output
String^ szLabel Label name Input
short sData Device values to be written Input

(c) Visual C#® .NET

iRet = object.SetDevice2(ref szLabel, sData)
int iRet Returned value Output
String szLabel Label name Input
short sData Device values to be written Input

(4) 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.

(5) How to specify devices

The following describes how to specify label names and device values to be written.
• The following data type can be specified for label name.
Type class Label data type Label name format
*1
Bit, Word, Double Word ,
Float (Single Precision)*1, Float (Double Precision)*1,
Basic type String*1, String (Unicode)*1, Time*1, Timer, Long timer, Label name
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.

512
 CHAPTER 5 FUNCTIONS

• Set the device values to be written as follows.

<When bit device is specified> <When word device is specified>
Example: Write data to M0. Example: Write data to D0.
• Label setting • Label setting

Data type Device Data type Device

Bit M0 Word D0

• Device values to be written • Device values to be written

2 Bytes 2 Bytes

M0*2 D0

*2 : The device to be written is 1 point of "M0", and the

value of least significant bit of 2 byte-data to be set
is the device value to be written.
<When CN200 or later of FXCPU is specified> <When FD device is specified (4-word device)> 5
Example: Write data to CN200. *3 Example: Write data by specifying FD0.
• Label setting • Label setting

Data type Device Data type Device

Double Word CN200 Word FD0

• Device values to be written • Device values to be written

2 Bytes 2 Bytes
L of CN200 LL of FD0*4

*3 : For FXCPU devices of CN200 and later, 4 bytes are *4 : Only lower 2 bytes are written. Data cannot be
written. Only lower 2 bytes can be set. "0" is written written to the specified devices HH, HL, and LH
to the specified device H (upper 2 bytes). (upper 6 bytes).
<When data type equivalent to 2 words or more is
specified for label>

5.3.22 SetDevice2 (Setting device data)

5.3 Details of Functions (For .NET Control)
Example: Write data by specifying String type label.
• Label setting

Data type Device

String D0

• Device values to be written

2 Bytes
*5
D0

*5 : Only lower 2 bytes are written to the start device.

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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.

513
5.3.23 GetDevice2 (Acquiring device data)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Acquire one point of device in 2-byte data unit.

(3) Format

(a) Visual Basic® .NET

IRet = object.GetDevice2(szLabel, sData)
Integer IRet Returned value Output
String szLabel Label name Input
Short sData Read device values Output

(b) Visual C++® .NET

iRet = object.GetDevice2(szLabel, sData)
int iRet Returned value Output
String^ szLabel Label name Input
short sData Read device values Output

(c) Visual C#® .NET

iRet = object.GetDevice2(ref szLabel, ref sData)
int iRet Returned value Output
String szLabel Label name Input
short sData Read device values Output

(4) Description
One point of device data specified for szLabel (label name) is stored in sData (read device values).

(5) How to specify devices

The following describes how to specify label names and device values to be read.
• The following data type can be specified for label name.
Type class Label data type Label name format
Bit, Word, Double Word*1,
Float (Single Precision)*1, Float (Double Precision)*1,
Basic type String*1, String (Unicode)*1, Time*1, Timer, Long timer, Label name
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.

514
 CHAPTER 5 FUNCTIONS

• The read device values are stored as follows.

<When bit device is specified> <When word device is specified>
Example: Read data from M0. Example: Read data from D0.
• Label setting • Label setting

Data type Device Data type Device

Bit M0 Word D0

• Read device values • Read device values

2 Bytes 2 Bytes
M0 *2 D0

*2 : The device to be read is 1 point of "M0", and "0" or "1"

is stored for the device value.
<When CN200 or later of FXCPU is specified> <When FD device is specified (4-word device)>

Example: Read data from CN200.*3 Example: Read data by specifying FD0. 5
• Label setting • Label setting

Data type Device Data type Device

Double Word CN200 Word FD0

• Read device values • Read device values

2 Bytes 2 Bytes
L of CN200 LL of FD0*4

*3 : The specified device H (lower 2 bytes) is read as 1 *4 : Only lower 2 bytes are read. Data are not read from
point for FXCPU devices of CN200 and later. the specified devices HH, HL, and LH (upper 6
Data are not read from the specified device H (upper bytes).
2 bytes).
<When data type equivalent to 2 words or more is specified
for label>

5.3.23 GetDevice2 (Acquiring device data)

5.3 Details of Functions (For .NET Control)
Example: Read data by specifying String type label.
• Label setting

Data type Device

String D0

• Read device values

2 Bytes
*5
D0

*5 : Only lower 2 bytes are read to the start device.

(6) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 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 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.

515
5.3.24 Connect (Connecting telephone line)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Connect the telephone line.

(3) Format

(a) Visual Basic® .NET

IRet = object.Connect()
Integer IRet Returned value Output

(b) Visual C++® .NET

iRet = object.Connect()
int iRet Returned value Output

(c) Visual C#® .NET

iRet = object.Connect()
int iRet Returned value Output

(4) 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.

(5) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

(6) 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.

516
 CHAPTER 5 FUNCTIONS

(7) 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.
Connection system of control which executed the Connect function second or Later
Auto line connect Callback connect Callback request
5
Connection system of control
Auto line connect(Callback (Fixation) (Fixation) Callback
which executed the Connect
fixation) Callback connect Callback request reception
function first
Auto line connect (Callback (Number (Number waiting
number specification) specification) 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)

5.3.24 Connect (Connecting telephone line)

5.3 Details of Functions (For .NET Control)
Callback request (Number    
specification)
Callback reception waiting    

: Normal termination : Abnormal termination (Error occurrence)

517
5.3.25 Disconnect (Disconnecting telephone line)

(1) Applicable control

Applicable to the DotUtlType control.

(2) Feature
Disconnect the telephone line.

(3) Format

(a) Visual Basic® .NET

IRet = object.Disconnect()
Integer IRet Returned value Output

(b) Visual C++® .NET

iRet = object.Disconnect()
int iRet Returned value Output

(c) Visual C#® .NET

iRet = object.Disconnect()
int iRet Returned value Output

(4) Description
The telephone line that was connected using the Connect function is disconnected.

(5) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

518
 CHAPTER 5 FUNCTIONS

(6) 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)
5
<Object A> <Object B>

Connection start Connection 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

the ReadDeviceBlock function Telephone line is connected.
Execution of the function such as

5.3.25 Disconnect (Disconnecting telephone line)

5.3 Details of Functions (For .NET Control)
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.

519
5.3.26 GetErrorMessage (Receiving error message)

(1) Applicable control

Applicable to the DotSupportMsg control.

(2) Feature
Receive the error description and its corrective action corresponding to the error code.

(3) Format

(a) Visual Basic® .NET

IRet = object.GetErrorMessage(IErrorCode, szErrorMessage)
Integer IRet Returned value Output
Integer IErrorCode Error code Input
String szErrorMessage Error message Output

(b) Visual C++® .NET

iRet = object.GetErrorMessage(iErrorCode, szErrorMessage)
int iRet Returned value Output
int iErrorCode Error code Input
String^ szErrorMessage Error message Output

(c) Visual C#® .NET

iRet = object.GetErrorMessage(iErrorCode, ref szErrorMessage)
int iRet Returned value Output
int iErrorCode Error code Input
String szErrorMessage Error message Output

(4) 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.

(5) Returned value

Normal termination : 0 is returned.
Abnormal termination: Any value other than 0 is returned. (Page 552, CHAPTER 7 ERROR CODES)

520
 CHAPTER 6 SAMPLE PROGRAMS

CHAPTER 6 SAMPLE PROGRAMS

This chapter explains the sample programs registered at the installation of MX Component.

(1) Sample programs, test programs, and sample sequence programs

(a) 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.

(b) 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.
6

(2) 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.
Supported
Folder name Description Reference
language
Page 528,
Sample Sample program for ActUtlType
AccessVBA VBA (Access) Section 6.1.3
TestPro *1 –
Test program for ActUtlType
Page 524,
Sample program for ActUtlType
Section 6.1.1
Sample
Sample program for ActUtlType and Page 526,
ExcelVBA VBA (Excel)
ActSupportMsg (Reading/writing devices) Section 6.1.2
Test program for ActUtlType and
TestPro –
ActSupportMsg*1
Page 532,
SampleASP HTML (ASP function)
Section 6.3
Sample program for ActMLUtlType
Page 530,
VBScript*2 SampleHTML
Section 6.2
HTML
Test program for ActUtlType and
TestPro –
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

521
 Supported
Folder name Description Reference
language
Visual Basic®.NET
ModemSample
Modem communication sample program for (Visual Studio® 2005) Page 535,
ActUtlType and ActSupportMsg Visual Basic ®.NET Section 6.4.1
ModemSample2010
(Visual Studio® 2010)
Visual Basic®.NET
Sample
Read/Write sample program for ActUtlType (Visual Studio® 2005)
and ActProgType Visual Basic®.NET
Sample2010
(Visual Studio® 2010)
Visual Basic®.NET
SampleDot
(Visual Studio® 2005)
Read/Write sample program for DotUtlType
Visual Basic®.NET
SampleDot2010
(Visual Studio® 2010) Page 537,
Vb.NET*3
®
Visual Basic .NET Section 6.4.2
Sample_References Read/Write sample program for ActUtlType
(Visual Studio® 2005)
and ActProgType
(for Reference) Visual Basic®.NET
Sample_References2010
(Visual Studio® 2010)

Visual Basic®.NET
Sample_ReferencesDot
Read/Write sample program for DotUtlType (Visual Studio® 2005)
(for Reference) Visual Basic®.NET
Sample_ReferencesDot2010
(Visual Studio® 2010)
Visual Basic®.NET
Sample_TypeConv
Type conversion sample program for (Visual Studio® 2005) Page 541,
ActUtlType and ActSupportMsg Visual Basic®.NET Section 6.4.3
Sample_TypeConv2010
(Visual Studio® 2010)
®
Visual C++ .NET
Sample2005
Read/Write sample program for ActUtlType (Visual Studio® 2005)
and ActProgType Visual C++®.NET
Sample2010
(Visual Studio® 2010)
Visual C++®.NET
SampleDot2005
(Visual Studio® 2005)
Read/Write sample program for DotUtlType
Visual C++®.NET
SampleDot2010
(Visual Studio® 2010) Page 543,
®
Visual C++ .NET Section 6.5.1
Sample_References2005 Read/Write sample program for ActUtlType
(Visual Studio® 2005)
Vc.NET and ActProgType
(for Reference) Visual C++®.NET
Sample_References2010
(Visual Studio® 2010)
Visual C++®.NET
Sample_ReferencesDot2005
Read/Write sample program for DotUtlType (Visual Studio® 2005)
(for Reference) Visual C++®.NET
Sample_ReferencesDot2010
(Visual Studio® 2010)
Visual C++®.NET
Sample_Support
Troubleshooting function sample program for (Visual Studio® 2005) Page 544,
DotSupportMsg Visual C++ ®.NET Section 6.5.2
Sample_Support2010
(Visual Studio® 2010)
*3 : When the operation environment of the sample program is Visual Studio®2013, the installation of MFC library (DLL) for multiple
byte character encode (MBCS) is required.

522
 CHAPTER 6 SAMPLE PROGRAMS

Supported Reference
Folder name Description
language Section
®
Visual C# .NET
Sample
Read/Write sample program for ActUtlType (Visual Studio® 2005)
and ActProgType Visual C#®.NET
Sample2010
(Visual Studio® 2010)

Visual C#®.NET
SampleDot
(Visual Studio® 2005)
Read/Write sample program for DotUtlType
Visual C#®.NET
SampleDot2010
(Visual Studio® 2010) Page 546,
Vcs.NET*4
®
Visual C# .NET Section 6.6.1
Sample_References Read/Write sample program for ActUtlType
(Visual Studio® 2005)
and ActProgType
(for Reference) Visual C#®.NET
Sample_References2010
(Visual Studio® 2010)

Sample_ReferencesDot
Visual C#®.NET
6
Read/Write sample program for DotUtlType (Visual Studio® 2005)
(for Reference) Visual C#®.NET
Sample_ReferencesDot2010
(Visual Studio® 2010)
Read/Write sample program for ActUtlType Page 547,
SampleENG
and ActProgType Section 6.7.1
Read/Write sample program for ActUtlType Visual C++®.NET(MFC) Page 549,
Vc CustomSampleENG
and ActProgType (Visual Studio® 2005) Section 6.7.2
Page 550,
Sample_SupportENG For ActSupportMsg
Section 6.7.3
Sample ladder for CC-Link G4
CCG4A
communication
Sample ladder for modem communication
FXCPUtel
(FXCPU)
MX
Sample ladder for modem communication
Component
QJ71C24Callback (Q series-compatible C24) in which the Sequence program
GppW Version 4
setting 1 is specified for the callback function (GX Developer)
Operating
Sample ladder for modem communication Manual.
QJ71C24Callback_Number (Q series-compatible C24) in which the
setting 3 is specified for the callback function
Sample ladder for modem communication
QJ71C24TEL
(Q series-compatible C24)

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

523
6.1 VBA Sample Programs

This section explains the VBA sample programs for Excel and Access.

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

(1) 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 button to start logging.

When the logging starts, the past 10 device values and line graphs are displayed on the graph.
6. Click the 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 552, CHAPTER 7 ERROR CODES)

(2) 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 button to stop logging, change the input value, and

click the 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.

(3) 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

524
 CHAPTER 6 SAMPLE PROGRAMS

(4) Screen
The following explains the settings on the sample program screen.

Item Description
Enter the logical station number which was specified for the communication setting in
LogicalStationNumber
Communication Setup Utility.
DeviceName Enter the start device of devices to be read.
Enter the logging interval.

6.1.1 Sample program for Excel

6.1 VBA Sample Programs
LoggingTiming (hh:mm:ss) 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.

button Start logging.

button Stop logging.

525
6.1.2 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.

(1) 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 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 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 the dialog box.

(2) Considerations for using the sample program

Before executing the sample program, set the communication settings in Communication Setup Utility.

(3) 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

526
 CHAPTER 6 SAMPLE PROGRAMS

(4) Screen
The following explains the settings on the sample program screen.

1 2

Item Description
Enter the logical station number which was specified for the communication setting in
LogicalStationNumber
Communication Setup Utility.
 (DeviceRead area) Display the device values of D0 to D9 of the programmable controller CPU.

6.1.2 Sample program for Excel (Reading/writing devices)

6.1 VBA Sample Programs
 (DeviceWrite area) Enter the values to be written into D0 to D9 of the programmable controller CPU.
Read the device values of D0 to D9 of the programmable controller CPU and display them on
button the DeviceRead area.
Write the device values entered into D0 to D9 of the DeviceWrite area to D0 to D9 of the
button programmable controller CPU.

527
6.1.3 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.

(1) 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 button to start logging.

5. Click the 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 552, CHAPTER 7 ERROR CODES)

(2) 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 button to stop logging, change the input value, and click

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

(3) 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

528
 CHAPTER 6 SAMPLE PROGRAMS

(4) Screen
The following explains the settings on the sample program screen.

Item Description
Enter the logical station number which was specified for the communication setting in
LogicalStationNumber
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.

button Start logging.

6.1.3 Sample program for Access

6.1 VBA Sample Programs
button Stop logging.

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

(1) 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 552, CHAPTER 7 ERROR CODES)

(2) 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.
• In this sample program, the device "D100" is used for the tank capacity, and the device "D101" is used for
the tank status.

(3) 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

530
 CHAPTER 6 SAMPLE PROGRAMS

(4) 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

Indicate the tank capacity.
Tank capacity Linked with the device "D100".
(Within the range of 0 device value 200)
Indicate the tank status.

6.2 VBScript Sample Program

Tank status Normal (device value = 0): Blue lamp ON Linked with the device "D101".
Error (device value <> 0): Red lamp ON

531
6.3 ASP Sample Programs

This sample program is a program to read programmable controller CPU data and device values using the ActUtlType
control.

(1) 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.

(2) 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 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 552, CHAPTER 7 ERROR CODES)
10. The data display screen repeats updating at the interval set for "MonitorTiming:".
11. Press the button to return to the initial screen.

(3) Considerations for using the sample program

• Before executing the sample program, set the communication settings in Communication Setup Utility.

(4) Sample file list

The sample program is installed in the following folder when the default pass is selected.

Folder name File name

Sample-E.asp
[User specified folder] - [Act] - [Samples] - [VBScript] - [SampleASP] SampleControl-E.asp
SampleMon-E.asp

532
 CHAPTER 6 SAMPLE PROGRAMS

(5) Screen
The following explains the settings on the sample program screen.

(a) 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.

6.3 ASP Sample Programs

DeviceSize Enter the number of points of the devices to be read.

button Start the monitor processing.

(b) 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.

533
 (c) 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.

button Return to the initial screen.

534
 CHAPTER 6 SAMPLE PROGRAMS

6.4 Visual Basic® .NET Sample Programs

6.4.1 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).

(1) 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 6
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.
5. Click the button to open the communication line after connecting the telephone line,
and read device values at the interval specified using the RedDeviceBlock 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 button to disconnect the telephone line after closing the communication

6.4.1 Modem communication sample program

6.4 Visual Basic® .NET Sample Programs
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
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 552, CHAPTER 7 ERROR CODES)

(2) 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 button to close the communication line, and click the button to resume
the communication.

535
 (3) 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

(4) 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.

button Open the communication line and start monitoring after connecting the telephone line.

button Disconnect the telephone line and stop monitoring after closing the communication line.

Acquire and display the error description and corrective action for the error code of
button "ReturnValue".

536
 CHAPTER 6 SAMPLE PROGRAMS

6.4.2 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".

(1) 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 6
before clicking the button.

3. Click the 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

button to display the 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

6.4.2 Read/Write sample program

6.4 Visual Basic® .NET Sample Programs
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

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
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 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 button.
10. If an error occurs during the process, an error code is displayed on the "Return Code" box in the
"Output" frame.
11. When an error occurs, perform the troubleshooting corresponds to the error code. (Page 552,
CHAPTER 7 ERROR CODES)

12. Click the button to close the communication line.

537
 (2) 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 button,

change the control, and click the button to reopen the line.

(3) 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

538
 CHAPTER 6 SAMPLE PROGRAMS

(4) Screen
The following explains the settings on the sample program screen.
<Sample> <Sample_References>

<SampleDot> <Sample_ReferencesDot>

6.4.2 Read/Write sample program

6.4 Visual Basic® .NET Sample Programs

539
 Item Description
Any of ActUtlType, ActProgType,
Select the control to be used.
or DotUtlType
"Control" frame
Enter the logical station number which was specified for
LogicalStationNumber
communication setting in Communication Setup Utility.

button Open the communication line.

button Close the communication line.

DeviceName Enter the device name for reading/writing devices randomly.

Enter the number of device points for reading/writing devices
DeviceSize
randomly.
DeviceData Enter the device value for writing devices randomly.
Read device data randomly from the programmable
controller CPU to the data source entered into the
"Random Read/Write" frame "DeviceName" and "DeviceSize" text boxes in the same
button
frame, and display the data on the "Data" text box in the
"Output" frame.
Write device data randomly to the programmable controller
CPU from the data source entered into the "DeviceName",
button "DeviceSize", and "DeviceData" text boxes in the same
frame.
DeviceName Enter the device name for reading/writing devices in bulk.
Enter the number of device points for reading/writing devices
DeviceSize
in bulk.
DeviceData Enter the device values for writing devices in bulk.
Read device data in bulk from the programmable controller
"Block Read/Write" frame CPU to the data source entered into the "DeviceName" and
button "DeviceSize" text boxes in the same frame, and display the
data on the "Data" text box in the "Output" frame.
Write device data in bulk to the programmable controller
CPU from the data source entered into the "DeviceName",
button "DeviceSize", and "DeviceData" text boxes in the same
frame.
DeviceName Enter the device name as an event occurrence condition.
Enter the number of device points as an event occurrence
DeviceSize
condition.
MonitorCycle Enter the event monitoring interval.
DeviceData Enter the device value as an event occurrence condition.
Register the on-device status/event to the data source
"Status Entry/Free" frame
entered into the "DeviceName", "DeviceSize",
"MonitorCycle", and "DeviceData" text boxes in the same
button frame. When the registered event occurrence condition is
satisfied, the event data is displayed on the "Data" text box
of the "Output" frame.

button Delete the registered on-device status/event.

Return Code Display the method execution result.

"Output" frame
Data Display the read device values.

540
 CHAPTER 6 SAMPLE PROGRAMS

6.4.3 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).

(1) 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

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 button in the
same frame.(The data write function is executed within the range of D0 to D9, regardless of the
6
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 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 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 button in the "32bit integer" frame. Data from the

6.4.3 Type conversion sample program

6.4 Visual Basic® .NET Sample Programs
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 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 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 552, CHAPTER 7 ERROR CODES)

9. Click the button to close the communication line.

(2) 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.

541
 (3) 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

(4) Screen
The following explains the settings on the sample program screen.

Item Description
Enter the logical station number which was specified for the
LogicalStationNumber
communication setting in Communication Setup Utility.

button Open the communication line.

button Close the communication line.

Write the ASCII character data, which was entered into the upper text
button box in the frame, to the programmable controller CPU.
"ASII character" frame
Display the ASCII character data, which was read from the
button programmable controller CPU, on the lower text box in the frame.
Write the 32-bit integer data, which was entered into the upper text box
button in the frame, to the programmable controller CPU.
"32bit integer" frame
Display the 32-bit integer data, which was read from the programmable
button controller CPU, on the lower text box in the frame.
Write the real number data, which was entered into the upper text box in
button the frame, to the programmable controller CPU.
"Real number" frame
Display the real number data, which was read from the programmable
button controller CPU, on the lower text box in the frame.

542
 CHAPTER 6 SAMPLE PROGRAMS

6.5 Visual C++® .NET Sample Programs

6.5.1 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) and Visual C++® .NET (Visual Studio®
2010).

(1) How to use the sample program

The operation is the same as that for Visual Basic® .NET (Visual Studio® 2005). (Page 537, Section 6.4.2 (1)
How to use the sample program)

(2) Considerations for using the sample program 6

The considerations are the same as those for Visual Basic® .NET (Visual Studio® 2005). (Page 538, Section
6.4.2 (2) Considerations for using the sample program)

(3) Sample file list

The sample program is installed in the following folder when the default pass is selected.

(a) For Visual C++® .NET (Visual Studio® 2005)

Folder name File name
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [Sample2005] Sample2005.sln

6.5.1 Read/Write sample program

6.5 Visual C++® .NET Sample Programs
[User specified folder] - [Act] - [Samples] - [Vc.NET] -
Sample_References2005.sln
[Sample_References2005]
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [SampleDot2005] Sample2005.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] -
Sample_References2005.sln
[Sample_ReferencesDot2005]

(b) 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.sln
[Sample_References2010]
[User specified folder] - [Act] - [Samples] - [Vc.NET] - [SampleDot2010] Sample2010.sln
[User specified folder] - [Act] - [Samples] - [Vc.NET] -
Sample_References2010.sln
[Sample_ReferencesDot2010]

(4) Screen
The settings on the screen are the same as those for Visual Basic® .NET (Visual Studio® 2005).
(Page 539, Section 6.4.2 (4) Screen)

543
6.5.2 Troubleshooting function sample program

This sample program is a program to perform the troubleshooting function using the DotSupportMsg control.

(1) 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 button to display the error description and corrective action on the text
box for displaying the error description.
4. Displayed error descriptions and corrective actions are the same as the descriptions on Page
552, CHAPTER 7 ERROR CODES.
5. Click the button to exit the sample program.

(2) Considerations for using the sample program

For error codes to be entered into the "ErrorCode" text box, enter the error code described on Page 552,
Section 7.1 Error Codes Returned by Controls (0x********), or enter it in decimal number.

(3) 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

544
 CHAPTER 6 SAMPLE PROGRAMS

(4) Screen
The following explains the settings on the sample program screen.

Item Description
ErrorCode Enter the error code.
Read the error description and corrective action of the error code entered into
button
the "ErrorCode" text box.

button Exit the sample program.

Display the error description and corrective action of the error code entered
 (Error definition displaying text box)
into the "ErrorCode" text box.

6.5.2 Troubleshooting function sample program

6.5 Visual C++® .NET Sample Programs

545
6.6 Visual C#® .NET Sample Programs

6.6.1 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).

(1) How to use the sample program

The operation is the same as that for Visual Basic® .NET (Visual Studio® 2005). (Page 537, Section 6.4.2 (1)
How to use the sample program)

(2) Considerations for using the sample program

The considerations are the same as those for Visual Basic® .NET (Visual Studio® 2005). (Page 538, Section
6.4.2 (2) Considerations for using the sample program)

(3) 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] - [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

(4) Screen
The settings on the screen are the same as those for Visual Basic® .NET (Visual Studio® 2005).
(Page 539, Section 6.4.2 (4) Screen)

546
 CHAPTER 6 SAMPLE PROGRAMS

6.7 Visual C++ ® .NET (MFC) Sample Programs

This section explains the sample programs for Visual C++ ® .NET (MFC) which were created using the dispatch
interface and the custom interface.

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

(1) How to use the sample program

1. Load the form and select the control to be used.

2. Click the button to open the communication line through Ethernet

communication.
3. Click the button to display the model code and the CPU model of the currently-
6
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 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 button to write the device value.
6. Click the 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.

6.7.1 Dispatch interface

6.7 Visual C++ ® .NET (MFC) Sample Programs
8. When an error occurs, perform the troubleshooting corresponds to the error code. (Page 552,
CHAPTER 7 ERROR CODES)

(2) 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
button, change the control, and reopen the line.

547
 (3) 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] sampleENG.sln

(4) Screen
The following explains the settings on the sample program screen.

Item Description
Control Select the control to be used.

button Open the communication line.

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.

button Close the communication line.

button Read the data of the device entered into the "Device Name" text box.

button Write the data of the device entered into the "Device Name" text box.

Return Display the function execution result.

Upper Display the CPU model code or the read device value.
Output
Lower Display the CPU model.

548
 CHAPTER 6 SAMPLE PROGRAMS

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

(1) How to use the sample program

The operation is the same as that for the dispatch interface.(Page 547, Section 6.7.1 (1) How to use the
sample program)

(2) 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
button, change the control, and reopen the line.
6
(3) Sample file
The sample files are installed into the following folders at default installation.

Folder name File name

[User specified folder] - [Act] - [Samples] - [Vc] - [CustomSampleENG] CustomSampleENG.sln

(4) Screen
The settings on the screen are the same as those for the dispatch interface. (Page 548, Section 6.7.1 (4)
Screen)

6.7.2 Custom interface

6.7 Visual C++ ® .NET (MFC) Sample Programs

549
6.7.3 Troubleshooting function sample program

This sample program is a program to perform the troubleshooting function using the ActSupportMsg control.

(1) 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 button to display the error description and corrective action on the text
box for displaying the error description.
4. Displayed error descriptions and corrective actions are the same as the descriptions on Page
552, CHAPTER 7 ERROR CODES.
5. Click the button to exit the sample program.

(2) Considerations for using the sample program

For error codes to be entered into the "ErrorCode" text box, enter the error code described on Page 552,
Section 7.1 Error Codes Returned by Controls (0x********), or enter it in decimal number.

(3) 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_SupportENG.sln

550
 CHAPTER 6 SAMPLE PROGRAMS

(4) Screen
The following explains the settings on the sample program screen.

Item Description
ErrorCode Enter the error code.
Read the error description and corrective action of the error code entered into
button

6.7.3 Troubleshooting function sample program

6.7 Visual C++ ® .NET (MFC) Sample Programs
the "ErrorCode" text box.

button Exit the sample program.

Display the error description and corrective action of the error code entered
 (Error definition displaying text box)
into the "ErrorCode" text box.

551
CHAPTER 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.
101
• Take measures against noise.
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.
• Check the cable connection.
106 The line was disconnected.
• 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.
• Check the property timeout value.
• Check the settings in the communication settings utility.
• Check the programmable controller, unit settings, state
0x01010002 Timeout error
of the cable, etc.
• Close and Open again.
• Exit the program and restart the personal computer.
• Check the system noise.
• Check the property timeout value.
• Check the settings in the communication settings utility.
0x01010005 Message error • Check the programmable controller, unit settings, status
of the cable, etc.
• Close and Open again.
• Exit the program, restart the personal computer.
Programmable controller No. error • Check the station number set on the communication
0x01010010 Communication could not be made with the specified setup utility.
station number. • Check the station number set to ActStationNumber.
• Check if the correct CPU type setting is done.
• Check the programmable controller, unit settings, status
Mode error
0x01010011 of the cable, etc.
Command not supported.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
0x01010012 Special Unit Specification error • Check the specified address of the special unit.
• Check that the system configuration is not an
Other data error unsupported configuration.
0x01010013
Communication cannot be made for some cause. • Check that the CPU type setting is correct.
• Exit the program and restart the personal computer.
Remote request error
• Cancel the remote operation being performed in the
0x01010018 Remote operation is being performed in the path different
other path.
from the communicating path.

552
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

• Check that reset operation is not performed for the other
Link error end of communication, the control station (master
0x01010020
Link communications could not be made. station) or the station passed through by routing.
• Check that the network parameter setting is correct.
Special Unit Bus error • Repair or exchange the special unit under consideration.
0x01010021 There is no response from the special unit under • Exit the program and restart the personal computer.
consideration. • Reinstall MX Component.
No command error
0x01800001 • The corresponding method does not support.
The method does not support.
• Exit the program and restart the personal computer.
• When using an interface board for personal computer,
0x01800002 Memory lock error
increase the minimum working set size of the personal
computer.*1
• Exit the program and restart the personal computer.
• Exit other programs and secure free memory area.
0x01800003 Memory securing error • When using an interface board for personal computer,
increase the minimum working set size of the personal
computer.*1
• Exit the program and restart the personal computer.
0x01800004 DLL load error • Exit other programs and secure free memory area.
• Reinstall MX Component. 7
• Exit the program and restart the personal computer.
0x01800005 Resource securing error
• Exit other programs and secure free memory area.
• Execute again after the other object completes the
Resource Timeout error communication.
0x01801001 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.

7.1 Error Codes Returned by Controls

0x01801002 Multi-line open error
• Exit the program and restart the personal computer.
0x01801003 Open not yet executed
0x01801004 Open Type error • Exit the program and restart the personal computer.
0x01801005 Specified port error • Reinstall MX Component.
• Check that the actual system configuration matches to
the settings in the communication settings utility or the
0x01801006 Specified module error values of the properties.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
• Check the CPU type set to ActCpuType.
• Check that the system configuration is not an
unsupported configuration.
0x01801007 Specified CPU error
• 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.
Registry open failure • Exit the program and restart the personal computer.
0x01801009
Failed while opening data key of the registry. • Reinstall MX Component.
• Recheck the ActPacketType.
Packet Type error
0x0180100A • Exit the program and restart the personal computer.
The packet type specified is incorrect.
• Reinstall MX Component.
*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

553
 Error code Error description Corrective action
Protocol Type error
0x0180100B
The protocol specified is incorrect.
• Exit the program and restart the personal computer.
0x0180100C Registry search failure
• Reinstall MX Component.
0x0180100D GetProcAddress failure
0x0180100E DLL non-load error
Another Object in execution
0x0180100F Method cannot be executed because of exclusive control in • Execute again after some time.
progress.
Device error
0x01802001 The device character string specified in the method is an • Review the device name.
unauthorized device character string.
Device number error
0x01802002 The device character string number specified in the • Review the device number.
method is an unauthorized device number.
• Exit the program and restart the personal computer.
0x01802003 Program Type error
• Reinstall MX Component.
• Check the module side sumcheck setting.
• Check the sumcheck property of the control.
Sumcheck error
0x01802004 • Check the cable.
The sumcheck value of the received data is abnormal.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
• Check the number of points specified in the method.
Size error • Review the system, e.g. programmable controller CPU,
0x01802005 The number of points specified in the method is module setting and cable status.
unauthorized. • Exit the program and restart the personal computer.
• Reinstall MX Component.
Block number error
• Review the block specifying number in the device
0x01802006 The block specifying number in the device character string
character string specified in the method.
specified in the method is unauthorized.
• Review the system, e.g. programmable controller CPU,
Receive data error module setting and cable status.
0x01802007
The data received is abnormal. • Check the cable.
• Exit the program and restart the personal computer.
0x01802008 Write Protect error
• Exit the program and restart the personal computer.
0x01802009 Reading Parameters error
• Reinstall MX Component.
0x0180200A Writing Parameters error
• Set the correct CPU type as the CPU type of the
Programmable controller type mismatch property.
The CPU type set to the property and the CPU type set on • Set the correct CPU type on the communication settings
0x0180200B
the communication settings utility do not match the CPU utility.
type on the other end of communication. • Review the system, e.g. programmable controller CPU,
module setting and cable status.
Request Cancel error
0x0180200C
The request was cancelled while being processed.
Drive Name error
0x0180200D
The specified drive name is incorrect.
Beginning Step error • Exit the program and restart the personal computer.
0x0180200E
The beginning step specified is incorrect. • Reinstall MX Component.
Parameter Type error
0x0180200F
The parameter type is incorrect.
File Name error
0x01802010
The file name is incorrect.

554
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

Status error
0x01802011
The status of Registration/Cancellation/Setting is incorrect.
0x01802012 Detailed Condition Field error • Exit the program and restart the personal computer.
0x01802013 Step Condition error • Reinstall MX Component.
0x01802014 Bit Device Condition error
0x01802015 Parameter Settings error
• Check the telephone exchange number.
Error in specifying telephone exchange number.
• Check if the method being executed is supported or not.
0x01802016 Method does not support the operations corresponding to
• Check the system configuration such as programmable
the specified telephone exchange number.
controller, unit, etc.
0x01802017 Keyword error
0x01802018 Read/Write Flag error
• Exit the program and restart the personal computer.
0x01802019 Refresh Method error
• Reinstall MX Component.
0x0180201A Buffer Access Method error
0x0180201B Start Mode/Stop Mode error
Written clock data error
0x0180201C Clock data specified for write cannot be written properly • Review the clock data to be written.
since that data is in error.
Online clock data write error

0x0180201D
Write of clock data failed. • Place the programmable controller CPU in the STOP 7
Clock data cannot be written since the programmable status.
controller CPU is during RUN.
0x0180201E ROM drive error
• Exit the program and restart the personal computer.
While Tracing error
0x0180201F • Reinstall MX Component.
Invalid operation was carried out during trace.
• Check the value of the first I/O number specified in the
First I/O number error method.

7.1 Error Codes Returned by Controls

0x01802020 The first I/O number specified in the method is an • Using the GPP function, check the programmable
unauthorized value. controller CPU parameters (I/O assignment).
• Exit the program and restart the personal computer.
First address error • Check the value of the buffer address specified in the
0x01802021 The buffer address specified in the method is an method.
unauthorized value. • Exit the program and restart the personal computer.
0x01802022 Pattern error
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 • Exit the program and restart the personal computer.
0x0180202A Signal Flow error • Reinstall MX Component.
0x0180202B Version Control error
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

555
 Error code Error description Corrective action
0x01802032 Specified Unit error
0x01802033 Error check flag error
0x01802034 Step RUN operation error
• Exit the program and restart the personal computer.
0x01802035 Step RUN data error
• Reinstall MX Component.
0x01802036 During Step RUN error
Write error while running program corresponding to
0x01802037
E2PROM
Clock data read/write error
The clock data read/write method was executed for the
0x01802038 • Do not execute clock data read/write.
programmable controller CPU which does not have the
clock devices.
0x01802039 Trace not completed error
0x0180203A Registration Clear Flag error
• Exit the program and restart the personal computer.
0x0180203B Operation error
• Reinstall MX Component.
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 programmable controller error
0x01802041 Motion programmable controller 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
• Exit the program and restart the personal computer.
0x0180204A Insufficient memory error
• Reinstall MX Component.
0x0180204B Back up drive ROM error
0x0180204C Block size error
0x0180204D Detached during RUN state error
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
Tracking cable error
• Reexamine the system such as the programmable
0x01802057 The tracking cable is faulty.
controller CPU, module setting and cable status.
The programmable controller CPU status is error.
Keyword protection error
0x0180205C • Disable the keyword and execute again.
Programmable controller is protected by the key word.
Keyword disable error
0x0180205D • Input a correct keyword.
The inputted keyword is wrong.

556
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

Keyword protecting error
• Execute again or re-switch the power of the
0x0180205E Programmable controller did not accept the protecting
programmable controller.
command.
Keyword entry error
0x0180205F
An illegal character is included in the inputted keyword.
• Input a correct keyword.
Keyword deletion error
0x01802060
The inputted keyword is wrong.
Received packet CRC check error
0x01802062
An error occurred in CRC check for receive packet data.
Received packet CRC check error • Execute the communication process again.
0x01802063 An error occurred in CRC check for whole data file of
receive packet.
0x01802064 FX Series programmable controller connection error • Please contact out telephone center.
Online change program error
• Execute the online change after turning the
0x01802070 No target program for online change exists in the
programmable controller CPU to STOP.
programmable controller CPU.
Ether direct communication multiple response receive error
0x01802071 Multiple responses were received during Ether direct
communication. • Check that the personal computer and the
Ether direct communication error programmable controller CPU are in a one-to-one
Cannot communicate because the programmable connection. 7
0x01802072
controller CPU is being accessed by another personal
computer during Ether direct communication.
Programmable controller CPU search response error
The number of responses in the programmable controller • Reduce the number of programmable controllers on the
0x01802073
CPU search exceeded the maximum number to be network to 1024 or less.
searched.
• Disconnect the cable and connect it to the currently

7.1 Error Codes Returned by Controls

Redundant system other system connection diagnostics disconnected programmable controller CPU.
0x01802074
error • Or, change the redundant CPU specification to the self
system.
Multiple Open error • Exit the program and restart the personal computer.
0x01808001
Open method was executed while it was open. • Execute any method other than Open.
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
0x01808002 • Make communication settings again on the
set on the communication settings utility are unauthorized
communication settings utility.
values.
Driver not yet started
0x01808003 • Start the driver.
The network board driver is not started.
0x01808004 Error in overlap event generation
MUTEX generation error
0x01808005 • Exit the program and restart the personal computer.
Creation of MUTEX to exercise exclusive control failed.
• Reinstall MX Component.
Error in socket object generation
0x01808006
Socket object could not be created
• Check for a running application which uses the same
port number.
• Retry after changing the port number value of the
property.
• Retry after changing the port number value on the
Socket object generation error
0x01808007 communication settings utility.
Creation of the Socket object failed.
• 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.

557
 Error code Error description Corrective action
• Review the IP address and port number values of the
properties.
Port connection error • Review the port number value on the communication
0x01808008 Establishment of connection failed. 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.
COM port handle error
The handle of the COM port cannot be acquired. • Check for an application which uses the COM port.
0x01808009
The COM port object cannot be copied. • Exit the program and restart the personal computer.
The SOCKET object cannot be copied.
• Check for an application which uses the COM port.
Buffer size setting error
0x0180800A • Make COM port setting on the control panel of the OS.
Setting of the COM port buffer size failed.
• Exit the program and restart the personal computer.
• Check for an application which uses the COM port.
DCB value acquisition error
0x0180800B • Make COM port setting on the control panel of the OS.
Acquisition of the COM port DCB value failed.
• Exit the program and restart the personal computer.
• Check for an application which uses the COM port.
DCB setting error
0x0180800C • Make COM port setting on the control panel of the OS.
Setting of the COM port DCB value failed.
• Exit the program and restart the personal computer.
• Review the time-out value of the property.
• Review the time-out value on the communication
Time-out value setting error settings utility.
0x0180800D
Setting of the COM port time-out value failed. • 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.
Shared memory open error • Check whether the GX Simulator has started.
0x0180800E
Open processing of shared memory failed. • Exit the program and restart the personal computer.
0x01808101 Duplex close error
Handle close error
0x01808102
Closing of the COM port handle failed. • Exit the program and restart the personal computer.
Driver close error
0x01808103
Closing of the driver handle failed.
0x01808104 Overlap Event Close error
• Exit the program and restart the personal computer.
0x01808105 Mutex Handle Close error
• Reinstall MX Component.
0x01808106 COM Port Handle Close error
• Review the system, e.g. programmable controller CPU,
module setting and cable status.
• Make COM port setting on the control panel of the OS.
Send error
0x01808201 • Make Ethernet board and protocol settings on the control
Data send failed.
panel.
• Retry the method.
• Exit the program and restart the personal computer.
Send data size error
0x01808202 • Exit the program and restart the personal computer.
Data send failed.
Queue clear error • Exit the program and restart the personal computer.
0x01808203
Clearing of the COM port queue failed. • Perform Close once and execute Open again.
• Review the system, e.g. programmable controller CPU,
module setting and cable status.
• Review the time-out value of the property.
Receive error
0x01808301 • Review the time-out value on the communication
Data receive failed.
settings utility.
• Retry the method.
• Exit the program and restart the personal computer.

558
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

0x01808302 Not Sent error • Exit the program and restart the personal computer.
0x01808303 Error in retrieving Overlap Event • Reinstall MX Component.
Receive buffer size shortage
0x01808304 Receive data was larger than the receive buffer size
prepared for the system. • Exit the program and restart the personal computer.
Control error
0x01808401
Changing of the COM port communication control failed.
• Exit the program and restart the personal computer.
0x01808402 Signal Line Control error
• Reinstall MX Component.
Signal line specifying error
0x01808403 • Exit the program and restart the personal computer.
Changing of the COM port communication control failed.
• Execute Open.
0x01808404 Open not yet executed
• Exit the program and restart the personal computer.
Communication parameter error
• Review the data bit and stop bit values of the properties.
0x01808405 The data bit and stop bit combination of the properties is
• Set them again on the communication settings utility.
unauthorized.
Transmission speed value specifying error • Review the transmission speed value of the property.
0x01808406
The transmission speed of the property is unauthorized. • Set it again on the communication settings utility.
Data length error • Review the data bit value of the property.
0x01808407
The data bit value of the property is unauthorized. • Set it again on the communication settings utility.
7
Parity specifying error • Review the parity value of the property.
0x01808408
The parity value of the property is unauthorized. • Set it again on the communication settings utility.
Stop bit specifying error • Review the stop bit value of the property.
0x01808409
The stop bit value of the property is unauthorized. • Set it again on the communication settings utility.
Communication control setting error • Review the control value of the property.
0x0180840A
The control value of the property is unauthorized. • Set it again on the communication settings utility.
• Review the time-out value of the property.

7.1 Error Codes Returned by Controls

• Set it again on the communication settings utility.
• Review the system, e.g. programmable controller CPU,
Time-out error module setting and cable status.
0x0180840B Though the time-out period had elapsed, data could not be • Check if communication can be established with the Ping
received. command.
• Retry the method.
• Perform Close once and execute Open again.
• Exit the program and restart the personal computer.
0x0180840C Connect error
0x0180840D Duplex connect error
Attach failure
0x0180840E • Exit the program and restart the personal computer.
Attaching of the socket object failed.
Signal line status acquisition failure
0x0180840F
Acquisition of the COM port signal line status failed.
CD signal line OFF • Review the system, e.g. programmable controller CPU,
0x01808410 The CD signal on the other end of communication is in the module setting and cable status.
OFF status. • Exit the program and restart the personal computer.
0x01808411 Password mismatch error • Check the remote password of the property.
• Exit the program and restart the personal computer.
0x01808412 TEL Communication error
• Reinstall MX Component.
USB driver load error
0x01808501 • Exit the program and restart the personal computer.
Loading of the USB driver failed.
• Reinstall MX Component.
USB driver connect error
0x01808502 • Check USB driver installation.
Connection of the USB driver failed.

559
 Error code Error description Corrective action
USB driver send error • Review the system, e.g. programmable controller CPU,
0x01808503
Data send failed. module setting and cable status.
• Make USB setting on the control panel (device manger)
USB driver receive error of the OS.
0x01808504
Data receive failed. • Retry the method.
• Exit the program and restart the personal computer.
• Recheck the timeout value.
0x01808505 USB Driver Timeout error • Exit the program and restart the personal computer.
• Reinstall MX Component.
• Make USB setting on the control panel (device manger)
USB driver initialization error
0x01808506 of the OS.
Initialization of the USB driver failed.
• Exit the program and restart the personal computer.
• Disconnect the cable once, then reconnect.
Other USB error
0x01808507 • Exit the program and restart the personal computer.
Error related to data send/receive occurred.
• Reinstall MX Component.
GX Works2 uninstallation error
0x01809000 The error occurred by retrieving the installation passing of • Reinstall GX Works2.
GX Simulator2.
GX Simulator2 unstart error
0x01809001 • Start GX Simulator2.
GX Simulator2 did not start.
0x01809002 GX Simulator2 start error
0x01809003 GX Simulator2 start time-out error
0x01809004 GX Simulator2 stop error
0x01809005 GX Simulator2 start error
0x01809007 GX Simulator2 stop error
GX Simulator2 start error
Because it had reached upper bounds of the number of
0x01809008
simulations that was able to be started at the same time, it
was not possible to start.
GX Simulator2 start error
0x01809009 The simulation of only one project that can be started has • Exit the program and restart the personal computer.
started. • Reinstall MX Component.
GX Simulator2 start information illegal error
0x01809010 The error occurred because it was not able to secure the
memory area to allocate GX Simulator2 start information.
GX Simulator2 start error
Because it had reached upper bounds of the number of
0x01809021
simulations that was able to be started at the same time, it
was not possible to start.
GX Simulator2 start error
The simulation of other CPU was not able to begin
0x01809022
because the simulation of the project of FXCPU had
already been begun.
Points Exceeded error • Reduce the no. of points registered by the monitor.
0x02000001 The number of points registered in the monitoring server is • Exit the program and restart the personal computer.
very high. • Reinstall MX Component.
Shared memory creation error
0x02000002 • Exit the program and restart the personal computer.
Failed in creating shared memory.
• Reinstall MX Component.
0x02000003 Shared memory access error
• Close the other applications.
Memory Secure error • Increase the system memory.
0x02000004
Failed in securing memory for the monitoring server. • Exit the program and restart the personal computer.
• Reinstall MX Component.

560
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

• Register the monitor in the monitoring server.
Device Not Registered error
0x02000005 • Exit the program and restart the personal computer.
Monitor has not been registered
• Reinstall MX Component.
• Start the Monitoring Server.
Monitoring Server Startup error
0x02000006 • Exit the program and restart the personal computer.
Monitoring Server is not started.
• Reinstall MX Component.
• Try to retrieve the value again after waiting for a fixed
Yet to retrieve Device Value error amount of time.
0x02000010
Monitoring is not yet completed. • Exit the program and restart the personal computer.
• Reinstall MX Component.
Command not Supported.
0x03000001
Command is not supported.
Memory Lock error
0x03000002
Failed while locking memory.
Error Securing Memory • Exit the program and restart the personal computer.
0x03000003
Failed in securing the memory. • Reinstall MX Component.
DLL read error
0x03000004
Failed in reading DLL.
Error in securing Resources.
0x03000005
Failed in securing the resources.
• Check if there is enough space on the hard disk. 7
File Creation error
0x03010001 • Exit the program and restart the personal computer.
Failed in creating the file.
• Reinstall MX Component.
File Open error
0x03010002
Failed to open the file.
Buffer Size error • Exit the program and restart the personal computer.
0x03010003
The buffer size specified is either incorrect or not enough. • Reinstall MX Component.
SIL Sentence formation error

7.1 Error Codes Returned by Controls

0x03010004
SIL sentence formation is incorrect.
• Specify a shorter filename.
Filename error
0x03010005 • Exit the program and restart the personal computer.
The specified filename is too long.
• Reinstall MX Component.
• Check the filename.
File does not exist error • Check if the file exists or not.
0x03010006
The specified file does not exist. • Exit the program and restart the personal computer.
• Reinstall MX Component.
File Structure error • Exit the program and restart the personal computer.
0x03010007
The data structure in the specified file is incorrect. • Reinstall MX Component.
File already exists error
0x03010008 • Check the filename.
The specified file already exists.
• Exit the program and restart the personal computer.
File does not exist error
0x03010009 • Reinstall MX Component.
The specified file does not exist.
File Deletion error
0x0301000A
The specified file could not be deleted. • Exit the program and restart the personal computer.
Multiple Open error • Reinstall MX Component.
0x0301000B
The specified project has been opened twice.
• Check the filename.
Filename error
0x0301000C • Exit the program and restart the personal computer.
The specified filename is incorrect.
• Reinstall MX Component.
File Read error
0x0301000D
Failed in reading the file. • Exit the program and restart the personal computer.
File Write error • Reinstall MX Component.
0x0301000E
Failed in writing the file.

561
 Error code Error description Corrective action
File Seek error
0x0301000F
File seek failed.
File Close error
0x03010010
Failed while closing the file.
Folder Creation error
0x03010011
Failed while creating the folder.
File Copy error
0x03010012
Failed while copying the file.
Project Path error
0x03010013
The length of the project path is incorrect.
Project Type error
0x03010014
The project type is incorrect.
File Type error
0x03010015
The file type is incorrect.
Sub-File Type error
0x03010016
The sub-file type is incorrect.
Insufficient Disk space error
0x03010017
The disk space is insufficient.
Multiple Open error
0x03020002
Tried to open DBProduct more than once.
Not Opened error
0x03020003
DBProduct is not opened.
Extract error
0x03020004
DBProduct is not extracted.
Parameter error
0x03020010 • Exit the program and restart the personal computer.
The parameters of DBProduct are incorrect.
• Reinstall MX Component.
Language error
0x03020011
The language parameter is incorrect.
Error in specifying Maker
0x03020012
The maker parameter is incorrect.
Error in specifying Unit
0x03020013
The unit parameter is incorrect.
SQL Parameter error
0x03020014
SIL, SQL Parameter of DBProduct is incorrect.
SIL Sentence formation error
0x03020015
SIL sentence formation is incorrect.
Field Key Input error
0x03020016
The field key entered is incorrect.
Record Data Construction error.
0x03020050
Failed in reconstructing the record data of DBProduct.
Error Retrieving Record Data
0x03020060
Failed while retrieving DBProduct record data.
Last Record error
0x03020061 Cannot retrieve the next record since the current record is
the last record.
0x03FF0000 Initialization error
0x03FF0001 Not Initialized error
0x03FF0002 Multiple Initialization error
0x03FF0003 Workspace Initialization error
0x03FF0004 Database Initialization error
0x03FF0005 Recordset Initialization error

562
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

0x03FF0006 Error Closing Database
0x03FF0007 Error Closing Recordset
Database Not Opened error
0x03FF0008
Database is not opened.
Recordset Not Opened error
0x03FF0009
Recordset is not opened.
Table Initialization error
0x03FF000A
Failed in initializing TtableInformation table.
Table Initialization error
0x03FF000B
Failed in initializing TfieldInformation table.
Table Initialization error
0x03FF000C
Failed in initializing TrelationInformation table.
Table Initialization error
0x03FF000D
Failed in initializing Tlanguage table.
Table Initialization error
0x03FF000E • Exit the program and restart the personal computer.
Failed in initializing Tmaker table.
• Reinstall MX Component.
Table Initialization error
0x03FF000F
Failed in initializing TOpenDatabase table.
0x03FF0010 Field Value error
0x03FF0011 Field Value error 7
Exit error
0x03FF0012
Failed to exit the database.
Moving Record error
0x03FF0100
Failed while moving the record.
Retrieving Record Count error
0x03FF0101
Failed to retrieve the record count.
Retrieving Field Value error

7.1 Error Codes Returned by Controls

0x03FF0110
Failed in retrieving the field value.
Setting Field Value error
0x03FF0111
Failed in setting the field value.
0x03FFFFFF Other errors
• Check the CPU type set to ActCpuType.
No command error • Check whether the system configuration is supported or
0x04000001 The specified CPU type cannot be used to perform not.
processing. • Exist the program and restart the personal computer.
• Reinstall MX Component.
Memory lock error
0x04000002
Failed in locking memory. • Exit the program and restart the personal computer.
Securing Memory error • Reinstall MX Component.
0x04000003
Failed in securing the memory.
• Check for the deleted or moved installation file of MX
Internal server DLL load error Component.
0x04000004
Start of the internal server failed. • Exit the program and restart the personal computer.
• Reinstall MX Component.
Securing Resources error
0x04000005
Failed in securing the resources.
Error Loading Main Object
0x04000006 • Exit the program and restart the personal computer.
Failed in reading the file.
• Reinstall MX Component.
Error Loading Conversion Table
0x04000007
Failed in reading table data.
0x04000100 Incorrect Intermediate Code Size error

563
 Error code Error description Corrective action
Intermediate Code Not Converted error
0x04010001 The converted machine code for one command is more
than 256 bytes.
Intermediate Code Completion error
0x04010002 Intermediate code area of the code to be converted ended
abruptly.
Insufficient Intermediate Code error
0x04010003 The intermediate code of the code to be converted was
insufficient.
Intermediate Code Data error
0x04010004
The intermediate code to be converted is incorrect.
Intermediate Code Structure error
0x04010005
The number of steps in the intermediate code is incorrect.
Error in Number of Steps
0x04010006 The number of steps in comment intermediate code is
incorrect.
Insufficient Storage Space for Machine Code error
0x04010007
The storage space for machine code is insufficient.
Other errors
0x04010008 (Other errors generated during the conversion of
Intermediate code to machine code.)
Machine Code Not Converted error
0x04011001 The converted intermediate code for one command is more
than 256 bytes.
Machine Code Completion error
0x04011002
The machine code area to be converted ended abruptly. • Exit the program and restart the personal computer.
Abnormal Machine Code • Reinstall MX Component.
0x04011003 Could not convert since the machine code to be converted
was abnormal.
Insufficient Storage Space for Intermediate Code error
0x04011004
The storage area for intermediate code is insufficient.
Other errors
0x04011005 Other errors generated while converting machine code to
Intermediate code.
Text Code Not Converted error
0x04020001 The converted intermediate code for one command is more
than 256 bytes.
No Input error
0x04020002
The input list code is insufficient.
Command error
0x04020003 The command name of list code to be converted is
incorrect.
Device error
0x04020004
The device name of list code to be converted is incorrect.
Device Number error
0x04020005 The device number of the list code to be converted is out of
range.
Conversion error
0x04020006 The list code to be converted conversion could not be
identified.
Text Data error
0x04020007
The list code to be converted is incorrect.

564
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

Error in SFC Operation Output
0x04020008
The output command of SFC operation is incorrect.
SFC Shift Condition error
0x04020009
SFC shift condition command is incorrect.
Error in Statements between lines
0x0402000A
The statements entered between lines are incorrect.
P.I Statement error
0x0402000B
The P.I statement entered is incorrect.
Note error
0x0402000C
The Note entered is incorrect.
Comment error
0x0402000D
The comment entered is incorrect.
Other errors
0x0402000E (Other errors generated during the conversion of list to
Intermediate code)
Intermediate Code Not Converted error
0x04021001 The converted list code for one command has exceeded
256 bytes.
Intermediate Code Area Full error
0x04021002
Intermediate code area to be converted is full.
Command error
7
0x04021003 The command specified by the intermediate code to be
converted is incorrect.
Device error
0x04021004 The device specified in the intermediate code to be
• Exit the program and restart the personal computer.
converted is incorrect.
• Reinstall MX Component.
Intermediate Code error
0x04021005 The structure of intermediate code to be converted is

7.1 Error Codes Returned by Controls

incorrect.
Insufficient List Storage Space error
0x04021006
The space for storing the converted list code is insufficient.
Other errors
0x04021007 (Other errors generated during the conversion of
intermediate code to list)
Not Converted error
0x04030001 The storage space for converted intermediate code is
insufficient.
Bad Circuit Creation error
0x04030002 The character memory circuit is not completed in a
sequence.
Specified Circuit Size Exceeded
0x04030003
Specified circuit size is too big.
Incorrect Return Circuit error
0x04030004 There is no consistency before and after the return circuit.
The setting for the return circuit is too high.
Other errors
0x04030005 (Other errors generated while converting from Character
Memory to Intermediate Code)
Not Converted error
0x04031001 The size (vertical/horizontal) of the character memory
specified is incorrect.

565
 Error code Error description Corrective action
Abnormal Command Code error
0x04031002 The command intermediate code to be converted is
incorrect.
Bad Circuit Creation error
0x04031003 Could not be converted to Sequence Circuit. There is no
END command.
Specified Circuit Size exceeded error
0x04031004
Specified circuit size is too big.
Fatal error
0x04031005
Fatal error has occurred.
Insufficient number of storage blocks error
0x04031006 The space to store the converted character memory circuit
blocks is not sufficient.
Circuit Block Search error
0x04031007
Data is broken off in the circuit block.
Other errors
0x04031008 (Other errors generated during the conversion of
intermediate code to character memory)
CAD Data error
0x04040001 There is no CAD data to be converted. The CAD data
format is incorrect.
Output Data error
0x04040002 The input CAD data type and the output CAD data type are
not matching.
Library Load error
0x04040003
Failed to load the library.
• Exit the program and restart the personal computer.
Storage Space Secure error
• Reinstall MX Component.
0x04040004 The space secured to store the converted data is not
sufficient.
No END Command error
0x04040005 There is no END command in the CAD data to be
converted.
Abnormal Command Code
0x04040006 There is abnormal command code in the CAD data to be
converted.
Device No. error
0x04040007
The device number is out of range.
Step No. error
0x04040008
The step number is out of range.
The specified circuit size exceeded error.
0x04040009
1 circuit block is too big.
Return Circuit Error
0x0404000A
The return circuit is incorrect.
Bad Circuit Creation error
0x0404000B
The circuit data is incorrect.
SFC Data error
0x0404000C
The SFC data to be converted is incorrect.
List Data error
0x0404000D
The list data to be converted is incorrect.
Comment Data error
0x0404000E
The comment data to be converted is incorrect.
Statement error
0x0404000F
The statement data to be converted is incorrect.

566
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

Other errors
0x04040010 (Other errors generated during the conversion of CAD
code to Intermediate code.)
Intermediate Code Data error
0x04041001 There is no intermediate code to be converted. The format
of the intermediate code is incorrect.
CAD Data Type error
0x04041002 The input CAD data type and the output CAD data type are
not matching.
Library error
0x04041003
Failed to load the library.
Insufficient Input Data error
0x04041004
Data to be converted is insufficient.
Insufficient Storage Space error
0x04041005 There is not enough space to store the CAD data to be
converted.
No END Command error
0x04041006 There is no END command in the CAD data to be
converted.
Abnormal Command Code
0x04041007 There is abnormal command code in the CAD data to be 7
converted.
Device No. error
0x04041008
The device number is out of range.
Step No. error
0x04041009
The step number is out of range.
• Exit the program and restart the personal computer.
The specified circuit size exceeded error
0x0404100A • Reinstall MX Component.
1 circuit block is too big.

7.1 Error Codes Returned by Controls

Return Circuit error
0x0404100B
The return circuit is incorrect.
Bad Circuit Creation error
0x0404100C
The circuit data is incorrect.
SFC Data error
0x0404100D
The SFC data to be converted is incorrect.
List Data error
0x0404100E
The list data to be converted is incorrect.
Comment Data error
0x0404100F
The comment data to be converted is incorrect.
Statement error
0x04041010
The statement data to be converted is incorrect.
Other errors
0x04041011 (Other errors generated during the conversion of
Intermediate code to CAD code.)
Abnormal Character String Specified error
0x04050001
Device character string specified is incorrect.
Device Points error
0x04050002
Device points are out of range.
Other errors
0x04050003 (The errors generated during the conversion of the Device
Character String to Device Intermediate Code)
Device Name error
0x04051001 The classification specified for the device intermediate
code is incorrect.

567
 Error code Error description Corrective action
Device Name error
0x04051002 The classification specified for the extended specification
device intermediate code is incorrect.
Other errors
0x04051003 (The errors generated during the conversion of the Device
Intermediate Code to Device Character String)
Abnormal Character String Specified error
0x04052001
Device character string specified is incorrect.
Device Points error
0x04052002
Device points are out of range.
Other errors
0x04052003 (The errors generated during the conversion of the Device
Character String to Device Representation Code)
Device Representation error
0x04053001 The classification specified for the device intermediate
code is incorrect.
Device Representation error
0x04053002 The classification specified for the extended specification
device intermediate code is incorrect.
Device Representation error
0x04053003
The rectification part specified for the device is incorrect.
Device Representation error
0x04053004 The rectification part specified for the extended device is
incorrect.
Other errors
0x04053005 (The errors generated during the conversion of the Device • Exit the program and restart the personal computer.
Representation Code to Device Character String) • Reinstall MX Component.
Abnormal Device Intermediate Code error
0x04064001
The intermediate code for the device is incorrect.
Other errors
0x04064002 (Other errors generated during the conversion of the
Intermediate code for the Device to Device Name)
Abnormal Device Name error
0x04065001 The classification specified for the intermediate code of the
device is incorrect.
Abnormal Device Name error
0x04065002 The classification for the intermediate code of the extended
specification device is incorrect.
Other errors
0x04065003 (Other errors generated during the conversion of the
device name to Intermediate code)
Device Intermediate Code error
0x04066001
The intermediate code for the device is incorrect.
Other errors
0x04066002 (Other errors generated during the conversion of the
device intermediate code to device representation code.)
Device Representation error
0x04067001 The classification specified for the intermediate code of the
device is incorrect.
Device Representation error
0x04067002 The classification for the intermediate code of the extended
specification device is incorrect.

568
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

Device Representation error
0x04067003
The rectification part specified for the device is incorrect.
Device Representation error
0x04067004 The rectification part specified for the extended device is
incorrect.
Other errors
0x04067005 (Other errors generated during the conversion of device
representation code to the device intermediate code)
Common Data Conversion error
0x04070001 The input data of the device comment conversion is
incorrect.
Insufficient Common Data
0x04070002
The data to be converted is insufficient.
Insufficient Storage Area
0x04070003 The area where the conversion data is stored is
insufficient.
Error in CPU Data Conversion
0x04071001 The input data of the device comment conversion is
incorrect.
Insufficient CPU Data error
0x04071002
The data to be converted is insufficient. 7
Insufficient Storage Area
0x04071003 The area where the conversion data is stored is
insufficient.
Open error
0x04072001
Failed in creating conversion object. • Exit the program and restart the personal computer.
CPU Type error • Reinstall MX Component.
0x04072002
The specified CPU type does not exist.

7.1 Error Codes Returned by Controls

Not Converted error
0x04072003
Converted object does not exist.
Input Data error
0x04072004
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
Network Parameter Common Data error
0x04074002
The parameter block exists, but the data inside is not set.
0x04074101 Parameter CPU Data error
Network Parameter CPU Data error
0x04074102
The parameter block exists, but the data inside is not set.
0x04074103 Offset error
Error in Specifying Network Type
0x04074201
The CPU specified does not support the network type.
Parameter Block Number error
0x04074202 The Block corresponding to the parameter block number
specified does not exist.
Parameter Block Content error
0x04074203
It is different from the content supported by the specified.
Parameter Block Information error
0x04074204
The specified block number does not exist.

569
 Error code Error description Corrective action
Default Parameter Block is Abnormal
0x04074205
The specified block number does not exist.
0x04074301 Error in Conversion of the Common Parameter Block
Error in Common Parameter Block No. 1001
0x04074302 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
Error in Common Parameter Block No. 2001
0x04074306
The device intermediate code specified does not exist.
0x04074307 Error in Common Parameter Block No. 3000
0x04074308 Error in Common Parameter Block No. 3002
Error in Common Parameter Block No. 3004
0x04074309
The settings for the annunciator display mode is incorrect.
Error in Common Parameter Block No. 4000
0x0407430A
I/O Allotment Data is not created.
Error in Common Parameter Block No. 5000
0x0407430B
The specified network is not supported.
Error in Common Parameter Block No. 5001
0x0407430C
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.
0x04074311 Error in Common Parameter Block No. 5NM2 • Reinstall MX Component.

0x04074312 Error in Common Parameter Block No. 5NM3

0x04074313 Error in Common Parameter Block No. 6000
Error in Common Parameter Block No. FF18
0x04074314
Link parameter Capacity is not set.
Error in Common Parameter Block No. FF25
0x04074315
Calculation circuit check is not set.
Error in Common Parameter Block No. FF30
0x04074316
Sampling Trace Data is not created.
Error in Common Parameter Block No. FF31
0x04074317
Status latch data is not created.
Error in Common Parameter Block No. FF42
0x04074318
Timer processing points are not set.
Error in Common Parameter Block No. FF30
0x04074319 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
Error in Common Parameter Block No. FF60
0x0407431C
Terminal Settings are not set.
Error in Common Parameter Block No. FF70
0x0407431D
User Release area is not set.
0x04074401 Error in Conversion of CPU Parameter Block
0x04074402 Error in CPU Parameter Block No.1001
0x04074403 Error in CPU Parameter Block No.1003

570
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

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
Error in CPU Parameter Block No.5000
0x0407440B
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
Error in CPU Parameter Block No. 5NM0
0x0407440F
The specified network type is not supported.
0x04074410 Error in CPU Parameter Block No. 5NM1
Error in CPU Parameter Block No. 5NM2
0x04074411
The specified network type is not supported.
0x04074412 Error in CPU Parameter Block No. 5NM3
0x04074413 Error in CPU Parameter Block No. 6000 7
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
• Exit the program and restart the personal computer.
0x04074418 Error in CPU Parameter Block No. FF42 • Reinstall MX Component.
0x04074419 Error in CPU Parameter Block No. FF43

7.1 Error Codes Returned by Controls

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
Common Data Conversion error
0x04075001 Failed while converting the device memory settings
portion.
Common Data Conversion error
0x04075002
Failed while converting the device memory data portion.
Common Data Conversion error
0x04075003
Device memory data portion did not exist.
CPU Data Conversion error
0x04075101 Failed while converting the settings portion of the device
memory.
CPU Data Conversion error
0x04075102 Failed while converting the data portion of the device
memory.
Common Data Conversion error
0x04076001 Failed while converting the settings portion of the device
comments.
Common Data Conversion error
0x04076002 Failed while converting the data portion of the device
comments.

571
 Error code Error description Corrective action
CPU Data Conversion error
0x04076101 Failed while converting the settings portion of the device
comments.
CPU Data Conversion error
0x04076102 Failed while converting the settings portion of the device
comments.
Common Data Conversion error
0x04077001 Failed during the conversion of sampling trace settings
portion.
Common Data Conversion error
0x04077002 Failed during the conversion of sampling trace data
portion.
CPU Data Conversion error
0x04077101 Failed during the conversion of sampling trace settings
portion.
CPU Data Conversion error
0x04077102 Failed during the conversion of sampling trace data
portion.
Common Data Conversion error
0x04078001
Failed in the conversion of the status latch settings portion.
Common Data Conversion error
0x04078002
Failed in the conversion of the status latch data portion.
CPU Data Conversion error
0x04078101
Failed in the conversion of the status latch settings portion.
CPU Data Conversion error
0x04078102
Failed in the conversion of the status latch data portion. • Exit the program and restart the personal computer.
0x04079101 Failure history CPU Data Conversion error • Reinstall MX Component.
0x0407A101 File List CPU Data Conversion error
0x0407B101 Error Information CPU Data Conversion error
Error in Conversion of Indirect Address to Device Name
0x0407C001
The device name storage area is not secured.
Error in Conversion of Device Name to Indirect Address
0x0407C002
Indirect Address storage area is not secured.
Error in Conversion of Indirect Address to Device
0x0407C003 Representation
The device representation storage area is not secured.
Error in Conversion of Device Representation to Indirect
0x0407C004 Address
Indirect Address storage area is not secured.
Error in Conversion of Indirect Address to Device
0x0407C005 Character String
Device Character String storage area is not secured.
Error in Conversion of Device Character String to Indirect
0x0407C006 Address
Indirect Address storage area is not secured.
Error in Conversion of Intermediate Code to Device Name
0x0407C007
Device Name storage area is not secured.
Error in Conversion of Device Name to Intermediate Code
0x0407C008
Intermediate Code storage area is not secured.
Error in Conversion of Intermediate Code to Device
0x0407C009 representation
Device Representation storage area is not secured.

572
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

Error in Conversion of Device Representation to
0x0407C00A Intermediate Code
Intermediate Code storage area is not secured.
Error in Conversion of Intermediate Code to Indirect
0x0407C00B Address
Indirect Address storage area is not secured.
Error in Conversion of Indirect Address to Intermediate
0x0407C00C Code
Intermediate Code storage area is not secured.
CPU Type error
0x0407C00D
The specified CPU type is not supported.
Device Character String error
0x0407C00E
The specified device is not supported.
Device Character String error
0x0407C00F
The specified device character string, type is incorrect.
Device error
0x0407C010 The specified device is not supported by the specified
CPU.
CPU Type error
0x0407C011
The specified CPU is not supported.
0x0407C012 Device out of Range error 7
Common Data Conversion error
0x0407D001
Error in Conversion of SFC trace condition settings portion.
Common Data Conversion error
0x0407D002
Error in Conversion of SFC trace condition data portion.
• Exit the program and restart the personal computer.
CPU Data Conversion error • Reinstall MX Component.
0x0407D101
Error in Conversion of SFC trace condition settings portion.

7.1 Error Codes Returned by Controls

CPU Data Conversion error
0x0407D102
Error in Conversion of SFC trace condition data portion.
Intermediate Code classification out of range error
0x04080001 The intermediate code classification specified is out of
range.
Extended specification Intermediate Code classification out
of range error
0x04080002
The extended specification intermediate code specified is
out of range.
Device Points check absent error
0x04080003
The device does not check the device points.
GPP Project error
0x04090001 The specified CPU type and GPP project type are not
matching.
File Type error
0x04090002 The specified GPP project type and file type are not
matching.
Insufficient GPP Data to be converted
0x04090010 There is no data to be converted. The data size specified is
incorrect.
Insufficient Storage Space for Converted Data
0x04090011
The space for storing converted data is insufficient.
Error in GPP Data to be converted
0x04090012
The GPP data to be converted is incorrect.

573
 Error code Error description Corrective action
Insufficient Data to be converted error
0x04090110 There is no data to be converted. The data size specified is
insufficient.
Insufficient Storage Space for Converted Data error.
0x04090111
The storage space for converted data is insufficient.
Error in data to be converted
0x04090112
The data to be converted is incorrect.
Insufficient Intermediate Code Storage Space
0x040A0001
The space to store the data after conversion is insufficient.
The space to store addition SFC information is not
0x040A0002
sufficient.
0x040A0003 Conversion error
0x040A0004 Non-SFC Program error
0x040A1001 Step Not Used / No Output error
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 • Exit the program and restart the personal computer.
• Reinstall MX Component.
Insufficient Intermediate Code Storage Space
0x040B0001
The space to store the data after conversion is insufficient.
0x040B0002 Conversion error
0x040B1001 Failed in creating Step Start position table
0x040B1002 Error Reading Step Information
0x040B1003 Step No. error
Failed in reading the output of operation/Transition
0x040B1004
condition intermediate code error
0x040B1005 Securing Internal Work Area Failed error
Error in setting the maximum value of X direction for
0x040B1006
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.
0x10000003 Open failed. (DiskDrive)
0x10000004 Duplex open error • Exit the program and restart the personal computer.
0x10000005 File Access error
0x10000006 Incorrect Folder Name error
0x10000007 File Access Denied error • Exit the program and restart the personal computer.
0x10000008 Disk Full error • Reinstall MX Component.
0x10000009 File Delete error
0x1000000A Incorrect File Name error
• Execute again after some time.
Execution failed since another application or thread is • Perform programming according to the multithread rules
0x1000000C
making a request. of COM and ActiveX.
• Exit the program and restart the personal computer.

574
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

0x1000000D Folder Creation error
0x1000000E Folder/ File Type error
• Exit the program and restart the personal computer.
0x1000000F Offset Address error
• Reinstall MX Component.
Request Cancel
0x10000010
Cancel Process has occurred.
• Exit the program and restart the personal computer.
0x10000011 Memory securing error
• Reinstall MX Component.
0x10000012 Open not yet executed • Exit the program and restart the personal computer.
0x10000013 Attach Not Executed error
0x10000014 Object Invalid error • Exit the program and restart the personal computer.
0x10000015 Request Cancel Failed error • Reinstall MX Component.
0x10000016 Failed in Reading Status error
• Check the number of points specified in the method.
0x10000017 The specified size (number of devices) is unauthorized.
• 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
0x1000001A Read Not Executed error
• Exit the program and restart the personal computer.
0x1000001B Incorrect Create Flag error
• Reinstall MX Component.
0x1000001C Operation Over Access 7
0x1000001D Redundant Device error
• Exit the program and restart the personal computer.
0x1000001E Registry search failed. • Exit other programs and secure free memory area.
• Reinstall MX Component.
0x1000001F File Type error
0x10000020 Device Memory Type error
0x10000021 Program Range error

7.1 Error Codes Returned by Controls

0x10000022 TEL Type error • Exit the program and restart the personal computer.
0x10000023 TEL Access error • Reinstall MX Component.
0x10000024 Cancel Flag Type error
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
0x10000040 Server start failed.
Server Stop error
0x10000041
Failed while stopping the server.
0x10000042 Server Started Twice error
0x10000043 Server Not Started error
0x10000044 Resource Timeout error • Exit the program and restart the personal computer.
0x10000045 Server Type error • Reinstall MX Component.
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

575
 Error code Error description Corrective action
0x1000004C Simulator Not Supported error
• Exit the program and restart the personal computer.
0x1000004D Simulator Started Twice error
• Reinstall MX Component.
0x1000004E Shared Memory Not Started error
0x10000055 GX Simulator3 did not start error • Start GX Simulator3.
• Check the property timeout value.
• Check the settings in the communication settings utility.
• Check the programmable controller, unit settings, state
0x10000059 Timeout error
of the cable, etc.
• Close and Open again.
• Exit the program and restart the personal computer.
• Check the system number set on the communication
0x1000005A System number error
setup utility
0x8001000C • Review the value of the property.
Data out of the allowable setting range is specified.
0x80010016 • Set it again on the communication settings utility.
• Check the property timeout value.
• Check the settings in the communication settings utility.
0x80010101 Timeout error • Check the unit settings, state of the cable, etc.
• Close and Open again.
• Exit the program and restart the personal computer.
• Review the value of the property.
0x80020001 Type of data is invalid.
• Set it again on the communication settings utility.
• Review the value of the property.
0x80020002 Range of the data is incorrect.
• Set it again on the communication settings utility.
• Review the communication port value of the property.
0x80030001 The specification of the communication port is incorrect.
• Set it again on the communication settings utility.
• Review the transmission speed value of the property.
0x80030002 The specification of the Transmission speed is incorrect.
• Set it again on the communication settings utility.
• Review the data bit length of the property.
0x80030003 The specification of the Data bit length is incorrect.
• Set it again on the communication settings utility.
• Review the parity value of the property.
0x80030004 The specification of the parity is incorrect.
• Set it again on the communication settings utility.
• Review the stop bit value of the property.
0x80030005 The specification of the stop bit length is incorrect.
• Set it again on the communication settings utility.
• Review the wait time of the property.
0x80030006 The specification of the wait time is incorrect.
• Set it again on the communication settings utility.
• Review the CR/LF of the property.
0x80030007 The specification of the CR/LF is incorrect.
• Set it again on the communication settings utility.
• Review the CR/LF of the property.
0x80030008 The specification of the timeout is incorrect.
• Set it again on the communication settings utility.
• Review the timeout of the property.
0x80030009 The specification of the station number is incorrect.
• Set it again on the communication settings utility.
0x8003000A USB communication setting is invalid. • Review the value of the property.
0x8003000B USB model code is invalid. • Set it again on the communication settings utility.
Duplication was detected in station number of the USB • Review the station number of the property.
0x8003000C
communication. • Set it again on the communication settings utility.
• Try the same method again.
0x80200107 Communication error
• Exit the program and restart the personal computer.
• Exit the program and restart the personal computer.
0x80200203 Memory Secure error
• Exit other programs and secure free memory area.
0x80201001 Specified CPU error • Connect to the supported motion CPU.
Already open error • When changing the communication target CPU, execute
0x80201101
The Open method was executed in the open status. the Open method after performing Close.

576
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

• Exit the program and restart the personal computer.
0x80201104 DLL load error • Exit other programs and secure free memory area.
• Reinstall MX Component.
• Exit the program and restart the personal computer.
0x80201106 Error in Communication object generation
• Reinstall MX Component.
Not yet open error • After executing the Open method, execute the
0x80201201
The Open method is not yet executed. corresponding method.
• Exit the program and restart the personal computer.
0x80201203 Memory Secure error
• Exit other programs and secure free memory area.
0x80204203 Memory Secure error • Exit the program and restart the personal computer.
0x80205203 Memory Secure error • Exit other programs and secure free memory area.
• Check the CPU type set to ActCpuType.
0x80205001 Specified CPU error • 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.
MT Simulator2 start error
Because it had reached upper bounds of the number of
0x80209504 • Retry after exiting MT Simulator2.
simulations that was able to be started at the same time, it 7
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.
MT Simulator2 stop error
0x8020950F •–
MT Simulator2 is not started.
MT Simulator2 stop error
0x80209510 • Retry after starting MT Simulator2.
MT Simulator2 is not started.

7.1 Error Codes Returned by Controls

MT Simulator2 start error
0x80209516 • Install MT Developer2.
MT Developer2 is not installed.
MT Simulator2 startup error
0x80209518 • Execute after exiting the specified No. of MT Simulator2.
The specified number is already used.
0x80209519 Send data illegal error • Review the argument.
MT Simulator2 start error
0x8020951C • Retry after exiting MT Simulator2.
MT Simulator2 is ending.
MT Simulator2 start error
0x8020951D • Retry after performing Close.
Already executed Open.
0x8020951E MT Simulator2 non-Open error •–
MT Simulator2 start error
0x8020951F • Retry after performing Close.
Already executed Open.
• Change the switch on the module to RUN, exit the test
0x80206004 Remote request error
mode, and try again.
• Exit the program and restart the personal computer.
0x8020A104 DLL load error • Exit other programs and secure free memory area.
• Reinstall MX Component.
• Exit the program and restart the personal computer.
0x8020A203 Memory Secure error
• Exit other programs and secure free memory area.
Not yet open error • After executing the Open method, execute the
0x80A00101
The Open method is not yet executed. corresponding method.
Already open error • When changing the communication target CPU, execute
0x80A00104
The Open method was executed in the open status. the Open method after performing Close.
0x80A00105 Incorrect data type of the argument • Check the data type being used for the argument.

577
 Error code Error description Corrective action
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.
The response format from the robot controller was
0x80A0010C • Take measures against noise.
incorrect.
No-license error • Using the license FD, give the license to the personal
0xF0000001
The license is not given to the personal computer. computer.
• Specify the correct logical station number.
Set data read error
0xF0000002 • Set the logical station number on the communication
Reading of the set data of the logical station number failed.
settings utility.
Already open error • When changing the communication target CPU, execute
0xF0000003
The Open method was executed in the open status. the Open method after performing Close.
Not yet open error • After executing the Open method, execute the
0xF0000004
The Open method is not yet executed. corresponding method.
Initialization error
• Exit the program and restart the personal computer.
0xF0000005 Initialization of the object possessed internally in MX
• Reinstall MX Component.
Component failed.
Memory securing error • Exit the program and restart the personal computer.
0xF0000006
Securing of MX Component internal memory failed. • Exit other programs and secure free memory area.
Function non-support error • Can not use because the corresponding method is not
0xF0000007
The method does not support. supported.
• Check the character string specified in the method.
• The ASCII character string acquired from the
Character code conversion error programmable controller CPU is abnormal.
0xF1000001 Character code conversion (UNICODE ASCII code or • Review the system, e.g. programmable controller CPU,
ASCII code UNICODE) failed. module setting and cable status.
• Exit the program and restart the personal computer.
• Retry the GetCpuType method.
• Check the value of the first I/O number specified in the
First I/O number error
method.
0xF1000002 The first I/O number specified is an unauthorized value.
• Using the GPP function, check the programmable
A matching first I/O number does not exist.
controller CPU parameters (I/O assignment).
Buffer address error
• Check the value of the buffer address specified in the
0xF1000003 The buffer address specified is an unauthorized value.
method.
The buffer address is outside the range.
• Perform reopen processing.
Buffer read size error • Review the system, e.g. programmable controller CPU,
0xF1000004 As a result of buffer read, the specified size could not be module setting and cable status.
acquired. • Retry.
• Exit the program.
Size error
The size specified in the read/write method is abnormal.
0xF1000005 • Check the size specified in the method.
The read/write first number plus size exceeds the device or
buffer area.
Operation error
• Check the operation specifying value specified in the
0xF1000006 The operation specified for remote operation is an
method.
abnormal value.
• Check the clock data specified in the method.
Clock data error
0xF1000007 • Set the correct clock data to the clock data of the
The clock data is abnormal.
programmable controller CPU.

578
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

Monitored device registration count excess
The number of device points registered in the
• Register the device points between 1 and 20 in the
0xF1000008 EntryDeviceStatus method was 0 or less.
EntryDeviceStaus method.
The number of device points registered in the
EntryDeviceStatus method was more than 20.
• After making deregistration in the FreeDeviceStatus
0xF1000009 Monitored device data registration error
method, execute the EntryDeviceStatus method again.
Device status monitor processing failed to start. • Start/end the device status monitor processing again in
0xF1000010
Device status monitor processing failed to end. the EntryDeviceStatus method.
• Reexamine the data type specified for the VARIANT
argument.
0xF1000011 The VARIANT argument data type is wrong. • Check whether the array variable size is large enough.
• Check whether the data type specified in the
corresponding method has been set.
The device status monitoring time interval is a value • Specify the device status monitoring time between 1 and
0xF1000012
outside the range 1 second to 1 hour (1 to 3600). 3600.
Already Connected error.
• Execute the Connect method after executing the
0xF1000013 Connect was executed again after it was executed for the
Disconnect method.
same object.
Invalid Telephone Number error.
0xF1000014 Characters other than "0123456789-*#" that are allowed • Rectify the Telephone number and try to Connect again. 7
for telephone numbers are included.
• In case if Connect/Disconnect method is being executed
for any other object, execute the failed method (Connect/
Disconnect) again after the completion of the Connect/
Exclusive Control Failure error. Disconnect method of that object.
0xF1000015 There was failure in the exclusive control process while • If the Connect/Disconnect process is in progress only for
executing the Connect and Disconnect method. the self object, perform the following.

7.1 Error Codes Returned by Controls

Exit the program.
Restart the personal computer.
Reinstall MX Component.
While connecting to the telephone line error.
• Try Connecting again after disconnecting the application
0xF1000016 The telephone line is connected to some other application,
that is using the telephone line.
other than the one using MX Component.
• (When Connect method has failed)
Execute Connect again after executing Disconnect
Telephone line not connected error.
method.
Telephone line is not connected.
0xF1000017 • (When method other than Connect has failed)
Connect was executed and the telephone line was
Execute Disconnect method, Execute Connect and
connected, but it got disconnected due to some reason.
connect to the telephone line. After connecting, execute
the method that failed once again.
• In case of program settings type, set the telephone No.
to the property ActDialNumber.
(Set the telephone No. to the properties ActDialNumber
and ActCallbackNumber, if the connection method is
No Telephone number error.
automatic (when specifying the call back No.), call back
The telephone No. is not set.
connection (when specifying the telephone No.), or call
The telephone No. or call back No. is not set, if the
back request (when specifying the number).)
0xF1000018 connection method is Automatic (when specifying the call
• In case of utility settings type, set the telephone No.
back No.), call back connection (when specifying the
using the wizard.
number), or call back Request(when specifying the
(Set the telephone No. and call back No. , if the
number).
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).)

579
 Error code Error description Corrective action
Not Closed error.
0xF1000019 • Try Disconnect again after executing Close.
Disconnect was executed while in Open state.
• If you want to connect to a different telephone number,
Target telephone line connection mismatch error.
Execute Disconnect with respect to the telephone line
Connect was tried for a different telephone number using
that is already connected and executes Connect after it
the port which is already connected to a telephone line.
gets disconnected.
0xF100001A (When the method of connection is a callback reception, it
• In case of connecting the telephone line with callback
is considered that the telephone number is different from
reception, use the Connect of the connection method
methods of connection in other than the callback
that is executed at the earliest in the same port as
reception.)
callback reception.
Control Type Mismatch error.
• Execute Disconnect for the object currently connected to
An object, whose control type is different from that of the
0xF100001B the telephone line and execute Connect once again after
object already connected to the telephone line, tried to
the telephone line gets disconnected.
Connect.
Not Disconnected error.
• Execute Disconnect for all the Connected objects. Try
When Disconnect method is executed for the object
0xF100001C Disconnect again for the object that actually performed
connected to the telephone line, it is found that other
the telephone line connection.
objects are in connected state.
Not Connected error.
• Execute Open again after executing Connect.
0xF100001D Open was executed before Connect.
• Or execute Disconnect again after executing Connect.
Or, Disconnect was executed.
• Exit the program.
0xF100001E Fatal error. • Restart the personal computer.
• Reinstall MX Component.
Open time setting error
There is some difference in telephone number and the port • Check the telephone number and the port number.
0xF100001F
number settings used during Connect and Open. • Check the Connect way.
There is some error in Connect way.
GX Simulator3 unstart error
0xF1000020 • Start GX Simulator3.
GX Simulator3 did not start error
• Check the value of the properties set in case of program
There is an error response from the target telephone.
settings type and check the contents of the detailed
0xF2000002 Causes can be the following.
settings that were set using the wizard in case of utility
• Communication error has occurred.
settings type.
Invalid data was received.
• Retry.
0xF2000003 Causes can be the following.
• Check the communication device used at the other end.
• Incorrect data packet received due to noise.
• Check the status of the modem.
• Check the telephone number.
There is no response from the modem. • If the problem persists even after checking the above
Causes can be the following. points, change the value of the properties set (Properties
0xF2000004
• Abnormality in the modem. such as ActConnectionCDWaitTime etc. , which set the
• Telephone number setting mistake. timings) 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 line.
The PC modem did not receive the AT command.
Causes can be the following. • Check the contents of the AT command.
0xF2000006
• Invalid AT command was specified. • Check the status of the modem.
• Abnormality in the modem.
• Check the modem.
Modem did not respond properly to the standard escape
0xF2000007 • Confirm whether the value of the time-out is too small.
command.
( 5000ms or more is recommended. )

580
 CHAPTER 7 ERROR CODES

Error code Error description Corrective action

Modem does not respond properly to the line Disconnect
0xF2000009 • Check the modem.
command.
Target did not receive the signal.
• Check the Receive settings of the modem at the other
• The Receive settings of the modem at the other end may
end.
0xF200000A be incorrect.
• Check if the other end is busy.
• The other end may be busy.
• Check the telephone number.
• The telephone number may be incorrect.
• Increase the call back receive waiting time
0xF200000B Timeout reached for the call back receive waiting time. ActCallbackReveptionWaitingTimeOut and execute
connect again.
• Set the password to ActPassword property and execute
0xF200000C Password of QJ71C24 units could not be resolved.
the failed method again.
• Check whether the callback line disconnect wait time is
with in 0 - 180 Seconds.
The callback line disconnect wait time is other than 0 -180
• Check whether the callback execution delay time is with
Seconds.
in 0 - 1800 Seconds.
0xF2010001 The callback execution delay time is other than 0 -1800
• Check whether the telephone number is less than or
Seconds.
equal to 62 characters.
The telephone number is more than 62 characters.
• Exit the program and restart the personal computer.
• Reinstall MX Component.
QJ71C24 did not receive the specified connection method.
Causes can be the following. • Check whether the settings of QJ71C24 and the MX
7
0xF2010002
• Incorrect Connection method. Component are matching.
• Incorrect telephone number for Call back.
QJ71C24 does not permit the automatic connection (during
0xF2010003 • Check the settings of QJ71C24.
fixed Call back or when the number is specified.)
• If there is no problem with the modem or the telephone
line, change the value of the properties set (Properties

7.1 Error Codes Returned by Controls

like ActConnectionCDWaitTime etc. , which set the
0xF2100005 There are chances that the line is not disconnected.
timings) 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.
• Change the settings of the property ActATCommand. in
case of program settings type and change the command
0xF2100006 Modem did not receive the startup command AT.
AT that were set using the wizard in case of utility
settings type.
• If there is no problem with the modem or the telephone
line, change the value of the properties set (Properties
The PC modem does not respond to the Escape like ActConnectionCDWaitTime etc. , which set the
0xF2100007
command. timings) 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.
• Change the value of the properties set (Properties such
as ActConnectionCDWaitTime etc. , which set the
There was no response from the modem for the data sent
0xF2100008 timings) in case of program settings type and change the
from the PC.
contents of the detailed settings that were set using the
wizard in case of utility settings type.
• Check the status of the modem.
• Check the telephone number.
There is no response from the modem. • If the problem persists even after checking the above
Causes can be the following. points, change the value of the properties set (Properties
0xF21000**
• Abnormality in the modem. such as ActConnectionCDWaitTime etc. , which set the
• Telephone number setting mistake. timings) 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.

581
 Error code Error description Corrective action
• Check whether the cable is broken.
• Check whether the specified port is not supported.
There was a communication failure.
• Check whether correct COM port is set.
Following causes can be considered depending on the
• Check if the modem power is switched OFF.
status.
0xF202**** • For detailed troubleshooting, please refer to the details
• Communication time over (Break in cable, the specified
of the error code got after replacing the first four digits
port not supported, mistake in specifying the COM port)
with "0x0180".
• Modem’s power is switched OFF.
eg In case of "0xF202480B", please refer to the code
"0x0180480B".
Label error
0xF3000001 The label character string specified in the method is an • Review the label name.
unauthorized label character string.
0xF3000002 Label Service not started • Exit the program and restart the personal computer.
0xF3000003 MMS Service not started • Reinstall MX Component.
The specified LabelSpace is currently being used and
0xF3000004 • Please retry.
cannot be opened.
• Please retry.
0xF3000005 Label data access timeout error
• Reduce systemlabel definition.
MUTEX acquisition error
0xF3000006 • Exit the program and restart the personal computer.
Acquisition of MUTEX to exercise exclusive control failed.
MX Component trial version error • Uninstall the trial version and install the commercial
0xFF000001
Expired MX Component trial version version, or reinstall the trial version.

582
 CHAPTER 7 ERROR CODES

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 the following (1).

Check the considerations described in the (2) first, and refer to the (1).

(1) 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 7
CC-Link IE Controller Network board, MELSECNET/H board, CC-Link Ver.2
0x01070000 to 0x0107FFFF*1
board
*1 FXCPU
0x01090000 to 0x0109FFFF

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

7.2 Error Codes Returned by CPUs, Modules, and Network Boards

0x010D0000 to 0x010DFFFF*1 PC CPU module

0x010F0000 to 0x010FFFFF*1 GOT

*1 : Refer to "Point"
*2 : The error codes are also described in the following section.
Page 552, Section 7.1 Error Codes Returned by Controls

(2) Considerations for confirming error codes

The following are the considerations for confirming the error codes returned by CPU, module, and network board.

(a) 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 ActEasyIF or ActMLEasyIF control is used, check the settings of Communication Setup Utility.

(b) 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.

583
 (3) 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

• When a system label is specified as a label, review the global label name
0x01802001 Label information errer assigned to the system label name in Label Utility.
• Check if the global labels exist in the CPU.
0x010A4000 to For the errors and their corrective actions, refer to the following manual.
0x010A4FFF MELSEC iQ-R CPU Module User's Manual (Application)

584
 CHAPTER 7 ERROR CODES

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 Termination status Description
S_OK Normal termination The function processing is normally terminated.
The function processing (as ActiveX control) is normally terminated, but the
S_FALSE Normal termination
operation (access to programmable controller) failed.
E_POINTER Abnormal termination The pointer passed to the function is abnormal.
E_OUTOFMEMORY Abnormal termination Memory reservation or object creation failed.
E_FAIL Abnormal termination An indefinite error occurred.

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

7.4 Error Codes Displayed on Event Viewer

This section explains the error codes displayed on Windows® Event Viewer by MX Component.

7.3 HRESULT Type Error Codes

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
• Wait for the completion of MMS (system label database) Service
startup.
3 MMS Service not started. If MMS Service startup does not complete, exit the program and
restart the personal computer.
• Reinstall MX Component.
MXLabelService error (%1,%2)
Please perform one of the following operations. • Exit the program and restart the personal computer.
5
- Restart the personal computer. • Reinstall MX Component.
- Reinstall the application and try again.

585
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 (1) to (3), the telephone use fees are charged on the personal computer side.
• For (4) to (8), the telephone use fees are charged on Q series-compatible C24 side.
For details of the callback function, refer to the following manual.
Q Corresponding Serial Communication Module User's Manual (Application)

(1) Auto line connect

Select this when the callback function is not set to Q series-compatible C24.

(2) 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.

(3) Auto line connect (Callback number specification)

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 specified by MX Component can be connected.

(4) Callback connect (Fixation)

Callback only personal computers whose telephone number is registered in the buffer memory (2101H) of Q
series-compatible C24.

(5) Callback connect (Number specification)

Callback only personal computers whose telephone number is specified by MX Component.

(6) 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.)

(7) Callback request (Number specification)

Send a callback request from the selected personal computer to callback personal computers whose telephone
number is specified by MX Component. (The callback is not performed on the personal computer which is
connected first.)

(8) 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.

586
 APPENDIX

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.

(1) 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® 6.0.
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 A
'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

Appendix 2 Programming Examples for Monitoring Word Device Status

'If the set value is negative
If lInputData(lCount) < 0 Then
'Masks with 65535 (0000FFFF[hex]) to store "0"s into upper 2 bytes.
lEntryData(lCount) = lInputData(lCount) And 65535
Else
'If the set value is positive, assigns the value as-is to lEntryData.
lEntryData(lCount) = lInputData(lCount)
End If
Next
'Executes EntryDeviceStatus.
lReturnCode = AxActUtlType1.EntryDeviceStatus(szDevice, 3, 5, lEntryData(0))

<When ldata = -1>

Private Sub AxActUtlType1_OnDeviceStatus(ByVal szDevice As String, ByVal lData As Long, ByVal lReturnCode As Long)
Dim lCheckData As Long 'Value set to EntryDeviceStatus (value before 0s are stored into the upper 2 bytes)
'If the device value whose condition was established is a WORD type negative value (greater than 32767 (7FFF[Hex])
If lData > 32767 Then
'Since "0"s are stored in the upper 2 bytes, the device value is ORed with FFFF0000[Hex] to convert it into a LONG
'type negative value.
lCheckData = lData Or &HFFFF0000
Else
'If the device value whose condition was established is positive, assigns the value as-is to lCheckData.
lCheckData = lData
End If
End Sub

587
 (2) 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;
}
}

588
 APPENDIX

(3) 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[] inputData = 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(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;
A
}else{
//If the set value is positive, assigns the value as-is to lEntryData.
lEntryData[lCount] = lInputData[lCount];

Appendix 2 Programming Examples for Monitoring Word Device Status

}
}
axActUtlType1.ActLogicalStationNumber = 0;
iReturnCode = axActUtlType1.Open();
//Executes EntryDeviceStatus.
iReturnCode =axActUtlType1.EntryDeviceStatus(szDevice, 3, 5, ref iEntryData[0]);

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

Appendix 3.1 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 paths for retries at a time-out error occurrence.

(1) Serial communication

(a) Configuration

1 2
Connected Connected Relayed
station CPU module module

Relayed network 3
Personal computer
4
Relayed Relayed
station CPU module

590
 APPENDIX

(b) Target/non-target communication path

The following table shows the communication paths 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).

Connected station 4. Relayed station CPU

3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
RCPU, R series-
Ethernet    
RCCPU compatible C24
Serial communication    
CC-Link    
Multi-drop connection    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H
RCPU, R series-
Ethernet












A
RCCPU compatible C24
Serial communication      
CC-Link      

Appendix 3.1 Communication retries at time-out error occurrence

Appendix 3 Time-Out Periods
Multi-drop connection      

591
 Connected station 4. Relayed station CPU
3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
QCPU Q series-
Ethernet    
(Q mode) compatible C24
Serial communication    
CC-Link    
Multi-drop connection    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
QCPU Q series-
Ethernet      
(Q mode) compatible C24
Serial communication      
CC-Link      
Multi-drop connection      

Connected station 4. Relayed station CPU

3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
L series-
LCPU Ethernet    
compatible C24
Serial communication    
CC-Link    
Multi-drop connection    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
L series-
LCPU Ethernet      
compatible C24
Serial communication      
CC-Link      
Multi-drop connection      

592
 APPENDIX

Connected station 4. Relayed station CPU

3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
FX extended
FXCPU Ethernet    
port
Serial communication    
CC-Link    
Multi-drop connection    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
FX extended
FXCPU Ethernet      
port
Serial communication      
CC-Link      
Multi-drop connection      

Appendix 3.1 Communication retries at time-out error occurrence

Appendix 3 Time-Out Periods

593
 (2) CPU COM communication

(a) Configuration
1
Connected Relayed
station CPU module

Relayed network 2
Personal computer
3
Relayed Relayed
station CPU module

(b) Target/non-target communication path

The following table shows the communication paths 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).

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
FX5CPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
FX5CPU
Ethernet      
Serial communication      
CC-Link      

594
 APPENDIX

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
QCPU (Q mode)
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
QCPU (Q mode)
Ethernet      
Serial communication      
CC-Link      

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU
CPU
FX5CPU
A
CC IE Field    
CC IE Control    
MELSECNET/H    

Appendix 3.1 Communication retries at time-out error occurrence

Appendix 3 Time-Out Periods
LCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
LCPU
Ethernet      
Serial communication      
CC-Link      

595
 3. Relayed station CPU
1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
Q motion CPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
Q motion CPU
Ethernet      
Serial communication      
CC-Link      

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
FXCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
FXCPU
Ethernet      
Serial communication      
CC-Link      *1

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

596
 APPENDIX

(3) CPU USB communication

(a) Configuration
1
Connected Relayed
station CPU module

Relayed network 2
Personal computer
3
Relayed Relayed
station CPU module

(b) Target/non-target communication path

The following table shows the communication paths 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).

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    

RCPU, MELSECNET/H    
RCCPU Ethernet     A
Serial communication    
CC-Link    

3. Relayed station CPU

Appendix 3.1 Communication retries at time-out error occurrence

Appendix 3 Time-Out Periods
1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
RCPU, MELSECNET/H      
RCCPU Ethernet      
Serial communication      
CC-Link      

597
 3. Relayed station CPU
1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
QCPU (Q mode)
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
QCPU (Q mode)
Ethernet      
Serial communication      
CC-Link      

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
QCCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
QCCPU
Ethernet      
Serial communication      
CC-Link      

598
 APPENDIX

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
LCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
LCPU
Ethernet      
Serial communication      
CC-Link      

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU
CPU
FX5CPU
A
CC IE Field    
CC IE Control    
MELSECNET/H    

Appendix 3.1 Communication retries at time-out error occurrence

Appendix 3 Time-Out Periods
FXCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
FXCPU
Ethernet      
Serial communication      
CC-Link      *1

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

599
 (4) CC-Link G4 communication

(a) Configuration
1
Connected CC-Link Relayed
station CPU module module

Relayed network 2
3
CC-Link G4 Relayed Relayed
module station CPU module
Personal computer

(b) Target/non-target communication path

The following tables show the communication paths 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

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
QCPU (Q mode)
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
QCPU (Q mode)
Ethernet      
Serial communication      
CC-Link      

600
 APPENDIX

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
QCCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
QCCPU
Ethernet      
Serial communication      
CC-Link      

When CC-Link G4-S3 module is Q mode and connected station CPU is LCPU
3. Relayed station CPU
1. Connected
2. Relayed network R motion
A
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    

Appendix 3.1 Communication retries at time-out error occurrence

Appendix 3 Time-Out Periods
MELSECNET/H    
LCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
LCPU
Ethernet      
Serial communication      
CC-Link      

601
 (5) Modem communication

(a) When using FXCPU

 Configuration
1
Connected Relayed
station CPU module

Modem Relayed network 2

Subscriber's line 3
Relayed Relayed
Modem station CPU module
Personal computer
 Target/non-target communication path
The following table shows the communication paths 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).

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
FXCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
FXCPU
Ethernet      
Serial communication      
CC-Link      

602
 APPENDIX

(b) When using Q series-compatible C24 or QC24N

 Configuration
1 2
Connected Connected Relayed
station CPU module module

Modem Relayed network 3

Subscriber's line 4
Relayed Relayed
Modem station CPU module
Personal computer
 Target/non-target communication path
The following table shows the communication paths 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).

Connected station 4. Relayed station CPU

3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
QCPU Q series- Ethernet    
(Q mode) compatible C24 Serial communication
CC-Link








A
Multi-drop connection
   
(Independent mode)

Appendix 3.1 Communication retries at time-out error occurrence

Appendix 3 Time-Out Periods
Connected station 4. Relayed station CPU
3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
QCPU Q series- Ethernet      
(Q mode) compatible C24 Serial communication      
CC-Link      
Multi-drop connection
     
(Independent mode)

603
 (c) When using L series-compatible C24
 Configuration
1 2
Connected Connected Relayed
station CPU module module

Modem Relayed network 3

Subscriber's line 4
Connected Relayed
Modem station CPU module
Personal computer
 Target/non-target communication path
The following table shows the communication paths 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).

Connected station 4. Relayed station CPU

3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
L series- Ethernet    
LCPU
compatible C24 Serial communication    
CC-Link    
Multi-drop connection
   
(Independent mode)

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
Ethernet      
L series-
LCPU Serial
compatible C24      
communication
CC-Link      
Multi-drop connection
     
(Independent mode)

604
 APPENDIX

Appendix 3.2 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 paths for retries at a receive data error occurrence.

(1) Ethernet communication

(a) Configuration
1 2
Connected Connected Relayed
station CPU module module
Ethernet
Relayed network 3
4
Relayed Relayed
station CPU module
Personal computer

(b) Target/non-target communication path

The following table shows the communication paths for retries at a data error occurrence. A
All the connected station CPUs can be the targets.
Target/non-target relayed CPUs are indicated by  (target) or  (non-target).

Connected station 4. Relayed station CPU

Appendix 3.2 Communication retries at receive data error occurrence

Appendix 3 Time-Out Periods
3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
R series-
RCPU, compatible E71, MELSECNET/H    
RCCPU RCPU, Ethernet    
RCCPU
Serial communication    
CC-Link    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      

R series- CC IE Control      
RCPU, compatible E71, MELSECNET/H      
RCCPU RCPU, Ethernet      
RCCPU Serial communication      
CC-Link      

605
 Connected station 4. Relayed station CPU
3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
FX5CPU FX5CPU
Ethernet    
Serial communication    
CC-Link    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
FX5CPU FX5CPU
Ethernet      
Serial communication      
CC-Link      

Connected station 4. Relayed station CPU

3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    

Q series- CC IE Control    
QCPU compatible E71, MELSECNET/H    
(Q mode) Built-in Ethernet Ethernet    
port QCPU Serial communication    
CC-Link    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      

Q series- CC IE Control      
QCPU compatible E71, MELSECNET/H      
(Q mode) Built-in Ethernet Ethernet      
port QCPU Serial communication      
CC-Link      

606
 APPENDIX

Connected station 4. Relayed station CPU

3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
Built-in Ethernet MELSECNET/H    
LCPU
port LCPU Ethernet    
Serial communication    
CC-Link    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
Built-in Ethernet MELSECNET/H      
LCPU
port LCPU Ethernet      
Serial communication      
CC-Link      

Appendix 3.2 Communication retries at receive data error occurrence

Appendix 3 Time-Out Periods

607
Appendix 3.3 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 (1000ms to 4500ms) 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 paths for a time-out error occurrence at the fixed time in the ACT control.

(1) Serial communication

(a) Configuration
1 2
Connected Connected Relayed
station CPU module module

Relayed network 3
Personal computer
4
Relayed Relayed
station CPU module

(b) Target/non-target communication path

The following table shows the communication paths 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).

Connected station 4. Relayed station CPU

3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
RCPU, R series-
Ethernet    
RCCPU compatible C24
Serial communication    
CC-Link    
Multi-drop connection    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
RCPU, R series-
Ethernet      
RCCPU compatible C24
Serial communication      
CC-Link      
Multi-drop connection      

608
 APPENDIX

Connected station 4. Relayed station CPU

3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
QCPU Q series-
Ethernet    
(Q mode) compatible C24
Serial communication    
CC-Link    
Multi-drop connection    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
QCPU Q series-
Ethernet      
(Q mode) compatible C24
Serial communication      
CC-Link      
Multi-drop connection      

Connected station 4. Relayed station CPU A

3. Relayed
2. Connected R motion
1. CPU network RCPU RCCPU FX5CPU
module CPU
CC IE Field    

Appendix 3.3 Time-out errors at fixed time in ACT control

Appendix 3 Time-Out Periods
CC IE Control    
MELSECNET/H    
L series-
LCPU Ethernet    
compatible C24
Serial communication    
CC-Link    
Multi-drop connection    

Connected station 4. Relayed station CPU

3. Relayed
2. Connected QCPU QS Q motion FX
1. CPU network QCCPU LCPU
module (Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
L series-
LCPU Ethernet      
compatible C24
Serial communication      
CC-Link      
Multi-drop connection      

609
 (2) CPU COM communication

(a) Configuration
1
Connected Relayed
station CPU module

Relayed network 2
Personal computer
3
Relayed Relayed
station CPU module

(b) Target/non-target communication path

The following table shows the communication paths 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).

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
FX5CPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
FX5CPU
Ethernet      
Serial communication      
CC-Link      

610
 APPENDIX

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
QCPU (Q mode), MELSECNET/H    
QCCPU Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
QCPU (Q mode), MELSECNET/H      
QCCPU Ethernet      
Serial communication      
CC-Link      

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU
CPU
FX5CPU
A
CC IE Field    
CC IE Control    
MELSECNET/H    

Appendix 3.3 Time-out errors at fixed time in ACT control

Appendix 3 Time-Out Periods
LCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
LCPU
Ethernet      
Serial communication      
CC-Link      

611
 3. Relayed station CPU
1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
FXCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
FXCPU
Ethernet      
Serial communication      
CC-Link      *1

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

612
 APPENDIX

(3) CC-Link G4 communication

(a) Configuration
1
Connected CC-Link Relayed
station CPU module module

Relayed network 2
3
CC-Link Relayed Relayed
G4 module station CPU module
Personal computer

(b) Target/non-target communication path

The following table shows the communication paths 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).

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H     A
QCPU (Q mode)
Ethernet    
Serial communication    
CC-Link    

Appendix 3.3 Time-out errors at fixed time in ACT control

Appendix 3 Time-Out Periods
3. Relayed station CPU
1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
QCPU (Q mode)
Ethernet      
Serial communication      
CC-Link      

613
 3. Relayed station CPU
1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
QCCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
QCCPU
Ethernet      
Serial communication      
CC-Link      

3. Relayed station CPU

1. Connected
2. Relayed network R motion
module RCPU RCCPU FX5CPU
CPU
CC IE Field    
CC IE Control    
MELSECNET/H    
LCPU
Ethernet    
Serial communication    
CC-Link    

3. Relayed station CPU

1. Connected
2. Relayed network QCPU QS Q motion FX
module QCCPU LCPU
(Q mode) CPU CPU CPU
CC IE Field      
CC IE Control      
MELSECNET/H      
LCPU
Ethernet      
Serial communication      
CC-Link      

614
 REVISIONS
*The manual number is given on the bottom left of the back cover.
Print date *Manual number Revision
Jul., 2012 SH-081085ENG-A First edition

Model Addition
Q03UDV, Q04UDV, Q06UDV, Q13UDV, Q26UDV, Q24DHCCPU-V, FX3GC

Correction
OPERATING CONSIDERATIONS, TERMS, Section 1.1, Section 2.1.3, Section 2.3,
Feb., 2013 SH-081085ENG-B Section 2.4, Section 3.2, Section 4.2 to 4.10, Section 4.13, Section 4.15,
Section 5.2.11 to 5.2.14, Section 5.2.23, Section 5.2.24, Section 5.2.26, Section 5.3.11,
Section 5.3.12, Section 5.3.24, Section 5.3.25, Section 7.1, Appendix 3

Deletion
Appendix 4

Model Addition
L02S, L06, L26

Addition
Section 2.2.5,Section 4.3.9, Section 4.3.10, Section 4.13, Section 4.16.13,
Section 4.16.14, Section 6.6, Section 6.6.1
Aug., 2013 SH-081085ENG-C
Correction
OPERATING CONSIDERATIONS, TERMS, Section 1.1, Section 1.2.1, Section 2.1.3,
Section 2.2.1 to Section 2.2.4, Section 3.2, Section 4.1, Section 4.3.1 to Section 4.3.4,
Section 4.4.4, Section 4.5.5, Section 4.16.1, Section 4.16.2, Section 4.16.15, CHAPTER 5,
Section 5.2.1 to Section 5.2.26, Section 5.3.1 to Section 5.3.26, CHAPTER 6, Section 7.1,
Appendix 2, Appendix 3.1, Appendix 3.2, Appendix 3.3

Model Addition
FX3S, Q12DC-V (Extended mode), Q24DHC-LS, GOT2000, A800
Addition
Section 4.4.5, Section 4.5.6
Dec., 2013 SH-081085ENG-D Correction
RELATED MANUALS, TERMS, Section 1.1, Section 2.3, Section 2.4, Section 3.1, Section 3.2,
Section 4.2.1, Section 4.2.2, Section 4.3.1 to Section 4.3.10, Section 4.4.1, Section 4.4.2,
Section 4.4.4, Section 4.5.1, Section 4.5.2, Section 4.6 to Section 4.10, Section 4.14.1,
Section 4.14.2, Section 4.16, Section 4.16.1 to Section 4.16.17, Section 5.1,
Section 5.2.3 to Section 5.2.26, Section 7.1

615
 Print date *Manual number Revision

Model Addition
R04, R08, R16, R32, R120, R16MT, R32MT
May, 2014 SH-081085ENG-E Correction
TERMS, Section 1.1, Section 2.3, Section 3.2, CHAPTER 4, CHAPTER 5, CHAPTER 6,
Appendix 3

Model Addition
CR750-D/CRnD-700 series
Addition
Dec., 2014 SH-081085ENG-F Section 4.3.15, Section 4.4.6, Section 4.5.9
Correction
TERMS, Section 1.1, Section 1.2.1, Section 2.1.3, Section 2.3, Section 3.2, Section 5.1,
Section 5.2.3 to Section 5.2.23, Section 5.2.26, Section 5.3.3 to Section 5.3.8,
Section 5.3.18 to Section 5.3.23, Section 7.1, Section 7.2

Addition
Section 4.3.7, Section 4.3.8, Section 4.4.1
Apr., 2015 SH-081085ENG-G
Correction
TERMS, Section 1.1, Section 2.3, Section 3.2, Section 5.2.9 to Section 5.2.14,
Appendix 3.1, Appendix 3.2, Appendix 3.3

Model Addition
R08P, R08SF, R16P, R16SF, R32P, R32SF, R120P, R120SF

Correction
Aug., 2015 SH-081085ENG-H OPERATING CONSIDERATIONS, TERMS,
Section 1.2.2, Section 2.3, Section 3.2, Section 4.2.1, Section 4.3.1, Section 4.3.2,
Section 4.3.4, Section 4.3.5, Section 4.3.6, Section 4.4.3, Section 4.5.1, Section 4.5.2,
Section 4.16.5, Section 4.16.6, Section 4.16.7, Section 4.16.9, Section 4.16.18,
Section 5.1, Section 5.2.13, Section 6.4.2

Model Addition
R04EN, R08EN, R16EN, R32EN, R120EN, Q24DHCCPU-VG, Q26DHCCPU-LS,
R12CCPU-V
Addition
Jan., 2016 SH-081085ENG-I Section 4.13
Correction
OPERATING CONSIDERATIONS, INTRODUCTION, RELATED MANUALS, TERMS,
Section 1.1, Section 2.3, Section 3.2, CHAPTER 4, Section 5.2.3, Section 5.2.4,
Section 5.2.9 to Section 5.2.14, Section 5.3.4, Section 5.3.19, Section 7.1, Appendix 3

Correction
Mar., 2016 SH-081085ENG-J
Section 3.2

616
 Print date *Manual number Revision
Correction
TERMS, Section 2.1.3, Section 2.2.4, Section 2.2.5, Section 3.2, Section 4.2.1,
Section 4.2.2, Section 4.2.3, Section 4.3.3, Section 4.3.4, Section 4.3.5, Section 4.3.6,
Section 4.3.7, Section 4.3.8, Section 4.3.9, Section 4.3.10, Section 4.3.11, Section 4.3.12,
Section 4.3.13, Section 4.3.14, Section 4.4.1, Section 4.4.2, Section 4.5.1, Section 4.17.1,
Jul., 2016 SH-081085ENG-K Section 4.17.2, Section 4.17.3, Section 4.17.5, Section 4.17.6, Section 4.17.7,
Section 4.17.8, Section 4.17.9, Section 4.17.10, Section 4.17.11, Section 4.17.12,
Section 4.17.13, Section 4.17.14, Section 4.17.15, Section 4.17.17, Section 4.17.18,
Section 5.2.9, Section 5.2.10, Section 5.3.3, Section 5.3.4, Section 5.3.5, Section 5.3.6,
Section 5.3.7, Section 5.3.9, Section 5.3.10, Section 5.3.13, Section 5.3.15, Section 5.3.17,
Section 5.3.18, Section 5.3.19, Section 5.3.20, Section 5.3.21, Section 5.3.22,
Section 5.3.23, Section 5.3.26, CHAPTER 6, Section 6.4.2

Addition
Section 4.3.5, Section 4.3.6, Section 4.17.9, Section 4.17.12
Correction
OPERATING CONSIDERATIONS, TERMS, Section 1.1, Section 2.3, Section 3.2,
Jan., 2017 SH-081085ENG-L Section 4.2.1, Section 4.2.3, Section 4.3.1, Section 4.3.2, Section 4.3.7, Section 4.3.8,
Section 4.3.13, Section 4.3.14, Section 4.4.3, Section 4.5.1, Section 4.5.4, Section 4.7,
Section 4.8, Section 4.9, Section 4.13, Section 4.17.1, Section 4.17.2, Section 4.17.5,
Section 4.17.6, Section 4.17.7, Section 4.17.10, Section 4.17.13, Section 4.17.14,
Section 5.2.9, Section 5.2.10, Section 5.2.11, Section 5.2.12, Section 5.2.14,
Section 5.3.12, Section 7.1, Section 7.2

Japanese Manual Version SH-081083-L

This manual confers no industrial rights or any rights of any other kind, nor does it confer any patent licenses.
Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property rights which may
occur as a result of using the contents noted in this manual.
© 2012 MITSUBISHI ELECTRIC CORPORATION

617
Memo

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

619
Microsoft, Microsoft Access, Excel, Windows, Visual Basic, Visual C++, Visual Studio, Windows, Windows Vista, and
Windows XP are registered trademarks or trademarks of Microsoft Corporation in the United States and other countries.
Ethernet is a registered trademark or trademark of Xerox Corporation.
The company names, system names and product names mentioned in this manual are either registered trademarks or
trademarks of their respective companies.
In some cases, trademark symbols such as '™' or '®' are not specified in this manual.
SPREAD
Copyright (C) 2004 FarPoint Technologies, Inc.

620
SH(NA)-081085ENG-L(1701)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.